User equipment context handling

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) can receive a radio access network (RAN) configuration for a plurality of service modules corresponding to a plurality of services and a plurality of service-specific UE contexts. While in an inactive state, the UE can transmit a resume identifier (ID) and one or more service indexes corresponding to one or more requested services of the plurality of services. The UE can receive a response indicating one or more valid services of the one or more requested services. The UE can transmit a communication associated with a valid service of the one or more valid services. Numerous other aspects are described.

Description

Cross-reference to related applications

[0001] This patent application claims priority to U.S. Patent Application No. 18 / 513,180, filed November 17, 2023, entitled “USER EQUIPMENT CONTEXTHANDLING,” which is assigned to the assignee of this application. The disclosure of the earlier application is considered part of this patent application and is incorporated herein by reference. Technical Field

[0002] This disclosure relates in general to wireless communication, and to technologies and apparatus for handling user equipment context. Background Technology

[0003] Wireless communication systems are widely deployed to provide a variety of services, including voice, text, messaging, video, data, and / or other services. Services may include unicast, multicast, and / or broadcast services, etc. Typical wireless communication systems employ multiple access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (e.g., time-domain resources, frequency-domain resources, spatial-domain resources, and / or device transmit power, etc.). Examples of such multiple access RATs include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0004] Such multiple access RATs have been adopted in various telecommunications standards to provide a common protocol enabling different wireless communication devices to communicate at city, national, regional, or global levels. An example telecommunications standard is New Radio (NR). NR (which can also be referred to as 5G) is part of the continuous evolution of mobile broadband announced by the 3rd Generation Partnership Project (3GPP). NR (and other mobile broadband evolutions beyond NR) can be designed to better support the deployment of Internet of Things (IoT) and degraded-capacity devices, industrial connectivity, millimeter-wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployment, sidelinks and other device-to-device direct communication technologies (e.g., cellular vehicle-to-everything (CV2X) communications), massive MIMO, decomposed network architectures and network topology expansion, multi-subscriber implementations, high-precision positioning and / or radio frequency (RF) sensing, and more. As the demand for mobile broadband access continues to grow, further improvements to NR can be implemented, and other radio access technologies, such as 6G, can be introduced to further advance mobile broadband evolution. Summary of the Invention

[0005] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include receiving a radio access network (RAN) configuration for multiple service modules corresponding to multiple services and multiple service-specific UE contexts. The method may include, when in an inactive state, transmitting a recovery identifier (ID) and one or more service indices corresponding to one or more requested services among the multiple services. The method may include receiving a response indicating one or more valid services among the one or more requested services. The method may include transmitting communication associated with a valid service among the one or more valid services.

[0006] Some aspects described herein relate to a method of wireless communication performed by a first network entity. The method may include receiving a recovery ID from a second network entity, the recovery ID having identification information associated with retrieving a UE context for a UE. The method may also include sending a response associated with the UE context to the second network entity.

[0007] Some aspects described herein relate to a method of wireless communication performed by a first network entity. The method may include receiving a recovery ID from a UE, the recovery ID having identification information associated with retrieving a UE context for that UE. The method may include sending the recovery ID to a second network entity. The method may include receiving the UE context. The method may include sending a response to the UE.

[0008] Some aspects described herein relate to a method for wireless communication performed by a first network entity. The method may include receiving registration information from a second network entity storing a UE context. The method may include receiving a recovery ID from a third network entity, the recovery ID having identification information associated with retrieving the UE context. The method may include sending a response associated with the UE context.

[0009] Some aspects described herein relate to an apparatus for wireless communication at a UE. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be individually or collectively configured to cause the UE to receive RAN configuration for multiple service modules corresponding to multiple services and multiple service-specific UE contexts. The one or more processors may be individually or collectively configured to cause the UE to send a recovery ID and one or more service indices corresponding to one or more requested services among the multiple services when in an inactive state. The one or more processors may be individually or collectively configured to cause the UE to receive a response indicating one or more valid services among the one or more requested services. The one or more processors may be individually or collectively configured to cause the UE to send communications associated with a valid service among the one or more valid services.

[0010] Some aspects described herein relate to an apparatus for wireless communication at a first network entity. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be individually or collectively configured to cause the first network entity to receive a recovery ID from a second network entity, the recovery ID having identification information associated with retrieving a UE context for a UE. The one or more processors may be individually or collectively configured to cause the first network entity to send a response associated with the UE context to the second network entity.

[0011] Some aspects described herein relate to an apparatus for wireless communication at a first network entity. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be individually or collectively configured to cause the first network entity to receive a recovery ID from a UE, the recovery ID having identification information associated with retrieving a UE context for the UE. The one or more processors may be individually or collectively configured to cause the first network entity to transmit the recovery ID to a second network entity. The one or more processors may be individually or collectively configured to cause the first network entity to receive the UE context. The one or more processors may be individually or collectively configured to cause the first network entity to send a response to the UE.

[0012] Some aspects described herein relate to an apparatus for wireless communication at a first network entity. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured individually or collectively to cause the first network entity to receive registration information from a second network entity storing a UE context. The one or more processors may be configured individually or collectively to cause the first network entity to receive a recovery ID from a third network entity, the recovery ID having identification information associated with retrieving the UE context. The one or more processors may be configured individually or collectively to cause the first network entity to send a response associated with the UE context.

[0013] Some aspects described herein relate to a non-transitory computer-readable medium for a set of instructions for wireless communication by a UE. When executed by one or more processors of the UE, the set of instructions enables the UE to receive RAN configuration for multiple service modules corresponding to multiple services and multiple service-specific UE contexts. When executed by one or more processors of the UE, the set of instructions enables the UE to send a recovery ID and one or more service indices corresponding to one or more requested services among the multiple services when in an inactive state. When executed by one or more processors of the UE, the set of instructions enables the UE to receive responses indicating one or more valid services among the one or more requested services. When executed by one or more processors of the UE, the set of instructions enables the UE to send communications associated with a valid service among the one or more valid services.

[0014] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a first network entity. When executed by one or more processors of the first network entity, the set of instructions enables the first network entity to receive a recovery ID from a second network entity, the recovery ID having identification information associated with retrieving a UE context for a UE. When executed by one or more processors of the first network entity, the set of instructions enables the first network entity to send a response associated with the UE context to the second network entity.

[0015] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a first network entity. When executed by one or more processors of the first network entity, the set of instructions causes the first network entity to receive a recovery ID from a UE, the recovery ID having identification information associated with retrieving a UE context for the UE. When executed by one or more processors of the first network entity, the set of instructions causes the first network entity to send the recovery ID to a second network entity. When executed by one or more processors of the first network entity, the set of instructions causes the first network entity to receive the UE context. When executed by one or more processors of the first network entity, the set of instructions causes the first network entity to send a response to the UE.

[0016] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a first network entity. When executed by one or more processors of the first network entity, the set of instructions enables the first network entity to receive registration information from a second network entity storing a UE context. When executed by one or more processors of the first network entity, the set of instructions enables the first network entity to receive a recovery ID from a third network entity, the recovery ID having identification information associated with retrieving the UE context. When executed by one or more processors of the first network entity, the set of instructions enables the first network entity to send a response associated with the UE context.

[0017] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving RAN configuration for multiple service modules corresponding to multiple services and multiple service-specific UE contexts. The apparatus may include components for transmitting a recovery ID and one or more service indices corresponding to one or more requested services among the multiple services when in an inactive state. The apparatus may include components for receiving a response indicating one or more valid services among the one or more requested services. The apparatus may include components for transmitting communications associated with a valid service among the one or more valid services.

[0018] Some aspects described herein relate to a first apparatus for wireless communication. The apparatus may include components for receiving a recovery ID from a second apparatus, the recovery ID having identification information associated with retrieving a UE context for a UE; and components for sending a response associated with the UE context to the second apparatus.

[0019] Some aspects described herein relate to a first apparatus for wireless communication. The apparatus may include components for receiving a recovery ID from a UE, the recovery ID having identification information associated with retrieving a UE context for the UE; components for transmitting the recovery ID to a second apparatus; components for receiving the UE context; and components for transmitting a response to the UE.

[0020] Some aspects described herein relate to a first apparatus for wireless communication. The apparatus may include components for receiving registration information from a second apparatus storing a UE context; components for receiving a recovery ID from a third apparatus, the recovery ID having identification information associated with retrieving the UE context; and components for sending a response associated with the UE context.

[0021] The entirety of the aspects includes, as fully described with reference to the accompanying drawings and illustrated by reference to the drawings, methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication equipment, network entities, network nodes and / or processing systems.

[0022] The features and technical advantages of the examples according to this disclosure have been summarized rather extensively above in order to better understand the detailed description below. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily utilized as the basis for modifying or designing other structures for achieving the same purpose of this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein (both their organization and manner of operation) and the associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each figure in the drawings is provided for illustrative and descriptive purposes and not as a limitation of the definitions in the claims. Attached Figure Description

[0023] Figure 1 This is a diagram illustrating an example of a wireless network.

[0024] Figure 2 This is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network.

[0025] Figure 3 This is a diagram illustrating an example of a decomposed base station architecture.

[0026] Figure 4 This is a diagram illustrating an example of a core network configured to provide network slicing.

[0027] Figure 5 This is a diagram illustrating examples of the user plane protocol stack and control plane protocol stack of the network node and core network used for communication with the UE.

[0028] Figure 6 This is an example diagram illustrating the design model.

[0029] Figure 7 This is an example diagram illustrating a 5G design.

[0030] Figure 8 This is a diagram illustrating an example of a new design for a network.

[0031] Figure 9 This is a diagram illustrating an example of a new radio (NR) system architecture according to this disclosure.

[0032] Figure 10 This is a diagram illustrating an example of a network design according to this disclosure.

[0033] Figure 11 This is a diagram illustrating an example of a control plane service according to this disclosure.

[0034] Figure 12 This is a diagram illustrating an example of a service-based architecture according to this disclosure.

[0035] Figure 13 This is a diagram illustrating an example of UE state management according to this disclosure.

[0036] Figure 14 This is a diagram illustrating an example of UE context management according to this disclosure.

[0037] Figure 15 This is a diagram illustrating an example of a UE restoring connection according to this disclosure.

[0038] Figure 16 This is a diagram illustrating an example of UE context management according to this disclosure.

[0039] Figure 17 This is a diagram illustrating an example of UE context management according to this disclosure.

[0040] Figure 18 This is a diagram illustrating an example of UE context management according to this disclosure.

[0041] Figure 19 This is a diagram illustrating an example of UE context management according to this disclosure.

[0042] Figure 20 This is a diagram illustrating an example of using a modular UE context according to this disclosure.

[0043] Figure 21 This is a continuation of an example illustrating the use of a modular UE context according to this disclosure.

[0044] Figure 22This is a diagram illustrating an example of using a modular UE context according to this disclosure.

[0045] Figure 23 This is a diagram illustrating an example process performed, for example, at the UE or at a device of the UE, according to this disclosure.

[0046] Figure 24 This is a diagram illustrating an example process performed, for example, at a first network entity or a device of the first network entity, according to the present disclosure.

[0047] Figure 25 This is a diagram illustrating an example process performed, for example, at a first network entity or a device of the first network entity, according to the present disclosure.

[0048] Figure 26 This is a diagram illustrating an example process performed, for example, at a first network entity or a device of the first network entity, according to the present disclosure.

[0049] Figure 27 This is a diagram of an example device for wireless communication according to the present disclosure.

[0050] Figure 28 This is a diagram of an example device for wireless communication according to the present disclosure.

[0051] Figure 29 This is a diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation

[0052] Various aspects of this disclosure are described below with reference to the accompanying drawings. However, aspects of this disclosure may be embodied in many different forms and should not be construed as limited to any specific aspect illustrated or described with reference to the drawings or otherwise presented in this disclosure. Rather, these aspects are provided so that this disclosure will be comprehensive and complete, and will fully convey the scope of protection of this disclosure to those skilled in the art. Those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, various combinations or numbers of aspects set forth herein may be used to implement an apparatus or a practice. Furthermore, the scope of this disclosure is intended to cover apparatuses having structures and / or functionalities other than those available for practicing the various aspects of this disclosure set forth herein, or methods practiced using these other structures and / or functionalities. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0053] Various methods, operations, apparatuses, and techniques will now be presented with reference to them. These methods, operations, apparatuses, and techniques will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0054] In the early days of the internet, data networks were designed to provide numerous services through heterogeneous devices. A design principle of the data network model was that it comprised a layered system architecture with simple service interfaces across many applications and transports. Different transport or service types could operate on this interface. With the introduction of smartphones, 4G successfully provided many services. The 4G protocol stack was designed to support the same model as the internet but used for cellular radio networks. This involved a separate control plane from the user plane to manage data transmission for cellular needs such as mobility. The separate control and user plane protocol stacks continued the architecture defined for 3G.

[0055] With the expansion of 4G, new features are being introduced to extend network communication capabilities to new use cases and device types. However, deploying new services without upgrading the underlying protocols is not feasible. Adding services via the control plane is not as straightforward as enabling new services via Internet Protocol (IP). The challenge lies in enabling services to be deployed independently, while utilizing existing protocols and allowing user equipment (UE) to directly address services without relying on intermediate network functions (e.g., Non-Access Layer (NAS) signaling, Radio Resource Control (RRC) signaling). Furthermore, as we move towards 6G, defining new data collection, location, or other protocols in 6G and subsequent generations (G) may not be optimal.

[0056] In some respects, the new network design can move away from a single set of protocols with centralized control (e.g., a Central Unit Control Plane (CU-CP) and Access and Mobility Functions (AMF)) that can make the control plane architecture quite inflexible. This can include providing separate control plane services that can be requested individually, such as authentication and security services, subscription services, and policy services. Any update to a separate service does not require an update to the entire control plane. For example, to use a service, a UE can send a message with an indication of the service (provided through the control plane) and its UE identifier (ID) to a Radio Access Network (RAN) entity. By using individually addressable services on the control plane, the UE and the network can have more flexible service deployments.

[0057] Another aspect of the network is the use of UE context. RAN network entities can use UE contexts for UEs. A UE context can be an information block in a RAN node associated with an active UE. This information block includes information that is expected to be stored to maintain network services for the UE. However, UE contexts in 5G may have limited reusability. In 5G, there is also a hard dependency between the RAN and the core network (CN) regarding UE contexts. The UE context in the CN and the UE context in the RAN are treated as a single UE context. This limits the area where UE contexts can be stored and reused. For example, a target Enhanced Distributed Unit (eDU) may be located at a distance from the source eDU. If the UE context used in the source eDU cannot be stored or retrieved in the target eDU, the UE context needs to be re-established, which increases latency.

[0058] Various aspects typically relate to UE connectivity to a network. In some aspects, 6G networks (or later) may be designed with a UE context store mechanism, which allows UE context to be reused in a larger area than allowed by 5G. The UE context store mechanism makes the UE context available to the target eDU when the UE connects to it. For example, the UE context store mechanism may include a discovery entity (e.g., a network entity in the CN) that has information about where the UE context for the UE can be obtained (e.g., in the source eDU or the RAN Context Store (RCS) entity). The UE may receive RAN configurations for multiple service modules. RAN configurations can configure the UE to use one or more services.

[0059] The UE may have received a recovery ID from a source eDU. The recovery ID may include an ID associated with the source eDU and transferable to a target eDU, which uses the recovery ID to retrieve the UE context during the recovery process (UE recovery from inactive state to connection with the eDU). The recovery ID may be unique to the UE context. The recovery ID may have identifying information used to retrieve the UE context. For example, the identifying information may be a number or code unique to the UE context and associated with the target eDU retrieving the UE context from another network entity. In some aspects, portions of the recovery ID may be unique to the source eDU that stored the UE context, last stored the UE context, or provided the UE context. UE inactivity may include the UE not being connected to an eDU or being released using a Radio Resource Control (RRC) release message with an inactivity identifier. UE inactivity may include RRC inactivity, RRC idle, or RRC disconnected. The UE may be in an inactive state and may send the recovery ID to the target eDU. The target eDU may send the recovery ID to a discovery entity pointing to the source eDU or RCS. The target eDU may retrieve the UE context from the source eDU or RCS. The UE can be connected to the target eDU and can now use the network's services.

[0060] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, the UE context for the UE can be retrieved over a larger geographic area by using discovery entities and / or RCS. The UE context does not need to be re-established by the target eDU, which reduces latency.

[0061] In 6G, UE contexts can also be modular and reflect service states. In some aspects, UE contexts can be handled using UE modular context modules, where each module can be active or inactive depending on the UE's needs. For example, when a UE connects to a target eDU only for service 1 and not service 2, the UE modular context module for service 1 is active in the RAN, while the UE modular context module for service 2 is not active (i.e., persistently inactive), although stored and maintained in the RAN. By modularizing service-specific UE contexts, a single UE context does not need to have information for all services, or each service does not require the same UE context. This provides a more service-based UE context handling, offering greater flexibility. With this flexibility, UE contexts can be smaller and more resource-efficient.

[0062] Multiple access radio access technology (RAT) has been adopted in various telecommunications standards to provide a common protocol that enables wireless communication devices to communicate at the city, enterprise, national, regional, or global level. For example, 5G New Radio (NR) is part of the continuous mobile broadband evolution announced by the 3rd Generation Partnership Project (3GPP). 5G NR supports a variety of technologies and use cases, including enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communication (mMTC), millimeter wave (mmWave) technology, beamforming, network slicing, edge computing, Internet of Things (IoT) connectivity and management, and network function virtualization (NFV).

[0063] With increasing demand for broadband access and the evolution of technologies supported by wireless communication networks, further technological improvements can be adopted or implemented in 5G NR or future RATs (such as 6G) to further advance the evolution of wireless communication for a wide variety of existing and new use cases and applications. Such technological improvements can be associated with new frequency band extensions, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, decomposed network architectures and network topology extensions, device aggregation, advanced duplex communication, sidelinks and other device-to-device direct communication, IoT (including passive or ambient IoT) networks, reduced-capacity (RedCap) UE functionality, industrial connectivity, multi-subscriber implementations, high-precision positioning, radio frequency (RF) sensing and / or artificial intelligence or machine learning (AI / ML), and more. These technological improvements can support use cases such as wireless backhaul, wireless data centers, extended reality (XR) and metaverse applications, meta-services for supporting vehicle connectivity, holographic and mixed reality communications, autonomous and collaborative robots, vehicle platooning and collaborative manipulation, sensor networks, posture monitoring, brain-computer interfaces, digital twin applications, asset management, and ubiquitous coverage applications using off-ground and / or aerial platforms, among others. The methods, operations, apparatuses, and techniques described herein can implement one or more of the foregoing technologies and / or support one or more of the foregoing use cases.

[0064] Figure 1 This is a diagram illustrating an example of a wireless communication network 100 according to the present disclosure. The wireless communication network 100 may be a 5G (or NR) network or a 6G network, or may include elements of a 5G (or NR) network or a 6G network, etc. The wireless communication network 100 may include a plurality of network nodes 110, shown as network node (NN) 110a, network node 110b, network node 110c, and network node 110d. Network nodes 110 may support communication with a plurality of UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e).

[0065] Network nodes 110 and UEs 120 of the wireless communication network 100 can communicate using the electromagnetic spectrum, which can be subdivided by frequency or wavelength into various categories, frequency bands, carriers, or channels. For example, devices in the wireless communication network 100 can communicate using one or more operating frequency bands. In some aspects, multiple wireless networks 100 can be deployed in a given geographical area. Each wireless communication network 100 can support a specific radio access technology (RAT) (which may also be referred to as an air interface) and can operate on one or more carrier frequencies within one or more frequency ranges. Examples of RATs include 4G RAT, 5G / NRRAT, and / or 6G RAT, etc. In some examples, when multiple RATs are deployed in a given geographical area, each RAT in that geographical area can operate on a different frequency to avoid interference with each other.

[0066] Various operating frequency bands have been defined as frequency ranges designated FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Although a portion of FR1 is greater than 6 GHz, in some documents and articles, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band. Similarly, in some documents and articles, FR2 is often (interchangeably) referred to as the “millimeter wave” band, but this is different from the Very High Frequency (EHF) band (30 GHz to 300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU). The frequencies between FR1 and FR2 are often referred to as the mid-band frequencies, including FR3. Frequency bands falling within FR3 can inherit FR1 or FR2 characteristics, thereby effectively extending the characteristics of FR1 or FR2 into mid-band frequencies. Therefore, "below 6 GHz" (if used herein) can broadly refer to frequencies less than 6 GHz, within FR1, and / or included in mid-band frequencies. Similarly, the term "millimeter wave" (if used herein) can broadly refer to frequencies included in mid-band frequencies, within FR2, FR4, FR4-a, FR4-1, or FR5, and / or within the EHF band. Higher frequency bands can extend 5G NR operation, 6G operation, and / or other RATs above 52.6 GHz. For example, each of FR4a, FR4-1, FR4, and FR5 falls within the EHF band. In some examples, the wireless communication network 100 can implement dynamic spectrum sharing (DSS), where multiple RATs (e.g., 4G / LTE and 5G / NR) are implemented within a single frequency band using dynamic bandwidth allocation (e.g., based on user demand). It is conceivable that the frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1 and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0067] Network node 110 may include one or more devices, components, or systems that enable communication between UE 120 and one or more devices, components, or systems of wireless communication network 100. Network node 110 may be, may include, or may also be referred to as an NR network node, 5G network node, 6G network node, Node B, eNB, gNB, Access Point (AP), Transmit / Receive Point (TRP), Mobility Element, Core, Network Entity, Network Element, Network Device, and / or another type of device, component, or system included in the RAN.

[0068] Network node 110 may be implemented as a single physical node (e.g., a single physical structure) or as two or more physical nodes (e.g., two or more different physical structures). For example, network node 110 may be a device or system implementing a portion of a radio protocol stack, a device or system implementing a complete radio protocol stack (such as a complete gNB protocol stack), or a collection of devices or systems collectively implementing a complete radio protocol stack. For example, and as shown, network node 110 may be an aggregated network node (with an aggregated architecture), meaning that network node 110 can implement a complete radio protocol stack physically and logically integrated within a single node (e.g., a single physical structure) in the wireless communication network 100. For example, aggregated network node 110 may consist of a single standalone base station or a single TRP that uses a complete radio protocol stack to implement or facilitate communication between UE 120 and the core network of wireless communication network 100. In some examples, core network node 130 may be a network node communicating with RAN nodes and / or other core network nodes.

[0069] Alternatively, and also as shown in the figure, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 can realize a radio protocol stack that is physically distributed and / or logically distributed among two or more nodes in the same or different geographical locations. For example, a decomposed network node may have a decomposed architecture. In some deployments, decomposed network node 110 may be used in integrated access and backhaul (IAB) networks, in open radio access networks (O-RAN) (such as network configurations compliant with the O-RAN Alliance), or in virtualized radio access networks (vRAN) (also referred to as cloud radio access networks (C-RAN)) to facilitate scaling by decomposing base station functionality into multiple units that can be deployed independently.

[0070] Network nodes 110 of wireless communication network 100 may include one or more central units (CUs), one or more distributed units (DUs), and / or one or more radio units (RUs). CUs may host one or more higher-layer control functions, particularly such as RRC functions, Packet Data Convergence Protocol (PDCP) functions, and / or Service Data Adaptation Protocol (SDAP) functions. DUs may host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and / or one or more higher physical (PHY) layers, at least in part, according to functional splits (such as those defined by 3GPP). In some examples, DUs may also host one or more lower PHY layer functions, such as Fast Fourier Transform (FFT), Inverse FFT (iFFT), beamforming, Physical Random Access Channel (PRACH) extraction and filtering, and / or scheduling of resources for one or more UEs 120, etc. RUs may host RF processing functions or lower PHY layer functions, such as FFT, iFFT, beamforming, or PRACH extraction and filtering, etc., according to functional splits (such as lower-layer functional splits). In this type of architecture, each RU can be operated to handle over-the-air (OTA) communications with one or more UE 120s.

[0071] In some aspects, network node 110 may include a combination of one or more CUs, one or more DUs, and / or one or more RUs. Additionally or alternatively, network node 110 may include one or more near real-time (near RT) RAN Intelligent Controllers (RICs) and / or one or more non-real-time (non-RT) RICs. In some examples, CUs, DUs, and / or RUs may be implemented as virtual units, such as Virtual Central Units (VCUs), Virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs), etc. Virtual units may be implemented as virtual network functions, such as those associated with cloud deployments.

[0072] Some network nodes 110 (e.g., base stations, RUs, or TRPs) can provide communication coverage for specific geographic areas. In 3GPP, the term "cell" can refer to the coverage area of ​​network node 110 or to network node 110 itself, depending on the context in which the term is used. Network node 110 can support one or more (e.g., three) cells. In some examples, network node 110 can provide communication coverage for macro cells, pico cells, femto cells, or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 120 with a service subscription. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UE 120 with a service subscription. A femto cell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UE 120 associated with that femto cell (e.g., UE 120 in a Closed Subscriber Group (CSG)). The network node 110 used for a macro cell may be referred to as a macro network node. Network node 110 used for a pico cell may be referred to as a pico network node. Network node 110 used for a femtocell may be referred to as a femto network node or a home network node. In some examples, the cell may not necessarily be stationary. For example, the geographical area of ​​the cell may be mobile based on the location of the associated mobile network node 110 (e.g., a train, satellite base station, unmanned aerial vehicle, or non-terrestrial network (NTN) network node).

[0073] The wireless communication network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, piconet nodes, femtonet nodes, relay network nodes, aggregation network nodes, and / or decomposition network nodes, etc. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 130a, network node 110b can be a pico network node for pico cell 130b, and network node 110c can be a femto network node for femto cell 130c. Compared to other types of network nodes 110, the various types of network nodes 110 typically transmit at different power levels, serve different coverage areas, and / or have different effects on interference in the wireless communication network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0074] In some examples, network node 110 may be, may include, or operate as a RU, TRP, or base station communicating with one or more UEs 120 via a radio access link (which may be referred to as a "Uu" link). The radio access link may include a downlink and an uplink. A "downlink" (or "DL") refers to the communication direction from network node 110 to UE 120, and an "uplink" (or "UL") refers to the communication direction from UE 120 to network node 110. Downlink channels may include one or more control channels and one or more data channels. Downlink control channels may be used to transmit downlink control information (DCI) (e.g., scheduling information, reference signals, and / or configuration information) from network node 110 to UE 120. Downlink data channels may be used to transmit downlink data (e.g., user data associated with UE 120) from network node 110 to UE 120. Downlink control channels may include one or more physical downlink control channels (PDCCH), and downlink data channels may include one or more physical downlink shared channels (PDSCH). The uplink channel may similarly include one or more control channels and one or more data channels. The uplink control channel can be used to transmit uplink control information (UCI) (e.g., reference signals and / or feedback corresponding to one or more downlink transmissions) from UE 120 to network node 110. The uplink data channel can be used to transmit uplink data (e.g., user data associated with UE 120) from UE 120 to network node 110. The uplink control channel may include one or more physical uplink control channels (PUCCH), and the uplink data channel may include one or more physical uplink shared channels (PUSCH). The downlink and uplink may each include a set of resources on which network node 110 and UE 120 can communicate.

[0075] Downlink and uplink resources may include time-domain resources (frames, subframes, time slots, and / or symbols), frequency-domain resources (bands, component carriers, subcarriers, resource blocks, and / or resource elements), and / or spatial-domain resources (specific transmission directions and / or beam parameters). Frequency-domain resources in some bands may be subdivided into bandwidth portions (BWPs). A BWP may be a contiguous block of frequency-domain resources allocated to one or more UEs 120 (e.g., a contiguous block of resource blocks). A UE 120 may be configured with both an uplink BWP and a downlink BWP (where the uplink BWP and downlink BWP may be the same BWP or different BWPs). BWPs may be dynamically configured and / or reconfigured (e.g., by sending DCI configuration to one or more UEs 120 via network node 110), meaning that BWPs may be adjusted in real-time (or near real-time) based on changing network conditions in the wireless communication network 100 and / or based on the specific requirements of one or more UEs 120. This allows for more efficient use of available frequency domain resources in the wireless communication network 100, as fewer frequency domain resources can be allocated to the BWP for UE 120 (which reduces the number of frequency domain resources that UE 120 needs to monitor), thus allowing more frequency domain resources to be distributed across multiple UE 120s. Therefore, the BWP can also assist in the implementation of such UE 120s by facilitating the configuration of smaller bandwidths for communications performed by lower-capacity UE 120s.

[0076] As described above, in some aspects, the wireless communication network 100 may be an IAB network, may include an IAB network, or may be included in an IAB network. In an IAB network, at least one network node 110 is an anchor network node communicating with a core network. The anchor network node 110 may also be referred to as an IAB donor (or "IAB donor"). The anchor network node 110 may be connected to the core network via a wired backhaul link. For example, the Ng interface of the anchor network node 110 may terminate at the core network. Additionally or alternatively, the anchor network node 110 may be connected to one or more devices in the core network that provide core access and mobility management functions (AMF). An IAB network typically also includes multiple non-anchor network nodes 110, which may also be referred to as relay network nodes or simply IAB nodes (or "IAB-nodes"). Each non-anchor network node 110 can directly communicate with the anchor network node 110 via a wireless backhaul link to access the core network, or can indirectly communicate with the anchor network node 110 via one or more other non-anchor network nodes 110 and an associated wireless backhaul link forming a backhaul path to the core network. Some anchor network nodes 110 or other non-anchor network nodes 110 can also directly communicate with one or more UEs 120 via a wireless access link carrying access services. In some examples, network resources for wireless communication (such as time resources, frequency resources, and / or spatial resources) can be shared between the access link and the backhaul link.

[0077] In some examples, any network node 110 relaying communication may be referred to as a relay network node, a relay station, or simply a repeater. A repeater may receive communications from an upstream station (e.g., another network node 110 or UE 120) and transmit communications to a downstream station (e.g., UE 120 or another network node 110). In this case, the wireless communication network 100 may include or be referred to as a "multi-hop network." Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. Additionally or alternatively, UE 120 can be a relay station capable of relaying transmissions to or from other UE 120s, or can operate as such a relay station. UE 120 relaying communication can be referred to as a UE repeater or relay UE, etc.

[0078] UE 120 may be physically distributed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. UE 120 may be, may include, an access terminal, another terminal, a mobile station, or a subscriber unit, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit. UE 120 may be, or may include, a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband and / or smart jewelry (such as a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), an extended reality (XR) device, a vehicle component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device), a UE function of a network node, and / or any other suitable device or function that can communicate via a wireless medium, or may be coupled to them.

[0079] UE 120 and / or network node 110 may include one or more chips, system-on-a-chip (SoC), chipsets, packages, or devices that individually or collectively constitute or include a processing system. The processing system includes processor (or “processing”) circuitry in the form of one or more processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs), and / or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), or other discrete gate or transistor logic components or circuits (all of which are generally referred to herein individually as “processors” or collectively as “processors” or “processor circuitry”). One or more of these processors may be individually or collectively configured to perform the various functions or operations described herein. A group of processors that can be configured or configured to perform a set of functions may include a first processor that can be configured or configured to perform a first function in the set, and a second processor that can be configured or configured to perform a second function in the set, or may include the entire group of processors that are configured or configured to perform the set of functions.

[0080] The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic components or circuits, each of which may include tangible storage media such as random access memory (RAM) or read-only memory (ROM) or combinations thereof (all of which are generally referred to herein individually as "memory" or collectively as "memory" or "memory circuitry"). One or more of these memories may be coupled to one or more processors in the processor (e.g., operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) and may store processor-executable code (such as software) individually or collectively, which, when executed by one or more processors in the processor, may configure one or more processors in the processor to perform the various functions or operations described herein. Additionally or alternatively, in some examples, one or more processors in the processor may be pre-configured to perform the various functions or operations described herein without being configured by software. The processing system may also include or be coupled to one or more modems (such as Wi-Fi (e.g., IEEE compliant) modems or cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modems). In some embodiments, one or more processors of the processing system include or implement one or more modems among the modems. The processing system may also include, or be coupled to, multiple radio components (collectively, “radio components”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled to one or more antennas among multiple antennas. In some embodiments, one or more processors of the processing system include or implement one or more of the radio components, RF chains, or transceivers. UE 120 may be included or may be contained in a housing that houses components associated with UE 120, including the processing system.

[0081] Some UEs 120 may be considered Machine Type Communication (MTC) UEs, Evolved or Enhanced Machine Type Communication (eMTC) UEs, Further Enhanced eMTC (feMTC) UEs or Enhanced feMTC (efeMTC) UEs, or further evolutions thereof, all of which may be collectively referred to as "MTC UEs". An MTC UE may be, may include, or may be included in or coupled with the following: robots, unmanned aerial vehicles or drones, remote devices, sensors, meters, monitors, and / or location tags. Some UEs 120 may be considered IoT devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. IoT UEs or NB-IoT devices may be, may include, or may be included in or coupled with the following: industrial machines, appliances, refrigerators, doorbell camera devices, home automation devices, and / or lighting fixtures, etc. Some UEs 120 may be considered customer premises equipment, which may include telecommunications equipment installed at a customer location (such as a home or office) to enable access to a service provider’s network (such as being included in or communicating with the wireless communication network 100).

[0082] Some UEs 120 can be categorized according to different categories associated with varying levels of complexity and / or capabilities. UEs 120 in the first category facilitate large-scale IoT within the wireless communication network 100 and offer lower complexity and / or cost compared to UEs 120 in the second category. UEs 120 in the second category may include, in particular, mission-critical IoT devices, legacy UEs, baseline UEs, high-level UEs, advanced UEs, full-capability UEs, and / or advanced UEs with URLLC, eMBB, and / or precise positioning capabilities within the wireless communication network 100. UEs 120 in the third category may have intermediate-level complexity and / or capabilities (e.g., capabilities between those of UEs 120 in the first category and those of UEs 120 with second-level capabilities). UEs 120 in the third category may be referred to as reduced-capability UEs (“RedCap UEs”), intermediate-level UEs, NR lightweight UEs, and / or NR simplified UEs, etc. RedCap UEs bridge the gap in capabilities and complexity between NB-IoT devices and / or eMTC UEs and mission-critical IoT devices and / or premium UEs. RedCap UE can include, for example, wearable devices, IoT devices, industrial sensors, and / or cameras associated with limited bandwidth, power capacity, and / or transmission range. RedCap UE can support healthcare environments, building automation, power distribution, process automation, transportation and logistics, and / or smart city deployments, among others.

[0083] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly with each other using sidelink communication (e.g., without communicating through a network node 110 acting as an intermediary). As an example, UE 120a can send data, control information, or other signaling directly to UE 120e as sidelink communication. This contrasts with, for example, UE 120a first sending data to network node 110 in UL communication, and then that network node sending data to UE 120e in DL communication. In various examples, UE 120 can send and receive sidelink communication using peer-to-peer (P2P) communication protocols, device-to-device (D2D) communication protocols, vehicle-to-everything (V2X) communication protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, and / or vehicle-to-pedestrian (V2P) protocols), and / or mesh network communication protocols. In some deployments and configurations, network node 110 may schedule and / or allocate resources for sidelink communication between UEs 120 in the wireless communication network 100. In some other deployments and configurations, UE 120 (instead of network node 110) may perform or cooperate with or negotiate with one or more other UEs to perform scheduling operations, resource selection operations, and / or other operations for sidelink communication.

[0084] In various examples, in addition to half-duplex operation, some network nodes and UEs in the wireless communication network 100, including network node 110 and UE 120, can also be configured for full-duplex operation. Network node 110 or UE 120 operating in half-duplex mode can perform only one of transmission or reception during a specific time resource period (such as a specific time slot, symbol, or other time period). Half-duplex operation may involve time division duplex (TDD), where the DL transmission of network node 110 and the UL transmission of UE 120 do not occur in the same time resource (i.e., the transmissions do not overlap in time). In contrast, network node 110 or UE 120 operating in full-duplex mode can transmit and receive communications concurrently (e.g., within the same time resource). By operating in full-duplex mode, network node 110 and / or UE 120 can generally increase the capacity of the network and radio access links. In some examples, full-duplex operation may involve frequency division duplex (FDD), in which network node 110 performs DL transmission in a first frequency band or on a first component carrier, and UE 120 performs transmission in a second frequency band or on a second component carrier, the second frequency band or the second component carrier being different from the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for UE 120 but not for network node 110. For example, UE 120 may simultaneously transmit UL to the first network node 110 and receive DL transmissions from the second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for network node 110 but not for UE 120. For example, network node 110 may simultaneously transmit DL to the first UE 120 and receive UL transmissions from the second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both network node 110 and UE 120.

[0085] In some examples, UE 120 and network node 110 can perform MIMO communication. "MIMO" generally refers to the simultaneous transmission or reception of multiple signals (such as multiple layers or multiple data streams) using the same time and frequency resources. MIMO technology typically utilizes multipath propagation. MIMO can be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO can support simultaneous transmission to multiple receivers, which is called multi-user MIMO (MU-MIMO). Some radio access technologies (RATs) can employ advanced MIMO techniques such as mTRP operation (including redundant transmission or reception on multiple TRPs), reciprocity in the time or frequency domain, single-frequency network (SFN) transmission, or noncoherent joint transmission (NC-JT).

[0086] In some aspects, the UE (e.g., UE 120) may include a communication manager 140. As described elsewhere in this document in more detail, the communication manager 140 may receive RAN configurations for multiple service modules corresponding to multiple services and multiple service-specific UE contexts. When the UE is in an inactive state, the communication manager 140 may send a recovery ID and one or more service indices corresponding to one or more requested services among the multiple services. The communication manager 140 may receive responses indicating one or more valid services among the one or more requested services. The communication manager 140 may send communications associated with a valid service among the one or more valid services. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0087] In some aspects, the first network entity (e.g., core network node 130) may include a communication manager 160. As described elsewhere in this document in more detail, the communication manager 160 may receive a recovery ID associated with a UE context for the UE from the second network entity. The communication manager 160 may send a response associated with the UE context to the second network entity. Additionally or alternatively, the communication manager 160 may perform one or more other operations described herein.

[0088] In some aspects, the first network entity (e.g., network node 110) may include a communication manager 150. As described elsewhere in this document in more detail, the communication manager 150 may receive a recovery ID from the UE. The communication manager 150 may send the recovery ID to a second network entity. The communication manager 150 may receive the UE context associated with the recovery ID. The communication manager 150 may send a response to the UE. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0089] In some aspects, the first network entity (e.g., core network node 130) may include a communication manager 160. As described elsewhere in this document in more detail, the communication manager 160 may receive registration information from a second network entity that stores the UE context. The communication manager 160 may receive a recovery ID associated with the UE context from a third network entity; and send a response associated with the UE context. Additionally or alternatively, the communication manager 160 may perform one or more other operations described herein.

[0090] As indicated above, Figure 1 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The examples described are different.

[0091] Figure 2 This is a diagram illustrating an example network node 110 communicating with example UE 120 in a wireless network.

[0092] like Figure 2 As shown, network node 110 may include a data source 212, a transmit processor 214, a transmit (TX) MIMO processor 216, a set of modems 232 (shown as 232a to 232t, where t≥1), a set of antennas 234 (shown as 234a to 234v, where v≥1), a MIMO detector 236, a receive processor 238, a data sink 239, a controller / processor 240, a memory 242, a communication unit 244, a scheduler 246, and / or a communication manager 150, etc. In some configurations, one or a combination of antennas 234, modems 232, MIMO detectors 236, receive processors 238, transmit processors 214, and / or TX MIMO processors 216 may be included in the transceiver of network node 110. The transceiver may be under the control of and used by one or more processors (such as controller / processor 240), and in some respects, may perform aspects of the methods, procedures and / or operations described herein in conjunction with processor-readable code stored in memory 242. In some respects, network node 110 may include one or more interfaces, communication components and / or other components that facilitate communication with UE 120 or another network node.

[0093] The terms “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. For example, references to “a / the processor,” “a / the controller / processor,” etc. (in the singular) should be understood as referring to a combination of… Figure 2 The processor described refers to any one or more processors, such as a single processor or a combination of multiple different processors. The reference to "one or more processors" should be understood as a combination of references. Figure 2 Any one or more processors described herein. For example, one or more processors of network node 110 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and / or controller / processor 240. Similarly, one or more processors of UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and / or controller / processor 280.

[0094] In some aspects, a single processor can perform all operations described as being performed by one or more processors. In some aspects, a first set of one or more processors can perform a first operation described as being performed by that one or more processors, and a second set of one or more processors can perform a second operation described as being performed by that one or more processors. The first set of processors and the second set of processors can be the same set of processors or can be different sets of processors. The reference to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as those in combination. Figure 2 The memory described. For example, an operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or by different subsets of the one or more memories.

[0095] For downlink communication from network node 110 to UE 120, transmitting processor 214 may receive data (“downlink data”) intended for use by UE 120 (or a set of UEs including UE 120) from data source 212 (such as a data pipeline or data queue). In some examples, transmitting processor 214 may select one or more MCSs for UE 120 based on one or more Channel Quality Indicators (CQIs) received from UE 120. Network node 110 may process the data (e.g., including encoding the data) according to the MCS selected for UE 120 for transmission to UE 120 on the downlink, thereby generating data symbols. Transmitting processor 214 may process system information (e.g., semi-static resource partitioning information (SRPI)) and / or control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and / or control symbols. The transmitting processor 214 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS), or channel state information (CSI) reference signals (CSI-RS)) and / or synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)).

[0096] The TX MIMO processor 216 can perform space processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., TA set of output symbol streams is provided to modem 232. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 232. Each modem 232 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for orthogonal frequency division multiplexing (OFDM)) to obtain an output sample stream. Each modem 232 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream to obtain a time-domain downlink signal. Modems 232a to 232t may transmit the set of downlink signals (e.g., [missing information]) together via a set of corresponding antennas 234. T (One downlink signal).

[0097] Downlink signals may include DCI communication, MAC control element (MAC-CE) communication, RRC communication, downlink reference signals, or another type of downlink communication. Downlink signals may be transmitted on the PDCCH, PDSCH, and / or on another downlink channel. Downlink signals may carry one or more transport blocks (TBs) of data. A TB may be a data unit transmitted via the air interface in the wireless communication network 100. A data stream (e.g., from data source 212) may be encoded into multiple TBs for transmission via the air interface. The number of TBs used to carry data associated with a particular data stream may be associated with a TB size shared by multiple TBs. The TB size may be based on the radio channel conditions of the air interface, the MCS used to encode the data, downlink resources allocated for transmitting data, and / or other parameters, or otherwise associated with them. Generally, a larger TB size allows for a larger amount of data to be transmitted in a single transmission, reducing signaling overhead. However, a larger TB size may be more prone to transmission and / or reception errors than a smaller TB size, but such errors can be mitigated through more robust error correction techniques.

[0098] For uplink communication from UE 120 to network node 110, the uplink signal from UE 120 may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232, shown as DEMOD), detected where applicable by MIMO detector 236 (e.g., receive (Rx) MIMO processor), and / or further processed by receive processor 238 to obtain decoded data and / or control information. Receive processor 238 may provide the decoded data to data sink 239 (which may be a data pipeline, data queue, and / or another type of data sink) and provide the decoded control information to processors such as controller / processor 240.

[0099] Network node 110 may use scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some aspects, scheduler 246 may use DCI to dynamically schedule DL transmissions to and / or UL transmissions from UE 120. In some examples, scheduler 246 may allocate repetitive time-domain and / or frequency-domain resources that UE 120 may use to transmit and / or receive communication using RRC configuration (e.g., semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure configuration grant (CG) for UE 120.

[0100] One or more of the following may be included in the RF chain of network node 110: transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, and / or controller / processor 240. The RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs), and / or other devices for converting analog signals (such as those used for transmission or reception via an air interface) to digital signals (such as those used for processing by one or more processors of network node 110). In some aspects, the RF chain may be a transceiver of network node 110, or may be included in such a transceiver.

[0101] In some examples, network node 110 may use communication unit 244 to communicate with the core network and / or other network nodes. Communication unit 244 may support wired and / or wireless communication protocols and / or connections, such as Ethernet, fiber optic, Common Public Radio Interface (CPRI), and / or wired or wireless backhaul, etc. Network node 110 may use communication unit 244 to send and / or receive data associated with UE 120, or to perform network control signaling, etc. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.

[0102] UE 120 may include a collection of antennas 252 (shown as antennas 252a to 252r, where r ≥ 1), a collection of modems 254 (shown as modems 254a to 254u, where u ≥ 1), a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, a memory 282, and / or a communication manager 140, etc. One or more components of UE 120 may be included in housing 284. In some aspects, one or a combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266 may be included in a transceiver included in UE 120. The transceiver may be under the control of and used by one or more processors (such as controller / processor 280), and in some respects, may perform aspects of the methods, procedures, or operations described herein in conjunction with processor-readable code stored in memory 282. In some respects, UE 120 may include another interface, another communication component, and / or another component that facilitates communication with network node 110 and / or another UE 120.

[0103] For downlink communication from network node 110 to UE 120, the set of antennas 252 can receive downlink communication or signals from network node 110, and can receive the set of downlink signals (e.g., R Each received signal is provided to a set of modems 254. For example, each received signal may be provided to a corresponding demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use the corresponding demodulator component to condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal to obtain an input sample. Each modem 254 may use the corresponding demodulator component to further demodulate or process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 may obtain the received symbols from the set of modems 254, may perform MIMO detection on the received symbols where applicable, and may provide the detected symbols. Receiver processor 258 may process (e.g., decode) the detected symbols, may provide the decoded data for UE 120 to data sink 260 (which may include data pipelines, data queues, and / or applications executed on UE 120), and may provide the decoded control information and system information to controller / processor 280.

[0104] For uplink communication from UE 120 to network node 110, the transmitting processor 264 may receive and process data (“uplink data”) from data source 262 (such as data pipelines, data queues, and / or applications running on UE 120) and control information from controller / processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and / or other types of control information. In some aspects, the receiving processor 258 and / or controller / processor 280 may determine one or more parameters related to the transmission of uplink communication for received signals (such as those received from network node 110 or another UE). One or more parameters may include a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, a Channel Quality Indicator (CQI) parameter, or a Transmit Power Control (TPC) parameter, etc. The control information may include indications of RSRP, RSSI, RSRQ, CQI, TPC, and / or another parameter. Control information can facilitate parameter selection and / or scheduling for UE 120 by network node 110.

[0105] Transmit processor 264 can generate reference symbols for one or more reference signals, such as uplink DMRS, uplink sounding reference signal (SRS), and / or another type of reference signal. Symbols from transmit processor 264 can be pre-decoded by TX MIMO processor 266 (where applicable) and further processed by an assembly of modems 254 (e.g., for DFT-s-OFDM or CP-OFDM). TX MIMO processor 266 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols (where applicable) and can provide an output symbol stream set (e.g., ...) to the assembly of modems 254. U Each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 254. Each modem 254 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 254 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.

[0106] Modems 254a to 254u can transmit uplink signal sets (e.g., via a set of corresponding antennas 252) R One uplink signal or UUplink signals may include UCI communication, MAC-CE communication, RRC communication, or another type of uplink communication. Uplink signals may be transmitted on PUSCH, PUCCH, and / or another type of uplink channel. Uplink signals may carry one or more TBs of data. Sidelink data and control transmission (i.e., transmission directly between two or more UEs 120) may typically use techniques similar to those described for uplink data and control transmission, and may use sidelink-specific channels such as the Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and / or Physical Sidelink Feedback Channel (PSFCH).

[0107] One or more antennas in the set of antennas 252 or the set of antennas 234 may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc., or may be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or with one or more transmitting or receiving components (such as...) Figure 2 An antenna module is a combination of one or more antenna elements coupled to one or more components. As used herein, "antenna" can mean one or more antennas, one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, or one or more antenna arrays. "Antenna panel" can mean a group of antennas (such as antenna elements) arranged in an array or panel that can facilitate beamforming by manipulating the parameters of that group of antennas. "Antenna module" can mean a circuit that includes one or more antennas, and may also include one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device.

[0108] In some examples, each antenna element of antenna 234 or antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element, which can be used to independently transmit cross-polarized signals. Antenna elements may include patch antennas, dipole antennas, and / or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. The spacing between antenna elements can allow signals with a desired wavelength transmitted individually by the antenna elements to interact or interfere (e.g., to form a desired beam) in various directions. For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, half a wavelength, or another fraction of the wavelength between adjacent antenna elements to allow desired constructive and destructive interference modes of signals transmitted by individual antenna elements within that desired range.

[0109] The amplitude and / or phase of signals transmitted via antenna elements and / or sub-elements can be modulated and (e.g., by manipulating phase shifts, phase offsets, and / or amplitudes) shifted relative to each other to generate one or more beams; this is known as beamforming. The term "beam" can refer to the directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. "Beam" can also generally refer to the direction associated with such directional signal transmission, the set of directional resources associated with the signal transmission (e.g., angle of arrival, horizontal direction, and / or vertical direction), and / or a set of parameters indicating one or more aspects of the directional signal, the direction associated with the signal, and / or the set of directional resources associated with the signal. In some implementations, antenna elements can be individually selected or deselected for the directional transmission of a signal (or multiple signals) by controlling the amplitude of one or more corresponding amplifiers and / or the phase of the signal to form one or more beams. The shape of the beam (such as amplitude, width, and / or the presence of sidelobes) and / or the direction of the beam (such as the angle of the beam relative to the surface of the antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and / or amplitudes of multiple signals relative to each other.

[0110] Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or different numbers of antenna elements. As another example, network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or different numbers of antenna elements. Generally speaking, a larger number of antenna elements provides increased control over the parameters used for beamforming compared to a smaller number of antenna elements, while a smaller number of antenna elements may be less complex to implement and can use less power. Multiple antenna elements can support multi-layer transmission, in which the same time and frequency resources are used to utilize spatial multiplexing to transmit a first layer of communication (which may include a first data stream) and a second layer of communication (which may include a second data stream).

[0111] In some respects, the controller / processor 280 may be a component of a processing system. A processing system can typically be a system or a series of machines or components that receive input and process it to produce output (which may be passed to other systems or components, such as UE 120). For example, the processing system of UE 120 may be a system that includes various other components or sub-components of UE 120.

[0112] The processing system of UE 120 can interface with one or more other components of UE 120, and can process information (such as input or signals) received from one or more other components, or can output information to one or more other components. For example, the chip or modem of UE 120 may include: a processing system, a first interface for receiving or acquiring information, and a second interface for outputting, transmitting, or providing information. In some examples, the first interface may be an interface between the processing system of the chip or modem and a receiver, allowing UE 120 to receive information or signal input and to pass information to the processing system. In some examples, the second interface may be an interface between the processing system of the chip or modem and a transmitter, allowing UE 120 to transmit information output from the chip or modem. Those skilled in the art will readily recognize that the second interface may also acquire or receive information or signal input, and the first interface may also output, transmit, or provide information.

[0113] In some respects, the controller / processor 240 may be a component of a processing system. A processing system can typically be a system or a series of machines or components that receive input and process it to produce output (which may be passed to other systems or components, such as network node 110). For example, the processing system of network node 110 may be a system that includes various other components or sub-components of network node 110.

[0114] The processing system of network node 110 can interface with one or more other components of network node 110, and can process information (such as input or signals) received from one or more other components, or can output information to one or more other components. For example, the chip or modem of network node 110 may include: a processing system, a first interface for receiving or acquiring information, and a second interface for outputting, transmitting, or providing information. In some examples, the first interface may be an interface between the processing system of the chip or modem and a receiver, allowing network node 110 to receive information or signal input and to pass information to the processing system. In some examples, the second interface may be an interface between the processing system of the chip or modem and a transmitter, allowing network node 110 to transmit information output from the chip or modem. Those skilled in the art will readily recognize that the second interface may also acquire or receive information or signal input, and the first interface may also output, transmit, or provide information.

[0115] Core network node 130 may include one or more components of network node 110. Core network node 130 can operate in a core network and may include communication unit 294, controller / processor 290, and memory 292. Core network node 130 can communicate with another core network node 130 or network node 110 via communication unit 294.

[0116] Although Figure 2 The boxes in the diagram are illustrated as different components, but the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0117] Figure 3This is an illustration of an example decomposed base station architecture 300 according to the present disclosure. One or more components of the example decomposed base station architecture 300 may be, may include, or may be included in one or more network nodes (such as one or more network nodes 110). The decomposed base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or may communicate indirectly with the core network 320 via one or more decomposed control units (such as non-RT RIC 350 and / or near-RT RIC 370 associated with a Service Management and Orchestration (SMO) framework 360 (e.g., via an E2 link). The CU 310 may communicate with one or more DU 330 via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RU 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UE 120 via a corresponding RF access link. In some deployments, a UE 120 may be served simultaneously by multiple RU 340s.

[0118] Each component in the components of the disassembled base station architecture 300 (including CU 310, DU 330, RU 340, near-RT RIC 370, non-RT RIC 350, and SMO frame 360) may include one or more interfaces or be coupled to one or more interfaces for receiving or transmitting signals, such as data or information, via wired or wireless transmission media.

[0119] In some respects, the CU 310 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be deployed to communicate with one or more DU 330s for network control and signaling, as needed. Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340s. For example, the DU 330 may host various layers, such as the RLC layer, MAC layer, or one or more PHY layers (such as one or more high PHY layers or one or more low PHY layers). Each layer (which may also be referred to as a module) can be implemented using an interface for signaling to other layers (and modules) hosted by the DU 330, or for signaling to control functions hosted by the CU 310. Each RU 340 may implement lower-layer functionality. In some respects, the real-time and non-real-time aspects of communication with the control plane and user plane of the RU 340 can be controlled by the corresponding DU 330.

[0120] The SMO framework 360 supports RAN deployment and provisioning for both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 360 supports the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 360 can interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 350, and / or near-RT RIC 370. In some aspects, the SMO framework 360 can communicate with hardware aspects of the 4G RAN, 5G NR RAN, and / or 6G RAN (such as the Open eNB (O-eNB) 380) via the O1 interface. Additionally or alternatively, the SMO framework 360 can communicate directly with each of one or more RUs 340 via the corresponding O1 interface. In some deployments, this configuration enables each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0121] The non-RT RIC 350 may include or implement logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, and / or policy-based guidance of applications and / or features in the near-RT RIC 370. The non-RT RIC 350 may be coupled to or communicate with the near-RT RIC 370, such as via an A1 interface. The near-RT RIC 370 may include or implement logical functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and actions, connecting one or more CU 310s, one or more DU 330s, and / or O-eNBs to the near-RT RIC 370.

[0122] In some aspects, to generate AI / ML models to be deployed in the near-RT RIC 370, the non-RT RIC 350 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 370 and can be received from non-network data sources or network functions at the SMO framework 360 or the non-RT RIC 350. In some examples, the non-RT RIC 350 or near-RT RIC 370 may modulate RAN behavior or performance. For example, the non-RT RIC 350 may monitor long-term trends and patterns in performance and may employ AI / ML models to perform corrective actions via the SMO framework 360 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0123] Figure 1 , Figure 2 or Figure 3 Network node 110, the controller / processor 240 of network node 110, UE 120, the controller / processor 280 of UE 120, core network node 130, the controller / processor 290 of core network node 130, CU 310, DU 330, RU 340, or any other component may implement one or more technologies associated with handling the UE context or perform one or more operations associated with handling the UE context, as described elsewhere in this document in more detail. For example, Figure 2 The controller / processor 240 of network node 110, the controller / processor 280 of UE 120, the controller / processor 290 of core network node 130, any other component (or combination of components), CU 310, DU 330, or RU 340 may (alone or with one or more other processors) execute or bootstrap, for example, Figure 23 Process 2300 Figure 24 Process 2400 Figure 25 Process 2500 Figure 26The operation of process 2600, or other processes as described herein. Memory 242 may store data and program code for network node 110, CU 310, DU 330, or RU 340. Memory 292 may store data and program code for core network node 130. Memory 282 may store data and program code for UE 120. In some examples, memory 242, memory 292, or memory 282 may include a non-transitory computer-readable medium storing a set of instructions (e.g., code or program code) for wireless communication. Memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). Memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). Memory 292 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). For example, this instruction set can be executed by one or more processors of network node 110, UE 120, core network node 130, CU 310, DU 330, or RU 340 (e.g., directly, or after compilation, transformation, or interpretation). Figure 23 Process 2300 Figure 24 Process 2400 Figure 25 Process 2500 Figure 26 The process 2600, or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions, and / or interpret instructions, etc.

[0124] In some aspects, the UE (e.g., UE 120) may include components for receiving RAN configuration for multiple service modules corresponding to multiple services and multiple service-specific UE contexts; components for transmitting a recovery ID and one or more service indices corresponding to one or more requested services when in an inactive state; components for receiving responses indicating one or more valid services among the one or more requested services; and / or components for transmitting communications associated with a valid service among the one or more valid services. Components for the UE to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0125] In some aspects, the first network entity (e.g., core network node 130) includes components for receiving a recovery ID associated with a UE context for a UE from a second network entity; and / or components for sending a response associated with the UE context to the second network entity. In some aspects, components for the first network entity to perform the operations described herein may include, for example, one or more of a communication manager 160, a controller / processor 290, a memory 292, or a communication unit 294.

[0126] In some aspects, the first network entity (e.g., network node 110) includes components for receiving a recovery ID from the UE; components for sending the recovery ID to a second network entity; components for receiving the UE context associated with the recovery ID; and / or components for sending a response to the UE. In some aspects, components for the first network entity to perform the operations described herein may include, for example, one or more of the following: a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0127] In some aspects, the first network entity (e.g., core network node 130) includes components for receiving registration information from a second network entity storing the UE context; components for receiving a recovery ID associated with the UE context from a third network entity; and / or components for sending a response associated with the UE context. In some aspects, components for the first network entity to perform the operations described herein may include, for example, one or more of a communication manager 160, a controller / processor 290, a memory 292, or a communication unit 294.

[0128] Figure 4 This is a diagram of an example 400 of a core network 405 configured to provide network slicing. (See diagram for example.) Figure 4 As shown, Example 400 may include UE 120, wireless communication network 100, and core network 405. The devices and / or networks of Example 400 may be interconnected via wired connections, wireless connections, or a combination thereof.

[0129] For example, wireless communication network 100 may support cellular RAT. Network 100 may include one or more network nodes, such as base stations (e.g., base transceivers, radio base stations, Node Bs, eNodeBs (eNBs), gNodeBs (gNBs), base station subsystems, cellular sites, cellular towers, access points, TRPs, radio access nodes, macrocell base stations, microcell base stations, picocell base stations, femtocell base stations, or similar devices) and other network nodes that can support wireless communication for UE 120. Network 100 may deliver services between UE 120 (e.g., using a cellular RAT), one or more network nodes (e.g., using a radio interface or backhaul interface, such as a wired backhaul interface) and / or core network 405. Network 100 may provide one or more cells covering a geographic area.

[0130] In some aspects, the wireless communication network 100 can perform scheduling and / or resource management for the UE 120 covered by the network 100 (e.g., UE 120 covered by a cell provided by the network 100). In some aspects, the network 100 can be controlled or coordinated by a network controller, which can perform load balancing and / or network-level configuration, etc., as described above. Figure 1 As described, the network controller can communicate with network 100 via wireless or wired backhaul. In some aspects, network 100 may include a network controller, an ad hoc network (SON) module or component, or a similar module or component. Therefore, network 100 can perform network control, scheduling, and / or network management functions (e.g., for uplink, downlink, and / or sidelink communication of UE 120 covered by network 100).

[0131] In some aspects, core network 405 may include example functional architectures in which the systems and / or methods described herein can be implemented. For example, core network 405 may include example architectures of 5G next-generation (NG) core networks included in fifth-generation (5G) wireless telecommunications systems. Although Figure 4 The example architecture of the core network 405 shown can be an example of a service-based architecture, but in some respects, the core network 405 can be implemented as a reference point architecture and / or a 4G core network, etc.

[0132] like Figure 4As shown, the core network 405 may include multiple functional elements. These functional elements may include, for example, a network slice selection function (NSSF) 410, a network open function (NEF) 415, an authentication server function (AUSF) 420, a unified data management (UDM) component 425, a policy control function (PCF) 430, an application function (AF) 435, an access and mobility management function (AMF) 440, a session management function (SMF) 445, and / or a user plane function (UPF) 450, etc. These functional elements may be communicatively connected via a message bus 455. Figure 4 Each of the functional elements shown can be implemented on one or more devices associated with a wireless telecommunications system. In some implementations, one or more of these functional elements can be implemented on physical devices such as access points, base stations, and / or gateways. In some implementations, one or more of these functional elements can be implemented on computing devices in a cloud computing environment.

[0133] NSSF 410 may include one or more devices for selecting network slice instances for UE 120. A network slice is a network architecture model in which logically distinct network slices operate using a common network infrastructure. For example, several network slices may operate as isolated end-to-end networks customized to meet different target service standards for different types of applications and / or communications to and from UE 120, which are at least partially performed by UE 120. Network slicing efficiently provides communication for different types of services with different service standards.

[0134] The NSSF 410 determines a set of network slicing policies to be applied at the wireless communication network 100. For example, the NSSF 410 can apply one or more UE routing policy (URSP) rules. In some aspects, the NSSF 410 can select network slices based on a mapping from the Data Network Name (DNN) field included in the Routing Description (RSD) to the DNN field included in the Service Descriptor selected by the UE 120. By providing network slices, the NSSF 410 allows operators to potentially deploy multiple substantially independent end-to-end networks over the same infrastructure. In some implementations, each slice can be customized for a different service.

[0135] NEF 415 may include one or more devices that support the opening of capabilities and / or events in a wireless telecommunications system to help other entities in the wireless telecommunications system discover network services. AUSF 420 may include one or more devices that act as an authentication server and support the process of authenticating UE 120 in a wireless telecommunications system.

[0136] The UDM 425 may include one or more devices for storing user data and profiles in a wireless telecommunications system. In some respects, the UDM 425 may be used for fixed access and / or mobile access, etc., in the core network 405.

[0137] PCF 430 may include one or more devices that provide a policy framework that incorporates network slicing, roaming, packet processing, and / or mobility management, among other things. In some aspects, PCF 430 may include one or more URSP rules used by NSSF 410 to select network slice instances for UE 120.

[0138] AF 435 may include one or more devices that support the impact of applications on service routing, access to NEF 415, and / or policy control, etc. AMF 440 may include one or more devices that act as an endpoint for NAS signaling and / or mobility management, etc. In some aspects, AMF may request NSSF 410 to select a network slice instance for UE 120, for example, at least in part in response to a request for data services from UE 120.

[0139] The SMF 445 may include one or more devices that support the establishment, modification, and release of communication sessions in a wireless telecommunications system. For example, the SMF 445 may configure service bootstrapping policies at the UPF 450 and / or enforce UE Internet Protocol (IP) address allocation and policies, etc. In some respects, the SMF 445 may supply the UE 120 with network slice instances selected by the NSSF 410.

[0140] UPF 450 may include one or more devices that act as anchors for mobility within and / or between RATs. In some respects, UPF 450 may apply rules to packets, particularly rules relating to packet routing, traffic reporting, and / or handling of user plane quality of service (QoS).

[0141] The message bus 455 can be a logical communication structure and / or a physical communication structure for communication between functional elements. Therefore, the message bus 455 can allow communication between two or more functional elements, whether logically (e.g., using one or more application programming interfaces (APIs) and / or physically (e.g., using one or more wired and / or wireless connections).

[0142] Figure 4 The number and arrangement of devices and networks shown are provided as an example. In practice, there may be different arrangements. Figure 4 The devices and / or networks shown are compared to additional devices and / or networks, fewer devices and / or networks, different devices and / or networks, or devices and / or networks arranged in a different manner. Furthermore, Figure 4 The two or more devices shown can be implemented within a single device, or Figure 4 The single device shown can be implemented as multiple distributed devices. Additionally or alternatively, the set of devices in Example 400 (e.g., one or more devices) can perform one or more functions described as being performed by another set of devices in Example Environment 400.

[0143] Although Figure 4 The elements described are those of 5G networks, but such elements may be included in 6G networks and subsequent networks.

[0144] As indicated above, Figure 4 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 4 The examples described are different.

[0145] Figure 5 This is a diagram illustrating example 500 of network node 110 and the user plane protocol stack and control plane protocol stack of the core network used for communication with UE 120.

[0146] In some aspects, network node 110 may include multiple network nodes 110. In some aspects, the protocol stack functionality of network node 110 may be distributed across multiple network nodes 110. For example, a first network node 110 may implement a first layer of the protocol stack, and a second network node 110 may implement a second layer of the protocol stack. The distribution of the protocol stack across network nodes (in this example of the distribution of the protocol stack across network nodes) may be based at least in part on functional partitioning, as described elsewhere herein. It should be understood that, in some aspects, references to “network node 110” or “the network node 110” may refer to multiple network nodes.

[0147] On the user plane, UE 120 and network node 110 may include corresponding PHY, MAC, RLC, PDCP, and SDAP layers. User plane functions handle the transmission of user data between UE 120 and network node 110. On the control plane, UE 120 and network node 110 may include corresponding RRC layers. Additionally, UE 120 may include a NAS layer that communicates with the AMF's NAS layer. The AMF may be associated with the core network associated with network node 110, such as a 5G core network (5GC), a 6G core network, or NG-RAN. Control plane functions handle the transmission of control information between the UE and the core network. Generally, if the first layer is further from the PHY layer than the second layer, the first layer is referred to as being higher than the second layer. For example, the PHY layer may be referred to as the lowest layer, and the SDAP / PDCP / RLC / MAC layers may be referred to as being higher than the PHY layer and lower than the RRC layer. Figure 5The Application (APP) layer, not shown, may be higher than the SDAP / PDCP / RLC / MAC layers. In some cases, an entity may handle the services and functions of a given layer (e.g., a PDCP entity may handle the services and functions of the PDCP layer), although the description herein mentions that the layer itself handles these services and functions.

[0148] The RRC layer handles communications related to the configuration and operation of UE 120, such as: broadcasting system information related to the Access Layer (AS) and NAS; paging initiated by 5GC or NG-RAN; establishment, maintenance, and release of RRC connections between the UE and NG-RAN, including the addition, modification, and release of carrier aggregation, as well as the addition, modification, and release of dual connections; security functions, including key management; establishment, configuration, maintenance, and release of Signaling Radio Bearers (SRBs) and Data Radio Bearers (DRBs); mobility functions (e.g., handover and context passing, UE cell selection and reselection and control of cell selection and reselection, inter-RAT mobility); QoS management functions; UE measurement reporting and control of reports; detection and recovery from radio link failures; and NAS messaging between the NAS layer and the lower layers of UE 120. The RRC layer is often referred to as Layer 3 (L3).

[0149] The SDAP, PDCP, RLC, and MAC layers can be collectively referred to as Layer 2 (L2). Therefore, in some cases, the SDAP, PDCP, RLC, and MAC layers are referred to as sublayers of Layer 2. On the transmitting side (e.g., if UE 120 is transmitting uplink communication or network node 110 is transmitting downlink communication), the SDAP layer can receive data streams in the form of QoS streams. A QoS stream is associated with a QoS identifier and a QoS stream identifier (QFI), the QoS identifier identifying the QoS parameters associated with the QoS stream and the QoS stream identifier (QFI) identifying the QoS stream. Policies and charging parameters are implemented according to the QoS stream granularity. A QoS stream may include one or more Service Data Streams (SDFs), provided that each SDF of the QoS stream is associated with the same policies and charging parameters. In some aspects, the RRC / NAS layer can generate control information to be transmitted and can map this control information to one or more radio bearers for provision to the PDCP layer.

[0150] The SDAP or RRC / NAS layer can map QoS flows or control information to radio bearers. Therefore, it can be said that the SDAP layer handles QoS flows on the transmitting side. The SDAP layer can provide QoS flows to the PDCP layer via the corresponding radio bearer. The PDCP layer can map radio bearers to RLC channels. The PDCP layer handles various services and functions on the user plane, including sequence numbering, header compression and decompression (if robust header compression is enabled), delivery of user data, reordering and copy detection (if in-order delivery to layers above the PDCP layer is required), PDCP Protocol Data Unit (PDU) routing (in the case of split bearers), retransmission, encryption and decryption of PDCP Service Data Units (SDUs), PDCP SDU discarding (e.g., according to timers, as described elsewhere in this document), PDCP reconstruction and data recovery for RLC Acknowledgment Mode (AM), and PDCP PDU copying. The PDCP layer handles similar services and functions on the control plane, including sequence numbering, encryption, decryption, integrity protection, delivery of control plane data, copy detection, and PDCP PDU copying.

[0151] The PDCP layer can provide data in the form of PDCP PDUs to the RLC layer via the RLC channel. The RLC layer can handle the transmission of upper-layer PDUs to the MAC and / or PHY layers, sequence numbering independent of PDCP sequence numbering, error correction via Automatic Repeat Request (ARQ), segmentation and resegmentation, SDU reassembly, RLC SDU discarding, and RLC reconstruction.

[0152] The RLC layer can provide the MAC layer with data mapped to logical channels. The services and functions of the MAC layer include mapping between logical channels and transport channels (used by the PHY layer as described below), multiplexing MACSDUs belonging to one or different logical channels into / from a transport block (TB) delivered to / from the physical layer on the transport channel, scheduling information reporting, error correction via Hybrid ARQ (HARQ), priority handling between UEs via dynamic scheduling, priority handling between logical channels of a UE via logical channel prioritization, and padding.

[0153] The MAC layer can encapsulate data from logical channels into data blocks (TBs) and can provide TBs to the PHY layer on one or more transport channels. The PHY layer can handle various operations related to the transmission of data signals, such as combining... Figure 2 In more detail, the PHY layer is often referred to as layer 1 (L1).

[0154] On the receiving side (e.g., if UE 120 is receiving downlink communication or network node 110 is receiving uplink communication), the operation can be similar to that described for the transmitting side, but in the reverse direction. For example, the PHY layer can receive the transport layer (TB) and provide the TB to the MAC layer on one or more transport channels. The MAC layer can map the transport channels to logical channels and provide data to the RLC layer via the logical channels. The RLC layer can map the logical channels to RLC channels and provide data to the PDCP layer via the RLC channels. The PDCP layer can map the RLC channels to radio bearers and provide data to the SDAP layer or RRC / NAS layer via the radio bearers.

[0155] Data can be transferred between layers in the form of PDUs and SDUs. An SDU is a data unit that has been passed from a layer or sublayer to the next layer. For example, the PDCP layer can receive PDCP SDUs. A given layer can then encapsulate the data unit into a PDU and pass the PDU to the next layer. For example, the PDCP layer can encapsulate a PDCP SDU into a PDCP PDU and pass the PDCP PDU to the RLC layer. The RLC layer can receive the PDCP PDU as an RLC SDU, encapsulate the RLC SDU into an RLC PDU, and so on. In effect, the PDU carries the SDU as a payload.

[0156] As indicated above, Figure 5 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 5 The examples described are different.

[0157] Figure 6 This is a diagram illustrating example 600 of the design model.

[0158] In the early days of the Internet, data networks were configured to provide numerous services through heterogeneous devices. One design principle illustrated by data network model 602 includes a layered system architecture with simple service interfaces across many applications and transports. Data network model 602, with an IP layer in the middle that allows routing protocols to be placed on top of any type of interface, resembles an hourglass. Different transport or service types can operate on this interface.

[0159] With the advent of cellular radio networks (such as 3G and 4G), the hourglass aspect of the data network model 602, as shown in cellular network model 604, was adopted. With the introduction of smartphones, 4G successfully provided many services. The 4G protocol stack was designed to support the same model as the Internet but used for cellular radio networks. This involves a control plane separate from the user plane to manage data transmission for cellular needs such as mobility. The separate control and user plane protocol stacks continue the architecture defined for 3G.

[0160] With the expansion of 4G, new capabilities are being introduced to extend the capabilities of communication systems to new use cases and device types. This includes horizontal expansion (carrier aggregation (CA), dual connectivity (DC), etc.) and vertical expansion (IoT, V2X, etc.). The success of 4G has helped to activate expectations for 5G vertical industries. Additionally, services are being introduced as part of the NAS / RRC protocol stack. NAS protocol services include location. RRC protocol services include data collection, such as Minimum Drive Test (MDT). In addition to data transmission and connectivity, additional services provided by NAS and / or RRC include positioning, sensing, timing, AI / ML, etc. The adoption of such NAS / RRC services is limited. Deploying new services without upgrading the underlying protocols is not feasible. Adding services through the control plane is not as straightforward as enabling new services via IP.

[0161] As indicated above, Figure 6 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 6 The examples described are different.

[0162] Figure 7 This is a diagram illustrating Example 700 of a 5G design.

[0163] Example 700 shows a 5G network model 702 that can be deployed standalone or non-standalone, involving 4G. However, the 5G NAS / RRC protocol stack can be even more singular than in 4G. NAS / RRC continues to evolve to support even more features, such as industrial IoT, satellite, etc. Service revenue has been concentrated on the user plane due to continued support for legacy services from the 4G era. History further suggests that the adoption of control plane services is limited. Differentiated services built on network slices already exist as potential features driving 5G standalone deployments. Policy and billing functions allow new revenue streams beyond data consumption.

[0164] The challenge lies in enabling services to be deployed independently while using existing protocols and allowing UEs to directly address services without relying on intermediate network functions (e.g., NAS signaling, RRC signaling). Furthermore, as we move towards 6G, defining new data collection, location, or other protocols in 6G and subsequent generations may not be optimal.

[0165] As indicated above, Figure 7 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 7 The examples described are different.

[0166] Figure 8 This is a diagram illustrating the new design of the network, example 800. (See diagram for example.) Figure 8As shown, network entity 810 (e.g., network node 110) and UE 820 (e.g., UE 120) can communicate with each other via a wireless network (e.g., including elements of wireless communication network 100). This network can be a 5G network, a 6G network, a next-generation network, or a combination of such networks.

[0167] In some aspects, new network designs may involve abandoning the definition of generation-specific control planes for each generation and enabling an hourglass model on the control plane. This could include defining the content hosted in the control plane in a user plane-first manner. A thinner control plane for 6G could make control plane services available in 5G and other RATs. Control plane services, including location and data collection, can be made available via the user plane (e.g., based on address requests) and can become generation-independent using standardized APIs. Service addresses and services performed via the user plane could include data sessions, PDU sessions, sensing services, location services, policy services, UE device management, and / or policy downloads on the UE.

[0168] The new design leverages the scale of internet services and protocols to enable many potential vendors, rather than the limited number of infrastructure providers available today, to offer such services. The new design may include simplified methods for enabling remaining services via NAS and RRC. The control plane is not generation-specific and can simply define NAS and RRC as the transport layer for services. Services can be decoupled from transport. For example, service interfaces can be enabled so that connectivity, session management, and other services are built on top of NAS and RRC rather than incorporated into the NAS protocol.

[0169] In some respects, the NAS layer can be common across services. The NAS layer can provide service discovery, routing, and late binding. The transport layer can be at the service entry point. The same transport layer can be used for both the user plane and control plane; from a protocol perspective, there is no difference. Services can be distinguished via service IDs. Reliability and security can be implemented at the transport / service layer or relocated according to service requirements. The microservices behind the service entry point can be transparent to other parts of the system, such as the UE. In some respects, the UE can use the service ID, NAS ID, paging ID, and / or RAN ID. The UE can use such IDs to directly address services through the user plane. The NAS / RRC layer can be used for authentication, some mobility services, and for setting up the user plane.

[0170] By using NAS protocols and RRC signaling as a transport / service layer operating on the user plane for setting up services, the adoption of services on the network can be scaled and new revenue streams can be created, while limiting the redefinition of the control plane with future generations.

[0171] Example 800 shows an example of a UE 820 requesting services via the user plane. At 825, network entity 810 and UE 820 may configure the control plane (e.g., NAS protocol, RRC signaling) for services via the user plane. This may include configuring the NAS / RRC layer to operate as transports for services that may have been handled by the control plane in earlier network scenarios. The control plane configuration may involve authenticating the UE 820 requesting the service.

[0172] In some respects, at 830, UE 820 may select to request services using either the user plane or the control plane, at least in part, based on the network type. For example, if the network is 6G, UE 820 may select the user plane, or if the network is 5G, the UE may select the control plane. The selection between the user plane and the control plane may be based on the G of the network connection (6G+ versus 3G / 4G / 5G). The selection between the user plane and the control plane may be based at least in part on the service or service type. The selection between the user plane and the control plane may be based at least in part on UE configuration, user preferences, or service availability. The service may be a service type that is typically handled by the control plane, such as MDT or managed QoS. In the example, if the service is for managed QoS, UE 820 may select the control plane. The service may be a service type using signaling radio bearers (SRBs) in 5G. The service protocol may be unaffected by whether the transport is via the control plane or the user plane.

[0173] In some respects, the control plane can be a thinner control plane that provides fewer services, and those services are provided on the user plane. That is, some services on the control plane can be replaced by services on the user plane. Compared to the control plane used for 5G, the thinner control plane used for 6G can have fewer protocols or signaling.

[0174] At 835, if UE 820 selects the user plane, UE 820 may send a request for services via the user plane. This may include addressing services using user plane addresses. This may include using the service ID, RAN ID, and / or NAS ID. At 840, UE 820 may perform services via the user plane.

[0175] In some respects, UE 820 can use specific PDU sessions and / or dedicated physical resource blocks (PRBs) that provide higher priority on the user plane to prevent latency increases beyond those expected on the control plane.

[0176] As indicated above, Figure 8 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 8 The descriptions are different.

[0177] Figure 9 This is a diagram illustrating an example 900 of the NR system architecture according to this disclosure.

[0178] Example 900 illustrates an NR architecture for 5G. The NR architecture may include network functions in RAN 902 and core network 904. RAN 902 may perform RAN paging or mobility functions. Core network 904 may include an AMF that provides functionality to the UE using NAS protocols. These functions may include: mobility; paging; identity; access, authorization, and registration; connectivity management; selection and transport; slicing; and security termination. Application services through the control plane may include SMF services (e.g., QoS, slicing), PCF services, AUSF services, location services, and sensing services. Each of these services has no interdependence with the AMF. That is, all core network functions depend on the AMF. Furthermore, the mobility management layer is involved in slice management (which is a service concept) and is therefore an inefficient division of network functionality. There is also duplicate functionality in the RAN and core network. All such services in the control plane involve single-vendor deployments, which are difficult to scale beyond the first version.

[0179] Additionally, there is only one control plane path between RAN 902 and core network 904. This forces the architecture to add functionality that is practically unrelated to access and mobility management to the AMF. This single control plane path also establishes interdependence between the AMF and RAN 902. The single set of protocols (e.g., NAS protocol, RRC protocol) at the centrally controlled control plane (e.g., CU-CP, AMF) makes network design less flexible in adding new features.

[0180] As indicated above, Figure 9 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 9 The examples described are different.

[0181] Figure 10 This is a diagram illustrating Example 1000 of a network design according to this disclosure.

[0182] In some aspects, the new network design can move away from a single set of protocols with centralized control. This can include providing separate, modular control plane services that can be requested individually, such as authentication and security services, subscription services, and policy services. Any update to a single service does not require an update to the entire control plane. For example, a UE can send a message with an indication of a service (provided via the control plane) and its UE ID to a RAN network entity. This message may include a control plane transport header on the control plane transport layer, which is used to forward the message to the address of the service. The RAN network entity can determine the address mapped to the service and forward the message to that address. The service entity at that address can send a configuration for the service, which is forwarded to the UE. The UE can then use the service via the control plane. In some aspects, the core network can provide a discovery and selection service for locating addresses for services.

[0183] By using individually addressable services on the control plane, the UE and core network can deploy services and features with greater flexibility. The core network can support more distributed functionalities, where the UE can communicate directly with each functionality (service). The UE can communicate with any service via the control plane, where control plane transports are common to and independent of the control plane service. The UE can discover service addresses, while the network hides the network topology. New or enhanced services can be added later without affecting control plane transports at the RAN or intermediate nodes. Therefore, updates to the control plane can be faster and involve less service disruption. This also improves the adoption of services on the network and creates new revenue streams while limiting future redefinitions of the control plane.

[0184] Example 1000 shows an example network design with an end-to-end system architecture for future generations, such as 6G. The network design shows a modular control plane protocol with a cloud-native service-based architecture. A streamlined, service-based control plane 1002 provides separate access services 1006, 1008, and 1010, typically provided by the AMF. Some services, such as device management, location, sensing, and data services, can be provided via either the control plane 1002 or the user plane 1004.

[0185] The new design can involve modularity and RAN / core network convergence. Network functionality can be modularized into self-contained service modules. RAN and core network functionality can be converged. NAS protocols and UE contexts can be modularized. A more streamlined control plane can focus on access, connectivity, mobility, and data services. Non-connectivity services can be moved to the user plane.

[0186] This new design allows for functional partitioning of networks both between and within suppliers. It enables faster and easier adoption of new vertical industries. Furthermore, it allows for forward compatibility of evolving and new features with minimal network impact.

[0187] As indicated above, Figure 10 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 10 The examples described are different.

[0188] Figure 11 This is a diagram illustrating example 1100 of a control plane service according to this disclosure.

[0189] Example 1100 shows that dedicated services can be addressed via service IDs. Control plane services may include, for example, subscriptions, policies, authentication and security, discovery and selection, and NEF. Control plane services may also include different Access and Mobility Services (AMS) for specific types of devices (e.g., RedCap. IoT, smartphones). Different vendors may offer specialized solutions. In some respects, such dedicated AMS services may each be identified by a service ID. For example, AMS service 1102 may be identified by service ID 1, and AMS service 1104 may be identified by service ID 2.

[0190] User plane services may include dedicated data services, each identified by a service ID. Each UE may have multiple data service slices (DSS). DSSs can interact directly with the UE and DU (e.g., eDU). DSSs can interact with AMS (e.g., for mobility areas, paging). DSSs can interact with authentication and security services to derive their own security context. DSS 1106 can be identified by service ID 3, and DSS 1108 can be identified by service ID 4.

[0191] As indicated above, Figure 11 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 11 The examples described are different.

[0192] Figure 12 This is a diagram illustrating example 1200 of a service-based architecture according to this disclosure.

[0193] In some respects, UE 1202 can use Control Plane Transport 1208 signaling Control Plane Service 1206 in an end-to-end control plane signaling solution. Control plane Transport 1208 can be a common transport for all services. RAN 1204 can involve only routing without a deep understanding of which service UE 1202 is communicating with. End-to-end security can be service-independent (supporting the zero-trust paradigm).

[0194] In some respects, one or more control plane transport APIs may exist between RAN 1204 and control plane service 1206. The APIs may utilize service-based interfaces (SBIs). Control plane service 1206 may use configuration APIs to request specific RAN configurations. The RAN may aggregate requests for different services and may accept, modify, or reject requests.

[0195] UE 1202 can use control plane transport 1208 to request and receive service configurations. The configuration can be local. The configuration can be service-specific (e.g., a logical channel corresponding to a QoS flow) or service-independent configuration inherent to eDU-UE connection operation and common to all services.

[0196] As indicated above, Figure 12 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 12 The examples described are different.

[0197] Figure 13 This is a diagram illustrating Example 1300 of UE state management according to this disclosure.

[0198] UE state management in 5G can involve relatively strict and centralized state management managed by CU-CP and AMF. Possible UE states may include, for example, RRC / CN CONNECTED, RRC INACTIVE / CN CONNECTED, and RRC / CN IDLE. UE state management in 6G can be more service-centric. That is, states can be managed according to services, and states can be active or inactive.

[0199] Example 1300 illustrates different scenarios involving UE states for network services (NS) (such as NS-1 and NS-2). The UE state in the RAN can be disconnected (no UE RAN connection), where the UE RAN context can be stored in both the UE and the RAN. The UE state in the RAN can be connected, where there is an active RAN connection with network entities in the RAN (e.g., eDU-1, eDU-2).

[0200] UE state can be per-service. State can be maintained independently for each service. Some services may be interdependent. A service's UE state may have no context (equivalent to the UE not registering for the service). A service's UE state can be active, where the context exists in the UE, the service, and possibly the eDU. A service's UE state can be inactive, where the context exists in the UE or the service, but the service may not be aware of the service eDU.

[0201] In scenario 1302, the UE can be idle (not connected) and there is no UE context stored for NS-1 or NS-2. In scenario 1304, the UE can be connected to eDU-1. NS-1 can be active, and NS-2 may be stateless. The UE context for NS-1 is stored at the UE. In scenario 1306, the UE is connected to eDU-1, NS-1 is active, and NS-2 is active. The UE contexts for NS-1 and NS-2 are stored at the UE and eDU-1, respectively. In scenario 1308, the UE is inactive, NS-1 is inactive, and NS-2 is inactive. The UE contexts for NS-1 and NS-2 are stored at the UE. In scenario 1310, the UE is connected to eDU-1, NS-1 is active, and NS-2 is inactive. The UE context for NS-1 is stored at the UE and eDU-1, respectively. In scenario 1312, the UE is connected to both eDU-1 and eDU-2, NS-1 is active, and NS-2 is active. The UE context of NS-1 is stored at eDU-1, and the UE context of NS-2 is stored at eDU-2.

[0202] As indicated above, Figure 13 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 13 The examples described are different.

[0203] Figure 14 This is a diagram illustrating Example 1400 of UE context management according to this disclosure.

[0204] In 5G, the UE RAN context may have limited reusability. The UE RAN context may include the UE context used by the RAN node (e.g., eNB). The UE context may be an information block associated with the active UE in the RAN node. This information block includes information that is expected to be stored to maintain network services for the active UE. The UE context may include at least UE state information, security information, UE capability information, and an identifier of the logical S1 connection associated with the UE. The UE context is established when the transition to the active state of the UE is complete, or when the UE context is in the target network entity after handover resource allocation is completed during handover preparation. The UE context may be local. The UE context may be suspended or resumed as a whole.

[0205] In 5G, there is a hard dependency between the RAN and CN regarding UE contexts. A UE context in the CN and a UE context in the RAN are treated as a single UE context. This limits the area where UE contexts can be stored and reused. For example, a target eDU may be located at a certain distance from the source eDU. If the UE context used in the source eDU cannot be stored or retrieved in the target eDU, the UE context needs to be re-established, which increases latency.

[0206] In some respects, UE contexts can be modularized in 6G networks. Modularization in 6G CN can translate into more modular UE context management. Each service can anticipate service-specific RAN configurations. For example, a security service might request access layer (AS) security, or a data service might anticipate specific QoS flows or DRBs. Depending on the specific service state and requirements, service-specific RAN configurations and service-specific UE contexts can be disposed of as self-contained modules.

[0207] Example 1400 illustrates an example of UE context management, where a service-specific UE context can be used in CN 1402 or stored in RAN 1404. Non-service-specific UE contexts can also be stored in RAN 1404. In Example 1400, Service 1 becomes inactive (e.g., a data service becomes inactive after a certain period of no data). RAN 1404 can make the Service 1 UE context inactive, maintain the Service 1 UE context, and quickly restore the UE context module used for the Service 1 UE context when Service 1 becomes active again.

[0208] As indicated above, Figure 14 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 14 The examples described are different.

[0209] Figure 15 This is a diagram illustrating Example 1500 of a UE reconnecting according to this disclosure.

[0210] Example 1500 shows UE 1502, connected to eDU 1504 as part of the eDU's connectivity management mechanism, becoming inactive and subsequently reconnecting to eDU 1504. UE 1502 connected to eDU 1504 can receive a RAN connection release message with an identifier (shown at 1506). UE 1502 can become inactive. eDU 1504 can maintain the UE context.

[0211] When UE 1502 becomes active, UE 1504 can send a RAN recovery message with an identifier to eDU 1504 (shown at 1508) and receive a RAN recovery acceptance message (shown at 1510). UE 1502 can then reconnect.

[0212] eDU 1504 can instruct UE 1502 to retain UE 1502's UE context. The UE context may include or correspond to the eDU local access configuration. If UE 1502 reconnects within the same eDU 1504, UE 1502 can reuse its UE context without requiring AS Security Mode Command (SMC) and RB reconfiguration. However, the UE context remains limited to the coverage area of ​​eDU 1504.

[0213] As indicated above, Figure 15 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 15 The examples described are different.

[0214] Figure 16 This is a diagram illustrating Example 1600 of UE context management according to this disclosure.

[0215] 6G networks (or later) can be designed to allow UE context to be reused in larger areas than 5G allows (e.g., in larger registration areas). 6G networks can leverage service-based architectures (cloud solutions) to enable UE context retrieval via inter-eDU mechanisms, regardless of where the UE reconnects, even with greater distances between eDUs. UE RAN context can be modular and reflect service state.

[0216] Based on the various aspects described herein, 6G networks can utilize a UE context storage mechanism, enabling the UE context to be stored and retrieved over a larger geographical area. When a UE connects to a target eDU, the UE context becomes available to the target eDU. For example, a 6G network may include a discovery entity (e.g., a network entity in a CN) that has information about where the UE context for the UE can be obtained (e.g., in a source eDU or RCS entity). The UE can send a recovery ID to the target eDU. The target eDU can then send the UE's recovery ID to the discovery entity pointing to the source eDU or RCS. The target eDU can then retrieve the UE context from the source eDU or RCS. In this way, the UE context for the UE can be retrieved over a larger geographical area. The UE context does not need to be re-established by the target eDU, which reduces latency.

[0217] In some respects, UE contexts can be disposed using RAN context modules, where each RAN context module can be active or inactive depending on the UE's needs. For example, when a UE connects to a target eDU only for service 1 and not service 2, the UE RAN context module for service 1 is active in the RAN, while the UE RAN context module for service 2 is not active (i.e., persistently inactive), although stored and maintained in the RAN. By modularizing service-specific UE contexts, a single UE context does not need to have information for all services, or each service does not require the same UE context. This provides more service-based UE context disposal, offering greater flexibility. With this flexibility, UE contexts can be smaller and more resource-efficient.

[0218] In Example 1600, a network (e.g., wireless communication network 100) may use discovery entity 1630 (e.g., network node 110, core network node 130) for UE context management. Discovery entity 1630 may store information related to the eDU (e.g., identifier, Internet Protocol (IP) address) and a recovery ID associated with the eDU. The recovery ID can be used to identify which eDU stores the UE context 1602 of UE 1610 (e.g., UE 120). UE context 1602 may include the local access configuration of UE 1610 (e.g., RB configuration, security context).

[0219] UE 1610 can be connected to a source eDU 1620 (e.g., network node 110). eDU 1620 can store the UE context 1602 of UE 1610. UE 1610 can also be connected to a target eDU 1625 (e.g., network node 110). Any eDU can communicate with discovery entity 1630. Discovery entity 1630 can be accessed by multiple eDUs over a large geographic area.

[0220] In some respects, eDU 1620 can register with discovery entity 1630. As shown by reference numeral 1632, eDU 1620 can send a registration message to discovery entity 1630 containing eDU information of eDU 1620 and one or more recovery IDs that can be used to look up the UE context in eDU 1620. The registration message can be sent using an application design interface (API). As shown by reference numeral 1634, eDU 1620 can receive registration acceptance messages.

[0221] UE 1610 can be connected to eDU 1620. For some reason, UE 1610 will become inactive. As shown by reference numeral 1636, UE 1610 can receive a RAN connection release message with recovery ID 1604 from eDU 1620. The recovery ID may be associated with retrieving the UE context. The recovery ID may include identification information associated with retrieving the UE context. Recovery ID 1604 may include a portion unique to eDU 1620. UE 1610 may then become inactive. eDU 1620 may maintain (store) UE context 1602 of UE 1610.

[0222] UE 1610 can reconnect to an eDU, such as to a target eDU 1625. As shown by reference numeral 1638, UE 1610 can send a RAN recovery request message with recovery ID 1604 to eDU 1625. As shown by reference numeral 1640, eDU 1625 can send a discovery message with recovery ID 1604 to discovery entity 1630. As shown by reference numeral 1642, discovery entity 1630 can send a response message with eDU information to eDU 1625. The eDU information can identify the eDU 1620 to which UE 1610 last connected. As shown by reference numeral 1644, eDU 1625 can send a UE context retrieval message with recovery ID 1604 to eDU 1620. As shown by reference numeral 1646, eDU 1620 can send a UE context response message with UE context 1602 to eDU 1625. As shown by reference numeral 1648 in the attached figure, eDU 1625 can send a RAN recovery accept message to UE 1610. UE 1610 and eDU 1625 can reuse their previous RAN configurations. The UE now connects to eDU 1625, where eDU 1625 is able to use UE context 1602 for connection with UE 1610.

[0223] As indicated above, Figure 16 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 16 The examples described are different.

[0224] Figure 17 This is a diagram illustrating Example 1700 of UE context management according to this disclosure.

[0225] In some respects, eDU 1625 can export eDU information of eDU 1620 without using a discovery entity. As shown by reference numeral 1702, eDU 1625 can export eDU 1620. eDU 1625 can export information of eDU 1620 using Operation, Administration and Maintenance (OAM) information. eDU 1625 can export information of eDU 1620 using the eDU ID in the Recovery ID. eDU 1625 can export information of eDU 1620 using previously cached information.

[0226] As indicated above, Figure 17 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 17 The examples described are different.

[0227] Figure 18 This is an illustration of Example 1800 of UE context management according to this disclosure.

[0228] In some respects, eDU 1620 and eDU 1625 can communicate with RCS 1810 (e.g., network node 110, core network node 130). RCS 1810 can store UE context and can be accessed by multiple eDUs over a large geographic area. Multiple eDUs can store the UE context with a recovery ID at RCS 1810. As shown by reference numeral 1812, eDU 1620 can send a storage message with the UE context and associated recovery ID to RCS 1810. As shown by reference numeral 1814, RCS 1810 can send a storage accept message to eDU 1620. UE 1610 can be connected to eDU 1620.

[0229] UE 1610 can become inactive. As shown by reference numeral 1816, eDU 1620 can send a RAN release message with a recovery ID to UE 1610. UE 1610 can also become inactive. As shown by reference numeral 1818, UE 1610 can send a RAN recovery request message with a recovery ID to eDU 1625. As shown by reference numeral 1820, eDU 1625 can send a UE context retrieval message with a recovery ID to RCS 1810. As shown by reference numeral 1822, RCS 1810 can send a UE context response message with the UE context to eDU 1625. As shown by reference numeral 1824, eDU 1625 can send a RAN recovery accept message to UE 1610. UE 1610 is now connected to eDU 1625.

[0230] As indicated above, Figure 18 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 18The examples described are different.

[0231] Figure 19 This is an illustration of Example 1900 of UE context management according to this disclosure.

[0232] In some aspects, UE context management may involve both RCS 1810 and Discovery Entity 1630. RCS 1810 may be responsible for UE context storage, and Discovery Entity 1630 may be responsible for pointing the eDU to RCS 1810. RCS 1810 may register with Discovery Entity 1630. As shown by reference numeral 1902, RCS 1810 may send a registration message to Discovery Entity 1630. The registration message may include RCS information (e.g., identification information, IP address) and recovery ID. As shown by reference numeral 1904, Discovery Entity 1630 may send a registration acceptance message to RCS 1810.

[0233] The eDU 1620 can store the UE context for the UE in the RCS 1810. As shown by reference numeral 1906, the eDU 1620 (connected to the UE 1610) can send a storage message containing the UE context of the UE 1610 to the RCS 1810. As shown by reference numeral 1908, the RCS 1810 can send a storage accept message. The RCS 1810 can provide a recovery ID in the storage accept message. The eDU 1620 can remove the UE context locally from the eDU 1620. In some respects, the eDU 1625 can host the RCS 1810 within the eDU 1625.

[0234] As shown by reference numeral 1910 in the attached figure, eDU 1620 can send a RAN release message with a recovery ID to UE 1610. UE 1610 can then become inactive. UE 1610 can then connect to eDU 1625. As shown by reference numeral 1912 in the attached figure, UE 1610 can send a RAN recovery request message with a recovery ID to eDU 1625.

[0235] The eDU 1625 can discover RCS information by contacting the discovery entity 1630. The eDU 1625 may also store previously discovered RCS information or OAM configurations. As shown by reference numeral 1914, the eDU 1625 can send a discovery request message with a recovery ID to the discovery entity 1630. As shown by reference numeral 1916, the discovery entity 1630 can send a discovery response message with RCS information to the eDU 1625. As shown by reference numeral 1920, the eDU 1625 can send a UE context retrieval message with a recovery ID to the RCS 1810. As shown by reference numeral 1922, the RCS 1810 can send a UE context response message with the UE context to the eDU 1625. As shown by reference numeral 1924, the eDU 1625 can send a RAN recovery accept message to the UE 1610.

[0236] In some respects, the network can maintain a certain level of security for UE 1610. UE 1610 can authenticate itself using the network's authentication token. Depending on the size of the RAN recovery request message, UE 1610 may include at least a subset of the Message Authentication Code – Integrity (MAC-I) configured using AS security settings. UE 1610 can be authenticated by either eDU 1620 or RCS 1810. In some respects, a new key can be derived for use by eDU 1625. eDU 1625 can interact with security services to derive the new key. Alternatively or additionally, RCS 1810 can interact with security services to derive the new key and provide it to eDU 1625.

[0237] As indicated above, Figure 19 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 19 The examples described are different.

[0238] Figure 20 This is an example diagram illustrating the use of a modular UE context according to this disclosure, specifically example 2000.

[0239] In some respects, two types of UE contexts can exist: service-specific UE contexts and non-service-specific UE contexts. Service-specific UE contexts can be specific to service requests or configurations. RB configurations can be associated with data service requests. AS security configurations can depend on security services. Measurement configurations can depend on mobility services. Non-service-specific UE contexts may not depend on a specific service. Non-service-specific UE contexts may not be associated with any specific service request.

[0240] In some respects, UE contexts can be service-specific modularized. Each service-specific UE modular context can be indexed as a UE context module in a storage entity (e.g., RCS 1810). During RAN configuration or UE 1610 reconfiguration, the eDU1620 can provide different types of configurations as the indexed UE context modules. In some respects, dependencies can exist between modules, where if one module is selected, one or more other modules can be activated along with that selected module.

[0241] Example 2000 illustrates the use of a UE modular context. UE 1610 may have a Service X configuration (displayed as Service 2010) with Service X and a Service Y configuration (displayed as Service 2020) with Service Y. Service X can be identified using Index X, and Service Y can be identified using Index Y. During service configuration in eDU 1620, eDU 1620 may assign an index to the UE modular context associated with the service (e.g., to the DRB configuration of a data service) and provide that index to UE 1610 and the service.

[0242] RCS 1810 can register with Discovery Entity 1630. As shown by reference numeral 2022, RCS 1810 can send a registration message with RCS information and recovery ID to Discovery Entity 1630. As shown by reference numeral 2024, Discovery Entity 1630 can send a registration acceptance message to RCS 1810. eDU 1620 can store one or more UE context modules representing (within the corresponding index) UE modular contexts in RCS 1810. As shown by reference numeral 2026, eDU 1620 can send a storage message to RCS 1810, indicating one or more UE modular contexts to RCS 1810. As shown by reference numeral 2028, RCS 1810 can send a storage acceptance message with recovery ID to eDU 1620.

[0243] UE 1610 can then become inactive. As shown by reference numeral 2030, eDU 1620 can send a RAN release message with a recovery ID and the index (e.g., index X, index Y) of the service to be inactive. During the RAN release message, eDU 1620 can provide UE 1610 with information on which UE modular contexts will remain inactive (and which UE modular contexts will be removed). eDU 1620 can use a bitmap to indicate which UE context modules will remain inactive. eDU 1620 can use a bitmap or another bitmap to indicate which services will be removed. That is, services associated with its UE modular context only during UE connection can be released. eDU 1620 can provide an indication that UE 1610 is inactive to the service. eDU 1620 can indicate to the service that the RAN context associated with that service is inactive.

[0244] For service-specific RAN configuration modules, eDU 1620 can indicate the index number of the UE modular context for a specific service. If the UE modular context is stored in RCS 1810, eDU 1620 can provide RCS information for contacting RCS 1810. For example, if a service-specific UE modular context is no longer valid (e.g., needs to be changed / reconfigured or completely removed), the RCS information can be used by the service to remove the UE context module associated with that service. As shown by reference numeral 2032, eDU 1620 can send a UE inactivity message with index X and RCS information to service X. Service X may be inactive for UE 1610. As shown by reference numeral 2034, eDU 1620 can send a UE inactivity message with index Y and RCS information to service Y. Service Y may be inactive for UE 1610.

[0245] As indicated above, Figure 20 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 20 The examples described are different.

[0246] Figure 21 This is a continuation illustration of Example 2000, which uses a modular UE context according to this disclosure. After services X and Y are deactivated (such as...) Figure 20 (As shown), the service can be inactive.

[0247] If the Service X context of UE 1610 is no longer valid (e.g., QoS will be modified in data service), Service X may request RCS 1810 to set its context to "invalid" (using the index provided by eDU 1620). RCS 1810 may set the UE context module of Service X's UE modular context to "invalid". RCS 1810 may confirm this situation to Service X.

[0248] In some respects, service-specific UE contexts (UE modular contexts) can be removed. If a service determines that a UE modular context (such as that of service X) is no longer valid or needs modification, the service may request RCS 1810 and / or eDU 1620 (depending on the specific implementation of UE context storage) to set the UE context module of service X to "invalid" (set as an invalid context). RCS 1810 (or eDU 1620) may set the UE context module of service X to "invalid". If any other UE context module depends on this context, it is also marked as invalid. Service-specific UE contexts not included in the service index by UE 1610 with the recovery ID may remain inactive. Inactivity may include being inactive but still considered valid for recovery. Service-specific contexts included by UE 1610 with the recovery ID but not indicated as valid in the response may be removed from UE 1610 or remain invalid.

[0249] As shown by reference numeral 2036 in the attached figure, service X can send a service context removal message with index X to RCS 1810. As shown by reference numeral 2038 in the attached figure, RCS 1810 can send a confirmation message to service X, indicating that index X has been removed.

[0250] It should be noted that since the UE 1610 can be connected to the eDU 1625, the eDU 1625 is now... Figure 21 This is part of Example 2000. UE 1610 can indicate (e.g., using a bitmap) which UE context modules to restore. In Example 2000, UE 1610 will restore both service X and service Y. As shown by reference numeral 2040, UE 1610 can send a restore request message with restore IDs and indices X and Y. As shown by reference numeral 2042, eDU 1620 can send a UE context retrieval message with a restore ID to RCS 1810.

[0251] The eDU 1625 can receive from the RCS 1810 a UE modular context indicating which UE context modules are still valid (e.g., via a bitmap, where an indication is valid and zero indicates invalid). In Example 2000, service X is no longer valid. As shown by reference numeral 2044, the RCS 1810 can send a UE context response message with a UE modular context for service Y. This response message can indicate that service X is invalid. The eDU 1625 can now have information that service X is invalid. As shown by reference numeral 2046, the eDU 1625 can send a recovery accept message to the UE 1610, using an index to indicate that service X is invalid while service Y is valid.

[0252] UE 1610 can reuse the configuration for service Y. To use service X, UE 1610 can be expected to reconfigure or reactivate service X. As shown in reference numeral 2048, UE 1610 can reconfigure the RAN for service X.

[0253] As indicated above, Figure 21 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 21 The examples described are different.

[0254] Figure 22 This is an illustration of example 2200 using a modular UE context according to this disclosure. Example 2200 may be a continuation of example 2000.

[0255] In some respects, UE 1610 can utilize modular activation to restore the UE modular context. In the restoration request, UE 1610 can request the activation of specific UE context modules. For example, if UE 1610 has eMBB and URLLC data services but only wants to establish a connection for eMBB, UE 1610 can instruct the restoration of the eMBB RB but not the URLLC RB. In the restoration response, eDU 1625 can confirm which UE context modules will be restored.

[0256] exist Figure 22 In Example 2200, services X and Y are currently inactive, but UE 1610 will use service X (instead of service Y). As shown by reference numeral 2202, eDU 1625 can send a recovery request message with a recovery ID and an index X for service X. As shown by reference numeral 2204, eDU 1625 can send a UE context retrieval message with a recovery ID to RCS 1810. As shown by reference numeral 2206, RCS 1810 can send a UE context response message to eDU 1625. As shown by reference numeral 2208, eDU 1625 can send a recovery accept message with an index X. UE 1610 can reuse the configuration for service X.

[0257] As indicated above, Figure 22 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 22 The examples described are different.

[0258] Figure 23 This is a diagram illustrating an example procedure 2300 performed, for example, at a UE or a device of a UE, according to this disclosure. Example procedure 2300 is an example of a device or UE (e.g., UE 120, UE 1610) performing an operation associated with UE context disposal.

[0259] like Figure 23As shown, in some aspects, process 2300 may include receiving RAN configuration for multiple service modules corresponding to multiple services and multiple service-specific UE contexts (block 2310). For example, the UE (e.g., using the one depicted in...) Figure 27 The receiving component 2702 and / or the communication manager 2706 in the RAN configuration can receive RAN configuration for multiple service modules corresponding to multiple services and multiple service-specific UE contexts, as described above.

[0260] like Figure 23 Further shown, in some aspects, process 2300 may include sending a recovery ID and one or more service indices corresponding to one or more requests among a plurality of services when in an inactive state (box 2320). For example, the UE (e.g., using the image depicted in...) Figure 27 The sending component 2704 and / or the communication manager 2706 in the middle can send a recovery ID and one or more service indexes corresponding to one or more requests among multiple services when in an inactive state, as described above.

[0261] like Figure 23 As further shown, in some aspects, process 2300 may include receiving a response indicating one or more valid services from among the requested services (box 2330). For example, the UE (e.g., using the service depicted in...) Figure 27 The receiving component 2702 and / or the communication manager 2706 in the middle can receive a response from one or more valid services among the services that indicate one or more requests, as described above.

[0262] like Figure 23 As further shown, in some aspects, process 2300 may include sending communication associated with a valid service in one or more valid services (block 2340). For example, the UE (e.g., using the method depicted in...) Figure 27 The sending component 2704 and / or the communication manager 2706 in the system can send communications associated with a valid service in one or more valid services, as described above.

[0263] Process 2300 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0264] In the first aspect, the first service of the plurality of services depends on the second service of the plurality of services, and the first service-specific UE context corresponding to the first service is used together with the second service-specific UE context corresponding to the second service.

[0265] In a second aspect, either alone or in combination with the first aspect, the response includes one or more valid service indexes for the one or more valid services or one or more invalid service indexes for the one or more invalid services in the services requested by the one or more requests.

[0266] In a third aspect, either alone or in combination with one or more of the first and second aspects, the RAN configuration includes the RB configuration for data services.

[0267] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the RAN configuration includes the AS security configuration for security services.

[0268] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the RAN configuration includes a measurement configuration for mobility services.

[0269] although Figure 23 An example box of process 2300 is shown, but in some respects, process 2300 may include... Figure 23 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 2300 may be executed in parallel.

[0270] Figure 24 This is a diagram illustrating an example process 2400 performed, for example, at a first network entity or a device of a first network entity, according to this disclosure. Example process 2400 is an example of an operation performed by a device or a first network entity (e.g., network node 110, core network node 130, RCS 1810) in relation to UE context handling.

[0271] like Figure 24 As shown, in some aspects, process 2400 may include receiving a recovery ID (block 2410) from a second network entity having identification information associated with retrieving the UE context for the UE. For example, a first network entity (e.g., using the one depicted in the diagram) Figure 28 The receiving component 2802 and / or the communication manager 2806 in the second network entity can receive a recovery ID having identification information associated with retrieving the UE context for the UE, as described above.

[0272] like Figure 24 As further shown, in some aspects, process 2400 may include sending a response associated with the UE context to a second network entity (box 2420). For example, a first network entity (e.g., using the one depicted in the diagram) Figure 28 The sending component 2804 and / or the communication manager 2806 in the network can send a response associated with the UE context to a second network entity, as described above.

[0273] Process 2400 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0274] In a first aspect, process 2400 includes receiving the UE context from a third network entity, and wherein the response includes the UE context.

[0275] In a second aspect, either alone or in combination with the first aspect, process 2400 includes sending registration information for the first network entity to a fourth network entity.

[0276] In a third aspect, either alone or in combination with one or more of the first and second aspects, process 2400 includes authenticating the UE using a derived security key.

[0277] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, process 2400 includes deriving a security key and sending the security key to the second network entity.

[0278] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 2400 includes storing multiple service indexes corresponding to multiple services and multiple service-specific UE contexts.

[0279] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the UE context is a service-specific UE context, and process 2400 includes receiving a service index corresponding to the service and the service-specific UE context using the recovery ID.

[0280] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, process 2400 includes maintaining the service-specific UE context used for a service index not included with the recovery ID as inactive.

[0281] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, process 2400 includes maintaining the service-specific UE context used to include with the recovery ID and not indicated as valid in the response as invalid.

[0282] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, process 2400 includes receiving from the service a request to set a service-specific UE context corresponding to the service to an invalid context, and setting a service module corresponding to the service to an invalid context.

[0283] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, process 2400 includes receiving a service index corresponding to the service using the recovery ID, and the response indicating that the service is invalid.

[0284] although Figure 24 An example box of process 2400 is shown, but in some respects, process 2400 may include... Figure 24 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 2400 may be executed in parallel.

[0285] Figure 25 This is a diagram illustrating an example process 2500 performed, for example, at a first network entity or a device of the first network entity, according to this disclosure. Example process 2500 is an example of an operation performed by a device or a first network entity (e.g., network node 110, eDU1625) in relation to UE context handling.

[0286] like Figure 25 As shown, in some aspects, process 2500 may include receiving a recovery ID from the UE, the recovery ID having identification information associated with retrieving the UE context for the UE (box 2510). For example, a first network entity (e.g., using the one depicted in...) Figure 29 The receiving component 2902 and / or the communication manager 2906 in the UE can receive a recovery ID from the UE, as described above. The recovery ID may have identification information associated with the UE context used to retrieve the UE.

[0287] like Figure 25 Further shown, in some aspects, process 2500 may include sending a recovery ID to a second network entity (box 2520). For example, the first network entity (e.g., using the one depicted in the diagram) Figure 29 The sending component 2904 and / or the communication manager 2906 in the network can send the recovery ID to the second network entity, as described above.

[0288] like Figure 25 As further shown, in some aspects, process 2500 may include receiving the UE context (box 2530). For example, a first network entity (e.g., using the one depicted in...) Figure 29 The receiving component 2902 and / or the communication manager 2906 in the UE can receive the UE context, as described above.

[0289] like Figure 25 As further shown, in some aspects, process 2500 may include sending a response to the UE (box 2540). For example, a first network entity (e.g., using the one depicted in the diagram) may send a response to the UE. Figure 29The sending component 2904 and / or the communication manager 2906 in the UE can send a response to the UE as described above.

[0290] Process 2500 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0291] In the first aspect, receiving the UE context includes receiving the UE context from the second network entity.

[0292] In a second aspect, either alone or in combination with the first aspect, process 2500 includes sending registration information for the first network entity to the second network entity.

[0293] In a third aspect, either alone or in combination with one or more of the first and second aspects, process 2500 includes sending the UE context for the UE at the first network entity to the second network entity.

[0294] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, process 2500 includes receiving information for a third network entity and sending the recovery ID to the third network entity, wherein receiving the UE context includes receiving the UE context from the third network entity.

[0295] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 2500 includes authenticating the UE using a security key.

[0296] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, process 2500 includes using the derived or received security key.

[0297] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, process 2500 includes receiving a request from the service to set a service-specific UE context corresponding to the service to an invalid context, and setting a service module corresponding to the service to an invalid context.

[0298] In the eighth aspect, alone or in combination with one or more of the first to seventh aspects, process 2500 includes receiving a service index corresponding to the service, wherein the response indicates that the service is invalid.

[0299] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the UE context is a service-specific UE context, and process 2500 includes receiving a service index corresponding to the service and the service-specific UE context using the recovery ID.

[0300] although Figure 25 An example box of process 2500 is shown, but in some respects, process 2500 may include... Figure 25 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 2500 may be executed in parallel.

[0301] Figure 26 This is a diagram illustrating an example process 2600 performed, for example, at a first network entity or a device of the first network entity, according to this disclosure. Example process 2600 is an example of an operation performed by a device or a first network entity (e.g., network node 110, core network node 130, discovery entity 1630) in relation to UE context handling.

[0302] like Figure 26 As shown, in some aspects, process 2600 may include receiving registration information from a second network entity storing the UE context (box 2610). For example, a first network entity (e.g., using the one depicted in the diagram) may receive registration information from a second network entity storing the UE context. Figure 28 The receiving component 2802 and / or the communication manager 2806 in the network can receive registration information from the second network entity storing the UE context, as described above.

[0303] like Figure 26 As shown, in some aspects, process 2600 may include receiving a recovery ID (block 2620) from a third network entity having identification information associated with the retrieved UE context. For example, a first network entity (e.g., using the one depicted in the diagram) Figure 28 The receiving component 2802 and / or the communication manager 2806 in the network can receive a recovery ID with identification information associated with the retrieved UE context from a third network entity, as described above.

[0304] like Figure 26 As further shown, in some aspects, process 2600 may include sending a response associated with the UE context (box 2630). For example, a first network entity (e.g., using the one depicted in the diagram) may send a response associated with the UE context. Figure 28 The transmitting component 2804 and / or the communication manager 2806 in the UE can transmit a response associated with the UE context, as described above.

[0305] Process 2600 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0306] In the first aspect, the response includes information relating to the second network entity.

[0307] In the second aspect, whether alone or in combination with the first aspect, the second network entity is the source RAN node.

[0308] In the third aspect, either alone or in combination with one or more of the first and second aspects, the second network entity is an RCS node.

[0309] although Figure 26 An example box of process 2600 is shown, but in some respects, process 2600 may include... Figure 26 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 2600 may be executed in parallel.

[0310] Figure 27 This is a diagram of an example device 2700 for wireless communication according to the present disclosure. Device 2700 may be a UE (e.g., UE 120, UE 1610), or a UE may include device 2700. In some aspects, device 2700 includes a receiving component 2702, a transmitting component 2704, and / or a communication manager 2706 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 2706 is combined with... Figure 1 The described communication manager 140. As shown, device 2700 can communicate with another device 2708 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 2702 and transmitting component 2704.

[0311] In some respects, device 2700 can be configured to perform the functions described herein. Figures 1 to 22 One or more operations described herein. Additionally or alternatively, the apparatus 2700 may be configured to perform one or more processes described herein, such as Figure 23 The process is 2300. In some respects, Figure 27 The illustrated device 2700 and / or one or more components may include a combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 27 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0312] Receiver 2702 may receive communications from device 2708, such as reference signals, control information, data communications, or combinations thereof. Receiver 2702 may provide the received communications to one or more other components of device 2700. In some aspects, receiver 2702 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.), and may provide the processed signals to one or more other components of device 2700. In some aspects, receiver 2702 may include combinations of... Figure 2 The described UE includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0313] Transmitting component 2704 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 2708. In some aspects, one or more other components of device 2700 can generate communications and provide the generated communications to transmitting component 2704 for transmission to device 2708. In some aspects, transmitting component 2704 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can transmit the processed signals to device 2708. In some aspects, transmitting component 2704 may include combinations of... Figure 2 The described UE may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, transmit component 2704 may co-located with receive component 2702 in one or more transceivers.

[0314] The communication manager 2706 may support the operation of the receiving component 2702 and / or the transmitting component 2704. For example, the communication manager 2706 may receive information associated with configuring the reception of communications by the receiving component 2702 and / or the transmission of communications by the transmitting component 2704. Additionally or alternatively, the communication manager 2706 may generate control information and / or provide control information to the receiving component 2702 and / or the transmitting component 2704 to control the reception and / or transmission of communications.

[0315] In some aspects, receiving component 2702 may receive RAN configuration for multiple service modules corresponding to multiple services and multiple service-specific UE contexts. When in an inactive state, transmitting component 2704 may transmit a recovery ID and one or more service indices corresponding to one or more requested services among the multiple services. Receiving component 2702 may receive responses indicating one or more valid services among the one or more requested services. Transmitting component 2704 may transmit communications associated with valid services among the one or more valid services.

[0316] Figure 27 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 27 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 27 The two or more components shown can be implemented within a single component, or Figure 27 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 27 The set (one or more) components shown are executable descriptions by Figure 27 The other set of components shown performs one or more functions.

[0317] Figure 28 This is a diagram of an example device 2800 for wireless communication according to the present disclosure. Device 2800 may be a first network entity (e.g., core network node 130, RCS 1810, discovery entity 1630), or the first network entity may include device 2800. In some aspects, device 2800 includes a receiving component 2802, a transmitting component 2804, and / or a communication manager 2806 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 2806 is combined with... Figure 1 The described communication manager 160. As shown, device 2800 can communicate with another device 2808 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 2802 and transmitting component 2804.

[0318] In some respects, device 2800 can be configured to perform the functions described herein. Figures 1 to 22 One or more operations described herein. Additionally or alternatively, the apparatus 2800 may be configured to perform one or more processes described herein, such as Figure 24 Process 2400 Figure 26 The process 2600 or a combination thereof. In some respects, Figure 28 The device 2800 and / or one or more components shown may include a combination Figure 2One or more components of the first network entity described. Additionally or alternatively, Figure 28 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0319] Receiver 2802 may receive communications from device 2808, such as reference signals, control information, data communications, or combinations thereof. Receiver 2802 may provide the received communications to one or more other components of device 2800. In some aspects, receiver 2802 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 2800. In some aspects, receiver 2802 may include combinations of... Figure 2 The first network entity described includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0320] Transmitting component 2804 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 2808. In some aspects, one or more other components of device 2800 can generate communications and provide the generated communications to transmitting component 2804 for transmission to device 2808. In some aspects, transmitting component 2804 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can transmit the processed signals to device 2808. In some aspects, transmitting component 2804 may include combinations of... Figure 2 The described first network entity includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 2804 may co-located with the receive component 2802 in one or more transceivers.

[0321] The communication manager 2806 may support the operation of the receiving component 2802 and / or the transmitting component 2804. For example, the communication manager 2806 may receive information associated with configuring the reception of communications by the receiving component 2802 and / or the transmission of communications by the transmitting component 2804. Additionally or alternatively, the communication manager 2806 may generate control information and / or provide control information to the receiving component 2802 and / or the transmitting component 2804 to control the reception and / or transmission of communications.

[0322] In some aspects of RCS operation involving the first network entity, receiving component 2802 may receive a recovery ID from a second network entity (e.g., a target eDU), which has identification information associated with retrieving the UE context for the UE. Transmitting component 2804 may transmit a response associated with the UE context to the second network entity. Receiving component 2802 may receive the UE context from a third network entity (e.g., a source eDU), and the response may include the UE context. Transmitting component 2804 may transmit registration information for the first network entity to a fourth network entity (e.g., a discovery entity).

[0323] The communication manager 2806 can authenticate the UE using the exported security key. The communication manager 2806 can export the security key. The transmitting component 2804 can send the security key to a second network entity.

[0324] The communication manager 2806 can store multiple service indexes corresponding to multiple services and multiple service-specific UE contexts. The receiving component 2802 can receive a request from a service to set the service-specific UE context corresponding to that service to an invalid context. The communication manager 2806 can set the service module corresponding to the service to an invalid context. The receiving component 2802 can receive the service index corresponding to the service using a recovery ID and respond to indicate that the service is invalid.

[0325] In some aspects of the first network entity's operation as a discovery entity, the receiving component 2802 may receive registration information from a second network entity (e.g., source eDU, RCS) that stores the UE context. The receiving component 2802 may also receive a recovery ID with identification information associated with retrieving the UE context from a third network entity (e.g., target eDU). The transmitting component 2804 may transmit a response associated with the UE context.

[0326] Figure 28 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 28 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 28 The two or more components shown can be implemented within a single component, or Figure 28 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 28 The set (one or more) components shown are executable descriptions by Figure 28 The other set of components shown performs one or more functions.

[0327] Figure 29 This is a diagram of an example device 2900 for wireless communication according to the present disclosure. Device 2900 may be a first network entity (e.g., network node 110, eDU 1625), or the first network entity may include device 2900. In some aspects, device 2900 includes a receiving component 2902, a transmitting component 2904, and / or a communication manager 2906 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 2906 is combined with... Figure 1 The described communication manager 150. As shown, device 2900 can communicate with another device 2908 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 2902 and transmitting component 2904.

[0328] In some respects, device 2900 can be configured to perform the functions described herein. Figures 1 to 22 One or more operations described herein. Additionally or alternatively, the apparatus 2900 may be configured to perform one or more processes described herein, such as Figure 25 The process is 2500. In some respects, Figure 29 The device 2900 and / or one or more components shown may include a combination Figure 2 One or more components of the first network entity described. Additionally or alternatively, Figure 29 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0329] Receiver 2902 may receive communications from device 2908, such as reference signals, control information, data communications, or combinations thereof. Receiver 2902 may provide the received communications to one or more other components of device 2900. In some aspects, receiver 2902 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 2900. In some aspects, receiver 2902 may include combinations of... Figure 2 The first network entity described includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0330] Transmitting component 2904 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 2908. In some aspects, one or more other components of device 2900 can generate communications and provide the generated communications to transmitting component 2904 for transmission to device 2908. In some aspects, transmitting component 2904 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can transmit the processed signals to device 2908. In some aspects, transmitting component 2904 may include combinations of... Figure 2 The described first network entity includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 2904 may co-located with the receive component 2902 in one or more transceivers.

[0331] The communication manager 2906 may support the operation of the receiving component 2902 and / or the transmitting component 2904. For example, the communication manager 2906 may receive information associated with configuring the reception of communications by the receiving component 2902 and / or the transmission of communications by the transmitting component 2904. Additionally or alternatively, the communication manager 2906 may generate control information and / or provide control information to the receiving component 2902 and / or the transmitting component 2904 to control the reception and / or transmission of communications.

[0332] In some aspects of the first network entity operating as a RAN node (e.g., eDU), the receiving component 2902 may receive a recovery ID from the UE, which has identification information associated with retrieving the UE context for the UE. The transmitting component 2904 may transmit the recovery ID to a second network entity (e.g., discovery entity, RCS, source eDU). The receiving component 2902 may receive the UE context. The transmitting component 2904 may transmit a response to the UE.

[0333] The sending component 2904 can send registration information for the first network entity to the second network entity. The sending component 2904 can also send the UE context for the UE from the first network entity to the second network entity.

[0334] The receiving component 2902 can receive information for a third network entity.

[0335] The sending component 2904 can send the recovery ID to a third network entity, wherein receiving the UE context includes receiving the UE context from the third network entity.

[0336] The Communication Manager 2906 can authenticate the UE using a security key. The Communication Manager 2906 can export or receive security keys.

[0337] The receiving component 2902 can receive a request from the service to set a service-specific UE context corresponding to the service to an invalid context. The communication manager 2906 can set a service module corresponding to the service to an invalid context. The receiving component 2902 can receive a service index corresponding to the service, wherein the response indicates that the service is invalid.

[0338] The following provides an overview of some aspects of this disclosure: Aspect 1: A method for wireless communication performed by a user equipment (UE), the method comprising: receiving a radio access network (RAN) configuration for multiple service modules corresponding to multiple services and multiple service-specific UE contexts; transmitting a recovery identifier (ID) and one or more service indices corresponding to one or more requested services among the multiple services when in an inactive state; receiving a response indicating one or more valid services among the one or more requested services; and transmitting communication associated with a valid service among the one or more valid services.

[0339] Aspect 2: According to the method of aspect 1, the first service of the plurality of services depends on the second service of the plurality of services, and the first service-specific UE context corresponding to the first service is used together with the second service-specific UE context corresponding to the second service.

[0340] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the response includes one or more valid service indexes for the one or more valid services or one or more invalid service indexes for the one or more invalid services in the services of the one or more requests.

[0341] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the RAN configuration includes resource block configuration for data services.

[0342] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the RAN configuration includes an access layer security configuration for security services.

[0343] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the RAN configuration includes a measurement configuration for mobility services.

[0344] Aspect 7: A method of wireless communication performed by a first network entity, the method comprising: receiving a recovery identifier (ID) from a second network entity, the recovery identifier having identification information associated with retrieving a UE context for a user equipment (UE); and sending a response associated with the UE context to the second network entity.

[0345] Aspect 8: According to the method of aspect 7, the method further includes receiving the UE context from a third network entity, and wherein the response includes the UE context.

[0346] Aspect 9: The method according to any one of Aspects 7 to 8, the method further comprising sending registration information for the first network entity to a fourth network entity.

[0347] Aspect 10: The method according to any one of Aspects 7 to 9 further includes authenticating the UE using a derived security key.

[0348] Aspect 11: The method according to any one of Aspects 7 to 10, the method further comprising: deriving a security key; and sending the security key to the second network entity.

[0349] Aspect 12: The method according to any one of Aspects 7 to 11, the method further comprising storing a plurality of service indexes corresponding to a plurality of services and a plurality of service-specific UE contexts.

[0350] Aspect 13: The method according to aspect 12, wherein the UE context is a service-specific UE context, and wherein the method includes receiving a service index corresponding to the service and the service-specific UE context using the recovery ID.

[0351] Aspect 14: The method according to aspect 13 further includes maintaining a service-specific UE context for a service index not included with the recovery ID as inactive.

[0352] Aspect 15: The method according to aspect 13 further includes maintaining the service-specific UE context used to include, together with the recovery ID and not indicated as valid in the response, as invalid.

[0353] Aspect 16: The method according to any one of Aspects 7 to 15, the method further comprising: receiving from a service a request to set a service-specific UE context corresponding to the service to an invalid context; and setting a service module corresponding to the service to the invalid context.

[0354] Aspect 17: The method according to aspect 16, the method further comprising receiving a service index corresponding to the service using the recovery ID, wherein the response indicates that the service is invalid.

[0355] Aspect 18: A method of wireless communication performed by a first network entity, the method comprising: receiving a recovery identifier (ID) from a user equipment (UE), the recovery ID having identification information associated with retrieving a UE context for the UE; sending the recovery ID to a second network entity; receiving the UE context; and sending a response to the UE.

[0356] Aspect 19: The method according to aspect 18, wherein receiving the UE context includes receiving the UE context from the second network entity.

[0357] Aspect 20: The method according to any one of Aspects 18 to 19, the method further comprising sending registration information for the first network entity to the second network entity.

[0358] Aspect 21: The method according to any one of Aspects 18 to 20, the method further comprising sending a UE context for the UE at the first network entity to the second network entity.

[0359] Aspect 22: The method according to any one of Aspects 18 to 21, the method further comprising: receiving information for a third network entity; and sending the recovery ID to the third network entity, wherein receiving the UE context includes receiving the UE context from the third network entity.

[0360] Aspect 23: The method according to any one of aspects 18 to 22, the method further includes authenticating the UE using a security key.

[0361] Aspect 24: According to the method of aspect 23, the method further includes exporting or receiving the security key.

[0362] Aspect 25: The method according to any one of Aspects 18 to 24, the method further comprising: receiving from a service a request to set a service-specific UE context corresponding to the service to an invalid context; and setting a service module corresponding to the service to the invalid context.

[0363] Aspect 26: According to the method of aspect 25, the method further includes receiving a service index corresponding to the service, wherein the response indicates that the service is invalid.

[0364] Aspect 27: The method according to any one of Aspects 18 to 26, wherein the UE context is a service-specific UE context, and wherein the method includes receiving a service index corresponding to the service and the service-specific UE context using the recovery ID.

[0365] Aspect 28: A method of wireless communication performed by a first network entity, the method comprising: receiving registration information from a second network entity storing a user equipment (UE) context; receiving a recovery identifier (ID) from a third network entity, the recovery identifier having identification information associated with retrieving the UE context; and sending a response associated with the UE context.

[0366] Aspect 29: The method according to aspect 28, wherein the response includes information relating to the second network entity.

[0367] Aspect 30: The method according to any one of Aspects 28 to 29, wherein the second network entity is a source radio access network node.

[0368] Aspect 31: The method according to any one of Aspects 28 to 30, wherein the second network entity is a source radio access network context service (RCS) node.

[0369] Aspect 32: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more of aspects 1 to 31.

[0370] Aspect 33: An apparatus for wireless communication at a device, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 1 to 31.

[0371] Aspect 34: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 31.

[0372] Aspect 35: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the method according to one or more of aspects 1 to 31.

[0373] Aspect 36: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1 to 31.

[0374] Aspect 37: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 1 to 31.

[0375] Aspect 38: An apparatus for wireless communication at a device, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more of aspects 1 to 31.

[0376] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit aspects to the precise forms disclosed. Modifications and variations can be made based on the foregoing disclosure, or from various aspects of practice.

[0377] As used herein, the term "component" is intended to be interpreted broadly as hardware, firmware, or a combination of hardware and software. As used herein, a processor is implemented as hardware, firmware, or a combination of hardware and software. As used herein, the phrase "based on" is intended to be interpreted broadly as "at least partially based on". As used herein, depending on the context, "meeting a threshold" can refer to a value greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc. As used herein, the phrase referring to "at least one of" a list of items means any combination of those items, including a single member. As an example, "at least one of a, b, or c" is intended to cover: a, b, c, a+b, a+c, b+c, and a+b+c.

[0378] Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are interchangeable with “one or more”. Furthermore, as used herein, the article “the” is intended to include one or more items mentioned in connection with the article “the” and is interchangeable with “one or more”. Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items) and are interchangeable with “one or more”. If only one item is desired, the phrase “only one” or similar terms will be used. Moreover, as used herein, the terms “having” and similar terms are intended to be open-ended terms that do not limit the elements they modify (e.g., an element “having” A may also have B). Furthermore, as used herein, the term “or” when used in a sequence is intended to be inclusive and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., in conjunction with “either of” or “only one of”).

[0379] The various exemplary logic components, logic blocks, modules, circuits, and algorithmic processes described in conjunction with the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. The interchangeability of hardware and software has been generally described in terms of functionality and is illustrated in the various exemplary components, blocks, modules, circuits, and processes described herein. Whether such functionality is implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0380] Hardware and data processing means for implementing the various exemplary logic, logic blocks, modules, and circuits described herein can be implemented or executed using general-purpose single-chip or multi-chip processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. In some aspects, specific processes and methods can be performed by circuitry dedicated to a given function.

[0381] In one or more aspects, the described functionality may be implemented in hardware, digital electronic circuits, computer software, firmware, including the structures disclosed in this specification and their structural equivalents or any combination thereof. Aspects of the subject matter described in this specification may also be implemented as one or more computer programs (such as one or more modules of computer program instructions) encoded on a computer storage medium for execution by or control of the operation of a data processing apparatus.

[0382] If implemented in software, the functionality can be stored as one or more instructions or code on or transmitted through a computer-readable medium. The processes of the methods or algorithms disclosed herein can be implemented in a processor-executable software module that can reside on a computer-readable medium. Computer-readable media include both computer storage media and communication media, with communication media including any medium capable of transferring a computer program from one place to another. Storage media can be any available medium accessible to a computer. By way of example, and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage devices, disk storage devices or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and is accessible to a computer. Furthermore, any connection may be properly referred to as a computer-readable medium. As used herein, disks and optical discs include compact optical discs (CDs), laser discs, optical discs, digital versatile optical discs (DVDs), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically, while optical discs reproduce data optically using lasers. Combinations of media described herein should also be included within the scope of computer-readable media. In addition, the operation of a method or algorithm may reside as a set of code and instructions or any combination of code and instructions on a machine-readable medium and a computer-readable medium that may be incorporated into a computer program product.

[0383] Various modifications to the aspects described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the spirit or scope of this disclosure. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be granted the widest scope consistent with this disclosure, the principles disclosed herein, and the novel features.

[0384] Additionally, those skilled in the art will readily recognize that the terms “upper” and “lower” are sometimes used to facilitate the description of the drawings and to indicate relative positioning on a correctly oriented page corresponding to the orientation of the drawings, and may not reflect the correct orientation of any device as implemented.

[0385] Some features described in the context of an independent aspect in this specification may also be implemented in combination in a single aspect. Conversely, various features described in the context of a single aspect may also be implemented individually or in any suitable sub-combination in multiple aspects. Furthermore, although features may be described as functioning in certain combinations and even originally claimed in this way, one or more features from the claimed combination may be removed from that combination in some cases, and the claimed combination may be for sub-combinations or variations thereof.

[0386] Similarly, although operations are depicted in a specific order in the figures, this should not be construed as requiring such operations to be performed in the specific order shown or in sequential order, or to perform all illustrated operations to achieve the desired result. Furthermore, the figures may schematically depict one or more example processes in the form of flowcharts. However, other operations not depicted may be incorporated into the schematically illustrated example processes. For example, one or more additional operations may be performed before, after, simultaneously with, or between any of the illustrated operations. In some contexts, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the described aspects should not be construed as requiring such separation in all aspects, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Additionally, other aspects also fall within the scope of the appended claims. In some cases, the actions recited in the claims may be performed in a different order and still achieve the desired result.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors individually or collectively configured to cause the UE to: Receive radio access network (RAN) configuration, the radio access network (RAN) configuration being used for multiple service modules corresponding to multiple services and multiple service-specific UE contexts; When in an inactive state, a recovery identifier (ID) and one or more service indexes corresponding to one or more requests among the plurality of services are sent; Receive a response from one or more valid services among the services indicated by the one or more requests; as well as Send communications associated with a valid service among the one or more valid services.

2. The apparatus of claim 1, wherein the first service of the plurality of services depends on the second service of the plurality of services, and wherein a first service-specific UE context corresponding to the first service is used in conjunction with a second service-specific UE context corresponding to the second service.

3. The apparatus of claim 1, wherein the response comprises one or more valid service indices for the one or more valid services or one or more invalid service indices for the one or more invalid services among the services of the one or more requests.

4. The apparatus of claim 1, wherein the RAN configuration includes a resource block configuration for data services.

5. The apparatus of claim 1, wherein the RAN configuration includes access layer security configuration for security services.

6. The apparatus of claim 1, wherein the RAN configuration includes a measurement configuration for mobility services.

7. An apparatus for wireless communication at a first network entity, the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors being individually or collectively configured to cause the first network entity to: Receive a recovery identifier (ID) from a second network entity, the recovery identifier (ID) having identification information associated with retrieving the UE context for the user equipment (UE); and The response associated with the UE context is sent to the second network entity.

8. The apparatus of claim 7, wherein the one or more processors are individually or jointly configured to cause the first network entity to receive the UE context from the third network entity, and wherein the response includes the UE context.

9. The apparatus of claim 7, wherein the one or more processors are individually or collectively configured to cause the first network entity to send registration information for the first network entity to a fourth network entity.

10. The apparatus of claim 7, wherein the one or more processors are individually or jointly configured to enable the first network entity to authenticate the UE using a derived security key.

11. The apparatus of claim 7, wherein the one or more processors are individually or collectively configured to cause the first network entity to: Export the security key; and The security key is sent to the second network entity.

12. The apparatus of claim 7, wherein the one or more processors are individually or collectively configured to cause the first network entity to store a plurality of service indexes corresponding to a plurality of services and a plurality of service-specific UE contexts.

13. The apparatus of claim 12, wherein the UE context is a service-specific UE context, and wherein the one or more processors are individually or collectively configured to cause the first network entity to receive a service index corresponding to the service and the service-specific UE context using the recovery ID.

14. The apparatus of claim 13, further comprising maintaining a service-specific UE context for a service index not included with the recovery ID as inactive.

15. The apparatus of claim 13, further comprising maintaining a service-specific UE context for inclusion with the recovery ID and not indicated as valid in the response as invalid.

16. The apparatus of claim 7, wherein the one or more processors are individually or collectively configured to cause the first network entity to: Receive a request from the service to set the service-specific UE context corresponding to the service to an invalid context; and Set the service module corresponding to the service to the invalid context.

17. The apparatus of claim 16, wherein the one or more processors are individually or jointly configured to cause the first network entity to receive a service index corresponding to the service using the recovery ID, and wherein the response indicates that the service is invalid.

18. An apparatus for wireless communication at a first network entity, the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors being individually or collectively configured to cause the first network entity to: Receive a recovery identifier (ID) from the user equipment (UE), the recovery ID having identification information associated with retrieving the UE context for the UE; Send the recovery ID to the second network entity; Receive the UE context; as well as The response is sent to the UE.

19. The apparatus of claim 18, wherein, in order to receive the UE context, the one or more processors are individually or jointly configured to cause the first network entity to receive the UE context from the second network entity.

20. The apparatus of claim 18, wherein the one or more processors are individually or collectively configured to cause the first network entity to send registration information for the first network entity to the second network entity.

21. The apparatus of claim 18, wherein the one or more processors are individually or jointly configured to cause the first network entity to transmit a UE context for the UE at the first network entity to the second network entity.

22. The apparatus of claim 18, wherein the one or more processors are individually or collectively configured to cause the first network entity to: Receive information for third network entities; and The recovery ID is sent to the third network entity, wherein, in order to receive the UE context, the one or more processors are individually or jointly configured to cause the first network entity to receive the UE context from the third network entity.

23. The apparatus of claim 18, wherein the one or more processors are individually or jointly configured to cause the first network entity to authenticate the UE using a security key, and wherein the one or more processors are individually or jointly configured to cause the first network entity to export or receive the security key.

24. The apparatus of claim 18, wherein the one or more processors are individually or jointly configured to cause the first network entity to: Receive a request from the service to set the service-specific UE context corresponding to the service to an invalid context; and Set the service module corresponding to the service to the invalid context.

25. The apparatus of claim 24, wherein the one or more processors are individually or jointly configured to cause the first network entity to receive a service index corresponding to the service, wherein the response indicates that the service is invalid.

26. The apparatus of claim 18, wherein the UE context is a service-specific UE context, and wherein the one or more processors are individually or jointly configured to cause the first network entity to receive a service index corresponding to the service and the service-specific UE context using the recovery ID.

27. An apparatus for wireless communication at a first network entity, the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors being individually or collectively configured to cause the first network entity to: Receive registration information from a second network entity that stores the user equipment (UE) context; Receive a recovery identifier (ID) from a third network entity, the recovery identifier (ID) having identification information associated with retrieving the UE context; and Send a response associated with the UE context.

28. The apparatus of claim 27, wherein the response includes information relating to the second network entity.

29. The apparatus of claim 27, wherein the second network entity is a source radio access network node.

30. The apparatus of claim 27, wherein the second network entity is a source radio access network context service (RCS) node.

Images