WO2017196412A1

WO2017196412A1 - Rrc signaling for dual connectivity

Info

Publication number: WO2017196412A1
Application number: PCT/US2017/013789
Authority: WO
Inventors: Sudeep Palat; Yujian Zhang; Richard Burbidge; Candy YIU; Young Hyoung Heo; Umesh PHUYAL
Original assignee: Intel IP Corporation
Priority date: 2016-05-13
Filing date: 2017-01-17
Publication date: 2017-11-16
Also published as: EP3456143A1

Abstract

The present disclosure provides the generation of an RRC message. Generating an RRC message can include decoding a first RRC message to determine that the first RRC message is associated with a UE; encoding a second RRC message, for a UE, comprising the first RRC message; and processing the second RRC message through a user plane to the UE.

Description

RRC SIGNALING FOR DUAL CONNECTIVITY

Related Applications

[0001] This application is a non-provisional of U.S. Provisional Patent Application No. 62/336,391 , filed May 13, 2016, which is hereby incorporated by reference herein in its entirety.

Technical Field

[0002] The present disclosure relates to generating a radio resource control (RRC) message. In particular, the present disclosure relates to RRC signaling for dual connectivity.

Brief Description of the Drawings

[0003] FIG. 1A is a block diagram illustrating generation and transport of RRC messages according to one embodiment.

[0004] FIG. 1 B is a block diagram illustrating an example user plane architecture for dual connectivity.

[0005] FIG. 2 is a block diagram illustrating electronic device circuitry that may be an evolved node B (eNodeB) circuitry, user equipment (UE) circuitry, network node circuitry, or some other type of circuitry according to one embodiment.

[0006] FIG. 3 is a block diagram illustrating a method for generating an RRC message according to one embodiment.

[0007] FIG. 4 is a block diagram illustrating a method for generating an RRC message according to one embodiment.

[0008] FIG. 5 is a block diagram illustrating a method for generating an RRC message according to one embodiment.

[0009] FIG. 6 is a block diagram illustrating components of a device according to one embodiment.

[0010] FIG. 7 is a block diagram illustrating components according to some embodiments.

Detailed Description of Preferred Embodiments

[0011] Wireless mobile communication technology uses various standards and protocols to generate and/or transmit data between a base station and a wireless communication device. Wireless communication system standards and protocols can include, for example, a 3rd Generation Partnership Project (3GPP) long term evolution (LTE); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, which is commonly known to industry groups as worldwide interoperability for microwave access (WiMAX); and the IEEE 802.1 1 standard, which is commonly known to industry groups as Wireless Local Area Network (WLAN) or Wi-Fi. In 3GPP radio access networks (RANs) in LTE systems, a base station may include Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB) and/or Radio Network Controllers (RNCs) in the E-UTRAN, which communicate with a wireless communication device, known as user equipment (UE). In LTE networks, the E-UTRAN may include a plurality of eNodeBs and may communicate with the plurality of UEs. LTE networks include a radio access technology (RAT) and core radio network architecture that can provide high data rate, low latency, packet optimization, and improved system capacity and coverage.

[0012] A non-access stratum (NAS) message may originate in a core such as a mobility management entity (MME) or a next generation core. The core may be referenced as a network core and/or a core network component. The NAS message can be sent from a core to a RAN master cell group (MCG) node via an S1 protocol. The NAS message can be encapsulated by the RRC message either as a direct transfer or as part of an RRC reconfiguration message. Two signaling radio bearers (SRBs), SRB1 with higher priority and SRB2 with lower priority, can be used for RRC message generation and/or transmission, such as RRC message generation and/or transmission of RRC messages carrying a NAS message.

[0013] In previous approaches, a RAN secondary cell group (SCG) node may not generate and/or provide a NAS message, an RRC message, and/or a user plane to a UE. As used herein, the term "user plane" can be used interchangeably with the terms "user plane stack" and/or "user plane protocol stack." A user plane can define the structure of data between a UE and an eNodeB. For example, the user plane can communicate application data and/or data configuring the communication channels between the eNodeB and the UE.

[0014] In some examples, the user plane stack can be used to transport RRC messages. This simplifies RRC message design by reducing packet loss protocols or packets out of sequence protocols, among other simplifications, within the RRC protocol itself. Another simplification can include performing security functions in a single protocol layer for control and user planes instead of performing the security functions in multiple protocol layers.

[0015] The user plane stack can provide an in-sequence, secure, and/or guaranteed delivery for transporting the RRC messages of both an MCG and/or an SCG. NAS messages can be encapsulated by RRC message or sent directly over the user plane. Encapsulating the NAS message in the RRC message provides a benefit of utilizing a single access point for the user plane stack, though it does introduce RRC processing overhead.

[0016] Reference is now made to the figures, in which like reference numerals refer to like elements. For clarity, the first digit of a reference numeral indicates the figure number in which the corresponding element is first used. In the following description, numerous specific details are provided for a thorough understanding of the embodiments disclosed herein. However, those skilled in the art will recognize that the embodiments described herein can be practiced without one or more of the specific details, or with other methods, components, or materials. Further, in some cases, well-known structures, materials, or operations are not shown or described in detail in order to avoid obscuring aspects of the embodiments. Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0017] FIG. 1A is a block diagram illustrating generation and transport of RRC messages according to one embodiment. FIG. 1A includes a cellular network 102. The cellular network 102 includes a radio access network (RAN) SCG node 104, a RAN MCG node 106, and a core 108. FIG. 1 A also includes a UE 1 10.

[0018] In a number of examples, the cellular network 102 can be a long term evolution (LTE) network or a next generation (NG) network, sometimes called New Radio (NR) (e.g., 5G). The cellular network 102 can also have components of an LTE network and/or an NG network. For example, the RAN MCG node 106 can be an NG MCG node and/or an LTE MCG eNodeB. The RAN SCG node 104 can be an NG SCG node and/or an LTE SCG eNodeB. In the example provided in FIG. 1A, the RAN MCG node 106 is an NG MCG eNodeB, and the RAN SCG node 104 is an LTE SCG eNodeB.

[0019] The UE 1 10 can be coupled simultaneously to the RAN SCG node 104 and the RAN MCG node 106. As such, the UE 1 10 can generate/transmit data for/to the RAN MCG node 106 and/or the RAN SCG node 104. The UE 1 10 can also receive/decode data from the RAN MCG node 106 and/or the RAN SCG node 104. Such a configuration is referred to as dual connectivity in 3GPP. A UE may also be coupled to more than two nodes, in which case there could be more than one RAN SCG. Connectivity between a UE and more than one RAN SCG can be referred to as multiconnectivity.

[0020] The UE 1 10 can receive/decode data from the RAN MCG node 106 and/or the RAN SCG node 104. The data can be received directly from the RAN MCG node 106 and/or the RAN SCG node 104. The data can be received indirectly from the RAN MCG node 106 and/or the RAN SCG node 104. For example, the data can be received indirectly from the RAN SCG node 104 via the RAN MCG node 106. The data can also be received indirectly from the RAN MCG node 106 via the RAN SCG node 104.

[0021] FIG. 1 A illustrates a control plane protocol architecture for dual

connectivity including, in respective nodes or elements, instances of a NAS protocol layer 1 12-1 , 1 12-2; instances of an RRC protocol layer 1 14-1 , 1 14-2, 1 14-3, 1 14-4; instances of a user plane 1 16-1 , 1 16-2, 1 16-3, 1 16-4; and instances of a physical layer 1 18-1 , 1 18-2, 1 18-3, 1 18-4. A physical protocol layer (or simply "physical layer" or "PHY") can include, by way of example and not by limitation, a physical downlink control channel (PDCCH), a physical uplink control channel (PUCCH), a random access channel (RACH), a physical downlink shared channel (PDSCH), and a physical uplink shared channel (PUSCH), among other types of channels in a physical layer. As such, control and/or user data can be received by the UE 1 10 via the RAN MCG node 106 (e.g., as represented by the connection between the physical layer 1 18-1 and the physical layer 1 18-3) and/or via the RAN SCG node 104 (e.g., as represented by the connection between the physical layer 1 18-2 and the physical layer 1 18-4). In one example, the RAN SCG node 104 is a new radio(NR) SCG node, and the RAN MCG node 106 is an LTE MCG eNodeB. In another example, the RAN SCG node 104 is an LTE SCG node, and the RAN MCG node 106 is an NR MCG eNodeB.

[0022] Receiving data from the NR SCG node can have different advantages as compared to receiving data from the LTE MCG eNodeB. The NR SCG node can generate data to be transmitted at a higher frequency and/or larger bandwidth and lower latency radio frames than the LTE MCG eNodeB. Transmitting data via a higher frequency/larger bandwidth can include delivery of the data at a faster rate than transmitting data via a lower frequency. However, transmitting data via a higher frequency can include a less reliable delivery of the data as compared to transmitting data via a lower frequency. For example, receiving data from the NG MCG node can include a faster delivery of the data to the UE 1 10 as compared to receiving data from the LTE SCG eNodeB. However, receiving data from the LTE SCG eNodeB can include a more reliable delivery of the data as compared to receiving data from the NG MCG node.

[0023] As such, there may be benefits to delivering the data via the RAN MCG node 106 and/or the RAN SCG node 104. For example, the data can be delivered by the RAN MCG node 106 as well as by the RAN SCG node 104 to take advantage of the benefits of providing data via both an NG MCG node and an LTE SCG eNodeB.

[0024] In some embodiments, an RRC message originating in the RAN MCG node 106, such as an RRC message generated by the instance of the RRC protocol layer 1 14-1 , is delivered to the UE 1 10 directly via the RAN MCG node 106 or via the RAN SCG node 104. An RRC message originating in the RAN MCG node 106 can also be delivered to the UE 1 10 over a mixture of the RAN MCG node 106 and the RAN SCG node 104. This can also involve duplicates of the RRC messages being sent over RAN MCG node 106 and the RAN SCG node 104, for diversity.

[0025] An RRC message originating in the RAN SCG node 104, such as an RRC message generated by the instance of the RRC protocol layer 1 14-2, can be delivered to the UE 1 10 directly via the RAN SCG node 104 or via the RAN MCG node 106. For example, a first RRC message originating in the RAN SCG node 104 can be sent to and incorporated into a second RRC message originating in the RAN MCG node 106. The second RRC message originating in the RAN MCG node 106 can then be sent either through the user plane 1 16-1 and physical layer 1 18-1 , the user plane 1 16-2 and the physical layer 1 18-2, or a mixture of both the user planes 1 16-1 , 1 16-2 and the respective physical layers 1 18-1 , 1 18-2.

[0026] A NAS message originating in the core 108 (e.g., from the instance of the NAS protocol layer 1 12-1 ) can be transferred to the RRC protocol layer 1 14-1 of the RAN MCG node 106. In some examples, the core 108 can include a mobility management entity (MME) in an evolved packet core (EPC) of a 3G or 4G LTE network and/or an entity in a next generation core network (e.g., a 5G core network). The NAS message can be incorporated into an RRC message by the instance of the RRC protocol layer 1 14-1. The RRC message generated by the instance of the RRC protocol layer 1 14-1 can be processed through the user plane 1 16-1 and/or the user plane 1 16-2.

[0027] The user planes 1 16-1 , 1 16-2, 1 16-3, 1 16-4 can include a packet data convergence protocol (PDCP) protocol layer, a radio link control (RLC) protocol layer, and/or a medium access control (MAC) protocol layer. The RRC message originating in the RRC protocol layer 1 14-1 of the RAN MCG node 106 can be processed through the user plane 1 16-1 and provided directly to the UE 1 10 via the physical layer 1 18-1 . The RRC message originating in the RRC protocol layer 1 14-1 can also be processed through the user plane 1 16-1 and the user plane 1 16-2, and provided (e.g., provided indirectly) via the physical layer 1 18-2.

[0028] An RRC message originating in the instance of the RRC protocol layer 1 14-2 of the RAN SCG node 104 can be processed through the user plane 1 16-2 and sent directly to the UE 1 10 via the physical layer 1 18-2. Alternatively, the RRC message originating in the instance of the RRC protocol layer 1 14-2 of the RAN SCG node 104 can be processed through the user plane 1 16-1 of the RAN MCG node 106.

[0029] The UE 1 10 can receive data through the physical layer 1 18-3 and/or the physical layer 1 18-4. The physical layer 1 18-3 and the physical layer 1 18-4 can correspond to the physical layer 1 18-1 and the physical layer 1 18-2, respectively. The UE 1 10 can decrypt the data received via the physical layers 1 18-3 and 1 18-4 to identify an RRC message and/or RRC messages originating from the RRC protocol layer 1 14-1 and/or the RRC protocol layer 1 14-2. The UE 1 10 can process the RRC messages through the user planes 1 16-3 and/or 1 16-4.

[0030] The UE 1 10 can provide the RRC messages originating from the RRC protocol layers 1 14-1 and/or 1 14-2 to the RRC protocol layers 1 14-3 and 1 14-4 after processing the RRC messages through the user planes 1 16-3 and/or 1 16-4. In some examples, an RRC message can be processed through the user plane 1 16-3 before being processed through the user plane 1 16-4. An RRC message can also be processed through all or part of the user plane 1 16-4 before being processed through part of the user plane 1 16-3. The RRC protocol layer 1 14-3 and/or the RRC protocol layer 1 14-4 can process the RRC messages originating from the RRC protocol layers 1 14-1 and/or 1 14-2. [0031] In some examples, the RRC protocol layer 1 14-4 can generate an RRC message based on the RRC message originating from the RRC protocol layer 1 14-1. The RRC protocol layer 1 14-4 can also provide the generated RRC message to the RRC protocol layer 1 14-3. The RRC protocol layer 1 14-4 can also process and respond with RRC messages to an RRC message originating from the RRC protocol layer 1 14-2.

[0032] The RRC protocol layer 1 14-3 can generate an RRC message based on the RRC message originating from the RRC protocol layer 1 14-2. The RRC protocol layer 1 14-3 can also generate an encapsulated RRC message on receipt of RRC messages from the RRC protocol layer 1 14-4. In some examples, the RRC protocol layer 1 14-3 can also process and respond with RRC messages to an RRC message originating from the RRC protocol layer 1 14-1 , which may include, comprise, and/or encapsulate a NAS message originating from the NAS protocol layer 1 12-1 of the core 108. As used herein, the terms include, comprise, and/or encapsulate can be used interchangeably. The RRC protocol layer 1 14-3 can provide the NAS message to the NAS protocol layer 1 12-2 of the UE 1 10 for processing. The RRC messages from the RRCs 1 14-3 and 1 14-4 may be transferred over either of the user plane 1 16-4 or 1 16-3 or a combination of the user planes 1 16-4 and 1 16-3.

[0033] FIG. 1A also includes lines 1 13, 1 15, 1 17, 1 19, and 121 . The lines 1 13, 1 15, 1 17, 1 19, and 121 signify logical correlations or communications between corresponding protocol layers. As such, the line 1 13 can signify a logical correlation between the NAS message generated by the core 108 and the NAS message received by the UE 1 10. The line 1 15 can signify a logical correlation between the RRC protocol layer 1 14-1 and the RRC protocol layer 1 14-3. The line 1 17 can signify a logical correlation between the RRC protocol layer 1 14-2 and the RRC protocol layer 1 14-4. The line 1 19 can signify a logical correlation between the user plane 1 16-1 and the user plane 1 16-3. The line 121 can signify a logical correlation between the user plane 1 16-2 and the user plane 1 16-4.

[0034] FIG. 1 B is a block diagram illustrating an example user plane architecture for dual connectivity. The example user plane architecture may be used, for example, for the instances of the user planes 1 16-1 , 1 16-2 shown in FIG. 1 A. As such, FIG. 1 B includes the RAN MCG node 106 and the RAN SCG node 104 shown in FIG. 1 A. Those skilled in the art will recognize from the disclosure herein, however, that the example user plane architecture shown in FIG. 1 B could also be used for the instances of the user planesl 16-3, 1 16-4 of the UE 1 10 shown in FIG. 1 A. Persons skilled in the art will also recognize from the disclosure herein that each of the RAN MCG node 106 and the RAN SCG node 104 can include one or more user planes, and that the UE 1 10 can include a single user plane or more than two user planes.

[0035] For example, the RAN MCG node 106 shown in FIG. 1 B includes a user plane comprising a PDCP protocol layer 123-1 , an RLC protocol layer 125-1 , and a MAC protocol layer 127-1 . The RAN MCG node 106 can also include a user plane comprising a PDCP protocol layer 123-2, an RLC protocol layer 125-2, and the MAC protocol layer 127-1 . An MCG bearer 129-1 can use the PDCP protocol layer 123-1 , the RLC protocol layer 125-1 , and the MAC protocol layer 127-1 . The MCG bearer 129-1 can carry traffic received for a bearer or quality of service (QoS) flow over S1 interface. A split bearer 129-2 can use the PDCP protocol layer 123-2, the RLC protocol layer 125-2, and the MAC protocol layer 127-1. In some examples, the split bearer 129-2 can use the PDCP protocol layer 123-2, an RLC protocol layer 125-3, and a MAC protocol layer 127-2. A split bearer can also use a combination of the PDCP protocol layer 123-2 with RLC protocol layer 125-2, the MAC protocol layer 127-1 and an RLC protocol layer 125-3, and a MAC protocol layer 127-2. The split bearer 129-2 can be implemented using the X2 or similar interfaces. A split bearer can receive traffic over an S1 interface or RRC messages as discussed above.

[0036] As also shown in FIG. 1 B, the RAN SCG node 104 includes a user plane comprising a PDCP protocol layer 123-3, an RLC protocol layer 125-4, and the MAC protocol layer 127-2. An SCG bearer 129-3 can use the PDCP protocol layer 123-3, the RLC protocol layer 125-4, and the MAC protocol layer 127-2. The SCG bearer 129-3 can carry traffic received over the S1 interface or RRC messages originating in an SCG node.

[0037] FIG. 2 is a block diagram illustrating electronic device circuitry that may be eNodeB circuitry, next generation (e.g., 5G) RAN node circuitry, user equipment (UE) circuitry, network node circuitry, or some other type of circuitry according to one embodiment. FIG. 2 illustrates an electronic device 200 that may be, or may be incorporated into or otherwise part of, an eNodeB, a UE, or some other type of electronic device in accordance with various embodiments. Specifically, the electronic device 200 may be logic and/or circuitry that may be at least partially implemented in one or more of hardware, software, and/or firmware. In embodiments, the electronic device logic may include radio transmit/transmitter logic (e.g., a first transmitter logic 277) and receive/receiver logic (e.g., a first receiver logic 283) coupled to a control logic 273 and/or a processor 271. In embodiments, the transmit/transmitter and/or receive/receiver logic may be elements or modules of transceiver logic. The first transmitter logic 277 and the first receiver logic 283 may be housed in separate devices. For example, the first transmitter logic 277 can be incorporated into a first device while the first receiver logic 283 is incorporated into a second device, or the first transmitter logic 277 and the first receiver logic 283 can be incorporated into a device separate from a device including any combination of the control logic 273, a memory 279, and/or the processor 271 . The electronic device 200 may be coupled with or include one or more antenna elements 285 of one or more antennas. The electronic device 200 and/or the components of the electronic device 200 may be configured to perform operations similar to those described elsewhere in this disclosure.

[0038] In embodiments where the electronic device 200 implements, is

incorporated into, or is otherwise part of a UE and/or an eNodeB, or a device portion thereof, the electronic device 200 can generate an extended synchronization signal (ESS). The processor 271 may be coupled to the first receiver and first transmitter. The memory 279 may be coupled to the processor 271 having control logic instructions thereon that, when executed, generate and/or transmit the ESS.

[0039] In embodiments where the electronic device 200 receives data, generates data, and/or transmits data to/from a UE to implement a downlink signal including the ESS, the processor 271 may be coupled to a receiver and a transmitter. The memory 279 may be coupled to the processor 271 having control logic instructions thereon that, when executed, may be able to generate an RRC message and provide the RRC message from a RAN MCG node and/or a RAN SCG node to a UE in dual connectivity, as described in embodiments herein.

[0040] As used herein, the term "logic" may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, the processor 271 (shared, dedicated, or group), and/or the memory 279 (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide

the described functionality. Specifically, the logic may be at least partially

implemented in, or an element of, hardware, software, and/or firmware. In some embodiments, the electronic device logic may be implemented in, or functions associated with the logic may be implemented by, one or more software or firmware modules.

[0041] FIG. 3 is a block diagram illustrating a method for generating an RRC message according to one embodiment. FIG. 3 includes a method comprising decoding 330 a first RRC message to determine that the first RRC message is associated with a UE; encoding 332 a second RRC message, for a UE, comprising the first RRC message; and processing 334 the second RRC message through a user plane for eventual transmission to the UE.

[0042] The method further comprises decoding a NAS message received from a network core. The second RRC message can further comprise or encapsulate the NAS message. The method can also comprise processing the second RRC message through the user plane of the RAN MCG node and a physical layer of the RAN MCG node and/or any combination of the RAN MCG and the SCG user planes and physical layers. The method can also comprise processing the second RRC message through the user plane of the RAN SCG node and a physical layer of the RAN SCG node.

[0043] The method can also comprise generating a third RRC message at the RAN MCG node and incorporating the third RRC message into a fourth RRC message at the RAN SCG node. The method can also include processing the fourth RRC message through a user plane of the RAN SCG node and a physical layer of the RAN SCG node and/or any combination of the RAN MCG and the SCG user planes and physical layers.

[0044] The UE can be a NR UE or a mixed LTE/NR UE. The RAN SCG node can be an NR RAN SCG node, and the RAN MCG node can be an NR RAN MCG node. The RAN SCG node can be an LTE SCG node, and the RAN MCG node can be an LTE RAN MCG node.

[0045] FIG. 4 is a block diagram illustrating a method for generating an RRC message according to one embodiment. The method can comprise generating 436 a first RRC message, for a UE, at a RAN SCG node; processing 438 the first RRC message through a user plane of the RAN SCG node; and providing 440 the first RRC message from the user plane of the RAN SCG node to a physical layer for communication to the UE. [0046] The first RRC message can comprise a second RRC message, wherein the second RRC message is received by the RAN SCG node from a RAN MCG node. In some examples, providing the first RRC message from the user plane of the RAN SCG node to the physical layer further includes providing the first RRC message from the user plane of the RAN SCG node to a user plane of the RAN MCG node, processing the first RRC message through the user plane of the RAN MCG node, and providing the first RRC message from the user plane of the RAN MCG node to the physical layer for communication to the UE.

[0047] The physical layer can correspond to the RAN MCG node. That is, the physical layer can be a physical layer of the RAN MCG node. In some examples, the physical layer can correspond to the RAN SCG node. That is, the physical layer can be a physical layer of the RAN SCG node.

[0048] The method can further include providing the first RRC message from a first RRC protocol layer corresponding to the RAN SCG node to a second RRC protocol layer corresponding to the RAN MCG node and incorporating the first RRC message in a second RRC message at the second RRC protocol layer

corresponding to the RAN MCG node. The method can also include providing the second RRC message to the user plane of the RAN SCG node to provide the first RRC message to the user plane of the RAN SCG node, and providing the second RRC message from the user plane of the RAN SCG node to the physical layer of the RAN SCG node to provide the first RRC message from the user plane of the RAN SCG node to the physical layer of the RAN SCG node.

[0049] FIG. 5 is a block diagram illustrating a method for generating an RRC message according to one embodiment. The method can comprise decoding 544 a physical layer message comprising the first RRC message, processing 546 the first RRC message through a first user plane corresponding to the RAN SCG node, and processing 548 the first RRC message at an RRC protocol layer. In some embodiments, the method can be executed by a UE. The first phyical layer message can be received by the UE.

[0050] The method can also include processing the first RRC message through a second user plane corresponding to the RAN MCG node. The first RRC message can be processed through the second user plane message corresponding to the RAN MCG node after the first RRC message is processed through part of the first user plane message corresponding to the RAN SCG node. That is, the first RRC message can be processed through part ( e.g., PDCP layer) of the first user plane message corresponding to the RAN SCG node and through part (e.g., RLC and MAC) of the second user plane message corresponding to the RAN MCG node.

[0051] The method can also include decoding the first RRC message to identify a second RRC message. The first RRC message can encapsulate the second RRC message. The method can also include decoding the second RRC message to identify a NAS message including an instance of the NAS corresponding to a RAN node. The NAS of the UE can then process the NAS message including the instance of the NAS corresponding to a RAN node.

[0052] In some examples, processing the first RRC message further comprises decoding, at a first RRC protocol layer corresponding to the RAN SCG node, the first RRC message to identify a second RRC message. Processing the first RRC message can further include providing the second RRC message to a second RRC protocol layer corresponding to the RAN MCG node and processing the second RRC message to identify a NAS message. Processing the first RRC message can also include processing the NAS message at a NAS of the UE. A transport of signaling messages between the network and UE is discussed in this disclosure.

[0053] The embodiments describe a mechanism for carrying RRC signals between a network comprising an MCG and an SCG and a dual-connected UE. The embodiments also describe carrying SCG RRC messages through an LTE network, and the embodiments provide configuration and change options in delivering LTE RRC messages. The embodiments also provide delivery where requested. The embodiments further ensure delivery by carrying messages over an MCG user plane. The embodiments also provide fast delivery and diversity by carrying MCG RRC messages through an SCG user plane. The embodiments also provide fast delivery of SCG RRC messages carrying them directly through an SCG user plane.

[0054] In LTE, a NAS message can originate in an MME and can be sent to an eNodeB over S1 signaling. The NAS message is then encapsulated by an RRC, either as direct transfer or as part of an RRC message (e.g., an RRC reconfiguration message). Further, two signaling radio bearers (SRBs)— SRB1 with higher priority, and SRB2 with lower priority— are used for main RRC messages and (mainly) RRC messages carrying NAS messages, respectively. [0055] In NR, the user plane stack can be used to deliver the RRC messages. Using the user plane stack that provides delivery assurances simplifies the RRC. The user plane stack can address packet loss and/or packets out of sequence within the user plane thereby avoiding building these functions into RRC protocol itself. Further, security functions can be performed in one protocol layer for a control plane and a user plane as in LTE.

[0056] A user plane stack provides an in-sequence, secure, and guaranteed delivery for transport of RRC signaling. NAS signaling can be encapsulated by RRC or sent directly over the user plane. Encapsulating the NAS signaling in an RRC message provides the benefit that only one access point for the user plane stack is defined, though it does introduce some additional RRC processing and overhead.

[0057] The tight interworking of LTE-NR dual connectivity (DC) design can be done in any way and can be different from the solution used for intra-LTE DC. If an NR-NR DC design using intra-LTE DC is used, a number of embodiments can be implemented in addition to the LTE-NR DC solution. If DC within standalone NR is supported, reuse of the main architectural principles for transport of SCG NR RRC signaling for non-standalone NR (where NR as SCG to LTE MCG) and for standalone NR can be used to minimize standardization and implementation efforts.

[0058] RRC signaling originating in SCG and can be transported directly over SCG. For this case, different combinations can be used. For RRC signaling originating in MCG, the RRC signaling can be delivered directly through the MCG and/or sent over a mixture of MCG and SCG through a user plane for diversity. For RRC signaling originating in the SCG, the RRC signaling can be delivered directly through SCG to UE and/or through the MCG RRC (this is similar to what is adopted in LTE DC, but here the SCG content may be transparent to the MCG RRC). The MCG RRC may then be sent either through MCG or SCG at the user plane as mentioned above.

[0059] FIG. 6 is a block diagram illustrating components of a device according to one embodiment. In some embodiments, the device may include application circuitry 603, baseband circuitry 605, Radio Frequency (RF) circuitry 607, front-end module (FEM) circuitry 609, and one or more antennas 614, coupled together at least as shown in FIG. 6. Any combination or subset of these components can be included, for example, in a UE device or an eNodeB device. [0060] The application circuitry 603 may include one or more application processors. By way of non-limiting example, the application circuitry 603 may include one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processor(s) may be operably coupled and/or include memory/storage, and may be configured to execute instructions stored in the memory/storage to enable various applications

and/or operating systems to run on the system.

[0061] By way of non-limiting example, the baseband circuitry 605 may include one or more single-core or multi-core processors. The baseband circuitry 605 may include one or more baseband processors and/or control logic. The baseband circuitry 605 may be configured to process baseband signals received from a receive signal path of the RF circuitry 607. The baseband circuitry 605 may also be configured to generate baseband signals for a transmit signal path of the RF circuitry 607. The baseband circuitry 605 may interface with the application circuitry 603 for generation and processing of the baseband signals, and for controlling operations of the RF circuitry 607.

[0062] By way of non-limiting example, the baseband circuitry 605 may include at least one of a second generation (2G) baseband processor 61 1 A, a third generation (3G) baseband processor 61 1 B, a fourth generation (4G) baseband processor 61 1 C, and other baseband processor(s) 61 1 D for other existing generations and

generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.). The baseband circuitry 605 (e.g., at least one of the baseband processors 61 1 A-61 1 D) may handle various radio control functions that

enable communication with one or more radio networks via the RF circuitry 607. By way of non-limiting example, the radio control functions may include signal modulation/demodulation, encoding/decoding, radio frequency shifting, other functions, and combinations thereof. In some embodiments,

modulation/demodulation circuitry of the baseband circuitry 605 may be programmed to perform Fast-Fourier Transform (FFT), precoding, constellation

mapping/demapping functions, other functions, and combinations thereof. In some embodiments, encoding/decoding circuitry of the baseband circuitry 605 may be programmed to perform convolutions, tail-biting convolutions, turbo, Viterbi, Low Density Parity Check (LDPC) encoder/decoder functions, other functions, and combinations thereof. Embodiments of modulation/demodulation and encoder/decoder functions are not limited to these examples, and may include other suitable functions.

[0063] In some embodiments, the baseband circuitry 605 may include elements of a protocol stack. By way of non-limiting example, elements of an evolved universal terrestrial radio access network (E-UTRAN) protocol include, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or radio resource control (RRC) elements. A central processing unit (CPU) 61 1 E of the baseband circuitry 605 may be

programmed to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers. In some embodiments, the baseband circuitry 605 may include one or more audio digital signal processor(s) (DSP) 61 1 F. The audio DSP(s) 61 1 F may include elements for compression/decompression and echo cancellation. The audio DSP(s) 61 1 F may also include other suitable processing elements.

[0064] The baseband circuitry 605 may further include a memory/storage 61 1 G. The memory/storage 61 1 G may include data and/or instructions for operations performed by the processors of the baseband circuitry 605 stored thereon. In some embodiments, the memory/storage 61 1 G may include any combination of suitable volatile memory and/or non-volatile memory. The memory/storage 61 1 G may also include any combination of various levels of memory/storage including, but not limited to, read-only memory (ROM) having embedded software instructions (e.g., firmware), random access memory (e.g., dynamic random access memory (DRAM)), caches, buffers, etc. In some embodiments, the memory/storage 61 1 G may be shared among the various processors or dedicated to particular processors.

[0065] Components of the baseband circuitry 605 may be suitably combined in a single chip or a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 605 and the application circuitry 603 may be

implemented together, such as, for example, on a system on a chip (SOC).

[0066] In some embodiments, the baseband circuitry 605 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 605 may support communication with an evolved universal terrestrial radio access network (E-UTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), or a wireless personal area network (WPAN). Embodiments in which the baseband circuitry 605 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0067] The RF circuitry 607 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 607 may include switches, filters, amplifiers, etc., to facilitate the communication with the wireless network. The RF circuitry 607 may include a receive signal path, which may include circuitry to down-convert RF signals received from the FEM circuitry 609, and provide baseband signals to the baseband circuitry 605. The RF circuitry 607 may also include a transmit signal path, which may include circuitry to up-convert baseband signals provided by the baseband circuitry 605, and provide RF output signals to the FEM circuitry 609 for

transmission.

[0068] In some embodiments, the RF circuitry 607 may include a receive signal path and a transmit signal path. The receive signal path of the RF circuitry 607 may include a mixer circuitry 613A, an amplifier circuitry 613B, and a filter circuitry 613C. The transmit signal path of the RF circuitry 607 may include the filter circuitry 613C and the mixer circuitry 613A. The RF circuitry 607 may further include a synthesizer circuitry 613D configured to synthesize a frequency for use by the mixer circuitry 613A of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 613A of the receive signal path may be configured to down- convert RF signals received from the FEM circuitry 609 based on the synthesized frequency provided by the synthesizer circuitry 613D. The amplifier circuitry 613B may be configured to amplify the down-converted signals.

[0069] The filter circuitry 613C may include a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 605 for further processing. In some embodiments, the output baseband signals may include zero-frequency baseband signals, although this is not a requirement. In some embodiments, the mixer circuitry 613A of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect. [0070] In some embodiments, the mixer circuitry 613A of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 613D to generate RF output signals for the FEM circuitry 609. The baseband signals may be provided by the baseband circuitry 605 and may be filtered by the filter circuitry 613C. The filter circuitry 613C may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.

[0071] In some embodiments, the mixer circuitry 613A of the receive signal path and the mixer circuitry 613A of the transmit signal path may include two or more mixers, and may be arranged for quadrature downconversion and/or upconversion, respectively. In some embodiments, the mixer circuitry 613A of the receive signal path and the mixer circuitry 613A of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 613A of the receive signal path and the mixer circuitry 613A of the transmit signal path may be arranged for direct downconversion and/or direct upconversion, respectively. In some embodiments, the mixer circuitry 613A of the receive signal path and the mixer circuitry 613A of the transmit signal path may be configured for super-heterodyne operation.

[0072] In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In such embodiments, the RF circuitry 607 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and the baseband circuitry 605 may include a digital baseband interface to communicate with the RF circuitry 607.

[0073] In some dual-mode embodiments, separate radio interference cancellation (IC) circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0074] In some embodiments, the synthesizer circuitry 613D may include one or more of a fractional-N synthesizer and a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may be suitable. For example, the synthesizer circuitry 613D may include a delta-sigma synthesizer, a frequency multiplier, a synthesizer comprising a phase-locked loop with a frequency divider, other synthesizers, and combinations thereof.

[0075] The synthesizer circuitry 613D may be configured to synthesize an output frequency for use by the mixer circuitry 613A of the RF circuitry 607 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 613D may be a fractional N/N+1 synthesizer.

[0076] In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry 605 or the application circuitry 603 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the application circuitry 603.

[0077] The synthesizer circuitry 613D of the RF circuitry 607 may include a divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the divider may include a dual modulus divider (DMD), and the phase accumulator may include a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on a carry-out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements; a phase detector; a charge pump; and a D-type flip-flop. In such embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL may provide negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0078] In some embodiments, the synthesizer circuitry 613D may be configured to generate a carrier frequency as the output frequency. In some embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency, etc.) and used in conjunction with a quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be an LO frequency (fLO). In some embodiments, the RF circuitry 607 may include an IQ/polar converter.

[0079] The FEM circuitry 609 may include a receive signal path, which may include circuitry configured to operate on RF signals received from the one or more antennas 614, amplify the received signals, and provide the amplified versions of the received signals to the RF circuitry 607 for further processing. The FEM circuitry 609 may also include a transmit signal path, which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 607 for transmission by at least one of the one or more antennas 614.

[0080] In some embodiments, the FEM circuitry 609 may include a TX/RX switch configured to switch between a transmit mode and a receive mode operation. The FEM circuitry 609 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry 609 may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 607). The transmit signal path of the FEM circuitry 609 may include a power amplifier (PA) configured to amplify input RF signals (e.g., provided by the RF circuitry 607), and one or more filters configured to generate RF signals for subsequent transmission (e.g., by the one or more antennas 614).

[0081] In some embodiments, the device may include additional elements such as, for example, memory/storage, a display, a camera, one of more sensors, an input/output (I/O) interface, other elements, and combinations thereof.

[0082] In some embodiments, the device may be configured to perform one or more processes, techniques, and/or methods as described herein, or portions thereof.

[0083] FIG. 7 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, FIG. 7 shows a diagrammatic representation of hardware resources 700 including one or more processors (or processor cores) 710, one or more memory/storage devices 720, and one or more communication resources 730, all of which are communicatively coupled via a bus 740.

[0084] The processors 710 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband processor, an application specific integrated circuit (ASIC), a radio-frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor 712 and a processor 714. The memory/storage devices 720 may include main memory, disk storage, or any suitable combination thereof.

[0085] The communication resources 730 may include interconnection and/or network interface components or other suitable devices to communicate with one or more peripheral devices 704 and/or one or more databases 71 1 via a network 708. For example, the communication resources 730 may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular

communication components, Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components.

[0086] Instructions 750 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least one of the processors 710 to perform any one or more of the methodologies discussed herein. The instructions 750 may reside, completely or partially, within at least one of the processors 710 (e.g., within the processor's cache memory), the memory/storage devices 720, or any suitable combination thereof. Furthermore, any portion of the instructions 750 may be transferred to the hardware resources 700 from any combination of the peripheral devices 704 and/or the databases 71 1 . Accordingly, the memory of the processors 710, the memory/storage devices 720, the peripheral devices 704, and the databases 71 1 are examples of computer-readable and machine-readable media.

Example Embodiments

[0087] Example 1 is an apparatus for a radio access network (RAN) master cell group (MCG) node. The apparatus includes electronic memory to store a first radio resource control (RRC) message received from a RAN secondary cell group (SCG) node. The apparatus also includes one or more baseband processors designed to decode the first RRC message to determine that the first RRC message is associated with a user equipment (UE). The apparatus also includes one or more baseband processors designed to encode a second RRC message, for the UE, including the first RRC message, and process the second RRC message through a user plane to the UE. [0088] Example 2 is the apparatus of Example 1 , where the one or more baseband processors are further designed to decode a non-access stratus (NAS) message received from a core network component.

[0089] Example 3 is the apparatus of Example 2, where the second RRC message further includes the NAS message.

[0090] Example 4 is the apparatus of Example 1 , where the one or more baseband processors are further designed to process the second RRC message through the user plane corresponding to the RAN MCG node and a physical layer of the RAN MCG node.

[0091] Example 5 is the apparatus of Example 1 , where the one or more baseband processors are further designed to process the second RRC message through the user plane corresponding to the RAN SCG node and a physical layer of the RAN SCG node.

[0092] Example 6 is the apparatus of Example 1 , where the one or more baseband processors are further designed to generate a third RRC message at the RAN MCG node.

[0093] Example 7 is the apparatus of Example 6, where the one or more baseband processors are further designed to incorporate the third RRC message in a fourth RRC message at the RAN SCG node, and process the fourth RRC message through the user plane corresponding to the RAN SCG node and a physical layer of the RAN SCG node.

[0094] Example 8 is the apparatus of Example 1 , where the UE is a new radio (NR) UE.

[0095] Example 9 is the apparatus of Example 1 , where the RAN SCG node is an NR RAN SCG node, and the RAN MCG node is a long term evolution (LTE) RAN MCG node.

[0096] Example 10 is the apparatus of Example 1 , where the RAN SCG node is an NR RAN SCG node, and the RAN MCG node is an NR RAN MCG node.

[0097] Example 1 1 is the apparatus of Example 1 , where the RAN SCG node is an LTE SCG node, and the RAN MCG node is an NR RAN MCG node.

[0098] Example 12 is a computer-readable storage medium having stored thereon instructions that, when implemented by a computing device, cause the computing device to generate a first radio resource control (RRC) message, for a user equipment (UE), at a radio access network (RAN) secondary cell group (SCG) node, process the first RRC message through a user plane of the RAN SCG node, and provide the first RRC message from the user plane of the RAN SCG node to a physical layer for communication to the UE.

[0099] Example 13 is the computer-readable storage medium of Example 12, where the first RRC message includes a second RRC message received by the RAN SCG node from a RAN master cell group (MCG) node.

[0100] Example 14 is the computer-readable storage medium of Example 12, where the instructions to provide the first RRC message from the user plane of the RAN SCG node to the physical layer further include instructions to provide the first RRC message from the user plane of the RAN SCG node to a user plane of a RAN MCG node, process the first RRC message through the user plane of the RAN MCG node, and provide the first RRC message from the user plane of the RAN MCG node to the physical layer for communication to the UE.

[0101] Example 15 is the computer-readable storage medium of Example 14, where the physical layer corresponds to the RAN MCG node.

[0102] Example 16 is the computer-readable storage medium of Example 12, where the physical layer corresponds to the RAN SCG node.

[0103] Example 17 is the computer-readable storage medium of Example 12, further including instructions to provide the first RRC message from a first RRC corresponding to the RAN SCG node to a second RRC corresponding to the RAN MCG node, and incorporate the first RRC message in a second RRC message at the second RRC corresponding to the RAN MCG node. The computer-readable storage medium also includes instructions to provide the second RRC message to the user plane of the RAN SCG node to provide the first RRC message to the user plane of the RAN SCG node, and provide the second RRC message from the user plane of the RAN SCG node to the physical layer of the RAN SCG node to provide the first RRC message from the user plane of the RAN SCG node to the physical layer of the RAN SCG node.

[0104] Example 18 is an apparatus for a user equipment (UE) in dual connectivity with a radio access network (RAN) master cell group (MCG) node and a RAN secondary cell group (SCG) node, including electronic memory to store a first radio resource control (RRC) message. The Apparatus for a user equipment (UE) in dual connectivity with a radio access network (RAN) master cell group (MCG) node and a RAN secondary cell group (SCG) node also includes one or more baseband processors designed to decode a physical layer message including the first RRC message, process the first RRC message through a first user plane corresponding to the RAN SCG node, and process the first RRC message at an RRC.

[0105] Example 19 is the apparatus of Example 18, where the one or more baseband processors are further designed to process the first RRC message through a second user plane corresponding to the RAN MCG node, decode the first RRC message to identify a second RRC message, decode the second RRC message to identify a non-access stratus (NAS) message, and process the NAS message at a NAS.

[0106] Example 20 is the apparatus of Example 18, where the one or more baseband processors designed to process the first RRC message further include instructions to decode, at a first RRC corresponding to the RAN SCG node, the first RRC message to identify a second RRC message, provide the second RRC message to a second RRC corresponding to the RAN MCG node, process the second RRC message to identify a NAS message, and process the NAS message at a NAS of the UE.

[0107] Example 21 is a method for a radio access network (RAN) master cell group (MCG) node, including storing a first radio resource control (RRC) message received from a RAN secondary cell group (SCG) node, decoding the first RRC message to determine that the first RRC message is associated with a user equipment (UE), encoding a second RRC message, for the UE, including the first RRC message, and processing the second RRC message through a user plane to the UE.

[0108] Example 22 is the method of Example 21 , further including decoding a non-access stratus (NAS) message received from a core network component.

[0109] Example 23 is the method of Example 22, where the second RRC message further includes the NAS message.

[0110] Example 24 is the method of Example 21 , further including processing the second RRC message through the user plane corresponding to the RAN MCG node and a physical layer of the RAN MCG node.

[0111] Example 25 is the method of Example 21 , further including processing the second RRC message through the user plane corresponding to the RAN SCG node and a physical layer of the RAN SCG node. [0112] Example 26 is the method of Example 21 , further including generating a third RRC message at the RAN MCG node.

[0113] Example 27 is the method of Example 26, further including incorporating the third RRC message in a fourth RRC message at the RAN SCG node, and processing the fourth RRC message through the user plane corresponding to the RAN SCG node and a physical layer of the RAN SCG node.

[0114] Example 28 is the method of Example 21 , where the UE is a new radio (NR) UE.

[0115] Example 29 is the method of Example 21 , where the RAN SCG node is an NR RAN SCG node, and the RAN MCG node is a long term evolution (LTE) RAN MCG node.

[0116] Example 30 is the method of Example 21 , where the RAN SCG node is an NR RAN SCG node, and the RAN MCG node is an NR RAN MCG node.

[0117] Example 31 is the method of Example 21 , where the RAN SCG node is an LTE SCG node, and the RAN MCG node is an NR RAN MCG node.

[0118] Example 32 is a method, including generating a first radio resource control (RRC) message, for a user equipment (UE), at a radio access network (RAN) secondary cell group (SCG) node, processing the first RRC message through a user plane of the RAN SCG node, and providing the first RRC message from the user plane of the RAN SCG node to a physical layer for communication to the UE.

[0119] Example 33 is the method of Example 32, where the first RRC message includes a second RRC message received by the RAN SCG node from a RAN master cell group (MCG) node.

[0120] Example 34 is the method of Example 32, where providing the first RRC message from the user plane of the RAN SCG node to the physical layer further includes providing the first RRC message from the user plane of the RAN SCG node to a user plane of a RAN MCG node, processing the first RRC message through the user plane of the RAN MCG node, and providing the first RRC message from the user plane of the RAN MCG node to the physical layer for communication to the UE.

[0121] Example 35 is the method of Example 34, where the physical layer corresponds to the RAN MCG node.

[0122] Example 36 is the method of Example 32, where the physical layer corresponds to the RAN SCG node. [0123] Example 37 is the method of Example 32, further includes providing the first RRC message from a first RRC corresponding to the RAN SCG node to a second RRC corresponding to the RAN MCG node, and incorporating the first RRC message in a second RRC message at the second RRC corresponding to the RAN MCG node. The method further includes providing the second RRC message to the user plane of the RAN SCG node to provide the first RRC message to the user plane of the RAN SCG node, and providing the second RRC message from the user plane of the RAN SCG node to the physical layer of the RAN SCG node to provide the first RRC message from the user plane of the RAN SCG node to the physical layer of the RAN SCG node.

[0124] Example 38 is a method for a user equipment (UE) in dual connectivity with a radio access network (RAN) master cell group (MCG) node and a RAN secondary cell group (SCG) node, including storing a first radio resource control (RRC) message, decoding a physical layer message including the first RRC message, processing the first RRC message through a first user plane

corresponding to the RAN SCG node, and processing the first RRC message at an RRC.

[0125] Example 39 is the method of Example 38, further including processing the first RRC message through a second user plane corresponding to the RAN MCG node, decoding the first RRC message to identify a second RRC message, decoding the second RRC message to identify a non-access stratus (NAS) message, and processing the NAS message at a NAS.

[0126] Example 40 is the method of Example 38, where processing the first RRC message further includes decoding, at a first RRC corresponding to the RAN SCG node, the first RRC message to identify a second RRC message, providing the second RRC message to a second RRC corresponding to the RAN MCG node, processing the second RRC message to identify a NAS message, and processing the NAS message at a NAS of the UE.

[0127] Example 41 is at least one computer-readable storage medium having stored thereon computer-readable instructions, when executed, to implement a method as exemplified in any of Examples 20-40.

[0128] Example 42 is an apparatus including manner to perform a method as exemplified in any of Examples 20-40. [0129] Example 43 is a manner for performing a method as exemplified in any of Examples 20-40.

[0130] Various techniques, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, a non-transitory computer-readable storage medium, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques. In the case of program code execution on programmable computers, the computing device may include a processor, a storage medium readable by the processor (including volatile and nonvolatile memory and/or storage elements), at least one input device, and at least one output device. The volatile and non-volatile memory and/or storage elements may be a RAM, an EPROM, a flash drive, an optical drive, a magnetic hard drive, or another medium for storing electronic data. The eNodeB (or other base station) and UE (or other mobile station) may also include a transceiver component, a counter

component, a processing component, and/or a clock component or timer component. One or more programs that may implement or utilize the various techniques described herein may use an application programming interface (API), reusable controls, and the like. Such programs may be implemented in a high-level procedural or an object-oriented programming language to communicate with a computer system. However, the program(s) may be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or an interpreted language, and combined with hardware implementations.

[0131] It should be understood that many of the functional units described in this specification may be implemented as one or more components, which is a term used to more particularly emphasize their implementation independence. For example, a component may be implemented as a hardware circuit comprising custom very large scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A component may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like.

[0132] Components may also be implemented in software for execution by various types of processors. An identified component of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, a procedure, or a function.

Nevertheless, the executables of an identified component need not be physically located together, but may comprise disparate instructions stored in different locations that, when joined logically together, comprise the component and achieve the stated purpose for the component.

[0133] Indeed, a component of executable code may be a single instruction, or many instructions, and may even be distributed over several different code

segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within components, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network. The components may be passive or active, including agents operable to perform desired functions.

[0134] Reference throughout this specification to "an example" means that a particular feature, structure, or characteristic described in connection with the example is included in at least one embodiment. Thus, appearances of the phrase "in an example" in various places throughout this specification are not necessarily all referring to the same embodiment.

[0135] As used herein, a plurality of items, structural elements, compositional elements, and/or materials may be presented in a common list for convenience. However, these lists should be construed as though each member of the list is individually identified as a separate and unique member. Thus, no individual member of such list should be construed as a de facto equivalent of any other member of the same list solely based on its presentation in a common group without indications to the contrary. In addition, various embodiments and examples may be referred to herein along with alternatives for the various components thereof. It is understood that such embodiments, examples, and alternatives are not to be construed as de facto equivalents of one another, but are to be considered as separate and autonomous representations of embodiments.

[0136] 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 embodiments are not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

1 . An apparatus for a radio access network (RAN) master cell group (MCG) node, comprising:

electronic memory to store a first radio resource control (RRC) message received from a RAN secondary cell group (SCG) node; and

one or more baseband processors configured to:

decode the first RRC message to determine that the first RRC message is associated with a user equipment (UE);

encode a second RRC message, for the UE, comprising the first RRC message; and

process the second RRC message through a user plane to the UE.

2. The apparatus of claim 1 , wherein the one or more baseband processors are further configured to decode a non-access stratus (NAS) message received from a core network component.

3. The apparatus of claim 2, wherein the second RRC message further comprises the NAS message.

4. The apparatus of claim 1 , wherein the one or more baseband processors are further configured to process the second RRC message through the user plane corresponding to the RAN MCG node and a physical layer of the RAN MCG node.

5. The apparatus of claim 1 , wherein the one or more baseband processors are further configured to process the second RRC message through the user plane corresponding to the RAN SCG node and a physical layer of the RAN SCG node.

6. The apparatus of claim 1 , wherein the one or more baseband processors are further configured to generate a third RRC message at the RAN MCG node.

7. The apparatus of claim 6, wherein the one or more baseband processors are further configured to:

incorporate the third RRC message in a fourth RRC message at the RAN SCG node; and

process the fourth RRC message through the user plane corresponding to the RAN SCG node and a physical layer of the RAN SCG node.

8. The apparatus as in claims 1 , 2, 3, 4, 5, 6, or 7, wherein the UE is a new radio (NR) UE.

9. The apparatus as in claims 1 , 2, 3, 4, 5, 6, or 7, wherein the RAN SCG node is an NR RAN SCG node, and the RAN MCG node is a long term evolution (LTE) RAN MCG node.

10. The apparatus as in claims 1 , 2, 3, 4, 5, 6, or 7, wherein the RAN SCG node is an NR RAN SCG node, and the RAN MCG node is an NR RAN MCG node.

1 1 . The apparatus as in claims 1 , 2, 3, 4, 5, 6, or 7, wherein the RAN SCG node is an LTE SCG node, and the RAN MCG node is an NR RAN MCG node.

12. A computer-readable storage medium having stored thereon instructions that, when implemented by a computing device, cause the computing device to:

generate a first radio resource control (RRC) message, for a user equipment (UE), at a radio access network (RAN) secondary cell group (SCG) node;

process the first RRC message through a user plane of the RAN SCG node; and

provide the first RRC message from the user plane of the RAN SCG node to a physical layer for communication to the UE.

13. The computer-readable storage medium of claim 12, wherein the first RRC message comprises a second RRC message received by the RAN SCG node from a RAN master cell group (MCG) node.

14. The computer-readable storage medium of claim 12, wherein the instructions to provide the first RRC message from the user plane of the RAN SCG node to the physical layer further comprise instructions to:

provide the first RRC message from the user plane of the RAN SCG node to a user plane of a RAN MCG node;

process the first RRC message through the user plane of the RAN MCG node; and

provide the first RRC message from the user plane of the RAN MCG node to the physical layer for communication to the UE.

15. The computer-readable storage medium of claim 14, wherein the physical layer corresponds to the RAN MCG node.

16. The computer-readable storage medium as in claims 12, 13, 14, or 15, wherein the physical layer corresponds to the RAN SCG node.

17. The computer-readable storage medium as in claims 12, 13, 14, or 15, further comprising instructions to:

provide the first RRC message from a first RRC corresponding to the RAN SCG node to a second RRC corresponding to the RAN MCG node;

incorporate the first RRC message in a second RRC message at the second RRC corresponding to the RAN MCG node;

provide the second RRC message to the user plane of the RAN SCG node to provide the first RRC message to the user plane of the RAN SCG node; and

provide the second RRC message from the user plane of the RAN SCG node to the physical layer of the RAN SCG node to provide the first RRC message from the user plane of the RAN SCG node to the physical layer of the RAN SCG node.

18. An apparatus for a user equipment (UE) in dual connectivity with a radio access network (RAN) master cell group (MCG) node and a RAN secondary cell group (SCG) node, comprising:

electronic memory to store a first radio resource control (RRC) message; and one or more baseband processors configured to:

decode a physical layer message comprising the first RRC message; process the first RRC message through a first user plane corresponding to the RAN SCG node; and

process the first RRC message at an RRC.

19. The apparatus of claim 18, wherein the one or more baseband processors are further configured to:

process the first RRC message through a second user plane corresponding to the RAN MCG node;

decode the first RRC message to identify a second RRC message;

decode the second RRC message to identify a non-access stratus (NAS) message; and

process the NAS message at a NAS.

20. The apparatus as in claims 18 or 19, wherein the one or more baseband processors configured to process the first RRC message further comprise

instructions to:

decode, at a first RRC corresponding to the RAN SCG node, the first RRC message to identify a second RRC message; provide the second RRC message to a second RRC corresponding to the RAN MCG node;

process the second RRC message to identify a NAS message; and process the NAS message at a NAS of the UE.