Method for conditional mobility

Abstract

This document relates generally to wireless communications, and more particularly to improvements in handling of conditional mobility of wireless terminals. For example, when conditional handover (CHO) and / or conditional PSCell add / change (CPAC) procedures are configured, various implementations disclosed herein facilitate providing inter-node interaction procedures between a primary access network node (MN) and a secondary access network node. Example mechanisms are provided for the SN to notify the MN of execution of a secondary cell group (SCG) reconfiguration / update, and to provide the MN with an updated SCG configuration.

Description

Technical Field

[0001] This document relates generally to wireless communications and, more particularly, to improved handling of mobility of wireless terminals. Background Art

[0002] Wireless communication technology is driving the world towards an increasingly interconnected and networked society. Wireless communication relies on efficient network resource management and allocation between user mobile stations and wireless access network nodes (including but not limited to wireless base stations). The next generation of networks is expected to provide high-speed, low-latency and ultra-reliable communication capabilities and meet the requirements of different industries and users. User mobile stations or user equipment (UE) are becoming more and more complex, and the amount of data communicated is increasing. In order to improve communication and meet the reliability requirements of vertical industries and support the next generation of network services, communication improvements should be made. Summary of the invention

[0003] This document relates generally to wireless communications, and more specifically to improvements in the handling of conditional mobility of wireless terminals. For example, when a Conditional Handover (CHO) and / or Conditional PSCell Addition / Change (CPAC) process is configured, various implementations disclosed herein facilitate providing an inter-node interaction process between a Master Access Network Node (MN) and a Secondary Access Network Node. An example mechanism is provided for an SN to notify an MN of the execution of a Secondary Cell Group (SCG) reconfiguration / update, and to provide an updated SCG configuration to the MN.

[0004] In some implementations, a method for wireless communication is disclosed. The method may include sending a request message including an indication of performance of a secondary cell group (SCG) reconfiguration; and receiving a response message associated with the request message.

[0005] In the above implementation, sending the request message may include: sending the request message from a secondary wireless communication node (SN) to a primary wireless communication node (MN), and wherein a response message is received by the SN from the MN.

[0006] In any of the above implementations, the request message includes an SN modification request message, and wherein the response message includes an SN modification response message.

[0007] In any of the above implementations, the request message includes the new SCG configuration, and wherein the new SCG configuration is contained in a container from SN to MN.

[0008] In any of the above implementations, the method may also include causing the MN to regard the new SCG configuration as already applied in the user equipment (UE) and not forwarding the new SCG configuration to the UE.

[0009] In any of the above implementations, the execution of SCG reconfiguration may include at least one of the following items: the execution of an intra-SN conditional PSCell change (CPC) procedure initiated by the SN; or the execution of RRC reconfiguration using signaling radio bearer (SRB) 3.

[0010] In any of the above implementations, the SN initiated execution of intra-SN CPC causes the MN to believe that, if the conditional reconfiguration was configured in the UE, the conditional reconfiguration has been released due to the SN initiated execution of intra-SN CPC.

[0011] In any of the above implementations, the conditional reconfiguration may include at least one of the following items: conditional handover (CHO); conditional PSCell addition (CPA); MN-initiated conditional PSCell change (CPC); or SN-initiated inter-SN CPC or SN-initiated intra-SN CPC.

[0012]

[0011] In some other implementations, another method for wireless communication is disclosed that can include receiving a request message including an indication of performance of a secondary cell group (SCG) reconfiguration; and sending a response message associated with the request message.

[0013] In the above implementation, receiving the request message includes: receiving the request message from the secondary wireless communication node (SN) by the primary wireless communication node (MN), and wherein the response message is sent by the MN to the SN.

[0014] In any of the above implementations, the request message includes an SN modification request message, and wherein the response message includes an SN modification response message.

[0015] In any of the above implementations, the request message includes the new SCG configuration, and wherein the new SCG configuration is contained in a container from SN to MN.

[0016] In any of the above implementations, the method may further include: considering the new SCG configuration as having been applied in the user equipment (UE) and not forwarding the new SCG configuration to the UE.

[0017] In any of the above implementations, the execution of SCG may include at least one of the following items: execution of an intra-SN conditional PSCell change (CPC) procedure initiated by the SN; or execution of RRC reconfiguration using signaling radio bearer (SRB) 3.

[0018] In any of the above implementations, the SN initiated execution of intra-SN CPC causes the MN to believe that, if the conditional reconfiguration was configured in the UE, the conditional reconfiguration has been released due to the SN initiated execution of intra-SN CPC.

[0019] In any of the above implementations, the conditional reconfiguration may include at least one of the following items: conditional handover (CHO); conditional PSCell addition (CPA); MN-initiated conditional PSCell change (CPC); or SN-initiated inter-SN CPC or SN-initiated intra-SN CPC.

[0020] In some other implementations, a wireless communication device is disclosed. The wireless communication device may include a processor and a memory, wherein the processor is configured to: read a code from the memory and implement any one of the above methods.

[0021] In some other implementations, a non-transitory computer-readable medium is disclosed. The non-transitory computer-readable medium may include computer instructions, which, when executed by a processor of a wireless communication device, may cause the wireless communication device to implement any of the above methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 An example base station is shown.

[0023] Figure 2 An example random access (RA) messaging environment is shown.

[0024] Figure 3 A Conditional PSCell Addition / Change (CPAC) procedure initiated by a Master Node (MN) according to an embodiment of the present disclosure is shown.

[0025] Figure 4 One embodiment of communication of a master node (MN) and a secondary node (SN) is shown.

[0026] Figure 5 Another embodiment of the communication of a master node (MN) and a secondary node (SN) is shown. DETAILED DESCRIPTION

[0027] The present disclosure will now be described in detail below with reference to the accompanying drawings, which form a part of the present disclosure and show specific examples of embodiments by way of illustration. However, it is noted that the present disclosure may be embodied in a variety of different forms and, therefore, the subject matter covered or claimed is intended to be construed as not being limited to any of the embodiments set forth below.

[0028] Throughout the specification and claims, terms may have nuanced meanings that are implied or suggested in the context rather than explicitly defined. Similarly, the phrases "in one embodiment" or "in some embodiments" used herein do not necessarily refer to the same embodiment, and the phrases "in another embodiment" or "in other embodiments" used herein do not necessarily refer to different embodiments. The phrases "in one implementation" or "in some implementations" used herein do not necessarily refer to the same implementation, and the terms "in another implementation" or "in other implementations" used herein do not necessarily refer to different implementations. For example, the claimed subject matter includes combinations of exemplary embodiments or implementations (in whole or in part).

[0029] In general, terms can be understood at least in part from usage in context. For example, terms used herein (such as "and", "or", "and / or") can include multiple meanings, which can depend at least in part on the context in which such terms are used. Typically, "or" if used in an associative list, such as A, B, or C, means A, B, and C, which are used here in an inclusive sense, and A, B, or C, which are used here only in an exclusive sense. In addition, the terms "one or more" or "at least one" used herein (depending at least in part on the context) can be used to describe any feature, structure, or characteristic in a singular sense, or can be used to describe a combination of features, structures, and characteristics in a plural sense. Similarly, terms such as "a", "an", or "the" can also be understood to convey singular or plural usage, which depends at least in part on the context. In addition, the term "based on" or "determined by..." can be understood to not necessarily be intended to convey a set of exclusive factors, but rather, other factors that are not necessarily explicitly described can be allowed to exist, which again depends at least in part on the context.

[0030] Radio Resource Control ("RRC") is a protocol layer between the UE and the base station at the IP layer (network layer). There may be various Radio Resource Control (RRC) states, such as RRC connected (RRC_CONNECTED), RRC inactive (RRC_INACTIVE), and RRC idle (RRC_IDLE) states. RRC messages are transmitted via the Packet Data Convergence Protocol ("PDCP"). As described above, the UE may send data via a Random Access Channel ("RACH") protocol scheme or a Configured Grant ("CG") scheme. CG may be used to reduce the waste of periodically allocated resources by enabling multiple devices to share periodic resources. A base station or node may allocate CG resources to eliminate packet transmission delays and improve the utilization of allocated periodic radio resources. The CG scheme is merely one example of a protocol scheme for communication, and other examples (including but not limited to RACH) are also possible. The wireless communication described herein may be conducted via wireless access.

[0031] There may be a master node (Master Node, "MN") and one or more secondary nodes (Secondary Node, "SN"). The MN may include a master cell group (Master Cell Group, "MCG"), and each SN may include a secondary cell group (Secondary Cell Group, "SCG"). The MCG is a group of cells provided by the master node ("MN"), and the SCG is a group of cells provided by the secondary node (Secondary Cell, "SN"). The MCG may include a primary cell (Primary Cell, "PCell") and one or more secondary cells (Secondary Cell, "SCell"). The SCG may include a primary secondary cell (Primary Secondary Cell, "PSCell") and one or more secondary cells ("SCell"). Each primary cell may be connected to multiple secondary cells. The primary cell (PCell, PSCell) is the primary cell of its corresponding group (MCG, SCG, respectively), and initial access may be initiated. The primary cell may be used for signaling notifications, and may be referred to as a special cell (Special Cell, "spCell"), where spCell = PCell + PSCell. The mobility between cells described in these embodiments may be based on PCell, PSCell and / or SCell. However, as described in the present disclosure, they may be referred to as source cells and target cells. When a user equipment ("UE") moves from a source cell to a target cell, the UE device may move between nodes or cells, in which case a handover or change / add operation may occur to improve the network reliability of the UE.

[0032] As follows about Figure 1-Figure 2 As described, a network provider may include multiple network nodes (ie, base stations) for providing network access to user equipment ("UE") devices. In some embodiments, a network node is referred to as a base station. Figure 3-Figure 4 An example of MN / SN communication for achieving UE mobility is illustrated.

[0033] Figure 1 An example base station 102 is shown. A base station may also be referred to as a radio network node and may be Figure 3-Figure 5The network nodes shown (e.g., master node ("MN"), secondary node ("SN"), and source / target node). The base station 102 can be further identified as a nodeB (NB, such as an eNB or gNB) in the context of mobile communications. The example base station may include: a wireless Tx / Rx circuit system 113 for receiving and transmitting with a user equipment (UE) 104. The base station may also include: a network interface circuit system 116 for coupling the base station to the core network 110, for example, an optical or wired interconnect, Ethernet, and / or other data transmission media / protocols.

[0034] The base station may also include system circuitry 122. System circuitry 122 may include processor(s) 124 and / or memory 126. Memory 126 may include operations 128 and control parameters 130 (collectively, instructions and data). Operations 128 may include instructions for execution on one or more processors 124 to support the functionality of the base station. For example, these operations may process random access transmission requests from multiple UEs. Control parameters 130 may include parameters or support the execution of operations 128. For example, control parameters may include: network protocol settings, random access message delivery format rules, bandwidth parameters, radio frequency mapping allocations, and / or other parameters.

[0035] Figure 2 An example random access messaging environment 200 is shown. In the random access messaging environment, the UE 104 can communicate with the base station 102 via a random access channel 252. In this example, the UE 104 supports one or more Subscriber Identity Modules (SIMs), such as SIM 1 202. An electrical and physical interface 206 connects SIM 1 202 to the rest of the user equipment hardware, such as via a system bus 210.

[0036] The mobile device 200 includes a communication interface 212, a system logic 214, and a user interface 218. The system logic 214 may include any combination of hardware, software, firmware, or other logic. The system logic 214 may be implemented, for example, with one or more systems on a chip (SoC), application specific integrated circuits (ASICs), discrete analog and digital circuits, and other circuit systems. The system logic 214 is part of the implementation of any desired function in the UE 104. In this regard, the system logic 214 may include logic that facilitates, for example, decoding and playing music and videos, for example, MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback; running applications; accepting user input; saving and retrieving application data; establishing, maintaining, and terminating cellular phone calls or data connections, such as Internet connections; establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying relevant information on the user interface 218. The user interface 218 and input 228 may include a graphical user interface, a touch-sensitive display, tactile feedback or other tactile output, voice or facial recognition input, buttons, switches, speakers, and other user interface elements. Additional examples of input 228 may include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headphone and microphone input / output jacks, Universal Serial Bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors), and other types of inputs.

[0037] The system logic 214 may include one or more processors 216 and memory 220. The memory 220 stores control instructions 222, for example, to be executed by the processor 216 to perform the desired functions of the UE 104. The control parameters 224 provide and specify configuration and operating options for the control instructions 222. The memory 220 may also store any BT, WiFi, 3G, 4G, 5G or other data 226 that the UE 104 will send or has received through the communication interface 212. In various implementations, system power may be provided by a power storage device such as a battery 282.

[0038] In the communication interface 212, the radio frequency (RF) transmit (Transmit, Tx) and receive (Receive, Rx) circuit system 230 handles the transmission and reception of signals through one or more antennas 232. The communication interface 212 may include one or more transceivers. The transceiver may be a wireless transceiver that includes modulation / demodulation circuit system, digital to analog converter (Digital to Analog Converter, DAC), shaping table, analog to digital converter (Analog to Digital Converter, ADC), filter, waveform shaper, filter, preamplifier, power amplifier, and / or other logic for transmitting and receiving through one or more antennas or (for some devices) through a physical (e.g., wired) medium.

[0039] The transmitted and received signals may follow any of a variety of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and encodings. As a specific example, the communication interface 212 may include a transceiver that supports transmission and reception under 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High Speed ​​Packet Access (HSPA)+, and 4G / Long Term Evolution (LTE) standards. However, the techniques described below are applicable to other wireless communication technologies, whether generated by the 3rd Generation Partnership Project (3GPP), the GSM Association, 3GPP2, IEEE, or other partners or standards bodies.

[0040] Multiple RAN nodes with the same or different Radio Access Technology (Radio Access Technology, "RAT") (e.g., eNB, gNB) may be deployed in the same or different frequency carriers in certain geographic areas, and may cooperate with each other via dual-connectivity operations to provide joint communication services for (multiple) the same target UEs. The Multi-RAT Dual Connectivity ("MR-DC") architecture may have non-co-located master nodes ("MNs") and secondary nodes ("SNs"). The Access Mobility Function ("AMF") and the Session Management Function ("SMF") may be control plane entities, while the User Plane Function ("UPF") may represent a user plane entity in a New Radio ("NR") or 5GC. The signaling connection between the AMF / SMF and the master node ("MN") may be a next generation control plane ("NG-C") / MN interface. The signaling connection between the MN and the SN may be an Xn control plane ("Xn-C") interface. The signaling connection between the MN and the UE may be a Uu control plane ("Uu-C") RRC interface. All of these connections manage the configuration and operation of the MR-DC. The user plane connection between the user plane function ("UPF") and the MN may be an NG-U(MN) interface instance.

[0041] In order to reduce the interruption time and improve the mobility reliability (i.e., mobility robustness) in SN change or SN addition, Conditional PSCell Addition / Change (CPAC) is proposed. CPAC is defined as the PSCell addition / change performed by the UE when (multiple) execution conditions are met. The UE starts to evaluate the (multiple) execution conditions after receiving the CPAC configuration, and stops evaluating the (multiple) execution conditions after the PSCell addition / change is triggered. The CPAC configuration includes: candidate PSCell configurations (including SCG configurations generated by candidate SNs, and possible MCG configurations generated by MNs), and (multiple) corresponding execution conditions of the candidate PSCells.

[0042] The CPAC process can be triggered by the MN or the SN, so it can be divided into CPAC initiated by the MN or CPAC initiated by the SN. In addition, the CPAC process can be with or without the participation of the MN, so it can also be divided into CPAC with the participation of the MN or CPAC without the participation of the MN (i.e., CPC within the SN without the participation of the MN (conditional PSCell change)).

[0043] Figure 3 The CPAC process initiated by the MN according to an embodiment of the present disclosure is illustrated. In this case, the execution condition(s) are determined by the MN. The source SN is denoted as s-SN, and the target SN or candidate SN is denoted as T-SN_1.

[0044] S302. The MN sends an SN adding request message to the target SN. In the SN adding request message, the MN may include the measurement result and CPAC indication related to the target SN, where the CPAC indication is used to indicate that this is a condition-based process.

[0045] S304. The target SN responds to the MN with an SN add request confirmation, including the configuration of (multiple) candidate PSCells.

[0046] S306. MN determines (multiple) execution conditions of the candidate PSCell.

[0047] S308. The MN sends an RRC reconfiguration message including the CPAC configuration to the UE. The CPAC configuration includes at least: a candidate PSCell configuration (ie, an RRC reconfiguration message generated by the target SN), and (multiple) corresponding execution conditions.

[0048] S310. The UE replies an RRC reconfiguration complete message to the MN to confirm receipt of the RRC reconfiguration message.

[0049] S312. The UE maintains connection with the source SN and starts evaluating (multiple) execution conditions. When at least one execution condition of the candidate PSCell is met, the UE selects the relevant cell as the target PSCell and triggers the execution of CPAC to access the target SN.

[0050] S314. When CPAC is executed, the UE sends an RRC reconfiguration completion message to the MN. The RRC reconfiguration completion message for the MN includes: embedded RRC reconfiguration completion for the target SN.

[0051] S316. The MN transmits an SN reconfiguration complete message (ie, embedded RRC reconfiguration complete) to the target SN.

[0052] S318. UE performs a random access (RA) procedure on the target PSCell of the SN. Note that there is no restriction on the order in which the UE sends the RRC reconfiguration complete message and performs a random access procedure on the SCG (ie, the order of S314, S316 and S318 is not defined and / or can be changed).

[0053] For a CPC procedure initiated by an SN with the participation of an MN (e.g., an inter-SN CPC initiated by an SN), the execution condition(s) are determined by the SN. The procedure is similar to a CPAC procedure initiated by an MN, except that the source SN first sends an SN change request message to the MN to request the initiation of a conditional SN change procedure. In addition, in this embodiment, the SN change request message may include the execution condition(s) generated by the source SN.

[0054] In CPC initiated by SN without MN participation (e.g., intra-SN CPC initiated by SN), if SRB3 is configured, the SN can send RRC reconfiguration including CPC configuration to the UE directly via SRB3. SRB3 is a signaling radio bearer between the UE and the SN. In another embodiment, the SN sends the RRC reconfiguration to the MN, and the MN transmits the message transparently to the UE.

[0055] In order to reduce the switching interruption time and improve the mobility reliability (i.e., mobility robustness), conditional handover (CHO) is generalized. CHO is defined as a handover performed by the UE when (multiple) execution conditions are met. The UE starts to evaluate the (multiple) execution conditions after receiving the CHO configuration, and stops evaluating the (multiple) execution conditions after the handover is triggered. The CHO configuration includes: a candidate primary cell (PCell) configuration generated by a candidate node, and (multiple) corresponding execution conditions of the candidate cell. In another embodiment, CHO is applicable to the MR-DC situation (i.e., CHO with MR-DC situation). The CHO configuration includes: a CHO candidate cell configuration generated by a candidate MN and a candidate SN, and (multiple) corresponding execution conditions of the candidate cell. The CHO candidate cell configuration includes: an MCG configuration generated by a candidate MN, and an SCG configuration generated by a candidate SN.

[0056] CHO and CPAC may refer to conditional reconfiguration, that is, conditional reconfiguration includes: CHO, CPA, CPC initiated by MN, inter-SN CPC initiated by SN, intra-SN CPC initiated by SN, etc.

[0057] The following aspects describe details of the present disclosure, but the present disclosure is not limited thereto.

[0058] In CHO with MR-DC case or CPC case, the candidate cell configuration may include an incremental configuration based on the source SCG configuration. When an SN-initiated SN modification procedure is performed without MN participation (e.g., a prepared SN-initiated intra-SN CPC procedure, or RRC reconfiguration using SRB3 has been performed), the MN will lose the latest SCG configuration. The MN should be aware of the updated / new SCG configuration. Then, if necessary, the MN can trigger CHO / CPAC cancellation to release the CHO / CPAC configuration, or trigger CHO / CPAC modification to update the candidate cell configuration based on the new SCG configuration.

[0059] In the case of coexistence of CHO and CPAC (including CPA, MN-initiated inter-SN CPC, SN-initiated inter-SN CPC, SN-initiated intra-SN CPC), CHO (including CHO with MR-DC) and CPAC can be configured for the UE at the same time. When one conditional reconfiguration is performed, the UE releases the other conditional reconfiguration. However, when intra-SN CPC is performed, the MN is not currently notified, so the MN cannot perform CHO and / or CPC release / update operations.

[0060] Aspect 1: Inter-node coordination / interaction process for notifying the SN of the CHO with MR-DC and / or CPC process

[0061] When the CHO process with MR-DC and / or CPC is configured / initiated, the MN notifies the SN. The MN sends an indication of CHO with MR-DC and / or CPC (e.g., CHO MR-DC indicator, CPC data forwarding indicator) to the SN via an Xn / X2 message (e.g., an Xn-U address indication message, a data forwarding address indication message, or other messages). The indication is used to notify that the CHO process with MR-DC and / or CPC is configured / initiated (e.g., "CHO ​​MR-DC indicator" is set to "true", "CPC data forwarding indicator" is set to "triggered"). In one embodiment, the SN may consider that the CHO process with MR-DC and / or CPC is configured / initiated. In another embodiment, when the SN modifies the SN configuration (e.g., a prepared SN-initiated SN intra-CPC process, or an RRC reconfiguration using SRB3 has been performed), the SN may notify the MN and may also send an updated / new SCG configuration to the MN. In another embodiment, the SN may not perform / initiate an SN initiated SN modification procedure (eg, RRC reconfiguration using SRB3) without the participation of the MN.

[0062] When the CHO process with MR-DC and / or CPC is canceled / released by the MN or the candidate SN, the MN notifies the SN. The MN sends a CHO indication (e.g., CHO MR-DC early data forwarding indicator, CPC data forwarding indicator) with MR-DC and / or CP to the SN via an Xn / X2 message (e.g., an Xn-U address indication message, a data forwarding address indication message, or other messages). The indication is used to notify that the CHO with MR-DC and / or CPC is canceled (e.g., "CHO ​​MR-DC early data forwarding indicator" is set to "stop", "CPC data forwarding indicator" is set to "triggered"). In one embodiment, the SN may consider the CHO process with MR-DC and / or CPC to be canceled / released or not configured. In another embodiment, when SCG reconfiguration is needed, the SN may perform / initiate an SN-initiated SN modification process (e.g., RRC reconfiguration using SRB3) without MN participation.

[0063] The above indication transmitted between the MN and the SN can be configured by one of the following options:

[0064] Option 1: Include the indication on the information element directly in the Xn / X2 message.

[0065] Option 2: Include the indication in an RRC message (eg, CG-Config / CG-ConfigInfo message). The RRC message is included as an information element in an Xn / X2 message.

[0066] Examples of indicators for CHO with MR-DC and / or CPC are shown in the following table:

[0067]

[0068] Table 1: Example of signaling structure of indicators for CHO with MR-DC and / or CPC

[0069] Aspect 2: Inter-node coordination / interaction procedures for notifying the MN of a prepared SN-initiated intra-SN CPC procedure and / or RRC reconfiguration using SRB3 that has been performed, and / or a new / updated SCG configuration:

[0070] The SN notifies the MN that the prepared SN-initiated intra-SN CPC procedure and / or RRC reconfiguration using SRB3 has been performed. The MN sends one or more indications via an Xn / X2 message (e.g., an S-NODE / SGNB modification required message). The indication may be at least one of the following:

[0071] Option 1: An indication used to indicate that the prepared SN initiated intra-SN CPC procedure and / or RRC reconfiguration using SRB3 has been performed (e.g., "SCG Reconfiguration Notification", the value can be set to: "SN initiated intra-SN CPC" and / or "RRC reconfiguration using SRB3").

[0072] Option 2: An indication for indicating that the SCG reconfiguration notification is for an SN-initiated intra-SN CPC procedure, or a conditional SCG reconfiguration (eg, "SN-initiated intra-SN CPC", the value can be set to "true" or "executed").

[0073] Option 3: An indication indicating that the prepared SN-initiated intra-SN CPC procedure has been executed (eg, "Conditional SCG Reconfiguration Notification", the value of which may be set to "Executed").

[0074] Option 4: An indication indicating that RRC reconfiguration using SRB3 has been performed (eg, "SCG Reconfiguration Notification", the value may be set to "Performed").

[0075] The SN may also send an updated / new SCG configuration to the MN, for example, by including a container IE for the S-NG-RAN node to the M-NG-RAN node in an S-NODE MODIFICATION REQUIRED message or other message, or by including a container IE for the SgNB to the MeNB in ​​an SGNB MODIFICATION REQUIRED message or other information. In one embodiment, the MN may consider that a prepared SN initiated intra-SN CPC procedure and / or RRC reconfiguration using SRB3 has been performed. In another embodiment, if the indication is an indication that a prepared SN initiated intra-SN CPC procedure has been performed, the MN may consider that if a conditional reconfiguration (e.g., CHO, CPC) is configured in the UE, the conditional reconfiguration has been released due to the execution of the conditional SCG configuration or the execution of the intra-SN CPC. In another embodiment, if the SgNB to MeNB container IE is included in the SGNB MODIFICATION REQUIRED message, or if the S-NG-RAN node to M-NG-RAN node container IE is included in the S-NODE MODIFICATION REQUIRED message, then, if supported, the MN may consider that the new SCG configuration has been applied in the UE and should not be forwarded to the UE. In another embodiment, the MN may initiate / trigger a CHO / CPAC cancellation / release procedure to (multiple) target / candidate nodes to cancel / release the CHO / CPAC configuration, and / or may initiate / trigger a CHO / CPAC modification procedure to (multiple) target / candidate nodes to update the candidate cell configuration based on the new SCG configuration. The MN may send the updated / new CHO / CPAC configuration (including the candidate cell configuration and / or execution conditions) to the UE via one or more RRC reconfiguration messages.

[0076] The above indication transmitted between the MN and the SN can be configured by one of the following options:

[0077] Option 1: Include the indication on the information element directly in the Xn / X2 message.

[0078] Option 2: Include the indication in an RRC message (eg, CG-Config / CG-ConfigInfo message). The RRC message is included as an information element in an Xn / X2 message.

[0079] Examples of indicators regarding SCG reconfiguration execution are shown in the following table:

[0080]

[0081] Table 2: Example of signaling structure of indicator for SCG reconfiguration execution

[0082] In the following paragraphs, details are provided on some examples, but the disclosure is not limited to these examples.

[0083] Figure 4 An embodiment of the communication of the master node (MN) and the secondary node (SN) is shown. In this embodiment, in the case of NR-DC, the CHO process with MR-DC is prepared / initiated. This process is also applicable to other MR-DC cases, such as EN-DC. Figure 4 The following example steps are shown.

[0084] Step 402. The source MN starts the handover process by initiating an Xn handover preparation process including both MCG and SCG configuration. The source MN includes a CHO indicator in the handover request message to request CHO initiation / preparation.

[0085] Step 404. If the target MN decides to keep the UE context in the source SN, the target MN sends a SN add request including the SNUE XnAP ID as a reference to the UE context in the SN established by the source MN. If the target MN decides to change the SN that allows incremental configuration, the target MN sends a SN add request to the target SN, the SN add request including: the UE context in the source SN established by the source MN. Otherwise, the target MN may send a SN add request to the target SN, the request including neither the SNUE XnAP ID nor the UE context in the source SN established by the source MN.

[0086] Step 406. The (target) SN replies with an SN Add Request Ack. The (target) SN may include an indication of a complete or incremental RRC configuration. In some embodiments, for CHO with SCG configuration (i.e., CHO with MR-DC), it is implemented by the target MN to ensure that the CG-Config provided from the (target) SN can be used for all CHO preparations.

[0087] Step 408: For the SN terminated bearer using MCG resources, the target MN provides Xn-U DL TNL address information in the Xn-U Address Indication message.

[0088] Step 410. The target MN includes in the Handover Request Confirmation message the MN RRC Reconfiguration message to be sent to the UE to perform the handover, and may also provide a forwarding address to the source MN.

[0089] Step 412. The source MN notifies the source SN that the CHO with MR-DC has been configured via the Xn-U Address Indication procedure, for example, by including a CHO MR-DC indicator (the value of which is set to "true") in the Xn-U Address Indication message. If applicable, the source SN starts early data forwarding for the SN terminated bearer and sends an early state transfer message to the source MN.

[0090] Step 414. The MN sends an RRC reconfiguration message to the UE, where the RRC reconfiguration message includes the CHO configuration of the candidate cells, that is, the candidate cell configuration and a list of corresponding execution conditions. The candidate cell configuration may include both the MCG configuration and the SCG configuration.

[0091] Step 416. The UE applies the RRC reconfiguration message received in step 414, stores the candidate cell configuration, and replies to the MN with an RRC reconfiguration complete message. In some embodiments, the UE may store candidate cell configurations for different types of conditional reconfigurations (e.g., CHO, CPA, MN-initiated inter-SN CPC, SN-initiated inter-SN CPC, SN-initiated intra-SN CPC, etc.). Steps 402-416 are examples of the preparation process for CHO with MR-DC.

[0092] Step 418. The UE starts evaluating the execution conditions. If the execution conditions of a candidate cell are met, the UE applies the selected candidate cell configuration and synchronizes to the cell.

[0093] Step 420. The prepared SN initiated intra-SN CPC procedure (eg, receiving an RRC reconfiguration complete message for intra-SN CPC execution from the UE) and / or RRC reconfiguration using SRB3 has been performed in the source SN.

[0094] Step 422. The source SN notifies the MN of the execution of the SCG reconfiguration execution (e.g., the execution of the SN initiated intra-SN CPC and / or RRC reconfiguration using SRB3) via an SN MODIFICATION REQUIRED message. The message includes: one or more indications (e.g., "SCG RECONFIGURATION NOTIFICATION") for indicating the execution of the SCG reconfiguration. The message may also include an updated / new SCG configuration for the MN (e.g., including a container IE of the S-NG-RAN node to the M-NG-RAN node in the SN MODIFICATION REQUIRED message).

[0095] Step 424. The MN sends an SN modification confirmation message to the source SN. If an indication (e.g., "SCG reconfiguration notification") is received from the source SN, the MN may consider that the prepared SN initiated intra-SN CPC procedure and / or RRC reconfiguration using SRB3 has been performed. In some embodiments, if the indication is that the prepared SN initiated intra-SN CPC procedure has been performed, the MN may consider that if the conditional reconfiguration (e.g., CHO, CPC) is configured in the UE, the conditional reconfiguration has been released due to the execution of the conditional SCG configuration or the execution of intra-SN CPC. In some embodiments, if the container IE from the S-NG-RAN node to the M-NG-RAN node is included in the SN modification request message, the MN may consider, if supported, that the new SCG configuration has been applied in the UE and should not be forwarded to the UE.

[0096] In some embodiments, the MN may initiate / trigger a CHO / CPAC cancellation / release procedure to (multiple) target / candidate nodes to cancel / release the CHO / CPAC configuration, and / or may initiate / trigger a CHO / CPAC modification procedure to (multiple) target / candidate nodes to update the candidate cell configuration based on the new SCG configuration. The MN may send an updated / new CHO / CPAC configuration (including the candidate cell configuration and / or execution conditions) to the UE via an RRC reconfiguration message.

[0097] In some embodiments, if any conditional reconfiguration (e.g., CHO, CPA, MN-initiated inter-SN CPC, SN-initiated inter-SN CPC, SN-initiated intra-SN CPC, etc.) is prepared and if the SN-initiated intra-SN CPC procedure is performed, the SN may include an indicator (e.g., SCG reconfiguration notification) in the SN / SgNB modification required message or other messages. The MN considers that, if the conditional reconfiguration is configured in the UE, the conditional reconfiguration has been released due to the execution of the conditional SCG configuration.

[0098] Figure 5Another embodiment of the communication of a master node (MN) and a secondary node (SN) is shown. In this embodiment, in the case of NR-DC, the CPC procedure is prepared / initiated. The procedure is also applicable to other MR-DC cases, such as EN-DC. The source SN is denoted as S-SN, and the target SN or candidate SN is denoted as T-SN and / or other potential T-SNs.

[0099] Step 502 / 504. The MN initiates a conditional SN change by requesting (multiple) candidate SNs to allocate resources for the UE by means of the SN Addition procedure. The MN issues an SN Addition Request message, which includes an indication indicating that the request is for CPAC. The MN also provides a candidate cell that is recommended by the MN for selecting and configuring (multiple) SCG cells for (multiple) candidate SNs via the latest measurement results, and provides an upper limit on the number of PSCells that can be prepared by the candidate SN. From the list of cells indicated in the measurement results indicated by the MN, the candidate SN determines the list of (multiple) PSCells to be prepared (considering the maximum number indicated by the MN), for each prepared PSCell, the candidate SN determines the other SCG SCells, and provides the new corresponding SCG radio resource configuration to the MN in the NR RRC Reconfiguration message included in the SN Addition Request Confirmation message with the prepared (multiple) PSCell IDs. If data forwarding is required, the candidate SN provides the data forwarding address to the MN. The candidate SN includes an indication of a complete or incremental RRC configuration. The candidate SN may accept or reject each of the candidate cells listed in the measurement results indicated by the MN, ie, it may not configure any alternative candidates.

[0100] Step 506: The MN sends an RRC reconfiguration message to the UE. The RRC reconfiguration message includes the CPC configuration of the candidate PSCell, that is, the candidate cell configuration and a list of corresponding execution conditions.

[0101] Step 508. The UE applies the RRC reconfiguration message received in step 506, stores the candidate cell configuration, and replies to the MN with an RRC reconfiguration complete message. In some embodiments, the UE may store candidate cell configurations for different types of conditional reconfigurations (e.g., CHO, CPA, MN-initiated inter-SN CPC, SN-initiated inter-SN CPC, SN-initiated intra-SN CPC, etc.). Steps 502-508 are examples of an MN-initiated inter-SN CPC preparation procedure.

[0102] Step 510. After receiving the MN RRC Reconfiguration Complete message from the UE, the MN notifies the source SN that CPC has been configured via the Xn-U Address Indication procedure, for example, by including a CPC data forwarding indicator (the value is set to "triggered") in the Xn-U Address Indication message. The source SN (if applicable) starts early data forwarding together with the early status transfer procedure. PDCP SDU forwarding can be performed during early data forwarding.

[0103] Step 512: The UE starts to evaluate the execution conditions. If the execution conditions of a candidate PSCell are met, the UE applies the selected candidate PSCell configuration and synchronizes with the PSCell.

[0104] Step 514. A prepared SN initiated intra-SN CPC procedure (eg, receiving an RRC reconfiguration complete message for intra-SN CPC execution from the UE) or RRC reconfiguration using SRB3 has been performed in the source SN.

[0105] Step 516. The source SN notifies the MN of the execution of the SCG reconfiguration execution (e.g., the execution of the SN initiated intra-SN CPC and / or RRC reconfiguration using SRB3) via an SN MODIFICATION REQUIRED message. The message includes: one or more indications (e.g., "SCG RECONFIGURATION NOTIFICATION") for indicating the execution of the SCG reconfiguration. The message may also include: an updated / new SCG configuration for the MN (e.g., including a container IE of the S-NG-RAN node to the M-NG-RAN node in the SN MODIFICATION REQUIRED message).

[0106] Step 518. The MN sends an SN modification confirmation message to the source SN. If an indication (e.g., "SCG reconfiguration notification") is received from the source SN, the MN may consider that the prepared SN initiated intra-SN CPC procedure and / or RRC reconfiguration using SRB3 has been performed. In some embodiments, if the indication indicates that the prepared SN initiated intra-SN CPC procedure has been performed, the MN may consider that if any conditional reconfiguration (e.g., CHO, CPC) is configured in the UE, the conditional reconfiguration has been released due to the execution of the conditional SCG configuration or the execution of intra-SN CPC. In some embodiments, if the container IE from the S-NG-RAN node to the M-NG-RAN node is included in the SN modification request message, the MN may consider, if supported, that the new SCG configuration has been applied in the UE and should not be forwarded to the UE.

[0107] In some embodiments, the MN may initiate / trigger a CHO / CPAC cancellation / release procedure to (multiple) target / candidate nodes to cancel / release the CHO / CPAC configuration, and / or may initiate / trigger a CHO / CPAC modification procedure to (multiple) target / candidate nodes to update the candidate cell configuration based on the new SCG configuration. The MN may send an updated / new CHO / CPAC configuration (including the candidate cell configuration and / or execution conditions) to the UE via an RRC reconfiguration message.

[0108] In some embodiments, if any conditional reconfiguration (e.g., CHO, CPA, MN-initiated inter-SN CPC, SN-initiated inter-SN CPC, SN-initiated intra-SN CPC, etc.) is prepared and if the SN-initiated intra-SN CPC procedure is performed, the SN may include an indicator (e.g., SCG reconfiguration notification) in the SN / SgNB modification required message or other messages. The MN considers that if any conditional reconfiguration is configured in the UE, the conditional reconfiguration has been released due to the execution of the conditional SCG configuration.

[0109] The above systems and processes may be encoded in a signal bearing medium, a computer readable medium such as a memory, programmed in a device such as one or more integrated circuits, one or more processors, or processed by a controller or computer. The data may be analyzed in a computer system and used to generate a spectrum. If the methods are performed by software, the software may reside in a memory that resides in or interfaces to a storage device, a synchronizer, a communication interface, or a non-volatile or volatile memory that communicates with a transmitter. A circuit or electronic device is designed to send data to another location. The memory may include an ordered list of executable instructions for implementing a logical function. The described logical functions or any system elements may be implemented by optical circuit systems, digital circuit systems, source code, analog circuits, analog sources (such as analog electrical, audio or video signals), or a combination thereof. The software may be embodied in any computer readable or signal bearing medium for use or in combination with an instruction executable system, device or device. Such a system may include a computer-based system, a system containing a processor, or another system that can selectively retrieve instructions from an instruction executable system, device or device that can also execute instructions.

[0110] "Computer readable medium", "machine readable medium", "propagating signal" medium and / or "signal bearing medium" may include any device that includes storage, communication, propagation or transmission of software for use by or in conjunction with an instruction executable system, device or apparatus. Machine readable medium may selectively be, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared or semiconductor system, apparatus, device or propagation medium. A non-exhaustive list of machine readable medium examples includes: an electrically connected "electronic device" having one or more wires, a portable magnetic or optical disk, a volatile memory (such as a random access memory "RAM", a read-only memory "ROM", an erasable programmable read-only memory (EPROM or flash memory)), or an optical fiber. Machine readable medium may also include a tangible medium on which the software is printed, as the software may be stored electronically as an image or in another format (e.g., by optical scanning), then compiled, and / or interpreted or otherwise processed. The processed medium may then be stored in a computer and / or machine memory.

[0111] The illustrations of the embodiments described herein are intended to provide a general understanding of the structures of various embodiments. These illustrations are not intended to be used as a complete description of all elements and features of the devices and systems utilizing the structures or methods described herein. Many other embodiments may be very clear to those skilled in the art after reviewing the present disclosure. Other embodiments may be utilized and other embodiments may be derived from the present disclosure so that structural and logical replacements and changes may be made without departing from the scope of the present disclosure. In addition, these illustrations are only representative and may not be drawn to scale. Some proportions in the illustrations may be exaggerated, while other proportions may be minimized. Therefore, the present disclosure and the accompanying drawings should be considered illustrative and not restrictive.

[0112] One or more embodiments of the present disclosure may be referred to herein individually and / or collectively by the term "invention", merely for convenience, and without intending to voluntarily limit the scope of the present application to any particular invention or inventive concept. In addition, although specific embodiments have been shown and described herein, it should be understood that any subsequent arrangement designed to achieve the same or similar purpose may replace the specific embodiments shown. The present disclosure is intended to cover any and all subsequent adaptations or variations of the various embodiments. The combination of the above embodiments and other embodiments not specifically described herein will be clear to those skilled in the art after reviewing the description.

[0113] The phrase "coupled" is defined to mean directly connected or indirectly connected through one or more intermediate components. Such intermediate components may include both hardware-based and software-based components. The arrangement and type of components may be varied without departing from the spirit or scope of the claims set forth herein. More, different, or fewer components may be provided.

[0114] The above disclosed subject matter is considered to be illustrative, not restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments that fall within the true spirit and scope of the present invention. Therefore, to the maximum extent permitted by law, the scope of the present invention will be determined by the broadest permissible interpretation of the following claims and their equivalents, and should not be restricted or limited by the foregoing detailed description. Although various embodiments of the present invention have been described, it is clear to those of ordinary skill in the art that more embodiments and implementations are possible within the scope of the present invention. Therefore, the present invention is not limited except in accordance with the appended claims and their equivalents.

Claims

1. A method for wireless communication, comprising: sending a request message, the request message including an indication of execution of a secondary cell group (SCG) reconfiguration; as well as A response message associated with the request message is received.

2. The method according to claim 1, wherein sending the request message comprises: The request message is sent from a secondary wireless communication node (SN) to a primary wireless communication node (MN), and wherein the response message is received by the SN from the MN.

3. The method of claim 1, wherein the request message comprises an SN modification request message, and wherein the response message comprises an SN modification response message.

4. The method of claim 1, wherein the request message includes a new SCG configuration, and wherein the new SCG configuration is contained in a SN to MN container.

5. The method according to claim 4, further comprising: The MN regards the new SCG configuration as having been applied in the user equipment (UE) and does not forward the new SCG configuration to the UE.

6. The method of claim 1 , wherein the performing of SCG reconfiguration comprises at least one of: Execution of the SN Intra-SN Conditional PSCell Change (CPC) procedure initiated by the SN; or Execution of RRC reconfiguration using Signalling Radio Bearer (SRB) 3.

7. The method according to claim 6, wherein the execution of the SN-initiated intra-SN CPC causes the MN to believe that: if conditional reconfiguration is configured in the UE, the conditional reconfiguration has been released due to the execution of the SN-initiated intra-SN CPC.

8. The method of claim 7, wherein the conditional reconfiguration comprises at least one of the following: Conditional switching (CHO); Conditional PSCell Addition (CPA); MN initiated Conditional PSCell Change (CPC); or Inter-SN CPC initiated by SN, or intra-SN CPC initiated by SN.

9. A method for wireless communication, comprising: receiving a request message including an indication of execution of a secondary cell group (SCG) reconfiguration; as well as A response message associated with the request message is sent.

10. The method of claim 9, wherein receiving the request message comprises: The request message is received by a primary wireless communication node (MN) from a secondary wireless communication node (SN), and wherein the response message is sent by the MN to the SN.

11. The method of claim 9, wherein the request message comprises an SN modification request message, and wherein the response message comprises an SN modification response message.

12. The method of claim 9, wherein the request message includes a new SCG configuration, and wherein the new SCG configuration is contained in a SN to MN container.

13. The method according to claim 12, further comprising: The new SCG configuration is considered to have been applied in the user equipment (UE) and is not forwarded to the UE.

14. The method of claim 9, wherein the performing of SCG reconfiguration comprises at least one of: Execution of the SN Intra-SN Conditional PSCell Change (CPC) procedure initiated by the SN; or Execution of RRC reconfiguration using Signalling Radio Bearer (SRB) 3.

15. The method according to claim 14, wherein the execution of the SN-initiated intra-SN CPC causes the MN to believe that: if conditional reconfiguration is configured in the UE, the conditional reconfiguration has been released due to the execution of the SN-initiated intra-SN CPC.

16. The method of claim 15, wherein the conditional reconfiguration comprises at least one of the following: Conditional switching (CHO); Conditional PSCell Addition (CPA); MN initiated Conditional PSCell Change (CPC); or Inter-SN CPC initiated by SN, or intra-SN CPC initiated by SN.

17. A wireless communication device, comprising a processor and a memory, wherein the processor is configured to: read a code from the memory and implement the method according to any one of claims 1 to 16.

18. A computer program product comprising computer readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement the method according to any one of claims 1 to 16.

Images