Communication methods, terminal devices, and network devices

Abstract

This invention provides a communication method, network device, terminal device, and computer-readable medium for configuring a secondary cell group (SCG) when the SCG is temporarily suspended or deactivated. [Solution] The communication method includes determining whether the SCG of the second network device is deactivated in a terminal device served by the first network device, in accordance with the determination that the conditions for performing the configuration for the primary secondary cell (PScell) of the SCG of the second network device have been met, and sending a third message to the second network device of the SCG indicating that the PScell ​​configuration has already been completed by the terminal device, in accordance with the determination that the SCG is deactivated.

Description

Technical Field

[0001] Embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly, to communication methods, network devices, terminal devices, and computer-readable media.

Background Art

[0002] Dual Connectivity (DC) is an operating mode in which a terminal device (e.g., a user equipment, UE) can be configured to utilize radio resources provided by two network devices, e.g., two base stations (BS). The first network device serves the terminal device as a master node (MN), and the second network device serves the terminal device as a secondary node (SN). In a conventional DC scenario, the MN and SN can typically be associated with one or more serving cells, and carrier aggregation (CA) technology can be further implemented to efficiently utilize frequencies. The serving cell group associated with the MN is called a master cell group (MCG), and the serving cell group associated with the SN is called a secondary cell group (SCG).

[0003] In a DC scenario, the terminal device needs to simultaneously maintain radio links with the MN and SN, which results in significant power consumption. For example, the power consumption of a DC terminal device is several times that of a conventional terminal device, e.g., 3 to 4 times that of a Long Term Evolution (LTE) terminal device. Further, in some cases (e.g., when the data rate of the terminal device changes from high to low), it has been proposed to suspend / deactivate the SCG serving the terminal device or set it to a dormant state to reduce power consumption. However, when the SCG is suspended / deactivated, the process of the DC procedure, particularly the procedure related to the configuration of the SCG, has not yet been defined. [Overview of the project] [Problems that the invention aims to solve]

[0004] Overall, the exemplary embodiments of this disclosure provide solutions for setting up the SCG when the SCG is suspended / deactivated. [Means for solving the problem]

[0005] In a first embodiment, a communication method is provided. This method includes a first network device sending a request to a second network device for setting up an SCG associated with the second network device. This request includes first information relating to a first activity state of the SCG. This method further includes receiving a response to the request from the second network device. The response indicates the current activity state of the SCG. The current activity state is determined by the second network device based on the first information.

[0006] In a second embodiment, a communication method is provided, which includes receiving a request from a first network device in a second network device to configure an SCG associated with the second network device. The request includes first information relating to a first active state of the SCG. The method further includes determining the current active state of the SCG based on the first information. The method further includes transmitting a response to the request to the first network device, the response indicating the current active state of the SCG.

[0007] In a third embodiment, a communication method is provided, which includes receiving a first request from a second network device in a first network device for setting up an SCG associated with the second network device. The first message includes requirements relating to a second activity state of the SCG. The method further includes sending a second message to the second network device for confirmation of the first message.

[0008] In a fourth embodiment, a communication method is provided. This method includes generating a first message in a second network device for setting an SCG associated with the second network device. The first message includes parameters relating to a second activity state of the SCG. This method further includes transmitting the first message to the first network device.

[0009] In a fifth embodiment, a communication method is provided. This method includes determining whether the SCG of the second network device has been deactivated in a terminal device served by the first network device, based on the determination that the conditions for performing the configuration for the primary secondary cell (PScell) of the SCG of the second network device have been met. The method further includes sending a third message to the second network device of the SCG in response to the determination that the SCG has been deactivated. The third message indicates that the configuration for the PScell ​​has already been completed by the terminal device.

[0010] In a sixth embodiment, a communication method is provided, which includes a terminal device receiving a fourth message from a second network device for configuring the SCG of the second network. The fourth message includes a second instruction indicating that the SCG is deactivated. The method further includes sending a fifth message to the second network device of the SCG. The fifth message indicates that the configuration for the PScell ​​has already been completed by the terminal device.

[0011] In a seventh embodiment, a network device is provided. The network device includes a processing unit and a memory coupled to the processing unit in which instructions are stored, and when an instruction is executed by the processing unit, the device is made to execute the method according to the first embodiment.

[0012] In an eighth embodiment, a network device is provided. The network device includes a processing unit and a memory coupled to the processing unit in which instructions are stored, and when an instruction is executed by the processing unit, the device is made to execute the method according to the second embodiment.

[0013] In a ninth embodiment, a network device is provided. The network device includes a processing unit and a memory coupled to the processing unit in which instructions are stored, and when an instruction is executed by the processing unit, the device is made to execute the method according to the third embodiment.

[0014] In a tenth embodiment, a network device is provided. The network device includes a processing unit and a memory coupled to the processing unit in which instructions are stored, and when an instruction is executed by the processing unit, the device is made to execute the method according to the fourth embodiment.

[0015] In an eleventh embodiment, a terminal device is provided. The terminal device includes a processing unit and a memory coupled to the processing unit in which instructions are stored, and when an instruction is executed by the processing unit, the device is made to execute the method according to the fifth embodiment.

[0016] In a twelfth embodiment, a terminal device is provided. The terminal device includes a processing unit and a memory coupled to the processing unit in which instructions are stored, and when an instruction is executed by the processing unit, the device is made to execute the method according to the sixth embodiment.

[0017] In a thirteenth embodiment, a computer-readable medium storing instructions is provided, and when the instructions are executed on at least one processor, the at least one processor is caused to perform the method according to the first embodiment.

[0018] In a fourteenth embodiment, a computer-readable medium storing instructions is provided, and when the instructions are executed on at least one processor, the at least one processor is caused to perform the method according to the second embodiment.

[0019] In a 15th embodiment, a computer-readable medium storing instructions is provided, and when the instructions are executed on at least one processor, the at least one processor is caused to perform the method according to the third embodiment.

[0020] In a sixteenth embodiment, a computer-readable medium storing instructions is provided, and when the instructions are executed on at least one processor, the at least one processor is caused to perform the method according to the fourth embodiment.

[0021] In a 17th aspect, a computer-readable medium storing instructions is provided, and when the instructions are executed on at least one processor, the at least one processor is caused to execute the method according to the 5th aspect.

[0022] In an 18th aspect, a computer-readable medium storing instructions is provided, and when the instructions are executed on at least one processor, the at least one processor is caused to execute the method according to the 6th aspect.

[0023] It should be understood that the summary section of the invention is not intended to identify important or fundamental features of the embodiments of the present disclosure, nor to limit the scope of the present disclosure. Other features of the present disclosure should be readily understandable from the following description.

Brief Description of Drawings

[0024] By further describing some embodiments of the present disclosure in the drawings, the above-mentioned and other objects, features, and advantages of the present disclosure will be made more apparent.

[0025] [Figure 1] It is a block diagram of a communication environment in which embodiments of the present disclosure can be implemented.

[0026] [Figure 2A] It is a signaling diagram showing a process of exchanging active state information according to some embodiments of the present disclosure. [Figure 2B] It is a signaling diagram showing a process of exchanging active state information according to some embodiments of the present disclosure. [Figure 2C] It is a signaling diagram showing a process of exchanging active state information according to some embodiments of the present disclosure. [Figure 2D] It is a signaling diagram showing a process of exchanging active state information according to some embodiments of the present disclosure.

[0027] [Figure 3A]This is a signaling diagram illustrating the process for setting up an SCG according to some embodiments of the present disclosure. [Figure 3B] This is a signaling diagram illustrating the process for setting up an SCG according to some embodiments of the present disclosure.

[0028] [Figure 4] This figure shows an exemplary communication method implemented in a first network device according to some embodiments of the present disclosure.

[0029] [Figure 5] This figure shows an exemplary communication method implemented in a second network device according to some embodiments of the present disclosure.

[0030] [Figure 6] This figure shows another exemplary communication method implemented in a first network device according to some embodiments of the present disclosure.

[0031] [Figure 7] This figure shows another exemplary communication method implemented in a second network device according to some embodiments of the present disclosure.

[0032] [Figure 8] This figure shows an exemplary communication method implemented in a terminal device according to some embodiments of the present disclosure.

[0033] [Figure 9] This figure shows another exemplary communication method implemented in a terminal device according to some embodiments of the present disclosure.

[0034] [Figure 10] This is a schematic block diagram of a device suitable for implementing an embodiment of the present disclosure.

[0035] In the diagram, identical or similar reference numbers represent identical or similar elements. [Modes for carrying out the invention]

[0036] The principles of this disclosure are described here with reference to several exemplary embodiments. These embodiments are provided for illustrative purposes only and are intended to help those skilled in the art understand and implement this disclosure, and should be understood as not to imply any limitation on the scope of this disclosure. The disclosures described herein can be implemented in a variety of ways other than those described below.

[0037] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meanings as those generally understood by those skilled in the art.

[0038] References in this disclosure to “one embodiment,” “embodiment,” “exemplary embodiment,” etc., indicate that the described embodiment may include certain features, structures, or characteristics, but not all embodiments necessarily include such specific features, structures, or characteristics. Furthermore, such phrases do not necessarily refer to the same embodiment. Moreover, when describing certain features, structures, or characteristics in relation to an embodiment, it is considered that the influence of such features, structures, or characteristics in relation to other embodiments, whether or not they are explicitly described, is within the knowledge of those skilled in the art.

[0039] The terms used herein are for the purpose of describing specific embodiments and are not intended to limit the exemplary embodiments. The singular forms “one” and “the said” as used herein also include the plural forms unless expressly indicated in the context. Where used herein, the terms “include,” “contain,” “have,” “equip,” “possess,” and / or “have” specify the presence of the described features, elements, and / or components, but should be further understood that they do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0040] The terms “first,” “second,” etc., may be used in this specification to describe various elements, but it should be understood that these elements should not be limited by these terms. These terms are used solely to distinguish one element from another. For example, without departing the scope of the exemplary embodiments, the first element may be named the second element, and similarly, the second element may be named the first element. As used herein, the term “and / or” includes any and all combinations of one or more of the terms described.

[0041] In some examples, values, procedures, or devices are referred to as “best,” “worst,” “highest,” “minimum,” “maximum,” etc. Such descriptions are intended to show that a choice can be made from among many used functional alternatives, and it should be understood that such a choice does not necessarily need to be better, smaller, higher, or otherwise more desirable than other choices.

[0042] As used in this text, the term “network device” means a device capable of providing or hosting a cell or coverage on which terminal devices can communicate. Examples of network devices include, but are not limited to, Node B (NodeB or NB), Evolutionary Node B (eNodeB or eNB), Node B for New Radio Access (gNB), Remote Radio Unit (RRU), Radio Head (RH), Remote Radio Head (RRH), low-power nodes such as femtonodes and piconodes, satellite network devices, and aircraft network devices. For illustrative purposes, several exemplary embodiments of a network device will be described below with reference to an eNB.

[0043] As used in this text, the term “terminal device” refers to any end device that may be capable of wireless communication. For the purposes of this text, but not as an limitation, a terminal device may also be called a communication device, user device (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices include, but are not limited to, mobile phones, cellular phones, smartphones, voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable devices, personal digital assistants (PDAs), portable computers, desktop computers, imaging devices such as digital cameras, game terminals, music storage and playback devices, in-vehicle wireless terminals, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics, and devices operating on commercial and / or industrial wireless networks. In the following description, the terms “terminal device,” “communication device,” “terminal,” “user device,” and “UE” can be used interchangeably.

[0044] As used herein, the term “waking up” or similar expression means an operation that enables transmission with another device. Specifically, an operation to wake up an SCG or PScell ​​may mean activating all serving cells of the SCG, or activating the PScell ​​of the SCG. Additionally, an operation to wake up an SCG or PScell ​​may mean switching all serving cells of the SCG from dormant BWPs to non-dormant BWPs, or switching the PScell ​​of the SCG from dormant BWPs to non-dormant BWPs. It should be understood that the concept of wake-up is applicable to any one or more devices / elements / modules.

[0045] As used herein, the terms “sleeping” or similar expressions mean an operation to disable / pause transmission with another device. Specifically, an operation to put an SCG or PScell ​​to sleep may mean deactivating all serving cells of the SCG, or deactivating the PScells of the SCG. Furthermore, an operation to put an SCG or PScell ​​to sleep may also mean switching the SCG to a dormant BWP, or switching the PScells of the SCG to a dormant BWP. It should be understood that the concept of sleep is applicable to any one or more devices / elements / modules.

[0046] In one embodiment, a terminal device can be connected to a first network device and a second network device. One of the first and second network devices may be a master node and the other a secondary node. The first and second network devices may use different radio access technologies (RATs). In one embodiment, the first network device may be a first RAT device, and the second network device may be a second RAT device. In one embodiment, the first RAT device is an eNB, and the second RAT device is a gNB. Information about different RATs can be transmitted to the terminal device from at least one of the first and second network devices. In one embodiment, the first information may be transmitted from the first network device to the terminal device, and the second information may be transmitted from the second network device directly or via the first network device to the terminal device. In one embodiment, information about the settings of the terminal device set by the second network device can be transmitted from the second network device via the first network device. Information regarding the reconfiguration of terminal devices set by the second network device can be transmitted from the second network device directly to the terminal devices or via the first network device.

[0047] The communications discussed herein may use any appropriate standard, including but not limited to New Radio (NR), Long-Term Evolution (LTE), LTE-Advanced (LTE-A), Broadband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), and Narrowband Internet of Things (NB-IoT). Furthermore, communications between the first and fourth devices in a communications network may be implemented in accordance with any appropriate generation of communications protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, future fifth-generation (5G) communications protocols, and / or any other protocols currently known or to be developed in the future. Embodiments of this disclosure can be applied to a variety of communications systems. Given the rapid development of communications, there will naturally be future types of communications technologies and systems that can embody this disclosure. This should not be considered to limit the scope of this disclosure to the aforementioned systems only.

[0048] The functions described herein can be performed in fixed and / or wireless network nodes in various exemplary embodiments, but in other exemplary embodiments, the functions can be implemented in user device equipment (e.g., mobile phones, tablet computers, laptop computers, desktop computers, mobile IoT devices, or fixed IoT devices). For example, user device equipment may optionally have the corresponding capabilities described in relation to fixed and / or wireless network nodes. User device equipment may be a control device such as a chipset or processor configured to control the user device when installed in the user device and / or within the user device. Examples of such functions include bootstrap server functions and / or home subscriber servers, and can be implemented within user device equipment by providing the user device equipment with software configured to run on the user device equipment from the perspective of these functions / nodes.

[0049] As mentioned above, in DC scenarios, CA technology can be implemented to use frequency efficiently. However, the introduction of CA technology typically increases power consumption in terminal equipment (e.g., UE).

[0050] One conventional power-saving solution for CA scenarios involves the activation / deactivation of the SCell. The SCell activation / deactivation mechanism is supported to allow for reasonable power consumption (e.g., battery consumption) of the terminal device when setting up CA. When the SCell is deactivated, the terminal device does not need to receive the corresponding PDCCH or PDSCH and cannot transmit within the corresponding uplink, but is required to perform Channel Quality Indicator (CQI) measurements. Conversely, when the SCell is activated, the terminal device is expected to receive PDSCH and PDCCH (if the terminal device is configured to monitor PDCCH from the SCell) and be able to perform CQI measurements.

[0051] Another conventional power-saving solution for CA scenarios involves SCell dormancy. To enable rapid SCell activation when CA is set, a SCell can be configured with one dormant bandwidth part (BWP). If the active BWP of an activated SCell is a dormant BWP, the terminal equipment stops monitoring the PDCCH on the SCell, but continues to perform Channel Status Information (CSI) (e.g., CQI) measurements, Automatic Gain Control (AGC), and beam management, if configured. Downlink Control Information (DCI) is used to control entry into / exit from a dormant BWP for one or more SCells or one or more SCGs. A dormant BWP is one of the dedicated BWPs of a UE configured by the network via dedicated radio resource control (RRC) signaling. Dormant BWPs cannot be configured for special cells (SpCells) and PUCCH SCells.

[0052] As mentioned above, in a DC scenario, maintaining two wireless links simultaneously poses a significant problem in terms of power consumption for terminal equipment and the network. Taking EN-DC as an example, in some cases, the power consumption of terminal equipment in an NR network is three to four times higher than that of terminal equipment in an LTE network. To reduce power consumption, it has been suggested that SCGs may be paused / deactivated, or in some cases, set to a dormant state. For example, in an EN-DC deployment, MNs provide basic coverage. If the UE's data rate requirements change dynamically, for example from high to low, SNs can be deactivated or paused to reduce power consumption.

[0053] It should be understood that the SCG deactivation mechanism is also required for other MR-DC deployments, including but not limited to EN-DC, NGEN-DC, and NR-DC. The terms “SCG pause” and “SCG deactivation” are used interchangeably herein.

[0054] Additionally, three options for modeling SCG pause have already been proposed below. In Option 1, all serving cells associated with the SN, including PScells and SCells, are activated, and the active BWP is set as a dormant BWP. In Option 2, all serving cells associated with the SN, including PScells and Scells, are deactivated. In Option 3, the SCell of the SCG should be deactivated, but the PScell ​​of the SCG should be activated, and the active BWP should be set as a dormant BWP.

[0055] As can be seen from the above, when the SCG is suspended / deactivated, SCG transmissions for all SRBs and data radio bearers (DRBs) should be suspended. However, some DC operations related to the SCG configuration procedure (e.g., adding / modifying / changing PScells, adding / modifying / changing SNs, etc.) may require the terminal device to perform interactions between the terminal device and the network device (e.g., performing Random Access (RA), sending Radio Resource Control (RRC) Reconfiguration Complete messages, etc.). However, it is not explained how to handle the above interactions when the SCG is suspended / deactivated.

[0056] According to some exemplary embodiments of this disclosure, a solution is proposed for setting up an SCG when it is suspended / deactivated. In this solution, network devices (e.g., MN and SN) can exchange activity status (e.g., active or inactive) information. More specifically, a first network device (e.g., MN) can send a request containing first information regarding a first activity status of an SCG for setting up an SCG associated with a second network device (e.g., SN). The second network device can then respond to the first network with its current activity status (i.e., its actual activity status). Alternatively, the second network device can generate a first message containing parameters regarding a second activity status of an SCG for setting up an SCG associated with the second network device. The second network device can then send the generated first message to the first network device. Thus, the first network device can obtain the current / actual activity status of the second network device.

[0057] According to some other exemplary embodiments of this disclosure, another solution is proposed for configuring the SCG when the SCG is suspended / deactivated. In this solution, if a terminal device determines that the conditions for performing the configuration of the SCG for the PScell ​​of the second network device are met and the SCG of the second network device is deactivated, the terminal device sends a third message to the second network device of the SCG indicating that the configuration for the PScell ​​has already been completed by the terminal device. Alternatively, if the terminal device receives a fourth message from the second network device containing a second instruction indicating that the SCG is deactivated for configuring the SCG of the second network, the terminal device may send a fifth message to the second network device of the SCG indicating that the configuration for the PScell ​​has already been completed by the terminal device. Thus, configuration for the SCG can be performed even if the SCG is deactivated.

[0058] The following will provide a more detailed explanation with reference to Figures 1 through 10. Environment example

[0059] Figure 1 shows an exemplary communication environment 100 in which exemplary embodiments of the present disclosure can be implemented. In the communication environment 100, a terminal device 130 is able to communicate with a first network device 110 and further with a second network device 120. The first network device 110 can communicate with the second network device 120 (for example, via an X2 or Xn interface).

[0060] In the example in Figure 1, the first network device 110 serves the terminal device 130 as an MN, while the second network device 120 serves the terminal device 130 as an SN. The serving areas of the first network device 110 and the second network device 120 are called cells. As shown in Figure 1, the cell group of the first network device 110 includes a primary cell 150-1 and an additional secondary cell (SCell) 150-2. Since the first network device 110 functions as an MN, the cell group of the first network device 110 is referred to as MCG 150. The cell group of the second network device 120 includes a primary cell 160-1 and an additional secondary cell 160-2. Since the second network device 120 functions as an SN, the cell group of the second network device 120 is referred to as SCG 160, and the primary cell 160-1 is also referred to as PScell ​​160-1.

[0061] Communication between terminal device 130 and the first network device 110, and between terminal device 130 and the second network device 120, can be implemented according to any appropriate communication protocol. Communication from terminal device 130 toward the first network device 110 or the second network device 120 is called UL communication, and communication from the first network device 110 or the second network device 120 toward terminal device 130 is called DL communication. Terminal device 130 can move between the coverage areas of the first network device 110, the second network device 120, and possibly other network devices.

[0062] In UL communication, terminal device 130 can transmit UL data and control information via the UL channel. In some exemplary embodiments, UL data can be transmitted over the physical uplink shared channel (PUSCH) and / or any other available UL channel used for data transmission. In DL transmission, the first network device 110 or the second network device 120 can transmit DL data and control information to terminal device 130 via the DL channel. In some examples, DL data can be transmitted over the physical downlink shared channel (PDSCH) and / or any other available DL channel used for data transmission.

[0063] The DCs provided by the first network device 110 and the second network device 120 may include any suitable type of multi-radio dual connection (MR-DC), including but not limited to E-UTRA (Evolved Universal Terrestrial Radio Access)-NR dual connection (EN-DC), NGEN-DC, NE-DC, and NR-DC. In the case of EN-DC, the first network device 110 is an eNB and the second network device 120 is a gNB. In the case of NGEN-DC, the first network device 110 is a gNB and the second network device 120 is an eNB. In the case of NR-DC, both network devices 110 and 120 are gNBs.

[0064] The number of SCells in Figure 1 is given for illustrative purposes only and should be understood as not implying any limitations to this disclosure. In some other embodiments, the first network device 110 and the second network device 120 can provide any suitable number of SCells for serving the terminal device 130.

[0065] It should be understood that the number and types of devices shown in Figure 1 are given for illustrative purposes only and do not imply any limitations to this disclosure. The communication environment 100 may include any suitable number of network devices and / or terminal devices suitable for carrying out embodiments of this disclosure. Furthermore, the communication environment 100 may include any other devices other than network devices and terminal devices (e.g., core network elements), but these are omitted herein to avoid obscuring the invention. Example procedure for exchanging activity status information

[0066] The inventors of this disclosure have noticed that there may be situations in which an inactive state is acceptable for an SCG, such as when the SCG is overloaded or when the SCG does not support SCG activation settings. Therefore, the MN needs to know the actual / current activity state of the SCG so that it can perform reasonable subsequent processing based on the actual / current activity state of the SCG. Several exemplary embodiments of this disclosure are described in detail below.

[0067] Figure 2A is a signaling diagram showing a process 200 for exchanging activity status information according to some embodiments of the present disclosure. For illustrative purposes, the process 200 will be described with reference to Figure 1. The process 200 may involve a terminal device 130, a first network device 110, and a second network device 120. In the process 200 of Figure 2A, the setup procedure for the SCG is initiated by the first network device 110, which operates as the MN.

[0068] The first network device 110 sends a request (202) to configure the SCG associated with the second network device 120. This request may include first information relating to the first active state of the SCG. This request can be sent via the X2 or Xn interface.

[0069] In some exemplary embodiments, the first network device 110 sends an SN addition request containing first information in accordance with the decision that an SCG should be added. For example, the first network device 110 sends an SN addition request to the second network device 120 with an SCG activation / deactivation request instruction.

[0070] Alternatively, in some exemplary embodiments, the first network device 110 transmits an SN modification request containing first information in accordance with the decision that the SCG should be modified. For example, the first network device 110 transmits an SN modification request with an SCG activation / deactivation request instruction to the second network device 120.

[0071] It should be understood that the above-mentioned messages are given for illustrative purposes only and do not imply any limitations. In other exemplary embodiments, requests can be any appropriate message via the X2 or Xn interface. It should also be understood that the first information relating to the first activity state of the SCG can be represented in any appropriate way, such as in instructions, fields, or headers. Furthermore, the first information relating to the first activity state of the SCG can be represented explicitly or implicitly. The scope of this disclosure is not limited in these respects.

[0072] Upon receiving a request from the first network device 110, the second network device 120 can configure the SCG according to this request. Furthermore, the second network device 120 can configure the activity state according to the first information contained in the request. In some cases, for example, if the SCG of the second network device 120 is performing a transmission (including data or signaling) to and from the terminal device 130, or if the SCG does not support SCG deactivation configuration, the deactivation configuration for the SCG may fail. In some other cases, if the second network device 120 is overloaded / busy (i.e., unable to provide further services), the activation configuration for the SCG may fail. It should be understood that the examples of failure configurations described above are given for illustrative purposes only and do not imply any limitations on this disclosure.

[0073] Next, the second network device 120 determines the current activity state of the SCG. Then, the second network device 120 transmits a response to the request to the first network device 110 (204), the response indicating the determined current activity state of the SCG.

[0074] In some exemplary embodiments, the second network device 120 sends an SN addition request acknowledgment in response to the SN addition request. For example, the second network device 120 sends an SN addition request acknowledgment with an SCG activation / deactivation instruction to the first network device 110.

[0075] Alternatively, in some exemplary embodiments, the second network device 120 transmits an SN modification request acknowledgment in response to the SN modification request. For example, the second network device 120 transmits an SN modification request acknowledgment with an SCG activation / deactivation instruction to the first network device 110.

[0076] It should be understood that the messages described above are given for illustrative purposes only and do not imply any limitations. In other exemplary embodiments, requests can be any appropriate message via the X2 or Xn interface. It should be understood that the second network device may explicitly or implicitly indicate a determined current activity state. Furthermore, the current activity state can also be represented in any appropriate way, such as indices, fields, or headers. The scope of this disclosure is not limited in these respects.

[0077] Thus, during the SN / SCG addition / modification / change procedure, the first network device 110 (i.e., MN) can request the SN to activate / deactivate the SCG, and the SCG can respond to the MN with its actual / current state (active / deactivate). Furthermore, the actual / current state (active / deactivate) of the SCG can be provided by the second network device 120 (i.e., SN). Based on the actual / current state (active / deactivate) of the SCG, the first network device 110 can perform reasonable subsequent processing based on the actual activity state of the SCG. For example, the first network device 110 can decide whether to set the SCG to terminal device 130 or change it to another SN.

[0078] Similarly, referring to Figure 2A, the first network device 110 sends an RRC message to the terminal device (206). The RRC message may include configuration information for the MCG of the first network device 110, and may also include configuration information for the SCG of the second network device 120 (for example, an instruction indicating that the SCG of the second network device 120 is deactivated). Thus, the terminal device 130 can send an RRC response to the first network device 110 (208). The RRC response indicates that the configuration for the MCG has been completed, and further indicates that the configuration for the SCG of the second network device 120 has been completed. Next, the first network device 110 can send a message to the second network device 120 (210) to complete the SCG configuration.

[0079] For illustrative purposes, without limiting the scope of this disclosure, the first network device 110 may send an RRCReconfiguration message to the terminal device 130. The terminal device 130 responds with an RRCReconfigurationComplete containing an SN RRCReconfigurationComplete message. The first network device 110 then sends an SN ReconfigurationComplete containing an SN RRCReconfiguretionComplete message to the second network device 120.

[0080] It should be understood that the activity state may be exchanged during the SN change procedure between the source SN and the target SN. These procedures are illustrated with reference to Figures 2B and 2C. Figure 2B is a signaling diagram showing process 240 for exchanging activity state information during the SN change procedure between the source SN and the target SN initiated by the first network device 110 (i.e., MN). Figure 2C is a signaling diagram showing process 260 for exchanging activity state information during the SN change procedure between the source SN and the target SN initiated by the second network device 120 (i.e., SN). For illustrative purposes, processes 240 and 260 are illustrated with reference to Figure 1. Processes 240 and 260 relate to terminal device 130, first network device 110, and second network devices 120-1 and 120-2. In process 240 in Figure 2B and process 260 in Figure 2C, the first network device 110 operates as an MN, the second network device 120-1 operates as a source SN, and the second network device 120-2 operates as a target SN.

[0081] First, referring to Figure 2B, the first network device 110 (i.e., MN) sends a request (202) to configure the SCG associated with the second network device 120-2 (i.e., target SN). This request may include first information regarding the first active state of the SCG of the second network device 120-2. For example, the first network device 110 sends an SN addition request with an SCG activation / deactivation request instruction.

[0082] Next, the second network device 120-2 can configure the SCG according to the request received in 202. Then, the second network device 120-2 determines the current activity state of the SCG. The second network device 120-2 sends a response to the first network device 110 (204), the response indicating the determined current activity state of the SCG. For example, the second network device 120-2 sends an SN addition request acknowledgment to the first network device 110 with an SCG activation / deactivation instruction.

[0083] Upon receiving a response from the second network device 120-2, the first network device 110 disconnects from the second network device 120-1 (i.e., the source SN). More specifically, the first network device 110 sends an SN Release request to the second network device 120-1 (242) and receives an SN Release request acknowledgment from the second network device 120-1 (244).

[0084] Next, the first network device 110 triggers the terminal device 130 to complete the corresponding configuration. More specifically, the first network device 110 sends an RRCReconfiguration message to the terminal device 130 (246) and receives an RRCReconfigurationComplete containing an SN RRCReconfigurationComplete message from the terminal device 130 (248). The first network device 110 then sends an SN ReconfigurationComplete containing an SN RRCReconfiguretionComplete message to the second network device 120-1 (250).

[0085] Thus, the exchange of active states is achieved during the SN change procedure between the source SN and the target SN.

[0086] Referring now to Figure 2C, the SN change procedure between the source SN and the target SN is initiated by the SN. The second network device 120-1 decides to initiate the SN change procedure and sends an SN change request to the first network device 110 (262). Upon receiving the SN change request, the first network device 110 sends a request (202) to configure the SCG associated with the second network device 120. This request may include first information regarding the first active state of the SCG. For example, the first network device 110 sends an SN addition request with an SCG activation / deactivation request instruction.

[0087] Next, the second network device 120-2 can configure the SCG according to the request received in 202. Then, the second network device 120-2 determines the current activity state of the SCG. The second network device 120-2 sends a response to the first network device 110 (204), the response indicating the determined current activity state of the SCG. For example, the second network device 120-2 sends an SN addition request acknowledgment to the first network device 110 with an SCG activation / deactivation instruction.

[0088] Upon receiving a response from the second network device 120-2, the first network device 110 triggers the terminal device 130 to complete the corresponding configuration. More specifically, the first network device 110 sends an RRCReconfiguration message to the terminal device 130 (264) and receives an RRCReconfigurationComplete from the terminal device 130 (266) which contains an SN RRCReconfigurationComplete message.

[0089] Next, each of the first network devices 110 sends an SN Change Confirmation to the second network device 120-1 (268) and sends an SN Reconfiguration complete message containing the SN RRC Reconfiguration complete message to the second network device 120-2.

[0090] Thus, the exchange of active states is achieved during the SN change procedure between the source SN and the target SN.

[0091] Referring to Figures 2B and 2C, the specific process for exchanging active states during an SN change procedure between a source SN and a target SN has already been described. When discussing the process in Figures 2B and 2C, it should be understood that the types and order of messages described above are shown for illustrative purposes only and do not imply any limitations. In other exemplary embodiments, messages can be replaced with any suitable messages and executed in any suitable order.

[0092] Figure 2D is a signaling diagram showing a process 280 for exchanging activity status information according to some embodiments of the present disclosure. For illustrative purposes, the process 280 will be described with reference to Figure 1. The process 280 may involve a terminal device 130, a first network device 110, and a second network device 120. In the process 280 of Figure 2D, the setup procedure for the SCG is initiated by the second network device 120, which acts as the SN.

[0093] The second network device 120 generates a first message containing parameters relating to a second active state of the SCG for setting the SCG associated with the second network device 120. The second network device 120 then transmits the first message to the first network device 110 (282). For illustrative purposes, without limiting the scope of this disclosure, the second network device 120 transmits an SN modification requesting an SCG active / inactive instruction.

[0094] In some exemplary embodiments, after sending the first message, the second network device 120 starts a timer. If the second network device 120 does not receive any messages indicating that the settings requested by the first message have been fully executed, the second network device 120 determines that the first message was rejected by the first network device 110 or terminal device 130, or that the settings requested by the second network device failed to be set by the first network device 110 or terminal device 130.

[0095] Next, the first network device 110 can determine whether the setting of the first message is acceptable. If the first network device 110 decides to accept the setting of the first message, the first network device 110 sends an RRC Reconfiguration to the terminal device 130 (284) and receives an RRC Reconfiguration complete from the terminal device 130 (286) which contains SN RRC Reconfiguration Complete. Next, the first network device 110 sends an SN Modification Confirmation which contains SN RRC Reconfiguration complete to the second network device 120 (288).

[0096] Alternatively, if the first network device 110 refuses to accept the first message, the first network device 110 may respond with a second message (283) which additionally includes the reason for the refusal, or the first network device 110 may simply ignore the first message and not respond with any message to the second network device 120.

[0097] In addition, if the first network device 110 determines that the settings required by the second network device have failed to be set by the first network device 110 or the terminal device 130 (for example, if the first network device 110 does not receive a message from the terminal device 130 indicating that the settings were successfully performed, or if the first network device 110 receives a message from the terminal device 130 indicating that the settings failed), the first network device 110 responds with a second message indicating failure (283), which additionally holds the cause of the failure, or the first network device 110 simply ignores the first message and does not respond with any message to the second network device 120.

[0098] When describing the process in Figure 2C, it should be understood that the types and order of messages described above are shown for illustrative purposes only and do not imply any limitations. In other exemplary embodiments, messages can be replaced with any suitable messages and executed in any suitable order.

[0099] Thus, when SN initiates SCG configuration, SN can determine the expected activity state, and MN can complete the SCG configuration requested by SN. Example process for configuring PSCELL for a deactivated SCG

[0100] Overall, if terminal device 130 needs to configure a PScell ​​(e.g., add or modify one), terminal device 130 must perform an interaction between terminal device 130 and the network device of the target PScell ​​(e.g., execute an RA procedure, send an RRC Reconfiguration Complete message, etc.). However, as mentioned above, when the SCG is suspended / deactivated, both the SRB and DRS between terminal device 130 and the SCG are suspended, and random access procedures are not permitted. Therefore, it is desirable to specify a process for configuring a PScell ​​for a deactivated SCG.

[0101] An example of performing the configuration for the PScell ​​of the SCG will be described with reference to Figure 3A. Figure 3A is a signaling diagram showing a process 300 for configuring the SCG according to some embodiments of the present disclosure. For illustrative purposes, the process 300 will be described with reference to Figure 1. The process 300 may involve a terminal device 130, a first network device 110, and a second network device 120. For illustrative purposes, without limiting the scope of the present disclosure, in the process 300 of Figure 3A, the first network device 110 operates as an MN and the second network device 120 operates as an SN.

[0102] As shown in Figure 3A, if the terminal device 130 determines that the conditions for performing the configuration for the PScell ​​of the SCG of the second network device 120 are met, the terminal device 130 determines whether or not the SCG of the second network device 120 is deactivated (310).

[0103] Next, if terminal device 130 determines that the SCG is deactivated, terminal device 130 sends a third message to the second network device 120 of the SCG (320) indicating that the configuration for PScell ​​has already been completed by terminal device 130.

[0104] This allows you to configure (for example, add or modify) the PScell ​​of the SCG even when the SCG is deactivated.

[0105] Furthermore, there are several scenarios in which the terminal device 130 needs to perform configuration for PScell. Therefore, this disclosure proposes multiple processes for different scenarios. In addition, this disclosure specifies a process for the RA procedure in a scenario in which the SCG is deactivated.

[0106] Hereafter, exemplary processes relating to this disclosure for different scenarios will be described as follows. Furthermore, it should be understood that the types and order of messages shown below when describing the process in Figure 3A are shown for illustrative purposes only and do not imply any limitations. In other exemplary embodiments, messages can be replaced with any appropriate messages and executed in any appropriate order.

[0107] First, we will describe a scenario in which the MN initiates the addition / modification of PScells for a deactivated SCG. Similarly, referring to Figure 3A, terminal device 130 receives a first RRC reconfiguration message from first network device 110 (302) to configure the SCG's PScells, and terminal device 130 can determine that the conditions for performing configuration for the SCG's PScells are met. As an example, terminal device 130 receives an RRCReconfiguration message for the SCG from first network device 110 via SRB 1, the RRCReconfiguration message includes a reconfigurationWithSync element, and terminal device 130 decides to perform PScell ​​configuration (e.g., adding or modifying PScells).

[0108] Next, the terminal device 130 determines (310) whether the SCG of the second network device 120 is deactivated. In some exemplary embodiments, the determination is made based on the original active state of the SCG and the first RRC reset message received in 302. In some exemplary embodiments, if the first RRC reset message indicates (e.g., by instruction) that the SCG is deactivated, the terminal device 130 determines that the SCG is deactivated. Alternatively, in some other exemplary embodiments, if the first RRC reset message indicates (e.g., by instruction) that the SCG is activated, the terminal device 130 determines that the SCG is activated. Furthermore, in some other exemplary embodiments, if the first RRC reset message does not indicate the active state of the SCG, the terminal device 130 continues to maintain the original active state.

[0109] For example, if an SCG is added and an RRCReconfiguration message (e.g., an SN addition message) indicates that the SCG has been deactivated (e.g., by instruction), the terminal device 130 determines that the SCG is deactivated. As another example, if the SCG was deactivated before receiving an RRCReconfiguration message and the RRCReconfiguration message does not indicate that the SCG is activated (e.g., the RRCReconfiguration message indicates that the SCG is deactivated, or the RRCReconfiguration message does not contain an instruction indicating the activity status of the SCG), the terminal device 130 determines that the SCG is deactivated.

[0110] As described above, if terminal device 130 determines that SCG is deactivated, terminal device 130 sends a third message to the second network device 120 of SCG (320) indicating that the configuration for PScell ​​has already been completed by terminal device 130.

[0111] In some exemplary embodiments, terminal device 130 applies the SCG configuration and sends an RRC Reconfiguration Complete message to the first network device 110 (i.e., MN) containing an SN RRC response message for SN, but terminal device 130 does not initiate an RA to the target PScell ​​in order to keep the SCG deactivated.

[0112] As an example of sending a third message, terminal device 130 sends the third message to the first network device 110 so that the third message is sent to the second network device 120 via the first network device 110. Additionally, terminal device 130 may suspend transmission with the second network device 120 to avoid the RA procedure for PScell.

[0113] Alternatively, in some exemplary embodiments, terminal device 130 applies the SCG configuration but maintains at least the PScell ​​or SCG in a wake-up state. Terminal device 130 then sends an RRC Reconfiguration Complete message, including an SN RRC response message, to the first network device 110 (i.e., MN). Additionally, terminal device 130 initiates an RA to the target PScell ​​and puts the PScell ​​or SCG to sleep after the RA procedure is complete.

[0114] As another example of sending a third message, terminal device 130 sends a third message to the first network device 110 so that the third message is sent to the second network device 120 via the first network device 110. Additionally, terminal device 130 enables transmission with the second network device, executes an RA procedure for the PScell ​​via the enabled transmission, and pauses transmission with the second network device upon completion of the RA procedure.

[0115] Thus, the process for adding / modifying PScells when SCG is inactive is defined.

[0116] Furthermore, the SN can also initiate configuration for the PScell. Similarly, referring to Figure 3A, terminal device 130 receives a second RRC reconfiguration message from the second network device 120 (306) for configuring the SCG's PScell, the second RRC reconfiguration message includes a first instruction indicating that the SCG is deactivated. Terminal device 130 can then determine that the conditions for performing configuration for the SCG's PScell ​​are met and further determine that the SCG is deactivated. For example, terminal device 130 receives an RRCReconfiguration message for the SCG from the second network device 120 via SRB 3, the RRCReconfiguration message includes a reconfigurationWithSync element, and the RRCReconfiguration message indicates that the SCG is deactivated (e.g., by the first instruction). Terminal device 130 then decides to perform PScell ​​configuration (e.g., modifying the PScell) and determines that the SCG is deactivated.

[0117] For example, the SCG is activated before the second RRC message is received, but the SCG deactivation instruction is included in the second RRCReconfiguration message from the second network device 120 (i.e., SN) via SRB 3. That is, the SCG deactivation is performed during the SN in-modification. The terminal device 130 then determines that the conditions for performing the configuration for the SCG's PScell ​​have been met and the SCG is deactivated.

[0118] As described above, if terminal device 130 determines that SCG is deactivated, terminal device 130 sends a third message to the second network device 120 of SCG (320) indicating that the configuration for PScell ​​has already been completed by terminal device 130.

[0119] In some exemplary embodiments, to ensure that the SCG is reliably deactivated, terminal device 130 applies the configuration and sends a ULInformationTransferMRDC message containing an embedded RRCReconfigurationComplete message to the SN to the first network device. Furthermore, terminal device 130 does not initiate RA to the target PScell.

[0120] As an example of sending a third message, terminal device 130 sends the third message to the first network device 110 so that the third message may be sent to the second network device 120 via the first network device 110. Additionally, terminal device 130 may suspend transmission with the second network device 120 to avoid the RA procedure for PScell.

[0121] In some exemplary embodiments, the terminal device 130 can deactivate the SCG after sending an RRCReconfigurationComplete message to the second network device 120.

[0122] Alternatively, in some other exemplary embodiments, terminal device 130 applies the SCG configuration but maintains at least the PScell ​​or SCG in a wake-up state and SRB3 not suspended. Terminal device 130 then sends an RRC Reconfiguration Complete message to the second network device 120 (i.e., SN). In addition, terminal device 130 initiates an RA procedure to the target PScell. The terminal device then puts the PScell ​​or SCG to sleep and suspends SRB3.

[0123] As another example of sending a third message, terminal device 130 enables transmission with second network device 120, sends the third message to second network device 120 via the enabled transmission, and pauses the enabled transmission with second network device 120 upon completion of transmission for the setup completion message. Additionally, terminal device 130 executes an RA procedure for PScell ​​via the enabled transmission before pausing the enabled transmission.

[0124] Thus, the process for adding / modifying PScells when SCG is inactive is defined.

[0125] Additionally, terminal device 130 can receive messages from the first network device (i.e., MN) for conditional PScell ​​addition / modification for deactivated SCGs. Before describing the process relating to this disclosure, a general conditional PScell ​​modification (CPC) or conditional PScell ​​addition (CPA) mechanism without SRB 3 is described below.

[0126] In a scenario where the SCG is activated, the second network device 120 (i.e., SN) initiates this procedure by sending an SN Modification Required message containing an SN RRC reconfiguration message to the first network device 110. The first network device 110 forwards the SN RRC reconfiguration message containing an RRC reconfiguration message to the terminal device 130. The terminal device 130 applies the new configuration and replies with an RRC reconfiguration complete message, including an SN RRC reconfiguration complete message. If a CPC is configured in the RRCReconfiguration message, the terminal device 130 maintains a connection with the source PScell ​​after receiving the CPC configuration and begins evaluating the CPC execution conditions for the candidate PScell. If at least one CPC candidate PScell ​​satisfies the corresponding CPC execution conditions, the terminal device 130 disconnects from the source PScell, applies the corresponding configuration stored for the selected candidate PScell, and synchronizes with the candidate PScell. Terminal device 130 completes the CPC execution procedure by sending a ULInformationTransferMRDC message to the first network device 110, which includes an embedded RRCReconfigurationComplete message to the second network device 120. When the first network device 110 receives an SN RRC response message from terminal device 130, it includes the SN RRC response message in an SN Modification Confirmation message and forwards it to the second network device 120. If instructed, terminal device 130 synchronizes with the PScell ​​of the second network device 120 as described in the SN Addition procedure. Alternatively, terminal device 130 may perform the UL transmission after the new configuration has already been applied.

[0127] Therefore, when terminal device 130 receives an RRC Reconfiguration message for CPC or CPA configuration, it sends an RRC Reconfiguration complete message to MN. Furthermore, when the CPC execution conditions are met, terminal device 130 should send an RRC Reconfiguration Complete message to MN and initiate an RA procedure to the target PScell ​​so that network devices can become aware of the target PScell's information. However, if SCG is deactivated, RA to SRB3 and SN is not normally permitted. Additionally, if RA is not permitted, and there are multiple candidate PScells, network devices (e.g., the first network device 110 and the second network device 120) will not know which candidate PScell ​​has been selected.

[0128] The inventors of this disclosure have found that if a CPC or CPA setting is received before SCG deactivation, the terminal device 130 can continue to evaluate the CPC execution conditions for the candidate PScell ​​even though the SCG is subsequently deactivated. Furthermore, the inventors of this disclosure have also found that if a CPC setting is received after SCG deactivation, the terminal device 130 can still evaluate the CPC execution conditions for the candidate PScell. In addition, information about the target PScell ​​(e.g., identification information of the target PScell) can be shown in the RRC Reconfiguration Complete message. Thus, even if the terminal device 130 does not initiate an RA procedure to the target PScell, the network devices (e.g., the first network device 110 and the second network device 120) can know the information about the target PScell. This will be explained in more detail below.

[0129] Similarly, referring to Figure 3A, terminal device 130 receives (304) a third RRC reset message from the first network device 110 for conditionally configuring the SCG's PScell. The third RRC reset message contains second information for multiple candidate PScells. Then, in response to the received third RRC reset message, terminal device 130 selects a PScell ​​to be switched from among the multiple candidate PScells and determines that the conditions for performing the configuration for the SCG's PScell ​​are met.

[0130] The terminal device 130 should understand that it can receive a third RRC reconfiguration message to conditionally configure a PScell ​​in several scenarios, such as a conditional PScell ​​change within a SN without MN involvement when SRB 3 is not used, a conditional PScell ​​change within a SN with MN involvement, a PScell ​​change between conditional SNs, or a conditional PScell ​​addition (CPC settings are received by SRB1).

[0131] Additionally, when a third RRC reconfiguration message is received, the terminal device 130 can apply the new settings contained in the third RRC message and return an RRC reconfiguration complete message, including an SN RRC reconfiguration complete message. Additionally, the terminal device 130 stores the settings of multiple candidate PScells. Next, the terminal device begins evaluating the CPC execution conditions for the candidate PScells and selects the PScell ​​to be switched from among the multiple candidate PScells. After the target PScell ​​is selected, the terminal device 130 can determine that the conditions for executing the settings for the SCG PScell ​​are met.

[0132] Next, the terminal device 130 determines (310) whether the SCG of the second network device is deactivated. In some exemplary embodiments, if the SCG is deactivated before the conditions for performing the configuration of the SCG for the PScell ​​are met / the stored configuration for the target PScell ​​is applied, and the stored configuration for the target PScell ​​does not indicate (e.g., by instruction) that the SCG is activated, the terminal device 130 determines that the SCG is deactivated. In some other exemplary embodiments, if the stored configuration for the target PScell ​​indicates (e.g., by instruction) that the SCG is deactivated, the terminal device 130 determines that the SCG is deactivated.

[0133] For example, if the SCG is deactivated after the CPC settings are received from the first network device 110, and the stored settings do not indicate that the SCG is activated, the terminal device 130 determines that the SCG is deactivated. As another example, if the SCG is activated before the CPC execution is triggered, and the stored settings indicate that the SCG is deactivated, the terminal device 130 determines that the SCG is deactivated.

[0134] As described above, if terminal device 130 determines that SCG is deactivated, terminal device 130 sends a third message to the second network device 120 of SCG (320) indicating that the configuration for PScell ​​has already been completed by terminal device 130.

[0135] In some exemplary embodiments, terminal device 130 applies the SCG settings but does not initiate RA to the target PScell. In some exemplary embodiments, terminal device 130 sends an uplink message to the first network device 110 indicating information about the selected target PScell ​​(e.g., target PScell ​​ID) so that the first network device can know the selected target PScell. Additionally, MN may notify the second network device 120 of the selected target PScell ​​information by sending another message. In some embodiments, this information may be represented as an indication indicating the identification information of the target PScell.

[0136] In some exemplary embodiments, the uplink message includes an embedded RRC ReconfigurationComplete message for the SN and information about the selected target PScell. The embedded RRC ReconfigurationComplete message can be transmitted to the second network device 120. In some exemplary embodiments, the embedded RRC ReconfigurationComplete message and the information about the selected target PScell ​​can be transmitted independently of each other. In some other exemplary embodiments, the information about the selected target PScell ​​may be included in the embedded RRC ReconfigurationComplete message. Additionally, in some exemplary embodiments, the uplink message may include the RRCReconfigurationComplete message, the ULInformationTransferMRDC message, the UE Assistance information message, etc.

[0137] As an example, terminal device 130 sends a ULInformationTransferMRDC message to the first network device 110 that includes an embedded RRCReconfigurationComplete message from the second network device 120. Here, the embedded RRCReconfigurationComplete message includes the target PScell ​​ID.

[0138] As an example of sending a third message, terminal device 130 sends the third message to the first network device 110 so that the third message is sent to the second network device by the first network device. Additionally, terminal device 130 pauses transmission with the second network device to avoid the RA procedure for PScell.

[0139] Alternatively, in some other exemplary embodiments, terminal device 130 applies the SCG configuration but maintains at least the wake-up state of the PScell ​​or SCG. Terminal device 130 then sends a ULInformationTransferMRDC message to the first network device 110. The ULInformationTransferMRDC message includes an embedded RRCReconfigurationComplete message to the second network device 120. Furthermore, the first network device sends an SgNB modification confirmation message to the second network device 120. In addition, terminal device 130 initiates an RA to the target PScell ​​and puts the PScell ​​or SCG to sleep after the RA procedure is successfully completed.

[0140] As another example of sending a third message, terminal device 130 sends the third message to the first network device 110 so that the third message is sent to the second network device by the first network device. Additionally, terminal device 130 enables transmission with the second network device, executes an RA procedure for the target PScell ​​via the enabled transmission, and pauses transmission with the second network device upon completion of the RA procedure.

[0141] Thus, when SCG is deactivated, PScell ​​settings (e.g., additional PScell ​​changes) can be made during CPC or CPA procedures.

[0142] The second network device (i.e., SN) can send a message for a conditional PScell ​​change for a deactivated SCG to the terminal device 130 via SRB 3. Before describing the process relating to this disclosure, a general CPC mechanism via SRB 3 will first be described.

[0143] In a scenario where the SCG is activated, the second network device 120 (i.e., SN) sends an SN RRC reconfiguration message to the terminal device 130 via SRB 3. The terminal device 130 applies the new configuration and replies to the second network device 120 with an SN RRC reconfiguration complete message. If the terminal device 130 is unable to apply at least some of the configurations contained in the SN RRC reconfiguration message, the terminal device 130 executes a reconfiguration failure procedure. If instructed, the terminal device 130 synchronizes with the PScell ​​of the second network device 130, similar to the SN append procedure. Alternatively, the terminal device 130 may perform a UL transmission after the new configuration has already been applied. For a CPC scenario, the terminal device 130 maintains a connection with the source PScell ​​after receiving the CPC configuration and begins evaluating the CPC execution conditions for the candidate PScell. If at least one CPC candidate PScell ​​satisfies the corresponding CPC execution conditions, terminal device 130 separates from the source PScell, applies the corresponding settings stored for the selected candidate PScell, and synchronizes with the candidate PScell. Terminal device 130 completes the CPC execution procedure by sending an RRCReconfigurationComplete message to the second network device 120.

[0144] Therefore, when terminal device 130 receives an RRC Reconfiguration message for CPC configuration, it sends an RRC Reconfiguration complete message to SN. Furthermore, once the CPC execution conditions are met, terminal device 130 should send an RRC Reconfiguration Complete message to SN (directly or via MN) and initiate an RA procedure to the target PScell ​​so that network devices can become aware of the target PScell's information. However, if SCG is deactivated, SRB3 and RA to SN are not normally permitted. Additionally, if RA is not permitted, and there are multiple candidate PScells, network devices (e.g., the first network device 110 and the second network device 120) will not know which candidate PScell ​​has been selected.

[0145] The inventors of this disclosure have found that if the CPC settings are received before the SCG is deactivated, the terminal device 130 can continue to evaluate the CPC execution conditions for the candidate PScell ​​even though the SCG is subsequently deactivated. Furthermore, the inventors of this disclosure have also found that if the CPC settings are received after the SCG is deactivated, the terminal device 130 can still evaluate the CPC execution conditions for the candidate PScell. In addition, information about the target PScell ​​(e.g., identification information of the target PScell) can be shown in the RRC Reconfiguration Complete message. Thus, even if the terminal device 130 does not initiate the RA procedure to the target PScell, the network devices (e.g., the first network device 110 and the second network device 120) can know the information about the target PScell. This will be explained in more detail below.

[0146] Similarly, referring to Figure 3A, terminal device 130 receives a third RRC reset message from second network device 120 (308) for conditionally configuring the SCG's PScell. The third RRC reset message contains second information for multiple candidate PScells. Then, in response to the received third RRC reset message, terminal device 130 selects a PScell ​​to be switched from among the multiple candidate PScells and determines that the conditions for performing the configuration for the SCG's PScell ​​are met.

[0147] As an example, in a conditional PScell ​​change scenario within a SN where SRB3 is configured without a SN change, terminal device 130 receives a third RRC reconfiguration message from the second network device 120 to conditionally configure the PScell ​​of the SCG.

[0148] Additionally, when a third RRC reset message is received, terminal device 130 can apply the new settings contained in the third RRC message and send an SN RRC reset completion message to the second network device 120. Additionally, terminal device 130 stores the settings of multiple candidate PScells. Next, terminal device 130 begins evaluating the CPC execution conditions for the candidate PScells and selects the PScell ​​to be switched from among the multiple candidate PScells. After the target PScell ​​is selected, terminal device 130 can determine that the conditions for executing the settings for the SCG PScell ​​are met.

[0149] Next, the terminal device 130 determines whether the SCG of the second network device is deactivated (310). In some exemplary embodiments, if the SCG is deactivated before the conditions for performing the configuration of the SCG for the PScell ​​are met / the stored configuration for the target PScell ​​is applied, and the stored configuration for the target PScell ​​does not indicate (e.g., by instruction) that the SCG is activated, the terminal device 130 determines that the SCG is deactivated. In some exemplary embodiments, if the stored configuration for the target PScell ​​indicates (e.g., by instruction) that the SCG is deactivated, the terminal device 130 determines that the SCG is deactivated.

[0150] For example, if the SCG is deactivated after the CPC settings are received from the first network device 110, and the stored settings do not indicate that the SCG is activated, the terminal device 130 determines that the SCG is deactivated. As another example, if the SCG was activated before the CPC execution was triggered, but the stored settings indicate that the SCG is deactivated, the terminal device 130 determines that the SCG is deactivated.

[0151] As described above, if terminal device 130 determines that SCG is deactivated, terminal device 130 sends a third message to the second network device 120 of SCG (320) indicating that the configuration for PScell ​​has already been completed by terminal device 130.

[0152] In some exemplary embodiments, terminal device 130 applies stored settings but does not initiate RA to target PScell. In some exemplary embodiments, terminal device 130 sends an uplink message to first network device 110 indicating information about the selected target PScell ​​(e.g., target PScell ​​ID) so that the first network device can know the selected target PScell. Additionally, MN may notify the second network device 120 of the selected target PScell ​​information by sending another message. In some embodiments, this information may be represented as an indication indicating the identification information of the target PScell.

[0153] In some exemplary embodiments, the uplink message includes an embedded RRC ReconfigurationComplete message for the SN and information about the selected target PScell. The embedded RRC ReconfigurationComplete message can be transmitted to the second network device 120. In some exemplary embodiments, the embedded RRC ReconfigurationComplete message and the information about the selected target PScell ​​can be transmitted independently of each other. In some other exemplary embodiments, the information about the selected target PScell ​​may be included in the embedded RRC ReconfigurationComplete message. Additionally, in some exemplary embodiments, the uplink message may include the RRCReconfigurationComplete message, the ULInformationTransferMRDC message, the UE Assistance information message, etc.

[0154] As an example, terminal device 130 sends a ULInformationTransferMRDC message to the first network device 110 that includes an embedded RRCReconfigurationComplete message from the second network device 120. Here, the embedded RRCReconfigurationComplete message includes the target PScell ​​ID.

[0155] As an example of sending a third message, terminal device 130 sends the third message to the first network device 110 so that the third message is sent to the second network device by the first network device. Additionally, terminal device 130 pauses transmission with the second network device to avoid the random access (RA) procedure for PScell.

[0156] Alternatively, in some exemplary embodiments, terminal device 130 applies the SCG configuration but maintains at least the PScell ​​or SCG in a wake-up state. Terminal device 130 then activates SRB3 if necessary, initiates RA to the target PScell, and sends RRCReconfigurationComplete via SRB3 to the second network device 120 (if configured). Terminal device 130 then puts the PScell ​​or SCG to sleep and pauses SRB3 after successfully sending the RRC Reconfiguration Complete message.

[0157] As another example of sending a third message, terminal device 130 enables transmission with a second network device, sends the third message to the second network device via the enabled transmission, and pauses transmission with the second network device upon completion of transmission for a setup completion message. Additionally, terminal device 130 executes an RA procedure for the target PScell ​​via the enabled transmission before pausing the transmission.

[0158] In this way, when SCG is deactivated, PScell ​​settings (e.g., changes to PScell) can be made during the CPC procedure. Example process for configuring SCG without changing PSCELL

[0159] Figure 3B is a signaling diagram showing a process 350 for setting up an SCG without modifying a PScell, according to some embodiments of the present disclosure. For illustrative purposes, the process 350 will be described with reference to Figure 1. The process 350 may involve a terminal device 130, a first network device 110, and a second network device 120. For illustrative purposes, without limiting the scope of the present disclosure, in the process 350 of Figure 3B, the first network device 110 operates as an MN and the second network device 120 operates as an SN.

[0160] As shown in Figure 3B, terminal device 130 receives a fourth message (360) for configuring the SCG of the second network device. The fourth message includes a second instruction indicating that the SCG is deactivated. Next, terminal device 130 sends a fifth message (370) to the second network device of the SCG. The fifth message indicates that the configuration for the PScell ​​has already been completed by the terminal device.

[0161] As an example of sending a third message, terminal device 130 sends a fifth message to the first network device in order for the fifth message to be sent to the second network device via the first network device.

[0162] As another example of sending a third message, terminal device 130 enables transmission with a second network device, sends the third message to the second network device via the enabled transmission, and then pauses the enabled transmission with the second network device upon completion of the transmission for the setup completion message.

[0163] Thus, even if the SCG is deactivated, the terminal device 130 can configure the SCG. Example of avoiding SCG settings for a deactivated SCG.

[0164] In some exemplary embodiments, if the SCG is deactivated, the first network device 110 or the second network device 130 ensures that the SCG cannot perform any configuration for PScells (e.g., adding or modifying PScells). For example, if the SCG is deactivated, the first network device 110 or the second network device 120 does not send an RRC reconfiguration message with PScell ​​ReconfigurationWithSync to the terminal device 130.

[0165] In some exemplary embodiments, the PScell ​​ReconfigurationWithSync element and the SCG deactivation instruction are set to the UE within separate RRC messages. More specifically, the SCG deactivation procedure is executed after the procedure for the ReconfigurationWithSync element.

[0166] In some exemplary embodiments, if the CPC setting is received before the SCG is deactivated, the network device (e.g., the first network device 110 or the second network device 120) configures the terminal device 130 to release the CPC setting when the SCG is deactivated. Alternatively, if the SCG is deactivated, the terminal device 130 releases the CPC setting.

[0167] In some exemplary embodiments, after an RRC message is sent for CPC or CPA, the first network device 110 determines that the SCG is deactivated. The first network device 110 then instructs the terminal device 130 to release the stored settings for the candidate PScell.

[0168] In some exemplary embodiments, after an RRC message is sent for the CPC, the second network device 120 determines that the SCG is deactivated. The second network device 120 then instructs the terminal device 130 to release the stored settings for the candidate PScell.

[0169] In some exemplary embodiments, after RRC messages for CPC and CPA are received, and before the stored settings for the selected target PScell ​​are applied, the terminal device 130 determines that the SCG is deactivated. The terminal device 130 then deactivates the stored settings for the candidate PScell.

[0170] In some exemplary embodiments, the CPC / CPA setting does not include an SCG inactive instruction.

[0171] In this way, by restricting network settings or defining the behavior of terminal devices (for example, deleting / releasing stored CPC settings when the SCG is deactivated), SCG settings are avoided for deactivated SCGs.

[0172] Figure 4 is a flowchart of an exemplary method 400 according to some embodiments of the present disclosure. Method 400 can be implemented in the first terminal device 110 shown in Figure 1. Method 400 may include additional blocks not shown and / or some blocks shown may be omitted, and it should be understood that the scope of the present disclosure is not limited in this respect. For illustrative purposes, Method 400 will be described with reference to Figure 1 from the perspective of the first network device 110.

[0173] In block 410, the first network device 110 sends a request to the second network device 120 to configure an SCG associated with the second network device 120. This request includes first information relating to a first activity state of the SCG. In block 420, the first network device 110 receives a response to the request from the second network device 120. The response indicates the current activity state of the SCG. The current activity state is determined by the second network device 120 based on the first information.

[0174] In some exemplary embodiments, the first network device 110 sends an SN addition request containing first information in accordance with a decision that an SCG should be added. In some other exemplary embodiments, the first network device 110 sends an SN modification request containing first information in accordance with a decision that an SCG should be modified.

[0175] In some exemplary embodiments, the first activity state of the SCG is active or inactive.

[0176] Figure 5 is a flowchart of an exemplary method 500 according to some embodiments of the present disclosure. Method 500 can be implemented in the second terminal device 120 shown in Figure 1. Method 500 may include additional blocks not shown and / or some blocks shown may be omitted, and it should be understood that the scope of the present disclosure is not limited in this respect. For illustrative purposes, Method 500 will be described with reference to Figure 1 from the perspective of the second network device 120.

[0177] In block 510, the second network device 120 receives a request from the first network device 110 to configure an SCG associated with the second network device 120. This request includes first information relating to a first activity state of the SCG. In block 520, the second network device 120 determines the current activity state of the SCG based on the first information. In block 530, the second network device 120 transmits a response to the request to the first network device 110. The response indicates the current activity state of the SCG.

[0178] In some exemplary embodiments, the second network device 120 receives an SN addition request based on a decision that an SCG should be added. In some other embodiments, the second network device 120 receives an SN modification request based on a decision that an SCG should be modified.

[0179] In some exemplary embodiments, the first activity state of the SCG is active or inactive.

[0180] Figure 6 is a flowchart of an exemplary method 600 according to some embodiments of the present disclosure. Method 600 can be implemented in the first terminal device 110 shown in Figure 1. Method 600 may include additional blocks not shown and / or some blocks shown may be omitted, and it should be understood that the scope of the present disclosure is not limited in this respect. For illustrative purposes, Method 600 will be described with reference to Figure 1 from the viewpoint of the first network device 110.

[0181] In block 610, the first network device 110 receives a first message from the second network device 120 for setting up the SCG associated with the second network device 120. The first message includes parameters relating to the second activity state of the SCG. In block 620, the network device 110 sends a second message to the second network device 120 to confirm the first message.

[0182] The terminal device 130 is instructed to configure the SCG. The terminal device 130 is served by the first network device 110 and the second network device 120.

[0183] In some exemplary embodiments, the second activity state of the SCG is active or inactive.

[0184] Figure 7 is a flowchart of an exemplary method 700 according to some embodiments of the present disclosure. Method 700 can be implemented in the second terminal device 120 shown in Figure 1. Method 700 may include additional blocks not shown and / or some blocks shown may be omitted, and it should be understood that the scope of the present disclosure is not limited in this respect. For illustrative purposes, Method 700 will be described with reference to Figure 1 from the perspective of the second network device 120.

[0185] In block 710, the second network device 120 generates a first message for configuring the SCG associated with the second network device 120. The first message includes parameters relating to the second activity state of the SCG. In block 720, the second network device 120 transmits the first message to the first network device 110.

[0186] In some exemplary embodiments, the second activity state of the SCG is active or inactive.

[0187] Figure 8 is a flowchart of an exemplary method 800 according to some embodiments of the present disclosure. Method 800 can be performed in the terminal device 130 shown in Figure 1. Method 800 may include additional blocks not shown and / or some blocks shown may be omitted, and it should be understood that the scope of the present disclosure is not limited in this respect. For illustrative purposes, Method 800 will be described with reference to Figure 1 from the viewpoint of the terminal device 130.

[0188] In block 810, terminal device 130 determines whether the SCG of the second network device 120 is deactivated, based on the determination that the conditions for performing the configuration of the SCG for the PScell ​​of the second network device 120 are met. Terminal device 130 is served by the first network device 110. In block 820, terminal device 130 sends a third message to the second network device 120 of the SCG, based on the determination that the SCG is deactivated. The third message indicates that the configuration for the PScell ​​has already been completed by terminal device 130.

[0189] In some exemplary embodiments, terminal device 130 receives a first RRC reconfiguration message from first network device 110 for configuring the PScell ​​of the SCG. Terminal device 130 determines that the conditions for performing the configuration for the PScell ​​of the SCG are met.

[0190] In some exemplary embodiments, terminal device 130 sends a third message to the first network device 110 so that the third message may be sent to the second network device 120 via the first network device 110. Terminal device 130 further pauses transmission with the second network device 120 to avoid the RA procedure for PScell.

[0191] In some exemplary embodiments, terminal device 130 sends a third message to the first network device 110 so that the third message may be sent to the second network device 120 via the first network device 110. Terminal device 130 further enables transmission with the second network device 120, executes an RA procedure for the PScell ​​via the enabled transmission, and pauses transmission with the second network device 120 upon completion of the RA procedure.

[0192] In some exemplary embodiments, terminal device 130 receives a second RRC reset message from second network device 120 for configuring the PScell ​​of the SCG. The second RRC reset message includes a first instruction indicating that the SCG is deactivated. Terminal device 130 determines that the conditions for performing the configuration for the PScell ​​of the SCG are met.

[0193] In some exemplary embodiments, terminal device 130 sends a third message to the first network device 110 so that the third message may be sent to the second network device 120 via the first network device 110. Terminal device 130 further pauses transmission with the second network device 120 to avoid the RA procedure for PScell.

[0194] In some exemplary embodiments, terminal device 130 enables transmission with second network device 120, sends a third message to second network device 120 via the enabled transmission, and pauses the enabled transmission with second network device 120 upon completion of transmission for a setup completion message. Terminal device 130 further executes an RA procedure for PScell ​​via the enabled transmission before pausing the enabled transmission.

[0195] In some exemplary embodiments, terminal device 130 receives a third RRC reset message from the first network device 110 or the second network device 120 for conditionally configuring the PScell ​​of the SCG. The third RRC reset message includes second information on a plurality of candidate PScells. In response to the received third RRC reset message, terminal device 130 selects a PScell ​​to be switched from among the plurality of candidate PScells and determines that the conditions for performing configuration for the PScell ​​of the SCG are met.

[0196] In some exemplary embodiments, terminal device 130 sends a third message to the first network device 110 in response to the reception of a third RRC reset message from the first network device 110, so that the third message may be sent to the second network device 120 via the first network device 110. The third message indicates a target PScell. Terminal device 130 further pauses transmission with the second network device 120 to avoid the RA procedure for the PScell.

[0197] In some exemplary embodiments, terminal device 130, upon receiving a third RRC reset message from the first network device 110, sends a third message to the first network device 110 so that the third message may be sent to the second network device 120 by the first network device 110. Terminal device 130 further enables transmission with the second network device 120, executes an RA procedure for the target PScell ​​via the enabled transmission, and pauses transmission with the second network device 120 upon completion of the RA procedure.

[0198] In some exemplary embodiments, terminal device 130 sends a third message to the first network device 110 in response to receiving a third RRC reset message from the second network device 120, so that a third message indicating a target PScell ​​is sent to the second network device 120 by the first network device 110. Terminal device 130 pauses transmission with the second network device 120 in accordance with the received third RRC reset message to avoid the RA procedure for the PScell.

[0199] In some exemplary embodiments, terminal device 130 activates transmission with second network device 120 in response to receiving a third RRC reset message from second network device 120, sends the third message to second network device 120 via the activated transmission, and suspends transmission with second network device 120 upon completion of transmission for the setup completion message. Terminal device 130 further executes an RA procedure for the target PScell ​​via the activated transmission before suspending the transmission.

[0200] Figure 9 is a flowchart of an exemplary method 900 according to some embodiments of the present disclosure. Method 900 can be performed in the terminal device 130 shown in Figure 1. Method 900 may include additional blocks not shown and / or some blocks shown may be omitted, and it should be understood that the scope of the present disclosure is not limited in this respect. For illustrative purposes, Method 900 will be described with reference to Figure 1 from the viewpoint of the terminal device 130.

[0201] In block 910, terminal device 130 receives a fourth message from second network device 120 for configuring the SCG of the second network. The fourth message includes a second instruction indicating that the SCG is deactivated. In block 920, terminal device 130 sends a fifth message to the second network device of the SCG. The fifth message indicates that the configuration for the PScell ​​has already been completed by terminal device 130.

[0202] In some exemplary embodiments, terminal device 130 transmits a fifth message to the first network device 110 so that the fifth message may be transmitted to the second network device 120 via the first network device 110.

[0203] In some exemplary embodiments, the terminal device 130 enables transmission with the second network device 120, sends a fifth message to the second network device 120 via the enabled transmission, and pauses the enabled transmission with the second network device 120 upon completion of the transmission for the setup completion message.

[0204] Figure 10 is a schematic block diagram of a device 1000 suitable for implementing an embodiment of the present disclosure. Device 1000 can be considered as another exemplary embodiment of the terminal device 130, the second network device 120, or the first network device 110 shown in Figure 1. Thus, device 1000 can be implemented in or as part of the terminal device 130, the second network device 120, or the first network device 110.

[0205] As illustrated, the device 1000 comprises a processor 1010, a memory 1020 coupled to the processor 1010, appropriate transmitters (TX) and receivers (RX) 1040 coupled to the processor 1010, and a communication interface coupled to the TX / RX 1040. The memory 1010 stores at least a portion of the program 1030. The TX / RX 1040 is used for bidirectional communication. The TX / RX 1040 has at least one antenna to facilitate communication, although the access node referred to herein may actually have multiple antennas. The communication interface can represent any interface necessary for communication with other network elements, such as an X2 interface for bidirectional communication between eNBs, an S1 interface for communication between a mobility management entity (MME) / serving gateway (S-GW) and an eNB, an Un interface for communication between an eNB and a relay node (RN), or a Uu interface for communication between an eNB and a terminal device 130.

[0206] It is assumed that program 1030 includes program instructions that, when executed by the associated processor 1010 as described herein with reference to Figures 2A, 2B, 3, 6A, 6B, 7, 9, and 10, enable the device 1000 to operate according to embodiments of the present disclosure. Embodiments of the present can be implemented by computer software executable by the processor 1010 of the device 1000, by hardware, or by a combination of software and hardware. The processor 1010 can be configured to implement various embodiments of the present disclosure. Furthermore, a combination of the processor 1010 and memory 1010 can form a processing means 1050 suitable for implementing various embodiments of the present disclosure.

[0207] Memory 1010 may be of any type suitable for a local technology network and can be implemented using any suitable data storage technology, such as non-temporary computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. Although only one memory 1010 is shown in device 1000, several physically different memory modules may exist within device 1000. Processor 1010 may be of any type suitable for a local technology network and can include, as non-limiting examples, one or more of general-purpose computers, dedicated computers, microprocessors, digital signal processors (DSPs), and processors based on multicore processor architectures. Device 1000 may have multiple processors, for example, application-specific integrated circuit chips that are temporally dependent on a clock that synchronizes the main processor.

[0208] Overall, various embodiments of the Disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some embodiments may be implemented in hardware, while others may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Various embodiments of the Disclosure are illustrated and described using block diagrams, flowcharts, or any other pictorial representation, but it should be understood that the blocks, devices, systems, techniques, or methods described herein can be implemented, in non-limiting examples, in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or any combination thereof.

[0209] This disclosure also provides at least one computer program product tangibly stored on a non-temporary computer-readable storage medium. The computer program product includes computer-executable instructions, such as instructions contained in a program module, which are executed within a device on a real or virtual processor of interest to perform the processes or methods described above with reference to Figures 2A-2D, 3A, 3B, 4 to 9. Generally, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a specific task or implement a specific abstract data type. In various embodiments, the functions of program modules can be combined or separated from program modules as needed. The machine-executable instructions of a program module can be executed within a local or distributed device. In a distributed device, the program module may reside in both local and remote storage media.

[0210] Program code for performing the methods of this disclosure can be written in any combination of one or more programming languages. These program codes are provided to a processor or controller of a general-purpose computer, a dedicated computer, or other programmable data processing device, and when executed by the processor or controller, the program code implements the functions / operations specified in the flowcharts and / or block diagrams. The program code can run entirely on a machine, partially on a machine, as an independent software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0211] The program code described above may be implemented on a machine-readable medium, which may be any tangible medium that can contain or store programs used by or associated with an instruction execution system, device, or apparatus. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or apparatus, or any suitable combination of the aforementioned mediums. More specific examples of machine-readable storage media may include electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable optical disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above.

[0212] While the operations have been described in a specific order, it should not be understood that, in order to obtain the desired results, these operations must be performed in the specific order shown, or in a sequential order, or that all of the described operations must be performed. In some cases, multitasking or parallel processing may be advantageous. Similarly, while some specific implementation details are included in the above discussion, these should not be interpreted as limitations on the scope of this disclosure, but rather as descriptions of features that may be specific to a particular embodiment. Some features described in the context of individual embodiments may be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may be implemented separately or in any suitable subcombination in multiple embodiments.

[0213] While this disclosure has been described in language specific to structural features and / or methodological behavior, it should be understood that the disclosure as defined in the attached claims is not necessarily limited to the specific features or behaviors described above. Rather, the specific features and behaviors described above are disclosed as exemplary forms of implementing the claims.

Claims

1. Receiving a Radio Resource Control (RRC) reconfiguration message from a network device to conditionally configure the PScell ​​of a secondary cell group (SCG), Select the target PScell ​​to be switched from among multiple candidate PScells, Sending an uplink message to the network device containing information indicating the selected target PScell, Applying the SCG settings without initiating random access, Includes, The RRC reset message includes information on the multiple candidate PScells, Communication method.

2. A terminal device, A receiving means for receiving a radio resource control (RRC) reconfiguration message from a network device for conditionally configuring the PScell ​​of a secondary cell group (SCG), A selection method for selecting the target PScell ​​to be switched from among multiple candidate PScells, A transmission means for transmitting an uplink message containing information indicating the selected target PScell ​​to the network device, An application means that applies the settings of the SCG without initiating random access, Equipped with, The RRC reset message includes information on the multiple candidate PScells, Terminal device.

3. Network device, A transmission means for sending a radio resource control (RRC) reset message to a terminal device for conditionally configuring the PScell ​​of a secondary cell group (SCG), Receiving means for receiving an uplink message from the terminal device containing information indicating the target PScell, Equipped with, The RRC reset message includes information on multiple candidate PScells, The terminal device applies the settings of the SCG without initiating random access. Network device.

4. Sending a Radio Resource Control (RRC) reset message to a terminal device to conditionally configure the PScell ​​of a secondary cell group (SCG), Receiving an uplink message from the terminal device containing information indicating the target PScell, Includes, The RRC reset message includes information on multiple candidate PScells, The terminal device applies the settings of the SCG without initiating random access. Communication method.

Images