FIELD OF DISCLOSURE

The present disclosure relates generally to the field of communications, and in particular to a method performed by a network node for mapping a wireless connection to a network slice, a network node for mapping a wireless device connection to a network slice, a corresponding method performed by a wireless device and a wireless device configured to perform a corresponding method

BACKGROUND

The third generation partnership project (3GPP) is currently working on

standardization of Release 14 of the Long Term Evolution (LTE) concept. FIG. 1 illustrates an LTE system architecture showing X2 logical interfaces between evolved Node Bs (eNBs) and Home eNB (HeNB) and S1 logical interfaces between eNB/HeNBs and Mobility Management Entity/Serving Gateway (MME/S-GW). In FIG. 1 , the LTE system architecture includes radio access nodes such as an eNB, HeNB, and HeNB Gateway (HeNB-GW), and evolved packet core nodes such as an MME/S-GW. Further, an S1 interface connects an HeNB or an eNB to an MME/S-GW. Further, an S1 interface connects an HeNB to an HeNB GW. An X2 interface connects peer eNBs and HeNBs and optionally connects eNBs and HeNBs via an X2 Gateway (X2 GW).

FIG. 2 illustrates one example of a network management system architecture for the LTE system architecture of FIG. 1. The node elements (NEs), also referred to as eNB or HeNB, are managed by a domain manager (DM). A domain manager may also be referred to as an operation and support system (OSS). A domain manager may further be managed by a network manager (NM). In FIG. 2, two node elements are interfaced by an X2 logical interface. The interface between two domain managers is referred to as ltf-P2P logical interface. The management system may configure the network elements, as well as receive observations associated with features in the network elements. For example, a domain manager observes and configures network elements, while a network manager observes and configures the domain manager, as well as the network elements via the domain manager. By means of configuration via the domain manager, network manager and related interfaces, functions over the X2 and S1 interfaces may be carried out in a coordinated way throughout the radio access network (RAN), eventually involving a core network (e.g., MME and S-GWs). 3GPP does not specify how the LTE architecture should evolve to meet the challenges of the fifth generation wireless systems (5G) time frame. However, there may be evolved counterparts of the S1 , X2, and Uu logical interfaces. Further, any new radio access technology (RAT) would be integrated with the LTE radio interface at RAN level in a similar fashion as the way LTE Dual Connectivity is defined. FIG. 3 Illustrates a 5G radio access network (RAN) architecture. In FIG. 3, gNBs (e.g., 5G New Radio (NR) eNB, evolved LTE (eLTE) eNB, evolution of eNB that supports connectivity to Evolved Packet Core (EPC) and Next Generation Core (NGC)) provide the NR user plane (U-plane) and NR control plane (C-plane) protocol terminations towards the User Equipment (UE). Further, eLTE eNBs provide the Evolved UMTS Terrestrial Radio Access (E-UTRA) U-plane and C- plane protocol terminations towards the UE. The logical nodes in the New RAN are interconnected with each other via the Xn interface. Also, the logical nodes in the New RAN are connected to the NGC via the Next Generation (NG) interface. The NG interface supports a many-to-many relationship between NG Control Plane/User Plane Gateways (NG-CP/UPGWs) and the logical nodes in the New RAN.

Network slicing is about creating logically separated partitions of the network, with each partition addressing different business purposes. These "network slices" are logically separated to a degree so that they can be regarded and managed as networks of their own. This new concept potentially applies to both LTE Evolution and 5G RAT, which is also referred to as 5G NR. The key driver for introducing network slicing is business expansion (e.g., improving the cellular operator's ability to serve other industries by offering connectivity services with different network characteristics such as performance, security, robustness, and complexity). There will be one shared radio access network (RAN) infrastructure that will connect to several core network (CN) instances with one or more common control network functions (CCNF) interfacing the RAN plus additional core network functions which may be slice-specific. As the core network functions are being virtualized, the operator will instantiate all or a portion of a new core network when a new slice is to be supported. An example of a system having network slicing is shown in FIG. 4. In FIG. 4, Slice 0 may, for example, be a Mobile Broadband slice and Slice 1 may, for example, be a Machine Type Communication network slice.

However, current systems having network slicing do not support, for instance, all or a subset of the requested network slices for a UE connecting to the system or an incoming handover to a RAN. Further, these current systems do not support a UE requesting a network slice that is not allowed or available at a certain time. Accordingly, there is a need for improved techniques for systems having network slicing. In addition, other desirable features and characteristics of the present disclosure will become apparent from the subsequent detailed description and embodiments, taken in conjunction with the accompanying figures and the foregoing technical field and background.

The Background section of this document is provided to place embodiments of the present disclosure in technological and operational context, to assist those of skill in the art in understanding their scope and utility. Unless explicitly identified as such, no statement herein is admitted to be prior art merely by its inclusion in the Background section.

SUMMARY

The following presents a simplified summary of the disclosure in order to provide a basic understanding to those of skill in the art. This summary is not an extensive overview of the disclosure and is not intended to identify key/critical elements of embodiments of the disclosure or to delineate the scope of the disclosure. The sole purpose of this summary is to present some concepts disclosed herein in a simplified form as a prelude to the more detailed description that is presented later.

Briefly described, embodiments of the present disclosure relate to mapping a network slice. According to one aspect, a method performed by a network node (e.g., eNB, HeNB, gNB) comprises determining a second network slice to which to map a wireless device (e.g., UE) connection that is established, or requested to be established, to a first network slice. Further, the method includes mapping the wireless device connection to the second network slice.

According to another aspect, the second network slice is indicated as being a network slice to which the wireless device is allowed to connect.

According to another aspect, the method further includes obtaining an identifier indicating a network slice to which the wireless device is allowed to connect. Further, the method includes determining that the second network slice to which to map the wireless device is the network slice that the wireless device is allowed to connect based on the identifier. Further, the method includes mapping the wireless device connection to the second network slice associated with the identifier.

According to another aspect, the step of obtaining the identifier is during initial context setup with a core network.

According to another aspect, the method includes obtaining another identifier indicating a network slice to which the wireless device requests to connect.

According to another aspect, the step of obtaining the other identifier is during radio resource connection (RRC) signaling. According to another aspect, the second network slice is used to replace the first network slice when that first network slice is unavailable.

According to another aspect, the step of mapping is responsive to determining that the first network slice is unavailable.

According to another aspect, the second network slice is a default network slice to which the network node autonomously maps the wireless device connection.

According to another aspect, the step of autonomously mapping is responsive to determining that there are no other suitable network slices to map the wireless device connection.

According to another aspect, the step of autonomously mapping is responsive to determining that a core network has not communicated a network slice that can be used for the wireless device connection.

According to another aspect, the network node is a core network node.

According to another aspect, the network node is a radio access network (RAN) node.

According to another aspect, the second network slice is a logical slice.

According to another aspect, the second network slice is a functional slice.

According to another aspect, the wireless device connection that is established, or requested to be established, to the first network slice includes the wireless device connection being mapped, or requested to be mapped, to the first network slice.

According to another aspect, the method includes establishing the wireless device connection to the first network slice. Further, the step of determining the second network slice is responsive to said establishing the wireless device connection.

According to another aspect, the method includes receiving, by the network node, from the wireless device, an indication of a request to establish the wireless device connection to the first network slice. Further, the step of determining the second network slice is responsive to the request to establish the wireless device connection.

According to another aspect, the method includes transmitting, by the network node, to the wireless device or a core network, an indication that the wireless device connection is mapped to the second network slice.

According to another aspect, during a handover of the wireless device from the network node to a second network node, the method includes transmitting, by the network node, to the second network node, an indication that the wireless device connection is mapped to the second network slice.

According to one aspect, a network node comprises a processing circuit configured to determine a second network slice to which to map a wireless device connection that is established, or requested to be established, to a first network slice. Further, the processing circuit is configured to map the wireless device connection to the second network slice.

According to one aspect, a method performed by a second network node comprises, during a handover of a wireless device from a first network node to the second network node, receiving, by the second network node, from the first network node, an indication that the wireless device connection is mapped to a certain network slice.

According to one aspect, a second network node comprises a processing circuit configured to, during a handover of a wireless device from a first network node to the second network node, receive, by the second network node, from the first network node, an indication that the wireless device connection is mapped to a certain network slice.

According to one aspect, a method performed by a wireless device comprises receiving, by the wireless device, from a network node, an indication that the wireless device connection is mapped to a second network slice responsive to establishing, or requesting to establish, a wireless device connection to a first network slice via a network node.

According to another aspect, the method includes transmitting, by the wireless device, to the network node, an indication of a request to establish the wireless device connection to the first network slice. Further, the step of receiving is responsive to said transmitting.

According to one aspect, a wireless device comprises a processing circuit configured to receive, from a network node, an indication that the wireless device connection is mapped to a second network slice responsive to establishing, or requesting to establish, a wireless device connection to a first network slice via a network node.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure will now be described more fully hereinafter with reference to the accompanying drawings, in which embodiments of the disclosure are shown. However, this disclosure should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Like numbers refer to like elements throughout. FIG. 1 illustrates an LTE system architecture showing X2 logical interfaces between eNBs and HeNBs and S1 logical interfaces between eNB/HeNBs and MME/S-GW.

FIG. 2 illustrates one example of a network management system architecture for the LTE system architecture of FIG. 1.

FIG. 3 Illustrates a 5G radio access network (RAN) architecture.

FIG. 4 illustrates one example of a system having network slicing.

FIG. 5 illustrates one embodiment of a system for mapping a network slice in accordance with various aspects as described herein.

FIG. 6 illustrates another embodiment of a system for mapping a network slice in accordance with various aspects as described herein.

FIG. 7 illustrates another embodiment of a system for mapping a network slice in accordance with various aspects as described herein.

FIGs. 8A-B illustrate embodiments of a network node in accordance with various aspects as described herein.

FIG. 9 illustrates embodiments of a method performed by a network node of mapping a network slice in accordance with various aspects as described herein.

FIG. 10 illustrates another embodiment of a method performed by a network node of mapping a network slice in accordance with various aspects as described herein.

FIG. 11 illustrates another embodiment of a method performed by a network node of mapping a network slice in accordance with various aspects as described herein.

FIG. 12 illustrates another embodiment of a method performed by a network node of mapping a network slice in accordance with various aspects as described herein.

FIGs. 13A-B illustrate embodiments of a wireless device in accordance with various aspects as described herein.

FIG. 14 illustrates one embodiment of a method performed by a wireless device of mapping a network slice in accordance with various aspects as described herein.

DETAILED DESCRIPTION

For simplicity and illustrative purposes, the present disclosure is described by referring mainly to an exemplary embodiment thereof. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. However, it will be readily apparent to one of ordinary skill in the art that the present disclosure may be practiced without limitation to these specific details. In this description, well known methods and structures have not been described in detail so as not to unnecessarily obscure the present disclosure.

As part of the evolution of LTE based systems into future generation mobile networks, the concept of network slicing is being developed. Network slicing is associated with defining, realizing, and operating end-to-end logical networks by means of dedicated or shared resources in the core network or the RAN and associated management system(s). However, current systems may not support all or a subset of the requested network slice such as for a UE connecting to the network, performing an incoming handover to a RAN, or requesting an unavailable or unsupported network slice. Such scenarios would benefit from a remapping mechanism that enables remapping the UE connection to a supported network slice. Further, it is not always possible to explicitly query the core network in order to have a certain network slice remapped to another network slice (e.g., some mobility mechanisms such as X2/Xn handover do not involve the core network signaling during the handover phase). Also, for some procedures (e.g., state transitions), this extra query may impact performance for the UE (e.g., delay the transition). When this remapping with core network involvement is possible, it should not impact regular mobility and connection handling performance.

Consequently, this disclosure describes various techniques for systems having network slicing. For instance, one of these techniques include establishing and maintaining (such as during mobility) a UE connection to a network slice even though the RAN may not support the network slice the UE and the core network prefer. Further, this disclosure describes mechanisms for a network slice to be remapped during connection handling and mobility signaling according to the following principles:

· By the core network, when there is naturally a signaling interaction between the

RAN and the core network and performance is thus not impacted;

• By the RAN as action following prior negotiation with the core network during connection setup; and

• By the RAN autonomously, when involving the core network would not be a practical solution and if prior negotiation did not take place.

As such, this disclosure describes multiple embodiments for re-mapping UE connections to different slices. These embodiments enable a UE to continue receiving network services, without loss of connectivity, even in scenarios with limited slice availability in certain areas or over a certain time of the day. Another advantage includes enabling the core network to re-map a UE connection and then inform a RAN so that the RAN can optimize resource usage and fulfill service requirements suited for the UE connection or services. In yet another advantage, re-mapping rules may be pre-configured in the RAN so that the RAN can perform a re-mapping in certain mobility or connection setup scenarios without first notifying the core network, which would add additional delay affecting the UE and system performance. Accordingly, FIG. 5 illustrates one embodiment of a system 500 for mapping a network slice of a core network in accordance with various aspects as described herein. In FIG. 5, a wireless device 501 (e.g., UE) communicates with a radio access network (RAN) 510 via one or more network nodes 511a,b (e.g., eNB, HeNB, gNB). The RAN may be configured to support one or more wireless communication systems such as NR, LTE, LTE-NR, 5G, UMTS, GSM, and the like. Further, the RAN 510 communicates with a core network 520 via a core network node 521 (MME/S-GW).

In one example embodiment, the wireless device 501 may transmit, to the first network node 511 a, an indication of a request to establish a wireless device connection 531 to a first network slice 525. The first network slice 525 may be a dedicated or shared resource (e.g., processing, memory, and the like) in the core network 520 or the RAN 510 and the associated management system. The first network node 511a may then receive this indication, and in response, may establish the wireless device connection 531 to the first network slice 525, as represented by reference 533. Further, the first network node 511 a determines a second network slice 527 to which to map the wireless device connection 531 that is established, or requested to be established, to the first network slice 525. In response, the network node 511a maps (such as by its map circuit 513) the wireless device connection 531 to the second network slice 527, as represented by reference 535. Like the first network slice 525, the second network slice 527 may be a dedicated or shared resource (e.g., processing, memory, and the like) in the core network 520 or the RAN 510 and the associated management system. In addition, the network node 511 a may transmit, to the wireless device 501 or the core network node 521 , an indication that the wireless device connection 531 is mapped to the second network slice 527.

In another example embodiment, the wireless device 501 may transmit, to the network node 511 a, an indication of a request to establish the wireless device connection 531 to the first network slice 525. The network node 511 a may then receive this indication, and in response, may obtain an identifier indicating the first network slice 525 to which the wireless device 501 requests to connect. The identifier indicating the first network slice 525 may be a network slice selection assistance information (NSSAI) or session management NSSAI (SM-NSSAI), or the like. Further, the network node 511a may establish the wireless device connection 531 to the first network slice 525 based on the identifier. The network node 511 a may receive, from another network node or the core network 521 , an indication of a second network slice 527 to which the wireless device 501 is allowed to connect. In response, the network node 511a obtains an identifier indicating a network slice to which the wireless device is allowed to connect. Also, the network node 511a determines that the second network slice 527 to which to map the wireless device connection 531 is the network slice that the wireless device 501 is allowed to connect based on the identifier. The network node 511 a then maps the wireless device connection 531 to the second network slice 527 associated with the identifier. In addition, the network node 511a may transmit, to the wireless device 501 or the core network node 521 , an indication that the wireless device connection 531 is mapped to the second network slice 527.

In another example embodiment, the network node 511a may determine that there are no other suitable network slices to map the wireless device connection 531. Additionally or alternatively, the network node 511 a may determine that the core network 520 has not communicated a network slice that can be used for the wireless device connection 531. In response, the network node 511a autonomously maps the wireless device connection 531 to a default network slice.

In another example embodiment, during a handover of the wireless device 501 from the network node 511a to another network node 511 b, the network node 511 a transmits, to the other network node 511 b, an indication that the wireless device connection 531 is mapped to the second network slice 527. The other network node 511 b then receives this indication.

Additionally or alternatively, each network node 511 a,b may be configured to support one or more wireless communication systems (e.g., NR, LTE, LTE-NR, 5G, UMTS, GSM, or the like). Further, each network node 511 a,b may be a base station (e.g., eNB, gNB, HeNB), an access point, a wireless router, or the like. Each network node 511 a,b may serve wireless devices such as the wireless device 501. The wireless device 501 may be configured to support one or more wireless communication systems (e.g., NR, LTE, LTE-NR, 5G, UMTS, GSM, or the like). The wireless device 501 may be a UE, a mobile station (MS), a terminal, a cellular phone, a cellular handset, a personal digital assistant (PDA), a smartphone, a wireless phone, an organizer, a handheld computer, a desktop computer, a laptop computer, a tablet computer, a set-top box, a television, an appliance, a game device, a medical device, a display device, a metering device, or the like. The core network node 521 may be configured to support one or more wireless communication systems (e.g., NR, LTE, LTE-NR, 5G, UMTS, GSM, or the like). The core network node 521 may be an

MME/S-GW node, NG-CP/UP GW node, or the like. In one example embodiment, during Initial Context Setup over an NG-C/NG2 logical interface, the core network communicates to the RAN one or more Slice identifiers (IDs) (may or may not be represented by a network slice selection assistance information (NSSAI) or session management NSSAI (SM-NSSAI), which uniquely represent the network slice(s) the UE is allowed to connect to, and these identifiers are different from the ones

communicated by the UE to the 5G RAN during RRC connection establishment, as a remapping has taken place in the core network. The RAN can then take this information into account when assigning resources to the UE connection.

In another example embodiment, during either NG Setup or later, in a UE-specific way, during Initial Context Setup, the core network provides the RAN with a number of network slices which are allowed to be used as replacement of a particular network slice when such network slice is not available for any reason. The RAN is then allowed to remap UE connections to such less-preferred network slices when needed during any subsequent signaling, for example, RAN-internal handovers, dual connectivity and because of internal radio resource management-related reasons in the RAN. This makes it possible to perform remapping for procedure that does not involve core network signaling such as X2 or Xn handover procedure or context fetch procedures. It also makes it possible to re-map UE connections to other slices during RRC connection setup, prior to receiving additional information from the core network. Information about alternative network slices the core network allows can be passed from source to target during RAN-based handovers and between master and secondary nodes as part of dual connectivity establishment.

In another example embodiment, if a prior negotiation did not take place, or if no alternative network slices are suitable, the RAN may autonomously remap the provided network slice to a default network slice and to the RAN resources corresponding to such default. It is possible to devise a signaling mechanism where the core network gives permission to the RAN to autonomously remap and if such permission is not given, the RAN should reject the corresponding protocol data unit (PDU) session. The core network needs to be informed that a remapping to default network slice/default policies has occurred when that is allowed. Such solution would also enable the core network to perform the re-mapping at later stage to a different slice or policy (e.g. after handover) in case the RAN re-mapping to the default slice or policy was not considered to be the best suited.

FIG. 6 illustrates another embodiment of a system 600 for mapping a network slice in accordance with various aspects as described herein. In FIG. 6, the system 600 includes a wireless device 601 , a network node 611 , and a core network node 621. The network node 611 may establish a wireless device connection with the wireless device 601. The wireless device 601 may transmit, to the network node 611 via a radio resource control (RRC) protocol, an indication of a requested slice 641 , as represented by block 603. The network node 611 may receive this indication of the requested slice 641 via the RRC protocol, as represented by block 613. During initial context setup, the core network node 621 may transmit, to the network node 611 , an indication of an allowed slice 643, as represented by block 623. Further, the network node 611 may receive, from the core network node 621 , the indication of the allowed slice 643, as represented by block 615. The network node 611 then determines that the requested slice 641 and the allowed slice 643 are different slices, as represented by block 617. In response, the network node 611 remaps the wireless device connection to the allowed slice 643, as represented by block 619. In addition, the network node 611 may transmit, to the wireless device 601 or the core network node 621 , an indication that the wireless device connection is mapped to the replacement network slice.

FIG. 7 illustrates another embodiment of a system 700 for mapping a core network slice in accordance with various aspects as described herein. In FIG. 7, the system 700 includes a wireless device 701 , a network node 711 , and a core network node 721. The network node 711 may establish a wireless device connection with the wireless device 701. The wireless device 701 may transmit, to the network node 711 via the RRC protocol, an indication of a request for a particular slice 741 , as represented by block 703. The network node 711 may receive this indication via the RRC protocol, as represented by block 712. During initial context setup, the core network node 721 may transmit, to the network node 711 , an indication of a slice used to replace the particular network slice 743, as represented by block 723. The network node 711 may then receive, from the core network node 721 , the indication of the slice used to replace the particular network slice 743, as represented by block 713.

In FIG. 7, the network node 711 may then transmit, to the wireless device 701 via RRC signaling, an indication of the slice used to replace the particular network slice 743, as represented by block 714. In response, the wireless device 701 may transmit, to the network node 711 via RRC signaling, an acknowledgement of the slice used to replace the particular network slice 743, as represented by block 705. The network node 711 then determines that the particular slice 741 is unavailable, as represented by block 715. In response, the network node 711 remaps the wireless device connection to the slice used to replace the particular network slice 743, as represented by block 717. In addition, the network node 711 may transmit, to the wireless device 701 or the core network node 721 , an indication that the wireless device connection is mapped to the replacement network slice.

FIGs. 8A-B illustrate embodiments of a network node 800a-b in accordance with various aspects as described herein. In FIG. 8A, the network node 800a (e.g., base station) may include processing circuit(s) 801a, radio frequency (RF) communications circuit(s) 805a, antenna(s) 807a, the like, or any combination thereof. The communication circuit(s) 805a may be configured to transmit or receive information to or from one or more network nodes, one or more core network nodes, or one or more wireless devices via any

communication technology. This communication may occur using the one or more antennas 807a that are either internal or external to the network node 800a. The processing circuit(s) 801 a may be configured to perform processing as described herein (e.g., the methods of FIGs. 9-12) such as by executing program instructions stored in memory 803a. The processing circuit(s) 801a in this regard may implement certain functional means, units, or modules.

In FIG. 8B, the network node 800b may implement various functional means, units, or modules (e.g., via the processing circuit(s) 801 a in FIG. 8A or via software code). These functional means, units, or modules (e.g., for implementing the methods of FIGs. 9-12) may include a receiving module or unit 811 b for receiving, from a wireless device, an indication of a request to establish a wireless device connection to a first network slice. Further, these functional means, units, or modules may include an obtaining module or unit 813b for obtaining an identifier indicating a network slice to which the wireless device is allowed to connect. Also, these functional means, units, or modules may include an establishing module or unit 815b for establishing the wireless device connection to the first network slice based on the identifier responsive to the request.

Furthermore, the receiving module or unit 811 b may include receiving, from another network node or a core network node, an indication of a second network slice to which the wireless device is allowed to connect. Further, the obtaining module or unit 813b may include obtaining an identifier indicating a network slice to which the wireless device is allowed to connect. Also, these functional means, units, or modules include a determining module or unit 813b for determining a second network slice to which to map a wireless device connection that is established, or requested to be established, to a first network slice. For instance, the determining module or unit 817b may include determining that the second network slice to which to map the wireless device is the network slice that the wireless device is allowed to connect based on the identifier. These functional means, units, or modules include a mapping module or unit 819b for mapping the wireless device connection to the second network slice. In one example, the mapping module or unit 815b may include mapping the wireless device connection to the second network slice associated with the identifier. In another example, the mapping module or unit 815b may include autonomously mapping a wireless device connection to a default network slice responsive to determining that there are no other suitable network slices to map the wireless device connection or determining that the core network has not communicated a network slice that can be used for the wireless device connection. Finally, these functional means, units, or modules include a transmitting module or unit 821 b for transmitting, to the wireless device or the core network node, an indication that the wireless device connection is mapped to the second network slice.

FIG. 9 illustrates one embodiment of a method 900 performed by a network node of mapping a network slice in accordance with various aspects as described herein. In FIG. 9, the method 900 may start, for instance, at block 901 where it includes determining a second network slice to which to map a wireless device connection that is established, or requested to be established, to a first network slice. At block 903, the method 900 includes mapping the wireless device connection to the second network slice.

FIG. 10 illustrates another embodiment of a method 1000 performed by a network node of mapping a network slice in accordance with various aspects as described herein. In FIG. 10, the method 1000 may start, for instance, at block 1001 where it may include receiving, from a wireless device, an indication of a request to establish a wireless device connection of a wireless device to a first network slice. At block 1003, the method 1000 may include obtaining an identifier indicating the first network slice to which the wireless device requests to connect. At block 1005, the method 1000 may include establishing the wireless device connection to the first network slice based on the identifier responsive to the request. At block 1007, the method 1000 may include receiving, from another network node or a core network node, an indication of a second network slice to which the wireless device is allowed to connect. At block 1009, the method 1000 includes obtaining an identifier indicating a network slice to which the wireless device is allowed to connect. At block 1011 , the method 1000 includes determining that the second network slice to which to map the wireless device is the network slice that the wireless device is allowed to connect based on the identifier. At block 1013, the method 1000 includes mapping the wireless device connection to the second network slice associated with the identifier. At block 1015, the method 1000 may include transmitting, to the wireless device or the core network node, an indication that the wireless device connection is mapped to the second network slice.

FIG. 11 illustrates another embodiment of a method 1100 performed by a network node of mapping a network slice in accordance with various aspects as described herein. In FIG. 11 , the method 1100 may start, for instance, at block 1101 where it may include determining that there are no other suitable network slices to map the wireless device connection. At block 1103, the method 1100 may include determining that a core network has not communicated a network slice that can be used for the wireless device connection. In response, the method 1100 includes autonomously mapping a wireless device connection to a default network slice, as represented by block 1105. FIG. 12 illustrates another embodiment of a method 1200 performed by a second network node of mapping a network slice in accordance with various aspects as described herein. During or associated with a handover of a wireless device from a first network node to the second network node, the method 1200 includes receiving, from the first network node, an indication that the wireless device connection is mapped to a certain network slice, as represented by block 1201.

FIGs. 13A-B illustrate embodiments of a wireless device 1300a, b in accordance with various aspects as described herein. In FIG. 13A, the wireless device 1300a (e.g., UE) may include processing circuit(s) 1301 a, radio frequency (RF) communications circuit(s) 1305a, antenna(s) 1307a, the like, or any combination thereof. The communication circuit(s) 1305a may be configured to transmit or receive information to or from one or more network nodes or one or more other wireless devices via any communication technology. This

communication may occur using the one or more antennas 1307a that are either internal or external to the wireless device 1300a. The processing circuit(s) 1301a may be configured to perform processing as described herein (e.g., the method of FIG. 14) such as by executing program instructions stored in memory 1303a. The processing circuit(s) 1301 a in this regard may implement certain functional means, units, or modules.

In FIG. 13B, these functional means, units, or modules (e.g., for implementing the method of FIG. 14) may include a transmitting module or unit 1311 b for transmitting, to a network node, an indication of a request to establish a wireless device connection of the wireless device to a first network slice. These functional means, units, or modules include a receiving module or unit 1313b for receiving, from the network node, an indication that the wireless device connection is mapped to a second network slice responsive to establishing, or requesting to establish, a wireless device connection to a first network slice via the network node.

FIG. 14 illustrates one embodiment of a method 1400 performed by a wireless device of mapping a network slice in accordance with various aspects as described herein. In FIG. 14, the method 1400 may start, for instance, at block 1401 where it may include transmitting, to a network node, an indication of a request to establish a wireless device connection of the wireless device to a first network slice. At block 1403, the method 1400 includes receiving, from the network node, an indication that the wireless device connection is mapped to a second network slice responsive to establishing, or requesting to establish, a wireless device connection to a first network slice via the network node.

In one example embodiment, a method performed by a network node may include determining a core network slice to which to map a wireless device connection that is established, or requested to be established, to a different network slice. Further, the method may include mapping the wireless device connection to the determined core network slice.

In another example embodiment, the core network slice may be indicated as being a core network slice that the wireless device is allowed to connect.

In another example embodiment, the method may include obtaining an identifier indicating a core network slice that the wireless device is allowed to connect. Further, the step of determining the core network slice may include determining that the core network slice to which to map the wireless device is the core network slice that the wireless device is allowed to connect based on the identifier. In addition, the step of mapping may include mapping the wireless device connection to the core network slice associated with the identifier.

In another example embodiment, the step of obtaining the identifier may be during initial context setup with the core network.

In another example embodiment, the method may include obtaining another identifier indicating a core network slice that the wireless device requests to connect.

In another example embodiment, the step of obtaining the other identifier may be during radio resource connection (RRC) signaling.

In another example embodiment, the core network slice may be used to replace the different core network slice when that different core network slice is unavailable.

In another example embodiment, the step of mapping the wireless device connection may be responsive to determining that the different core network slice is unavailable.

In another example embodiment, the core network slice may be a default core network slice to which the network node autonomously maps the wireless device connection.

In another example embodiment, the step of autonomously mapping may be responsive to determining that there are no other suitable network slices to map the wireless device connection.

In another example embodiment, the step of autonomously mapping may be responsive to determining that the core network has not communicated a core network slice that can be used for the wireless device connection.

In another example embodiment, the network node may be a core network node.

In another example embodiment, the network node may be a radio access network node. In another example embodiment, the network slice may be a logical slice. The network is sliced logically into multiple virtual networks, with each virtual network being a logical slice. Each logical slice may be optimized to provide a specific vertical application to support network services. The network may include at least one of a RAN and a core network. In one example, the network is a core network. In another example, the network is a RAN and a core network.

In another example embodiment, the network slice may be a functional slice. The functional slice corresponds to functionality needed by a UE to find the correct network, access the network, and attach to a core network with a set of functionality needed by that UE. For example, a wireless device such as a gas meter can find a functional slice that is tailored to small, infrequent messages. In another example, a wireless device such as a smartphone can find one or more functional slices that are each tailored to a specific purpose such as streaming video, voice calls, Internet browsing, video calls, and the like. The network may include at least one of a RAN and a core network.

In one example embodiment, a network node may include a processing circuit. The processing circuit may be configured to determine a core network slice to which to map a wireless device connection that is established, or requested to be established, to a different network slice. Further, the processing circuit may be further configured to map the wireless device connection to the determined core network slice.

ABBREVIATIONS

Abbreviation Explanation

AS Access Stratum

CN Core Network

ID Identifier

LTE Long Term Evolution

NAS Non Access Stratum

NG New Generation

NG-C New Generation-Core Network

NR New Radio

NSSAI Network Slice Selection Assistance Information

NW Network

PDU Protocol Data Unit

RAN Radio Access Network

RRC Radio Resource Control

SM-NSSAI Session Management-Network Slice Selection Assistance Information SRB Signaling Radio Bearer SLA Service Level Agreement

UE User Equipment

UMTS Universal Mobile Telecommunications System Furthermore, the various aspects described herein may be implemented using standard programming or engineering techniques to produce software, firmware, hardware (e.g., circuits), or any combination thereof to control a computing device to implement the disclosed subject matter. It will be appreciated that some embodiments may be comprised of one or more generic or specialized processors such as microprocessors, digital signal processors, customized processors and field programmable gate arrays (FPGAs) and unique stored program instructions (including both software and firmware) that control the one or more processors to implement, in conjunction with certain non-processor circuits, some, most, or all of the functions of the methods, devices and systems described herein. Alternatively, some or all functions could be implemented by a state machine that has no stored program instructions, or in one or more application specific integrated circuits

(ASICs), in which each function or some combinations of certain of the functions are implemented as custom logic circuits. Of course, a combination of the two approaches may be used. Further, it is expected that one of ordinary skill, notwithstanding possibly significant effort and many design choices motivated by, for example, available time, current technology, and economic considerations, when guided by the concepts and principles disclosed herein will be readily capable of generating such software instructions and programs and ICs with minimal experimentation.

The term "article of manufacture" as used herein is intended to encompass a computer program accessible from any computing device, carrier, or media. For example, a computer-readable medium may include: a magnetic storage device such as a hard disk, a floppy disk or a magnetic strip; an optical disk such as a compact disk (CD) or digital versatile disk (DVD); a smart card; and a flash memory device such as a card, stick or key drive. Additionally, it should be appreciated that a carrier wave may be employed to carry computer-readable electronic data including those used in transmitting and receiving electronic data such as electronic mail (e-mail) or in accessing a computer network such as the Internet or a local area network (LAN). Of course, a person of ordinary skill in the art will recognize many modifications may be made to this configuration without departing from the scope or spirit of the subject matter of this disclosure.

Throughout the specification and the embodiments, the following terms take at least the meanings explicitly associated herein, unless the context clearly dictates otherwise.

Relational terms such as "first" and "second," and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. The term "or" is intended to mean an inclusive "or" unless specified otherwise or clear from the context to be directed to an exclusive form. Further, the terms "a," "an," and "the" are intended to mean one or more unless specified otherwise or clear from the context to be directed to a singular form. The term "include" and its various forms are intended to mean including but not limited to. References to "one embodiment," "an embodiment," "example embodiment," "various embodiments," and other like terms indicate that the embodiments of the disclosed technology so described may include a particular function, feature, structure, or

characteristic, but not every embodiment necessarily includes the particular function, feature, structure, or characteristic. Further, repeated use of the phrase "in one embodiment" does not necessarily refer to the same embodiment, although it may. The terms "substantially," "essentially," "approximately," "about" or any other version thereof, are defined as being close to as understood by one of ordinary skill in the art, and in one non-limiting embodiment the term is defined to be within 10%, in another embodiment within 5%, in another embodiment within 1 % and in another embodiment within 0.5%. A device or structure that is "configured" in a certain way is configured in at least that way, but may also be configured in ways that are not listed.