Communication method, terminal device, and network device
By exchanging activity status information, network devices and terminal devices can efficiently manage SCG states, addressing high power consumption in dual connectivity scenarios and optimizing battery life.
Patent Information
- Application Number
- JP2024139391
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-08-21
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2040-07-28
AI Technical Summary
In dual connectivity scenarios, the power consumption of terminal devices is significantly higher due to the need to maintain simultaneous radio links with both the master and secondary network devices, and the process of configuring a suspended or deactivated secondary cell group (SCG) is not well-defined, leading to inefficiencies.
Network devices and terminal devices exchange activity status information to determine and manage the configuration of SCGs, allowing for efficient activation or deactivation of SCGs based on current activity states, thereby optimizing power consumption.
This approach reduces power consumption by enabling intelligent management of SCG states, improving battery life in dual connectivity scenarios without compromising communication efficiency.
Smart Images

Figure 2024161553000001_ABST
Abstract
Description
[Technical field]
[0001] TECHNICAL FIELD Embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly to a communication method, a network device, a terminal device, and a computer-readable medium. [Background technology]
[0002] Dual Connectivity (DC) is an operation mode in which a terminal device (e.g., user equipment, UE) can be configured to utilize radio resources provided by two network devices, e.g., two base stations (BSs). 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 usually 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 the master cell group (MCG), and the serving cell group associated with the SN is called the secondary cell group (SCG).
[0003] In the DC scenario, the terminal device needs to simultaneously maintain radio links with the MN and the SN, which leads to significant power consumption. For example, the power consumption of a DC terminal device is several times that of a conventional terminal device, for example, three to four times that of a Long Term Evolution (LTE) terminal device. Furthermore, 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 or set the SCG serving the terminal device to a dormant state in order to reduce power consumption. However, when the SCG is suspended / deactivated, the process of the DC procedure, especially the procedure for setting the SCG, has not yet been specified. Summary of the Invention [Problem to be solved by the invention]
[0004] Overall, the exemplary embodiments of the present disclosure provide a solution for configuring an SCG when the SCG is suspended / deactivated. [Means for solving the problem]
[0005] In a first aspect, a communication method is provided. The method includes sending, at a first network device, a request to a second network device to configure an SCG associated with the second network device. The request includes first information regarding a first activity state for an SCG. The method further includes receiving a response to the request from the second network device. The response indicates a 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 aspect, a communication method is provided. The method includes receiving, at a second network device, a request from a first network device to configure an SCG associated with the second network device. The request includes first information regarding a first activity state of the SCG. The method further includes determining a current activity state of the SCG based on the first information. The method further includes sending a response to the request to the first network device. The response indicates the current activity state of the SCG.
[0007] In a third aspect, a method of communication is provided. The method includes receiving, at a first network device, from a second network device, a first request to configure an SCG associated with the second network device. The first message includes requirements regarding a second activity state of the SCG. The method further includes sending a second message to the second network device to confirm the first message.
[0008] In a fourth aspect, a method of communication is provided. The method includes generating, at a second network device, a first message for configuring an SCG associated with the second network device. The first message includes parameters related to a second activity state of the SCG. The method further includes transmitting the first message to the first network device.
[0009] In a fifth aspect, a communication method is provided. The method includes determining, in a terminal device served by a first network device, whether an SCG of a second network device is deactivated in accordance with determining that a condition for performing configuration for a primary secondary cell (PScell) of the SCG of the second network device is satisfied. The method further includes transmitting a third message to the second network device of the SCG in response to determining that the SCG is deactivated. The third message indicates that configuration for the PScell has already been completed by the terminal device.
[0010] In a sixth aspect, a communication method is provided. The method includes receiving, at a terminal device, from a second network device, a fourth message for configuring an SCG of the second network. The fourth message includes a second indication indicating that the SCG is deactivated. The method further includes transmitting a fifth message to the second network device of the SCG. The fifth message indicates that configuration for a PScell has already been completed by the terminal device.
[0011] In a seventh aspect, there is provided a network device comprising a processing unit and a memory coupled to the processing unit and having instructions stored thereon that, when executed by the processing unit, cause the device to perform a method according to the first aspect.
[0012] In an eighth aspect there is provided a network device comprising a processing unit and a memory coupled to the processing unit and having instructions stored thereon which, when executed by the processing unit, cause the device to perform a method according to the second aspect.
[0013] In a ninth aspect there is provided a network device comprising a processing unit and a memory coupled to the processing unit and having instructions stored thereon which, when executed by the processing unit, cause the device to perform a method according to the third aspect.
[0014] In a tenth aspect there is provided a network device comprising a processing unit and a memory coupled to the processing unit and having instructions stored thereon which, when executed by the processing unit, cause the device to perform a method according to the fourth aspect.
[0015] In an eleventh aspect, there is provided a terminal device, the terminal device comprising a processing unit and a memory coupled to the processing unit and having instructions stored thereon, the instructions, when executed by the processing unit, causing the device to perform a method according to the fifth aspect.
[0016] In a twelfth aspect, there is provided a terminal device, the terminal device comprising a processing unit and a memory coupled to the processing unit and having instructions stored thereon, the instructions, when executed by the processing unit, causing the device to perform a method according to the sixth aspect.
[0017] In a thirteenth aspect, a computer readable medium is provided having instructions stored thereon which, when executed on at least one processor, cause the at least one processor to perform a method according to the first aspect.
[0018] In a fourteenth aspect, a computer readable medium is provided having instructions stored thereon which, when executed on at least one processor, cause the at least one processor to perform a method according to the second aspect.
[0019] In a fifteenth aspect, a computer readable medium is provided having instructions stored thereon which, when executed on at least one processor, cause the at least one processor to perform a method according to the third aspect.
[0020] In a sixteenth aspect, a computer readable medium is provided having instructions stored thereon which, when executed on at least one processor, cause the at least one processor to perform a method according to the fourth aspect.
[0021] In a seventeenth aspect, a computer readable medium is provided having instructions stored thereon which, when executed on at least one processor, cause the at least one processor to perform a method according to the fifth aspect.
[0022] In an eighteenth aspect, there is provided a computer readable medium having instructions stored thereon which, when executed on at least one processor, cause the at least one processor to perform a method according to the sixth aspect.
[0023] It should be understood that this summary is not intended to identify key or essential features of the embodiments of the present disclosure, nor to limit the scope of the present disclosure. Other features of the present disclosure will be readily apparent from the following description. [Brief description of the drawings]
[0024] The above and other objects, features and advantages of the present disclosure will become more apparent from the following detailed description of several embodiments of the present disclosure in the drawings.
[0025] [Figure 1] FIG. 1 is a block diagram of a communication environment in which embodiments of the present disclosure can be implemented.
[0026] [Figure 2A] FIG. 2 is a signaling diagram illustrating a process for exchanging activity state information in accordance with some embodiments of the present disclosure. [Figure 2B] FIG. 2 is a signaling diagram illustrating a process for exchanging activity state information in accordance with some embodiments of the present disclosure. [Figure 2C] FIG. 2 is a signaling diagram illustrating a process for exchanging activity state information in accordance with some embodiments of the present disclosure. [Figure 2D] FIG. 2 is a signaling diagram illustrating a process for exchanging activity state information in accordance with some embodiments of the present disclosure.
[0027] [Figure 3A]FIG. 1 is a signaling diagram illustrating a process for configuring an SCG in accordance with some embodiments of the present disclosure. [Figure 3B] FIG. 1 is a signaling diagram illustrating a process for configuring an SCG in accordance with some embodiments of the present disclosure.
[0028] [Figure 4] A diagram illustrating an example communication method implemented in a first network device in accordance with some embodiments of the present disclosure.
[0029] [Diagram 5] A diagram illustrating an example communication method implemented in a second network device in accordance with some embodiments of the present disclosure.
[0030] [Figure 6] A diagram showing another exemplary communication method implemented in a first network device in accordance with some embodiments of the present disclosure.
[0031] [Figure 7] A diagram showing another exemplary communication method implemented in a second network device in accordance with some embodiments of the present disclosure.
[0032] [Figure 8] FIG. 2 illustrates an exemplary communication method implemented in a terminal device according to some embodiments of the present disclosure.
[0033] [Figure 9] FIG. 1 illustrates another exemplary communication method implemented in a terminal device in accordance with some embodiments of the present disclosure.
[0034] [Figure 10] FIG. 1 is a schematic block diagram of an apparatus suitable for implementing embodiments of the present disclosure.
[0035] In the drawings, the same or similar reference numbers represent the same or similar elements. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0036] The principles of the present disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are set forth for illustrative purposes only, to assist those skilled in the art in understanding and implementing the present disclosure, and do not imply any limitations on the scope of the present disclosure. The disclosure described herein can be implemented in various ways different from the methods described below.
[0037] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.
[0038] References in this disclosure to "one embodiment," "an embodiment," "an exemplary embodiment," and the like indicate that the described embodiment may include a particular feature, structure, or characteristic, but each embodiment does not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is believed to be within the knowledge of one of ordinary skill in the art to affect such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.
[0039] The terms used herein are used only for the purpose of describing particular embodiments and are not intended to limit the exemplary embodiments. As used herein, the singular forms "a," "an," and "said" include the plural forms unless the context clearly indicates otherwise. It should be further understood that, as used herein, the terms "comprise," "include," "have," "comprise," "comprises," and / or "have" specify the presence of stated features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.
[0040] It should be understood that although the terms "first" and "second" etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may be named a second element, and similarly, a second element may be named a first element, without departing from the scope of the exemplary embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.
[0041] In some instances, values, procedures, or devices are referred to as "best," "lowest," "highest," "minimum," "maximum," etc. Such descriptions are intended to illustrate that selections can be made from among many functional alternatives used, and it should be understood that such selections are not necessarily better, smaller, higher, or otherwise more preferred than other selections.
[0042] The term "network device" as used herein means a device capable of providing or hosting a cell or coverage in which a terminal device can communicate. Examples of network devices include, but are not limited to, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), a Node B for New Radio Access (gNB), a Remote Radio Unit (RRU), a Radio Head (RH), a Remote Radio Head (RRH), a low power node such as a femto node or a pico node, a satellite network device, an aircraft network device, etc. For the sake of explanation, some exemplary embodiments will be described below with reference to an eNB as an example of a network device.
[0043] As used herein, the term "terminal" refers to any end device capable of wireless communication. By way of example and not limitation, a terminal may be referred to as a communication device, a user equipment (UE), a subscriber station (SS), a portable subscriber station (Portable Subscriber Station), a mobile station (MS), or an access terminal (AT). The terminal device may include, but is not limited to, a mobile phone, a cellular phone, a smartphone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet, a wearable terminal device, a personal digital assistant (PDA), a portable computer, a desktop computer, an imaging terminal device such as a digital camera, a gaming terminal device, a music storage and playback device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop embedded device (LEE), a laptop mounted device (LME), a USB dongle, a smart device, a wireless customer premises equipment (CPE), an Internet of Things (loT) device, a watch or other wearable device, a head mounted display (HMD), a vehicle, a drone, a medical device and application (e.g., remote surgery), an industrial device and application (e.g., a robot and / or other wireless device operating in an industrial and / or automated processing chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.
[0044] As used herein, the term "waking up" / "wake up" or similar expressions means an operation of enabling transmission with another device. In particular, an operation of waking up an SCG or a PScell can mean activating all serving cells of the SCG or activating a PScell of the SCG. Additionally, an operation of waking up an SCG or a PScell can mean switching all serving cells of the SCG from a dormant BWP to a non-dormant BWP or switching a PScell of the SCG from a dormant BWP to a non-dormant BWP. It should be understood that the concept of waking up is suitable for any one or more devices / elements / modules.
[0045] As used herein, the term "sleeping" / "sleep" or similar expressions refers to an operation of disabling / suspending transmission with another device. In particular, an operation of sleeping an SCG or a PScell may mean deactivating all serving cells of the SCG or deactivating a PScell of the SCG. It should be understood that an operation of sleeping an SCG or a PScell may also mean switching an SCG to a dormant BWP or switching a PScell of the SCG to a dormant BWP. It should be understood that the concept of sleeping is suitable for any one or more devices / elements / modules.
[0046] In one embodiment, the terminal device may be connected to a first network device and a second network device. One of the first network device and the second network device may be a master node and the other may be a secondary node. The first network device and the second network device 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 the different RATs may be transmitted from at least one of the first network device and the second network device to the terminal device. 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 to the terminal device directly or via the first network device. In one embodiment, information about the configuration of the terminal device configured by the second network device may be transmitted from the second network device via the first network device. Information regarding the reconfiguration of the terminal device configured by the second network device can be transmitted to the terminal device directly from the second network device or via the first network device.
[0047] The communication discussed herein may use communication conforming to any suitable standard, including but not limited to New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), and the like. Furthermore, the communication between the first device and the fourth device in the communication network may be realized according to any suitable generation of communication protocols, 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) communication protocols, and / or any other protocols now known or developed in the future. The embodiments of the present disclosure may be applied to various communication systems. In view of the rapid development of communication, there will naturally be future types of communication technologies and systems in which the present disclosure may be embodied. This should not be considered as limiting the scope of the present disclosure to only the aforementioned systems.
[0048] While the functions described herein may be performed in fixed and / or wireless network nodes in various exemplary embodiments, in other exemplary embodiments, the functions may be realized in user equipment equipment (e.g., a mobile phone, a tablet computer, a laptop computer, a desktop computer, a mobile IoT device, or a fixed IoT device). For example, the user equipment equipment may include corresponding capabilities described in connection with the fixed and / or wireless network nodes, as appropriate. The user equipment equipment may be a user equipment and / or a control device, such as a chipset or processor, configured to control the user equipment when installed within the user equipment. Examples of such functions include a bootstrap server function and / or a home subscriber server, which may be implemented within the user equipment equipment by providing the user equipment equipment with software configured to cause the user equipment equipment to perform from the perspective of these functions / nodes.
[0049] As mentioned above, in the DC scenario, CA technology can be implemented to efficiently use frequencies. However, the introduction of CA technology usually causes power consumption of a terminal device (e.g., UE).
[0050] One conventional power saving solution for CA scenarios involves activation / deactivation of the SCell. In order to enable reasonable power consumption (e.g., battery consumption) of the terminal device when configuring CA, an activation / deactivation mechanism of the SCell is supported. When an SCell is deactivated, the terminal device does not need to receive the corresponding PDCCH or PDSCH and cannot transmit in the corresponding uplink, but is required to perform a channel quality indicator (CQI) measurement. Conversely, when an SCell is activated, the terminal device receives the PDSCH and PDCCH (if the terminal device is configured to monitor the PDCCH from the SCell) and it is expected that the terminal device can perform a CQI measurement.
[0051] Another conventional power saving solution for CA scenarios includes SCell dormancy. To enable fast SCell activation when CA is configured, one dormant bandwidth part (BWP) can be configured on the SCell. If the active BWP of the activated SCell is a dormant BWP, the terminal device stops monitoring the PDCCH on the SCell but continues to perform channel state information (CSI) (e.g., CQI) measurements, automatic gain control (AGC) and beam management, if configured. Downlink control information (DCI) is used to control entry / exit into the dormant BWP for one or more SCells or one or more SCGs. The dormant BWP is one of the dedicated BWPs of the UE that is configured by the network via dedicated radio resource control (RRC) signaling. Dormant BWPs cannot be configured on special cell (SpCell) and PUCCH SCells.
[0052] As mentioned above, in the DC scenario, the power consumption of the terminal and the network is also a big problem because two radio links are maintained simultaneously. Taking EN-DC as an example, in some cases, the power consumption of the terminal in the NR network is three to four times higher than that of the terminal in the LTE network. It was proposed that the SCG may be suspended / deactivated or may be set to a dormant state in some cases to reduce the power consumption. For example, in an EN-DC deployment, the MN provides basic coverage. If the data rate requirement of the UE changes dynamically, for example from high to low, the SN may be deactivated or suspended to reduce the power consumption.
[0053] It should be understood that the SCG deactivation mechanism is also necessary for other MR-DC deployments, including but not limited to EN-DC, NGEN-DC, NR-DC, etc. The terms "SCG pause" and "SCG deactivate" are used interchangeably herein.
[0054] Additionally, three options for modelling SCG suspension have already been proposed below. In option 1, activate all serving cells associated with the SN, including PScells and SCells, and set the active BWPs as dormant BWPs. In option 2, all serving cells associated with the SN, including PScell and Scell, are deactivated. In option 3, the SCells of the SCG should be deactivated, but the PScells of the SCG should be activated, and the active BWP is 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 PScell, adding / modifying / changing SN, 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 message, etc.). However, it is not described how to handle the above interactions when the SCG is suspended / deactivated.
[0056] According to some exemplary embodiments of the present disclosure, a solution is proposed for configuring an SCG when the SCG is suspended / deactivated. In this solution, network devices (e.g., MN and SN) can exchange activity state (e.g., active or inactive) information. More specifically, a first network device (e.g., MN) can send a request including first information regarding a first activity state of an SCG for configuring an SCG associated with a second network device (e.g., SN). The second network device can then respond to the first network device with its current activity state (i.e., its actual activity state). Alternatively, the second network device can generate a first message including parameters regarding a second activity state of an SCG for configuring an SCG associated with the second network device. The second network device can then send the generated first message to the first network device. In this way, the first network device can obtain the current / actual activity state of the second network device.
[0057] According to some other exemplary embodiments of the present disclosure, another solution is proposed for configuring the SCG when the SCG is suspended / deactivated. In this solution, when the terminal device determines that the conditions for performing the configuration for the PScell of the SCG 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, when the terminal device receives a fourth message from the second network device for configuring the SCG of the second network, the fourth message including a second indication indicating that the SCG is deactivated, the terminal device can 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. In this way, the configuration for the SCG can be performed even if the SCG is deactivated.
[0058] A more detailed explanation will now be given with reference to FIGS. Example environment
[0059] 1 illustrates an exemplary communication environment 100 in which exemplary embodiments of the present disclosure may be implemented. In the communication environment 100, a terminal device 130 may communicate with a first network device 110, which may further communicate with a second network device 120. The first network device 110 may communicate with the second network device 120 (e.g., via an X2 or Xn interface).
[0060] In the example of FIG. 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 FIG. 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 called an 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 called an SCG 160, and the primary cell 160-1 is also called a PScell 160-1.
[0061] The communications between the terminal device 130 and the first network device 110 and between the terminal device 130 and the second network device 120 may be realized according to any suitable communications protocol. Communications in the direction from the terminal device 130 to the first network device 110 or the second network device 120 are referred to as UL communications, and communications in the direction from the first network device 110 or the second network device 120 to the terminal device 130 are referred to as DL communications. The terminal device 130 may 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 may transmit UL data and control information over a UL channel. In some example embodiments, the UL data may be transmitted on a physical uplink shared channel (PUSCH) and / or any other available UL channel used for data transmission. In DL transmission, first network device 110 or second network device 120 may transmit DL data and control information to terminal device 130 over a DL channel. In some examples, the DL data may be transmitted on a physical downlink shared channel (PDSCH) and / or any other available DL channel used for data transmission.
[0063] The DC provided by the first network device 110 and the second network device 120 may include any suitable type of multi-radio dual connectivity (MR-DC), including but not limited to E-UTRA (Evolved Universal Terrestrial Radio Access)-NR dual connectivity (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 the network devices 110 and 120 are gNBs.
[0064] It should be understood that the number of SCells in FIG. 1 is given for illustrative purposes and does not imply any limitation to the present disclosure. In some alternative embodiments, the first network device 110 and the second network device 120 may provide any suitable number of SCells for serving the terminal device 130.
[0065] It should be understood that the number and types of devices in FIG. 1 are provided for illustrative purposes and do not imply any limitations to the present disclosure. The communication environment 100 may include any suitable number of network devices and / or terminal devices suitable for implementing embodiments of the present disclosure. Furthermore, the communication environment 100 may include any other devices (e.g., core network elements) other than the network devices and terminal devices, which are omitted herein to avoid obscuring the present invention. Example of a procedure for exchanging activity status information
[0066] The inventors of the present disclosure have noticed that there are cases where the deactivation state is acceptable for the SGC, for example, the SCG is overloaded or the SCG does not support the SCG activation setting. Therefore, the MN needs to know the actual / current activity state of the SCG so that the MN can perform reasonable subsequent processing based on the actual / current activity state of the SCG. Some exemplary embodiments of the present disclosure are described in detail below.
[0067] 2A is a signaling diagram illustrating a process 200 for exchanging activity state information according to some embodiments of the present disclosure. For illustrative purposes, the process 200 is described with reference to FIG. 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 FIG. 2A, a configuration procedure for an SCG is initiated by the first network device 110 acting as a MN.
[0068] A first network device 110 sends (202) a request to configure an SCG associated with a second network device 120. The request may include first information regarding a first activity state of the SCG. The request may be sent over an X2 or Xn interface.
[0069] In some exemplary embodiments, the first network device 110 transmits an SN addition request including the first information in accordance with the determination that an SCG should be added, for example, the first network device 110 transmits an SN addition request with an SCG activation / deactivation request indication to the second network device 120.
[0070] Alternatively, in some exemplary embodiments, the first network device 110 transmits an SN modification request including the first information in accordance with the determination that the SCG should be modified, for example, the first network device 110 transmits an SN modification request with an SCG activation / deactivation request indication to the second network device 120.
[0071] It should be appreciated that the above-mentioned messages are provided for illustrative purposes only, and no limitation is implied. In other example embodiments, the request may be any suitable message over an X2 or Xn interface. It should also be appreciated that the first information regarding the first active state of the SCG may be represented in any suitable manner, such as an indication, a field, a header, etc. Furthermore, the first information regarding the first active state of the SCG may be represented explicitly or implicitly. The scope of the present disclosure is not limited in these respects.
[0072] Upon receiving the request from the first network device 110, the second network device 120 can configure the SCG according to the request. Furthermore, the second network device 120 can configure the active state according to the first information included in the request. In some cases, the deactivation setting for the SCG may fail, for example, when the SCG of the second network device 120 is performing transmission (including data or signaling) with the terminal device 130, or when the SCG does not support the SCG deactivation setting. In some other cases, the activation setting for the SCG may fail when the second network device 120 is overloaded / busy (i.e., cannot provide further services). It should be understood that the above-mentioned examples of failure settings are given merely for illustrative purposes and do not imply any limitation to the present disclosure.
[0073] The second network device 120 then determines the current activity state of the SCG, and then sends (204) a response to the request to the first network device 110, 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 the SN addition request acknowledgment with an SCG activate / deactivate indication to the first network device 110.
[0075] Alternatively, in some exemplary embodiments, the second network device 120 sends an SN modification request acknowledgment in response to the SN modification request, e.g., the second network device 120 sends the SN modification request acknowledgment with an SCG activate / deactivate indication to the first network device 110.
[0076] It should be appreciated that the above-mentioned messages are provided for illustrative purposes only, and no limitation is implied. In other example embodiments, the request may be any suitable message over an X2 or Xn interface. It should be appreciated that the second network device may indicate the determined current activity state, either explicitly or implicitly. Furthermore, the current activity state may be represented in any suitable manner, such as an indication, a field, a header, etc. The scope of the present 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 the actual / current state (active / inactive) of the SCG. Furthermore, the actual / current state (active / inactive) of the SCG can be provided by the second network device 120 (i.e., SN). Based on the actual / current state (active / inactive) of the SCG, the first network device 110 can perform reasonable follow-up processing based on the actual active state of the SCG. For example, the first network device 110 decides whether to set the SCG to the terminal device 130 or change to another SN.
[0078] 2A, the first network device 110 transmits (206) an RRC message to the terminal device. 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 (e.g., an indication that the SCG of the second network device 120 is deactivated). Thus, the terminal device 130 may transmit (208) an RRC response to the first network device 110. 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. The first network device 110 may then transmit (210) a message to the second network device 120 to complete the configuration of the SCG.
[0079] For purposes of illustration, and without limiting the scope of the present disclosure, the first network device 110 may send an RRCReconfiguration message to the terminal device 130. The terminal device 130 responds with an RRCReconfigurationComplete carrying an SN RRCReconfigurationComplete message. The first network device 110 then sends an SN ReconfigurationComplete carrying the SN RRCReconfigurationComplete message to the second network device 120.
[0080] It should be understood that activity state may be exchanged during an SN change procedure between a source SN and a target SN. These procedures are described with reference to Figures 2B and 2C. Figure 2B is a signaling diagram showing a process 240 of exchanging activity state information during an SN change procedure between a source SN and a target SN initiated by a first network device 110 (i.e., MN). Figure 2C is a signaling diagram showing a process 260 of exchanging activity state information during an SN change procedure between a source SN and a target SN initiated by a second network device 120 (i.e., SN). For illustrative purposes, the processes 240 and 260 are described with reference to Figure 1. The processes 240 and 260 relate to the terminal device 130, the first network device 110, and the second network devices 120-1 and 120-2. In the process 240 of FIG. 2B and the process 260 of FIG. 2C, the first network device 110 acts as a MN, the second network device 120-1 acts as a source SN, and the second network device 120-2 acts as a target SN.
[0081] 2B, the first network device 110 (i.e., MN) sends (202) a request to set up an SCG associated with the second network device 120-2 (i.e., target SN). The request may include first information regarding a first active state of the SCG of the second network device 120-2. As an example, the first network device 110 sends an SN addition request with an SCG activation / deactivation request indication.
[0082] The second network device 120-2 may then configure the SCG according to the request received at 202. The second network device 120-2 then determines a current activity state of the SCG. The second network device 120-2 sends (204) a response to the first network device 110, the response indicating the determined current activity state of the SCG. For example, the second network device 120-2 sends an SN addition request acknowledgement response with an SCG activate / deactivate indication to the first network device 110.
[0083] Upon receiving the response from the second network device 120-2, the first network device 110 releases its connection with the second network device 120-1 (i.e., the source SN). More specifically, the first network device 110 sends (242) an SN Release request to the second network device 120-1 and receives (244) an SN Release request acknowledgment response from the second network device 120-1.
[0084] The first network device 110 then triggers the terminal device 130 to complete the corresponding configuration. More specifically, the first network device 110 sends (246) an RRCReconfiguration message to the terminal device 130 and receives (248) an RRCReconfigurationComplete carrying an SN RRCReconfigurationComplete message from the terminal device 130. The first network device 110 sends (250) an SN ReconfigurationComplete carrying the SN RRCReconfigurationComplete message to the second network device 120-1.
[0085] Thus, an active state exchange is achieved during the SN change procedure between the source SN and the target SN.
[0086] Now referring to FIG. 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 (262) an SN change request to the first network device 110. Upon receiving the SN change request, the first network device 110 sends (202) a request to configure an SCG associated with the second network device 120. The request may include first information regarding a first active state of said SCG. As an example, the first network device 110 sends an SN addition request with an SCG activation / deactivation request indication.
[0087] The second network device 120-2 may then configure the SCG according to the request received at 202. The second network device 120-2 then determines a current activity state of the SCG. The second network device 120-2 sends (204) a response to the first network device 110, the response indicating the determined current activity state of the SCG. For example, the second network device 120-2 sends an SN addition request acknowledgement response with an SCG activate / deactivate indication to the first network device 110.
[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 (264) an RRCReconfiguration message to the terminal device 130 and receives (266) an RRCReconfigurationComplete from the terminal device 130 carrying a SN RRCReconfigurationComplete message.
[0089] Next, each of the first network devices 110 sends (268) a SN Change Confirmation to the second network device 120-1 and a SN Reconfiguration complete message carrying the SN RRC Reconfiguration complete message to the second network device 120-2.
[0090] Thus, an active state exchange is achieved during the SN change procedure between the source SN and the target SN.
[0091] An illustrative process for exchanging activity state during a SN change procedure between a source SN and a target SN has already been described with reference to Figures 2B and 2C. When discussing the process of 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, the messages can be replaced with any suitable messages and executed in any suitable order.
[0092] 2D is a signaling diagram illustrating a process 280 for exchanging activity state information according to some embodiments of the present disclosure. For illustrative purposes, the process 280 is described with reference to FIG. 1. The process 280 may involve the terminal device 130, the first network device 110, and the second network device 120. In the process 280 of FIG. 2D, a configuration procedure for the SCG is initiated by the second network device 120 acting as an SN.
[0093] The second network device 120 generates a first message including parameters related to a second activity state of the SCG for configuring an SCG associated with the second network device 120. The second network device 120 then transmits (282) the first message to the first network device 110. For purposes of illustration, and without limiting the scope of the present disclosure, the second network device 120 transmits an SN modification for which an SCG active / inactive indication is desired.
[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 message indicating that the configuration requested by the first message has been fully performed, the second network device 120 determines that the first message was rejected by the first network device 110 or the terminal device 130, or that the configuration requested by the second network device failed to be configured by the first network device 110 or the terminal device 130.
[0095] The first network device 110 can then determine whether the configuration in the first message is acceptable. If the first network device 110 determines to accept the configuration in the first message, the first network device 110 sends (284) an RRC Reconfiguration to the terminal device 130 and receives (286) an RRC Reconfiguration complete carrying the SN RRC Reconfiguration Complete from the terminal device 130. The first network device 110 then sends (288) an SN Modification Confirmation carrying the SN RRC Reconfiguration Complete to the second network device 120.
[0096] Alternatively, if the first network device 110 rejects the setting of the first message, the first network device 110 responds (283) with a second message additionally carrying the reason for the rejection, or the first network device 110 simply ignores the first message and does not respond with any message to the second network device 120.
[0097] Additionally, if the first network device 110 determines that the settings required by the second network device have failed to be configured by the first network device 110 or the terminal device 130 (e.g., if the first network device 110 does not receive a message from the terminal device 130 indicating that the settings have been fully performed, or if the first network device 110 receives a message from the terminal device 130 indicating that the settings have failed), the first network device 110 responds (283) with a second message indicating the failure, additionally carrying 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] In describing the process of 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 example embodiments, the messages can be replaced with any suitable messages and executed in any suitable order.
[0099] In this way, when the SN initiates the SCG setup, the SN can ask for the activity state expected by the SN, and the MN can complete the SCG setup requested by the SN. Example process for configuring PSCELL for a deactivated SCG
[0100] Overall, when the terminal device 130 needs to configure (e.g., add or change) a PScell, the terminal device 130 needs to perform an interaction (e.g., perform an RA procedure, send an RRC Reconfiguration Complete message, etc.) between the terminal device 130 and the network device of the target PScell. However, as mentioned above, when an SCG is suspended / deactivated, both the SRB and DRS between the terminal device 130 and the SCG are suspended and random access procedures are not allowed. Therefore, it is desirable to specify a process for configuring a PScell for a deactivated SCG.
[0101] An example of performing configuration for a PScell of an SCG will be described with reference to FIG. 3A. FIG. 3A is a signaling diagram illustrating a process 300 for configuring an SCG according to some embodiments of the present disclosure. For illustrative purposes, the process 300 will be described with reference to FIG. 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 FIG. 3A, the first network device 110 acts as a MN and the second network device 120 acts as a SN.
[0102] As shown in FIG. 3A, if the terminal device 130 determines that the conditions for performing configuration for a PScell of the SCG of the second network device 120 are met, the terminal device 130 determines (310) whether the SCG of the second network device 120 is deactivated.
[0103] Next, if the terminal device 130 determines that the SCG is deactivated, the terminal device 130 sends (320) a third message to the second network device 120 of the SCG indicating that configuration for the PScell has already been completed by the terminal device 130.
[0104] This allows PScells of an SCG to be configured (eg, added, changed, etc.) even if the SCG is deactivated.
[0105] Furthermore, there are multiple scenarios in which the terminal device 130 needs to perform configuration for PScells. Therefore, the present disclosure proposes multiple processes for different scenarios. In addition, the present disclosure specifies a process of RA procedure for a scenario in which the SCG is deactivated.
[0106] From now on, exemplary processes according to the present disclosure for different scenarios will be described as follows. Furthermore, it should be understood that the types and order of messages as shown below in describing the process of Figure 3A are shown for illustrative purposes only and do not imply any limitations. In other exemplary embodiments, the messages can be replaced with any suitable messages and executed in any suitable order.
[0107] First, a scenario in which the MN initiates the addition / modification of a PScell for a deactivated SCG will be described. Referring again to FIG. 3A, the terminal device 130 receives a first RRC reconfiguration message for configuring a PScell of the SCG from the first network device 110 (302), and the terminal device 130 can determine that the conditions for performing the configuration for the PScell of the SCG are met. As an example, the terminal device 130 receives an RRC Reconfiguration message of the SCG from the first network device 110 via SRB 1, the RRC Reconfiguration message includes a reconfigurationWithSync element, and the terminal device 130 determines to perform a PScell configuration (e.g., adding or modifying a PScell).
[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 performed based on the original active state of the SCG and the first RRC reconfiguration message received in 302. In some exemplary embodiments, if the first RRC reconfiguration message indicates (e.g., by an indication) 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 reconfiguration message indicates (e.g., by an indication) 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 reconfiguration message does not indicate an active state of the SCG, the terminal device 130 continues to maintain the original active state.
[0109] As an example, if an SCG is added and the RRCReconfiguration message (e.g., an SN addition message) indicates that the SCG is deactivated (e.g., by an indication), the terminal device 130 determines that the SCG is deactivated. As another example, if the SCG is deactivated before receiving the RRCReconfiguration message and the RRCReconfiguration message does not indicate that the SCG is activated (e.g., if the RRCReconfiguration message indicates that the SCG is deactivated or if the RRCReconfiguration message does not include an indication indicating the active state of the SCG), the terminal device 130 determines that the SCG is deactivated.
[0110] As described above, if the terminal device 130 determines that the SCG is deactivated, the terminal device 130 sends (320) a third message to the second network device 120 of the SCG indicating that configuration for the PScell has already been completed by the terminal device 130.
[0111] In some exemplary embodiments, the terminal device 130 applies the SCG configuration and sends an RRC Reconfiguration Complete message including an SN RRC response message for the SN to the first network device 110 (i.e., the MN), but the terminal device 130 does not initiate an RA to the target PScell to keep the SCG deactivated.
[0112] As an example of transmitting the third message, the terminal device 130 transmits the third message to the first network device 110 such that the third message is transmitted to the second network device 120 via the first network device 110. Additionally, the terminal device 130 may suspend transmission with the second network device 120 to avoid an RA procedure for the PScell.
[0113] Alternatively, in some exemplary embodiments, the terminal device 130 applies the configuration of the SCG but keeps at least the PScell or SCG awake. Then, the terminal device 130 transmits an RRC Reconfiguration Complete message including an SN RRC response message to the first network device 110 (i.e., the MN). Additionally, the terminal device 130 initiates an RA to the target PScell and puts the PScell or SCG to sleep after the RA procedure is completed.
[0114] As another example of transmitting the third message, the terminal device 130 transmits the third message to the first network device 110 such that the third message is transmitted to the second network device 120 via the first network device 110. Additionally, the terminal device 130 enables transmission with the second network device, performs an RA procedure for the PScell via the enabled transmission, and suspends transmission with the second network device upon completion of the RA procedure.
[0115] Thus, the process of adding / changing a PScell when the SCG is inactive is defined.
[0116] Further, the SN may also initiate configuration for the PScell. Referring also to FIG. 3A, the terminal device 130 receives (306) a second RRC reconfiguration message for configuring the PScell of the SCG from the second network device 120, the second RRC reconfiguration message including a first indication indicating that the SCG is deactivated. The terminal device 130 may then determine that the conditions for performing the configuration for the PScell of the SCG are met and further determine that the SCG is deactivated. As an example, the terminal device 130 receives an RRCReconfiguration message for the SCG from the second network device 120 via SRB 3, the RRCReconfiguration message including a reconfigurationWithSync element, the RRCReconfiguration message indicating that the SCG is deactivated (e.g., by the first indication). The terminal device 130 then decides to perform the PScell configuration (e.g., change the PScell) and determines that the SCG is deactivated.
[0117] As an example, the SCG is activated before the second RRC message is received, but the SCG deactivation indication 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 intra-SN modification. The terminal device 130 then determines that the conditions for performing the configuration for the PScell of the SCG are met and the SCG is deactivated.
[0118] As described above, if the terminal device 130 determines that the SCG is deactivated, the terminal device 130 sends (320) a third message to the second network device 120 of the SCG indicating that configuration for the PScell has already been completed by the terminal device 130.
[0119] In some exemplary embodiments, to ensure that the SCG is deactivated, the terminal device 130 applies the configuration and sends a ULInformationTransferMRDC message to the first network device with an embedded RRCReconfigurationComplete message to the SN. Furthermore, the terminal device 130 does not initiate an RA to the target PScell.
[0120] As an example of transmitting the third message, the terminal device 130 transmits the third message to the first network device 110 so that the third message is transmitted to the second network device 120 via the first network device 110. Additionally, the terminal device 130 may suspend transmission with the second network device 120 to avoid an RA procedure for the PScell.
[0121] In some exemplary embodiments, the terminal device 130 may deactivate the SCG after sending an RRCReconfigurationComplete message to the second network device 120.
[0122] Alternatively, in some other exemplary embodiments, the terminal device 130 applies the configuration of the SCG, but keeps at least the PScell or SCG in a awake state and SRB3 not suspended. Then, the terminal device 130 sends an RRC Reconfiguration Complete message to the second network device 120 (i.e., the SN). Additionally, the terminal device 130 initiates an RA procedure to the target PScell. Then, the terminal device puts the PScell or SCG to sleep and suspends SRB3.
[0123] As another example of transmitting the third message, the terminal device 130 enables transmission with the second network device 120, transmits the third message to the second network device 120 via the enabled transmission, and suspends the enabled transmission with the second network device 120 upon completion of the transmission for the configuration complete message. Additionally, the terminal device 130 performs an RA procedure for the PScell via the enabled transmission before suspending the enabled transmission.
[0124] Thus, the process of adding / changing a PScell when the SCG is inactive is defined.
[0125] Additionally, the terminal device 130 may receive a message for conditional PScell addition / modification for a deactivated SCG from the first network device (i.e., MN). Before describing the process according to the present disclosure, a general conditional PScell modification (CPC) or conditional PScell addition (CPA) mechanism without SRB 3 is first described below.
[0126] In a scenario where the SCG is activated, the second network device 120 (i.e., the SN) starts this procedure by sending an SN Modification Required containing an SN RRC reconfiguration message to the first network device 110. The first network device 110 forwards the SN RRC reconfiguration message containing the RRC reconfiguration message to the terminal device 130. The terminal device 130 applies the new configuration and replies with an RRC reconfiguration complete message containing an SN RRC reconfiguration complete message. If a CPC is configured in the RRC Reconfiguration message, the terminal device 130 maintains a connection with the source PScell after the CPC configuration is received and starts evaluating the CPC execution conditions for the candidate PScells. If at least one CPC candidate PScell satisfies the corresponding CPC execution condition, the terminal device 130 detaches from the source PScell, applies the corresponding configuration stored for the selected candidate PScell, and synchronizes with the candidate PScell. The terminal device 130 completes the CPC execution procedure with a ULInformationTransferMRDC message to the first network device 110 including an embedded RRCReconfigurationComplete message to the second network device 120. If the first network device 110 receives an SN RRC response message from the terminal device 130, it forwards the SN RRC response message in an SN Modification Confirmation message to the second network device 120. If instructed, the terminal device 130 performs synchronization with the PScell of the second network device 120 as described in the SN addition procedure. Alternatively, the terminal device 130 may perform a UL transmission after already applying the new configuration.
[0127] Therefore, when receiving an RRC Reconfiguration message for CPC or CPA configuration, the terminal device 130 sends an RRC Reconfiguration complete message to the MN. Furthermore, when the CPC execution condition is met, the terminal device 130 should send an RRC Reconfiguration Complete message to the MN and initiate an RA procedure to the target PScell so that the network device can perceive the information of the target PScell. However, when the SCG is deactivated, RA to the SRB3 and the SN is usually not allowed. Additionally, if RA is not allowed, when there are multiple candidate PScells, the network device (e.g., the first network device 110 and the second network device 120) does not know which candidate PScell has been selected.
[0128] The inventors of the present disclosure have noticed that if a CPC or CPA configuration is received before SCG deactivation, the terminal device 130 can still evaluate the CPC execution condition for the candidate PScell even though the SCG is later deactivated. Furthermore, the inventors of the present disclosure have also noticed that if a CPC configuration is received after SCG deactivation, the terminal device 130 can still evaluate the CPC execution condition for the candidate PScell. Note that the information of the target PScell (e.g., the identification information of the target PScell) can be indicated in the RRC Reconfiguration Complete message. In this way, 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 of the target PScell. This will be described in more detail below.
[0129] 3A, the terminal device 130 receives (304) a third RRC reconfiguration message for conditionally configuring a PScell of the SCG from the first network device 110. The third RRC reconfiguration message includes second information of the multiple candidate PScells. Then, in response to the received third RRC reconfiguration message, the terminal device 130 selects a PScell to be switched from among the multiple candidate PScells and determines that a condition for performing configuration for the PScell of the SCG is met.
[0130] It should be understood that the terminal device 130 can receive a third RRC reconfiguration message to conditionally configure a PScell in multiple scenarios, for example, a conditional PScell change within a conditional SN where the MN is not involved when SRB 3 is not used, a conditional PScell change within a conditional SN where the MN is involved, a conditional PScell change between SNs, or a conditional PScell addition (CPC configuration is received via SRB1).
[0131] Additionally, when the third RRC reconfiguration message is received, the terminal device 130 can apply the new configuration included 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 configurations of multiple candidate PScells. The terminal device then starts evaluating CPC execution conditions for the candidate PScells and selects a 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 performing the configuration for the PScell of the SCG 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 for the PScell of the SCG 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] As an example, if the SCG is deactivated after the CPC configuration is received from the first network device 110 and the stored configuration does 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 configuration indicates that the SCG is deactivated, the terminal device 130 determines that the SCG is deactivated.
[0134] As described above, if the terminal device 130 determines that the SCG is deactivated, the terminal device 130 sends (320) a third message to the second network device 120 of the SCG indicating that configuration for the PScell has already been completed by the terminal device 130.
[0135] In some exemplary embodiments, the terminal device 130 applies the SCG configuration but does not initiate an RA to the target PScell. In some exemplary embodiments, the terminal device 130 transmits an uplink message to the first network device 110 indicating information of the selected target PScell (e.g., target PScell ID) so that the first network device can know the selected target PScell. Additionally, the MN can inform the second network device 120 of the information of the selected target PScell by transmitting another message. In some embodiments, the information can be expressed as an indication indicating the identity of the target PScell.
[0136] In some exemplary embodiments, the uplink message includes an embedded RRC ReconfigurationComplete message for the SN and the information of 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 of the selected target PScell can be transmitted independently of each other. In some other exemplary embodiments, the information of the selected target PScell may be included in the embedded RRC ReconfigurationComplete message. Additionally, in some exemplary embodiments, the uplink message is an RRCReconfigurationComplete message, a ULInformationTransferMRDC message, a UE Assistance information message, etc.
[0137] As an example, the terminal device 130 sends a ULInformationTransferMRDC message including an embedded RRCReconfigurationComplete message of the second network device 120 to the first network device 110. Here, the embedded RRCReconfigurationComplete message includes the target PScell ID.
[0138] As an example of transmitting the third message, the terminal device 130 transmits the third message to the first network device 110 so that the third message is transmitted by the first network device to the second network device. Additionally, the terminal device 130 suspends transmission with the second network device to avoid an RA procedure for the PScell.
[0139] Alternatively, in some other exemplary embodiments, the terminal device 130 applies the configuration of the SCG but keeps at least the PScell or SCG awake. Then, the terminal device 130 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 SgNBModifyConfirm message to the second network device 120. Additionally, the 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 transmitting the third message, the terminal device 130 transmits the third message to the first network device 110 so that the third message is transmitted by the first network device to the second network device. Additionally, the terminal device 130 enables transmission with the second network device, performs an RA procedure for the target PScell via the enabled transmission, and suspends transmission with the second network device upon completion of the RA procedure.
[0141] Thus, PScell configuration (eg, additional PScell changes) can be performed during a CPC or CPA procedure when the SCG is deactivated.
[0142] The second network device (i.e., SN) may send a message for conditional PScell change for the deactivated SCG to the terminal device 130 via the SRB 3. Before describing the process according to the present disclosure, a general CPC mechanism via the SRB 3 will first be described.
[0143] In a scenario where the SCG is activated, the second network device 120 (i.e., the SN) sends an SN RRC reconfiguration message to the terminal device 130 through the SRB 3. The terminal device 130 applies the new configuration and returns an SN RRC reconfiguration complete message to the second network device 120. If the terminal device 130 cannot adapt to at least some of the configurations included in the SN RRC reconfiguration message, the terminal device 130 performs a reconfiguration failure procedure. If instructed, the terminal device 130 performs synchronization with the PScell of the second network device 130, similar to the SN addition procedure. Alternatively, the terminal device 130 may perform a UL transmission after already applying the new configuration. For a CPC scenario, the terminal device 130 maintains a connection with the source PScell after the CPC configuration is received and starts evaluating the CPC execution conditions for the candidate PScell. If at least one CPC candidate PScell satisfies the corresponding CPC execution condition, the terminal device 130 detaches from the source PScell, applies the corresponding configuration stored for the selected candidate PScell, and synchronizes with the candidate PScell. The terminal device 130 completes the CPC execution procedure by sending an RRCReconfigurationComplete message to the second network device 120.
[0144] Therefore, when receiving the RRC Reconfiguration message for CPC setting, the terminal device 130 sends an RRC Reconfiguration complete message to the SN. Furthermore, when the CPC execution condition is met, the terminal device 130 should send an RRC Reconfiguration Complete message to the SN (directly or via the MN) and initiate an RA procedure to the target PScell so that the network device can perceive the information of the target PScell. However, when the SCG is deactivated, the SRB3 and RA to the SN are usually not allowed. Additionally, if RA is not allowed, when there are multiple candidate PScells, the network device (e.g., the first network device 110 and the second network device 120) does not know which candidate PScell has been selected.
[0145] The inventors of the present disclosure have noticed that if a CPC configuration is received before SCG deactivation, the terminal device 130 can still evaluate the CPC execution condition for the candidate PScell even though the SCG is later deactivated. Furthermore, the inventors of the present disclosure have also noticed that if a CPC configuration is received after SCG deactivation, the terminal device 130 can still evaluate the CPC execution condition for the candidate PScell. Note that the information of the target PScell (e.g., the identification information of the target PScell) can be indicated in the RRC Reconfiguration Complete message. In this way, 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 of the target PScell. This will be described in more detail below.
[0146] 3A, the terminal device 130 receives (308) a third RRC reconfiguration message for conditionally configuring a PScell of the SCG from the second network device 120. The third RRC reconfiguration message includes second information of the multiple candidate PScells. Then, in response to the received third RRC reconfiguration message, the terminal device 130 selects a PScell to be switched from among the multiple candidate PScells and determines that a condition for performing configuration for the PScell of the SCG is met.
[0147] As an example, for a conditional intra-SN PScell change scenario in which SRB3 is configured without SN change, the terminal device 130 receives a third RRC reconfiguration message from the second network device 120 to conditionally configure a PScell of the SCG.
[0148] Additionally, when the third RRC reconfiguration message is received, the terminal device 130 can apply the new configuration included in the third RRC message and return an SN RRC reconfiguration complete message to the second network device 120. Additionally, the terminal device 130 stores the configurations of multiple candidate PScells. Then, the terminal device starts to evaluate the CPC execution conditions for the candidate PScells and selects a 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 performing the configuration for the PScell of the SCG are met.
[0149] 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 for the PScell of the SCG 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] As an example, if the SCG is deactivated after the CPC configuration is received from the first network device 110 and the stored configuration does 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 but the stored configuration indicates that the SCG is deactivated, the terminal device 130 determines that the SCG is deactivated.
[0151] As described above, if the terminal device 130 determines that the SCG is deactivated, the terminal device 130 sends (320) a third message to the second network device 120 of the SCG indicating that configuration for the PScell has already been completed by the terminal device 130.
[0152] In some exemplary embodiments, the terminal device 130 applies the stored configuration but does not initiate an RA to the target PScell. In some exemplary embodiments, the terminal device 130 transmits an uplink message to the first network device 110 indicating information of the selected target PScell (e.g., target PScell ID) so that the first network device can know the selected target PScell. Additionally, the MN can inform the second network device 120 of the information of the selected target PScell by transmitting another message. In some embodiments, the information can be expressed as an indication indicating the identity of the target PScell.
[0153] In some exemplary embodiments, the uplink message includes an embedded RRC ReconfigurationComplete message for the SN and the information of 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 of the selected target PScell can be transmitted independently of each other. In some other exemplary embodiments, the information of the selected target PScell may be included in the embedded RRC ReconfigurationComplete message. Additionally, in some exemplary embodiments, the uplink message is an RRCReconfigurationComplete message, a ULInformationTransferMRDC message, a UE Assistance information message, etc.
[0154] As an example, the terminal device 130 sends a ULInformationTransferMRDC message including an embedded RRCReconfigurationComplete message of the second network device 120 to the first network device 110. Here, the embedded RRCReconfigurationComplete message includes the target PScell ID.
[0155] As an example of transmitting the third message, the terminal device 130 transmits the third message to the first network device 110 so that the third message is transmitted by the first network device to the second network device. Additionally, the terminal device 130 suspends transmission with the second network device to avoid a random access (RA) procedure for the PScell.
[0156] Alternatively, in some exemplary embodiments, the terminal device 130 applies the configuration of the SCG but keeps at least the PScell or SCG awake. The terminal device 130 then activates SRB3 if necessary, initiates an RA to the target PScell, and sends an RRCReconfigurationComplete to the second network device 120 via SRB3 (if configured). The terminal device 130 then puts the PScell or SCG to sleep after successfully sending the RRC Reconfiguration Complete message and suspends SRB3.
[0157] As another example of transmitting the third message, the terminal device 130 enables transmission with the second network device, transmits the third message to the second network device via the enabled transmission, and suspends transmission with the second network device upon completion of the transmission for the configuration complete message. Additionally, the terminal device 130 performs an RA procedure for the target PScell via the enabled transmission before suspending the transmission.
[0158] Thus, PScell configuration (eg, changing PScell) can be performed during a CPC procedure when the SCG is deactivated. Example of SCG setting process without changing PSCELL
[0159] 3B is a signaling diagram illustrating a process 350 for configuring an SCG without changing a PScell according to some embodiments of the present disclosure. For illustrative purposes, the process 350 is described with reference to FIG. 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 FIG. 3B, the first network device 110 acts as a MN and the second network device 120 acts as a SN.
[0160] As shown in FIG. 3B, the terminal device 130 receives (360) a fourth message for configuring the SCG of the second network device. The fourth message includes a second indication that the SCG is deactivated. The terminal device 130 then transmits (370) 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.
[0161] As an example of sending the third message, the terminal device 130 sends a fifth message to the first network device so that the fifth message is sent to the second network device via the first network device.
[0162] As another example of transmitting the third message, the terminal device 130 enables transmission with the second network device, transmits the third message to the second network device via the enabled transmission, and suspends the enabled transmission with the second network device in response to completion of the transmission for the configuration completion message.
[0163] In this way, the terminal device 130 can set up the SCG even if the SCG is deactivated. Example of avoiding SCG configuration for a deactivated SCG
[0164] In some example embodiments, when an SCG is deactivated, the first network device 110 or the second network device 130 ensures that configuration for a PScell of the SCG (e.g., adding or modifying a PScell) cannot be performed. As an example, when an SCG is deactivated, the first network device 110 or the second network device 120 does not send an RRC reconfiguration message with ReconfigurationWithSync for the PScell to the terminal device 130.
[0165] In some exemplary embodiments, the ReconfigurationWithSync element of the PScell and the SCG deactivation indication are configured in separate RRC messages to the UE. More specifically, the SCG deactivation procedure is performed after the procedure for the ReconfigurationWithSync element.
[0166] In some exemplary embodiments, if a CPC configuration is received before SCG deactivation, 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 configuration when the SCG is deactivated. Alternatively, the terminal device 130 releases the CPC configuration when the SCG is deactivated.
[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, and instructs the terminal device 130 to release the stored configuration for the candidate PScell.
[0168] In some exemplary embodiments, after the RRC message is sent for the CPC, the second network device 120 determines that the SCG is deactivated, and instructs the terminal device 130 to release the stored configuration for the candidate PScell.
[0169] In some example embodiments, after the RRC messages for CPC and CPA are received and before the stored configuration for the selected target PScell is applied, the terminal device 130 determines that the SCG is deactivated, and releases the stored configuration for the candidate PScell.
[0170] In some exemplary embodiments, the CPC / CPA settings do not include an SCG inactive indication.
[0171] In this way, SCG configuration is avoided for deactivated SCGs by restricting network configuration or specifying the behavior of the terminal device (e.g. deleting / releasing stored CPC settings when the SCG is deactivated).
[0172] 4 is a flow chart of an example method 400 according to some embodiments of the present disclosure. Method 400 may be implemented in the first terminal device 110 shown in FIG. It should be understood that method 400 may include additional blocks not shown and / or may omit some blocks shown, and the scope of the disclosure is not limited in this respect. For purposes of explanation, method 400 will be described with reference to FIG. 1 from the perspective of the first network device 110.
[0173] At 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. The request includes first information regarding a first activity state of the SCG. At block 420, the first network device 110 receives a response to the request from the second network device 120. The response indicates a 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 transmits an SN add request including the first information in accordance with a determination that an SCG should be added. In some other exemplary embodiments, the first network device 110 transmits an SN modify request including the first information in accordance with a determination that an SCG should be modified.
[0175] In some exemplary embodiments, the first activity state of the SCG is active or inactive.
[0176] 5 is a flow chart of an example method 500 according to some embodiments of the present disclosure. Method 500 may be implemented in second terminal device 120 shown in FIG. 1. It should be understood that method 500 may include additional blocks not shown and / or may omit some blocks shown, and the scope of the disclosure is not limited in this respect. For purposes of explanation, method 500 will be described with reference to FIG. 1 from the perspective of 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. The request includes first information regarding a first activity state of the SCG. In block 520, the second network device 120 determines a current activity state of the SCG based on the first information. In block 530, the second network device 120 sends 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 the SN add request pursuant to a determination that an SCG should be added. In some other embodiments, the second network device 120 receives the SN modify request pursuant to a determination that an SCG should be modified.
[0179] In some exemplary embodiments, the first activity state of the SCG is active or inactive.
[0180] 6 is a flow chart of an example method 600 according to some embodiments of the present disclosure. Method 600 may be implemented in the first terminal device 110 shown in FIG. 1. It should be understood that method 600 may include additional blocks not shown and / or may omit some blocks shown, and the scope of the disclosure is not limited in this respect. For purposes of explanation, method 600 will be described with reference to FIG. 1 from the perspective of the first network device 110.
[0181] At block 610, the first network device 110 receives a first message from the second network device 120 for configuring an SCG associated with the second network device 120. The first message includes parameters related to a second activity state of the SCG. At block 620, the network device 110 sends a second message to the second network device 120 for acknowledging the first message.
[0182] The terminal device 130 is instructed to perform settings for the SCG for the terminal device 130. 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] 7 is a flow chart of an example method 700 according to some embodiments of the present disclosure. Method 700 may be implemented in second terminal device 120 shown in FIG. 1. It should be understood that method 700 may include additional blocks not shown and / or may omit some blocks shown, and the scope of the disclosure is not limited in this respect. For purposes of explanation, method 700 will be described with reference to FIG. 1 from the perspective of second network device 120.
[0185] At block 710, the second network device 120 generates a first message for configuring an SCG associated with the second network device 120. The first message includes parameters related to a second activity state of the SCG. At 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] 8 is a flow chart of an example method 800 according to some embodiments of the present disclosure. Method 800 may be performed in terminal device 130 shown in FIG. It should be understood that method 800 may include additional blocks not shown and / or may omit some blocks shown, and the scope of the disclosure is not limited in this respect. For purposes of explanation, method 800 will be described with reference to FIG. 1 from the perspective of terminal device 130.
[0188] In block 810, the terminal device 130 determines whether the SCG of the second network device 120 is deactivated in accordance with the determination 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 is served by the first network device 110. In block 820, the terminal device 130 sends a third message to the SCG of the second network device 120 in accordance with the determination that the SCG is deactivated. The third message indicates that the configuration for the PScell has already been completed by the terminal device 130.
[0189] In some example embodiments, terminal device 130 receives a first RRC reconfiguration message for configuring a PScell of an SCG from first network device 110. Terminal device 130 determines that conditions for performing the configuration for the PScell of the SCG are met.
[0190] In some exemplary embodiments, terminal device 130 transmits the third message to first network device 110 so that the third message is transmitted to second network device 120 via first network device 110. Terminal device 130 further suspends transmission with second network device 120 to avoid an RA procedure for the PScell.
[0191] In some exemplary embodiments, terminal device 130 transmits a third message to first network device 110 so that the third message is transmitted to second network device 120 via first network device 110. Terminal device 130 further enables transmission with second network device 120, performs an RA procedure for the PScell via the enabled transmission, and suspends transmission with second network device 120 upon completion of the RA procedure.
[0192] In some exemplary embodiments, the terminal device 130 receives a second RRC reconfiguration message for configuring a PScell of the SCG from the second network device 120. The second RRC reconfiguration message includes a first indication that the SCG is deactivated. The terminal device 130 determines that a condition for performing the configuration for the PScell of the SCG is met.
[0193] In some exemplary embodiments, terminal device 130 transmits the third message to first network device 110 so that the third message is transmitted to second network device 120 via first network device 110. Terminal device 130 further suspends transmission with second network device 120 to avoid an RA procedure for the PScell.
[0194] In some exemplary embodiments, terminal device 130 enables transmission with second network device 120, transmits a third message to second network device 120 via the enabled transmission, and suspends the enabled transmission with second network device 120 in response to completion of the transmission for the configuration complete message. Terminal device 130 further performs an RA procedure for the PScell via the enabled transmission before suspending the enabled transmission.
[0195] In some example embodiments, the terminal device 130 receives a third RRC reconfiguration message for conditionally configuring a PScell of the SCG from the first network device 110 or the second network device 120. The third RRC reconfiguration message includes second information of the multiple candidate PScells. The terminal device 130 selects a PScell to be switched from among the multiple candidate PScells in response to the received third RRC reconfiguration message, and determines that a condition for performing configuration for the PScell of the SCG is met.
[0196] In some exemplary embodiments, in response to receiving the third RRC reconfiguration message from the first network device 110, the terminal device 130 transmits a third message to the first network device 110 for transmission to the second network device 120 via the first network device 110. The third message indicates the target PScell. The terminal device 130 further suspends transmission with the second network device 120 to avoid an RA procedure for the PScell.
[0197] In some exemplary embodiments, in response to receiving the third RRC reconfiguration message from first network device 110, terminal device 130 transmits a third message to first network device 110 for transmission by first network device 110 to second network device 120. Terminal device 130 further enables transmission with second network device 120, performs an RA procedure for the target PScell via the enabled transmission, and suspends transmission with second network device 120 in response to completion of the RA procedure.
[0198] In some exemplary embodiments, terminal device 130 transmits the third message to first network device 110 in response to receiving the third RRC reconfiguration message from second network device 120, so that the third message indicating the target PScell is transmitted by first network device 110 to second network device 120. Terminal device 130 suspends transmission with second network device 120 in accordance with the received third RRC reconfiguration message to avoid an RA procedure for the PScell.
[0199] In some example embodiments, terminal device 130 enables transmission with second network device 120 in response to receiving the third RRC reconfiguration message from second network device 120, transmits the third message to second network device 120 via the enabled transmission, and suspends transmission with second network device 120 in response to completing the transmission for the configuration complete message. Terminal device 130 further performs an RA procedure for the target PScell via the enabled transmission before suspending the transmission.
[0200] 9 is a flow chart of an example method 900 according to some embodiments of the present disclosure. Method 900 may be performed in terminal device 130 shown in FIG. It should be understood that method 900 may include additional blocks not shown and / or may omit some blocks shown, and the scope of the disclosure is not limited in this respect. For purposes of explanation, method 900 will be described with reference to FIG. 1 from the perspective of terminal device 130.
[0201] In block 910, the terminal device 130 receives a fourth message from the second network device 120 for configuring an SCG of the second network. The fourth message includes a second indication indicating that the SCG is deactivated. In block 920, the 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 the terminal device 130.
[0202] In some exemplary embodiments, the terminal device 130 sends the fifth message to the first network device 110 so that the fifth message is sent to the second network device 120 via the first network device 110.
[0203] In some demonstrative embodiments, terminal device 130 enables transmission with second network device 120, transmits a fifth message to second network device 120 via the enabled transmission, and suspends the enabled transmission with second network device 120 in response to completion of the transmission for the configuration completion message.
[0204] 10 is a schematic block diagram of an apparatus 1000 suitable for implementing an embodiment of the present disclosure. The apparatus 1000 may be considered as another exemplary implementation of the terminal apparatus 130, the second network apparatus 120, or the first network apparatus 110 shown in FIG. 1. Thus, the apparatus 1000 may be implemented in or as at least a part of the terminal apparatus 130, the second network apparatus 120, or the first network apparatus 110.
[0205] As shown, the apparatus 1000 comprises a processor 1010, a memory 1020 coupled to the processor 1010, a suitable transmitter (TX) and receiver (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 a 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 nodes referred to herein may in practice have multiple antennas. The communication interface may represent any interface required 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 the program 1030 includes program instructions that, when executed by the associated processor 1010, enable the device 1000 to operate according to embodiments of the present disclosure, as described herein with reference to Figures 2A, 2B, 3, 6A, 6B, 7, 9 and 10. The embodiments herein can be realized by computer software executable by the processor 1010 of the device 1000, or 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, the combination of the processor 1010 and the memory 1010 can form a processing means 1050 suitable for implementing various embodiments of the present disclosure.
[0207] The memory 1010 may be of any type suitable for a local technology network and may be implemented using any suitable data storage technology, such as, by way of non-limiting example, non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. Although only one memory 1010 is shown in the device 1000, there may be several physically different memory modules in the device 1000. The processor 1010 may be of any type suitable for a local technology network and may include, by way of non-limiting example, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. The device 1000 may have multiple processors, for example application specific integrated circuit chips time-slaved to a clock that synchronizes the main processor.
[0208] Overall, various embodiments of the present disclosure can be realized in hardware or special purpose circuits, software, logic, or any combination thereof. Some aspects may be realized in hardware, while other aspects may be realized in firmware or software that can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure have been illustrated and described using block diagrams, flow charts, or some other pictorial representations, it should be understood that the blocks, devices, systems, techniques, or methods described herein can be implemented, by way of non-limiting examples, in hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing device, or any combination thereof.
[0209] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as instructions included in a program module, that are executed in a device on a target real or virtual processor to perform the process or method described above with reference to Figures 2A-2D, 3A, 3B, 4 to 9. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. In various embodiments, the functionality of the program modules may be combined or split between program modules as appropriate. The machine-executable instructions of the program modules may be executed in local or distributed devices. In a distributed device, the program modules may be located in both local and remote storage media.
[0210] The program codes for carrying out the methods of the present 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 special purpose computer, or other programmable data processing device, and when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code can be executed entirely on the machine, partially on the machine, as a separate software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.
[0211] The above program code may be implemented on a machine-readable medium, which may be any tangible medium that can contain or store a program 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, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or apparatus, or any suitable combination of the aforementioned media. More specific examples of machine-readable storage media may include an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable optical disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the aforementioned.
[0212] It should be understood that although operations have been described in a particular order, it is not required that such operations be performed in the particular order shown, or in any sequential order, or that all of the operations described be performed, in order to achieve desired results. In some cases, multitasking or parallel processing may be advantageous. Similarly, although some specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of features that may be specific to certain embodiments. Some features that are described in the context of individual embodiments may be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may be implemented in multiple embodiments separately or in any suitable subcombination.
[0213] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the present disclosure, as defined in the appended claims, is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims
1. receiving a radio resource control (RRC) reconfiguration message for conditionally configuring a PScell of a secondary cell group (SCG) from a network device; selecting a target PS cell to be switched from among a plurality of candidate PS cells; transmitting an uplink message to the network device including information indicating the selected target PS cell; Including, The RRC reconfiguration message includes information of the plurality of candidate PS cells. Communication methods.
2. Applying the settings of the SCG The method of claim 1.
3. A terminal device, A receiving means for receiving a radio resource control (RRC) reconfiguration message for conditionally configuring a PScell of a secondary cell group (SCG) from a network device; A selection means for selecting a target PS cell to be switched from among a plurality of candidate PS cells; a transmitting means for transmitting an uplink message to the network device, the uplink message including information indicating the selected target PS cell; Equipped with The RRC reconfiguration message includes information of the plurality of candidate PS cells. Terminal device.
4. An application means for applying the setting of the SCG, The terminal device according to claim 3.
5. A network device, A transmission means for transmitting a radio resource control (RRC) reconfiguration message for conditionally configuring a PS cell of a secondary cell group (SCG) to a terminal device; A receiving means for receiving an uplink message including information indicating a target PS cell from the terminal device; Equipped with The RRC reconfiguration message includes information of multiple candidate PS cells. Network device.
6. Transmitting a radio resource control (RRC) reconfiguration message for conditionally configuring a PScell of a secondary cell group (SCG) to a terminal device; receiving an uplink message from the terminal device, the uplink message including information indicating a target PS cell; Including, The RRC reconfiguration message includes information of multiple candidate PS cells. Communication methods.
Citation Information
Patent Citations
Method and device for switching a serving cell and method and device supporting on-demand system information message
US20200120553A1
Wireless access network node, wireless terminal, and method therefor
WO2020144919A1
