Efficient handling of resource control state changes and multi-node connections
Patent Information
- Application Number
- KR1020217010502
- Authority / Receiving Office
- KR · KR
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2018-10-26
- Filing Date
- 2019-10-25
- Publication Date
- 2026-08-11
- Estimated Expiration
- 2039-10-25
Smart Images
Figure 112021041273026-PCT00001_ABST
Abstract
Description
Technology Field
[0001] This specification relates to resource control state changes and the efficient processing of multi-node connections. Background Technology
[0002] The evolution of wireless communication to 5th generation (5G) standards and technologies provides higher data rates and greater capacity with enhanced stability and low latency, which improves mobile broadband services. 5G technology also provides a new class of services for vehicles, fixed wireless broadband, and the Internet of Things (IoT). The functional specifications of the 5G wireless interface are defined as 5G NR (5G New Radio).
[0003] To communicate wirelessly with a network, a User Equipment (UE) can establish a connection to the network using at least one node (e.g., a base station or a serving cell) that supports a 5th Generation Core Network (5GC). In some situations, the UE may use a multi-node connection (e.g., a duplex connection) to connect to multiple nodes at once. By connecting to multiple nodes, performance improvements in user throughput, mobility robustness, or load balancing can be realized. Multiple nodes may be associated with the same Radio Access Technology (RAT) or different RATs. For example, the UE may establish communication with two nodes (e.g., a Master Node (MN) and a Secondary Node (SN)) using a Multi-RAT Duplex (MR-DC) or a New Radio Duplex (NR-DC).
[0004] Current technology executes multiple Radio Resource Control (RRC) procedures to change the resource control state of a UE and to reset, modify, or release connections to a multi-node connection. For example, current technology can execute an RRC connection resumption procedure to change the resource control state of a UE and an RRC reconfiguration procedure to establish a connection with a multi-node connection at different times. Each of the multiple RRC procedures can instruct the UE to transmit or receive.
[0005] However, executing multiple RRC procedures can be inefficient and lead to communication delays of several seconds. Additionally, the sequential execution of multiple RRC procedures provides an opportunity for errors to occur during the intervals between them. For example, a failure may occur if the secondary cell group (SCG) configuration stored by the UE is invalid for the new SN selected by the MN to establish a multi-node connection. Another failure may occur if the UE selects a new MN that cannot support a multi-node connection with the SN and then attempts to communicate with the SN previously used for the multi-node connection. Both the execution of multiple RRC procedures and the additional transmissions performed to report failures can waste the UE's power or timing resources.
[0006] A technique and apparatus for efficiently handling resource control state changes and multi-node connections are described. Instead of performing multiple radio resource control (RRC) procedures to change the resource control state of a User Equipment (UE) and to establish, modify, or disconnect a connection to a multi-node connection, the technique described herein combines multiple RRC procedures into a single RRC procedure that supports both resource control state changes and multi-node connections. In particular, a Master Node (MN) transmits a resource control state and multi-node connection message to the UE that includes both state change information and multi-node connection information. This single message can instruct the UE to switch to a different resource control state and instruct the UE to perform an operation for a multi-node connection. For example, state change information can instruct the UE to switch between a connected state and an inactive state, while multi-node connection information can instruct the UE to reconnect to a multi-node connection, connect without a multi-node connection, disconnect from a multi-node connection, connect to another SN via a multi-node connection, or connect to another MN and another SN via a multi-node connection.
[0007] Resource control status and multi-node connection messages may contain information from multiple messages, such as resource control status messages (e.g., RRC disconnection messages containing interruption information elements (IE) or RRC connection resumption messages) and RRC reconfiguration messages, which are currently transmitted at different times for different RRC procedures. By simultaneously transmitting information from these messages within resource control status and multi-node connection messages, the UE's timing and power resources can be preserved, and failures caused by asynchronous communication of this information can be avoided.
[0008] The embodiments described below include a method performed by a base station for the efficient processing of resource control state changes and multi-node connections. The method includes a base station operating as a master node (MN) for multi-node connections with user equipment (UE) and secondary nodes (SN). The method also includes the base station transmitting a first resource control state and multi-node connection message to the UE. The first resource control state and multi-node connection message includes state change information and multi-node connection information. The state change information instructs the UE to transition from the first resource control state to the second resource control state. The multi-node connection information includes at least one secondary cell group configuration that instructs the user equipment to modify a previously stored secondary cell group configuration based on at least one secondary cell group configuration.
[0009] The embodiments described below include a base station comprising a radio frequency transceiver. The base station also includes a processor and a memory system configured to perform any of the described methods.
[0010] The embodiment described below includes a method performed by a User Equipment (UE) for the efficient processing of resource control state changes and multi-node connections. This method includes a User Equipment that connects to a Master Node (MN) and a Secondary Node (SN) via a multi-node connection. The method also includes a User Equipment that receives a first resource control state and a multi-node connection message containing state change information and multi-node connection information. The multi-node connection information includes one or more secondary cell group configurations. Based on the state change information, the method further includes a User Equipment that transitions from a first resource control state to a second resource control state. The method further includes a User Equipment that modifies a previously stored secondary cell group configuration based on at least one secondary cell group configuration.
[0011] The embodiments described below include user equipment comprising a radio frequency transceiver. The user equipment also includes a processor and a memory system configured to perform any of the described methods.
[0012] The embodiment described below also includes a system having means for efficiently processing resource control state changes and multi-node connections by transmitting a multi-node connection message and a resource control state that includes state change information and multi-node connection information. Brief explanation of the drawing
[0013] Refer to the following drawings to describe devices and technologies for efficiently handling resource control state changes and multi-node connections. Throughout the drawings, the same numbers are used to refer to the same functions and components. FIG. 1 illustrates an exemplary wireless network environment in which resource control state changes and efficient processing of multi-node connections can be implemented. FIG. 2 illustrates an exemplary device diagram of user equipment and a base station for efficient processing of resource control state changes and multi-node connections. Figure 3 shows details of example data and control transactions between entities to efficiently handle resource control state changes and multi-node connections. Figure 4 shows details of example data and control transactions between entities for efficient processing of multi-node connections for resource control state changes and reconnection to multi-node connections. Figure 5 shows details of example data and control transactions between entities for efficient processing of multi-node connections for connecting without resource control state changes and multi-node connections. Figure 6 illustrates different example data and details of control transactions between entities for efficient processing of multi-node connections to change resource control states and release multi-node connections. Figure 7 illustrates details of example data and control transactions between entities for efficiently handling resource control state changes and multi-node connections to connect multi-node connections to other SNs. Figure 8 illustrates details of example data and control transactions between entities for efficiently handling multi-node connections to connect to other MNs without resource control state changes and multi-node connections. Figure 9 illustrates details of example data and control transactions between entities for efficiently handling resource control state changes and multi-node connections to connect multi-node connections to other MNs and other SNs. FIG. 10 illustrates an exemplary method for efficient processing of resource control state changes and multi-node connections. Specific details for implementing the invention
[0014] outline
[0015] A technique and apparatus for efficiently handling resource control state changes and multi-node connections are described. Instead of performing multiple radio resource control (RRC) procedures to change the resource control state of a user equipment (UE) and to establish, modify, or disconnect a connection to a multi-node connection, the technique described herein combines multiple RRC procedures into a single RRC procedure that supports both resource control state changes and multi-node connections. In particular, a master node (MN) transmits a resource control state and multi-node connection message to the UE that includes both state change information and multi-node connection information. This single message can instruct the UE to switch to a different resource control state and instruct the UE to perform operations for a multi-node connection. For example, state change information can instruct the UE to switch between a connected state and an inactive state, while multi-node connection information can instruct the UE to reconnect to a multi-node connection, connect without a multi-node connection, disconnect from a multi-node connection, connect to a multi-node connection for another SN, or connect to a multi-node connection for another MN and another SN.
[0016] Resource control status and multi-node connection messages may contain information from multiple messages, such as resource control status messages (e.g., RRC disconnection messages containing interruption information elements (IE) or RRC connection resumption messages) and RRC reconfiguration messages, which are currently transmitted at different times for different RRC procedures. By simultaneously transmitting information from these messages within resource control status and multi-node connection messages, the UE's timing and power resources can be preserved, and failures caused by asynchronous communication of information can be avoided.
[0017] Example Environment
[0018] FIG. 1 illustrates an exemplary environment (100) comprising a multi-user device (110) (UE 110) exemplified by UE (111), UE (112), and UE (113). Each UE (110) can communicate with a base station (120) (indicated as base stations 121, 122, 123, and 124) via one or more wireless communication links (130) (wireless link 130) exemplified by wireless links (131 and 132). For simplicity, the UE (110) is implemented as a smartphone, but can be implemented as a suitable computing or electronic device such as a mobile communication device, modem, mobile phone, gaming device, navigation device, media device, laptop computer, desktop computer, tablet computer, smart device, vehicle-based communication system, or Internet of Things (IoT) device such as a sensor or actuator. The base station (120) (e.g., Evolved Universal Terrestrial Radio Access Network Node B, E-UTRAN Node B, evolved Node B, eNodeB, eNB, Next Generation Evolved Node B, ng-eNB, Next Generation Node B, gNode B, gNB, etc.) can be implemented as a macro cell, micro cell, small cell, pico cell, etc. or any combination thereof.
[0019] A base station (120) communicates with a UE (110) using a wireless link (131 and 132) which can be implemented as any suitable type of wireless link. The wireless link (131 and 132) includes control and data communication, such as a downlink of data and control information transmitted from the base station (120) to the UE (110), an uplink of other data and control information transmitted from the UE (110) to the base station (120), or both. The wireless link (130) may include one or more wireless links (e.g., radio links) or bearers implemented using any suitable communication protocol or standard, or a combination of communication protocols or standards, such as 3GPP LTE (3rd-Generation Partnership Project Long-Term Evolution), eLTE (Enhanced Long-Term Evolution), 5G NR (5th-Generation New Radio), 4G (4th Generation) standards, etc. Multiple wireless links (130) can be integrated in carrier aggregation to provide a higher data rate for the UE (110). Multiple wireless links (130) from multiple base stations (120) can be configured for Coordinated Multipoint (CoMP) communication with the UE (110).
[0020] The base station (120) is collectively a wireless access network (140) (e.g., RAN, Evolved Universal Terrestrial Radio Access Network, E-UTRAN, 5G NR RAN, or NR RAN). The RAN (140) is exemplified by the NR RAN (141) and the E-UTRAN (142). In FIG. 1, the core network (190) is depicted as comprising different types of core networks: a 5th generation core (5GC) network (150) (5GC 150) and an Evolved Packet Core (EPC) network (160) (EPC (160)). The base stations (121 and 123) of the NR RAN (141) are connected to the 5GC (150). The base stations (122 and 124) of the E-UTRAN (142) are connected to the EPC (160). Optionally or additionally, the base station (122) can be connected to both the 5GC (150) and EPC (160) networks.
[0021] Base stations (121 and 123) are connected to the 5GC (150) via an NG2 interface for control-plane signaling at 102 and 104, respectively, and use an NG3 interface for user-plane data communication. Base stations (122 and 124) are connected to the EPC (160) at 106 and 108, respectively, using an S1 interface for control-plane signaling and user-plane data communication. Optionally or additionally, if base station (122) is connected to the 5GC (150) and EPC (160) networks, base station (122) uses an NG2 interface for control-plane signaling at 180 and connects to the 5GC (150) via an NG3 interface for user-plane data communication.
[0022] In addition to the connection to the core network (190), base stations (120) can communicate with each other. For example, base stations (121 and 123) communicate via the Xn interface at 103, base stations (122 and 123) communicate via the Xn interface at 105, and base stations (122 and 124) communicate via the X2 interface at 107.
[0023] The 5GC (150) includes an access and mobility management function (152) (AMF 152) that provides control plane functions such as registration and authentication, authorization, and mobility management of multiple UEs (110) in a 5G NR network. The EPC (160) includes a mobility management entity (162) (MME 162) that provides control plane functions such as registration and authentication, authorization, or mobility management of multiple UEs (110) in an E-UTRA network. The AMF (152) and MME (162) communicate with a base station (120) in the RAN (140) and also communicate with multiple (multiple) UEs (110) using the base station (120).
[0024] The UE (110) may use a multi-node connection to connect to multiple nodes at once (e.g., at least two base stations or serving cells). Other types of multi-node connections may include a multi-RAT dual (dual) connection (MR-DC) or a new radio dual connection (NR-DC). Through the MR-DC, the UE (110) can connect to the 5GC via base stations (121 and 122), either of which can operate as an MN or SN. Through the NR-DC, the UE (110) can connect to the 5GC via base stations (121 and 123). Performance improvements in user throughput, mobility robustness, or load balancing can be realized through multi-node connections. However, to avoid wasting UE resources or communication delays, the UE (110) and the base station (120) each include a resource control module capable of jointly executing a single procedure that supports resource control state changes and multi-node connections, as described in FIG. 2.
[0025] Example device
[0026] FIG. 2 illustrates an exemplary device diagram (200) of a UE (110) and a base station (120) for efficient processing of resource control state changes and multi-node connections. The UE (110) and the base station (120) may include additional functions and interfaces omitted in FIG. 2 for clarity. The UE (110) includes a radio frequency transceiver, a radio frequency (RF) front end (204) (RF front end (204)), and an antenna (202), such as an LTE transceiver (206) and / or a 5G NR transceiver (208) for communicating with the base station (120) in a 5G RAN (141) and / or E-UTRAN (142). The RF front end (204) of the UE (110) may combine or connect the LTE transceiver (206) and the 5G NR transceiver (208) to the antenna (202) to facilitate various types of wireless communication. The antenna (202) of the UE (110) may include an array of multiple antennas configured similarly or differently from each other. The antenna (202) and the RF front end (204) may be tuned and / or tunable for one or more frequency bands defined by 3GPP LTE and 5G NR communication standards and implemented by an LTE transceiver (206) and / or a 5G NR transceiver (208).
[0027] The UE (110) also includes processor(s) (210) and a computer-readable storage medium (212) (CRM) (212). The processor (210) may be a single-core processor or a multi-core processor composed of various materials such as silicon, polysilicon, high dielectric constant, copper, etc. The computer-readable storage medium described herein excludes radio signals. The CRM (212) may include a suitable memory or storage device such as random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or flash memory that can be used to store device data (214) of the UE (110). Device data (214) includes user data, multimedia data, beamforming codebooks, applications and / or the operating system of the UE (110), which can be executed by the processor(s) (210) to enable user plane communication, control plane signaling, and user interaction with the UE (110).
[0028] The CRM (212) also includes a resource control module (216). Alternatively or additionally, the resource control module (216) may be implemented wholly or partially as hardware logic or circuitry that is integrated with or separate from other components of the UE (110). The resource control module (216) may implement a wireless resource control (RRC) layer as described in accordance with the wireless communication standard. The resource control module (216) controls the resource control state of the UE (110) and instructs the UE (110) to perform operations according to the resource control state. Exemplary resource control states include a connected state (e.g., RRC connected state), an inactive state (e.g., RRC inactive state), or an idle state (e.g., RRC idle state). Generally, when the UE (110) is in a connected state, the connection with the base station (120) is active. In an inactive state, the connection with the base station (120) is suspended. If the UE (110) is in an idle state, the connection with the base station (120) is disconnected.
[0029] The resource control module (216) can also manage information for multi-node connections. For example, the resource control module (216) can store, update, or release one or more master cell group (MCG) configurations or secondary cell group (SCG) configurations used for multi-node connections. Typically, the UE (110) uses an MCG configuration to communicate with the MN and an SCG configuration to communicate with the SN. Various types of MCG or SCG configurations may include physical layer configurations, MAC (Medium Access Control) configurations, RLC (Radio Link Control) configurations, PDCP (Packet Data Convergence Protocol) configurations, radio bearer configurations, random access configurations, etc.
[0030] In at least some embodiments, the resource control module (216) configures an LTE transceiver (206) or a 5G NR transceiver (208) for communication with the base station (120). In this way, the resource control module (216) can receive resource control status and multi-node connection messages as further described with respect to FIG. 3.
[0031] The device diagram for the base station (120) illustrated in FIG. 2 includes a single network node (e.g., gNode B). The functions of the base station (120) may be distributed across multiple network nodes or devices and may be distributed in any manner suitable for performing the functions described herein. The base station (120) includes one or more radio frequency transceivers, such as one or more LTE transceivers (256) and / or one or more 5G NR transceivers (258) for communicating with the UE (110), a radio frequency (RF) front end (254) (RF front end (254)), and an antenna (252). The RF front end (254) of the base station (120) may combine or connect the LTE transceivers (256) and 5G NR transceivers (258) to the antenna (252) to facilitate various types of wireless communication. The antenna (252) of the base station (120) may include an array of multiple antennas that are similar or different from each other. The antenna (252) and RF front end (254) may be tuned to and / or tunable to one or more frequency bands defined by 3GPP LTE and 5G NR communication standards and implemented by an LTE transceiver (256) and / or a 5G NR transceiver (258). Additionally, the antenna (252), RF front end (254), LTE transceiver (256) and / or 5G NR transceiver (258) may be configured to support beamforming, such as "Massive-MIMO," for transmitting and receiving communication with the UE (110).
[0032] The base station (120) also includes processor(s) (260) and a computer-readable storage medium (262) (CRM 262). The processor (260) may be a single-core processor or a multi-core processor composed of various materials such as silicon, polysilicon, high dielectric constant, copper, etc. The CRM (262) may include any suitable memory or storage device, such as handed-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or flash memory that can be used to store device data (264) of the base station (120). The device data (264) includes network scheduling data, wireless resource management data, beamforming codebook, applications, and / or operating systems of the base station (120) that are executable by the processor (260) to enable communication with the UE (110).
[0033] The CRM (262) also includes a resource control module (266). Alternatively or additionally, the resource control module (266) may be implemented wholly or partially as hardware logic or circuits that are integrated with or separated from other components of the base station (120). In at least some embodiments, the resource control module (266) comprises an LTE transceiver (256) and a 5G NR transceiver (258) for communication with the UE (110) and communication with the core network (190). In particular, the resource control module (266) may transmit resource control status and multi-node connection messages to the UE (110), as further described in connection with FIG. 3. In this way, the resource control module (266) of the base station (120) may communicate with the resource control module (216) of the UE (110) so that the resource control modules (216 and 266) jointly execute a single procedure that supports both resource control status changes and multi-node connections. The resource control module (266) can also manage information about the multi-node connection by storing or updating the MCG and SCG configurations used for the multi-node connection.
[0034] The base station (120) includes an inter-base station interface (268), such as an Xn and / or X2 interface, to exchange user plane and control plane data with other base stations (120). The base station (120) also includes a core network interface (270) to exchange information with core network functions and entities.
[0035] The resource control module (216) of the UE (110) and the resource control module (266) of the base station (120) can at least partially implement resource control state changes and efficient processing of multi-node connections as described in this specification. FIGS. 3 through 9 further illustrate exemplary data and control transactions that can be performed by the resource control modules (216 and 266).
[0036] Efficient handling of resource control state changes and multi-node connections
[0037] FIG. 3 illustrates details of example data and control transactions between entities to efficiently handle resource control state changes and multi-node connections. In this example, the UE (110) connects to a master node (MN) (302) (e.g., base station (121)) and at least one secondary node (SN) (304) (e.g., base station (122 or 123)) via a multi-node connection. For example, the UE (110) may connect to the MN (302) and the SN (304) via a dual connection (e.g., MR-DC or NR-DC). To establish a connection via a multi-node connection, the MN (302) may send an SN addition request message (not shown) to the SN (304), and the SN (304) may respond with an SN addition request acknowledgment message (not shown). The SN addition request approval message may include one or more SCG configurations that enable the UE (110) to communicate with the SN (304). The MN (302) may transmit the SCG configurations to the UE (110) in a reconfiguration message (e.g., an RRC reconfiguration message or an RRC connection reconfiguration message) (not shown). Both the UE (110) and the MN (302) may store the SCG configurations provided indirectly or directly by the SN (304).
[0038] In 305, the UE (110) is connected to the MN (302) and SN (304) via a multi-node connectivity. Through this connection, the UE (110) can communicate directly with the MN (302) and directly or indirectly with the SN (304). For example, the UE (110), MN (302), or SN (304) can communicate RRC messages or application data with each other. Various types of data and control transactions may occur while the connection through the multi-node connectivity is active, examples of which are further described in relation to FIG. 4.
[0039] In some situations, MN (302) and SN (304) perform an SN request procedure (310). During the SN request procedure (310), MN (302) sends an SN request message (316) (e.g., an SN modification request message or an SN addition request message) to SN (304) as illustrated in 315. In some situations, the SN request message (316) may include a stored SCG configuration (318) that SN (304) previously provided to MN (302). The stored SCG configuration (318) is a full SCG configuration containing a complete set of information elements (IE) that enable the UE (110) to communicate with SN (304). Optionally, the SN request message (316) may include an IE that instructs SN (304) to send a delta SCG configuration based on the stored SCG configuration (318). A delta SCG configuration includes one or more IEs of a new or changed SCG configuration in relation to a previously stored SCG configuration (318). In other situations, the SN request message (316) does not include the stored SCG configuration (318) that instructs the SN (304) to respond to the request with a full SCG configuration (see below). For example, if the SN (304) has not previously sent an SCG configuration to the MN (302), the stored SCG configuration (318) may not be included in the SN request message (316).
[0040] In 320, SN (304) sends an SN response message (322) (e.g., an SN add request confirmation message or an SN modify request confirmation message) to MN (302). Depending on the situation, the SN response message (322) may or may not include an SCG configuration (351), which may be a delta SCG configuration or a full SCG configuration. In some cases, if the SN request message (316) does not include a stored SCG configuration (318), SN (304) may decide to send a full (full) SCG configuration. In other cases, if the SN request message (316) includes a stored SCG configuration (318), or if the SN request message (316) includes an IE that forces SN (304) to send a delta SCG configuration, SN (304) may decide to send a delta SCG configuration. In another case, SN (304) may ignore the stored SCG configuration (318) provided by the SN request message (316) and transmit the pool (full) SCG configuration as the SCG configuration (351).
[0041] Sometimes, the SN (304) may reject the SN request message (316) or be unable to provide the SCG configuration (351). In this situation, the SN (304) may not respond to the SN request message (316) in a given time period, or instead respond with an SN response message (322) containing a rejection element, in which case the MN (302) may disconnect from the multi-node connection using the resource control status and multi-node connection message (326), as further described in relation to FIG. 5.
[0042] In 325, the MN (302) transmits a resource control status and multi-node connection message (326) to the UE (110). The resource control status and multi-node connection message (326) may be transmitted due to other circumstances while a connection having a multi-node connection is active or interrupted. The resource control status and multi-node connection message (326) includes both state change information (340) and multi-node connection information (350).
[0043] State change information (340) instructs the UE (110) to transition from its current resource control state to another resource control state. For example, the state change information (340) may include a connection resumption IE (341) (e.g., connection resumption information) that instructs the UE (110) to transition from an inactive state to a connected state. As another example, the state change information (340) may include a connection interruption IE (342) (e.g., connection interruption information) that instructs the UE (110) to transition from a connected state to an inactive state.
[0044] The multi-node connection information (350) may include at least one SCG configuration (351) or a multi-node disconnection indicator (352). The SCG configuration (351) may be a delta SCG configuration or a pool SCG configuration. The use of a delta SCG configuration may reduce the size of the resource control state and multi-node connection message (326) compared to the use of a pool (full) SCG configuration. The multi-node connection information (350) may also include an indicator that instructs the UE (110) to modify or replace a previously stored SCG configuration with the SCG configuration (351) provided by the resource control state and multi-node connection message (326).
[0045] The multi-node disconnection indicator (352) may instruct the UE (110) to release a previously stored SCG configuration associated with the SN (304). In this way, the connection with the multi-node connection at 305 may be released. In some cases, the multi-node connection information (350) may include at least one MCG configuration (353), which may be a delta MCG configuration or a pool (full) MCG configuration similar to the SCG configuration (351).
[0046] In 330, the UE (110) may send an acknowledgment message (332) in response to receiving a resource control status and multi-node connection message (326). As illustrated in FIGS. 4 through 9, the resource control status and multi-node connection message (326) is sent to simultaneously convey state change information (340) and multi-node connection information (350).
[0047] FIG. 4 shows details of example data and control transactions between entities for efficient processing of multi-node connections for resource control state changes and reconnection to multi-node connections. As described above with respect to FIG. 3, UE (110) connects to MN (302) and SN (304) via a multi-node connection at 305. In some cases, an SCG configuration (402) may be provided to MN (302) by SN (304) via an active (activity) notification message (406) or SN modification procedure (410) while the connection with the multi-node connection is active. With the SCG configuration (402), MN (302) can add or update the stored SCG configuration (318).
[0048] For example, in 405, the SN (304) transmits an active (activity) notification message (406) along with the SCG configuration (402). The active notification message (406) may also be used by the SN (304) to inform the MN (302) of data inactivity between the SN (304) and the UE (110). Data inactivity indicates a situation where the SN (304) does not receive a request to transmit or receive data from the UE (110). This may cause the MN (302) to perform a connection termination procedure (415), which is further explained below.
[0049] During the SN modification procedure (410), MN (302) may send an SN modification request message (not shown) to SN (304) to instruct SN (304) to provide the SCG configuration (402). SN (304) may include the SCG configuration (402) in the SN modification request acknowledgment message (not shown) sent to MN (302). However, in some cases, SN (304) may instead respond with an SN modification request acknowledgment message that does not include the SCG configuration (402). Sometimes, this SN modification request acknowledgment message may include a rejection element indicating to MN (302) that SN (304) cannot provide the SCG configuration (402).
[0050] While a connection via a multi-node connection is active, the SN (304) may decide to add or modify the SCG configuration (402). To instruct the UE (110) to use this new SCG configuration, the SN (304) may initiate the execution of an SCG reconfiguration procedure (not shown) with the UE (110). During the SCG reconfiguration procedure, the SN (304) may send a reconfiguration message with the SCG configuration (e.g., an RRC reconfiguration message or an RRC connection reconfiguration message) to the UE (110). In response to receiving the reconfiguration message, the UE (110) may save the SCG configuration and send an SCG reconfiguration completion message (e.g., an RRC reconfiguration completion message or an RRC connection reconfiguration completion message) to the SN (304). The SCG reconfiguration completion message may notify the SN (304) that the UE (110) can use the SCG configuration for future communication using the multi-node connection.
[0051] While the connection with the multi-node connection is active, the connection termination procedure (415) is jointly executed by the UE (110), MN (302), and SN (304). The connection termination procedure (415) terminates the connection with the multi-node connection and instructs the UE (110) to transition from a connected state to an inactive state. The connection termination procedure (415) may be performed in response to a decision by the MN (302) to terminate communication, or in response to the SN (304) sending an activity notification message (406) to the MN (302) to inform the MN (302) of data inactivity between the SN (304) and the UE (110). During the connection termination procedure (415), the MN (302) may perform the SN modification procedure (410) to release the lower layer of the SN (304) or release the SCG configuration stored by the SN (304). MN (302) can also send a connection interruption message to UE (110) (e.g., an RRC release message with SuspendConfig IE or an RRC disconnection message with InactiveConfig IE) to instruct UE (110) to switch from a connected state to an inactive state.
[0052] Generally, the inactive state allows the UE (110) to conserve power and retain information in order to efficiently reconnect to the core network (190). While in the inactive state, the UE (110) can continue to store one or more MCG configurations and one or more SCG configurations associated with the multi-node connection in 305. By storing these configurations, the UE (110) can easily reconnect to the multi-node connection for the MN (302) and SN (304). The UE (110) can also perform some actions, such as a cell re-selection procedure, while in the inactive state. In some situations, the cell re-selection procedure may instruct the UE (110) to connect to another MN, as further described in relation to FIGS. 8 and 9.
[0053] While the UE (110) is in an inactive state, a connection resumption initiation procedure (420) may be performed between the UE (110) and the MN (302). Generally, the connection resumption initiation procedure (420) triggers the UE (110) and the MN (302) (or other MNs shown in FIGS. 8 and 9) to establish a connection. In other words, the connection resumption initiation procedure (420) may include a beginning set of data and control transactions that are considered part of the connection resumption procedure, which causes the UE (110) to transition to a connected state.
[0054] The connection resumption initiation procedure (420) may be performed in response to a decision by the MN (302) to re-establish communication with the UE (110). Sometimes this decision is based on the SN (304) sending a second activity notification message to the MN (302) to indicate data activity. In other cases, this decision is based on the MN (302) receiving a connection resumption request message (e.g., an RRC resumption request message or an RRC connection resumption request message) from the UE (110). The second activity notification message or the connection resumption request message may include a request to establish a connection with a multi-node connection. Before sending the connection resumption request message, the UE (110) and the MN (302) may perform a random access procedure as part of the connection resumption initiation procedure (420) so that the UE (110) can use an uplink grant configured by the random access procedure to send the connection resumption request message.
[0055] In response to the connection resumption initiation procedure (420) or as part of the connection resumption procedure, the MN (302) and SN (304) may perform the SN request procedure (310) as described for FIG. 3. In this case, the MN (302) receives an SCG configuration (351) from the SN (304) during the SN request procedure (310). The SCG configuration (351) may be the most recent SCG configuration used while the connection using the multi-node connection was active at 305. In some cases, the MN (302) may not have prior knowledge of the SCG configuration (351). This may occur if the SN (304) communicated the SCG configuration (351) directly with the UE (110) (e.g., using a dedicated signaling radio bearer (SRB)). Therefore, the SN request procedure (310) enables MN (302) to obtain the SCG configuration (351).
[0056] In 425, the MN (302) transmits a multi-node connection message (326) and resource control status to the UE (110), having an SCG configuration (351) and a connection resumption IE (341), as described in FIG. 3. In this example scenario, the SCG configuration (351) and the connection resumption IE (341) are in the form of the multi-node connection information (350) and state change information (340) of FIG. 3, respectively. Using the SCG configuration (351), the UE (110) can reconnect to a multi-node connection with the MN (302) and SN (304) as illustrated in 430. In some situations, the SCG configuration (351) may include a random access configuration (not shown). With the random access configuration, the UE (110) can perform a random access procedure with the SN (304) to reset the connection with the SN (304). Generally, the execution of the SN request procedure (310) and the transmission of the resource control status and multi-node connection message (326) allow the multi-node connection in 305 to be reset between the UE (110), MN (302) and SN (304).
[0057] FIG. 5 shows details of example data and control transactions between entities for efficient processing of multi-node connections for connecting without resource control state changes and multi-node connections. Similar to FIG. 4, UE (110) connects to MN (302) and SN (304) via multi-node connections. The connection termination procedure (415), connection resumption initiation (start) procedure (420), and SN request procedure (310) can also be performed as described above.
[0058] In contrast to FIG. 4, however, the SN (304) of FIG. 5 does not transmit the SCG configuration (351) to the MN (302) during the SN request procedure (310). This may occur if the SN (304) rejects the SN request message (316) or if the SN (304) is unable to provide the SCG configuration (351).
[0059] In 505, the MN (302) transmits a resource control status and a multi-node connection message (326) to the UE (110) along with a connection resumption IE (341) and a multi-node disconnection indicator (352). As described above with respect to FIG. 4, the connection resumption IE (341) instructs the UE (110) to transition from an inactive state to a connected state. By including the multi-node disconnection indicator (352), which is in the form of the multi-node connection information (350) of FIG. 3, the MN (302) instructs the UE (110) to release one or more SCG configurations stored by the UE (110). In this way, the connection having the multi-node connection is released, and the UE (110) connects to the MN (302) without the multi-node connection as illustrated in 510. In this case, the execution of the SN request procedure (310), the resource control status, and the transmission of the multi-node connection message (326) allow a single-node connection to be established between the UE (110) and the MN (302), and enable the multi-node connection established in 305 between the UE (110), the MN (302), and the SN (304) to be released.
[0060] FIG. 6 illustrates other example data and details of control transactions between entities for efficient processing of multi-node connections to change resource control states and to disconnect multi-node connections. In 605, MN (302) decides to disconnect from UE (110) and disconnect from multi-node connections. Because MN (302) decides to disconnect from multi-node connections, MN (302) may decide not to execute the SN request procedure (310) of FIG. 3.
[0061] In 610, the MN (302) transmits resource control status and multi-node connection messages (326) along with a multi-node disconnection indicator (352) and a disconnection IE (606). In this example scenario, the multi-node disconnection indicator (352) and the disconnection IE (606) are in the form of the multi-node connection information (350) and state change information (340) of FIG. 3, respectively. Similar to FIG. 5, the multi-node disconnection indicator instructs the UE (110) to release the SCG configuration associated with the multi-node connection in 305. By including the disconnection IE (606), the MN (302) also instructs the UE (110) to transition from a connected state to an inactive state.
[0062] At 615, the connection with the MN (302) is terminated and the connection through the multi-node connection is released. Typically, the transmission of the resource control status and multi-node connection message (326) enables the release of the multi-node connection between the UE (110), MN (302), and SN (304) at 305. The UE (110) may remain inactive until the connection resumption procedure is performed.
[0063] FIG. 7 illustrates details of example data and control transactions between entities for efficiently handling resource control state changes and multi-node connections to connect a multi-node connection to another SN. In this example, MN (302) decides to establish a multi-node connection with SN (702) instead of SN (304), which was previously used for a multi-node connection in 305. Using the technique described below, MN (302) can switch from supporting a multi-node connection with SN (304) to supporting a multi-node connection with SN (702). In some examples, this may occur when UE (110) moves to another location that has coverage with SN (702) and not coverage with SN (304) while UE (110) is in an inactive state.
[0064] In 305, a connection with multiple nodes is activated. Although not explicitly shown, the SN (304) may provide the SCG configuration (351) to the MN (302) via an activity notification message (406) or an SN modification procedure (410) as illustrated in FIG. 4. In this example, the connection termination procedure (415) and the connection resumption initiation procedure (420) are performed as described above for FIG. 4. In other situations, the MN (302) may perform the SN request procedure (705) with the SN (702) and / or the SN request procedure (710) with the SN (304). Generally, the SN request procedure (705, 710) is similar to the SN request procedure (310) described in FIG. 3.
[0065] During the SN request procedure (705) having SN (702), MN (302) may transmit an SN request message (316) with or without a stored SCG configuration (318), and SN (702) may transmit an SN response message (322) with an SCG configuration (351). As previously described, the SCG configuration (351) may be a delta SCG configuration based on the stored SCG configuration (318) or the entire SCG configuration.
[0066] In a situation where there is no SCG configuration (318) stored in MN (302), MN (302) may execute an SN request procedure (710) with SN (304) to request SN (304) to provide an SCG configuration such as the currently stored SCG configuration of UE (110). If SN (304) responds with an SCG configuration, MN (302) may add a new stored SCG configuration (318) or update the stored SCG configuration (318) based on this SCG configuration. MN (302) may also include the stored SCG configuration (318) in the SN request message (316) of the SN request procedure (705). Alternatively, if SN (304) does not respond with an SCG configuration or includes a rejection element in the SN response message (322) during the SN request procedure (710), MN (302) may transmit the SN request message (316) of the SN request procedure (705) without the stored SCG configuration (318) as previously described.
[0067] In 715, the MN (302) transmits a resource control status and multi-node connection message (326) along with the SCG configuration (351) provided during the connection resumption IE (341) and SN request procedure (705). Using the SCG configuration (351), the UE (110) establishes a multi-node connection for the MN (302) and SN (702) as illustrated in 720. Generally, the execution of the SN request procedure (705) and the transmission of the resource control status and multi-node connection message (326) enable a multi-node connection to be established between the UE (110), MN (302), and SN (702).
[0068] FIG. 8 illustrates details of example data and control transactions between entities for efficiently handling multi-node connections to connect to another MN without resource control state changes and multi-node connections. In this example, UE (110) decides to connect to MN (802) instead of MN (302), which was previously used for multi-node connections in 305. MN (802) may be selected by UE (110) during a cell re-selection procedure that may occur while UE (110) is in an inactive state. With the technique described below, UE (110) can connect to MN (802) without multi-node connections in a situation where MN (802) cannot connect to SN (304) because MN (802) does not have a connection interface with SN (304).
[0069] In 305, a connection via a multi-node connection is enabled. Although not explicitly shown, the SN (304) may provide the SCG configuration (402) to the MN (302) via an activity notification message (406) similar to that shown in FIG. 4 or an SN modification procedure (410). In this example, the connection termination procedure (415) and the connection resumption initiation procedure (420) are performed as described above for FIG. 4.
[0070] In this example, the UE context request procedure (805) may be performed between MN (802) and MN (302) as part of a connection resumption procedure or in response to a connection resumption initiation procedure (420). During the UE context request procedure (805), MN (802) may send a UE context request message (812) to MN (302) as illustrated in 810. Typically, the UE context request message (812) instructs MN (302) to provide one or more configurations used for multi-node connections in 305.
[0071] In 815, the MN (302) may send a UE context response message (816) to the MN (802). The UE context response message (816) may include one or more MCG configurations or one or more SCG configurations associated with the connection in 305. In some situations, the UE context request message (812) may instruct the MN (302) and the SN (304) to perform the SN request procedure (310). The SN request procedure (310) of FIG. 8 allows the MN (302) to request that the SN (304) provide an SCG configuration such as the UE (110)'s stored SCG configuration. If the SN (304) responds with an SCG configuration, the MN (302) may add a new stored SCG configuration (318) or update the stored SCG configuration (318) based on this SCG configuration. MN (302) may also include the SCG configuration (318) stored in the UE context response message (816). Alternatively, if SN (304) does not respond with the SCG configuration or includes a rejection element in the SN response message (322) during the SN request procedure (310), MN (302) may transmit the UE context response message (816) without the stored SCG configuration (318) as described above.
[0072] If the SCG configuration is not provided to the MN (302) by the SN (304) during the SN request procedure (310), the MN (302) may include an indicator in the UE context response message (816) to inform the MN (802) of the previous connection of the UE having a multi-node connection in 305. This indicator may instruct the MN (802) to determine whether it can support a multi-node connection with the SN (304). In this example, the MN (802) decides to disconnect the connection with the multi-node connection because it cannot support a multi-node connection with the SN (304).
[0073] In 820, the MN (802) transmits a resource control status and a multi-node connection message (326) to the UE (110). Similar to FIG. 5, the multi-node connection message (326) and resource control status of FIG. 8 include a multi-node disconnection indicator (352) that instructs the UE (110) to release the SCG configuration and a connection resumption IE (341) that allows the UE (110) to connect with the MN (802).
[0074] In 825, the UE (110) connects to the MN (802) without a multi-node connection. In this case, the execution of the UE context request procedure (805), the resource control status, and the transmission of the multi-node connection message (326) allow a single-node connection to be established between the UE (110) and the MN (802), and allow the multi-node connection established in 305 between the UE (110), the MN (302), and the SN (304) to be released.
[0075] FIG. 9 illustrates details of example data and control transactions between entities for efficiently handling resource control state changes and multi-node connections to connect to other MNs and other SNs. Similar to FIG. 8, UE (110) decides to connect to MN (802) instead of MN (302), which was previously used for multi-node connections in 305. However, using the technique described below, UE (110) connects to SN (702) of FIG. 9 via a multi-node connection instead of SN (304) (as shown in FIG. 8). In this example, MN (802) cannot support a multi-node connection with SN (304) but can support a multi-node connection with SN (702). Thus, MN (802) establishes a multi-node connection with SN (702) instead of releasing the multi-node connection as described above in FIG. 8.
[0076] In 305, the UE (110) connects to the MN (302) and SN (304) via a multi-node connection. Although not explicitly shown, the SN (304) may provide the SCG configuration (351) to the MN (302) via an activity notification message (406) or an SN modification procedure (410) as described in relation to FIG. 4. Similar to FIG. 8, the connection disconnection procedure (415), connection resumption initiation procedure (420), UE context request procedure (805), and optionally the SN request procedure (310) may be performed as described above for FIG. 8.
[0077] To establish a multi-node connection with the SN (702), the SN request procedure (905) is performed after the UE context request procedure (805). Generally, the SN request procedure (905) is similar to the SN request procedure (310) described above in FIG. 3. In this case, the SN request procedure (905) provides the SCG configuration (351) to the MN (802). In some situations, the SCG configuration (351) may include a delta SCG configuration based on the stored SCG configuration (318) provided by the UE context request procedure (805). In other situations, the SCG configuration (351) may include a full (pool) SCG configuration.
[0078] In 910, the MN (802) transmits a resource control status and a multi-node connection message (326) to the UE (110) along with an SCG configuration (351) and a connection resumption IE (341). Through the SCG configuration (351) and the connection resumption IE 341, the UE (110) establishes a multi-node connection for the MN (802) and SN (702) as illustrated in 915. Generally, the execution of the SN request procedure (905) and the transmission of the resource control status and the multi-node connection message (326) enable a multi-node connection to be established between the UE (110), the MN (802), and the SN (702).
[0079] Example method
[0080] FIG. 10 illustrates an exemplary method (1000) for efficient processing of resource control state changes and multi-node connections. The method (1000) is illustrated as a series of operations (or actions) performed, but the actions are not necessarily limited to the order or combination exemplified. Additionally, any one or more of the actions may be repeated, combined, reconfigured, or linked to provide a wide range of additional and / or alternative methods. In part of the following description, the environment (100) of FIG. 1 and the entities described in FIG. 2-9 are merely examples. The technology is not limited to the performance of a single entity or multiple entities operating on a single device.
[0081] In 1002, a multi-node connection for the master node and secondary nodes occurs. For example, the UE (110) can be connected to the MN (302) and SN (304) via a multi-node connection. While the multi-node connection is active, the MN (302) can receive an SCG configuration (351) from the SN (304) via an activity notification message (406) or an SN modification procedure (410) as illustrated in FIG. 4. In some cases, the UE (110), MN (302), and SN (304) can perform the connection disconnection procedure (415) of FIG. 4.
[0082] In 1004, a resource control status and multi-node connection message is received. The resource control status and multi-node connection message includes status change information and multi-node connection information. For example, a UE (110) may receive a resource control status and multi-node connection message (326). As illustrated in FIG. 3, the resource control status and multi-node connection message (326) may include at least one SCG configuration (351) or multi-node disconnection indicator (352). In some cases, the multi-node connection information (350) may also include an MCG configuration (353). In other situations, the resource control status and multi-node connection message (326) may be received from an MN that the UE was previously connected to via multi-node connection (e.g., MN (302)) or another MN selected by the UE (e.g., MN (802)).
[0083] In 1006, a transition from the first resource control state to the second resource control state occurs based on the resource control state and the state change information of the multi-node connection message. For example, the UE (110) may transition from the inactive state to the connected state based on the connection resumption IE (341) of FIG. 4, which is in the form of the state change information (340) shown in FIG. 3. As another example, the UE (110) may transition from the connected state to the inactive state based on the connection interruption IE (606) of FIG. 6, which is another form of the state change information (340) shown in FIG. 3.
[0084] In 1008, at least one operation (action) associated with a multi-node connection is performed based on multi-node connection information. For example, the UE (110) modifies a previously stored secondary cell group configuration based on at least one SCG configuration (351). Additionally or alternatively, the UE (110) is reconnected to a multi-node connection using the SCG configuration (351) (illustrated in FIG. 4), connected without a multi-node connection based on a multi-node disconnection indicator (352) (illustrated in FIG. 5 and 8), disconnected from a multi-node connection (illustrated in FIG. 6), connected to a multi-node connection for another SN (illustrated in FIG. 7), or connected to a multi-node connection for another MN and another SN (illustrated in FIG. 9).
[0085] conclusion
[0086] Although the technology for efficiently handling resource control state changes and multi-node connections is described in language specific to the function and / or method, it should be understood that the essence of the appended claims is not necessarily limited to the specific feature or method described. Rather, the specific function and method are disclosed as examples of implementations for efficiently handling resource control state changes and multi-node connections.
[0087] Several examples are explained below.
[0088] Example 1: The method performed by the base station is,
[0089] A step of operating as a master node for multi-node connection with user equipment and secondary nodes; and
[0090] The method includes the step of transmitting resource control status and multi-node connection messages to user equipment, wherein the resource control status and multi-node connection messages are,
[0091] State change information instructing the user equipment to switch from a first resource control state to a second resource control state; and
[0092] It includes multi-node connection information that instructs user equipment to perform operations associated with multi-node connections.
[0093] Example 2: In the method of Example 1, the above method is,
[0094] The method further includes the step of suspending the connection associated with the multi-node connection and instructing the user equipment to transition from a connected state to an inactive state before transmitting the first resource control state and multi-node connection message,
[0095] The first resource control state includes an inactive state;
[0096] The second resource control state includes the connection state; and
[0097] State change information includes connection resumption information that instructs the user equipment to transition from an inactive state to a connected state.
[0098] Example 3: In the method of Example 2, the above method is,
[0099] The method further includes the step of receiving at least one secondary cell group configuration from a secondary node, and the multi-node connection information includes at least one secondary cell group configuration that instructs the user equipment to reconnect to a multi-node connection for the master node and the secondary node.
[0100] Example 4: In the method of Example 3, the above method is,
[0101] The method further includes the step of sending a secondary node request message to a secondary node to instruct the secondary node to provide at least one secondary cell group configuration,
[0102] The step of receiving at least one secondary cell group configuration includes receiving a secondary node response message containing at least one secondary cell group configuration.
[0103] Example 5: In Example 3 or 4, at least one secondary cell group configuration includes at least one pool secondary cell group configuration.
[0104] Example 6: In the method of Example 4, the above method is,
[0105] It further includes a step of storing other secondary cell group configurations associated with the secondary node, and
[0106] The secondary node request message includes another secondary cell group configuration that instructs the secondary node to transmit at least one delta secondary cell group configuration as at least one secondary cell group configuration, and at least one delta secondary cell group configuration is based on the other secondary cell group configuration.
[0107] Example 7: In the method of Example 6, the above method is,
[0108] It further includes the step of receiving an activity notification message containing other secondary cell group configurations at the secondary node.
[0109] Example 8: As a method of Example 6, the above method is,
[0110] It further includes the step of performing a secondary node modification procedure together with the secondary node to instruct the secondary node to transmit a different secondary cell group configuration to the base station.
[0111] Example 9: In Example 1 or 2, the above method is,
[0112] A step of sending a secondary node request message to another secondary node instructing the other secondary node to provide at least one secondary cell group configuration; and
[0113] The method further includes the step of receiving a secondary node response message from another secondary node having at least one secondary cell group configuration, and
[0114] Multi-node connectivity information includes at least one secondary cell group configuration that instructs user equipment to connect to a master node and other secondary nodes through multi-node connectivity.
[0115] Example 10: In Example 1 or 2, the multi-node connection information includes a multi-node disconnection indicator that instructs the user equipment to connect to the master node without a multi-node connection.
[0116] Example 11: In the method of Example 1,
[0117] The first resource control state includes the connection state;
[0118] The second resource control state includes an inactive state;
[0119] State change information includes a disconnection information element that instructs the user device to transition from a connected state to an inactive state; and
[0120] Multi-node connection information includes a multi-node disconnection indicator that instructs user equipment to disconnect the connection associated with the multi-node connection.
[0121] Example 12: The base station is,
[0122] Radio frequency transceiver; and
[0123] Includes a processor and memory system configured to perform any one of the methods in Example 1-11.
[0124] Example 13: The method performed by the user equipment is,
[0125] Step of connecting to the master node and secondary nodes through a multi-node connection;
[0126] Step of receiving resource control status and multi-node connection messages - Resource control status and multi-node connection messages include status change information and multi-node connection information -;
[0127] A step of transitioning from a first resource control state to a second resource control state based on state change information; and
[0128] It includes a step of performing operations (actions) associated with multi-node connections based on multi-node connection information.
[0129] Example 14: In Example 13, the above method is,
[0130] Before receiving resource control status and multi-node connection messages, it further includes a step of transitioning from a connected state to an inactive state,
[0131] The status change information includes connection resumption information elements;
[0132] The first resource control state includes an inactive state based on connection resumption information elements; and
[0133] The second resource control state includes a connection state based on connection resumption information elements.
[0134] Example 15: In Example 13 or 14,
[0135] Multi-node connection information includes at least one secondary cell group configuration; and
[0136] The step of performing the operation includes the step of reconnecting the master node and the secondary node to a multi-node connection based on at least one secondary cell group configuration.
[0137] Example 16: In the method of Example 15,
[0138] At least one secondary cell group configuration includes a random access configuration, and
[0139] The method is,
[0140] It further includes a step of performing a random access procedure with a secondary node based on a random access configuration.
[0141] Example 17: In Example 15,
[0142] At least one secondary cell group configuration includes at least one pool secondary cell group configuration, and
[0143] The method is,
[0144] A step of storing at least one pool secondary cell group configuration; or
[0145] It further includes a step of replacing a previously saved secondary cell group configuration with one or more full secondary cell group configurations.
[0146] Example 18: In Example 15,
[0147] At least one secondary cell group configuration includes at least one delta secondary cell group configuration, and
[0148] The method is,
[0149] It further includes a step of modifying a previously saved secondary cell group configuration based on the delta secondary cell group configuration.
[0150] Example 19: In Example 13 or 14,
[0151] Multi-node connection information includes a multi-node disconnection indicator;
[0152] The step of performing the operation is,
[0153] A step of disconnecting a connection associated with a multi-node connection based on a multi-node disconnection indicator; and
[0154] It includes the step of connecting to the master node without multiple node connections.
[0155] Example 20: In Example 13 or 14, the method is,
[0156] It further includes the step of sending a connection resumption request message to the second master node;
[0157] The step of receiving resource control status and multi-node connection messages includes the step of receiving resource control status and multi-node connection messages from the second master node;
[0158] Multi-node connection information includes at least one secondary cell group configuration associated with a secondary node; and
[0159] The step of performing the operation includes connecting to the second master node and the second node via a multi-node connection based on at least one secondary cell group configuration.
[0160] Example 21: In Example 13 or 14, the method is,
[0161] It further includes the step of sending a connection resumption request message to the second master node, and
[0162] The step of receiving resource control status and multi-node connection messages includes the step of receiving resource control status and multi-node connection messages from the second master node;
[0163] Multi-node connection information includes at least one secondary cell group configuration associated with another secondary node; and
[0164] The step of performing the operation includes connecting to a second master node and other second nodes via a multi-node connection based on at least one secondary cell group configuration.
[0165] Example 22: In Example 13,
[0166] The status change information includes connection interruption information elements;
[0167] The first resource control state includes a connection state based on a connection interruption information element;
[0168] The second resource control state includes an inactive state based on connection interruption information elements;
[0169] Multi-node connection information includes a multi-node disconnection indicator; and
[0170] The step of performing the operation includes the step of releasing the connection associated with the multi-node connection based on the multi-node connection release indicator.
[0171] Example 23: User equipment is,
[0172] Radio frequency transceiver; and
[0173] Includes a processor and memory system configured to perform any one of the methods in Examples 12-22.
[0174] Example 24: The system includes the base station of Example 12 and the user equipment of Example 23.
Claims
Claim 1 A method performed by a base station, comprising: operating as a master node for a multi-node connection with a user device and a secondary node; suspending the connection associated with the multi-node connection and instructing the user device to switch from a resource control connection state to a resource control inactive state before transmitting a first resource control state and a multi-node connection message; receiving the at least one secondary cell group configuration from the secondary node in order to instruct the user device to modify a previously stored secondary cell group configuration based on at least one secondary cell group configuration and to instruct the user device to reconnect to the multi-node connection associated with the master node and the secondary node, wherein the at least one secondary cell group configuration includes a random access configuration. A method performed by a base station, comprising the step of transmitting the first resource control state and multi-node connection message to the user equipment, wherein the first resource control state and multi-node connection message comprises state change information for instructing the user equipment to switch from the resource control inactive state to the resource control connected state—the state change information includes a connection resumption information element for instructing the user equipment to switch from the resource control inactive state to the resource control connected state—; and multi-node connection information including the at least one secondary cell group configuration for instructing the user equipment to modify a previously stored secondary cell group configuration based on at least one secondary cell group configuration and to perform a random access procedure to the secondary node based on the random access configuration. Claim 2 delete Claim 3 delete Claim 4 A method performed by a base station, wherein the at least one secondary cell group configuration comprises the at least one full secondary cell group configuration for instructing the user equipment to replace the previously stored secondary cell group configuration with at least one full secondary cell group configuration. Claim 5 A method performed by a base station, wherein the at least one secondary cell group configuration comprises the at least one delta secondary cell group configuration for instructing the user equipment to modify a portion of the previously stored secondary cell group configuration based on at least one delta secondary cell group configuration. Claim 6 The method of claim 1 further comprises the step of transmitting a secondary node request message to another secondary node to instruct the other secondary node to provide the at least one secondary cell group configuration; and the step of receiving a secondary node response message from the other secondary node having the at least one secondary cell group configuration, wherein the at least one secondary cell group configuration is performed by a base station, instructing the user equipment to connect to the master node and the other secondary node via a multi-node connection. Claim 7 A method performed by a base station, wherein the method further comprises the step of transmitting a second resource control state and a multi-node connection message to the user equipment, wherein the second resource control state and the multi-node connection message comprises other state change information for instructing the user equipment to switch from the resource control connection state to the resource control inactive state—the other state change information includes connection disconnection information—; and other multi-node connection information including a multi-node disconnection indicator for instructing the user equipment to disconnect the connection associated with the multi-node connection and to connect to the master node without the multi-node connection. Claim 8 A method performed by user equipment, comprising: connecting to a master node and a secondary node via a multi-node connection; switching from a resource control connection state to a resource control inactive state before receiving a first resource control state and a multi-node connection message; receiving the first resource control state and the multi-node connection message including at least one secondary cell group configuration including a random access configuration and a connection resumption information element; switching from the resource control inactive state to the resource control connection state; modifying a previously stored secondary cell group configuration based on the at least one secondary cell group configuration; and performing a random access procedure with the secondary node based on the random access configuration. Claim 9 delete Claim 10 A method performed by user equipment according to claim 8, wherein the method further comprises the step of reconnecting to the multi-node connection for the master node and the secondary node based on the configuration of at least one secondary cell group. Claim 11 delete Claim 12 A method performed by user equipment, wherein, in claim 8, the at least one secondary cell group configuration includes at least one full secondary cell group configuration, and the step of modifying the previously stored secondary cell group configuration includes the step of replacing the previously stored secondary cell group configuration with the at least one full secondary cell group configuration. Claim 13 A method performed by user equipment, wherein, in claim 8, the at least one secondary cell group configuration includes at least one delta secondary cell group configuration, and the step of modifying the previously stored secondary cell group configuration includes the step of modifying a part of the previously stored secondary cell group configuration based on the delta secondary cell group configuration. Claim 14 In claim 8, the method further comprises the step of receiving a second resource control state and a multi-node connection message—wherein the second resource control state and multi-node connection message includes other state change information and other multi-node connection information, wherein the other state change information includes connection interruption information and the other multi-node connection information includes a multi-node disconnection indicator—; the step of switching from the resource control connection state to the resource control inactive state based on the connection interruption information; the step of disconnecting the connection associated with the multi-node connection based on the multi-node disconnection indicator; and the step of connecting to the master node without a multi-node connection, the method being performed by a user device. Claim 15 In claim 8, the method further comprises the step of transmitting a connection resumption request message to a second master node, the step of receiving the first resource control status and multi-node connection message comprises the step of receiving the first resource control status and multi-node connection message from the second master node, and the method is performed by user equipment in which the configuration of at least one secondary cell group is associated with the secondary node or another secondary node. Claim 16 A method performed by user equipment according to claim 15, wherein the method further comprises the step of connecting the secondary node and one of the other secondary nodes to the second master node via a multi-node connection based on the configuration of at least one secondary cell group. Claim 17 A method performed by a base station, wherein, in paragraph 1, the master node is a gNB base station and the secondary node is another gNB base station. Claim 18 A method performed by a base station, wherein, in claim 1, the master node is a gNB base station and the secondary node is an ng-eNB base station. Claim 19 A method performed by user equipment in claim 8, wherein the master node is a gNB base station and the secondary node is another gNB base station. Claim 20 A method performed by user equipment in claim 8, wherein the master node is a gNB base station and the secondary node is an ng-eNB base station.