Method and apparatus for operating user equipment and network equipment

Abstract

Techniques for operating a user equipment in a communication network are provided. For example, a method of operating a user equipment in a communication network is disclosed. The method comprises determining a change of the user equipment from a first coverage area providing a network slice allowed for the user equipment to a second coverage area not providing the network slice, suspending data transmission of a data session established in the first coverage area or another coverage area for the network slice, and maintaining a user equipment data session context for the data session.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communication systems and, more particularly, to operating user equipment and network equipment in a communication network. Background Art

[0002] Wireless telecommunications systems are constantly evolving. There is a constant demand for higher data rates and high quality of service. Reliability requirements are increasing, and the methods and means of ensuring reliable connections and data services while keeping transmission delays to a minimum are constantly evolving.

[0003] Evolving networks enable new services for customers. One service is network slicing, which can provide connectivity, quality of service, and data processing solutions tailored to specific customer requirements. Network slices are logical end-to-end virtual networks that can be created dynamically and provide specific capabilities and features. Multiple network slices can be created on top of a common shared physical network infrastructure to run services that may have different requirements for latency, reliability, throughput, and mobility.

[0004] For example, in 5G, network slicing will be a key feature to support different services using the same underlying mobile network infrastructure. Summary of the invention

[0005] According to a first aspect of the present disclosure, a method for operating a user equipment in a communication network is provided. The method according to the first aspect can be performed by the user equipment. The method comprises: determining a change of the user equipment from a first coverage area providing a network slice allowed for the user equipment to a second coverage area not providing the network slice; suspending data transmission of a data session established in the first coverage area or another coverage area for the network slice; and maintaining a user equipment data session context for the data session.

[0006] Pausing data transmission may also be referred to as suspending data transmission.

[0007] Pausing and terminating data transmission is specifically intended to indicate that information, parameters, processes, etc. related to data transmission (which are necessary, for example, to provide data to be sent and / or to achieve actual transmission of data) are maintained in such a way that no actual data transmission is performed during the pause of data transmission, but data transmission can be resumed, restarted, continued, etc. after the pause of data transmission.

[0008] Some exemplary, non-limiting explanations are given below. For example, pausing an ongoing data transmission may result in a scenario where the data to be sent is retained at the sender. In another example, assume the following situation: data is not actually being sent at the moment, but such data is being generated or will be generated at the sender. Then, pausing the data transmission may result in a scenario where the data to be sent is generated but not sent and is retained at the sender, or a scenario where the generation of the data to be sent is delayed during the pause.

[0009] In some embodiments of the first aspect, the method may be used to allow operation of the user equipment in at least one registration area.

[0010] In some embodiments of the first aspect, the method can be used for at least one non-homogeneous network slicing scenario and / or at least one homogeneous network slicing scenario.

[0011] In some embodiments of the first aspect, the suspending may include releasing a user equipment data radio bearer associated with the data session or deactivating the user equipment data radio bearer.

[0012] In some embodiments of the first aspect, the determination may include: receiving a message from the communication network that the network slice is not provided.

[0013] In some embodiments of the first aspect, the determining may include receiving a message from the communications network instructing the user equipment to suspend the data session.

[0014] In some embodiments of the first aspect, the message from the communications network may be an RRC reconfiguration message.

[0015] In some embodiments of the first aspect, the determination may include: detecting, by the user equipment, that the network slice is not provided.

[0016] In some embodiments of the method according to the first aspect, the maintaining comprises: maintaining, by the user equipment, the data session at a non-access layer, and suspending the data session at an access layer.

[0017] In some embodiments of the first aspect, the method may include: the first coverage area is a first tracking area, and / or the second coverage area is a second tracking area.

[0018] In some embodiments of the first aspect, the data session is a PDU session.

[0019] In some embodiments of the first aspect, the user equipment is in a connected mode in at least one of the first coverage area and the second coverage area.

[0020] According to a second aspect of the present disclosure, a method for operating a network device in a communication network is provided. The communication network includes a first coverage area that provides a network slice that is allowed to be used for a user device and a second coverage area that does not provide the network slice. The method according to the second aspect can be performed by one or more network nodes. The method includes: sending a message to the user equipment indicating a change from a first coverage area that provides a network slice that is allowed to be used for the user device to a second coverage area that does not provide the network slice, the message including information indicating to the user equipment to suspend a data session established for the network slice; receiving a message from the user equipment indicating a change from the first coverage area to the second coverage area.

[0021] In some embodiments of the second aspect, the method may be used to allow operation of the user equipment in at least one registration area.

[0022] In some embodiments of the second aspect, the method can be used for at least one of a non-homogeneous network slicing scenario and a homogeneous network slicing scenario.

[0023] In some embodiments of the second aspect, the first coverage area may be a first tracking area, and / or the second coverage area may be a second tracking area.

[0024] In some embodiments of the second aspect, the data session may be a PDU session.

[0025] In some embodiments of the method according to the second aspect, the method may further comprise: preferably, if the user equipment is in the second coverage area, maintaining a network device data session context for the data session.

[0026] In some embodiments of the method according to the second aspect, the method may further include: after receiving the message indicating a change from the first coverage area to the second coverage area, deactivating the network data radio bearer associated with the network slice data session.

[0027] In some embodiments of the second aspect, deactivating the network data radio bearer comprises: when the user equipment is in the second coverage area, deactivating a tunnel associated with the data session and / or maintaining a data session context for the network slice.

[0028] In some embodiments of the method according to the second aspect, the method may further include: buffering and / or discarding downlink data of the network slice after receiving the message indicating a change from the first coverage area to the second coverage area.

[0029] In some embodiments of the method according to the second aspect, the method may further comprise: indicating the amount of discarded data to the communications network.

[0030] According to a third aspect of the present disclosure, a method for operating a user equipment in a communication network is provided. The method according to the third aspect may be performed by the user equipment. The method comprises: determining a change of the user equipment from a second coverage area that does not provide a network slice allowed for the user equipment to a first coverage area that provides the network slice; reactivating data transmission of a data session from a user equipment data session context maintained at the user equipment, wherein the data session has previously been established for the network slice in the first coverage area or in another coverage area that provides the network slice allowed for the user equipment.

[0031] In some embodiments of the third aspect, the method may be used to allow operation of the user equipment in at least one registration area.

[0032] In some embodiments of the third aspect, the method can be used for at least one of a non-homogeneous network slicing scenario and a homogeneous network slicing scenario.

[0033] In some embodiments of the third aspect, the determination may include: receiving a message from the communication network that the network slice is provided.

[0034] In some embodiments of the third aspect, the determining may include receiving a message from the communications network instructing the user equipment to reactivate the data session.

[0035] In some embodiments of the third aspect, wherein the message from the communication network includes information instructing the user equipment to establish a user equipment data radio bearer for the reactivated data session, wherein the method further comprises: establishing a user equipment data radio bearer for the reactivated data session.

[0036] In some embodiments of the third aspect, the message from the communications network may be an RRC reconfiguration message.

[0037] In some embodiments of the third aspect, the determining may include: detecting, by the user equipment, that the network slice is provided.

[0038] In some embodiments of the method according to the third aspect, the reactivation comprises: establishing or activating a user equipment data radio bearer for the reactivated data session.

[0039] In some embodiments of the third aspect, the method may include: the first coverage area is a first tracking area, and / or the second coverage area is a second tracking area.

[0040] In some embodiments of the third aspect, the data session is a PDU session.

[0041] In some embodiments of the third aspect, the method may further include sending a message to the network indicating a change from the second coverage area to the first coverage area.

[0042] According to a fourth aspect of the present disclosure, a method for operating a network device in a communication network is provided. The communication network includes a first coverage area that provides a network slice allowed for a user device and a second coverage area that does not provide the network slice. The method according to the fourth aspect can be performed by one or more network nodes. The method includes: sending a message to the user equipment indicating a change from a second coverage area that does not provide a network slice allowed for the user device to a first coverage area that provides the network slice, the message including information instructing the user equipment to reactivate a data session with the network slice from a user equipment data session context maintained at the user equipment, wherein the data session has previously been established for the network slice in the first coverage area or in another coverage area that provides the network slice allowed for the user device; receiving a message from the user equipment indicating a change from the second coverage area to the first coverage area.

[0043] In some embodiments of the fourth aspect, the method may be used to allow operation of the user equipment in at least one registration area.

[0044] In some embodiments of the fourth aspect, the method can be used for at least one of a non-homogeneous network slicing scenario and a homogeneous network slicing scenario.

[0045] In some embodiments of the fourth aspect, the first coverage area may be a first tracking area, and / or the second coverage area may be a second tracking area.

[0046] In some embodiments of the fourth aspect, the data session may be a PDU session.

[0047] In some embodiments of the method according to the fourth aspect, the method may also include: reactivating a network slice data session maintained at the communication network, wherein the network slice data session has been previously established for the user equipment in the first coverage area or in another coverage area providing the network slice.

[0048] In some embodiments of the method according to the fourth aspect, the method may also include: establishing a network data radio bearer associated with the network slice data session.

[0049] In some embodiments of the method according to the fourth aspect, the method may also include: sending buffered downlink data of the network slice, wherein the buffered downlink data is previously buffered downlink data of the network slice for the network slice data session, and the network slice data session has been previously established for the user equipment of the network slice in the first coverage area or in another coverage area that provides the network slice allowed for the user equipment.

[0050] According to a fifth aspect of the present disclosure, a user equipment is provided. The user equipment may include at least one processor; and at least one memory including computer program code. When the computer program code is executed using the at least one processor, the user equipment at least: determines the change of the user equipment from a first coverage area providing a network slice allowed for the user equipment to a second coverage area not providing the network slice; suspends data transmission of a data session established in the first coverage area or another coverage area for the network slice; and maintains a user equipment data session context for the data session.

[0051] In some embodiments of the fifth aspect, the user equipment may be used in at least one registration area.

[0052] In some embodiments of the fifth aspect, the user equipment can be used in at least one of a non-homogeneous network slicing scenario and a homogeneous network slicing scenario.

[0053] In some embodiments of the fifth aspect, the computer program code, when executed using the at least one processor, may cause the user equipment to perform at least one method described above for the user equipment to change from the first coverage area supporting the network slice to the second coverage area not supporting the network slice.

[0054] According to a sixth aspect of the present disclosure, a user equipment is provided. The user equipment may include at least one processor; and at least one memory including computer program code. When the computer program code is executed using the at least one processor, the user equipment at least: determines the change of the user equipment from a second coverage area that does not provide a network slice allowed for the user equipment to a first coverage area that provides the network slice; reactivates the data transmission of a data session from a user equipment data session context maintained at the user equipment, wherein the data session has previously been established for the network slice in the first coverage area or in another coverage area that provides the network slice allowed for the user equipment.

[0055] In some embodiments of the sixth aspect, the user equipment may be used in at least one registration area.

[0056] In some embodiments of the sixth aspect, the user equipment can be used in at least one of a non-homogeneous network slicing scenario and a homogeneous network slicing scenario.

[0057] In some embodiments of the sixth aspect, the computer program code, when executed using the at least one processor, may cause the user equipment to perform at least one method described above for the user equipment to change from a coverage area that does not provide a network slice allowed for the user equipment to a coverage area that provides the network slice.

[0058] According to a seventh aspect of the present disclosure, a network device in a network is provided. The network device includes at least one processor; and at least one memory, which includes computer program code. When the computer program code is executed using the at least one processor, the network device at least: sends a message to the user equipment indicating a change from a first coverage area that provides a network slice allowed for the user equipment to a second coverage area that does not provide the network slice, the message including information indicating to the user equipment to suspend a data session established for the network slice; receives a message from the user equipment indicating a change from the first coverage area to the second coverage area.

[0059] In some embodiments of the seventh aspect, the network device can be used in at least one registration area.

[0060] In some embodiments of the seventh aspect, the network device can be used in at least one of a non-homogeneous network slicing scenario and a homogeneous network slicing scenario.

[0061] In some embodiments of the seventh aspect, the computer program code, when executed using the at least one processor, may cause the user equipment to perform at least one method described above for the network device to notify the user equipment of suspending the data session with the network slice.

[0062] According to an eighth aspect of the present disclosure, a network device in a network is provided. The network device includes at least one processor; and at least one memory, which includes computer program code. When the computer program code is executed using the at least one processor, the network device at least: sends a message to the user equipment indicating a change from a second coverage area that does not support a network slice allowed for the user equipment to a first coverage area that supports the network slice, the message including information indicating to the user equipment to reactivate a data session with the network slice from a user equipment data session context maintained at the user equipment, wherein the data session has previously been established for the network slice in the first coverage area or in another coverage area that provides the network slice allowed for the user equipment; receives a message from the user equipment indicating a change from the second coverage area to the first coverage area.

[0063] In some embodiments of the eighth aspect, the network device can be used for at least one registration area.

[0064] In some embodiments of the eighth aspect, the network device can be used in at least one of a non-homogeneous network slicing scenario and a homogeneous network slicing scenario.

[0065] In some embodiments of the eighth aspect, the computer program code, when executed using the at least one processor, may cause the user equipment to perform at least one method described above for the network device to notify the user equipment of reactivating the data session with the network slice.

[0066] According to a ninth aspect of the present disclosure, a user equipment is provided. The user equipment comprises: a component for determining a change of the user equipment from a first coverage area providing a network slice allowed for the user equipment to a second coverage area not providing the network slice; a component for suspending data transmission of a data session established in the first coverage area or another coverage area for the network slice; and a component for maintaining a user equipment data session context for the data session.

[0067] In some embodiments of the ninth aspect, the user equipment may be used in at least one registration area.

[0068] In some embodiments of the ninth aspect, the user equipment can be used in at least one of a non-homogeneous network slicing scenario and a homogeneous network slicing scenario.

[0069] In some embodiments of the ninth aspect, the computer program code, when executed using the at least one processor, may cause the user equipment to perform at least one method described above for the user equipment changing from the first coverage area providing the network slice to the second coverage area not providing the network slice.

[0070] According to a tenth aspect of the present disclosure, a user equipment is provided. The user equipment comprises: a component for determining a change of the user equipment from a second coverage area that does not provide a network slice allowed for the user equipment to a first coverage area that provides the network slice; a component for reactivating data transmission of a data session from a user equipment data session context maintained at the user equipment, wherein the data session has previously been established for the network slice in the first coverage area or in another coverage area that provides the network slice allowed for the user equipment.

[0071] In some embodiments of the tenth aspect, the user equipment may be used in at least one registration area.

[0072] In some embodiments of the tenth aspect, the user equipment can be used in at least one of a non-homogeneous network slicing scenario and a homogeneous network slicing scenario.

[0073] In some embodiments of the tenth aspect, the computer program code, when executed using the at least one processor, may cause the user equipment to perform at least one method described above for the user equipment to change from the second coverage area that does not provide a network slice allowed for the user equipment to the first coverage area that provides the network slice.

[0074] According to an eleventh aspect of the present disclosure, a network device in a network is provided. The network device includes: a component for sending a message to the user equipment indicating a change from a first coverage area providing a network slice allowed for the user equipment to a second coverage area not providing the network slice, the message including information indicating to the user equipment to suspend a data session established for the network slice; and a component for receiving a message from the user equipment indicating a change from the first coverage area to the second coverage area.

[0075] In some embodiments of the eleventh aspect, the network device can be used in at least one registration area.

[0076] In some embodiments of the eleventh aspect, the network device can be used in at least one of a non-homogeneous network slicing scenario and a homogeneous network slicing scenario.

[0077] In some embodiments of the eleventh aspect, the computer program code, when executed using the at least one processor, may cause the user equipment to perform at least one method described above for the network device to notify the user equipment of suspending the data session established for the network slice.

[0078] According to the twelfth aspect of the present disclosure, a network device in a network is provided. The network device includes: a component for sending a message to the user equipment indicating a change from a second coverage area that does not support a network slice allowed for the user equipment to a first coverage area that supports the network slice, the message including information indicating to the user equipment to reactivate a data session with the network slice from a user equipment data session context maintained at the user equipment, wherein the data session has previously been established for the network slice in the first coverage area or in another coverage area that provides the network slice allowed for the user equipment; and a component for receiving a message from the user equipment indicating a change from the second coverage area to the first coverage area.

[0079] In some embodiments of the twelfth aspect, the network device can be used in at least one registration area.

[0080] In some embodiments of the twelfth aspect, the network device can be used in at least one of a non-homogeneous network slicing scenario and a homogeneous network slicing scenario.

[0081] In some embodiments of the twelfth aspect, the computer program code, when executed using the at least one processor, may cause the user equipment to perform at least one method described above for the network device to notify the user equipment of reactivating the data session established for the network slice.

[0082] According to a thirteenth aspect of the present disclosure, a non-transitory computer-readable medium containing computer-executable instructions is provided, and the computer-executable instructions, when executed on one or more processors, perform the steps described in any embodiment of the above method.

[0083] Depending on the desired configuration, the above aspects and features can be implemented in systems, apparatuses, methods, articles of manufacture, and / or non-transitory computer-readable media. The present disclosure can be implemented in and / or used with a variety of different types of devices, including but not limited to cellular phones, tablet computers, wearable computing devices, portable media players, and any of a variety of other computing devices.

[0084] This summary is intended to provide a brief overview of some aspects and features of the present disclosure. Therefore, it will be understood that the above-mentioned features are only examples and should not be interpreted as narrowing the scope of the present disclosure in any way. Other features, aspects and advantages of the present disclosure will become apparent through the following detailed description, drawings and claims.

[0085] List of abbreviations

[0086] In this disclosure, the following abbreviations are used and they should be understood according to the given definitions:

[0087] 3GPP Third Generation Partnership Project

[0088] 5G Fifth Generation (mobile communication network)

[0089] 5GC 5G Core

[0090] 5GS 5G System

[0091] AF Application Function

[0092] AMF Access and Mobility Function

[0093] AN Access Network

[0094] APN Access Point Name

[0095] BS Base Station

[0096] CDMA Code Division Multiple Access

[0097] CN Core Network

[0098] CP Control Plane

[0099] DNN data network name

[0100] eNB Evolved Node B

[0101] EPC Evolved Packet Core

[0102] EPS Evolved Packet System

[0103] ETSI European Telecommunications Standards Institute

[0104] E-UTRAN Evolved UMTS Terrestrial Radio Access

[0105] IE Information Elements

[0106] IMS IP Multimedia Subsystem

[0107] IP Internet Protocol

[0108] LTE Long Term Evolution

[0109] MME Mobility Management Entity

[0110] NAS Non-Access Stratum

[0111] NR New Radio

[0112] NSSAI Network Slice Selection Assistance Information

[0113] PDN Packet Data Network

[0114] PDP Packet Data Protocol

[0115] PGW PDN Gateway

[0116] PGW-C PGW control function

[0117] PLMN Public Land Mobile Network

[0118] RAN Radio Access Network

[0119] RCS Rich Communication Service

[0120] RRC Radio Resource Control (protocol)

[0121] SGW Service Gateway

[0122] SIM Subscriber Identity Module

[0123] SMF session management functions

[0124] S-NSSAI Single NSSAI

[0125] TS Technical Specifications

[0126] UE User Equipment

[0127] URLLC Ultra-Reliable Low Latency Communications

[0128] VoNR NR Voice BRIEF DESCRIPTION OF THE DRAWINGS

[0129] The present disclosure may be better understood when the following detailed description of various embodiments is considered in conjunction with the following drawings, in which:

[0130] Figure 1 A schematic diagram of an example communication system including a base station and a plurality of communication devices is shown;

[0131] Figure 2 A schematic diagram of an example mobile communication device is shown;

[0132] Figure 3A schematic diagram of an example control device is shown;

[0133] Figure 4 An example network slicing scenario is shown;

[0134] Figure 5 An example network slicing scenario is shown;

[0135] Figure 6 shows an example message sequence chart for session management;

[0136] Figure 7 An example message sequence chart is shown;

[0137] Figure 8 and 9 An example flow chart illustrating a method for session management; and

[0138] Fig.10 and 11 An example flow chart of a method for session management is shown. DETAILED DESCRIPTION

[0139] Before explaining the examples in detail, refer to Figures 1 to 3 Certain general principles of wireless communication systems and mobile communication devices are briefly explained to aid understanding of the underlying technology of the described examples.

[0140] In e.g. Figure 1 In the wireless communication system 100 shown in , wireless access is provided to mobile communication devices, user equipment, user equipment (UE) 102, 104, 105 via at least one base station (e.g., next generation NB, i.e., gNB), similar wireless transmission and / or reception nodes or network nodes. The base station can be controlled or assisted by at least one appropriate controller device so as to be able to operate the base station and manage the mobile communication devices communicating with the base station. The controller device can be located in a radio access network (e.g., wireless communication system 100) or a core network (CN) (not shown) and can be implemented as a central device, or its functions can be distributed across multiple devices. The controller device can be part of the base station and / or provided by a separate entity, such as a radio network controller (RNC). In Figure 1 In the embodiment, control means 108 and 109 are shown as controlling respective macro-level base stations 106 and 107. The control means of the base stations may be interconnected with other control entities. The control means typically have storage capacity and at least one data processor. The control means and functions may be distributed among a plurality of control units. In some systems, the control means may additionally or alternatively be arranged in a radio network controller.

[0141] exist Figure 1, base stations 106 and 107 are shown connected to a wider communications network 113 via a gateway 112. Other gateway functions may be provided to connect to another network.

[0142] As used herein, the term "base station" has the full breadth of its ordinary meaning and includes at least a wireless communication station installed in a fixed location and used to communicate as part of a wireless telephone system or radio system. The communication area (or coverage area) of a base station may be referred to as a "cell". A base station and UEs may be configured to communicate over a transmission medium using any of the various radio access technologies (RATs) (also referred to as wireless communication technologies) or telecommunication standards described below. Figure 1 As shown in , although one of the base stations can act as a "serving cell" for the UE, each UE is also able to receive signals from (and may be within the communication range of) one or more other cells (which may be provided by the base station and / or any other base station), and the one or more other cells may be referred to as "neighboring cells."

[0143] Smaller base stations 116, 118 and 120 may also be connected to the network 113, for example, by separate gateway functions and / or via a controller of a macro-level station. Base stations 116, 118 and 120 may be micro or femto-level base stations, etc. In this example, stations 116 and 118 are connected via gateway 111, while station 120 is connected via controller device 108. In some embodiments, smaller stations may not be provided. Smaller base stations 116, 118 and 120 may be part of a second network (e.g., a wireless local area network (WLAN)) and may be WLAN access points (APs). Communication devices 102, 104, 105 may access the communication system based on various access technologies (e.g., code division multiple access (CDMA) or wideband CDMA (WCDMA)). Other non-limiting examples include time division multiple access (TDMA), frequency division multiple access (FDMA) and various schemes thereof, such as interleaved frequency division multiple access (IFDMA), single carrier frequency division multiple access (SC-FDMA) and orthogonal frequency division multiple access (OFDMA), space division multiple access (SDMA), etc.

[0144] An example of a wireless communication system is an architecture standardized by the Third Generation Partnership Project (3GPP). The latest development based on 3GPP is generally referred to as the Long Term Evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio access technology. The various development stages of the 3GPP specification are referred to as releases. The latest development of LTE is generally referred to as Advanced LTE (LTE-A). LTE (LTE-A) adopts a radio mobile architecture called Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and a core network called Evolved Packet Core (EPC). The base station of such a system is referred to as an evolved or enhanced Node B (eNB), and provides E-UTRAN features toward the communication device, such as user plane packet data convergence / radio link control / medium access control / physical layer protocol (PDCP / RLC / MAC / PHY) and control plane radio resource control (RRC) protocol termination. Other examples of radio access systems include radio access systems provided by base stations of systems based on technologies such as WLAN and / or Worldwide Interoperability for Microwave Access (WiMax). The base station can provide coverage for an entire cell or similar radio service area. The core network elements include a Mobility Management Entity (MME), a Serving Gateway (S-GW), and a Packet Gateway (P-GW).

[0145] An example of a suitable communication system is the 5G or NR concept. The network architecture in NR may be similar to that of LTE-A. The base station of the NR system may be referred to as a next generation Node B (gNB). Changes to the network architecture may depend on the need to support various radio technologies and more refined quality of service (QoS) support, as well as some on-demand requirements for, for example, QoS levels, to support quality of experience (QoE) from the user's perspective. In addition, network-aware services and applications, as well as service- and application-aware networks, may bring changes to the architecture. These changes involve information-centric network (ICN) and user-centric content delivery network (UC-CDN) approaches. NR may use multiple-input multiple-output (MIMO) antennas, many more base stations or nodes than LTE (the so-called small cell concept), including macro sites that operate in collaboration with smaller stations, and may also employ various radio technologies to achieve better coverage and enhanced data rates.

[0146] Future networks may utilize network function virtualization (NFV), a network architecture concept that proposes virtualizing network node functions into "building blocks" or entities that can be operationally connected or linked together to provide services. Virtualized network functions (VNFs) may include one or more virtual machines that use standard or general-purpose servers rather than custom hardware to run computer program code. Cloud computing or data storage may also be utilized. In radio communications, this may mean that node operations will be performed at least in part in a server, host, or node that is operationally coupled to a remote radio head. It is also possible that node operations will be distributed among multiple servers, nodes, or hosts. It should also be understood that the distribution of work between core network operations and base station operations may be different from LTE, or even non-existent.

[0147] Example 5G Core Network (CN) includes functional entities. CN is connected to UE via Radio Access Network (RAN). UPF (User Plane Function) whose role is called PSA (PDU Session Anchor) can be responsible for forwarding frames back and forth between DN (Data Network) and one or more tunnels established towards UE through 5G to exchange services with Data Network (DN).

[0148] The UPF is controlled by the SMF (Session Management Function) which receives policies from the PCF (Policy Control Function). The CN may also include an AMF (Access and Mobility Function).

[0149] Reference will now be made to the schematic partial cross-sectional view of Figure 2 A possible (mobile) communication device 200 is described in more detail. Such a mobile communication device 200 is generally referred to as a user equipment (UE), a user device or a terminal device. A suitable mobile communication device 200 can be provided by any device capable of sending and receiving radio signals. Non-limiting examples include a mobile station (MS) or a mobile device, such as a mobile phone or a so-called smart phone, a computer with a wireless interface card or other wireless interface facilities (e.g., a USB adapter), a personal data assistant (PDA) or a tablet computer with wireless communication capabilities, or any combination of these items, etc. The communication device 200 can provide, for example, communication of data (e.g., voice, e-mail, text messages, multimedia, etc.) for carrying communication. Therefore, a variety of services can be provided to the user via the user's communication device. Non-limiting examples of these services include two-way or multi-way calls, data communications or multimedia services, or simply access to a data communication network system (e.g., the Internet). Broadcast or multicast data can also be provided to the user. Non-limiting examples of content include downloads, television and radio programs, videos, advertisements, various alarms and other information.

[0150] In industrial applications, the communications device may be a modem integrated into an industrial actuator (e.g., a robotic arm) and / or a modem acting as an Ethernet hub that would serve as a connection point for one or more connected Ethernet devices (the connection may be wired or non-wired).

[0151] The communication device 200 is typically provided with at least one data processing entity 201, at least one memory 202 and possibly other components 203 for software and hardware assisted execution of the tasks it is designed to perform, including controlling access to and communications with access systems and other communication devices. The data processing, storage and other related control means may be provided on appropriate circuit boards and / or in a chipset 204. The user may control the operation of the communication device 200 by means of a suitable user interface (e.g. a keypad 205, voice commands, a touch-sensitive screen or touchpad, a combination thereof, etc.). A display 208, a speaker and a microphone may also be provided. In addition, the communication device 200 may include appropriate connectors (wired or wireless) to other devices and / or for connecting external accessories (e.g. a hands-free device).

[0152] The communication device 200 may receive signals over the air or radio interface 207 via appropriate means for receiving, and may transmit signals via appropriate means for transmitting radio signals. Figure 2 In the embodiment of the present invention, the transceiver arrangement is schematically designated by block 206. The transceiver arrangement 206 may be provided, for example, by means of a radio component and an associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the communication device 200.

[0153] If desired, the communication device 200 may also or alternatively be configured to communicate using one or more global navigation satellite systems (GNSS, such as GPS or GLONASS), one or more mobile television broadcast standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocol. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0154] generally, Figure 2 The communication device 200 shown in includes a component set configured to perform core functions. For example, the component set can be implemented as a system on a chip (SoC), which can include parts for various purposes. Alternatively, the component set can be implemented as a separate component or component group for various purposes. The component set can be coupled to various other circuits of the communication device 200 (e.g., in communication; directly or indirectly).

[0155] The communication device 200 may include at least one antenna for communicating with a transmitter and a receiver (e.g., a transceiver device 206). Alternatively, the transmitting antenna and the receiving antenna may be separate. The communication device 200 may also include a processor (e.g., at least one data processing entity 201), which is configured to provide signals to the transmitter and receive signals from the receiver, respectively, and control the functions of the communication device 200. The processor may be configured to control the functions of the transmitter and the receiver by implementing control signaling via wires reaching the transmitter and the receiver. Similarly, the processor may be configured to control other units of the communication device 200 by implementing control signaling via wires connecting the processor to other units (e.g., a display (e.g., display 208) or a memory (e.g., at least one memory 202)). For example, a processor may be embodied in various ways, including circuitry, at least one processing core, one or more microprocessors with an attached digital signal processor, one or more processors without an attached digital signal processor, one or more coprocessors, one or more multi-core processors, one or more controllers, processing circuitry, one or more computers, various other processing units including integrated circuits (e.g., application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), etc.), or some combination thereof. Thus, in some examples, a processor may include multiple processors or processing cores.

[0156] The communication device 200 is capable of operating using one or more air interface standards, communication protocols, modulation types, access types, etc. The signals sent and received by the processor may include signaling information in accordance with the air interface standard of the applicable cellular system and / or any number of different wired or wireless networking technologies, including but not limited to Wi-Fi, WLAN technologies, such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, 802.16, 802.3, ADSL, DOCSIS, etc. In addition, these signals may include voice data, user-generated data, user-requested data, etc.

[0157] For example, the communication device 200 and / or the cellular modem therein can operate according to various third generation (3G) communication protocols, fourth generation (4G) communication protocols, fifth generation (5G) communication protocols, Internet Protocol Multimedia Subsystem (IMS) communication protocols (e.g., Session Initiation Protocol (SIP)), or protocols above 5G. For example, the communication device 200 can operate according to 4G wireless communication protocols (e.g., Advanced LTE, 5G, etc.) and similar wireless communication protocols that may be developed subsequently.

[0158] It will be understood that the processor may include circuits for implementing the audio / video and logic functions of the communication device 200. For example, the processor may include a digital signal processor device, a microprocessor device, an analog-to-digital converter, a digital-to-analog converter, etc. The control and signal processing functions of the communication device 200 may be allocated between these devices according to their respective capabilities. The processor may also include an internal voice encoder (VC), an internal data modem (DM), etc. In addition, the processor may include the function of operating one or more software programs, which may be stored in the memory. In general, the processor and the stored software instructions may be configured to enable the communication device 200 to perform actions. For example, the processor is capable of operating a connection program, such as a web browser. The connection program may allow the communication device 200 to send and receive network content, such as location-based content, according to a protocol (e.g., wireless application protocol (WAP), hypertext transfer protocol (HTTP), etc.).

[0159] The communication device 200 may also include a user interface, which includes, for example, a headset or speaker, a ringer, a microphone, a display, a user input interface, etc., which may be operatively coupled to the processor. As described above, the display may include a touch-sensitive display, wherein the user may select, input a value, etc., by touch and / or gestures. The processor may also include a user interface circuit, which is configured to control at least some functions of one or more units of the user interface (e.g., a speaker, a ringer, a microphone, a display, etc.). The processor and / or the user interface circuit including the processor may be configured to control one or more functions of one or more units of the user interface by computer program instructions (e.g., software and / or firmware) stored on a memory accessible to the processor (e.g., a volatile memory, a non-volatile memory, etc.). The communication device 200 may include a battery for powering various circuits associated with the mobile terminal (e.g., a circuit that provides mechanical vibration as a detectable output). The user input interface may include a device that allows the communication device 200 to receive data, such as a keypad (e.g., a keypad 206) and / or other input devices. The keypad may also be a virtual keyboard presented on the display or an externally coupled keyboard.

[0160] The communication device 200 may also include one or more mechanisms for sharing and / or obtaining data. For example, the communication device 200 may include a short-range radio frequency (RF) transceiver and / or interrogator, and thus may share data with and / or obtain data from electronic devices based on RF technology. The communication device 200 may include other short-range transceivers, such as infrared (IR) transceivers, Bluetooth transceivers, and / or other short-range transceivers. TM Wireless technology operated by Bluetooth TM (BT) transceiver, wireless universal serial bus (USB) transceiver, Bluetooth TMLow power transceiver, ZigBee transceiver, ANT transceiver, cellular device to device transceiver, wireless local area network link transceiver, and / or any other short-range radio technology. The communication device 200 (and more specifically, the short-range transceiver) can send data to and / or receive data from electronic devices near the device (e.g., within 10 meters). The communication device 200, which includes a Wi-Fi or wireless local area networking modem, can also send and / or receive data from electronic devices according to various wireless networking technologies, including 6LoWpan, Wi-Fi, Wi-Fi low power, WLAN technology, such as IEEE802.11 technology, IEEE 802.15 technology, IEEE 802.16 technology, etc.

[0161] The communication device 200 may include memory, such as one or more user identity modules (SIMs), one or more universal user identity modules (USIMs), one or more removable user identity modules (R-UIMs), one or more eUICCs, one or more UICCs, etc., which can store information elements related to mobile users. In addition, the communication device 200 may include other removable and / or fixed memories. The communication device 200 may include volatile memory and / or non-volatile memory. For example, the volatile memory may include random access memory (RAM), including dynamic and / or static RAM, on-chip or off-chip cache memory, etc. Non-volatile memory (which may be embedded and / or removable) may include, for example, read-only memory, flash memory, magnetic storage devices (such as hard disks, floppy disk drives, tapes), optical disk drives and / or media, non-volatile random access memory (NVRAM), etc. Like volatile memory, non-volatile memory may include a cache area for temporarily storing data. At least a portion of the volatile and / or non-volatile memory may be embedded in the processor. The memory may store one or more software programs, instructions, information segments, data, etc., which may be used by the apparatus to perform the operations disclosed herein.

[0162] The memory may include an identifier, such as an International Mobile Equipment Identity (IMEI) code, that can uniquely identify the communication device 200. The memory may include an identifier, such as an International Mobile Equipment Identity (IMEI) code, that can uniquely identify the communication device 200. In an example embodiment, the processor may be configured using computer code stored at the memory to cause the processor to perform the operations disclosed herein.

[0163] Some embodiments disclosed herein may be implemented in software, hardware, application logic, or a combination of software, hardware, and application logic. For example, the software, application logic, and / or hardware may reside in a memory, a processor, or an electronic component. In some example embodiments, the application logic, software, or instruction set may be maintained on any of a variety of conventional computer-readable media. In the context of this document, a "computer-readable medium" may be any non-transitory medium that is capable of containing, storing, communicating, propagating, or transmitting instructions for execution by an instruction execution system, apparatus, or device (e.g., a computer or data processor circuit, an example of which is a computer-readable medium). Figure 2 As shown in ), for use or in conjunction with the computer, the computer-readable medium may include non-transitory computer-readable storage media, which may be any medium that can contain or store instructions for use by or in conjunction with an instruction execution system, apparatus, or device (e.g., a computer).

[0164] In some embodiments, the communication device 200 (i.e., a user equipment (UE) or user device in a network) includes a processor (e.g., at least one data processing entity 201) and a memory (e.g., at least one memory 202). The memory includes computer program code that causes the communication device 200 to perform the same as described below with reference to Figure 8 and Fig. 9 Processing consistent with the described method.

[0165] Figure 3 An example embodiment of a control device for a communication system is shown, the communication system being, for example, to be coupled to and / or used to control a station of an access system, the access system being, for example, a RAN node (e.g., a base station, an eNB or a gNB, a relay node) or a core network node (e.g., an MME or an S-GW or a P-GW) or a core network function (e.g., an AMF / SMF) or a server or a host. The method may be implanted in a single control device or implanted across multiple control devices. The control device may be integrated with a node or module of a core network or a RAN or be external to a node or module of a core network or a RAN. In some embodiments, the base station comprises a separate control device unit or module. In other embodiments, the control device may be another network unit, such as a radio network controller or a spectrum controller. In some embodiments, each base station may have such a control device and a control device arranged in a radio network controller. The control device 300 may be arranged to provide control of communications in a service area of ​​the system. The control device 300 comprises at least one memory 301, at least one data processing unit 302, 303 and an input / output interface 304. Via the interface, the control device may be coupled to a receiver and a transmitter of the base station. The receiver and / or the transmitter may be implemented as a radio front end or a remote radio head.

[0166] Typically, the control device 300 has an antenna for sending and receiving radio signals. A radio frequency (RF) transceiver module coupled to the antenna receives RF signals from the antenna, converts them to baseband signals and sends them to a processor (e.g., at least one data processing unit 302, 303). The RF transceiver also converts the baseband signals received from the processor into RF signals and sends them to the antenna. The processor processes the received baseband signals and calls different functional modules to perform features in the control device 300. A memory (e.g., at least one memory 301) stores program instructions and data that control the operation of the control device 300. In Figure 3 In the example of , the control device 300 also includes a protocol stack and a set of control function modules and circuits. The PDU session processing circuit processes the PDU session establishment and modification process. The policy control module configures policy rules for the UE. The configuration and control circuits provide different parameters to configure and control relevant functions of the UE, including mobility management and session management. Suitable processors include, for example, dedicated processors, digital signal processors (DSPs), multiple microprocessors, one or more microprocessors associated with a DSP core, controllers, microcontrollers, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) circuits, and other types of integrated circuits (ICs) and / or state machines.

[0167] In some embodiments, the control device 300 (i.e., a base station, a wireless transmission and / or reception point device, or a network node in a network) includes a processor (e.g., at least one data processing unit 302, 303) and a memory (e.g., at least one memory 301). The memory includes computer program code, which enables the control device 300 to perform the same operations as described below. Fig.10 and Fig.11 Processing consistent with the described method.

[0168] As mentioned above, network slicing is a concept in which the network resources of an end-to-end connection between a user device (i.e., user equipment UE) and another endpoint in a network (e.g., a public land mobile network (PLMN)) are sliced. Similar network slicing can also be adopted in private networks. Network slicing can be understood as a logical end-to-end network that can be dynamically created and / or modified. The network between terminal devices can be completely sliced ​​from one terminal device to another, and the slices thus form a logical pipeline within the network. The user device can access the slices through the radio interface. As described in 3GPP TS38.300 (e.g., Version 16.8.0 (Release 16), January 2022), network slicing will be a key feature in 5G to support different services using the same underlying mobile network infrastructure.

[0169] Slices can serve specific service types. So far, three different network slices / service types have been standardized: eMBB (slices suitable for handling 5G enhanced mobile broadband), URLLC (slices suitable for handling ultra-reliable low latency communications), and MIoT (slices suitable for handling massive IoT). Communications service providers (CSPs) can define additional network slices / service types if required. A given user device can access multiple slices through the same access network (e.g., through the same radio interface).

[0170] Thus, network slicing enables communications service providers to provide dedicated virtual networks on a public network infrastructure. Different virtual or logical networks can be designed to provide different networking characteristics (e.g., different quality of service (QoS)) in order to host services with different requirements and service level agreements (SLAs). For example, a virtual network can be customized to meet the specific needs of various applications, services, devices, customers and / or operators. Thus, network slicing enables different services to be provided to terminal devices. In one example, network slices may differ in their service requirements (such as URLLC and eMBB) or the tenants that provide these services.

[0171] Figure 4 An illustration of a scenario in which a user equipment (i.e., UE) uses two different services provided by two different networks (e.g., IMS networks) is provided. In this scenario, the UE is connected to the IMS network through two different network slices (e.g., 5GS network slices). That is, the UE is connected to IMS network #1 through 5GS slice #1 and uses services (e.g., RCS) provided by IMS network #1. The UE is also connected to IMS network #2 through 5GS slice #2 and uses services (e.g., VoNG) provided by IMS network #2. This allows network slices to be customized for different services hosted by each IMS network. IMS networks #1 and #2 are shown by way of example and are optional.

[0172] The network slice is uniquely identified via single network slice selection assistance information (S-NSSAI). The current 3GPP specification (e.g., 3GPP TS 38.300 Version 16.8.0 (Release 16), January 2022) allows user equipment to be simultaneously connected and served by up to eight network slices corresponding to eight S-NSSAIs. On the other hand, each cell can support dozens or even hundreds of S-NSSAIs. In the current 3GPP specification (e.g., 3GPP TS 38.423 Version 16.8.0 (Release 16), January 2022), a tracking area (TA) can support up to 1024 network slices.

[0173] The format of S-NSSAI may include both a slice service type (SST) field and a slice distinguisher (SD) field with a total length of 32 bits, or only a portion of the SST field, in which case the length of the S-NSSAI is only 8 bits. Examples of the format are described in 3GPP specifications (e.g., 3GPP TS23.501 or 3GPP TS23.003). The SST field may have standardized values ​​and non-standardized values. Values ​​0 to 127 belong to the standardized SST range. For example, an SST value of 1 may indicate that the slice is suitable for processing 5GeMBB, 2 is suitable for processing URLLC, etc. SD is defined only by the operator.

[0174] Other concepts involve defining Tracking Areas (TAs) and Registration Areas (RAs). A TA is a logical concept of an area where a user can move around without updating the MME, and is the LTE, EPS or 5GS counterpart of location areas and routing areas for GSM, WCDMA and GPRS. A TA includes a set of cells. TAs can be grouped into tracking area lists (TA lists), which can be configured on the UE. For example, the network assigns a list with one or more TAs to the user. In certain operations, the UE can move freely among all TAs in the list without updating the MME. A RA is a list including tracking areas (TAs), which is configured to the UE by the network. The RA is used to track the UE for paging purposes. If the UE leaves the RA, the UE will notify the network through a NAS registration request (called mobility registration update) so that the correct RA can be configured to the UE.

[0175] In 5G, RA also has the role of maintaining the allowed slices (alternatively, allowed NSSAI) of the UE. The allowed NSSAI is configured to the UE by the network. Throughout this disclosure, allowed S-NSSAI may refer to the S-NSSAI included in the allowed NSSAI. The UE NAS may request access to the S-NSSAI, and the network will decide whether to add the S-NSSAI to the UE's list.

[0176] In recent developments, an agreement was reached to have homogeneous slice support within TA as well as RA. This means that the same slices will be supported across the TA and the allowed NSSAI will be valid across the RA of the UE.

[0177] However, a RA may include multiple TAs that do not support all allowed slices for a UE, thereby allowing more flexible registration area configurations, including support for non-homogeneous slices for the TA containing the RA.

[0178] Figure 5 An example network slicing scenario is shown.

[0179] In this example scenario, a user equipment (e.g., UE) 530 is configured with a registration area (RA) that includes two tracking areas, such as a first tracking area (TA1) 510 and a second tracking area (TA2) 520. That is, the RA is defined as RA={TA1+TA2}. Figure 5 In the example, the first tracking area (TA1) corresponds to the first cell (cell 1), and the second tracking area (TA2) corresponds to the second cell (cell 2). Cell 1 and cell 2 may belong to one or two network nodes, such as gNBs.

[0180] In a first tracking area (TA1) or a first cell (cell 1), two network slices are configured, namely, slice A and slice B. One of the two network slices provides a first service (e.g., eMBB), while the other provides a second service (e.g., URLLC). In a second tracking area (TA2) or a second cell (cell 2), only one network slice, namely, slice A, is configured, which provides a first service (e.g., eMBB).

[0181] UE 530 has slice A and slice B, which are allowed slices providing the first (eMBB) service and the second (URLLC) service.

[0182] exist Figure 5 In the example scenario shown in FIG. 5 , it is assumed that UE 530 is camped on a second cell (cell 2) in a second tracking area (TA2) and is therefore able to use the first service (eMBB).

[0183] When UE 530 is paged for a PDU session for a second service (URLLC), the network (e.g., AMF) sends a message to a first cell (cell 1) supporting the second service (URLLC), and may send messages to other cells of the first tracking area (TA1). However, UE 530 is not camped on the first cell (cell 1), and therefore UE 530 cannot receive the paging message.

[0184] exist Figure 6 In FIG. 1 , a message sequence diagram for session management is shown. The message sequence diagram shows a message sequence diagram similar to Figure 5 Messages exchanged between user equipment / network nodes of a network and operations performed by user equipment / network nodes in the example scenario shown in FIG.

[0185] Figure 6The network may include one or more network nodes (e.g., one or more base stations and one or more control functions) and at least one user equipment (UE). The network includes two cells, including a first cell (cell 1) and a second cell (cell 2). In the network, a first tracking area (TA1) including the first cell (cell 1) and a second tracking area (TA2) including the second cell (cell 2) are defined. Each cell (or tracking area) is controlled or served by a base station gNB1. The network also includes core network functions such as AMF, SMF, and UPF. In the network, network slices are configured. The network slice includes a network slice configured in the first cell (cell 1) and providing slice A and slice B. Network slice A is configured in the second cell (cell 2). Network slices can be configured in the network to provide, for example, eMBB and URLLC services. Here, the first cell (cell 1) can provide eMBB and URLLC services to UEs residing on the first cell (cell 1). On the other hand, the second cell (cell 2) can provide eMBB slices and eMBB services to UEs residing on the second cell (cell 2).

[0186] like Figure 6 The session management of the user equipment shown in the present invention proposes a method for correct mobile originated (MO) data request in connected mode in a scenario where non-homogeneous slice support exists for a TA including an RA (registration area of ​​the UE). In this scenario, slice support is lost due to movement to a cell (cell 2) that does not support allowed slices for the UE corresponding to the ongoing protocol data unit (PDU) session. Due to non-homogeneous slice support in the registration area, the loss of slice support does not affect the registration area or allowed slice list of the UE.

[0187] A PDU session provides an end-to-end user plane connection between a UE and a specific data network (DN) through a user plane function (UPF). A PDU session supports one or more quality of service (QoS) flows.

[0188] In addition to the already mentioned slices eMBB and URLLC, other slices are also included, such as MIoT or V2X or dynamic slices.

[0189] Figure 6The mobility of a UE is shown, the UE is in CM-CONNECTED with RA=TAI,TAI2, with allowed NSSAI S-NSSAI1 (slice A) and partially allowed S-NSSAI (slice B) in TAI1S-NSSAI1, where TAI1 and TAI2 are supported by cells under gNB1, and where the UE has PDU sessions activated for both S-NSSAI1 and S-NSSAI2. After moving to TAI2, the PDU sessions for S-NSSAI2 are deactivated, which means that at least the context is retained, but the DL data is dropped and not considered. The related DRBs are also reconfigured to be deactivated during HO. The trigger for deactivation at the AMF can be the receipt of a path switch indicating that S-NSSAI2 is now not supported (this can be explicitly indicated), or the ULI allows the AMF to detect this situation (option 1).

[0190] After moving to TAI2 (option 2), the DL of the PDU session for S-NSSAI2 data is discarded in the RAN. The associated DRBs are also reconfigured to be deactivated during HO. Because there is DL discarded data at the RAN, this data is taken into account, so reports on the amount of discarded data may need to be sent periodically and when the AN connection is released according to the configuration in the RAN. This report can be sent to the HPLMN SMF based on the roaming agreement. Based on the TA in which the UE is located, the activation / deactivation of the session can be a local event in the RAN. RRC inactivity can be enabled, or RRC can be deactivated. This option that requires end-to-end modification of the PDU session state can be used.

[0191] exist Figure 6 In step 0, gNB1 establishes AMF, in particular to support non-uniform slicing in the tracking area. This establishment may affect the RA configuration for the UE at the AMF. The UE has connected DRB and data or PDU sessions for two S-NSSAI slices. It is also possible to have only a single slice connection or a connection to more than two slices.

[0192] like Figure 6 As shown in step 1 of , the UE has slice A and slice B as allowed slices and indicates its capability of supporting non-uniform slicing in the tracking areas of the registration area. In addition, the UE is configured with a registration area (RA) including first and second tracking areas (TA1 and TA2).

[0193] In addition, if Figure 6 As shown in step 2 of , the UE is in connected mode in cell 1. Support for non-uniform slicing in the tracking area of ​​the registration area is registered in the UE context.

[0194] In step 3, in the network, the RAN switches the UE to a TA that does not support slice B, such as TA2 of cell 2. The admission control at the gNB releases the DRB of slice B and suspends the corresponding PDU session and / or releases any PDU session context. The PDU session related context is retained at gNB1 for possible session reactivation.

[0195] Therefore, in step 4, the gNB sends an RRC reconfiguration message towards the UE in step 4. The message includes a handover (HO) command to cell 2 and a command to suspend the PDU session or information about suspending the PDU session.

[0196] In response to receiving the RRC reconfiguration message from the gNB, the UE releases the data radio bearer (DRB) or deactivates the data radio bearer (DRB) in step 5. Even if there is no DRB associated with the PDU session, the UE does not release the PDU session and will consider the PDU session to be deactivated.

[0197] After completion, in step 6, the UE transmits an RRC Reconfiguration Complete message to the gNB.

[0198] In response to the RRC Reconfiguration Complete message, two options on the network side are discussed below.

[0199] On the network side, as option 1, the PDU session is deactivated at the Session Management Function (SMF), or as option 2, the PDU session data is buffered at the RAN node (here gNB1).

[0200] In step 7, as the first step of option 1, gNB1 notifies the AMF of the suspension of the PDU session. To this end, in step 8, gNB1 sends a PDU session suspension request to the access and mobility management function (AMF). The request includes retaining or maintaining the PDU session of slice B with the deactivated DRB.

[0201] In step 9, the AMF forwards the PDU Session Suspend Request to the SMF. These messages can be NGAP messages. Specifically, a Path Switch Request in the inter-gNB scenario or a new NGAP message in the intra-gNB scenario.

[0202] In step 10, the SMF contacts the user plane function (UPF) to notify that the PDU session is deactivated. In addition, the SMF releases or removes the tunnel to the UPF. Such a tunnel may be an N3 tunnel. In addition, when the user equipment is in the second coverage area, the data session context for the network slice may be maintained. The data session context for the network slice may include information about the DRB link and the (N3) tunnel. The (N3) tunnel may be retained while deactivating the DRB.

[0203] Then in step 11, SMF replies to AMF with a session modification response message indicating that the tunnel has been removed.

[0204] In step 12, as the first step of Option 2, the UPF sends the DL data of slice B to gNB1. In step 13, gNB1 buffers the DL data of the PDU session. The DL data may be buffered until the UE returns to the cell or TA of gNB1. Additionally or alternatively, the DL data may be buffered until a timer expires. In this option, the core network is unaware of the deactivation status of the PDU session on the UE side.

[0205] In step 14, buffered and / or discarded data at the RAN node may be reported from gNB1 to the SMF in order to properly handle charging.

[0206] Such buffered and / or discarded data are not provided to the UE. Therefore, they may be excluded from billing. To this end, for example, a message sent from gNB1 to the SMF may be used to indicate that the buffered and / or discarded data is to be excluded from billing. The network device may indicate the amount of discarded data to the communication network. The amount of discarded data may be related to a lack of service support due to non-provision of a network slice. For billing purposes, the amount of discarded data may be indicated to the core network, in particular to a charging calculation entity.

[0207] Because the UE does not release (i.e., maintain) the PDU session, when the UE moves to the next cell under coverage that supports network slicing, the UE does not need to generate more signaling according to the PDU session establishment procedure to request connection again.

[0208] exist Figure 7 In FIG. 1 , a message sequence diagram for session management is shown. The message sequence diagram shows a message sequence diagram similar to Figure 5 Messages exchanged between user equipment / network nodes of a network and operations performed by user equipment / network nodes of the network in the example scenario shown in FIG.

[0209] like Figure 7 The session management of the user equipment shown in involves obtaining slice support due to moving from a cell that does not support slicing for the UE to a cell that does support slicing for the UE.

[0210] Figure 7Mobility of a UE is shown, the UE is in CM-CONNECTED with RA=TAI,TAI2, with allowed NSSAI S-NSSAI1 and partially allowed S-NSSAI in TAI2 S-NSSAI2, where TAI1 and TAI2 are supported by cells under different gNBs, and where the UE has a PDU Session activated for S-NSSAI1 and deactivated for S-NSSAI2. After moving to TAI1, the PDU Session for S-NSSAI2 is reactivated, which means that the context is now set up in the SMF / UPF to enable data forwarding for the PDU Session for S-NSSAI2. The relevant DRBs are also reconfigured to be activated during HO. The trigger for reactivation at the AMF may be the receipt of a path switch indicating that S-NSSAI2 is now supported (this may be explicitly indicated), or the ULI allows the AMF to detect this situation (option 1). The trigger for reactivation at the AMF may be the receipt of an NG-AP message indicating that S-NSSAI2 is now supported (option 2).

[0211] Figure 7 The network may include one or more network nodes (e.g., one or more base stations and one or more control functions) (here gNB1 and gNB2) and at least one user equipment (UE). The network includes two cells, including a first cell (cell 1) and a second cell (cell 2). The first cell is controlled by gNB1, and the second cell is controlled by gNB2. In the network, a first tracking area (TA1) including the first cell (cell 1) and a second tracking area (TA2) including the second cell (cell 2) are defined. The network also includes core network functions such as AMF, SMF, and UPF. In the network, network slices are configured. The network slices include network slices configured in the first cell (cell 1) and the second cell (cell 2). Network slices can be configured in the network to provide services in TA1 or in the first cell, such as eMBB and URLLC services. On the other hand, TA2 or the second cell (cell 2) can provide eMBB slice services to UEs residing on the second cell (cell 2).

[0212] exist Figure 7 Step 1 of , indicates that the UE has eMBB and URLLC as allowed slices.

[0213] exist Figure 7 Step 2 indicates that a registration area (RA) including a first and a second tracking area (TA1 and TA2) is configured for the UE.

[0214] In addition, if Figure 7 As shown in step 3 of , the UE is in connected mode in cell 2 or TA2 of gNB2.

[0215] exist Figure 7 In step 4, gNB2 controlling cell 2 and TA2 sends a HO request message to gNB1 controlling cell 1 and TA1. The message also includes information about the deactivation or suspension of PDU sessions of the UE. The deactivated PDU sessions include one or more sessions that are not supported by TA2 or cell 2 of gNB2 and that were active with the UE in a previous cell or previous TA. The previous cell or previous TA can be gNB1 or another network node supporting, for example, URLLC or even other services.

[0216] exist Figure 7 In step 5, gNB1 sends a HO request confirm message to gNB2, which includes a HO command with a DRB corresponding to the deactivated PDU session. The DRB and / or the deactivated PDU session may be supported by gNB1 (such as URLLC in this example).

[0217] exist Figure 7 In step 6, gNB2 sends an RRC reconfiguration message to the UE. The message includes a handover (HO) command to cell 1 and DRB establishment information corresponding to the deactivated PDU session.

[0218] exist Figure 7 In step 7, the UE reactivates one or more PDU sessions that have been deactivated previously (i.e., before or when logging into TA2 or cell 2). This reactivation only requires the establishment of DRBs, because the deactivated PDU sessions have been kept active or maintained at the UE. In other words, the PDU sessions are only deactivated globally or on the network side, and are retained at the UE, but with deactivated DRBs. Therefore, it can be said that in step 7, at the UE, only the DRBs corresponding to the deactivated PDU sessions are reactivated.

[0219] After completion, in step 8, the UE transmits an RRC reconfiguration complete message to gNB1.

[0220] In response to the RRC Reconfiguration Complete message, two options on the network side are discussed below.

[0221] On the network side, as option 1, the PDU Session is reactivated at the SMF, or as option 2, the buffered DL data of the PDU Session at gNB2 is forwarded to the slicing-enabled gNB1 supporting the UE.

[0222] In step 9, as the first step of option 1, gNB1 sends a path switch request message including a command or notifier to reactivate the PDU session of URLLC to AMF. The message can be an NGAP message. In addition, the message can be or include a path switch request in the inter-gNB scenario or a new NGAP message in the intra-gNB scenario.

[0223] In step 10, the AMF sends a session modification request message to the SMF in response to a path switch request message including a command or notifier for reactivating the PDU session of URLLC received from gNB1.

[0224] In step 11, SMF establishes a tunnel to UPF in response to receiving the session modification request message. Then in step 12, SMF replies to AMF with a session modification response message indicating that the tunnel has been established.

[0225] In step 13, as a first step for option 2, gNB2 forwards the buffered DL data of the URLLC session that was active with the UE and then deactivated to gNB1.

[0226] In step 14, after receiving the data, gNB1 sends a path switch request message to AMF.

[0227] In step 15, the AMF sends a session modification request message to the SMF in response to the path switch request message received from gNB1.

[0228] In step 16, in response to receiving the session modification request message, SMF moves the tunnel to the UPF corresponding to the session. Then in step 17, SMF replies to AMF with a session modification response message indicating that the tunnel has been moved.

[0229] Figure 7 Option 1 with Figure 6 The counterpart of Option 1 is to indicate the deactivation of the PDU session to the network side (particularly the SMF). Therefore, when the UE loses slice support, the tunnel is removed ( Figure 6 ), and once the UE obtains slice support, the tunnel is established again ( Figure 7 ).

[0230] Similarly, Figure 7 Option 2 with Figure 6 The counterpart of Option 2 is that the deactivation of the PDU session is not indicated to the network side. Therefore, when the UE loses slice support, DL data is buffered ( Figure 6 ), and when the UE gets slice support again, the DL data and tunnel are moved ( Figure 7 ).

[0231] Figure 8A flow chart showing a method of operating a user equipment in a network is shown. Figure 8 The method shown in shows pausing data transmission of a data session.

[0232] The method is performed by a user equipment (also referred to as user equipment (UE)) or an apparatus used in the user equipment. For example, the UE may be configured as described above with reference to Figure 1 The wireless communication system 100 described above may be represented by any one of the mobile communication devices 102, 104, 105, or by the mobile communication devices 102, 104, 105 as described above with reference to Figure 2 The communication device 200 is described as an example.

[0233] In one example, a network may include at least two cells, including a first cell and a second cell. Each cell corresponds to or belongs to a tracking area. For example, in the network, the first tracking area includes the first cell, and the second tracking area includes the second cell. The first cell and the second cell (or tracking area) are each controlled or served by a base station. The first base station controls the first cell and / or the first tracking area, and the second base station controls the second cell and / or the second tracking area. Alternatively, a single base station (e.g., a gNB) controls the cell and / or the tracking area. The network also includes core network functions.

[0234] In the network, the concept of network slicing is established. The network slices configured in the network may include a first slice configured in two cells (i.e., a first cell and a second cell) and providing a first service, a second slice configured in the first cell and providing a second service, and a third slice configured in the second cell and providing a third service.

[0235] The UE may reside on one of the cells of the network (e.g., the first cell), and the first slice and the second slice may be configured as slices allowed for the UE. That is, the UE is allowed to use the services of the first slice and the second slice. The network may configure the first and second tracking areas for the UE, and may configure the registration area including the first and second tracking areas for the UE.

[0236] In box 810, the UE determines a change of the user equipment from a first coverage area that provides a network slice allowed for the user equipment to a second coverage area that does not provide a network slice. The first coverage area may correspond to a first tracking area and / or a first cell, and the second coverage area may correspond to a second tracking area and / or a second cell. The determination made by the UE may include: receiving a message from a communication network. Such a message may include an indication that a network slice is not provided, an indication that a change of the user equipment from the second coverage area to the first coverage area has been or will be made, and / or an indication that the user equipment will suspend a data session. The message from the communication network may be an RRC reconfiguration message. Such a message may also include that the DRB corresponding to the network slice is no longer used for the UL. Receiving an explicit indication from the RAN whether a slice or service is supported (i.e., a message as described above) can enhance consistency between the RAN and the UE. The RAN may know whether a coverage area provides a network slice based on a cell ID, etc.

[0237] As an alternative to a message from the communication network, the user equipment or UE may detect that the second coverage area does not provide a network slice.

[0238] At block 820, the UE suspends data transmission for a data session established in the first coverage area or another coverage area for the network slice. The suspension may include releasing a user equipment data radio bearer associated with the data session or deactivating a user equipment data radio bearer. In other words, the UE suspends or blocks UL / DL data. The UE remains in connected mode, but there are no DRBs for the network slice or slice for the data session.

[0239] At block 830, the UE maintains a user equipment data session context for the data session. Thus, at least the context of the data session (e.g., PDU session) is retained or stored at the UE. The maintained session context may include information such as a session ID, an IP or protocol configuration for restarting the session, a state of the session, etc. Furthermore, maintaining the user equipment data session context or the data session may include storing or buffering data from the data session, such as UL data. Maintaining may include the UE maintaining the data session at the non-access layer and suspending the data session at the access layer. Thus, when the UE does not receive a radio bearer for the data session, it does not terminate the data session, but at least maintains the user equipment data session context.

[0240] In some examples, method 800 may also include: at block 840, deactivating a user equipment data radio bearer associated with the data session. Such a step may include: the UE releasing a user equipment data radio bearer associated with the data session or deactivating a user equipment data radio bearer. The deactivation may affect one or more user equipment data radio bearers.

[0241] Fig. 9 A flow chart showing a method of operating a user equipment in a network is shown. Fig. 9 The method shown in shows data transmission for reactivating a data session.

[0242] The method is performed by a user equipment (also referred to as user equipment (UE)) or an apparatus used in the user equipment. For example, the UE may be configured as described above with reference to Figure 1 The wireless communication system 100 described above may be represented by any one of the mobile communication devices 102, 104, 105, or by the mobile communication devices 102, 104, 105 as described above with reference to Figure 2 The communication device 200 is described as an example.

[0243] In one example, a network may include at least two cells, including a first cell and a second cell. Each cell corresponds to or belongs to a tracking area. For example, in the network, the first tracking area includes the first cell, and the second tracking area includes the second cell. The first cell and the second cell (or tracking area) are each controlled or served by a base station. The first base station controls the first cell and / or the first tracking area, and the second base station controls the second cell and / or the second tracking area. Alternatively, a single base station (e.g., a gNB) controls the cell and / or the tracking area. The network also includes core network functions.

[0244] In the network, the concept of network slicing is established. The network slices configured in the network may include a first slice configured in two cells (i.e., a first cell and a second cell) and providing a first service, a second slice configured in the first cell and providing a second service, and a third slice configured in the second cell and providing a third service.

[0245] The UE may reside on one of the cells of the network (e.g., the second cell), and the second slice may be configured as a slice allowed for the UE. That is, the UE is only allowed to use the services of the second slice. The network may configure the first and second tracking areas for the UE, and may configure the registration area including the first and second tracking areas for the UE. The first cell of the network allows or provides the first slice and the second slice.

[0246] At block 910, the UE determines a change of the user equipment from a second coverage area that does not provide a network slice allowed for the user equipment to a first coverage area that provides a network slice. The first coverage area may correspond to a first tracking area and / or a first cell, and the second coverage area may correspond to a second tracking area and / or a second cell. Here, the UE moves with Figure 8 The UE moves in the opposite direction. Therefore, Fig. 9 The method shown in can be followed Figure 8In addition, a data session for the network slice may be established in the first coverage area or in another coverage area where the UE was located before entering the first coverage area.

[0247] The determination made by the UE may include: receiving a message from the communication network. Such a message may include an indication that network slicing is not provided, an indication that a change of the user equipment from the second coverage area to the first coverage area has been or will be made, and / or an indication that the user equipment will suspend a data session. The message from the communication network may be an RRC reconfiguration message. Such a message may also include that the DRB corresponding to the network slice is no longer used for the UL. Receiving an explicit indication of whether a slice or service is supported from the RAN (i.e., a message as described above) can enhance consistency between the RAN and the UE. The RAN can know whether the coverage area provides network slicing based on the cell ID, etc.

[0248] As an alternative to a message from the communication network, the user equipment or UE may detect that the second coverage area does not provide a network slice.

[0249] At block 920, the UE reactivates data transmission of a data session from a user equipment data session context maintained at the user equipment. The data session has previously been established for a network slice in the first coverage area or in another coverage area providing a network slice allowed for the user equipment. Such steps may include the UE establishing or activating a user equipment data radio bearer associated with the data session. The reactivation may affect one or more user equipment data radio bearers.

[0250] At least a context of a data session (e.g., a PDU session) is maintained or stored at the UE. The maintained session context may include information such as a session ID, an IP or protocol configuration for restarting the session, a state of the session, etc. In addition, maintaining the user equipment data session context or data session may include storing or buffering data from the data session, such as UL data. Maintaining may include the UE maintaining the data session at the non-access layer and suspending the data session at the access layer.

[0251] In some examples, method 900 may also include establishing a user equipment data radio bearer for the reactivated data session at block 930. Establishing may affect one or more user equipment data radio bearers.

[0252] Fig.10 A flow chart of a method of operating a network device in a communication network is shown. Fig.10 The method shown in shows pausing data transmission of a data session.

[0253] The method is performed by a network. More specifically, the method may be performed by one or more network nodes or network functions of the network, or by a device used in a network node, or by a network function. For example, the method may be performed by a base station (e.g., by the above reference Figure 3 The control device 300 described in the present invention may be a base station) and / or a core network function (such as AMF). Examples of network nodes / devices or network functions may be Figure 6 and 7 gNB1 and / or AMF in the

[0254] In one example, a network may include at least two cells, including a first cell and a second cell. Each cell corresponds to or belongs to a tracking area. For example, in the network, the first tracking area includes the first cell, and the second tracking area includes the second cell. The first cell and the second cell (or tracking area) are each controlled or served by a base station. The first base station controls the first cell and / or the first tracking area, and the second base station controls the second cell and / or the second tracking area. Alternatively, a single base station (e.g., a gNB) controls the cell and / or the tracking area. The network also includes core network functions.

[0255] In the network, the concept of network slicing is established. The network slices configured in the network may include a first slice configured in two cells (i.e., a first cell and a second cell) and providing a first service, a second slice configured in the first cell and providing a second service, and a third slice configured in the second cell and providing a third service.

[0256] The UE may reside on one of the cells of the network (e.g., the first cell), and the first slice and the second slice may be configured as slices allowed for the UE. That is, the UE is allowed to use the services of the first slice and the second slice. The network may configure the first and second tracking areas for the UE, and may configure the registration area including the first and second tracking areas for the UE.

[0257] At block 1010, the network sends a message to a user equipment or UE indicating a change from a first coverage area providing a network slice allowed for the user equipment to a second coverage area not providing the network slice, the message including information indicating to the user equipment to suspend a data session established for the network slice not provided in the second coverage area. The message may be sent after the network determines a change of the user equipment from the first coverage area providing a network slice allowed for the user equipment to the second coverage area not providing the network slice.

[0258] The first coverage area may correspond to a first tracking area and / or a first cell, and the second coverage area may correspond to a second tracking area and / or a second cell. The message may include an indication that network slicing is not provided, an indication that a change of the user equipment from the second coverage area to the first coverage area has been or will be made, and / or an indication that the user equipment will suspend a data session. The message from the communication network may be an RRC reconfiguration message. Such a message may also include that the DRB corresponding to the network slice is no longer used for the UL. Receiving an explicit indication from the RAN whether a slice or service is supported (i.e., a message as described above) can enhance consistency between the RAN and the UE. The RAN can know whether the coverage area provides network slicing based on the cell ID, etc.

[0259] At block 1020, the network receives a message from the user equipment indicating a change from the first coverage area to the second coverage area. The message from the UE may indicate that the UE has suspended data transmission for a data session established in the first coverage area or in another coverage area for the network slice. The suspension may include releasing a user equipment data radio bearer associated with the data session or deactivating a user equipment data radio bearer. In other words, the UE suspends or blocks UL / DL data. The UE remains in connected mode, but there are no DRBs for the slice for the network slice or data session.

[0260] In some examples, method 1000 may also include: at box 1030, the network maintains a network device data session context for the data session. Therefore, at least the context of the data session (e.g., PDU session) corresponding to the network slice is retained or stored at the network. The maintained session context may include information such as session ID, IP or protocol configuration for restarting the session, the state of the session, etc. In addition, maintaining the network device data session context or data session may include: storing or buffering data from the data session, such as DL data. Maintenance may include: notifying AMF, SMF and / or other network functions. Maintenance may also include: blocking DL.

[0261] In some examples, method 1000 may also include: deactivating data radio bearers associated with the data session. Such steps may include: the network releasing data radio bearers associated with the data session or deactivating data radio bearers. Deactivation may affect one or more data radio bearers.

[0262] Fig.11 A flow chart of a method of operating a communication network is shown. Fig.11 The method shown in shows data transmission for reactivating a data session.

[0263] The method is performed by a network. More specifically, the method may be performed by one or more network nodes or network functions of the network, or by a device used in a network node, or by a network function. For example, the method may be performed by a base station (e.g., by the above reference Figure 3 The control device 300 described is represented by a base station) and / or a core network function (such as AMF).

[0264] In one example, a network may include at least two cells, including a first cell and a second cell. Each cell corresponds to or belongs to a tracking area. For example, in the network, the first tracking area includes the first cell, and the second tracking area includes the second cell. The first cell and the second cell (or tracking area) are each controlled or served by a base station. The first base station controls the first cell and / or the first tracking area, and the second base station controls the second cell and / or the second tracking area. Alternatively, a single base station (e.g., a gNB) controls the cell and / or the tracking area. The network also includes core network functions.

[0265] In the network, the concept of network slicing is established. The network slices configured in the network may include a first slice configured in two cells (i.e., a first cell and a second cell) and providing a first service, a second slice configured in the first cell and providing a second service, and a third slice configured in the second cell and providing a third service.

[0266] The UE may reside on one of the cells of the network (e.g., the second cell), and the second slice may be configured as a slice allowed for the UE. That is, the UE is only allowed to use the services of the second slice. The network may configure the first and second tracking areas for the UE, and may configure the registration area including the first and second tracking areas for the UE. The first cell of the network allows or provides the first slice and the second slice.

[0267] At block 1110, the network sends a message to the user equipment indicating a change from a second coverage area that does not provide a network slice allowed for the user equipment to a first coverage area that provides a network slice, the message including information indicating to the user equipment or UE to reactivate a data session with the network slice from a user equipment data session context maintained at the user equipment, wherein the data session had previously been established for the network slice in the first coverage area or another coverage area that provides a network slice allowed for the user equipment. The message may be sent after the network determines a change of the user equipment from the first coverage area that provides a network slice allowed for the user equipment to the second coverage area that does not provide a network slice.

[0268] The first coverage area may correspond to a first tracking area and / or a first cell, and the second coverage area may correspond to a second tracking area and / or a second cell. The message may include an indication that a network slice is provided and / or an indication that a change of the user equipment from the second coverage area to the first coverage area has been or will be made. The message from the communication network may be an RRC reconfiguration message. Such a message may also include that the DRB corresponding to the network slice is now available for UL. Receiving an explicit indication from the RAN whether a slice or service is supported (i.e., a message as described above) can enhance consistency between the RAN and the UE. The RAN may know whether a coverage area provides network slicing based on the cell ID, etc.

[0269] At block 1120, the network receives a message from the user equipment indicating a change from the second coverage area to the first coverage area. The message from the UE may indicate that the UE has reactivated data transmission for a data session established in the first coverage area or another coverage area for the network slice.

[0270] In some examples, method 1100 may also include: at box 1130, the network reactivates a network slice data session maintained at the communication network, wherein the network slice data session has previously been established for a user device in a first coverage area or another coverage area providing the network slice. Therefore, at least the context of the data session (e.g., a PDU session) corresponding to the network slice is retained or stored at the network. The maintained session context may include information such as a session ID, an IP or protocol configuration for restarting the session, the state of the session, etc. In addition, the method may include: storing or buffering data from the data session, such as DL data. Maintenance may include: notifying AMF, SMF and / or other network functions. Maintenance may also include: blocking DL.

[0271] In some examples, method 1100 may also include activating or reactivating a data radio bearer associated with the data session. Activation may affect one or more data radio bearers.

[0272] In some examples, method 1100 may also include: sending buffered downlink data of the network slice, wherein the buffered downlink data is previously buffered downlink data of the network slice for a network slice data session that has been previously established for a user device of the network slice in a first coverage area or in another coverage area that provides the network slice allowed for use by the user device.

[0273] It should be understood that these devices may include or be coupled to other units or modules, such as radio components or radio heads for transmission and / or reception. Although these devices are described as one entity, different modules and memories may be implemented in one or more physical or logical entities.

[0274] It will be noted that although embodiments have been described for LTE and 5G NR, similar principles may be applied to other networks and communication systems where fast connection re-establishment needs to be implemented. Thus, although specific embodiments are described above by way of example with reference to specific example architectures for wireless networks, technologies and standards, the embodiments may be applied to any other suitable form of communication system other than that shown and described herein.

[0275] It is also noted herein that while exemplary embodiments are described above, there are several variations and modifications which may be made to the disclosed solution without departing from the scope of the present disclosure.

[0276] In general, various exemplary embodiments may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects of the present disclosure may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, however, the present disclosure is not limited thereto. Although various aspects of the present disclosure may be shown and described as block diagrams, flow charts, or using some other graphical representation, it is understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof.

[0277] The example embodiments of the present disclosure may be implemented by computer software or hardware or a combination of software and hardware that can be executed by a data processor of a mobile device (e.g., in a processor entity). Computer software or programs (also referred to as program products, including software routines, applets, and / or macros) may be stored in any device-readable data storage medium, and they include program instructions for performing specific tasks. A computer program product may include one or more computer executable components that are configured to perform an embodiment when the program is running. One or more computer executable components may be at least one software code or a portion thereof.

[0278] In addition, it should be noted at this point that any box of the logic flow in the figure can represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. Software can be stored on physical media such as: memory chips, or storage blocks implemented in processors, magnetic media (such as hard disks or floppy disks), and optical media (such as DVDs and their data variants CDs). Physical media are non-temporary media.

[0279] The memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based storage devices, magnetic storage devices and systems, optical storage devices and systems, fixed memory, and removable memory. The data processor may be of any type suitable for the local technical environment and may include, as non-limiting examples, one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an FPGA, a gate-level circuit, and a processor based on a multi-core processor architecture.

[0280] The exemplary embodiments of the present disclosure can be practiced in various components such as integrated circuit modules. Generally speaking, the design of integrated circuits is a highly automated process. Complex and powerful software tools can be used to convert a logic level design into a semiconductor circuit design that can be etched and formed on a semiconductor substrate.

[0281] The above description has been provided by way of non-limiting examples, i.e., a comprehensive and informative description of exemplary embodiments of the present disclosure. However, when read in conjunction with the accompanying drawings and the appended claims, many modifications and variations may become apparent to those skilled in the relevant art in view of the above description. However, all such and similar modifications to the present teachings are still within the scope of the present disclosure as defined in the appended claims. Indeed, there are further embodiments that include a combination of one or more embodiments with any other embodiments previously discussed.

Claims

1. A method for operating a user equipment in a communication network, the method comprising: - determining a change of the user equipment from a first coverage area providing a network slice allowed for the user equipment to a second coverage area not providing the network slice, - suspending data transmission of a data session established in the first coverage area or in another coverage area for the network slice, and - Maintaining a user equipment data session context for said data session.

2. The method according to claim 1, wherein: The suspending includes releasing a user equipment data radio bearer associated with the data session or deactivating the user equipment data radio bearer.

3. The method according to one of the preceding claims, wherein: The determination comprises receiving a message from the communication network that the network slice is not provided.

4. The method according to one of the preceding claims, wherein: The determining comprises receiving a message from the communication network instructing the user equipment to suspend the data session.

5. The method according to claim 3 , wherein: The message from the communications network is a RRC reconfiguration message.

6. The method according to one of the preceding claims, wherein: The determination includes: detecting, by the user equipment, that the network slice is not provided.

7. The method according to one of the preceding claims, wherein: The maintaining includes: maintaining the data session at the non-access layer by the user equipment, and suspending the data session at the access layer.

8. The method according to one of the preceding claims, wherein: The first coverage area is a first tracking area, and / or The second coverage area is a second tracking area.

9. The method according to one of the preceding claims, wherein: The data session is a PDU session.

10. The method according to one of the preceding claims, wherein: The user equipment is in a connected mode in at least one of the first coverage area and the second coverage area.

11. The method according to one of the preceding claims, further comprising: - sending a message to the network indicating a change from the first coverage area to the second coverage area.

12. A method of operating a network device in a communication network, the communication network comprising a first coverage area providing a network slice allowed for user equipment and a second coverage area not providing the network slice; the method comprising: - sending a message to the user equipment indicating a change from a first coverage area providing a network slice allowed for the user equipment to a second coverage area not providing the network slice, the message comprising information indicating to the user equipment to suspend a data session established for the network slice, - receiving a message from the user equipment indicating a change from the first coverage area to the second coverage area.

13. The method according to claim 12, wherein: The first coverage area is a first tracking area, and / or The second coverage area is a second tracking area.

14. The method according to claim 12 or 13, wherein: The data session is a PDU session.

15. The method according to one of claims 12 to 14, further comprising: - if the user equipment is in the second coverage area, maintaining a network equipment data session context for the data session.

16. The method according to one of claims 12 to 15, further comprising: -Upon receipt of the message indicating a change from the first coverage area to the second coverage area, deactivating the network data radio bearer associated with the network slice data session.

17. The method according to claim 16, wherein: Deactivating the network data radio bearer includes: when the user equipment is in the second coverage area, deactivating a tunnel associated with the data session and / or maintaining a data session context for the network slice.

18. The method according to one of claims 12 to 17, further comprising: -After receiving the message indicating a change from the first coverage area to the second coverage area, buffering and / or discarding downlink data of the network slice.

19. The method according to claim 18, further comprising: The amount of discarded data is indicated to the communications network.

20. A method of operating a user equipment in a communication network, the method comprising: - determining a change of the user equipment from a second coverage area not providing a network slice allowed for the user equipment to a first coverage area providing the network slice, -Reactivating data transmission of a data session from a user equipment data session context maintained at the user equipment, wherein the data session has been previously established for the network slice in the first coverage area or in another coverage area providing the network slice allowed for the user equipment.

21. The method according to claim 20, wherein: The determination comprises receiving a message from the communication network that the network slice is provided.

22. The method according to claim 20 or 21, wherein: The determining comprises receiving a message from the communication network instructing the user equipment to reactivate the data session.

23. The method according to one of claims 20 to 22, wherein: The message from the communication network includes information instructing the user equipment to establish a user equipment data radio bearer for the reactivated data session, wherein the method further comprises establishing a user equipment data radio bearer for the reactivated data session.

24. The method according to one of claims 21 to 23, wherein: The message from the communications network is a RRC reconfiguration message.

25. The method according to one of claims 20 to 24, wherein: The determining includes: detecting, by the user equipment, that the network slice is provided.

26. The method according to one of claims 20 to 25, wherein: The reactivation includes establishing or activating a user equipment data radio bearer for the reactivated data session.

27. The method according to one of claims 20 to 26, wherein: The first coverage area is a first tracking area, and / or The second coverage area is a second tracking area.

28. The method according to one of claims 20 to 27, wherein: The data session is a PDU session.

29. The method according to one of claims 20 to 28, further comprising: - sending a message to the network indicating a change from the second coverage area to the first coverage area.

30. A method of operating a network device in a communication network, the communication network comprising a first coverage area providing a network slice allowed for user equipment and a second coverage area not providing the network slice, the method comprising: - sending a message to the user equipment indicating a change from a second coverage area that does not provide a network slice allowed for the user equipment to a first coverage area that provides the network slice, the message comprising information instructing the user equipment to reactivate a data session with the network slice from a user equipment data session context maintained at the user equipment, wherein the data session had previously been established for the network slice in the first coverage area or in another coverage area that provides the network slice allowed for the user equipment, - receiving a message from the user equipment indicating a change from the second coverage area to the first coverage area.

31. The method according to claim 30, wherein: The first coverage area is a first tracking area, and / or The second coverage area is a second tracking area.

32. The method according to one of claims 30 to 31, wherein: The data session is a PDU session.

33. The method according to one of claims 30 to 32, further comprising: -Reactivating a network slice data session maintained at the communication network, wherein the network slice data session has been previously established for the user equipment in the first coverage area or in another coverage area providing the network slice.

34. The method according to one of claims 30 to 33, further comprising: -Establishing a network data radio bearer associated with the network slice data session.

35. The method according to one of claims 30 to 34, further comprising: -Sending buffered downlink data of the network slice, wherein the buffered downlink data is previously buffered downlink data of the network slice for the network slice data session, which has been previously established for the user equipment of the network slice in the first coverage area or in another coverage area providing the network slice allowed for the user equipment.

36. A user equipment comprising: at least one processor; as well as at least one memory comprising computer program code, wherein the computer program code, when executed using the at least one processor, causes the user equipment to at least: determining a change of the user equipment from a first coverage area providing a network slice allowed for the user equipment to a second coverage area not providing the network slice, suspending data transmission of a data session established in the first coverage area or in another coverage area for the network slice, and A user equipment data session context for the data session is maintained at the user equipment.

37. The user equipment according to claim 36, wherein: The computer program code, when executed using the at least one processor, further causes the user equipment to perform a method according to any one of claims 2 to 11.

38. A user equipment comprising: at least one processor; as well as at least one memory comprising computer program code, wherein the computer program code, when executed using the at least one processor, causes the user equipment to at least: determining a change of the user equipment from a second coverage area not providing a network slice allowed for the user equipment to a first coverage area providing the network slice, Reactivate data transmission of a data session from a user equipment data session context maintained at the user equipment, wherein the data session had been previously established for the network slice in the first coverage area or in another coverage area providing the network slice allowed for the user equipment.

39. The user equipment according to claim 38, wherein: The computer program code, when executed using the at least one processor, further causes the user equipment to perform a method according to any one of claims 21 to 29.

40. A network device comprising: at least one processor; as well as at least one memory comprising computer program code, wherein the computer program code, when executed using the at least one processor, causes the network device to at least: sending a message to the user equipment indicating a change from a first coverage area providing a network slice allowed for the user equipment to a second coverage area not providing the network slice, the message comprising information indicating to the user equipment to suspend a data session established for the network slice, A message is received from the user equipment indicating a change from the first coverage area to the second coverage area.

41. The network device according to claim 40, wherein: The computer program code, when executed using the at least one processor, further causes the network device to perform a method according to any one of claims 13 to 19.

42. A network device comprising: at least one processor; as well as at least one memory comprising computer program code, wherein the computer program code, when executed using the at least one processor, causes the network device to at least: sending a message to the user equipment indicating a change from a second coverage area that does not provide a network slice allowed for the user equipment to a first coverage area that provides the network slice, the message comprising information instructing the user equipment to reactivate a data session with the network slice from a user equipment data session context maintained at the user equipment, wherein the data session had previously been established for the network slice in the first coverage area or in another coverage area that provides the network slice allowed for the user equipment, A message is received from the user equipment indicating a change from the second coverage area to the first coverage area.

43. The network device according to claim 42, wherein: The computer program code, when executed using the at least one processor, further causes the network device to perform a method according to any one of claims 31 to 35.

44. A user equipment comprising: means for determining a change of the user equipment from a first coverage area providing a network slice allowed for the user equipment to a second coverage area not providing the network slice, means for suspending data transmission of a data session established in said first coverage area or in another coverage area for said network slice, and Means for maintaining a user equipment data session context for the data session.

45. The user equipment according to claim 44, wherein: The computer program code, when executed using the at least one processor, further causes the user equipment to perform a method according to any one of claims 2 to 11.

46. ​​A user device comprising: means for determining a change of the user equipment from a second coverage area not providing a network slice allowed for the user equipment to a first coverage area providing the network slice, Means for reactivating data transmission of a data session from a user equipment data session context maintained at the user equipment, wherein the data session had been previously established for the network slice in the first coverage area or in another coverage area providing the network slice allowed for use by the user equipment.

47. The user equipment according to claim 46, wherein: The computer program code, when executed using the at least one processor, further causes the user equipment to perform a method according to any one of claims 21 to 29.

48. A network device comprising: means for sending a message to the user equipment indicating a change from a first coverage area providing a network slice allowed for the user equipment to a second coverage area not providing the network slice, the message comprising information indicating to the user equipment to suspend a data session established for the network slice, Means for receiving a message from the user equipment indicating a change from the first coverage area to the second coverage area.

49. The network device according to claim 48, wherein: The computer program code, when executed using the at least one processor, further causes the network device to perform a method according to any one of claims 13 to 19.

50. A network device comprising: means for sending a message to the user equipment indicating a change from a second coverage area not providing a network slice allowed for the user equipment to a first coverage area providing the network slice, the message comprising information instructing the user equipment to reactivate a data session with the network slice from a user equipment data session context maintained at the user equipment, wherein the data session had previously been established for the network slice in the first coverage area or in another coverage area providing the network slice allowed for the user equipment, Means for receiving a message from the user equipment indicating a change from the second coverage area to the first coverage area.

51. The network device according to claim 50, wherein: The computer program code, when executed using the at least one processor, further causes the network device to perform a method according to any one of claims 31 to 35.

52. A non-transitory computer readable medium containing computer executable instructions which, when executed on one or more processors, perform the steps of the method of any one of claims 1 to 11 or 20 to 29.

53. A non-transitory computer readable medium containing computer executable instructions which, when executed on one or more processors, perform the steps of the method of any one of claims 12 to 19 or 31 to 35.

Images