Systems and methods for connection and data path establishment in scalable ran architectures

Abstract

Systems and methods for connection and data path establishment in scalable radio access network (RAN) architectures are discussed. A user equipment (UE) sends, to a RAN access node (AN) (RAN-AN) of a RAN, a connection request message indicating a request for the UE to connect to the RAN; receives, from a RAN control function (CF) (RAN-CF) of the RAN, via the RAN-AN, a connection setup message comprising RAN-AN configuration information for the RAN-AN and an access stratum (AS) data plane (DP) configuration for a RAN data function (DF) (RAN-DF) of the RAN; and performs a connection setup for the RAN based on the RAN-AN configuration information for the RAN-AN and the AS DP configuration for the RAN-DF. Various other UE, RAN-CF, RAN-DF, and RAN-AF functions are also discussed.

Description

SYSTEMS AND METHODS FOR CONNECTION AND DATA PATH ESTABLISHMENT IN SCALABLE RAN ARCHITECTURESCROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims the benefit of U.S. Provisional Patent Application No.63 / 755,015, filed February 6, 2025, entitled “SCALABLE RAN ARCHITECTURE FOR 6G IN CELL-FREE USE CASES,'’ which is hereby incorporated by reference herein in its entirety.TECHNICAL FIELD

[0002] This application relates generally to wireless communication systems, including systems implementing cell-free communication.BACKGROUND

[0003] Wireless mobile communication technology uses various standards and protocols to transmit data between a base station and a wireless communication device. Wireless communication system standards and protocols can include, for example. 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard for Wireless Local Area Networks (WLAN) (commonly known to industry groups as Wi-Fi®).

[0004] As contemplated by the 3GPP, different wireless communication systems' standards and protocols can use various radio access networks (RANs) for communicating between a base station of the RAN (which may also sometimes be referred to generally as a RAN node, a network node, or simply a node) and a wireless communication device known as a user equipment (UE). 3GPP RANs can include, for example, Global System for Mobile communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN). Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or Next-Generation Radio Access Network (NG-RAN). Herein, references to 6G RAN may be used to denote RANs beyond these RANs that are presently under development.

[0005] Each RAN may use one or more radio access technologies (RATs) to perform communication between the base station and the UE. For example, the GERAN14935-4185-2302,1 P70374WO3implements GSM and / or EDGE RAT, the UTRAN implements Universal Mobile Telecommunication System (UMTS) RAT or other 3GPP RAT, the E-UTRAN implements LTE RAT (sometimes simply referred to as LTE), and NG-RAN implements NR RAT (sometimes referred to herein as 5G RAT, 5GNR RAT, or simply NR). In certain deployments, the E-UTRAN may also implement NR RAT. In certain deployments, NG-RAN may also implement LTE RAT. Herein, references to 6G RAT may be used to denote RATs beyond these RATs that are presently under development.

[0006] A base station used by a RAN may correspond to that RAN. One example of an E-UTRAN base station is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB). One example of an NG-RAN base station is a next generation Node B (also sometimes referred to as a g Node B or gNB).

[0007] A RAN provides its communication services with external entities through its connection to a core network (CN). For example, E-UTRAN may utilize an Evolved Packet Core (EPC) while NG-RAN may utilize a 5G Core Network (5GC). A 6G RAN may utilize a corresponding 6G CN, which may adopt one or more entities of EPC and / or 5GC.BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

[0008] To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced.

[0009] FIG. 1 illustrates an example of a multi-connectivity deployment as may be used in an existing wireless communication system (e.g., a 5G wireless communication system).

[0010] FIG. 2 illustrates an example of a cloud-based RAN architecture deployment as may be used in an existing wireless communication system (e.g., a 5G wireless communication system).

[0011] FIG. 3 illustrates a scalable RAN architecture, according to embodiments herein.

[0012] FIG. 4 illustrates an example mapping of services and functions as may be used in the scalable RAN architectures disclosed herein.

[0013] FIG. 5A through FIG. 5D illustrate examples of data transfer using a scalable RAN architecture.24935-4185-2302,1 P70374WO3

[0014] FIG. 6 illustrates an example of RAN mobility types within a scalable RAN architecture.

[0015] FIG. 7A and FIG. 7B together provide an illustration of existing 5G mobility framework for the mobility of a UE as in existing 5G wireless communication systems.

[0016] FIG. 8A and FIG. 8B together provide an illustration of a RAN-AN mobility framework for the mobility of a UE in a wireless communication system implementing the scalable RAN architectures discussed herein.

[0017] FIG. 9 illustrates a timeline and a corresponding chart of an execution of RAN-AN mobility from a first RAN-AN to a second RAN-AN, according to embodiments discussed herein.

[0018] FIG. 10 illustrates an example flow diagram for RAN-AN mobility, according to embodiments discussed herein.

[0019] FIG. 11 illustrates an example flow diagram for RAN-AN mobility, according to embodiments discussed herein.

[0020] FIG. 12 illustrates a visualization of an RB context as may be understood within a scalable RAN as disclosed herein.

[0021] FIG. 13A illustrates a transparent RAN-DF mobility mode where RB context information is not updated / changed when the RB is moved.

[0022] FIG. 13B illustrates a non-transparent RAN-DF mobility mode where RB context information is updated 1318 for use by the target RAN-DF.

[0023] FIG. 14 illustrates an example flow diagram for transparent RAN-DF mobility, according to embodiments discussed herein.

[0024] FIG. 15 illustrates an example flow diagram for non-transparent RAN-DF mobility, according to embodiments discussed herein.

[0025] FIG. 16 illustrates an example flow diagram for RAN-CF mobility, according to embodiments discussed herein.

[0026] FIG. 17 illustrates an example flow diagram for RAN-AN scaling for a UE, according to embodiments discussed herein.

[0027] FIG. 18 illustrates a visualization of a UE-RAN context as may be understood within a scalable RAN as disclosed herein.

[0028] FIG. 19 illustrates a comparison between RRC states as may be used in current systems and a state conception as may instead be used in scalable RAN systems.34935-4185-2302,1 P70374WO3

[0029] FIG. 20 illustrates a UE-RAN ID as may be used for maintaining / tracking a UE-RAN context in a scalable RAN system according to embodiments herein.

[0030] FIG. 21 A illustrates an example flow diagram for initial RAN registration and UE-RAN context and UE-RAN ID assignment for a UE in a scalable RAN, according to embodiments discussed herein.

[0031] FIG. 21B illustrates an example flow diagram for a UE-RAN context establishment procedure.

[0032] FIG. 22 illustrates a method of a RAN, according to embodiments discussed herein.

[0033] FIG. 23 illustrates a method of a RAN-DF of a RAN, according to embodiments discussed herein.

[0034] FIG. 24 illustrates a method of a UE, according to embodiments discussed herein.

[0035] FIG. 25 illustrates a method of a RAN-DF of a RAN, according to embodiments discussed herein.

[0036] FIG. 26 illustrates a method of a RAN-CF of a RAN, according to embodiments discussed herein.

[0037] FIG. 27 illustrates a method of a RAN-CF of a RAN, according to embodiments discussed herein.

[0038] FIG. 28 illustrates a method of a source RAN-DF of a RAN that is performing management of an RB of a UE served by the RAN, according to embodiments discussed herein.

[0039] FIG. 29 illustrates a method of a target RAN-DF of a RAN, according to embodiments discussed herein.

[0040] FIG. 30 illustrates a method of a source RAN-CF of a RAN, according to embodiments discussed herein.

[0041] FIG. 31 illustrates a method of a target RAN-CF of a RAN, according to embodiments discussed herein.

[0042] FIG. 32 illustrates a method of a UE, according to embodiments discussed herein.

[0043] FIG. 33 illustrates a method of a RAN-CF of a RAN, according to embodiments discussed herein.44935-4185-2302,1 P70374WO3

[0044] FIG. 34 illustrates a method of a UE, according to embodiments discussed herein.

[0045] FIG. 35 illustrates a method of a RAN-CF of a RAN, according to embodiments discussed herein.

[0046] FIG. 36 illustrates an example architecture of a wireless communication system, according to embodiments disclosed herein.

[0047] FIG. 37 illustrates a system for performing signaling between a wireless device and a network device, according to embodiments disclosed herein.DETAILED DESCRIPTION

[0048] Various embodiments are described with regard to a UE. However, reference to a UE is merely provided for illustrative purposes. The example embodiments may be utilized with any electronic component that may establish a connection to a network and is configured with the hardware, software, and / or firmware to exchange information and data with the network. Therefore, the UE as described herein is used to represent any appropriate electronic component.Issues in Achieving Cell-Free Targets Under Existing 5G / 5G-A Architectures

[0049] FIG. 1 illustrates an example of a multi -connectivity deployment 100 as may be used in an existing wireless communication system (e.g.. a 5G wireless communication system). As illustrated, a UE 102 connects to a first base station 104 via a first Uu interface 106 and to a second base station 108 on a second Uu interface 110. The first base station 104 connects to a CN 112 via a first N2 / N3 interface 114, while the second N2 / N3 interface 116 connects to the CN 112 via a second N2 / N3 interface 116, as shown. Any inter-base-station communications between the first base station 104 and the second base station 108 occur on an Xn interface 118.

[0050] Under the multi-connectivity deployment 100 of the existing wireless communication system, each of the first base station 104 and the second base station 108 utilizes a set of resources that is dedicated for that base station. For example, as illustrated, the first base station 104 uses a first CU-UP function 120, a first CU-CP function 122, first DU(s) 124, and first TRP(s) 126 that are dedicated to the first base station 104. Further, the second base station 108 uses a second CU-UP function 128. a second CU-CP function 130, second DU(s) 132, and second TRP(s) 134 that are dedicated to the second base station 108.54935-4185-2302,1 P70374WO3

[0051] Multi-connectivity mechanisms in existing wireless communication systems (such as that illustrated in FIG. 1) exhibit various scaling problems. In such cases, adding an extra node requires the establishment of a complete UE-access stratum (AS)-context per node (i. e. , a complete L1 / L2 / L3 configuration for each note). Accordingly, even with just two base stations, the current systems using multi-connectivity (such as that shown in FIG. 1) face many complexities.

[0052] FIG. 2 illustrates an example of a cloud-based RAN architecture deployment 200 as may be used in an existing wireless communication system (e.g., a 5G wireless communication system). A UE 202 connects to a physical coverage space 204 of the RAN via a Uu interface 206. A cloud-based base station function 208 operates the physical coverage space 204 over an Fl interface 210 using a first CU-UP function 212 and a first CU-CP function 214. Finally, the cloud-based base station function 208 connects back to a CN 216 via an N2 / N3 interface 218.

[0053] Cloud-based RAN architecture deployments (such as that shown in FIG. 2) exhibit various drawbacks. Firstly, because there is only limited coverage corresponding to the physical coverage space 204, if the service coverage for the base station remains similar in scope to that of a base station in a non-cloud based RAN architecture, then UE physical movement / UE mobility leads to changing base stations. This can result in data transfer interruption.

[0054] Secondly, it is noted that a base station cannot have unlimited service coverage due to load balancing concerns. Functions of / at a single base station are ultimately limited by the processing capabilities of that base station. Accordingly, it may be necessary to operate additional base stations in a same / overlapping physical area to allow for load balancing across the base stations. This means that there may be UE mobility across the base stations (even in cases where the UE is not moving). This can result in data transfer interruption.Embodiments for Scalable RAN Architectures

[0055] Various embodiments discussed herein use improved RAN architecture designs (e.g., as compared to those illustrated in FIG. 1 and FIG. 2). Such designs may be conceived as a set of network nodes and / or functions. These designs are compatible with cloud (e.g., centralized, edge-cloud, or far-edge cloud) deployments. The architecture64935-4185-2302,1 P70374WO3designs discussed herein reflect a focus on UE-centric multi-node, multi-function connectivity.

[0056] Discussion herein relates to the uses of RAN access nodes (ANs) (RAN-ANs), RAN data functions (DFs) (RAN-DFs), and RAN control functions (CFs) (RAN-CFs). Roles and responsibilities for these entities are described. Various mappings of network services to these network entities / functions are explained. Relationships between radio bearers (RBs) and RAN-DFs are explained.

[0057] Corresponding to various embodiments, interfaces between RAN network nodes and functions are defined. In particular, many-to-many interfaces between RAN-ANs and RAN-DFs are defined. Further, many-to-many interfaces between RAN-DFs and RAN-CFs are defined. Various interfaces between RAN network nodes and functions and cellular CN functions are discussed.

[0058] These interfaces enable the decoupling of mobility aspects between layers, in that mobility procedures of each particular type can be accomplished without necessarily triggering a mobility procedure of another type. Three types of RAN mobility are contemplated, as follows. First, RAN-AN mobility may occur. This t pe of mobility impacts layer 1 (L2) and lower layer 2 (L2). RAN-AN configurations are impacted.

[0059] Further, RAN-DF mobility may occur. This type of mobility impacts upper L2 (data plane). RAN-DF radio bearer configurations are impacted.

[0060] Still further, RAN-CF mobility may occur. This ty pe of mobility impacts layer 3 (L3) (RAN control plane). RAN-CF configurations are impacted.

[0061] RAN-AN mobility7(for physical layer services of a UE) enables a low-complexity version / application of a "make-before-break" principle corresponding to an LI configuration update. It provides the system with a robust mobility7option without data transfer interruption, and therefore is suitable for highly -mobile scenarios. Herein, RAN-AN mobility' procedures are described.

[0062] RAN-DF mobility can be triggered if a RAN decides to change the data function entity' (e.g., the RAN-DF) that supports a radio bearer (RB) of a UE. Two options for this ty pe of mobility' are defined. In a first option, this type of mobility' is transparent to the UE (occurs without an update of RB context). In a second option, this ty pe of mobility is non-transparent to the UE, in which case there is an impact on / change of the RB context at the UE.74935-4185-2302,1 P70374WO3

[0063] Herein, various RAN-CF mobility' procedures are described.

[0064] In some embodiments herein, an option of UE-RAN context handling by a control function (e.g., a RAN-CF) is described that may be used to reduce an applicable UE context migration overhead. As enabled by CF UE context handling, a new nonconnected radio resource control (RRC) state may be used (e.g.. as a replacement for both of the existing RRC idle and RRC inactive states used in some present 5G systems). A latency required for the UE to transition from the new non-connected state to the new connected state and to correspondingly perform data transfer is relatively reduced corresponding to such cases. Further, an initial RAN registration procedure for the case of CF-handled UE contexts is described.

[0065] Finally, discussion found herein relates to a procedure of UE serving access node (RAN-AN) scaling. Details on how additional RAN-ANs or additional component carriers (CCs) can be configured for a UE in this context are provided.

[0066] FIG. 3 illustrates a scalable RAN architecture 300, according to embodiments herein. The scalable RAN architecture 300 can be conceived in terms of a RAN 302 that communicates with a cellular CN 304, as illustrated. Various functions and nodes are now discussed.

[0067] Under a scalable RAN architecture, a RAN may include one or more RAN-CFs. FIG. 3 illustrates that the RAN 302 includes a number of RAN-CFs from the first RAN-CF 306 to a Z-th RAN-CF 308.

[0068] A RAN-CF may be a cloud-based module. It may operate as a cellular network function that is responsible for controlling, for a UE 310, cluster access, mobility, and / or various related configurations. It is contemplated that the UE 310 is served by only a single RAN-CF (e.g., that there is 1:1 relationship between the UE 310 and aRAN-CF). Accordingly, FIG. 3 illustrates that the first RAN-CF 306 is presently active 312 with respect to the UE 310 (the first RAN-CF 306 is ’'serving" the UE 310).

[0069] Note that first RAN-CF 306 could (also) be active for other UE(s). Note also that another RAN-CF (e.g.. the Z-th RAN-CF 308) could be active of other UE(s) served by the RAN.

[0070] Under a scalable RAN architecture, a RAN may include one or more RAN-DFs that are shared across different RAN-CFs to provide data plane (DP) services access to UEs. FIG. 3 illustrates that the RAN 302 includes a number of RAN-DFs, from the first RAN-DF 314 through the M-th RAN-DF 316 and ending at the Y-th RAN-DF 318.84935-4185-2302,1 P70374WO3

[0071] A RAN-DF may be a cloud based module. It may operate as a cellular network function that is responsible for performing one or more access stratum (AS) layer data plane (DP) functionalities. A RAN-DF could be used by one or more than one RAN-CF of the RAN 302. A RAN-DF could use one or more than one RAN-AN of the RAN 302.

[0072] A RAN-CF could serve a UE via one or more RAN-DFs at the same time. FIG.3 illustrates a case where the first RAN-DF 314 through the M-th RAN-DF 316 are active 320 for the UE (the first RAN-DF 314 through the M-th RAN-DF 316 are “serving'’ the UE 310).

[0073] Note that any one or more of the first RAN-DF 314 through the X-th RAN-AN 326 could simultaneously be active for other UE(s) served by the RAN.

[0074] Under a scalable RAN architecture, a RAN may include one or more RAN-ANs that are shared across different RAN functions (e.g., RAN-CF and RAN-DF) to provide UEs with radio access. Note that this is different than architectures used in existing wireless communication systems, where each node in a RAN is associated with a specific base station. FIG. 3 illustrates that the RAN 302 includes a number of RAN-ANs, from the first RAN-AN 322 through the N-th RAN-AN 324 and ending at the X-th RAN-AN 326.

[0075] A RAN-AN may be a cellular RAN node that provides a UE with access to cellular network over radio via one or more carriers. Provided functionalities may include, but are not limited to, physical layer services, scheduling of radio resources, and / or at least part of services from / or a medium access control (MAC) layer, such as hybrid automatic repeat request (HARQ) soft-combing.

[0076] Multiple RAN-ANs can be used to serve a UE. FIG. 3 illustrates a case where the first RAN-AN 322 through the N-th RAN-AN 324 are active 328 for the UE 310 (the first RAN-AN 322 through the N-th RAN-AN 324 are “serving” the UE 310).

[0077] A RAN-AN may provide services to one or more RAN-DFs. Note that any single RAN-AN could be providing services for more than one RAN-DF. For example, in FIG. 3, each of the first RAN-AN 322 through the N-th RAN-AN 324 could be understood to provide services to each of the first RAN-DF 314 through the M-th RAN-DF 316 for purposes of serving the UE 310.

[0078] Note that any one or more of the first RAN-AN 322 through the X-th RAN-AN 326 could simultaneously be active for other UE(s) served by the RAN.94935-4185-2302,1 P70374WO3

[0079] Data between a UPF 330 of the cellular CN 304 that is associated with the UE 310 and the UE 310 is communicated using the set of active 320 RAN-DFs for the UE 310 and the set of active 328 RAN-ANs for the UE 310 (where, for example, the set of active 320 RAN-DFs for the UE 310 and the set of active 328 RAN-AFs for the UE was previously established by the first RAN-CF 306). The UPF 330 interacts directly with the set of RAN-DFs that is active 320 for the UE 310 via a RAN-control function (CF) user plane (UP) interface (IF) (RAN-CF UP IF) 332, as shown.

[0080] FIG. 3 also illustrates that various other CN functions 334 may communicate with the RAN-CFs (e.g., the first RAN-CF 306 through the Z-th RAN-CF 308) via a RAN-CF control plane (CP) IF (RAN-CF CP IF) 336.

[0081] Communication between RAN-CFs and RAN-DFs occurs according to a CF-data function (DF) IF (CF-DF IF) 338 between the set of RAN-CFs and the set of RAN-DFs.

[0082] Communication between RAN-DFs and RAN-AFs occurs according to a DF-access node (AN) IF (DF-AN IF) 340 between the set of RAN-DFs and the set of RAN-ANs.

[0083] The set of RAN-CFs may be understood to control the set of RAN-ANs through the use of a pass-through CF-AN IF 342 that runs between the CF-DF IF 338 and the DF-AN IF 340, as shown.

[0084] FIG. 4 illustrates an example mapping 400 of services and functions as may be used in the scalable RAN architectures disclosed herein. The mapping 400 illustrates functional relationships as between a UE 402, a CN 404, and a RAN-AN 406, a RAN-DF 408, and a RAN-CF 410 of a scalable RAN.

[0085] The UE 402 operates a set of NAS control plane layers 412 that map to a set of CN control plane layers 414 operated at the CN 404.

[0086] The UE 402 operates an AS control plane layer 416 that maps to an AS control plane 418 operated by the RAN-CF 410. This mapping may be used to facilitate RRC layer functionalities for the UE 402. Accordingly, it may be understood that an AS / RAN control plane functionally (e.g., corresponding to a 5G RRC layer) is realized in / via RAN-CF.

[0087] The UE 402 operates AS data plane layers 420 that map to AS data plane layers 422 operated by the RAN-DF 408. This mapping may be used to facilitate radio link104935-4185-2302,1 P70374WO3control (RLC) layer, packet data convergence protocol (PDCP) layer, and / or service data adaptation protocol (SDAP) layer functionalities for the UE 402. Accordingly, it may be understood that AS / RAN data plane functionally, other than MAC and limited services from RLC (e.g., corresponding to 5G SDAP / PDCP / RLC layers) is realized in / via RAN-DF.

[0088] The UE 402 operates AS access layers 424 that map to an AS access layers 426 operated by the RAN-CF 410. This mapping may be used to facilitate MAC and LI layer functionalities for the UE 402. Accordingly, it may be understood that AS / RAN lower layer functionality (e.g., corresponding to 5G PHY / MAC) is realized in / via RAN-AN.

[0089] Returning to FIG. 3, additional details are now provided related to various interfaces illustrated therein. The CF-DF IF 338 that operates within the RAN 302 may be used for establishing, modifying, and / or releasing an AS RB context for a UE and for updating which RAN-AN(s) serve that UE. A RAN-CF can serve a UE via any RAN-DF(s). In other words, there is no limitation that only certain RAN-DFs can be / are used by certain RAN-CFs.

[0090] The DF-AN IF 340 that operates within the RAN 302 may be used for transferring data between a RAN-DF and a RAN-AN in order to facilitate data exchange with a UE. Any RAN-DFs can serve one or more UE(s) via any RAN-AN. In other words, there is no limitation that only certain RAN-ANs can be used by certain RAN-DFs.

[0091] The RAN-CN UP IF 332 that operates between the RAN 302 and the cellular CN 304 may be used for exchanging UE user plane data with the CN. In various cases, UE user plane traffic on certain RB(s) is mapped directly to associated RAN-DF(s) serving that UE.

[0092] The RAN-CN CP IF 336 that operates between the RAN 302 and the cellular CN 304 may be used for exchanging control information with the CN (e.g., access for establishing connection, paging, etc.).

[0093] Various differences of the scalable RAN architecture 300 as compared to architectures used in presently deployed wireless communication systems are now discussed. Within the scalable RAN architecture 300, there is no dedication of radio access nodes or data functions to a particular / certain RAN entity (e.g., to a particular base station). Further, the scalable RAN architecture 300 implements a many-to-many interface concept, where all RAN-CFs could serve their UEs via all / any RAN-DFs, and 114935-4185-2302,1 P70374WO3all RAN-DFs could serve their UEs via all / any RAN-ANs. Still further, RAN-AN(s) that serve a particular UE may be decided dynamically based on UE-to-RAN-AN coverage aspects. Still further, a RAN-CF and RAN-DF(s) used to serve a UE can be decided based on loading within the RAN for these node types and / or based on processing capabilities within the RAN as compared to existing UE requirements.

[0094] FIG. 5 A through FIG. 5D illustrate examples of data transfer using a scalable RAN architecture 500. The scalable RAN architecture 500 may be similar to the scalable RAN architecture 300 previously described. As shown, the scalable RAN architecture 500 includes a RAN 502 and a UE 504.

[0095] As illustrated, the RAN 502 includes a number of RAN-CFs (the first RAN-CF 506 through the Z-th RAN-CF 508), a number of RAN-DFs (the first RAN-DF 510 through the Y-th RAN-DF 512), and a number of RAN-ANs (the first RAN-AN 514, the second RAN-AN 516, and onward through the X-th RAN-AN 518). A CF-DF IF 520 is implemented between the RAN-CFs and the RAN-DFs. A DF-AN IF 522 is implemented between the RAN-DFs and the RAN-ANs. A CF-AN IF 524 is implemented between the CF-DF IF 520 and the DF-AN IF 522.

[0096] The first RAN-CF 506 is active 526 for purposes of providing service to the UE 504 through the RAN 502. Each of the first RAN-DF 510 through the Y-th RAN-DF 512 is active 528 for purposes of providing service to the UE 504 through the RAN 502. Finally, each of the first RAN-AN 514, the second RAN-AN 516. and onward through the X-th RAN-AN 518 is active 530 for purposes of providing service to the UE 504 through the RAN 502.

[0097] A cellular CN 532 implements a UPF 534 that manages each of a first RB 536 and a second RB 538 for a UE 504. The cellular CN 532 also includes other CN functions 540 may be used to configure one or more of the RAN-CFs of the RAN 502.

[0098] Under the scalable RAN architecture 500, there may be a 1: 1 relationship between an RB of the UPF 534 and a RAN-DF through which packets of that RB are managed through the RAN 502. Accordingly, FIG. 5A through FIG. 5D illustrate that the first RB 536 is managed by the first RAN-DF 510 of the RAN 502, while the second RB 538 is managed by the Y-th RAN-DF 512 of the RAN 502.

[0099] FIG. 5A illustrates the traversal of a first packet 542 through the RAN 502. The first packet 542 is a packet of the first RB 536, as shown. The first packet 542 is accordingly delivered from the UPF 534 to the first RAN-DF 510 that manages the first 124935-4185-2302,1 P70374WO3RB 536 via the CF-DF IF 520. Then, the first RAN-DF 510 selects the first RAN- AN 514 for use in delivering the first packet 542 to the UE. Accordingly, the first packet 542 is then delivered from the first RAN-DF 510 to the first RAN- AN 514 via the DF-AN IF 522. Finally, the first RAN-AN 514 delivers the first packet 542 to the UE 504 over the physical radio channel.

[0100] Continuing with the example, FIG. 5B illustrates the traversal of a second packet 544 through the RAN 502. The second packet 544 is a packet of the first RB 536, as shown. The second packet 544 is accordingly delivered from the UPF 534 to the first RAN-DF 510 that manages the first RB 536 via the CF-DF IF 520. Then, the first RAN-DF 510 selects the X-th RAN-AN 518 for use in delivering the second packet 544 to the UE. Accordingly, the second packet 544 is then delivered from the first RAN-DF 510 to the X-th RAN-AN 518 via the DF-AN IF 522. Finally, the X-th RAN-AN 518 delivers the second packet 544 to the UE 504 over the physical radio channel.

[0101] Continuing with the example, FIG. 5C illustrates the traversal of a third packet 546 through the RAN 502. The third packet 546 is a packet of the second RB 538, as shown. The third packet 546 is accordingly delivered from the UPF 534 to the Y-th RAN-DF 512 that manages the second RB 538 via the CF-DF IF 520. Then, the Y-th RAN-DF 512 selects the first RAN-AN 514 for use in delivering the third packet 546 to the UE. Accordingly, the third packet 546 is then delivered from the Y-th RAN-DF 512 to the first RAN-AN 514 via the DF-AN IF 522. Finally, the first RAN-AN 514 delivers the third packet 546 to the UE 504 over the physical radio channel.

[0102] Continuing with the example, FIG. 5D illustrates the traversal of a fourth packet 548 through the RAN 502. The fourth packet 548 is a packet of the second RB 538, as shown. The fourth packet 548 is accordingly delivered from the UPF 534 to the Y-th RAN-DF 512 that manages the second RB 538 via the CF-DF IF 520. Then, the Y-th RAN-DF 512 selects the second RAN-AN 516 for use in delivering the fourth packet 548 to the UE. Accordingly, the fourth packet 548 is then delivered from the Y-th RAN-DF 512 to the second RAN-AN 516 via the DF-AN IF 522. Finally, the second RAN-AN 516 delivers the fourth packet 548 to the UE 504 over the physical radio channel.

[0103] Note that while the example case given in FIG. 5A through FIG. 5D uses two RBs, other RBs of the UE (not illustrated) could be similarly managed by / through any of the RAN-DFs of the RAN (any of the first RAN-DF 510 through the Y-th RAN-DF 512).134935-4185-2302,1 P70374WO3

[0104] Note that in the UL direction, packets of either of the first RB 536 and / or the second RB 538 could be scheduled to any of the set of RAN-ANs for the UE (any of the first RAN-AN 514, the second RAN-AN 516, and onward to the X-th RAN-AN 518) over the physical radio channel. Once delivered to a RAN-AN, that RAN-AN forwards the packet on the DF-AN IF 522 to the one of the RAN-DF(s) (the one of the first RAN-DF 510 through the Y-th RAN-DF 512) that manages that RB. That RAN-DF then sends the packet to the UPF 534 of the cellular CN 532 on the CF-DF IF 520.

[0105] Mobility concepts for scalable RAN architectures discussed herein are now- discussed.

[0106] FIG. 6 illustrates an example of RAN mobility- types within a scalable RAN architecture 600. Note that the scalable RAN architecture 600 may be similar to the scalable RAN architecture 500 previously discussed.

[0107] As illustrated, the scalable RAN architecture 600 may allow for three types of mobility: a UE RAN-AN mobility 602 (also referred to herein as “RAN-AN mobility-’’), a UE RAN-DF mobility 604 (also referred to herein as “RAN-DF mobility”), and a UE RAN-CF mobility 606 (also referred to herein as “RAN-CF mobility”).

[0108] Under UE RAN-AN mobility 602, the network notifies the UE of a modification to the set of RAN-AN nodes of the scalable RAN architecture 600 that are used to serve the UE by triggering RAN-AN change / add / release procedures. This may occur due to UE movement in space. RAN-AN configurations for newly moved-to and / or moved-away-from RAN-ANs are impacted.

[0109] Under UE RAN-DF mobility 604, the network notifies the UE of a modification of RAN-DF(s) serving RB(s) of the UE by triggering an RB change procedure. As part of this RB change procedure, RB(s) can be moved from one serving RAN-DF to another. This may be done due to network load balancing needs, due to RB quality- of service (QoS) requirement changes, etc. RAN-DF configurations for newly moved-to and / or moved-away-from RAN-DFs are impacted.

[0110] Under UE RAN-CF mobility 606, the network notifies the UE of a modification of RAN-CF node that serves the UE. This is done by triggering RAN-CF change / add / release procedures. This may be done due to network load balancing needs. In some cases, this change may- be due to UE movement beyond a geographical area controlled by a present / former RAN-CF (e.g., across countries, across operators, etc ).144935-4185-2302,1 P70374WO3RAN-CF configurations for newly moved-to and / or moved-away-from RAN-CFs are impacted.[OHl] It is contemplated that a UE can execute handovers within the RAN-AN layer, the RAN-DF layer, or the RAN-CF layer independently, without necessarily affecting the other layers. Providing for this t pe of independently-layered handover within the scalable RAN architecture 600 has various UE-side benefits. For example, a layer-wise handover limits a number of configurations and / or state variables being impacted (e.g., as compared to a case of handover in cases of existing wireless communication systems). Accordingly, UE handover impacts (e.g., latency) are reduced.

[0112] For example, it may be understood that there is a case where UE physical movement only requires changes to UE-radio interface link with serving RAN-AN(s), without any need to change UE links with presently active RAN-DF(s) and the presently active RAN-CF for the UE. In such a case, the amount of information needs to be exchanged between the UE and RAN during physical mobility7to account for the changes in RAN-AN configuration is limited only to RAN-AN configuration updates. This amount of information may be reduced as compared to handover information that may be needed for mobility between base stations of, for example, current implementations of 5G RAN.

[0113] Aspects of RAN-AN mobility are now discussed in additional detail.

[0114] For purposes of facilitating comparison between existing systems and the improved systems described herein, FIG. 7A and FIG. 7B together provide an illustration of existing 5G mobility framework 700 for the mobility of a UE 702 as in existing 5G wireless communication systems. A RAN 704 between the core network 706 and the UE 702 includes a first base station 708 and a second base station 710. The first base station 708 implements a first CU-CP function 712, a first CU-UP function 714, and operates a first distributed unit (DU) 716 and a second DU 718. The second base station 710 implements a second CU-CP function 720, a second CU-UP function 722, and operates a third DU 724 and a fourth DU 726.

[0115] As shown in FIG. 7A, the UE 702 is initially served through the first base station 708 (through the second DU 718 of the first base station 708).

[0116] FIG. 7B proceeds to illustrate that, due to the UE motion 728 of the UE 702 in physical space, a handover of the UE 702 from the first base station 708 to the second base station 710 (such that the UE is now served by the third DU 724 of the second base 154935-4185-2302,1 P70374WO3station 710) has occurred. Attendant to that handover, there has been a contextual mobility at each of the LI, L2, and L3 levels. For example, as shown, there has been an LI context mobility 730 between the second DU 718 of the first base station 708 and the third DU 724 of the second base station 710, an L2 context mobility 732 between the first CU-UP function 714 of the first base station 708 and the second CU-UP function 722 of the second base station 710, and an L3 context mobility 734 between the first UUCP function 712 of the first base station 708 and the second CU-CP function 720 of the second base station 710.

[0117] In such a case, the UE updates its configurations at each of the LI. L2, and L3 layers. In other words, for the inter-base-station / 5G mobility case illustrated in FIG. 7A and FIG. 7B, LI, L2 and L3 context mobilities are each executed.

[0118] FIG. 8A and FIG. 8B together provide an illustration of a RAN-AN mobility framework 800 for the mobility of a UE 802 in a wireless communication system implementing the scalable RAN architectures discussed herein. A UE 802 uses a RAN 804 to communicate with a CN 806. The RAN 804 is an example of a scalable RAN architecture. Accordingly, the RAN 804 includes various RAN-CFs (the first RAN-CF 808, the second RAN-CF 810, and the third RAN-CF 812), various RAN-DFs (the first RAN-DF 814, the second RAN-DF 816, and the third RAN-DF 818), and various RAN-ANs (the first RAN-AN 820, the second RAN-AN 822, the third RAN-AN 824, and the fourth RAN-AN 826).

[0119] In this example, each of the CN 806, the first RAN-CF 808, the second RAN-CF 810, the third RAN-CF 812, the first RAN-DF 814, the second RAN-DF 816, and the third RAN-DF 818 are entities of the cloud 828, as shown. The second RAN-CF 810 and the second RAN-DF 816 are both active 834 for use at the UE (where the second RAN-CF 810 performs RAN-CF functions for the UE 802 and where the second RAN-DF 816 performs RAN-DF functions for at least one RB of the UE 802).

[0120] FIG. 8A illustrates that the UE 802 is initially served by the second RAN-AN 822 of the RAN 804.

[0121] FIG. 8B proceeds to illustrate that, due to the UE motion 830 of the UE 802 in physical space, mobility of the UE 802 from the second RAN-AN 822 (the “source RAN-AN”) to the third RAN-AN 824 (the “target RAN-AN”), such that the UE is now served by the third RAN-AN 824, has occurred. Attendant to that mobility, there has164935-4185-2302,1 P70374WO3been an LI context mobility 832 between the second RAN-AN 822 and the third RAN-AN 824.

[0122] Note that within the RAN-AN mobility framework 800, the second RAN-CF 810 is responsible for an L3 context of the UE 802 and the second RAN-DF 816 is responsible for an L2 context of the UE 802. Further, the second RAN-CF 810 and the second RAN-DF 816 are, architecturally speaking, capable of continuing to be active for the UE 802 going forward with the UE 802 at either of the second RAN-AN 822 or the third RAN-AN 824. Accordingly, when the UE 802 changes from the second RAN-AN 822 to the third RAN-AN 824, only the LI context mobility 832 is executed (no L2 context mobility or L3 context mobility is executed).

[0123] Accordingly, it will be understood that, as compared to the existing 5G mobility framework 700 of FIG. 7A and FIG. 7B, the handover of the RAN-AN mobility framework 800 of FIG. 8A and FIG. 8B represents relatively fewer configurational actions within / between RAN entities. This means that the mobility of the UE 802 as shown in FIG. 8A and FIG. 8B corresponds to a lessened service disruption time as compared to that which applies for the UE 702 of FIG. 7A and FIG. 7B.

[0124] FIG. 9 illustrates a timeline 902 and a corresponding chart 904 of an execution of RAN-AN mobility7from a first RAN-AN (RAN-AN #1) to a second RAN-AN (RAN-AN #2), according to embodiments discussed herein. The UE 906 uses each of a RAN-AN #1 LI config 908, a RAN-AN #2 LI config 910, and a unified L2 configuration 912. Note that, as illustrated by the chart 904) the RAN-AN #1 LI config 908 and the RAN-AN #2 LI config 910 are both compatible with the use of the unified L2 configuration 912 at the UE 906.

[0125] At the beginning of the timeline 902, the UE 906 is served by RAN-AN #1, and thus the RAN-AN #1 LI config 908 and the unified L2 configuration 912 are active for the UE 906. The RAN-ANs of the system (the RAN-AN #1 and the RAN-AN #2) are then configured 914 for measurement. The UE 906 accordingly proceeds to perform the configured LI measurements 916 (e.g., of both of the RAN-AN #1 and the RAN-AN #2).

[0126] As a result of the LI measurements 916, the UE 906 is instructed to switch from RAN-AN #1 to RAN-AN #2. Accordingly, pre-synchronization 922 to RAN-AN #2 is performed. RAN-AN #2 is then added 918 for the UE 906. Then, the RAN-AN #2 LI config 910 is activated 924.174935-4185-2302,1 P70374WO3

[0127] Note that as a result of the activation of the RAN-AN #2 LI config 910, there is a period 926 during which each of the RAN-AN #1 and RAN-AN #2 are active at and usable by the UE 906. The RAN-AN #2 addition is deemed complete 928 after some non-zero running of this period 926, as shown. Once the RAN-AN #2 addition is deemed complete 928, RAN-AN #1 is released 920 by the UE 906.

[0128] Note that in this case there is no reconfiguration requirement 930 for the unified L2 configuration 912 (the same unified L2 configuration 912 can be used with the UE 906 while it is served at either and / or both of the RAN-AN #1 and / or the RAN-AN #2).

[0129] RAN-AN mobility embodiments described herein (e.g., as illustrated here in FIG. 9) exhibit various benefits. First, under such RAN-AN mobility embodiments, there is potentially no interruption for data service at the UE 906. Second, the RAN-AN mobility embodiments are robust, in that they confirm that there is a successful addition of a new RAN-AN prior to the release of the prior RAN-AN. Finally, note that the complexity for RAN-AN mobility is less than that exhibited in, for example, L1 / L2 triggered mobility' (LTM) schemes and / or dual active protocol stacks (DAPS) schemes that are used in some current wireless communication systems.

[0130] The improvements are enabled by the use of unified L2 configurations (e.g., the unified L2 configuration 912) and the use of LI multi-node connectivity frameworks.

[0131] FIG. 10 illustrates an example flow diagram 1000 for RAN-AN mobility', according to embodiments discussed herein. The flow diagram 1000 illustrates communications between / among a UE 1002, a first RAN-AN 1004, a second RAN-AN 1006, a RAN-DF 1008, a RAN-CF 1010, and a CN user plane function 1012. The first RAN-AN 1004, the second RAN-AN 1006, the RAN-DF 1008, and the RAN-CF 1010 are understood of entities of a scalable RAN 1014 as discussed herein. It is presumed that at the beginning of the flow diagram 1000, the first RAN-AN 1004, the RAN-DF 1008, and the RAN-CF 1010 are active for purposes of serving the UE 1002.

[0132] As illustrated, the UE 1002 generates a measurement report (of one or more cell(s) on one or more RAN-AN(s)), generates a UL air-message 1016 that includes the measurement report, and sends that UL air-message 1016 by way of the first RAN-AN 1004 and the RAN-DF 1008 to the RAN-CF 1010. Upon receiving this measurement report, the RAN-CF 1010 determines 1018 that the UE 1002 should be served by the second RAN-AN 1006 instead of by the first RAN-AN 1004.184935-4185-2302,1 P70374WO3

[0133] Accordingly, the RAN-CF 1010 sends the second RAN-AN 1006 an add UE context request message 1020 that identifies the UE 1002 to the second RAN-AN 1006. Service profile information for the UE 1002 and / or cell measurements taken by UE 1002 may also be included in the add UE context request message 1020.

[0134] The second RAN-AN 1006 responds with an add UE context confirmation message 1022 that confirms that the second RAN-AN 1006 is prepared to operate with the UE 1002 and that provides a configuration (e.g., an LI configuration) for the second RAN-AN 1006 for the UE 1002 to use with the second RAN-AN 1006.

[0135] The RAN-CF 1010 then sends a DL air-message 1024 to the UE 1002 by way of the RAN-DF 1008 and the first RAN-AN 1004 that includes a reconfiguration message instructing the UE 1002 to add the second RAN-AN 1006 and an instruction for the UE to release the first RAN-AN 1004. The included reconfiguration message may include the configuration information for the second RAN-AN 1006 that is for use by the UE 1002 that was provided to the RAN-CF 1010 by the second RAN-AN 1006.

[0136] Upon receiving this message, the UE 1002 applies 1026 the configuration information for the second RAN-AN 1006. Note that the while the UE 1002 is preparing to use the second RAN-AN 1006 in this manner, data transfer 1028 between the UE 1002 and the CN user plane function 1012 by way of the first RAN-AN 1004 and the RAN-DF 1008 continues, as shown.

[0137] Once the configuration information is applied 1026, the UE 1002 generates a UL air-message 1030 containing an indication that the reconfiguration of the UE to use the second RAN-AN 1006 is complete, and sends the UL air-message 1030 to the RAN-CF 1010 by way of the first RAN-AN 1004 and the RAN-DF 1008, as illustrated.

[0138] The UE 1002 then initiates an initial access 1032 with the second RAN-AN 1006 (e.g., the UE 1002 sends a random access (RA) request to the second RAN-AN 1006). The initial access 1032 may be based on the configuration information for the second RAN-AN 1006 that the UE 1002 received from the RAN-CF 1010.

[0139] One the initial access 1032 of the UE 1002 of the with the second RAN-AN 1006 is successful 1036, the second RAN-AN 1006 sends a UE link status message 1034 indicating that the UE 1002 is active at the second RAN-AN 1006 to the RAN-CF 1010.

[0140] The RAN-CF 1010 then sends the RAN-DF 1008 a modify UE RAN-AN list request message 1038 to the RAN-DF 1008. This message instructs the RAN-DF 1008 to release the use of the first RAN-AN 1004 in the set of RAN-ANs for the UE 1002 and to 194935-4185-2302,1 P70374WO3add the use of the second RAN-AN 1006 into the set of RAN-ANs for the UE 1002. Once this message is received at the RAN-DF 1008 and correspondingly carried out by the RAN-DF 1008, the RAN-DF 1008 responds to the RAN-CF 1010 with a modify UE RAN-AN list confirm message 1040.

[0141] Going forward, data transfer 1042 between the UE 1002 and the CN user plane function 1012 occurs by way of the second RAN-AN 1006 and the RAN-DF 1008, as shown.

[0142] FIG. 11 illustrates an example flow diagram 1100 for RAN-AN mobility, according to embodiments discussed herein. The flow diagram 1100 illustrates communications between / among a UE 1002, a RAN-AN cluster 1104 that includes the S-th RAN-AN 1106 and the T-th RAN-AN 1108, a RAN-DF 1110, and a RAN-CF 1112. The RAN-ANs of the RAN-AN cluster 1104, the RAN-DF 1110, and the RAN-CF 1112 are understood of entities of a scalable RAN as discussed herein. It is presumed that at the beginning of the flow diagram 1100, the UE 1102 is in connected mode and being served 1114 by the S-th RAN-AN 1106, and thus that the S-th RAN-AN 1106, the RAN-DF 1110, and the RAN-CF 1112 are active for purposes of serving the UE 1002.

[0143] The UE 1102 generates and sends L3 measurement reports 1116 to the RAN-CF 1112. Based on these L3 measurement reports 1116, the RAN-CF 1112 sends the UE 1102 a RAN-AN cluster configuration message 1118 that identifies a RAN-AN cluster (in the illustrated case, the RAN-AN cluster 1104) to the UE 1102 for purposes of presynchronization and / or LI measurement. The RAN-AN cluster configuration message 1118 configures the UE with LI measurement configuration information and RRC configuration information for control resource set(s) (CORESET(s)), HARQ(s), physical uplink control channel (PUCCH) resource(s), and / or tracking area group(s) (TAG(s)) for the RAN-ANs of the RAN-AN cluster 1104. The UE 1102 proceeds to perform LI measurement of and pre-synchronization with the RAN-ANs of the RAN-AN cluster 1104.

[0144] The UE 1102 then performs LI measurement and pre-synchronization 1120 with the RAN-ANs of the RAN-AN cluster 1104 using the received configuration information.

[0145] One of the RAN-ANs of the RAN-AN cluster 1104 (in the illustrated case, the T-th RAN-AN 1108) correspondingly sends the RAN-CF 1112 a pre-sync report 1122 that identifies ones of the RAN-AN cluster 1104 with which the UE 1102 successfully204935-4185-2302,1 P70374WO3performed pre-synchronization. The network then proceeds to perform RAN-AN UE context and L2 configuration setup procedure 1124 across the RAN-DF 1110 and the RAN-AN cluster 1104. Note that due to the RAN-AN UE context and L2 configuration setup procedure 1124, the UE 1102 has no need to prepare or change L2 contexts for the RAN-ANs of the RAN-AN cluster 1104.

[0146] Aspects for adding a new RAN-AN of the RAN-AN cluster 1104 for service for the UE 1102 are now discussed. Assume that, as just described, the UE 1102 is served currently by the S-th RAN-AN 1106, and that the T-th RAN-AN 1108 of the RAN-AN cluster 1104 is to be added for service for the UE 1102. This addition can be executed 1126 according to various mechanisms. A first possible mechanism uses medium access control control element (MAC CE) signaling to instruct the addition of the T-th RAN-AN 1108. Another possible mechanism uses UE-side pre-configured threshold(s) (e.g., measurement threshold(s) for the T-th RAN-AN 1108) that represent conditions that, when met, cause the T-th RAN-AN 1108 to be added for the UE 1102. Another possible mechanism uses RRC signaling from the RAN-CF 1112 to instruct the addition of the T-th RAN-AN 1108.

[0147] In response to receiving the messaging corresponding to one of these mechanisms for the T-th RAN-AN 1108, the UE 1102 activates 1128 the RRC configuration for the T-th RAN-AN 1108. Note, however, that data transfer through the network for the UE 1102 is still continued through the S-th RAN-AN 1106. In some cases, a data status transfer message 1130 is sent by the S-th RAN-AN 1106 to the T-th RAN-AN 1108 for the purpose of transferring PDU status information to the T-th RAN-AN 1108.

[0148] The S-th RAN-AN 1106 then sends the RAN-DF 1110 an activation request message 1132 requesting that the T-th RAN-AN 1108 be activated for the UE 1102.

[0149] After the activation request message 1132 is sent, there is multi-RAN-A connectivity 1134 for the UE 1102 through each of the S-th RAN-AN 1106 and the T-th RAN-AN 1108. Corresponding to this status, in DL, data can be duplicated, while in UL, data may be jointly received in the selected TAG.

[0150] When network confirms the success of target RAN-AN addition (in this case, the success of the addition of the T-th RAN-AN 1108), it may decide to remove some or all of the source RAN-AN(s) for the UE (the UE 1102). Accordingly, the flow diagram 1100 illustrates that the RAN-CF 1112 sends a release request message 1136 to the UE214935-4185-2302,1 P70374WO31102 that requests the release of the S-th RAN-AN 1106 from serving the UE 1102. In response to the release request message 1136. the UE 1102 releases 1138 its configuration for the S-th RAN-AN 1106 and stops 1140 sending PUSCH transmissions to the S-th RAN-AN 1106. The S-th RAN-AN 1106 correspondingly stops 1140 DL transmissions to the UE 1102.

[0151] The UE 1102 then sends the RAN-CF 1112 a RAN-AN release indication message 1142 informing the RAN-CF 1112 that the S-th RAN-AN 1106 is released from serving the UE 1102. The S-th RAN-AN 1106 then correspondingly stops 1144 expecting PUCCH transmissions from the UE 1102.

[0152] Note that an implementation for RAN-AN mobility according to the flow diagram 1100 provides various advantages with respect to handover efficiency and / or speed while having a low associated complexity. For example, in the flow diagram 1100, the UE is always connected to at least one of the S-th RAN-AN 1106 and the T-th RAN-AN 1108 (which promotes reliable data transfer through the change), while the use of pre-synchronization across the RAN-ANs of the RAN-AN cluster 1104 allows an eventually-selected target RAN-AN (in this case, the T-th RAN-AN 1108) to be added quickly.

[0153] Aspects of RAN-DF mobility7are now discussed in additional detail.

[0154] FIG. 12 illustrates a visualization of an RB context 1202 as may be understood within a scalable RAN as disclosed herein. As shown, an operative RB context 1202 for an RB may include L2 state variables 1204 for the RB, RB L2 configurations 1206 for the RB, and / or security parameters 1208 for the RB (e.g., security keys used by the RB, identifications of / for security algorithms used by the RB, etc.).

[0155] In scalable RANs as discussed herein, UE RB mobility as between RAN-DFs (“RAN-DF mobility”) may be implemented. The network may determine that a UE RB should be moved from one RAN-DF (a “source RAN-DF”) to another RAN-DF (a “target RAN-DF”). This may be done as part of, for example, a load balancing mechanism that controls the distribution of RBs across the RAN-DFs.

[0156] There are multiple possible modes for RAN-DF mobility. FIG. 13A illustrates a transparent RAN-DF mobility mode 1302 ("Mode #A"), where RB context information (RB configurations, state variables, and / or security parameters, etc.) is not updated / changed when the RB is moved. For example, as shown in FIG. 13 A, the system determines 1304 that the an RB at source RAN-DF 1306 is to be transferred a target 224935-4185-2302,1 P70374WO3RAN-DF 1308. Corresponding to this case, the configuration information for the RB is transparently transferred 1310 from the source RAN-DF 1306 to the target RAN-DF 1308 (there is no change to the configuration information as part of this transfer 1310). In this case, there is also no impact 1312 on the UE-side configuration information 1314 for the RB.

[0157] FIG. 13B illustrates a non-transparent RAN-DF mobility mode 1316 ("Mode #B"), where RB context information (RB configurations, state variables, and / or security parameters, etc.) is updated 1318 for use by the target RAN-DF. For example, as shown in FIG. 13B. the system determines 1320 that the an RB at source RAN-DF 1322 is to be transferred to a target RAN-DF 1324. Corresponding to this case, when / as this configuration information is transferred 1326, it is updated 1318 from the version used the source RAN-DF 1306 into new context information 1328. This new context information 1328 is what is used by the target RAN-DF 1308.

[0158] Further, in this case, UE-side configuration information 1330 is also updated 1318 to implement corresponding new context information 1332 for the RB at the UE-side (as shown).

[0159] FIG. 14 illustrates an example flow diagram 1400 for transparent RAN-DF mobility7, according to embodiments discussed herein. The flow diagram 1400 illustrates communications between / among a UE 1402, a RAN-AN 1404, a first RAN-DF 1406, a second RAN-DF 1408, a RAN-CF 1410, and a CN user plane function 1412. The RAN-AN 1404, the first RAN-DF 1406, the second RAN-DF 1408, and the RAN-CF 1410 are understood of entities of a scalable RAN 1414 as discussed herein. It is presumed that at the beginning of the flow diagram 1400, the RAN-AN 1404, the first RAN-DF 1406, and the RAN-CF 1410 are active for purposes of serving the UE 1402.

[0160] Initially, data transfer 1416 on a first radio bearer ("RBI") between the UE 1402 and the CN user plane function 1412 occurs by way of one or more RAN-AN(s) (including the first RAN-AN 1404) and the first RAN-DF 1406. as shown. Then, the RAN-CF 1410 determines 1418 that the serving RAN-DF for RBI is to be changed from the first RAN-DF 1406 to the second RAN-DF 1408. Accordingly, the RAN-CF 1410 sends the first RAN-DF 1406 an RB data path switching request message 1420. The RB data path switching request message 1420 identifies the UE 1402 and RBI to the first RAN-DF 1406 and indicates a request for RBI to be switched to the control of the second RAN-DF 1408.234935-4185-2302,1 P70374WO3

[0161] In response, the first RAN-DF 1406 sends the second RAN-DF 1408 an RB addition request message 1422 that identifies the UE 1402 and RBI and that further includes the RB context information for RBI (e.g., RB configurations, state variables, and / or security parameters, etc., for RBI). The second RAN-DF 1408 replies back to the first RAN-DF 1406 with an RB addition confirmation message 1424 that indicates that the second RAN-DF 1408 is ready to manage RBI according to the provided RB context information. Note that corresponding to the transparent RAN-DF mobility case presently under discussion, no change to the this RB context information is made at / for the second RAN-DF 1408.

[0162] The first RAN-DF 1406 then sends the CN user plane function 1412 a path switch request message 1426 that identifies the UE 1402 and RBI to the CN user plane function 1412 and that indicates a request for RBI to be switched to the control of the second RAN-DF 1408. The CN user plane function 1412 replies back to the first RAN-DF 1406 with a path switch confirmation message 1428 that indicates that the CN user plane function 1412 understands that RBI is to use the second RAN-DF 1408 instead of the first RAN-DF 1406. After receiving the path switch confirmation message 1428, the first RAN-DF 1406 sends the RAN-CF 1410 an RB datapath switching confirmation message 1430.

[0163] The first RAN-DF 1406 then forwards any pending DL data to the second RAN-DF 1408 using a data forwarding indication message 1432. The data forwarding indication message 1432 identifies the UE 1402 and RBI and includes a listing of any DL packets that are presently pending for the UE 1402 on RBI.

[0164] The RAN-CF 1410 sends the second RAN-DF 1408 a modify UE RAN-AN list message 1434 that identifies the UE 1402 and any RAN-AN(s) of the scalable RAN 1414 that are currently active for the UE 1402 (e.g., the RAN-AN 1404 and any other additional RAN-AN(s) that are also active for the UE 1402, as the case may be).

[0165] The second RAN-DF 1408 sends any RAN-AN(s) of the scalable RAN 1414 that are currently active for the UE 1402 (e.g., the RAN-AN 1404 and any other additional RAN-AN(s) that are also active for the UE 1402, as the case may be) an update serving RAN-DF indication message 1436 that identifies the UE 1402 and RBI, and that indicates that target RAN-DF for RBI is the second RAN-DF 1408 going forward. Accordingly, these RAN-AN(s) are aware that UE UL data for RBI should be forwarded to the second RAN-DF 1408 going forward.244935-4185-2302,1 P70374WO3

[0166] Accordingly, going forward, data transfer 1438 on RBI between the UE 1402 and the CN user plane function 1412 occurs by way of one or more RAN-AN(s) (including the first RAN-AN 1404) and the second RAN-DF 1408, as shown

[0167] FIG. 15 illustrates an example flow diagram 1500 for non-transparent RAN-DF mobility, according to embodiments discussed herein. The flow diagram 1500 illustrates communications between / among a UE 1502, a RAN-AN 1504, a first RAN-DF 1506, a second RAN-DF 1508, a RAN-CF 1510, and a CN user plane function 1512. The RAN-AN 1504, the first RAN-DF 1506, the second RAN-DF 1508, and the RAN-CF 1510 are understood of entities of a scalable RAN 1514 as discussed herein. It is presumed that at the beginning of the flow diagram 1500, the RAN-AN 1504, the first RAN-DF 1506, and the RAN-CF 1510 are active for purposes of serving the UE 1502.

[0168] Initially, data transfer 1516 on a first radio bearer ("RBI") between the UE 1502 and the CN user plane function 1512 occurs by way of one or more RAN-AN(s) (including the first RAN-AN 1504) and the first RAN-DF 1506, as shown. Then, the RAN-CF 1510 determines 1518 that the serving RAN-DF for RBI is to be changed from the first RAN-DF 1506 to the second RAN-DF 1508. Accordingly, the RAN-CF 1510 sends the first RAN-DF 1506 an RB data path switching request message 1520. The RB data path switching request message 1520 identifies the UE 1502 and RBI to the first RAN-DF 1506 and indicates a request for RBI to be switched to the control of the second RAN-DF 1508.

[0169] In response, the first RAN-DF 1506 sends the second RAN-DF 1508 an RB addition request message 1522 that identifies the UE 1502 and RBI and that further includes the RB context information for RBI (e.g., RB configurations, state variables, and / or security’ parameters, etc., for RBI). The second RAN-DF 1508 replies back to the first RAN-DF 1506 with an RB addition confirmation message 1524 that indicates that the second RAN-DF 1408 is ready to manage RBI and that includes a new / updated context information for RBI as will be used by / at the second RAN-DF 1508.

[0170] The first RAN-DF 1506 then sends the CN user plane function 1512 a path switch request message 1526 that identifies the UE 1502 and RBI to the CN user plane function 1512 and that indicates a request for RBI to be switched to the control of the second RAN-DF 1508. The CN user plane function 1512 replies back to the first RAN-DF 1506 with a path switch confirmation message 1528 that indicates that the CN user plane function 1512 understands that RBI is to use the second RAN-DF 1508 instead of254935-4185-2302,1 P70374WO3the first RAN-DF 1506. After receiving the path switch confirmation message 1528, the first RAN-DF 1506 sends the RAN-CF 1510 an RB data path switching confirmation message 1530 that includes the new context information for RBI that is to be used at / by the second RAN-DF 1508.

[0171] The first RAN-DF 1506 then forwards any pending DL data to the second RAN-DF 1508 using a data forwarding indication message 1532. The data forwarding indication message 1532 identifies the UE 1502 and RBI and includes a listing of any DL packets that are presently pending for the UE 1502 on RBI.

[0172] The RAN-CF 1510 sends a signaling air-message reconfiguration request 1534 to the UE 1502 by way of the first RAN-DF 1506 and the RAN-AN 1504. This signaling air-message reconfiguration request 1534 informs the UE 1502 of the new / updated context information for RBI that is to be used at / by the second RAN-DF 1508. The UE 1502 responds with a signaling air-message reconfiguration confirmation 1536 indicating that it is prepared to use the RBI with the second RAN-DF 1508 according to the new / updated context information.

[0173] The RAN-CF 1510 sends the second RAN-DF 1508 a modify UE RAN-AN list message 1538 that identifies the UE 1502 and any RAN-AN(s) of the scalable RAN 1514 that are currently active for the UE 1502 (e.g., the RAN-AN 1504 and any other additional RAN-AN(s) that are also active for the UE 1502, as the case may be).

[0174] The second RAN-DF 1508 sends any RAN-AN(s) of the scalable RAN 1514 that are currently active for the UE 1502 (e.g., the RAN-AN 1504 and any other additional RAN-AN(s) that are also active for the UE 1502, as the case may be) an update serving RAN-DF indication message 1540 that identifies the UE 1502 and RBI, and that indicates that target RAN-DF for RBI is the second RAN-DF 1508 going forward. Accordingly, these RAN-AN(s) are aware that UE UL data should be forwarded to the second RAN-DF 1508 going forward.

[0175] Accordingly, going forward, data transfer 1542 on RBI between the UE 1502 and the CN user plane function 1512 occurs by way of one or more RAN-AN(s) (including the first RAN-AN 1504) and the second RAN-DF 1508, as shown.

[0176] Aspects of RAN-CF mobility are now discussed in additional detail.

[0177] The network may determine that a UE that is served by a first RAN-CF (a "source RAN-CF’7) should instead be served by a second RAN-CF (a "target RAN-CF”).264935-4185-2302,1 P70374WO3Such determinations may be taken for reasons of, for example, load balancing across a set ofRAN-CFs.

[0178] FIG. 16 illustrates an example flow diagram 1600 for RAN-CF mobility, according to embodiments discussed herein. The flow diagram 1600 illustrates communications between / among a UE 1602, a RAN-AN 1604, a RAN-DF 1606. a first RAN-CF 1608, a second RAN-CF 1610, and a CN user plane function 1612. The RAN-AN 1604, the RAN-DF 1606, the first RAN-CF 1608, and the second RAN-CF 1610 are understood of entities of a scalable RAN 1614 as discussed herein. Initially, control of the service of the UE 1602 by / through the scalable RAN 1614 is managed by first RAN-CF 1608.

[0179] The first RAN-CF 1608 determines 1616 that the serving RAN-CF for the UE 1602 is to be changed from the first RAN-CF 1608 to the second RAN-CF 1610.Accordingly, the first RAN-CF 1608 sends the second RAN-CF 1610 a UE transfer request message 1618 that identifies the UE 1602 and corresponding UE-RAN context information for the UE 1602 to the second RAN-CF 1610. The second RAN-CF 1610 responds with a UE transfer configuration message 1620 that identifies the UE 1602 back to the first RAN-CF 1608, that includes new / modified UE-RAN context information (e.g., modified RAN-CF configurations (L3 configurations)) for the UE, and includes a UE-RAN ID that is to be used for the UE by the second RAN-CF 1610. Note that this UE-RAN ID may be configured such that the (new / modified) UE-RAN context information for the UE used by the second RAN-CF 1610 and / or the second RAN-CF 1610 itself is identifiable. Note that this UE-RAN ID may be considered part of the updated / modified UE-RAN context information.

[0180] Note also that UE-RAN context information used by that UE may include aspects such as, for example, conditional addition / reconfiguration features, minimization of drive tests (MDTs) / self organizing network (SON) parameters, paging configurations for the UE 1602, etc.

[0181] Corresponding to such RAN-CF mobility cases, there may be no need to change any L2 configurations (e.g., RB configurations) or any LI configurations (e.g., serving RAN-AN configurations) used by / for the UE.

[0182] The first RAN-CF 1608 then sends the UE 1602 a signaling air-message 1622 that identifies the new / modified UE-RAN context information to the UE 1602 and that acts as a reconfiguration request for the UE 1602 to use the new / modified UE-RAN274935-4185-2302,1 P70374WO3context information going forward. The UE replies with a signaling air-message 1624 that confirms that the UE has / will perform such a reconfiguration using the new / modified UE-RAN context information.

[0183] The first RAN-CF 1608 then sends the second RAN-CF 1610 a UE transfer complete indication message 1626 that identifies the UE 1602 and any RAN-AN(s) of the scalable RAN 1614 that are currently active for the UE 1602 (e.g., the RAN-AN 1604 and any other additional RAN-AN(s) that are also active for the UE 1602, as the case may be).

[0184] The second RAN-CF 1610 then sends any RAN-DF(s) serving the UE 1602 (e.g., the RAN-DF 1606 and any other applicable RAN-DF(s)) a RAN-CF update indication message 1628 that informs those RAN-DF(s) that service of the UE 1602 through the scalable RAN 1614 is controlled by the second RAN-CF 1610 going forward.

[0185] Aspects of serving RAN-AN scaling for a UE are now discussed in additional detail.

[0186] A number of RAN-ANs that are active for purposes of serving a UE may be dynamically changed. For example, RAN-AN(s) may be made active for a UE or removed from activity for a UE based on UE data transfer needs, QoS requirements of the UE with respect to throughput and / or latency, etc.

[0187] FIG. 17 illustrates an example flow diagram 1700 for RAN-AN scaling for a UE, according to embodiments discussed herein. The flow diagram 1700 illustrates communications between / among a UE 1702, a first RAN-AN 1704, a second RAN-AN 1706, a RAN-DF 1708, a RAN-CF 1710, and a CN user plane function 1712. The first RAN-AN 1704, the second RAN-AN 1706, the RAN-DF 1708, and the RAN-CF 1710 are understood of entities of a scalable RAN 1714 as discussed herein. It is presumed that at the beginning of the flow diagram 1700, the first RAN-AN 1704, the RAN-DF 1708, and the RAN-CF 1710 are active for purposes of serving the UE 1702.

[0188] Preliminarily, the UE 1702 sends the RAN-CF 1710 a UL air-message 1716 by way of the first RAN-AN 1704 and the RAN-DF 1708. The UL air-message 1716 includes measurements of one or more cells served by one or more RAN-ANs. These measurements could include, for example, measurements of cells on RAN-ANs that are not currently active for the UE (e.g., cell(s) of the second RAN-AN 1706).284935-4185-2302,1 P70374WO3

[0189] Further, the RAN-DF 1708 that serves the UE has identified that there is data congestion at the UE 1702. Accordingly, the RAN-DF 1708 sends the RAN-CF 1710 a UE load indication message 1718 that indicates that there is a high data load for the UE.

[0190] In response to the UE load indication message 1718 the RAN-CF 1710 determines to increase capacity for the UE 1702. The RAN-CF 1710 determines 1720. based on the measurements provided in the UL air-message 1716, one or more additional CCs of the first RAN-AN 1704 to add at the UE 1702, and / or determines 1720 to add the second RAN-AN 1706 to the set of RAN-ANs serving the UE 1702 (e.g., the RAN-CF 1710 determines 1720 one or more CCs of the second RAN-AN 1706 that should be used to serve the UE 1702). Note that the balance of the flow diagram 1700 illustrates the case where the RAN-CF 1710 determines 1720 to perform both of these options. However, in other embodiments, only one or the other option could be instead implemented.

[0191] The RAN-CF 1710 sends the first RAN-AN 1704 a modify UE context request message 1724 that identifies the UE 1702, identifies a service profile for the UE 1702, and that includes one or more cell measurements for cells of the first RAN-AN 1704 that were previously taken by the UE 1702. In response, the first RAN-AN 1704 sends the RAN-CF 1710 a modify UE context confirmation message 1726 providing RAN-AN configuration information for the UE 1702 to use to operate on one or more additional cells of the first RAN-AN 1704.

[0192] The RAN-CF 1710 sends the second RAN-AN 1706 an add UE context request message 1728 that identifies the UE 1702, identifies a service profile for the UE 1702, and that includes one or more cell measurements for cells of the second RAN-AN 1706 that were previously taken by the UE 1702. In response, the second RAN-AN 1706 sends the RAN-CF 1710 an add UE context confirmation message 1730 providing RAN-AN configuration information for the UE 1702 to use to operate on one or more additional cells of the second RAN-AN 1706. The add UE context confirmation message 1730 may also include a listing of neighbor RAN-AN(s) to the second RAN-AN 1706 (thereby- making the RAN-CF 1710 aware of these neighbor RAN-AN(s) in the event that the RAN-CF 1710 is not already aware of them).

[0193] The RAN-CF 1710 then sends the UE 1702 a DL signaling air-message 1732 that identifies the UE 1702 and that includes reconfiguration information for the UE 1702. This reconfiguration information may include the RAN-AN configuration information provided by the first RAN-AN 1704 that, when applied by the UE 1702,294935-4185-2302,1 P70374WO3causes the UE 1702 to add the one or more additional cells of the first RAN-AN 1704 previously discussed. The reconfiguration message may further include the RAN-AN configuration information provided by the second RAN-AN 1706 that, when applied by the UE 1702, causes the UE 1702 to add the one or more cells of the second RAN-AN 1706 previously discussed. The DL signaling air-message 1732 may also include corresponding measurement configuration information for these cells.

[0194] The UE 1702 then applies 1722 the provided configuration information for each of the first RAN-AN 1704 and the second RAN-AN 1706 such that, going forward, the UE 1702 uses the indicated additional cell(s) on the first RAN-AN 1704 and the indicated new cell(s) of the second RAN-AN 1706. Once the configuration information is applied, the UE 1702 sends the RAN-CF 1710 a UL signaling air message 1734 that indicates that this reconfiguration of the UE 1702 is complete.

[0195] Attendant to the new use by / for the UE 1702 of the second RAN-AN 1706, the RAN-CF 1710 sends the RAN-DF 1708 a modify UE RAN-AN list message 1736 that identifies the UE 1702 and indicates that the second RAN-AN 1706 is now active for the UE 1702.

[0196] Going forward, first data transfer 1738 occurs between the UE 1702 and the CN user plane function 1712 occurs by way of the first RAN-AN 1704 and the RAN-DF 1708. Further, second data transfer 1740 between the UE 1702 and the CN user plane function 1712 occurs by way of the second RAN-AN 1706 and the RAN-DF 1708.

[0197] Note that corresponding to such cases, a RAN-AN may be responsible for activating / deactivating RAN-AN CCs based on pending data for UE on that RAN-AN level.

[0198] Aspects of UE-RAN contexts as may be used in scalable RAN embodiments are now discussed in additional detail.

[0199] FIG. 18 illustrates a visualization of a UE-RAN context 1802 as may be understood within a scalable RAN as disclosed herein. As shown, an operative UE-RAN context 1802 may include serving RAN-AN configuration information 1804 for one or more RAN-AN(s) that serve a UE, RB configuration information 1806 for one or more RB(s) used at / by the UE, UE capability information 1808 for the UE, and / or RAN-CF configuration information 1810 for a RAN-CF that serves the UE.304935-4185-2302,1 P70374WO3

[0200] FIG. 19 illustrates a comparison between RRC states as may be used in current systems 1920 and a state conception as may instead be used in scalable RAN systems 1922.

[0201] As illustrated, the RRC states used in current systems 1920 includes an idle state 1902, an inactive state 1904, and a connected state 1906. A UE-RAN context 1912 is maintained between the UE and the RAN across the inactive state 1904 and the connected state 1906.

[0202] A state conception for scalable RAN systems 1922 as discussed herein includes a RAN unregistered mode 1908 and a RAN registered mode 1910. The RAN registered mode 1910 incorporates both anon connected state 1916 and a connected state 1918. In cases of the scalable RAN systems 1922, A UE-RAN context 1914 is active across the entire RAN registered mode 1910 (that includes both the non connected state 1916 and the connected state 1918).

[0203] A UE-RAN context in a scalable RAN includes configurations used by the UE to be served by the scalable RAN, such as serving RAN-AN(s) configuration information, information about RB configuration(s) (and possibly associated state variables), UE capability information, and / or L3 configuration information (e.g., for RRM measurements, for RRC features enabling statuses, etc.).

[0204] In various embodiments of scalable RAN, a UE-RAN context is represented with the scalable RAN by an ID (a “UE-RAN ID”) that is assigned to the UE at initial RAN registration between the UE and the RAN. This ID is maintained until the UE is de-registered from RAN. The ID may be used as part of various connection establishments.

[0205] In various embodiments of scalable RAN, the UE-RAN context is maintained as long as the UE is in a RAN registered mode 1910. Information that is retained in the UE-RAN context may be controlled by the RAN-CF. For example, configuration information for the UE's serving RAN-AN(s) could be optionally maintained while the UE is in the non-connected state, based on a network configuration during a connection release. In some cases, RAN-AN configuration information for one / some of these serving RAN-AN(s) could be retained, while RAN-AN configuration information for other RAN-AN(s) is released.314935-4185-2302,1 P70374WO3

[0206] In various embodiments of scalable RAN, a UE-RAN context is maintained by the RAN-CF serving the UE. Then, in cases of RAN-CF mobility, the UE-RAN context is transferred to the target RAN-CF that will serve the UE going forward.

[0207] Scalable RAN embodiments using such UE-RAN contexts enjoy various benefits. For example, because the UE-RAN context is maintained by default while the UE is in a RAN registered mode 1910, the latency required for transition from a non connected state 1916 to a connected state 1918 and then performing data transfer will be reduced (e.g., relative to the case of the RRC state usage of current systems 1920).

[0208] FIG. 20 illustrates a UE-RAN ID 2002 as may be used for maintaining / tracking a UE-RAN context in a scalable RAN system according to embodiments herein. The UE-RAN ID 2002 includes a RAN ID 2004 that identifies the scalable RAN, a CF ID 2006 that identifies the RAN-CF serving the UE, and a UE ID 2008 that identifies the UE itself.

[0209] FIG. 21A illustrates an example flow diagram 2100 for initial RAN registration and UE-RAN context and UE-RAN ID assignment for a UE in a scalable RAN, according to embodiments discussed herein. The flow diagram 2100 illustrates communications between / among a UE 2106, a first RAN-AN 2108, an N-th RAN-AN 2110, a RAN-DF 2112, a RAN-CF 2114, and a CN 2116. The first RAN-AN 2108 through the N-th RAN-AN 2110, the RAN-DF 2112, and the RAN-CF 2114 are understood of entities of a scalable RAN 2130 as discussed herein.

[0210] The UE 2106 is initially in a RAN unregistered mode 2104. The UE 2106 transmits a connection request message 2120, which is routed by a RAN-AN (any of the first RAN-AN 2108 through the N-th RAN-AN 2110 that receives the connection request message 2120) to a default RAN-CF (in this case, the RAN-CF 2114). The connection request message 2120 includes a “registration request” cause indication and a UE identity' (e.g., an international mobile subscriber identity (IMSI) of the UE).

[0211] In response to the connection request message 2120, the system performs a UE-RAN context establishment procedure 2102. As part of the UE-RAN context establishment procedure 2102, the UE receives a UE-RAN ID from the RAN-CF 2114 for purposes of facilitating further communication with the network. Note that additional details of an example UE-RAN context establishment procedure 2102 are provided herein in FIG. 2 IB and corresponding discussion.324935-4185-2302,1 P70374WO3

[0212] As a result of the UE-RAN context establishment procedure 2102, the UE 2106 transitions to a RAN registered mode 2160 and initially operates according to a connected state 2122 for that RAN registered mode 2160.

[0213] At some later time, the RAN-CF 2114 sends the UE 2106 a connection release message 2124. The connection release message 2124 includes a list of UE-RAN context information for the UE to retain during a non-connected state 2126.

[0214] The UE 2106 accordingly transitions to the non-connected state 2126. Attendant to this transition, the UE retains the UE-RAN context information indicated in the connection release message 2124. Note that the UE 2106 remains in the RAN registered mode 2160 even after the transition to the non-connected state 2126.

[0215] Suppose that the UE 2106 then wishes to re-enter the connected state 2122 (e.g., the UE has new UL data for transmission). The UE can send the illustrated connection request message 2128. Note that, as opposed to the connection request message 2120 previously used, the UE is able to include its retained UE-RAN ID that was previously established during the UE-RAN context establishment procedure 2102 (instead of having to rely on some other non-contextual ID, such as an IMSI). The connection request message 2128 may thus be routed by the receiving RAN-AN based on / to the RAN-CF that is identified in the UE-RAN ID. This facilitates a relatively fast transition of the UE back to the connected state 2122 for the RAN registered mode 2160.

[0216] FIG. 21B illustrates an example flow diagram 2100 for a UE-RAN context establishment procedure. The flow diagram 2118 illustrates communications between the UE 2106, the first RAN-AN 2108 through the N-th RAN-AN 2110, the RAN-DF 2112, the RAN-CF 2114, and the CN 2116 first introduced in FIG. 21A. The flow diagram 2118 can be understood as a more detailed illustration for / of the UE-RAN context establishment procedure 2102 introduced in FIG. 21 A.

[0217] The UE 2106 sends the first RAN-AN 2108 a connection request message 2132 that identifies a cause for the connection request and an identity of the UE (e.g., an IMSI). The first RAN-AN 2108 then sends the RAN-CF 2114 a connection request message 2134 that identifies the UE 2106, identifies a connection request air-message, and provides the RAN-CF 2114 with configuration information for the first RAN-AN 2108 that may be used by a UE such as the UE 2106.

[0218] The RAN-CF 2114 then sends the RAN-DF 2112 an add UE request message 2136 that identifies the UE 2106, identifies any capability information for the UE 2106,334935-4185-2302,1 P70374WO3identifies a signaling data session type for establishment, and identifies a RAN-AN list for the UE 2106 (in this case, that includes the first RAN-AN 2108 with which the UE 2106 initially interacts). The RAN-DF 2112 responds back to the RAN-CF 2114 with an add UE confirmation message 2138 that identifies the UE 2106, indicates that the addition request is accepted, and that provides an AS DP configuration information that is to be used by the UE 2106.

[0219] The RAN-CF 2114 then creates a UE-RAN context using the AS DP configuration information from the RAN-DF 2112 and the configuration information provided by the first RAN-AN 2108. The RAN-CF then sends the UE 2106, by way of the RAN-DF 2112 and the first RAN-AN 2108, a DL air-message 2140 that includes this UE-RAN context. The UE 2106 responds to the RAN-CF 2114, by way of the first RAN-AN 2108 and the RAN-DF 2112, with a UL air-message 2142 that indicates that the UE has applied the configurations of the UE-RAN context and is therefore ready to operate according to the UE-RAN context.

[0220] Then, the RAN-CF 2114 sends the CN 2116 a UE initial access message 2144 that identifies the UE 2106 and identifies a RAN-DF listing for the UE 2106 (in this case, that includes the RAN-DF 2112 that is presently operating for the UE 2106). The CN 2116 responds to the RAN-CF 2114 with a UE initial context setup request message 2146 that instructs the RAN-CF 2114 to set up the context for the UE 2106.

[0221] The RAN-CF 2114 then sends the RAN-DF 2112 a modify UE request message 2148 that identifies the UE 2106 and indicates one or more data session(s) for the UE 2106. The RAN-DF 2112 replies to the RAN-CF 2114 with a modify UE confirmation message 2150 that identifies the UE 2106 and that provides the RAN-CF 2114 with an RB listing for the UE 2106 (including AS DP configuration information for those RB(s)).

[0222] The RAN-CF 2114 then sends the first RAN-AN 2108 an add UE request message 21 2 that identifies the UE 2106, provides capability information for the UE 2106, provides a service profile information for the UE 2106, and identifies UE-common RAN-AN configuration information that the UE 2106 will use to communicate with the first RAN-AN 2108 going forward. Note that the RAN-CF 2114 may provide the first RAN-AN 2108 a UE unified RAN-AN configuration information. This information could include UE logical channels and their priority, QoS focused parameters, etc. In some cases, a total amount of bytes served for a certain RB within a certain time-window344935-4185-2302,1 P70374WO3across all serving ANs is controlled via RAN-DF. In some cases, information about discontinuing a reception configuration is provided.

[0223] The first RAN-AN 2108 responds with an add UE confirmation message 2154 that identifies the UE 2106, that provides UE-specific RAN-AN configuration information for the UE 2106 to use when communicating with the first RAN-AN 2108, and provides a list of neighbor cells.

[0224] The RAN-CF 2114 then sends the UE 2106 a DL air-message 2156 by way of the RAN-DF 2112 that identifies the UE 2106 and that includes security information command along with reconfiguration information. The reconfiguration information includes RAN-AN configuration information (e.g., developed using the UE-specific RAN-AN configuration information previously provided to the RAN-CF 2114 by the first RAN-AN 2108), DP configuration information, and a measurement configuration for the UE 2106 to use going forward. The UE 2106 responds to the RAN-CF 2114 with a UL air-message 2158 that is sent by way of the RAN-DF 2112 and that includes a security configuration response message and an indication that the UE has accomplished the reconfiguration indicated in the just-provided reconfiguration information.

[0225] Note that, as is described herein, the RAN-CF 2114 is not required to serve all RBs of the UE via a same single RAN-DF.Additional Example Embodiments

[0226] FIG. 22 illustrates a method 2200 of a RAN, according to embodiments discussed herein. The method 2200 includes receiving 2202. from a CN, a first user plane data packet of a first RB of a first UE that is served by the RAN by a first RAN-AN set for the first UE. The method 2200 further includes routing 2204 the first user plane data packet to a first RAN-DF of the RAN that manages the first RB of the first UE. The method 2200 further includes selecting 2206, by the first RAN-DF, from the first RAN-AN set for the first UE, a first RAN-AN to transport the first user plane data packet to the first UE. The method 2200 further includes routing 2208 the first user plane data packet to the first RAN-AN. The method 2200 further includes transmitting 2210, by the first RAN-AN, the first user plane data packet to the first UE.

[0227] In some embodiments, the method 2200 further includes receiving, from the CN, a second user plane data packet of the first RB of the first UE; routing the second user plane data packet to the first RAN-DF that manages the first RB of the first UE;354935-4185-2302,1 P70374WO3selecting, by the first RAN-DF, from the first RAN-AN set, a second RAN-AN to transport the second user plane data packet to the first UE; routing the second user plane data packet to the second RAN-AN; and transmitting, by the second RAN-AN, the second user plane data packet to the first UE.

[0228] In some embodiments, the method 2200 further includes assigning, by a RAN-CF of the RAN, the first RAN-DF to manage the first RB of the first UE.

[0229] In some embodiments, the method 2200 further includes assigning, by a first RAN-CF of the RAN. the first RAN-AN set to the first UE.

[0230] In some embodiments, the method 2200 further includes receiving, from the CN, a second user plane data packet of a second RB of the first UE served by the RAN; routing the second user plane data packet to a second RAN-DF of the RAN that manages the second RB of the first UE; selecting, by the second RAN-DF, from the first RAN-AN set for the first UE, the first RAN-AN to transport the second user plane data packet to the first UE; routing the second user plane data packet to the first RAN-AN; and transmitting, by the first RAN-AN, the second user plane data packet to the first UE. In some of these embodiments, the method 2200 further includes assigning, by a RAN-CF of the RAN, the first RAN-DF to manage the first RB of the first UE and the second RAN-DF to manage the second RB of the first UE.

[0231] In some embodiments, the method 2200 further includes receiving, from the CN, a second user plane data packet of a second RB of the first UE served by the RAN; routing the second user plane data packet to a second RAN-DF of the RAN that manages the second RB of the first UE; selecting, by the second RAN-DF, from the first RAN-AN set for the first UE, a second RAN-AN to transport the second user plane data packet to the first UE; routing the second user plane data packet to the second RAN-AN; and transmitting, by the second RAN-AN, the second user plane data packet to the first UE. In some of these embodiments, the method 2200 further includes assigning, by a RAN-CF of the RAN, the first RAN-DF to manage the first RB of the first UE and the second RAN-DF to manage the second RB of the first UE.

[0232] In some embodiments of the method 2200, the first RAN-DF manages a second RB of a second UE served by the RAN by a second RAN-AN set for the second UE. and the method 2200 further includes: receiving, from the CN, a second user plane data packet of the second RB of the second UE; routing the second user plane data packet to the first RAN-DF; selecting, by the first RAN-DF, from the second RAN-AN set for the364935-4185-2302,1 P70374WO3second UE, a second RAN-AN to transport the second user plane data packet to the second UE; routing the second user plane data packet to the second RAN-AN; and transmitting, by the second RAN-AN, the second user plane data packet to the second UE. In some of these embodiments, the method 2200 further includes assigning, by a RAN-CF of the RAN, the first RAN-DF to manage the first RB of the first UE and the second RB of the second UE. In some of these embodiments, the method 2200 further includes assigning, by a first RAN-CF of the RAN, the first RAN-DF to manage the first RB of the first UE; and assigning, by a second RAN-CF of the RAN, the first RAN-DF to manage the second RB of the second UE.. In some of these embodiments, the method 2200 further includes assigning, by a first RAN-CF of the RAN, the first RAN-AN set to the first UE and the second RAN-AN set to the second UE. In some of these embodiments, the method 2200 further includes assigning, by a first RAN-CF of the RAN, the first RAN-AN set to the first UE; and assigning, by a second RAN-CF of the RAN, the second RAN-AN set to the second UE. In some of these embodiments, the first RAN-AN set for the first UE comprises a shared RAN-AN that is also in the second RAN-AN set for the second UE. In some of these embodiments, the first RAN-AN set for the first UE is disjoint with respect to the second RAN-AN set for the second UE.

[0233] FIG. 23 illustrates a method 2300 of a RAN-DF of a RAN, according to embodiments discussed herein. The method 2300 includes receiving 2302 a first user plane data packet of a first RB of a first UE that is served by the RAN by a first RAN-AN set for the first UE. The method 2300 further includes selecting 2304 a first RAN-AN of the first RAN-AN set for the first UE for use to transmit the first user plane data packet to the first UE. The method 2300 further includes routing 2306 the first user plane data packet to the first RAN-AN.

[0234] In some embodiments, the method 2300 further includes receiving, from a RAN-CF of the RAN, an identification of the first RAN-AN set to the first UE.

[0235] In some embodiments, the method 2300 further includes receiving, from a RAN-CF of the RAN, an instruction to manage the first RB of the first UE

[0236] In some embodiments, the method 2300 further includes receiving a second user plane data packet of the first RB of the first UE; selecting a second RAN-AN of the first RAN-AN set for the first UE for use to transmit the second user plane data packet to the first UE; and routing the second user plane data packet to the second RAN-AN.374935-4185-2302,1 P70374WO3

[0237] In some embodiments, the method 2300 further includes receiving a second user plane data packet of a second RB of the first UE; selecting the first RAN-AN for use to transmit the second user plane data packet to the first UE; and routing the second user plane data packet to the first RAN-AN.

[0238] In some embodiments, the method 2300 further includes receiving a second user plane data packet of a second RB of a second UE served by the RAN by a second RAN-AN set for the second UE; selecting a second RAN-AN of the second RAN-AN set for the second UE for use to transmit the second user plane data packet to the second UE; and routing the second user plane data packet to the second RAN-AN.

[0239] In some embodiments of the method 2300, the RAN serves a second UE using a second RAN-AN set that includes the first RAN-AN of the first RAN-AN set; and the method 2300 further includes: receiving a second user plane data packet of a second RB of the second UE; selecting the first RAN-AN for use to transmit the second user plane data packet to the second UE; and routing the second user plane data packet to the first RAN-AN.

[0240] In some embodiments, the method 2300 further includes receiving, from a RAN-CF of the RAN: a first identification of the first RAN-AN set to the first UE; and a second identification of the second RAN-AN set to the second UE.

[0241] In some embodiments, the method 2300 further includes receiving, from a RAN-CF of the RAN: a first instruction to manage the first RB of the first UE; and a second instruction to manage the second RB of the second UE.

[0242] In some embodiments, the method 2300 further includes receiving, from a first RAN-CF of the RAN, a first identification of the first RAN-AN set to the first UE; and receiving, from a second RAN-CF of the RAN, a second identification of the second RAN-AN set to the second UE.

[0243] In some embodiments, the method 2300 further includes receiving, from a first RAN-CF of the RAN, a first instruction to manage the first RB of the first UE; and receiving, from a second RAN-CF of the RAN, a second instruction to manage the second RB of the second UE.

[0244] FIG. 24 illustrates a method 2400 of a UE, according to embodiments discussed herein. The method 2400 includes receiving 2402, from a RAN-CF of a RAN, a message comprising an instruction for the UE to release a first RAN-AN from a RAN-AN set for the UE and a configuration for the UE to use to add a second RAN-AN to the RAN-AN 384935-4185-2302,1 P70374WO3set for the UE. The method 2400 further includes performing 2404 an initial access procedure through the second RAN-AN based on the configuration. The method 2400 further includes performing 2406 a first data transfer through the RAN via the first RAN-AN using an RB of the UE that is managed by a RAN-DF of the RAN, wherein the first data transfer via the first RAN-AN occurs while the UE is performing the initial access procedure through the second RAN-AN. The method 2400 further includes releasing 2408 the first RAN-AN from the RAN-AN set for the UE after accessing the RAN through the second RAN-AN as a result of the initial access procedure through the second RAN-AN. The method 2400 further includes performing 2410 a second data transfer through the RAN via the second RAN-AN after accessing the RAN through the second RAN-AN, wherein the second data transfer uses the RB managed by the RAN-DF.

[0245] In some embodiments, the method 2400 further includes sending, to the RAN-CF, a measurement report comprising a first measurement for a first MO of the first RAN-AN and a second measurement for a second MO of the second RAN-AN.

[0246] FIG. 25 illustrates a method 2500 of a RAN-DF of a RAN, according to embodiments discussed herein. The method 2500 includes routing 2502 a first packet of an RB of a UE served by the RAN that is managed by the RAN-DF to a first RAN-AN of a RAN-AN set for the UE. The method 2500 further includes receiving 2504, from a RAN-CF of the RAN, an instruction to release the first RAN-AN from the RAN-AN set for the UE and to add a second RAN-AN to the RAN-AN set for the UE. The method 2500 further includes routing 2506, after receiving the instruction, a second packet of the RB to the second RAN-AN.

[0247] FIG. 26 illustrates a method 2600 of a RAN-CF of a RAN, according to embodiments discussed herein. The method 2600 includes sending 2602, to a UE, a message comprising an instruction for the UE to release a first RAN-AN from a RAN-AN set for the UE and a configuration for the UE to use to add a second RAN-AN to the RAN-AN set for the UE. The method 2600 further includes receiving 2604, from the second RAN-AN, a first indication that the UE has connected to the second RAN-AN. The method 2600 further includes sending 2606, after receiving the first indication, to a RAN-DF of the RAN managing an RB of the UE, a second indication that the first RAN-AN is released from the RAN-AN set for the UE and that the second RAN-AN is added to the RAN-AN set for the UE.394935-4185-2302,1 P70374WO3

[0248] In some embodiments, the method 2600 further includes sending, to the second RAN-AN, a UE context request message identifying the UE; and receiving, from the second RAN-AN, in response to the UE context request message, the configuration for the UE to use with the second RAN-AN.

[0249] In some embodiments, the method 2600 further includes receiving, from the UE, a measurement report comprising a measurement for a MO of the second RAN-AN; and identifying the second RAN-AN for addition to the RAN-AN set for the UE based on the measurement report.

[0250] In some embodiments, the method 2600 further includes receiving, from the UE, a measurement report comprising a measurement for a MO of the first RAN-AN; and identifying the first RAN-AN for release from the RAN-AN set for the UE based on the measurement report.

[0251] FIG. 27 illustrates a method 2700 of a RAN-CF of a RAN, according to embodiments discussed herein. The method 2700 includes sending 2702, to a source RAN-DF of the RAN that is performing management of an RB of a UE served by the RAN, a request message comprising a request to switch the management of the RB to a target RAN-DF. The method 2700 further includes receiving 2704, from the source RAN-DF, a confirmation message confirming the switch of the management of the RB to the target RAN-DF. The method 2700 further includes sending 2706, to the target RAN-DF, an identification of a RAN-AN set for the UE.

[0252] In some embodiments of the method 2700, the configuration message comprises a new RB context for the RB, and further comprising sending the new RB context for the RB to the UE.

[0253] In some embodiments of the method 2700, the new RB context comprises L2 configuration information.

[0254] In some embodiments of the method 2700, the new RB context comprises security information.

[0255] In some embodiments, the method 2700 further includes determining to perform load balancing between the source RAN-DF and the target RAN-DF, and the request message is sent to the source RAN-DF as a result of the determining to perform the load balancing.404935-4185-2302,1 P70374WO3

[0256] FIG. 28 illustrates a method 2800 of a source RAN-DF of a RAN that is performing management of an RB of a UE served by the RAN, according to embodiments discussed herein. The method 2800 includes receiving 2802, from a RAN-CF of the RAN, a first request message comprising a request to switch the management of the RB to a target RAN-DF. The method 2800 further includes sending 2804, to the target RAN-DF, a second request message comprising a second request for the target RAN-DF to perform the management of the RB and context information for the RB. The method 2800 further includes receiving 2806, from the target RAN-DF, a first confirmation message comprising a first confirmation that the target RAN-DF performs the management of the RB. The method 2800 further includes sending 2808, to a CN, a third request message comprising a third request for the CN to route data packets of the RB to the target RAN-DF. The method 2800 further includes receiving 2810, from the CN, a second confirmation message comprising a second confirmation that the CN routes data packets of the RB to the target RAN-DF. The method 2800 further includes sending 2812, to the RAN-CF, a third confirmation message comprising a third confirmation indicating that the target RAN-DF performs the management of the RB.

[0257] In some embodiments, the method 2800 further includes forwarding a pending packet of the RB that is at the source RAN-DF to the target RAN-DF.

[0258] In some embodiments of the method 2800, the first confirmation message received from the target RAN-DF further comprises a new RB context for the RB, and the third confirmation message sent to the RAN-CF comprises the new RB context for the RB.

[0259] FIG. 29 illustrates a method 2900 of a target RAN-DF of a RAN, according to embodiments discussed herein. The method 2900 includes receiving 2902, from a source RAN-DF that is performing management of an RB of a UE served by the RAN, a first request message comprising a first request for the target RAN-DF to perform the management of the RB and context information for the RB. The method 2900 further includes sending 2904, to the source RAN-DF, a first confirmation message comprising a first confirmation that the target RAN-DF performs the management of the RB. The method 2900 further includes receiving 2906, from a RAN-CF of the RAN, an identification of a RAN-AN set for the UE. The method 2900 further includes sending 2908, to a RAN-AN of the RAN-AN set, an indication that the target RAN-DF is performing the management of the RB of the UE.414935-4185-2302,1 P70374WO3

[0260] In some embodiments, the method 2900 further includes receiving a pending packet of the RB from the source RAN-DF.

[0261] In some embodiments, the method 2900 further includes determining a new RB context for the RB to use with the source RAN-DF. and wherein the first confirmation message comprises the new RB context.

[0262] FIG. 30 illustrates a method 3000 of a source RAN-CF of a RAN, according to embodiments discussed herein. The method 3000 includes sending 3002, to a target RAN-CF of the RAN. a request message comprising a request to transfer control of a UE served by the RAN to the target RAN-CF and UE-RAN context information for the UE. The method 3000 further includes receiving 3004, from the target RAN-CF, a first confirmation message comprising a first confirmation that the target RAN-CF assumes the control of the UE and updated UE-RAN context information. The method 3000 further includes sending 3006, to the UE, the updated UE-RAN context information. The method 3000 further includes receiving 3008, from the UE, a second confirmation message comprising a second confirmation that the UE received the updated UE-RAN context information. The method 3000 further includes sending 3010, to the target RAN-CF, an indication of a RAN-AN set for the UE.

[0263] In some embodiments of the method 3000, the updated UE-RAN context information comprises a UE-RAN ID for the UE to use with the target RAN-CF.

[0264] In some embodiments of the method 3000, the updated UE-RAN context information comprises a UE activated L3 feature.

[0265] FIG. 31 illustrates a method 3100 of a target RAN-CF of a RAN, according to embodiments discussed herein. The method 3100 includes receiving 3102, from a source RAN-CF of the RAN that controls a UE served by the RAN, a request message comprising a request to transfer control the UE to the target RAN-CF and UE-RAN context information for the UE. The method 3100 further includes generating 3104 updated UE-RAN context information based on the UE-RAN context information received from the source RAN-CF. The method 3100 further includes sending 3106, to the source RAN-CF, a confirmation message comprising a confirmation that the target RAN-CF assumes the control of the UE and the updated UE-RAN context information. The method 3100 further includes receiving 3108, from the source RAN-CF, an indication of a RAN-AN set for the UE. The method 3100 further includes sending 3110,424935-4185-2302,1 P70374WO3to a RAN-DF of the RAN that is performing management of an RB of the UE, an indication that the target RAN-CF controls the UE.

[0266] In some embodiments of the method 3100, the updated UE-RAN context information comprises a UE-RAN ID for the UE to use with the target RAN-CF.

[0267] In some embodiments of the method 3100, the updated UE-RAN context information comprises a UE activated L3 feature.

[0268] FIG. 32 illustrates a method 3200 of a UE. according to embodiments discussed herein. The method 3200 includes sending 3202, to a RAN-AN of a RAN, a connection request message indicating a request for the UE to connect to the RAN. The method 3200 further includes receiving 3204, from a RAN-CF of the RAN, via the RAN-AN, a connection setup message comprising RAN-AN configuration information for the RAN-AN and an AS DP configuration for a RAN-DF of the RAN. The method 3200 further includes performing 3206 a connection setup for the RAN based on the RAN-AN configuration information for the RAN-AN and the AS DP configuration for the RAN-DF.

[0269] In some embodiments, the method 3200 further includes sending, to the RAN-CF, a confirmation message confirming that the UE has performed the connection setup.

[0270] In some embodiments of the method 3200, the connection request message indicates a cause for the UE request.

[0271] In some embodiments of the method 3200. the connection request message comprises an ID for the UE.

[0272] FIG. 33 illustrates a method 3300 of a RAN-CF of a RAN, according to embodiments discussed herein. The method 3300 includes receiving 3302, from a RAN-AN of the RAN, a connection request message that identifies a UE that has requested service by the RAN through the RAN AN and RAN-AN configuration information for the RAN-AN. The method 3300 further includes sending 3304, to a RAN-DF of the RAN, a first request message comprising a request for the RAN-DF to manage a signaling data session for the UE. The method 3300 further includes receiving 3306, from the RAN-DF, a first confirmation message confirming that the RAN-DF manages the signaling data session and comprising an AS DP configuration for the RAN-DF. The method 3300 further includes sending 3308, to the UE. via the RAN-AN, a connection setup message comprising the RAN-AN configuration information for the RAN-AN and the AS DP configuration for the RAN-DF.434935-4185-2302,1 P70374WO3

[0273] In some embodiments of the method 3300, the first request message comprises an identification of the RAN-AN.

[0274] In some embodiments, the method 3300 further includes receiving, from the UE, a second confirmation message confirming that the UE has performed a connection setup using the RAN-AN configuration information for the RAN-AN and the AS DP configuration for the RAN-DF.

[0275] FIG. 34 illustrates a method 3400 of a UE, according to embodiments discussed herein. The method 3400 includes sending 3402, to a RAN-CF of a RAN, via a RAN-AN of the RAN, an indication that the UE has performed a connection setup for the RAN. The method 3400 further includes receiving 3404, from the RAN-CF, a configuration message comprising UE RAN context information for the UE, wherein the UE RAN context information comprises configuration information for the RAN-AN. The method 3400 further includes performing 3406 data communication through the RAN using the UE RAN context information for the UE.

[0276] In some embodiments of the method 3400. the UE RAN context information further comprises a UE RAN ID for the UE to use with the RAN-CF.

[0277] In some embodiments of the method 3400, the UE RAN context information further comprises a UE activated L3 feature.

[0278] In some embodiments of the method 3400, the UE RAN context information further comprises configuration information for an RB used in the data communication.

[0279] FIG. 35 illustrates a method 3500 of a RAN-CF of a RAN, according to embodiments discussed herein. The method 3500 includes sending 3502, to a RAN-DF of the RAN, a first request message comprising a first request for the RAN-DF to perform management of an RB for a UE. The method 3500 further includes receiving 3504, from the RAN-DF a first confirmation indicating that the RAN-DF performs the management of the RB and comprising an AS DP configuration for the RAN-DF. The method 3500 further includes sending 3506, to a RAN-AN of the RAN, a second request message requesting the RAN-AN to operate in a RAN-AN set for the UE. The method 3500 further includes receiving 3508, from the RAN-AN, a second confirmation message confirming that the RAN-AN operates in the RAN-AN set for the UE and comprising UE-specific configuration information for the RAN-AN. The method 3500 further includes generating 3510 UE RAN context information for the UE using the AS DP configuration for the RAN-DF and the UE-specific RAN-AN configuration information 444935-4185-2302,1 P70374WO3for the RAN-AN. The method 3500 further includes sending 3512, to the UE, a configuration message comprising the UE RAN context information.

[0280] In some embodiments of the method 3500, the UE RAN context information comprises a UE RAN ID for the UE to use with the RAN-CF.

[0281] In some embodiments of the method 3500, the UE RAN context information comprises a UE activated L3 feature.

[0282] In some embodiments of the method 3500, the UE RAN context information comprises configuration information for the RAN-AN.

[0283] In some embodiments of the method 3500, the UE RAN context information comprises configuration information for the RB.

[0284] In some embodiments, the method 3500 further includes sending, to a core network (CN). an initial access message that indicates to the CN that the UE is connected to the RAN via the RAN-DF; and receiving, from the CN, a setup message identifying the RB for establishment for the UE, wherein the first request message is sent to the RAN-DF in response to the receiving the setup message identifying the RB from the CN.

[0285] In some embodiments of the method 3500, the first request message identifies a QoS requirement for the RB.

[0286] In some embodiments of the method 3500. the first request message indicates that the RB is for a data session between the UE and the CN.

[0287] In some embodiments of the method 3500, the second request message further comprises a common configuration for the RAN-AN that is in use by the UE.

[0288] In some embodiments of the method 3500, the second confirmation message further comprises an identification of a neighbor RAN-AN to the RAN-AN.

[0289] FIG. 36 illustrates an example architecture of a wireless communication system 3600, according to embodiments disclosed herein.

[0290] As shown by FIG. 36, the wireless communication system 3600 includes UE 3602 and UE 3604 (although any number of UEs may be used). In this example, the UE 3602 and the UE 3604 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device configured for wireless communication.

[0291] The UE 3602 and UE 3604 may be configured to communicatively couple with a RAN 3606. The UE 3602 and UE 3604 utilize connections (or channels) (shown as454935-4185-2302,1 P70374WO3connection 3608 and connection 3610. respectively) with the RAN 3606, each of which comprises a physical communications interface. The RAN 3606 may be a scalable RAN as discussed herein, and may include one or more RAN-CF(s) (e.g., the RAN-CF #1 3628 through the RAN-CF #N 3634), one or more RAN-DF(s) (e.g., the RAN-DF #1 3630 through the RAN-DF #M 3636), and / or one or more RAN-AN(s) (e g., the RAN-AN #1 3632 through the RAN-AN #P 3638).

[0292] In this example, the connection 3608 and connection 3610 are air interfaces to enable such communicative coupling, and may be consistent with RAT(s) used by the RAN 3606.

[0293] In some embodiments, the UE 3602 and UE 3604 may also directly exchange communication data via a sidelink interface 3612. The UE 3604 is shown to be configured to access an access point (shown as AP 3614) via connection 3616. By way of example, the connection 3616 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 3614 may comprise a Wi-Fi® router. In this example, the AP 3614 may be connected to another network (for example, the Internet) without going through a CN 3618.

[0294] In embodiments, the UE 3602 and UE 3604 can be configured to communicate using orthogonal frequency division multiplexing (OFDM) communication signals with each other or with an RAN-AN of the RAN 3606 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an orthogonal frequency division multiple access (OFDMA) communication technique (e.g., for downlink communications) or a single carrier frequency division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

[0295] In some embodiments, all or parts of any of the RAN-CF(s), RAN-DF(s), and / or the RAN-AN(s) of the RAN 3606 may be implemented as one or more software entities running on server computers as part of a virtual network. In addition, or in other embodiments, these entities may be configured to communicate with one another via an appropriate interface.

[0296] The RAN 3606 is shown to be communicatively coupled to the CN 3618. The CN 3618 may comprise one or more network elements 3620, which are configured to offer various data and telecommunications services to customers / subscribers (e.g., users464935-4185-2302,1 P70374WO3of UE 3602 and UE 3604) who are connected to the CN 3618 via the RAN 3606. The components of the CN 3618 may be implemented in one physical device or separate physical devices including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium).

[0297] In embodiments, the RAN 3606 may be connected with the CN 3618 via an interface 3622. In embodiments, the interface 3622 may be split into two parts, a user plane interface, which carries traffic data between the RAN 3606 and a user plane entity of the CN 3618, and the control plane interface, which is a signaling interface between the RAN 3606 and a control plane entity of the CN 3618.

[0298] Generally, an application server 3624 may be an element offering applications that use internet protocol (IP) bearer resources with the CN 3618 (e g., packet switched data services). The application server 3624 can also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for the UE 3602 and UE 3604 via the CN 3618. The application server 3624 may communicate with the CN 3618 through an IP communications interface 3626.

[0299] FIG. 37 illustrates a system 3700 for performing signaling 3734 between a wireless device 3702 and a network entity' 3718, according to embodiments disclosed herein. The system 3700 may be a portion of a wireless communications system as herein described. The wireless device 3702 may be, for example, a UE of a wireless communication system. The network entity 3718 may implement, for example, one or more RAN-AN, a RAN-DF, and / or a RAN-CF of a RAN of the wireless communication system.

[0300] The wireless device 3702 may include one or more processor(s) 3704. The processor(s) 3704 may execute instructions such that various operations of the wireless device 3702 are performed, as described herein. The processor(s) 3704 may include one or more baseband processors implemented using, for example, a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0301] The wireless device 3702 may include a memory 3706. The memory73706 may be a non-transitory7computer-readable storage medium that stores instructions 3708474935-4185-2302,1 P70374WO3(which may include, for example, the instructions being executed by the processor(s) 3704). The instructions 3708 may also be referred to as program code or a computer program. The memory 3706 may also store data used by, and results computed by, the processor(s) 3704.

[0302] The wireless device 3702 may include one or more transceiver(s) 3710 that may include radio frequency (RF) transmitter circuitry and / or receiver circuitry that use the antenna(s) 3712 of the wireless device 3702 to facilitate signaling (e.g., the signaling 3734) to and / or from the wireless device 3702 with other devices (e.g., the network entity 3718) according to corresponding RATs.

[0303] The wireless device 3702 may include one or more antenna(s) 3712 (e.g., one, two, four, or more). For embodiments with multiple antenna(s) 3712, the wireless device 3702 may leverage the spatial diversity of such multiple antenna(s) 3712 to send and / or receive multiple different data streams on the same time and frequency resources. This behavior may be referred to as, for example, multiple input multiple output (MIMO) behavior (referring to the multiple antennas used at each of a transmitting device and a receiving device that enable this aspect). MIMO transmissions by the wireless device 3702 may be accomplished according to precoding (or digital beamforming) that is applied at the wireless device 3702 that multiplexes the data streams across the antenna(s) 3712 according to known or assumed channel characteristics such that each data stream is received with an appropriate signal strength relative to other streams and at a desired location in the spatial domain (e.g.. the location of a receiver associated with that data stream). Certain embodiments may use single user MIMO (SU-MIMO) methods (where the data streams are all directed to a single receiver) and / or multi user MIMO (MU-MIMO) methods (where individual data streams may be directed to individual (different) receivers in different locations in the spatial domain).

[0304] In certain embodiments having multiple antennas, the wireless device 3702 may implement analog beamforming techniques, whereby phases of the signals sent by the antenna(s) 3712 are relatively adjusted such that the (joint) transmission of the antenna(s) 3712 can be directed (this is sometimes referred to as beam steering).

[0305] The wireless device 3702 may include one or more interface(s) 3714. The interface(s) 3714 may be used to provide input to or output from the wireless device 3702. For example, a wireless device 3702 that is a UE may include interface(s) 3714 such as microphones, speakers, a touchscreen, buttons, and the like in order to allow for484935-4185-2302,1 P70374WO3input and / or output to the UE by a user of the UE. Other interfaces of such a UE may be made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver(s) 3710 / antenna(s) 3712 already described) that allow for communication between the UE and other devices and may operate according to known protocols (e.g., Wi-Fi®, Bluetooth®, and the like).

[0306] The wireless device 3702 may include a scalable RAN module 3716. The scalable RAN module 3716 may be implemented via hardware, software, or combinations thereof. For example, the scalable RAN module 3716 may be implemented as a processor, circuit, and / or instructions 3708 stored in the memory 3706 and executed by the processor(s) 3704. In some examples, the scalable RAN module 3716 may be integrated within the processor(s) 3704 and / or the transceiver(s) 3710. For example, the scalable RAN module 3716 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g.. logic gates and circuitry) within the processor(s) 3704 or the transceiver(s) 3710.

[0307] The scalable RAN module 3716 may be used for various aspects of the present disclosure, for example, aspects of FIG. 24, FIG. 32, and / or FIG. 34.

[0308] For example, the scalable RAN module 3716 may configure the wireless device 3702 to receive, from a RAN-CF of a RAN, a message comprising an instruction for the UE to release a first RAN-AN from a RAN-AN set for the UE and a configuration for the UE to use to add a second RAN-AN to the RAN-AN set for the UE; perform an initial access procedure through the second RAN-AN based on the configuration; perform a first data transfer through the RAN via the first RAN-AN using an RB of the UE that is managed by a RAN-DF of the RAN, wherein the first data transfer via the first RAN-AN occurs while the UE is performing the initial access procedure through the second RAN-AN; release the first RAN-AN from the RAN-AN set for the UE after accessing the RAN through the second RAN-AN as a result of the initial access procedure through the second RAN-AN; and perform a second data transfer through the RAN via the second RAN-AN after accessing the RAN through the second RAN-AN, wherein the second data transfer uses the RB managed by the RAN-DF.

[0309] As another example, the scalable RAN module 3716 may configure the wireless device 3702 to send, to a RAN-AN of a RAN, a connection request message indicating a request for the UE to connect to the RAN; receive, from a RAN-CF of the RAN, via the RAN-AN, a connection setup message comprising RAN-AN configuration information494935-4185-2302,1 P70374WO3for the RAN-AN and an AS DP configuration for a RAN-DF of the RAN; and perform a connection setup for the RAN based on the RAN-AN configuration information for the RAN-AN and the AS DP configuration for the RAN-DF.

[0310] As another example, the scalable RAN module 3716 may configure the wireless device 3702 to send, to a RAN-CF of a RAN, via a RAN-AN of the RAN, an indication that the UE has performed a connection setup for the RAN; receive, from the RAN-CF, a configuration message comprising UE RAN context information for the UE, wherein the UE RAN context information comprises configuration information for the RAN-AN; and perform data communication through the RAN using the UE RAN context information for the UE.

[0311] The network entity 3718 may include one or more processor(s) 3720. The processor(s) 3720 may execute instructions such that various operations of the network entity 3718 are performed, as described herein. The processor(s) 3720 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0312] The network entity 3718 may include a memory 3722. The memory 3722 may be a non-transitory computer-readable storage medium that stores instructions 3724 (which may include, for example, the instructions being executed by the processor(s) 3720). The instructions 3724 may also be referred to as program code or a computer program. The memory 3722 may also store data used by, and results computed by, the processor(s) 3720.

[0313] In embodiments where the network entity 3718 is or includes a RAN-AN. the network entity 3718 may include one or more transceiver(s) 3726 that may include RF transmitter circuitry' and / or receiver circuitry that use the antenna(s) 3728 of the network entity 3718 to facilitate signaling (e.g., the signaling 3734) to and / or from the network entity 3718 with other devices (e.g., the wireless device 3702) according to corresponding RATs.

[0314] In embodiments where the network entity 3718 is or includes a RAN-AN, the network entity 3718 may include one or more antenna(s) 3728 (e.g., one, two, four, or more). In embodiments having multiple antenna(s) 3728, the network entity 3718 may perform MIMO, digital beamforming, analog beamforming, beam steering, etc., as has been described.504935-4185-2302,1 P70374WO3

[0315] The network entity 3718 may include one or more interface(s) 3730. The interface(s) 3730 may be used to provide input to or output from the network entity 3718. For example, a network entity 3718 may include interface(s) 3730 made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver(s) 3726 / antenna(s) 3728 already described) that enables the network entity 3718 communicate with other equipment found in a core network, and / or that enables the network entity 3718 to communicate with external networks, computers, databases, and the like for purposes of operations, administration, and maintenance of the network entity or other equipment operably connected thereto.

[0316] The network entity 3718 may include a scalable RAN module 3732. The scalable RAN module 3732 may be implemented via hardware, software, or combinations thereof. For example, the scalable RAN module 3732 may be implemented as a processor, circuit, and / or instructions 3724 stored in the memory 3722 and executed by the processor(s) 3720. In some examples, the scalable RAN module 3732 may be integrated within the processor(s) 3720 and / or the transceiver(s) 3726. For example, the scalable RAN module 3732 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g.. logic gates and circuitry) within the processor(s) 3720 or the transceiver(s) 3726.

[0317] In embodiments where the network entity 3718 is or includes a RAN-AN, the scalable RAN module 3732 may be used for various aspects of the present disclosure for RAN-ANs.

[0318] In embodiments where the network entity 3718 is or includes a RAN-DF, the scalable RAN module 3732 may be used for various aspects of the present disclosure for RAN-DFs. for example, aspects of FIG. 23, FIG. 25, FIG. 28, and / or FIG. 29.

[0319] For example, the scalable RAN module 3732 configures a network entity 3718 that is or includes a RAN-DF to receive a first user plane data packet of a first RB of a first UE that is served by the RAN by a first RAN-AN set for the first UE; select a first RAN-AN of the first RAN-AN set for the first UE for use to transmit the first user plane data packet to the first UE; and route the first user plane data packet to the first RAN-AN.

[0320] As another example, the scalable RAN module 3732 configures a network entity 3718 that is or includes a RAN-DF to route a first packet of an RB of a UE served by the RAN that is managed by the RAN-DF to a first RAN-AN of a RAN-AN set for the UE;514935-4185-2302,1 P70374WO3receive, from a RAN-CF of the RAN, an instruction to release the first RAN-AN from the RAN-AN set for the UE and to add a second RAN-AN to the RAN-AN set for the UE; route, after receiving the instruction, a second packet of the RB to the second RAN-AN.

[0321] As another example, the scalable RAN module 3732 configures a network entity 3718 that is or includes a RAN-DF to receive, from a RAN-CF of the RAN, a first request message comprising a request to switch the management of the RB to a target RAN-DF; send, to the target RAN-DF, a second request message comprising a second request for the target RAN-DF to perform the management of the RB and context information for the RB; receive, from the target RAN-DF, a first confirmation message comprising a first confirmation that the target RAN-DF performs the management of the RB; send, to a CN, a third request message comprising a third request for the CN to route data packets of the RB to the target RAN-DF; receive, from the CN, a second confirmation message comprising a second confirmation that the CN routes data packets of the RB to the target RAN-DF; and send, to the RAN-CF, a third confirmation message comprising a third confirmation indicating that the target RAN-DF performs the management of the RB.

[0322] As another example, the scalable RAN module 3732 configures a network entity 3718 that is or includes a RAN-DF to receive, from a source RAN-DF that is performing management of an RB of a UE served by the RAN, a first request message comprising a first request for the target RAN-DF to perform the management of the RB and context information for the RB; send, to the source RAN-DF, a first confirmation message comprising a first confirmation that the target RAN-DF performs the management of the RB; receive, from a RAN-CF of the RAN, an identification of a RAN-AN set for the UE; and send, to a RAN-AN of the RAN-AN set, an indication that the target RAN-DF is performing the management of the RB of the UE.

[0323] In embodiments where the network entity 3718 is or includes a RAN-CF, the scalable RAN module 3732 may be used for various aspects of the present disclosure for RAN-CF, for example, aspects of FIG. 26, FIG. 27, FIG. 30. FIG. 31. FIG. 33. and / or FIG. 35.

[0324] For example, the scalable RAN module 3732 configures a network entity 3718 that is or includes a RAN-CF to send, to a UE, a message comprising an instruction for the UE to release a first RAN-AN from a RAN-AN set for the UE and a configuration for524935-4185-2302,1 P70374WO3the UE to use to add a second RAN-AN to the RAN-AN set for the UE: receive, from the second RAN-AN, a first indication that the UE has connected to the second RAN-AN; and send, after receiving the first indication, to a RAN-DF of the RAN managing an RB of the UE, a second indication that the first RAN-AN is released from the RAN-AN set for the UE and that the second RAN-AN is added to the RAN-AN set for the UE.

[0325] As another example, the scalable RAN module 3732 configures a network entity 3718 that is or includes a RAN-CF to send, to a source RAN-DF of the RAN that is performing management of an RB of a UE served by the RAN, a request message comprising a request to switch the management of the RB to a target RAN-DF; receive, from the source RAN-DF, a confirmation message confirming the switch of the management of the RB to the target RAN-DF; and send, to the target RAN-DF, an identification of a RAN-AN set for the UE.

[0326] As another example, the scalable RAN module 3732 configures a network entity 3718 that is or includes a RAN-CF to send, to a target RAN-CF of the RAN, a request message comprising a request to transfer control of a UE served by the RAN to the target RAN-CF and UE-RAN context information for the UE; receive, from the target RAN-CF, a first confirmation message comprising a first confirmation that the target RAN-CF assumes the control of the UE and updated UE-RAN context information; send, to the UE, the updated UE-RAN context information; receive, from the UE, a second confirmation message comprising a second confirmation that the UE received the updated UE-RAN context information; and send, to the target RAN-CF, an indication of a RAN-AN set for the UE.

[0327] As another example, the scalable RAN module 3732 configures a network entity- 3718 that is or includes a RAN-CF to receive, from a source RAN-CF of the RAN that controls a UE served by the RAN, a request message comprising a request to transfer control the UE to the target RAN-CF and UE-RAN context information for the UE; generate updated UE-RAN context information based on the UE-RAN context information received from the source RAN-CF; send, to the source RAN-CF. a confirmation message comprising a confirmation that the target RAN-CF assumes the control of the UE and the updated UE-RAN context information; receive, from the source RAN-CF, an indication of a RAN-AN set for the UE; and send, to a RAN-DF of the RAN that is performing management of an RB of the UE, an indication that the target RAN-CF controls the UE.534935-4185-2302,1 P70374WO3

[0328] As another example, the scalable RAN module 3732 configures a network entity 3718 that is or includes a RAN-CF to receive, from a RAN-AN of the RAN, a connection request message that identifies a UE that has requested service by the RAN through the RAN AN and RAN-AN configuration information for the RAN-AN; send, to a RAN-DF of the RAN, a first request message comprising a request for the RAN-DF to manage a signaling data session for the UE; receive, from the RAN-DF, a first confirmation message confirming that the RAN-DF manages the signaling data session and comprising an AS DP configuration for the RAN-DF; and send, to the UE, via the RAN-AN, a connection setup message comprising the RAN-AN configuration information for the RAN-AN and the AS DP configuration for the RAN-DF.

[0329] As another example, the scalable RAN module 3732 configures a network entity 3718 that is or includes a RAN-CF to send, to a RAN-DF of the RAN, a first request message comprising a first request for the RAN-DF to perform management of an RB for a UE; receive, from the RAN-DF a first confirmation indicating that the RAN-DF performs the management of the RB and comprising an AS DP configuration for the RAN-DF; send, to a RAN-AN of the RAN, a second request message requesting the RAN-AN to operate in a RAN-AN set for the UE; receive, from the RAN-AN, a second confirmation message confirming that the RAN-AN operates in the RAN-AN set for the UE and comprising UE-specific configuration information for the RAN-AN; generate UE RAN context information for the UE using the AS DP configuration for the RAN-DF and the UE-specific RAN-AN configuration information for the RAN-AN; and send, to the UE, a configuration message comprising the UE RAN context information.

[0330] Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of either of the method 2400, the method 3200, and / or the method 3400. This apparatus may be, for example, an apparatus of a UE (such as a wireless device 3702 that is a UE, as described herein).

[0331] Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of either of the method 2400, the method 3200, and / or the method 3400. This non-transitory computer-readable media may be, for example, a memory of a UE (such as a memory 3706 of a wireless device 3702 that is a UE, as described herein).544935-4185-2302,1 P70374WO3

[0332] Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of either of the method 2400, the method 3200, and / or the method 3400. This apparatus may be, for example, an apparatus of a UE (such as a wireless device 3702 that is a UE, as described herein).

[0333] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of either of the method 2400, the method 3200, and / or the method 3400. This apparatus may be, for example, an apparatus of a UE (such as a wireless device 3702 that is a UE, as described herein).

[0334] Embodiments contemplated herein include a signal as described in or related to one or more elements of either of the method 2400. the method 3200, and / or the method 3400.

[0335] Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processor is to cause the processor to carry out one or more elements of either of the method 2400, the method 3200, and / or the method 3400. The processor may be a processor of a UE (such as a processor(s) 3704 of a wireless device 3702 that is a UE, as described herein). These instructions may be, for example, located in the processor and / or on a memory of the UE (such as a memory 3706 of a wireless device 3702 that is a UE, as described herein).

[0336] Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of any procedure of a RAN-AN as discussed herein. This apparatus may be, for example, an apparatus of a RAN-AN (such as a network entity' 3718 that is a RAN-AN, as described herein).

[0337] Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of any of the method 2300, the method 2500, the method 2800, and / or the method 2900. This apparatus may be, for example, an apparatus of a RAN-DF (such as a network entity 3718 that is a RAN-DF, as described herein).

[0338] Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of any of the method 2300, the method 2500, the method 554935-4185-2302,1 P70374WO32800, and / or the method 2900. This non-transitory computer-readable media may be, for example, a memory of a RAN-DF (such as a memory 3722 of a network entity 3718 that is a RAN-DF, as described herein).

[0339] Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of any of the method 2300, the method 2500, the method 2800, and / or the method 2900. This apparatus may be, for example, an apparatus of a RAN-DF (such as a network entity 3718 that is a RAN-DF, as described herein).

[0340] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of any of the method 2300, the method 2500, the method 2800, and / or the method 2900. This apparatus may be, for example, an apparatus of a RAN-DF (such as a network entity 3718 that is a RAN-DF, as described herein).

[0341] Embodiments contemplated herein include a signal as described in or related to one or more elements of any of the method 2300, the method 2500, the method 2800, and / or the method 2900

[0342] Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out one or more elements of any of the method 2300, the method 2500, the method 2800, and / or the method 2900. The processor may be a processor of a RAN-DF (such as a processor(s) 3720 of a network entity 3718 that is a RAN-DF, as described herein). These instructions may be. for example, located in the processor and / or on a memory of the RAN-DF (such as a memory 3722 of a network entity 3718 that is a RAN-DF, as described herein).

[0343] Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of any of the method 2600, the method 2700, the method 3000, the method 3100, the method 3300, and / or the method 3500. This apparatus may be, for example, an apparatus of a RAN-CF (such as a network entity 3718 that is a RAN-CF, as described herein).

[0344] Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to 564935-4185-2302,1 P70374WO3perform one or more elements of any of the method 2600, the method 2700, the method 3000, the method 3100. the method 3300, and / or the method 3500. This non-transitory computer-readable media may be, for example, a memory of a RAN-CF (such as a memory 3722 of a network entity 3718 that is a RAN-CF, as described herein).

[0345] Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of any of the method 2600, the method 2700, the method 3000, the method 3100, the method 3300, and / or the method 3500. This apparatus may be, for example, an apparatus of a RAN-CF (such as a network entity 3718 that is a RAN-CF, as described herein).

[0346] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of any of the method 2600, the method 2700, the method 3000, the method 3100, the method 3300, and / or the method 3500. This apparatus may be, for example, an apparatus of a RAN-CF (such as a network entity 3718 that is a RAN-CF, as described herein).

[0347] Embodiments contemplated herein include a signal as described in or related to one or more elements of any of the method 2600, the method 2700, the method 3000, the method 3100, the method 3300, and / or the method 3500.

[0348] Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out one or more elements of any of the method 2600. the method 2700, the method 3000, the method 3100, the method 3300, and / or the method 3500. The processor may be a processor of a RAN-CF (such as a processor(s) 3720 of a network entity 3718 that is a RAN-CF, as described herein). These instructions may be, for example, located in the processor and / or on a memory of the RAN-CF (such as a memory 3722 of a network entity 3718 that is a RAN-CF, as described herein).

[0349] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and / or methods as set forth herein. For example, a baseband processor as described herein in connection with one or more of the preceding figures may be configured to operate in accordance w ith one or more of the examples set forth574935-4185-2302,1 P70374WO3herein. For another example, circuitry associated with a UE, base station, network element / entity, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein.

[0350] Any of the above described embodiments may be combined with any other embodiment (or combination of embodiments), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0351] Embodiments and implementations of the sy stems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system. A computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and / or firmware.

[0352] It should be recognized that the systems described herein include descriptions of specific embodiments. These embodiments can be combined into single systems, partially combined into other systems, split into multiple systems or divided or combined in other ways. Tn addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment can be used in another embodiment. The parameters, attributes, aspects, etc. are merely described in one or more embodiments for clarity, and it is recognized that the parameters, attributes, aspects, etc. can be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment unless specifically disclaimed herein.

[0353] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.584935-4185-2302,1 P70374WO3

[0354] Although the foregoing has been described in some detail for purposes of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles thereof. It should be noted that there are many alternative ways of implementing both the processes and apparatuses described herein. Accordingly, the present embodiments are to be considered illustrative and not restrictive, and the description is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.594935-4185-2302,1 P70374WO3

Claims

CLAIMS1. A method of a user equipment (UE), comprising:sending, to a RAN access node (AN) (RAN-AN) of a RAN, a connection request message indicating a request for the UE to connect to the RAN;receiving, from a RAN control function (CF) (RAN-CF) of the RAN, via the RAN-AN, a connection setup message comprising RAN-AN configuration information for the RAN-AN and an access stratum (AS) data plane (DP) configuration for a RAN data function (DF) (RAN-DF) of the RAN; andperforming a connection setup for the RAN based on the RAN-AN configuration information for the RAN-AN and the AS DP configuration for the RAN-DF.

2. The method of claim 1, further comprising sending, to the RAN-CF, a confirmation message confirming that the UE has performed the connection setup.

3. The method of claim 1 or claim 2, wherein the connection request message indicates a cause for the UE request.

4. The method of any of claim 1 to claim 3, wherein the connection request message comprises an identifier (ID) for the UE.

5. A method of a radio access network (RAN) control function (CF) (RAN-CF) of a RAN, comprising:receiving, from a RAN access node (AN) (RAN-AN) of the RAN, a connection request message that identifies a user equipment (UE) that has requested service by the RAN through the RAN AN and RAN-AN configuration information for the RAN-AN;sending, to a RAN data function (DF) (RAN-DF) of the RAN, a first request message comprising a request for the RAN-DF to manage a signaling data session for the UE;receiving, from the RAN-DF, a first confirmation message confirming that the RAN-DF manages the signaling data session and comprising an access stratum (AS) data plane (DP) configuration for the RAN-DF; andsending, to the UE, via the RAN-AN, a connection setup message comprising the RAN-AN configuration information for the RAN-AN and the AS DP configuration for the RAN-DF.604935-4185-2302,1 P70374WO36. The method of claim 5, wherein the first request message comprises an identification of the RAN- AN.

7. The method of claim 5 or claim 6, further comprising receiving, from the UE, a second confirmation message confirming that the UE has performed a connection setup using the RAN-AN configuration information for the RAN-AN and the AS DP configuration for the RAN-DF.

8. A method of a user equipment (UE), comprising:sending, to a RAN control function (CF) (RAN-CF) of a RAN, via a RAN access node (AN) (RAN-AN) of the RAN, an indication that the UE has performed a connection setup for the RAN;receiving, from the RAN-CF, a configuration message comprising UE RAN context information for the UE, wherein the UE RAN context information comprises configuration information for the RAN-AN; andperforming data communication through the RAN using the UE RAN context information for the UE.

9. The method of claim 8, wherein the UE RAN context information further comprises a UE RAN identifier (ID) for the UE to use with the RAN-CF.

10. The method of claim 8 or claim 9, wherein the UE RAN context information further comprises a UE activated layer 3 (L3) feature.

11. The method of any of claim 8 to claim 10, wherein the UE RAN context information further comprises configuration information for a radio bearer (RB) used in the data communication.

12. A method of a radio access network (RAN) control function (CF) (RAN-CF) of a RAN, comprising:sending, to a RAN data function (DF) (RAN-DF) of the RAN, a first request message comprising a first request for the RAN-DF to perform management of a radio bearer (RB) for a user equipment (UE);receiving, from the RAN-DF a first confirmation indicating that the RAN-DF performs the management of the RB and comprising an access stratum (AS) data plane (DP) configuration for the RAN-DF;614935-4185-2302,1 P70374WO3sending, to a RAN access node (AN) (RAN-AN) of the RAN, a second request message requesting the RAN-AN to operate in a RAN-AN set for the UE;receiving, from the RAN-AN, a second confirmation message confirming that the RAN-AN operates in the RAN-AN set for the UE and comprising UE-specific configuration information for the RAN-AN;generating UE RAN context information for the UE using the AS DP configuration for the RAN-DF and the UE-specific RAN-AN configuration information for the RAN-AN; andsending, to the UE, a configuration message comprising the UE RAN context information.

13. The method of claim 12, wherein the UE RAN context information comprises a UE RAN identifier (ID) for the UE to use with the RAN-CF.

14. The method of claim 12 or claim 13. wherein the UE RAN context information comprises a UE activated layer 3 (L3) feature.

15. The method of any of claim 12 to claim 14, wherein the UE RAN context information comprises configuration information for the RAN-AN.

16. The method of any of claim 12 to claim 15, wherein the UE RAN context information comprises configuration information for the RB.

17. The method of any of claim 12 to claim 16, further comprising:sending, to a core network (CN), an initial access message that indicates to the CN that the UE is connected to the RAN via the RAN-DF; andreceiving, from the CN. a setup message identifying the RB for establishment for the UE,wherein the first request message is sent to the RAN-DF in response to the receiving the setup message identifying the RB from the CN.

18. The method of any of claim 12 to claim 17, wherein the first request message identifies a quality of service (QoS) requirement for the RB.

19. The method of any of claim 12 to claim 18, wherein the first request message indicates that the RB is for a data session between the UE and the CN.624935-4185-2302,1 P70374WO320. The method of any of claim 12 to claim 19, wherein the second request message further comprises a common configuration for the RAN-AN that is in use by the UE.

21. The method of any of claim 12 to claim 20, wherein the second confirmation message further comprises an identification of a neighbor RAN-AN to the RAN-AN.

22. An apparatus comprising means to perform the method of any of claim 1 to claim 21.

23. A computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform the method of any of claim 1 to claim 21.

24. An apparatus comprising logic, modules, or circuitry to perform the method of any of claim 1 to claim 21.

25. A baseband processor for a user equipment (UE) that is configured to cause the UE to perform one or more elements of any one of claim 1 to claim 4 and claim 8 to claim 11.634935-4185-2302,1 P70374WO3

Images