Network-initiated slice-based session switching

Abstract

Disclosed herein are systems and methods for network-initiated slice-based handover in a cellular communication system. In one embodiment, a method in a cellular communication system includes: detecting, at a network node in a core network of the cellular communication system, a triggering event for a network slice handover for a session of a specific wireless communication device. The method further includes: identifying, at the network node and in response to detecting the triggering event, a target network slice for the network slice handover, and sending a message to a policy and control function (PCF) in the core network to initiate a network slice handover of the session from a source network slice to a target network slice. The method further includes: receiving, at the PCF, a message initiating the network slice handover, and performing an action resulting in the network slice handover.

Description

Technical Field

[0001] The present disclosure relates to session switching in a cellular communication system, and in particular, to session switching in a cellular communication system supporting network slicing. Background Art

[0002] Network slicing uses virtualization technologies (e.g., software-defined networking (SDN) and network function virtualization (NFV)) to allow the creation of multiple virtual (i.e., logical) networks on top of a common shared physical infrastructure. These virtual networks are called network slices. In turn, network slices can be customized to meet the needs of different use cases.

[0003] Network slicing has been proposed in the 3rd Generation Partnership Project (3GPP) for the fifth generation system (5GS). Network slicing in 5GS leads to many new features that can be provided by 5GS, but challenges still arise when implementing these features using network slicing using existing 5GS mechanisms. Summary of the invention

[0004] Disclosed herein are systems and methods for network-initiated slice-based handover in a cellular communication system. In one embodiment, a method for network slice handover in a cellular communication system comprises: at a network node in a core network of the cellular communication system, detecting a triggering event for a network slice handover for a session of a specific wireless communication device. The method further comprises: at the network node and in response to detecting a triggering event for the network slice handover, identifying a target network slice for the network slice handover of the session of the specific wireless communication device, and sending a message to a policy and control function (PCF) in the core network to initiate a network slice handover of the session of the specific wireless communication device from a source network slice to a target network slice. The method further comprises: at the PCF, receiving a message from the network node to initiate a network slice handover of the session of the specific wireless communication device from a source network slice to a target network slice, and performing an action that causes a network slice handover of the session of the specific wireless communication device from the source network slice to the target network slice. In this way, session handover between network slices can be provided.

[0005] In one embodiment, the message initiating the network slice handover includes information identifying the target network slice. In one embodiment, the information identifying the target network slice is Subscription Network Slice Selection Assistance Information (S-NSSAI) of the target network slice.

[0006] In one embodiment, performing an action resulting in a network slice switch includes: sending a request to a session management function (SMF) in the core network to replace a session of a specific wireless communication device using a source network slice with a new session using a target network slice. In one embodiment, the request includes information identifying the target network slice. In one embodiment, the information identifying the target network slice is the S-NSSAI of the target network slice. In one embodiment, the method further includes: receiving, at the SMF, a request to replace a session of the specific wireless communication device using the source network slice with a new session using the target network slice, and sending an instruction to the specific wireless communication device via an access and mobility function (AMF) in the core network to replace the session using the source network slice with the new session using the target network slice. In one embodiment, the instruction is an instruction to trigger the wireless communication device to initiate a session establishment, through which a new session is established on the target network slice. In one embodiment, the instruction includes information identifying the target network slice. In one embodiment, the information identifying the target network slice is the S-NSSAI of the target network slice. In one embodiment, the instruction includes information indicating a reason for the instruction to replace the session using the source network slice with the new session using the target network slice. In one embodiment, the instruction includes information indicating an amount of time that the new session is permitted to use the target network slice.

[0007] In one embodiment, the method further comprises: receiving, at the wireless communication device, an instruction to replace a session using the source network slice with a new session using the target network slice, and in response to the instruction, initiating a process of establishing a new session using the target network slice. In one embodiment, the method further comprises: presenting, at the wireless communication device, a notification regarding the network slice switch, the notification being an audio notification, a visual notification, or an audio-visual notification.

[0008] In one embodiment, the triggering event for network slice switching is based on: (a) the location of a particular wireless communication device, (b) a location or area associated with a source network slice, (c) a location or area associated with a target network slice, (d) payment-related information, or (e) a combination of any combination of two or more of (a) and (b) to (d).

[0009] In one embodiment, the trigger event for network slice switching is a time-based trigger event.

[0010] In one embodiment, the source network slice is associated to a first subscriber identity module (SIM) of a wireless communication device, the target network slice is associated to a second SIM of the wireless communication device, and the first SIM and the second SIM are associated to the same network operator.

[0011] In one embodiment, the network node is a unified data management function (UDM).

[0012] Corresponding embodiments of a cellular communication system are also disclosed. In one embodiment, a cellular communication system comprises: a network node in a core network of the cellular communication system, wherein the network node is adapted to: detect a triggering event for a network slice switch for a session of a specific wireless communication device. The network node is further adapted to: in response to detecting a triggering event for the network slice switch, identify a target network slice for the network slice switch for the session of the specific wireless communication device, and send a message to a PCF in the core network to initiate a network slice switch for the session of the specific wireless communication device from a source network slice to a target network slice. The network node is further adapted to: at the PCF, receive from the network node a message initiating a network slice switch for the session of the specific wireless communication device from a source network slice to a target network slice, and perform an action resulting in a network slice switch for the session of the specific wireless communication device from the source network slice to the target network slice.

[0013] An embodiment of a method for operation of a network node in a core network of a cellular communication system for network slice switching is also disclosed. In one embodiment, the method of operation of the network node includes: detecting a triggering event for a network slice switching of a session of a specific wireless communication device. The method further includes: in response to detecting the triggering event for the network slice switching, identifying a target network slice for the network slice switching of the session of the specific wireless communication device, and performing an action of initiating a network slice switching of the session of the specific wireless communication device from a source network slice to a target network slice.

[0014] In one embodiment, performing the action includes: sending a message to the PCF in the core network to initiate a network slice switch of a session of a specific wireless communication device from a source network slice to a target network slice.

[0015] In one embodiment, the message initiating the network slice handover includes information identifying the target network slice. In one embodiment, the information identifying the target network slice is the S-NSSAI of the target network slice.

[0016] In one embodiment, the source network slice is associated to a first SIM of a wireless communication device, the target network slice is associated to a second SIM of the wireless communication device, and the first SIM and the second SIM are associated to the same network operator.

[0017] In one embodiment, the network node is a UDM. In another embodiment, the network node is a PCF.

[0018] A corresponding embodiment of a network node for a core network of a cellular communication system for network slice switching is also disclosed. In one embodiment, the network node is adapted to: detect a triggering event for a network slice switching for a session of a specific wireless communication device. The network node is further adapted to: in response to detecting the triggering event for the network slice switching, identify a target network slice for the network slice switching of the session of the specific wireless communication device, and send a message to a PCF in the core network to initiate a network slice switching of the session of the specific wireless communication device from a source network slice to a target network slice.

[0019] In one embodiment, a physical infrastructure node of a network node of a core network of a cellular communication system for implementing network slice switching includes: a processing circuit configured to cause the physical infrastructure node to: detect a triggering event for a network slice switching of a session of a specific wireless communication device. The processing circuit is further configured to cause the physical infrastructure node to: in response to detecting the triggering event for the network slice switching, identify a target network slice for the network slice switching of the session of the specific wireless communication device, and send a message to a PCF in the core network to initiate a network slice switching of the session of the specific wireless communication device from a source network slice to a target network slice.

[0020] An embodiment of a method for operation of a PCF for a core network of a cellular communication system for network slice switching is also disclosed. In one embodiment, the method of operation of the PCF includes: receiving a message from a network node to initiate a network slice switching of a session of a specific wireless communication device from a source network slice to a target network slice. The method further includes: performing an action that causes a network slice switching of a session of the specific wireless communication device from the source network slice to the target network slice.

[0021] In one embodiment, the message initiating the network slice handover includes information identifying the target network slice. In one embodiment, the information identifying the target network slice is the S-NSSAI of the target network slice.

[0022] In one embodiment, performing an action resulting in a network slice switch includes sending a request to the SMF in the core network to replace a session of a specific wireless communication device using a source network slice with a new session using a target network slice. In one embodiment, the request includes information identifying the target network slice. In one embodiment, the information identifying the target network slice is an S-NSSAI of the target network slice.

[0023] In one embodiment, the source network slice is associated to a first SIM of a wireless communication device, the target network slice is associated to a second SIM of the wireless communication device, and the first SIM and the second SIM are associated to the same network operator.

[0024] In one embodiment, the network node is a UDM.

[0025] A corresponding embodiment of the PCF is also disclosed. In one embodiment, a PCF for a core network of a cellular communication system for network slice switching is adapted to: receive a message from a network node initiating a network slice switching of a session of a specific wireless communication device from a source network slice to a target network slice. The PCF is further adapted to: perform an action resulting in a network slice switching of the session of the specific wireless communication device from the source network slice to the target network slice.

[0026] A corresponding embodiment of a physical infrastructure node of a PCF for a core network of a cellular communication system for implementing network slice switching includes a network interface and a processing circuit associated with the network interface. The processing circuit is configured to cause the physical infrastructure node to: receive a message from a network node initiating a network slice switching of a session of a specific wireless communication device from a source network slice to a target network slice, and perform an action resulting in a network slice switching of the session of the specific wireless communication device from the source network slice to the target network slice.

[0027] An embodiment of a method for operating an SMF of a core network of a cellular communication system is also disclosed. In one embodiment, the method for operating the SMF includes: receiving a request from a PCF in the core network to replace a session of a specific wireless communication device using a source network slice with a new session using a target network slice, and sending an instruction to the specific wireless communication device via an access and mobility function (AMF) in the core network to replace the session using the source network slice with a new session using the target network slice.

[0028] In one embodiment, the request includes information identifying the target network slice. In one embodiment, the information identifying the target network slice is the S-NSSAI of the target network slice.

[0029] In one embodiment, the instruction is an instruction that triggers the wireless communication device to initiate session establishment, through which a new session is established on the target network slice.

[0030] In one embodiment, the instruction includes information identifying the target network slice. In one embodiment, the information identifying the target network slice is the S-NSSAI of the target network slice.

[0031] In one embodiment, the instruction includes information indicating the reason for the instruction to replace the session using the source network slice with a new session using the target network slice.

[0032] In one embodiment, the instruction includes information indicating an amount of time that the new session is permitted to use the target network slice.

[0033] In one embodiment, the source network slice is associated to a first SIM of a wireless communication device, the target network slice is associated to a second SIM of the wireless communication device, and the first SIM and the second SIM are associated to the same network operator.

[0034] A corresponding embodiment of the SMF is also disclosed. In one embodiment, an SMF is adapted to: receive a request from a PCF in a core network to replace a session of a specific wireless communication device using a source network slice with a new session using a target network slice, and send an instruction to the specific wireless communication device via the AMF in the core network to replace the session using the source network slice with the new session using the target network slice.

[0035] A corresponding embodiment of a physical infrastructure node of an SMF for a core network of a cellular communication system for implementing network slice switching includes a network interface and a processing circuit associated with the network interface. The processing circuit is configured to cause the physical infrastructure node to: receive a request from a PCF in the core network to replace a session of a specific wireless communication device using a source network slice with a new session using a target network slice, and send an instruction to the specific wireless communication device via the AMF in the core network to replace the session using the source network slice with a new session using the target network slice.

[0036] An embodiment of a method of operation of a wireless communication device for network slice switching in a cellular communication system is also disclosed. In one embodiment, the method of operation of the wireless communication device includes: receiving an instruction from a network node in a core network of the cellular communication system to replace a current session of the wireless communication device using a source network slice with a new session using a target network slice. The method further includes: in response to the instruction, initiating a process of establishing a new session using the target network slice.

[0037] In one embodiment, the instruction includes information identifying the target network slice. In one embodiment, the information identifying the target network slice is the S-NSSAI of the target network slice.

[0038] In one embodiment, the instruction includes information indicating the reason for the instruction to replace the session using the source network slice with a new session using the target network slice.

[0039] In one embodiment, the instruction includes information indicating an amount of time that the new session is permitted to use the target network slice.

[0040] In one embodiment, the method further comprises presenting a notification regarding the network slice switching from the source network slice to the target network slice, the notification being an audio notification, a visual notification, or an audio-visual notification.

[0041] In one embodiment, the source network slice is associated to a first SIM of a wireless communication device, the target network slice is associated to a second SIM of the wireless communication device, and the first SIM and the second SIM are associated to the same network operator.

[0042] Corresponding embodiments of wireless communication devices are also disclosed. In one embodiment, a wireless communication device for network slice switching in a cellular communication system is adapted to: receive an instruction from a network node in a core network of the cellular communication system to replace a current session of the wireless communication device using a source network slice with a new session using a target network slice, and in response to the instruction, initiate a process of establishing a new session using the target network slice.

[0043] In one embodiment, a wireless communication device for network slice switching in a cellular communication system includes: one or more transmitters, one or more receivers, and processing circuits associated with the one or more transmitters and the one or more receivers. The processing circuit is configured to enable the wireless communication device to: receive an instruction from a network node in a core network of the cellular communication system to replace a current session of the wireless communication device using a source network slice with a new session using a target network slice, and in response to the instruction, initiate a process of establishing a new session using the target network slice. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] The accompanying drawings incorporated in and forming a part of this specification illustrate several aspects of the disclosure and together with the description serve to explain the principles of the disclosure.

[0045] Figure 1 An example of a system including a fifth generation system (5GS) and IMS is shown;

[0046] Figure 2 Showing the network slice within 5GS;

[0047] Figure 3 An example of a wireless communication system in which embodiments of the present disclosure may be implemented is shown;

[0048] Figure 4A and 4B A network-initiated slice switching process according to an embodiment of the present disclosure is shown;

[0049] Figure 5A and 5B A network-initiated slice switching process according to another embodiment of the present disclosure is shown;

[0050] Figure 6 and 7 is a schematic block diagram of an example embodiment of a physical infrastructure node; and

[0051] Figure 8 and 9 is a schematic block diagram of an example embodiment of a wireless communication device, such as a user equipment (UE). DETAILED DESCRIPTION

[0052] The embodiments set forth below represent information that enables those skilled in the art to practice the embodiments, and illustrate the best mode for practicing the embodiments. When reading the following description according to the accompanying drawings, those skilled in the art will understand the concepts of the present disclosure, and will recognize the application of these concepts that are not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the present disclosure.

[0053] Radio Node: As used herein, a "radio node" is a radio access node or a wireless communication device.

[0054] Radio access node: As used herein, a "radio access node" or "radio network node" or "radio access network node" is any node in a radio access network (RAN) of a cellular communication network that operates to send and / or receive signals wirelessly. Some examples of radio access nodes include, but are not limited to, a base station (e.g., a new radio (NR) base station (gNB) in a third generation partnership project (3GPP) fifth generation (5G) NR network or an enhanced or evolved node B (eNB) in a 3GPP long term evolution (LTE) network), a high power or macro base station, a low power base station (e.g., a micro base station, a pico base station, a home eNB, etc.), a relay node, a network node that implements part of the functionality of a base station, or a network node that implements part of the functionality of some other type of radio access node.

[0055] Core network node: As used herein, a "core network node" is any type of node in a core network or any node that implements a core network function. Some examples of core network nodes include, for example, a mobility management entity (MME), a packet data network gateway (P-GW), a service capability exposure function (SCEF), a home subscriber server (HSS), etc. Some other examples of core network nodes include nodes that implement access and mobility functions (AMF), user plane functions (UPF), session management functions (SMF), authentication server functions (AUSF), network slice selection functions (NSSF), network exposure functions (NEF), network functions (NF) repository functions (NRF), policy control functions (PCF), unified data management (UDM), etc.

[0056] Communication device: As used herein, a "communication device" is any type of device that can access an access network. Some examples of communication devices include, but are not limited to: mobile phones, smart phones, sensor devices, meters, vehicles, household appliances, medical devices, media players, cameras, or any type of consumer electronics, such as but not limited to televisions, radios, lighting devices, tablet computers, laptop computers, or personal computers (PCs). A communication device may be a portable, handheld, computer-included, or vehicle-mounted mobile device that enables the transmission of voice and / or data via a wireless or wired connection.

[0057] Wireless communication device: One type of communication device is a wireless communication device, which may be any type of wireless device that can access (i.e., be served by) a wireless network (e.g., a cellular network). Some examples of wireless communication devices include, but are not limited to: User Equipment (UE) in a 3GPP network, Machine Type Communication (MTC) devices, and Internet of Things (IoT) devices. Such a wireless communication device may be or may be integrated into a mobile phone, a smart phone, a sensor device, a meter, a vehicle, a home appliance, a medical device, a media player, a camera, or any type of consumer electronic product, such as, but not limited to, a television, a radio, a lighting device, a tablet computer, a laptop computer, or a PC. A wireless communication device may be a portable, handheld, including a computer, or a vehicle-mounted mobile device that enables the transmission of voice and / or data via a wireless connection.

[0058] Network node: As used herein, a "network node" is any node that is part of the RAN or core network of a cellular communication network / system.

[0059] Note that the description given herein focuses on 3GPP cellular communication systems and therefore often uses 3GPP terminology or terminology similar to 3GPP terminology. However, the concepts disclosed herein are not limited to 3GPP systems.

[0060] Note that in the description of this document, reference may be made to the term "cell"; however, particularly with respect to 5G NR concepts, beams may be used instead of cells, and therefore it is important to note that the concepts described herein apply equally to both cells and beams.

[0061] Disclosed herein is a system and method for network-initiated network slicing handover of a session of a specific wireless communication device (e.g., UE) in a cellular communication system. In the following description, the cellular communication system is 5GS; however, the solution described herein can be used in other types of cellular or wireless communication systems that support network slicing.

[0062] The need for network-initiated slice switching can be illustrated by the following non-limiting use case.

[0063] Use Case 1 : Call switching between network slices.

[0064] In shopping malls, users (i.e., customers) like to move from one store to another to view and possibly purchase products in different stores. Store operators or owners in such locations want customers to make purchases. To encourage customers to do so, store operators or owners offer various on-site discounts to attract more and more customers, increasing the chances of them buying in their stores.

[0065] It is conceivable that such business operators or owners in the 5G ecosystem may like to purchase or lease network slices from the network operator in order to attract customers to their stores, serve their customers, or enhance the customer experience of customers already in their stores. The network slices may be associated with or used to provide one or more services, such as, for example, free product video streaming or on-site price reductions. Such network slices are location-defined, in that different stores may be associated with different network slices, wherein these network slices are defined to the location of the corresponding stores. In other words, customers may only be allowed to access these network slices when they are located in the corresponding stores.

[0066] Consider a customer moving from one store to another within such a shopping mall, wherein network slices purchased or leased by the store operators or owners are being allocated and unallocated as the customer leaves the boundary of one store and enters the boundary of another store. The customer can, for example, make a voice call using the services (e.g., voice services) provided by the network slice of a particular store.

[0067] It is known that services are disconnected when the network slice changes. That is, a mobile user (customer) is browsing products from one store to another and at the same time making a call using the services of the network slice that is associated to the location of a particular store. As the user moves, it is likely that the voice call is disconnected when the user moves from one network slice to another.

[0068] Now, to protect the end customer experience, such a store providing area-defined network slices to its customers may prefer a call switching mechanism that allows calls to be switched between such area-defined network slices provided by the store as the customer moves from one store to another within the shopping mall to avoid frequent call disconnections.

[0069] Use Case 2 : Beep indication when approaching a slice boundary during an ongoing voice call.

[0070] Consider a commercial location (such as an airport lounge) where users are waiting for some purpose and use services provided at the location while waiting. Consider a situation where there is a network slice: the network slice is limited to the location by business / vertical industry and / or has a time limitation (e.g., has a time limit), and a service (e.g., voice) is provided via the network slice. The user (or customer) waiting in the lounge can, for example, use the service to make a call. When the user moves around and reaches the location boundary of the network slice (e.g., the location boundary of the geographical area where the network slice is accessible), it would be desirable to provide a "beep indication" to the user during an ongoing voice call to remind the user that if the user crosses the network slice boundary, the call will be stopped.

[0071] Use Case 3 : In an ecosystem where services are provided as part of a network slice assigned to a SIM, it may be desirable to switch a call from a network slice of one SIM to a network slice of another SIM in a multi-SIM UE. Here, both SIMs are provided by the same network operator.

[0072] As an example, consider SIMs (SIM1 and SIM2) with different subscription plans, where a call is established using the network slice of SIM1 provided by an operator. In this case, when the user's subscription for SIM1 is at a low account balance, a network slice handover from the network slice of SIM1 to the network slice of SIM2 of the same network operator is desired, e.g., to avoid voice call disconnections. A handover from the network slice of SIM1 to the network slice of SIM2 of the same operator may also occur when the user's subscription for SIM1 has exhausted its approved data limit, e.g., to avoid over-the-top (OTT) call disconnections.

[0073] Now, before describing the embodiments of the present disclosure, it is beneficial to briefly describe the network slices in 5GS and in particular in 5GC (ie, 5GC network slices). Figure 1 An example of a system 100 including a 5G radio access network (RAN) 102, a 5G core network (5GC) 104, and an optional Internet Protocol (IP) multimedia subsystem (IMS) 106 is shown. The 5G RAN 102 and the 5GC 104 are collectively referred to as 5GS. As shown, the 5G RAN 102 includes a plurality of radio access nodes 108 (referred to as new radio (NR) base stations (gNBs)). The 5GC 104 includes a plurality of core network nodes or core network functions, such as, for example, an access and mobility function (AMF) 110, a user plane function (UPF) 112, a policy control function (PCF) 114, etc. The IMS 106 includes a plurality of IMS nodes, such as, for example, a serving call session control function (S-CSCF) 116, a proxy call session control function (P-CSCF) 118, an I-CSCF 120, etc.

[0074] Figure 2 The concept of 5GC network slicing is shown. Figure 2 As shown in , 5GS supports multiple services. In this example, there are four services, labeled as Service 1, Service 2, Service 3, and Service 4. Example services include, but are not limited to, enhanced mobile broadband (eMBB) services, ultra-reliable low-latency communications (URLLC) services, massive machine type communications (mMTC) services, massive Internet of Things (IoT) services, emergency services, and the like. Other examples of services are location-limited services (e.g., eMBB services provided in an airport lobby), time-limited services (e.g., eMBB services provided by a store operator for a limited time and possibly in a predefined area or location (e.g., in a store, etc.)). As shown in the figure, each service is mapped to a 5GC network slice, which is customized to meet the needs of that service. Note that more than one service can be mapped to the same 5GC network slice. Also as shown in Figure 2 As shown in , 5GC network slicing is implemented on the same physical infrastructure.

[0075] It should also be noted that in some use cases of network-initiated network slice switching described herein, one or more 5GS network slices may be location-limited and / or time-limited and / or have other restrictions defined by the network operator and / or provider of associated services (e.g., restrictions on the amount of data that can be consumed by a UE while connected to the network slice, restrictions on the number of UEs that can be connected to the network slice, restrictions on the number of PDU sessions that can be active on the network slice at any one time, etc.).

[0076] in this regard, Figure 3 An example of a cellular communication system 300 in which embodiments of network-initiated slice switching can be implemented is shown. In this example, the cellular communication system 300 is a 5GS; however, the embodiments disclosed herein are not limited thereto. As shown, the 5GS 300 includes a 5G RAN 302 (also referred to herein as an NR RAN or next generation RAN (NG-RAN)) and a 5GC 304. The 5G RAN 302 includes a base station 306 (i.e., a gNB and / or ng-eNB) that provides radio access to a UE 308. Network slicing is used in the 5GC 304 so that in this example, the 5GC 304 includes a plurality of network slices 310-1 to 310-N. Any network slice in the network slices 310-1 to 310-N is denoted herein as a network slice 310-n. Each network slice 310-n includes its own set of NFs, such as, for example, a UPF 312-n. In addition, the 5GC 304 may include NFs that are common to all network slices 310-1 to 310-N. These NFs are referred to herein as common NFs, and may include, for example, UDM 314, HSS 316, AMF 318, SMF 320, PCF 322, NEF 324, and the like.

[0077] This paper describes enabling systems such as Figure 3A system and method for network-initiated network slice switching in an example 5GS 300). On the network side, a network node determines a triggering event for a network slice switching of a session for a specific UE 308 from one network slice (denoted herein as a source network slice 310-s) to a target network slice (denoted herein as a target network slice 310-t). In turn, the network node initiates a slice switching of the session of UE 308 from the source network slice 310-s to the target network slice 310-t. As described below, in one embodiment, the network node that determines that a triggering event has occurred and initiates a slice switching in response is a UDM 314. However, the network node is not limited thereto. As another example, the network node may be a PCF.

[0078] In one embodiment, the slice switch may be due to, for example, location constraints associated with the currently used network slice (i.e., the source network slice 310-s), due to the expiration of a timer for using the currently used network slice, payment related information (e.g., moving to a lower cost network slice due to, for example, the time of day or just a general price drop), etc. In some embodiments, the detection of a triggering event for the slice switch and / or the selection of the target network slice 310-t is based on factors such as information about constraints or restrictions on at least a subset of the network slices 310-1 to 310-N purchased or leased by an entity such as, for example, an operator or owner of an associated location in the case of a location-defined network slice, a service provider of an associated service in the case of, for example, a time-defined network slice, etc. In another scenario, the network node initiating the slice switch may be configured with one or more locations and specific network slices 310-n that are only assigned when the UE 308 is in those locations. This may be due to a commercial agreement, for example, an agreement with a shopping mall and the stores in that shopping mall. An incentive may be that when a user uses a network slice 310-n associated to a specific store, the user will be notified of special discounts and other coupons that they would otherwise not be aware of.

[0079] In one embodiment, a network node (e.g., UDM 314) that determines that a triggering event has occurred and initiates a slice switch in response subscribes to one or more events from the core NFs in 5GC 304 to enable the network node to detect the triggering event for slice switching.

[0080] Upon detecting a triggering event for a slice switch, the network node identifies a target network slice 310-t for the slice switch, and in one embodiment, generates or otherwise obtains a corresponding USRP rule based on the selected target network slice 310-t for the slice switch. In one embodiment, the selected target network slice 310-t depends on the detected triggering event and information configured in the network node (e.g., UDM 314 is configured). The target network slice 310-t may be, for example, a network slice 310-n that the UE 308 already has in its subscription profile, a network slice 310-n identified based on the current location of the UE 308, or a network slice 310-n that provides temporary services and is, for example, assigned to the UE 308 until the UE 308 removes, for example, a PDU session on an expired source network slice 310-s (referred to herein as a "temporary network slice"). There may be a time limit associated with a temporary network slice, after which the PDU session on the temporary network slice is released by the network. Therefore, if a temporary network slice is selected as the target network slice 310-t for slice switching, some variations may apply here.

[0081] When the network node detects a triggering event for slice switching, the network node checks whether the UE 308 is still using the source network slice 310-s (for example, checks whether the UE SMF context still indicates that the UE 308 is using the source network slice 310-s), and the PDU session of the UE 308 must be switched from the source network slice 310-s due to, for example, timer expiration, the current slice is not allowed in the existing location, or a new slice determined by the current location. If so, the network node initiates a process for establishing a new PDU session for the UE 308 using the target network slice 310-t. Once the new PDU session using the target network slice 310-t is successfully established, the old PDU session on the source network slice 310-s is preferably deleted. This matches Session and Service Continuity (SSC) mode 3, i.e., make-before-break. Therefore, UE activities are not interrupted.

[0082] In order to establish a new PDU session using the target network slice 310-t, the network node initiates a request to the PCF 322 for this purpose. The request includes information identifying the target network slice 310-t to be used (e.g., the S-NSSAI of the target network slice 310-t) and information identifying the affected PDU session (i.e., the PDU session of the UE 308 on the source network slice 310-s). The PCF 322 then interacts with the SMF 320 to request the establishment of a new PDU session on the target network slice 310-t.

[0083] In this example, the SMF 320 supports a new procedure for performing network slice switching according to SSC Mode 3. In one embodiment, the procedure follows the same logic as described in Section 4.3.5.2 "Change of SSC mode 3 PDU Session Anchor with multiple PDUSessions" in 3GPP TS 23.502 V16.5.0.

[0084] Embodiments of the solutions described herein may provide one or more of the following advantages. Embodiments of the solutions described herein may provide session switching between network slices, and optionally, provide a beep indication to the caller when approaching the boundary of the geographic area associated to the corresponding network slice during an ongoing voice call, web surfing, or even in an idle state. In addition, the binding of network slices with time restrictions or constraints, location restrictions or constraints, and / or other related variables is an important driving factor and will bring new revenue opportunities to 5G network operators, support new use cases, etc. Business owners and operators, for example, can purchase or lease location-defined or time-defined network slices from network operators, and then provide services to potential customers visiting their stores via these network slices. These services may include services that enhance the customer communication service (e.g., voice call) experience by incorporating call switching between area-defined network slices when the customer moves from one location to another (e.g., from the store of one business owner / operator to the store of another business owner / operator). These services may also include providing a beep or other type of indication to alert the caller when approaching the boundary of the location-defined network slice provided by the business owner / operator. In some embodiments, customers can request these services directly from the operator, providing the operator with the possibility of alternative revenue stream options. In addition, call handovers between network slices and / or beep indications upon reaching the boundaries of a location-defined network slice will find huge coverage across the globe.

[0085] Figure 4A and 4B as well as Figure 5A and 5B An exemplary process for implementing an embodiment of the solution described above is shown. In particular, Figure 4A and 4B 5GS 300 according to one embodiment of the present disclosure performs the operation of a network-initiated slice switching process. Optional steps are represented by dashed lines or dashed boxes. In this embodiment, the slice switching is initiated by a network node 400 in 5GC 304.

[0086] As shown, UE 308 registers and establishes a PDU session in 5GS 400 based on the existing process in 3GPP TS 23.502 (step 404). In this example, a PDU session is established on a specific network slice, which is referred to as the source network slice 310-s for the purpose of the following slice switching process. The UPF 312-n of the source network slice 310-s is referred to as the UPF 312-s of the source network slice 310-s in this article. The PDU session established in step 404 can be an IMS PDU session or any session towards any DNN for which the UE 308 has a subscription. During or in association with the PDU session establishment process, the UE 308 is assigned an IP address, which is designated as IP1. Using the established PDU session, the UE 308 communicates with the AS 402. During the PDU session establishment process, if there is a condition associated with the use of the source network slice 310-s, the condition is recorded, for example, by the network node 400, for example, in a specific context created for this purpose, for example, in association with the UE 308. The condition will apply to the DNN currently being used by the UE 308. The condition (which is also referred to herein as a constraint or restriction for the source network slice 310-s) can be, for example, a time-related condition, a location-related condition, etc. The network node 400 can also be configured with the network slice 310-n to be used when a UE (such as UE 308) enters a specific location, in which case this information will not be in the user profile.

[0087] The network node 400 performs an action capable of detecting a triggering event for a slice switch of a PDU session for the UE 308 from a source network slice 310-s to a target network slice. For example, the triggering event may be based on a condition obtained and stored for the source network slice 310-s during PDU session establishment, or based on information configured in the network node 400 for the source network slice 310-s or a potential target network slice. In this example, the action performed by the network node 400 capable of detecting a triggering event for a slice switch includes: subscribing to event notifications for one or more related events from one or more NFs in the 5GC 304 (step 406). For example, for a location-based triggering event for a slice switch, the network node 400 subscribes to the NEF 324 and all appropriate AMFs 318 to be notified when the UE 308 leaves a location associated with the source network slice 310-s or enters a location associated with a potential target network slice. As another example, for a time-related triggering event for a slice switch, the network node 400 sets a timer to be notified.

[0088] The network node 400 detects a triggering event for a slice switch from a source network slice 310-s to another network slice 310-n (step 408). As discussed above, the triggering event can be, for example, location-based, time-based, etc. In addition, in one embodiment, the triggering event is related to the source network slice 310-s. For example, the triggering event can be the UE 308 leaving the boundary of the location to which the source network slice 310-s is defined. In another embodiment, the triggering event is related to a specific target network slice 310-t to which the switch is to be performed. For example, the triggering event can be the UE 308 entering the boundary of the location to which the specific network slice 310-n is defined, in which case the specific network slice 310-n becomes the target network slice 310-t for slice switching.

[0089] Optionally, the network node 400 determines whether the UE 308 is still using the source network slice 310-s (step 410). This can be done by checking the SMF context associated with the UE 308 accessible to the network node 400. If so, the network node 400 proceeds to initiate a slice switch.

[0090] To initiate a slice switch, the network node 400 identifies a target network slice 310-t for the slice switch (step 412) and a corresponding UE routing policy (URSP) rule (step 414), and provides these URSP rules to the UE 308 (step 416). The target network slice 310-t may be a network slice 310-n that has been identified in the subscription profile of the UE 308, a network slice 310-n that is limited to the current location of the UE 308, or a temporary network slice that is assigned to the UE 308 until the UE 308 removes the PDU session on the source network slice 310-s and / or deregisters. There may be a time limit associated with the temporary network slice, after which the PDU session is released by the network. In step 416, these URSP rules are provided to the UE 308 using, for example, existing procedures. Note that the UE 308 must maintain the old context and the new context for the source network slice 310-s and the target network slice 310-t until the slice switch is successfully completed, after which the UE 308 may delete any context specific to the source network slice 310-s, although this may not be strictly required.

[0091] The network node 400 then performs an action to initiate or cause a handover from the source network slice 310-s to the identified target network slice 310-t. As shown, the network node 400 sends a request to the PCF 322 to reestablish the PDU session of the UE 308 in the target network slice 310-t (step 418). More specifically, in this embodiment, the network node 400 triggers the service Npcf_PolicyAuthorizationUpdate to request the PCF 322 to update the policy for the PDU session of the UE 308 to move the PDU session to the target network slice 310-t, which can be identified, for example, by its S-NSSAI.

[0092] The PCF 322 sends a request to the SMF 320 via Npcf-SMPolicyControlUpdateNotify to replace the existing PDU session with a new PDU session that uses the target network slice 310-t (i.e., uses the S-NSSAI of the target network slice 310-t) (step 420). In turn, the SMF 320 initiates a process to establish a new PDU session and release the old PDU session (step 422). In one embodiment, the process is similar to the process described in 3GPP TS 23.502 Section 4.3.5.2 "Change of PDU Session Anchor for SSC Mode 3 with Multiple PDU Sessions", with the following extensions. The SMF 320 indicates to the UE 308 that a slice change is required and notifies the UE 308 of the reason for the slice change (steps 422 and 424). More specifically, in step 422, the SMF 320 sends a request for a slice change to the target network slice 310-t and a notification of the reason for the change to the AMF 318 via a Namf_Communication_N1N2MessageTransfer. In step 424, the AMF 318 forwards the request for the slice change and the notification of the reason for the slice change to the UE 308 via a PDU Session Modification Command. Thus, the AMF 318 is aware of the slice change. The PDU Session Modification Request notifies the UE 308 of the target network slice 310-t (e.g., including the S-NSSAI of the target network slice 310-t), and optionally indicates a lifetime for a new PDU session in the target network slice 310-t, which may optionally be presented to a user of the UE 308. If a lifetime is indicated, the target network slice 310-t may be referred to herein as a temporary network slice. The lifetime is the amount of time that the new PDU session can be maintained on the target network slice 310-t before it is terminated or switched to another network slice.

[0093] In one embodiment, the UE 308 provides a notification about the slice change to the user of the UE 308 (step 426). For example, in one particular embodiment, the UE 308 displays a message with an optional beep to the user to notify the user of the slice change, the reason for the change, and optionally the lifetime of the new PDU session on the target network slice 310-t (if provided).

[0094] UE 308 initiates the process of establishing a new PDU session on the target network slice 310-t (step 428).

[0095] Note that the above process for establishing a new PDU session on the target network slice 310-t may or may not result in a change of the SMF 320. Whether a new SMF or the same SMF 320 is used, a new IP address is assigned to the UE 308 and used for the new PDU session.

[0096] Note that for IMS PDU sessions, additional considerations are required. In one embodiment, the IMS application indicates to the user of UE 308 that the session will be maintained so that the remote terminal can be updated with a new IP address for UE 308 (e.g., using a SIP process for this purpose). Once the update is complete, the session is resumed using the new IP address. In one embodiment, UE 308 then releases the old session. This ensures minimal and graceful session interruption. Another option that does not involve session interruption at all is that the session is not maintained, but the voice bits from the old session (old IP address) are processed until when the remote UE is fully updated and starts using the new session. There should be no voice interruption in this case, but the UE must be able to support this feature. In one embodiment, the IMS application initiates the release of the old session after a complete and successful transmission of the IMS PDN.

[0097] Once the slice switch is completed, the network node 400 can perform actions to detect other slice switch triggering events.

[0098] Figure 5A and 5B FIG. 5 shows the operation of the 5GS 300 performing a network-initiated slice switching process according to an embodiment of the present disclosure. Optional steps are represented by dashed lines or dashed boxes. Figure 4A and 4B The embodiment is similar to that of , but the network node 400 initiating the slice switching is the UDM 314.

[0099] As shown, UE 308 registers and establishes a PDU session in 5GS 400 based on the existing process in 3GPP TS 23.502 (step 500). In this example, a PDU session is established on a specific network slice, which is referred to as the source network slice 310-s for the purpose of the following slice switching process. The UPF 312-n of the source network slice 310-s is referred to as the UPF 312-s of the source network slice 310-s in this article. The PDU session established in step 500 can be an IMS PDU session or any session towards any DNN for which the UE 308 has a subscription. During or in association with the PDU session establishment process, the UE 308 is assigned an IP address, which is designated as IP1. Using the established PDU session, the UE 308 communicates with the AS 402. During the PDU session establishment process, if there are conditions associated with the use of the source network slice 310-s, the condition is recorded, for example, by the UDM 314, for example, in a specific context created for this purpose, such as in the subscription profile of the UE 308. The condition will apply to the DNN currently being used by the UE 308. The condition (which is also referred to herein as a constraint or restriction for the source network slice 310-s) can be, for example, a time-related condition, a location-related condition, etc. The UDM 314 can also be configured with the network slice 310-n to be used when a UE (such as the UE 308) enters a specific location, in which case this information will not be in the user profile.

[0100] The UDM 314 performs actions capable of detecting a triggering event for a slice switch of a PDU session for the UE 308 from a source network slice 310-s to a target network slice. For example, the triggering event may be based on a condition obtained and stored for the source network slice 310-s during PDU session establishment, or based on information configured in the UDM 314 for the source network slice 310-s or a potential target network slice. In this example, the actions performed by the UDM 314 capable of detecting a triggering event for a slice switch include: subscribing to event notifications for one or more related events from one or more NFs in the 5GC 304 (step 502). For example, for a location-based triggering event for a slice switch, the UDM 314 subscribes to the NEF 324 and all appropriate AMFs 318 to be notified when the UE 308 leaves a location associated with the source network slice 310-s or enters a location associated with a potential target network slice. As another example, for a time-related triggering event for a slice switch, the UDM 314 sets a timer to be notified.

[0101] The UDM 314 detects a triggering event for a slice switch from a source network slice 310-s to another network slice 310-n (step 504). As discussed above, the triggering event can be, for example, location-based, time-based, etc. In addition, in one embodiment, the triggering event is related to the source network slice 310-s. For example, the triggering event can be the UE 308 leaving the boundary of the location to which the source network slice 310-s is defined. In another embodiment, the triggering event is related to a specific target network slice 310-t to which the switch is to be performed. For example, the triggering event can be the UE 308 entering the boundary of the location to which a specific network slice 310-n is defined, in which case the specific network slice 310-n becomes the target network slice 310-t for slice switching.

[0102] Optionally, UDM 314 determines whether UE 308 is still using source network slice 310-s (step 506). This can be done by checking the SMF context associated with UE 308 accessible to UDM 314. If so, UDM 314 proceeds to initiate a slice switch.

[0103] To initiate a slice switch, the UDM 314 identifies a target network slice 310-t for the slice switch (step 508) and a corresponding UE routing policy (URSP) rule (step 510), and provides these URSP rules to the UE 308 (step 512). The target network slice 310-t may be a network slice 310-n that has been identified in the subscription profile of the UE 308, a network slice 310-n that is limited to the current location of the UE 308, or a temporary network slice that is assigned to the UE 308 until the UE 308 removes the PDU session on the source network slice 310-s and / or deregisters. There may be a time limit associated with the temporary network slice, after which the PDU session is released by the network. In step 512, these URSP rules are provided to the UE 308 using, for example, existing procedures. Note that the UE 308 must maintain the old context and the new context for the source network slice 310-s and the target network slice 310-t until the slice switch is successfully completed, after which the UE 308 may delete any context specific to the source network slice 310-s, although this may not be strictly required.

[0104] The UDM 314 then performs an action to initiate or cause a handover from the source network slice 310-s to the identified target network slice 310-t. As shown, the UDM 314 sends a request to the PCF 322 to reestablish the PDU session of the UE 308 in the target network slice 310-t (step 514). More specifically, in this embodiment, the UDM 314 triggers a service Npcf_PolicyAuthorizationUpdate to request the PCF 322 to update the policy for the PDU session of the UE 308 to move the PDU session to the target network slice 310-t, which can be identified, for example, by its S-NSSAI.

[0105] The PCF 322 sends a request to the SMF 320 via Npcf-SMPolicyControlUpdateNotify to replace the existing PDU session with a new PDU session that uses the target network slice 310-t (i.e., uses the S-NSSAI of the target network slice 310-t) (step 516). In turn, the SMF 320 initiates a process to establish a new PDU session and release the old PDU session (step 518). In one embodiment, the process is similar to the process described in 3GPP TS 23.502 Section 4.3.5.2 "Change of PDU Session Anchor for SSC Mode 3 with Multiple PDU Sessions", with the following extensions. The SMF 320 indicates to the UE 308 that a slice change is required and notifies the UE 308 of the reason for the slice change (steps 518 and 520). More specifically, in step 518, the SMF 320 sends a request for a slice change to the target network slice 310-t and a notification of the reason for the change to the AMF 318 via Namf_Communication_N1N2MessageTransfer. In step 520, the AMF 318 forwards the request for the slice change and the notification of the reason for the slice change to the UE 308 via a PDU Session Modification Command. Thus, the AMF 318 is aware of the slice change. The PDU Session Modification Request notifies the UE 308 of the target network slice 310-t (e.g., including the S-NSSAI of the target network slice 310-t), and optionally indicates a lifetime for a new PDU session in the target network slice 310-t, which may optionally be presented to a user of the UE 308. If a lifetime is indicated, the target network slice 310-t may be referred to herein as a temporary network slice. The lifetime is the amount of time that the new PDU session can be maintained on the target network slice 310-t before it is terminated or switched to another network slice.

[0106] In one embodiment, the UE 308 provides a notification about the slice change to a user of the UE 308 (step 522). For example, in one particular embodiment, the UE 308 displays a message with an optional beep to the user to notify the user of the slice change, the reason for the change, and optionally the lifetime of the new PDU session on the target network slice 310-t (if provided).

[0107] UE 308 initiates the process of establishing a new PDU session on the target network slice 310-t (step 524).

[0108] Note that the above process for establishing a new PDU session on the target network slice 310-t may or may not result in a change of the SMF 320. Whether a new SMF or the same SMF 320 is used, a new IP address is assigned to the UE 308 and used for the new PDU session.

[0109] Note that for IMS PDU sessions, additional considerations are required. In one embodiment, the IMS application indicates to the user of UE 308 that the session will be maintained so that the remote terminal can be updated with a new IP address for UE 308 (e.g., using a SIP process for this purpose). Once the update is complete, the session is resumed using the new IP address. In one embodiment, UE 308 then clears the old session. This ensures minimal and graceful session interruption. Another option that does not involve session interruption at all is that the session is not maintained, but the voice bits from the old session (old IP address) are processed until when the remote UE is fully updated and starts using the new session. There should be no voice interruption in this case, but the UE must be able to support this feature. In one embodiment, the IMS application initiates the clearing of the old session after a complete and successful transmission of the IMS PDN.

[0110] Once the slice switch is completed, the UDM 314 may perform actions to detect other slice switch triggering events.

[0111] The slice switching process described herein may be extended to slice switching between network slices associated with different user identity modules (SIMs) within the same UE 308. In other words, in one embodiment, the UE 308 has two or more SIMs belonging to the same network operator and having separate subscriptions for 5GS, wherein the slice switching is from a source network slice associated with one of the SIMs to a target network slice associated with a different one of the SIMs. In this case, the network node (e.g., the network node 400, such as, for example, the UDM 314) and the UE 308 perform coordination to ensure that the same SMF 320 is selected when the UE 308 establishes a PDU session using the SIM associated with the target network slice (i.e., the "target SIM").

[0112] For network coordination, the network node 400 (e.g., UDM 314) may provide the SMF identity (i.e., the identity of SMF 320) to AMF 318. AMF 318 selects the SMF 320 to be used. In one embodiment, network coordination (e.g., UDM coordination) is achieved by updating the UE subscription in AMF 318 with the SMF identity used in association with the DNN (if UE 308 has registered with the target SIM), or providing this information at registration time when UE 308 registers in 5GC 304.

[0113] In one embodiment, UE coordination is established in two steps. This will be combined with Figure 4A and 4B as well as Figure 5A and 5B 4 and 512 of the call flow, the URSP rules indicate that they apply to the target SIM. Therefore, the UE 308 will maintain two contexts, one in the source SIM (i.e., the SIM associated with the source network slice) and one in the target SIM.

[0114] Next, in the procedure used from 3GPP TS 23.502 Section 4.3.5.2 "Change of PDU Session Anchor for SSC Mode 3 with Multiple PDU Sessions", the UE 308 knows the target SIM and target S-NSSAI to use. This additional capability needs to include the target SIM, in addition to the capability required to handle slice handovers within the same SIM. In one embodiment, this information is transmitted in the PDU Session Modification Request 422 or 520. Now, the PDU Session Modification Request further includes the target SIM.

[0115] Figure 6is a schematic block diagram of a physical infrastructure node 600. Network slices 310-1 to 310-N are logical or virtual networks implemented on multiple physical infrastructure nodes (such as IMS physical infrastructure nodes 600) using virtualization technology. In this regard, the NFs (e.g., UPFs 312-1 to 312-N) forming the network slices 310-1 to 310-N are implemented as virtual nodes operating on multiple physical infrastructure nodes 600. Similarly, public NFs (e.g., UDM 314, HSS 316, AMF 318, SMF 320, PCF 322, and / or NEF 324) can be implemented on one or more physical infrastructure nodes 600.

[0116] In this regard, Figure 6 As shown in FIG. 1 , the physical infrastructure node 600 includes one or more processors 602 (e.g., central processing unit (CPU), application specific integrated circuit (ASIC), field programmable gate array (FPGA), etc.), memory 604, and network interface 606. In some embodiments, using virtualization, NFs (e.g., UPF 312-n, UDM 314, HSS 316, AMF 318, SMF 320, PCF 322, and / or NEF 324) are implemented as virtual nodes using physical resources (e.g., processors 602, memory 604, and network interface 606) of one or more physical infrastructure nodes 600.

[0117] In some embodiments, a computer program comprising instructions is provided, which, when executed by at least one processor, causes the at least one processor to perform the functions of a network node or NF according to any embodiment described herein. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electrical signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).

[0118] Figure 7 7 is a schematic block diagram of a physical infrastructure node 600 according to some other embodiments of the present disclosure. The physical infrastructure node 600 includes one or more modules 700, each of which is implemented in software. The module 700 provides the functionality of one or more NFs described herein (e.g., one or more functions of UPF 312-n, UDM 314, HSS 316, AMF 318, SMF 320, PCF 322, and / or NEF 324 as described herein).

[0119] Figure 8800 (e.g., a CPU, an ASIC, an FPGA, etc.), a memory 804, and one or more transceivers 806, each transceiver 806 including one or more transmitters 808 and one or more receivers 810 coupled to one or more antennas 812. The transceiver 806 includes a radio front-end circuit connected to the antenna 812, which is configured to condition the signal 802 transmitted between the antenna 812 and the processor, as will be understood by a person of ordinary skill in the art. The processor 802 is also referred to as a processing circuit in this article. The transceiver 806 is also referred to as a radio circuit in this article. In some embodiments, the functions of the above-mentioned wireless communication device 800 can be implemented in whole or in part in software, for example, stored in the memory 804 and executed by the processor 802. Note that the wireless communication device 800 may include Figure 8 Additional components not shown in the figure, such as, for example, one or more user interface components (e.g., input / output interfaces, including displays, buttons, touch screens, microphones, speakers, etc. and / or any other components for allowing information to be input into the wireless communication device 800 and / or allowing information to be output from the wireless communication device 800), power sources (e.g., batteries and associated power circuits), etc.

[0120] In some embodiments, a computer program comprising instructions is provided, which, when executed by at least one processor, causes the at least one processor to perform the functions of the wireless communication device 800 according to any embodiment described herein. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).

[0121] Fig. 9 9 is a schematic block diagram of a wireless communication device 800 according to some other embodiments of the present disclosure. The wireless communication device 800 includes one or more modules 900, each of which is implemented in software. The modules 900 provide the functions of the wireless communication device 800 described herein.

[0122] Any suitable steps, methods, features, functions or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include multiple of these functional units. These functional units may be implemented via processing circuits and other digital hardware, wherein the processing circuits may include one or more microprocessors or microcontrollers, and other digital hardware may include digital signal processors (DSPs), dedicated digital logic, etc. The processing circuit may be configured to execute program codes stored in a memory, and the memory may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), buffer memory, flash memory device, optical memory, etc. The program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols, and instructions for executing one or more technologies described herein. In some implementations, according to one or more embodiments of the present disclosure, the processing circuit may be used to cause the corresponding functional unit to perform the corresponding function.

[0123] Although the processes in the figures may illustrate a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform operations in a different order, combine certain operations, overlap certain operations, etc.).

[0124] At least some of the following abbreviations may be used in the present disclosure. If there is an inconsistency between these abbreviations, then the above usage of the abbreviation should take precedence. If listed multiple times below, then the first listing should take precedence over any subsequent listings.

[0125] 3GPP Third Generation Partnership Project

[0126] 5G fifth generation

[0127] 5GC Fifth Generation Core

[0128] 5GS Fifth Generation System

[0129] AF application function

[0130] AMF access and mobility functions

[0131] AN Access Network

[0132] AP Access Point

[0133] ●ASIC Application-Specific Integrated Circuit

[0134] AUSF authentication server function

[0135] ●CPU Central Processing Unit

[0136] ●DN Data Network

[0137] ●DSP Digital Signal Processor

[0138] ●eNB Enhanced or evolved Node B

[0139] ●EPS Evolved Packet System

[0140] ●E-UTRA Evolved Universal Terrestrial Radio Access

[0141] ●FPGA Field Programmable Gate Array

[0142] gNB New Radio Base Station

[0143] gNB-DU New Radio Base Station Distributed Unit

[0144] ●HSS Home Subscriber Server

[0145] IoT

[0146] ●IP Internet Protocol

[0147] LTE Long Term Evolution

[0148] MME Mobility Management Entity

[0149] MTC Machine Type Communication

[0150] NEF network open function

[0151] NF Network Function

[0152] NR New Radio

[0153] NRF Network Function Repository function

[0154] NSSF network slice selection function

[0155] OTT Over the Top

[0156] PC Personal Computer

[0157] PCF policy control function

[0158] P-GW Packet Data Network Gateway

[0159] QoS Quality of Service

[0160] RAM Random Access Memory

[0161] RAN Radio Access Network

[0162] ●ROM Read Only Memory

[0163] ●RRH Remote Radio Head

[0164] ●RTT Round Trip Time

[0165] ●SCEF service capability exposure function

[0166] ●SMF session management function

[0167] ●TCI Transmission Configuration Indicator

[0168] ●TRP Send / Receive Point

[0169] ●UDM unified data management

[0170] UE User Equipment

[0171] ●UPF User plane function

[0172] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered to fall within the scope of the concepts disclosed herein.

Claims

1. A method for network slice switching in a cellular communication system (300), the method comprising: At a network node (400; 314) in a core network (304) of the cellular communication system (300): o Detecting (408; 504) a triggering event for a network slice switch for a session of a particular wireless communication device (308); and o In response to detecting (408; 504) the triggering event for the network slice switching: ■ identifying (412; 508) a target network slice (310-t) for said network slice handover for said session of said particular wireless communication device (308); as well as ■ sending (418; 514) a message to a policy and control function PCF (322) in the core network (304) initiating a network slice handover of the session of the specific wireless communication device (308) from a source network slice (310-s) to the target network slice (310-t); as well as At the PCF (322): o receiving (418; 514) from the network node (400; 314) the message initiating the network slice handover of the session of the specific wireless communication device (308) from the source network slice (310-s) to the target network slice (310-t); as well as ○ Executing an action resulting in the network slice switching of the session of the specific wireless communication device (308) from the source network slice (310-s) to the target network slice (310-t), wherein executing the action resulting in the network slice switching includes: sending (420; 516) a request to a session management function SMF (320) in the core network (304) to replace the session of the specific wireless communication device (308) using the source network slice (310-s) with a new session using the target network slice (310-t).

2. The method according to claim 1, wherein: The message initiating the network slice switch includes information identifying the target network slice (310-t).

3. The method according to claim 2, wherein: The information identifying the target network slice (310-t) is the subscription network slice selection auxiliary information S-NSSAI of the target network slice (310-t).

4. The method according to any one of claims 1 to 3, further comprising: At the SMF (320): receiving (420; 516) said request to replace said session of said particular wireless communication device (308) using said source network slice (310-s) with said new session using said target network slice (310-t); and An instruction is sent (422-424; 518-520) to the specific wireless communication device (308) via the access and mobility function AMF (318) in the core network (304) to replace the session using the source network slice (310-s) with the new session using the target network slice (310-t).

5. The method according to claim 4, further comprising: At the wireless communication device (308): Receive (422-424; 518-520) replacing the instruction for the session using the source network slice (310-s) with the new session using the target network slice (310-t); as well as In response to the instruction, a process of establishing the new session using the target network slice (310-t) is initiated (428; 524).

6. The method according to any one of claims 1 to 3, wherein: The triggering event for the network slice switching is based on: (a) the location of the particular wireless communication device (308), (b) a location or area associated with the source network slice (310-s), (c) a location or area associated with the target network slice (310-t), (d) payment-related information, or (e) a combination of any combination of (a) and two or more of (b) to (d).

7. The method according to any one of claims 1 to 3, wherein: The trigger event for the network slice switching is a time-based trigger event.

8. The method according to any one of claims 1 to 3, wherein: The source network slice (310-s) is associated with a first user identification module SIM of the wireless communication device (308), the target network slice (310-t) is associated with a second SIM of the wireless communication device (308), and the first SIM and the second SIM are associated with the same network operator.

9. The method according to any one of claims 1 to 3, wherein: The network node (400; 314) is a unified data management function UDM (314).

10. A cellular communication system (300), comprising: A network node (400; 314) in a core network (304) of the cellular communication system (300), the network node (400; 314) comprising one or more processors, the one or more processors being configured to: o Detecting (408; 504) a triggering event for a network slice switch for a session of a particular wireless communication device (308); and o In response to detecting (408; 504) the triggering event for the network slice switching: ■ identifying (412; 508) a target network slice (310-t) for said network slice handover for said session of said particular wireless communication device (308); as well as ■ sending (418; 514) a message to a policy and control function PCF (322) in the core network (304) initiating a network slice handover of the session of the specific wireless communication device (308) from a source network slice (310-s) to the target network slice (310-t); as well as The PCF (322), the PCF (322) comprising one or more processors, the one or more processors being configured to: o receiving (418; 514) from the network node (400; 314) the message initiating the network slice handover of the session of the specific wireless communication device (308) from the source network slice (310-s) to the target network slice (310-t); as well as ○ Executing an action resulting in the network slice switching of the session of the specific wireless communication device (308) from the source network slice (310-s) to the target network slice (310-t), wherein executing the action resulting in the network slice switching includes: sending (420; 516) a request to a session management function SMF (320) in the core network (304) to replace the session of the specific wireless communication device (308) using the source network slice (310-s) with a new session using the target network slice (310-t).

11. The cellular communication system (300) according to claim 10, wherein: The one or more processors of the PCF (322) are further configured to perform the method according to claim 2 or 3.

12. A method of operation of a network node (400; 314) in a core network (304) of a cellular communication system (300) for network slice switching, the method comprising: ●Detection (408; 504) A triggering event for a network slice switch for a session of a specific wireless communication device (308); In response to detecting (408; 504) the triggering event for the network slice switching: o Identifying (412; 508) a target network slice (310-t) for the network slice handover of the session for the particular wireless communication device (308); as well as ○ Execute the action of initiating the network slice switching of the session of the specific wireless communication device (308) from the source network slice (310-s) to the target network slice (310-t), wherein executing the action includes: sending (418; 514) a message to the policy and control function PCF (322) in the core network (304) to initiate the network slice switching of the session of the specific wireless communication device (308) from the source network slice (310-s) to the target network slice (310-t).

13. The method according to claim 12, wherein: The message initiating the network slice switch includes information identifying the target network slice (310-t).

14. The method according to claim 13, wherein: The information identifying the target network slice (310-t) is the subscription network slice selection auxiliary information S-NSSAI of the target network slice (310-t).

15. The method according to any one of claims 12 to 14, wherein: The source network slice (310-s) is associated with a first user identification module SIM of the wireless communication device (308), the target network slice (310-t) is associated with a second SIM of the wireless communication device (308), and the first SIM and the second SIM are associated with the same network operator.

16. The method according to any one of claims 12 to 14, wherein: The network node (400; 314) is a unified data management function UDM (314).

17. A network node (400; 314) for a core network (304) of a cellular communication system (300) for network slice switching, the network node (400; 314) comprising one or more processors, the one or more processors being configured to: ● detecting (408; 504) a triggering event for a network slice switch for a session of a particular wireless communication device (308); In response to detecting (408; 504) the triggering event for the network slice switching: o Identifying (412; 508) a target network slice (310-t) for the network slice handover of the session for the particular wireless communication device (308); as well as ○ Executing an action of initiating the network slice handover of the session of the specific wireless communication device (308) from the source network slice (310-s) to the target network slice (310-t), wherein: Executing the action includes: sending (418; 514) initiates a message for switching the network slice of the session of the specific wireless communication device (308) from the source network slice (310-s) to the target network slice (310-t).

18. The network node (400; 314) according to claim 17, wherein: The one or more processors are further configured to perform the method according to claim 13 or 14.

19. A method for operation of a policy and control function (PCF) (322) of a core network (304) of a cellular communication system (300) for network slice switching, the method comprising: Receive (418; 514) a message for initiating a network slice handover of a session of a specific wireless communication device (308) from a source network slice (310-s) to a target network slice (310-t); as well as An action is performed to cause the network slice switch of the session of the specific wireless communication device (308) from the source network slice (310-s) to the target network slice (310-t), wherein the action to cause the network slice switch includes: sending (420; 516) a request to a session management function SMF (320) in the core network (304) to replace the session of the specific wireless communication device (308) using the source network slice (310-s) with a new session using the target network slice (310-t).

20. The method according to claim 19, wherein: The message initiating the network slice switch includes information identifying the target network slice (310-t).

21. The method according to claim 20, wherein: The information identifying the target network slice (310-t) is the subscription network slice selection auxiliary information S-NSSAI of the target network slice (310-t).

22. The method according to any one of claims 19 to 21, wherein: The request includes information identifying the target network slice (310-t).

23. The method according to claim 22, wherein: The information identifying the target network slice (310-t) is the S-NSSAI of the target network slice (310-t).

24. The method according to any one of claims 19 to 21, wherein: The source network slice (310-s) is associated with a first user identification module SIM of the wireless communication device (308), the target network slice (310-t) is associated with a second SIM of the wireless communication device (308), and the first SIM and the second SIM are associated with the same network operator.

25. The method according to any one of claims 19 to 21, wherein: The network node (400; 314) is a unified data management function UDM (314).

26. A policy and control function (PCF) (322) of a core network (304) of a cellular communication system (300) for network slice switching, the PCF (322) comprising one or more processors, the one or more processors being configured to: receiving (418; 514) a message from a network node (400; 314) initiating a network slice handover of a session of a particular wireless communication device (308) from a source network slice (310-s) to a target network slice (310-t); and performing actions that result in the network slice handover of the session of the particular wireless communication device (308) from the source network slice (310-s) to the target network slice (310-t), wherein: Executing the action resulting in the switching of the network slice includes sending (420; 516) a request to a session management function SMF (320) in the core network (304) to replace the session of the specific wireless communication device (308) using the source network slice (310-s) with a new session using the target network slice (310-t).

27. The PCF (322) of claim 26, wherein: The one or more processors are further configured to perform the method according to claim 20 or 21.

28. A method for operation of a session management function (SMF) (320) of a core network (304) of a cellular communication system (300), the method comprising: receiving (420; 516) a request from a policy and control function PCF (322) in the core network (304) to replace a session of a particular wireless communication device (308) using a source network slice (310-s) with a new session using a target network slice (310-t); as well as An instruction is sent (422-424; 518-520) to the specific wireless communication device (308) via the access and mobility function AMF (318) in the core network (304) to replace the session using the source network slice (310-s) with the new session using the target network slice (310-t).

29. A session management function (SMF) (320) for a core network (304) of a cellular communication system (300), the SMF (320) comprising one or more processors, the one or more processors being configured to: receiving (420; 516) a request from a policy and control function PCF (322) in the core network (304) to replace a session of a particular wireless communication device (308) using a source network slice (310-s) with a new session using a target network slice (310-t); and An instruction is sent (422-424; 518-520) to the specific wireless communication device (308) via the access and mobility function AMF (318) in the core network (304) to replace the session using the source network slice (310-s) with the new session using the target network slice (310-t).

30. A method of operation of a wireless communication device (308) for network slice switching in a cellular communication system (300), the method comprising: receiving (424; 520) from a network node (318) in a core network (304) of the cellular communication system (600) an instruction to replace a current session of the wireless communication device (608) using a source network slice (310-s) with a new session using a target network slice (310-t), wherein the instruction includes information indicating an amount of time that the new session is permitted to use the target network slice (310-t); In response to the instruction, a process of establishing the new session using the target network slice (310-t) is initiated (428; 524), and the new session is terminated after the amount of time or a network slice switch to another network slice is initiated.

31. The method according to claim 30, wherein: The instruction includes information identifying the target network slice (310-t).

32. The method according to claim 31, wherein: The information identifying the target network slice (310-t) is the subscription network slice selection auxiliary information S-NSSAI of the target network slice (310-t).

33. The method according to any one of claims 30 to 32, wherein: The instruction includes information indicating a reason for the instruction to replace the session using the source network slice (310-s) with the new session using the target network slice (310-t).

34. The method according to any one of claims 30 to 32, further comprising: Presenting (426; 522) a notification regarding a network slice switch from the source network slice (310-s) to the target network slice (310-t), the notification being an audio notification, a visual notification, or an audio-visual notification.

35. The method according to any one of claims 30 to 32, wherein: The source network slice (310-s) is associated to a first user identification module SIM of the wireless communication device (308), the target network slice (310-t) is associated to a second SIM of the wireless communication device (308), and the first SIM and the second SIM are associated to the same network operator, wherein the wireless communication device (308) maintains a first context for the first SIM and a second context for the second SIM.

36. A wireless communication device (308) for network slice switching in a cellular communication system (300), the wireless communication device (300) comprising one or more processors, the one or more processors being configured to: Receiving (424; 520) from a network node (318) in a core network (304) of the cellular communication system (600) an instruction to replace a current session of the wireless communication device (608) using a source network slice (310-s) with a new session using a target network slice (310-t), wherein: The instruction includes information indicating an amount of time that the new session is permitted to use the target network slice (310-t); as well as In response to the instruction, a process of establishing the new session using the target network slice (310-t) is initiated (428; 524), and the new session is terminated after the amount of time or a network slice switch to another network slice is initiated.

37. The wireless communication device (300) of claim 36, wherein: The one or more processors are further configured to perform the method according to claim 31 or 32.

Images