Measurement configuration method and communication device
By having the source master node and candidate master node collaboratively configure the measurement objects and gaps when the terminal device switches cells, the problem of insufficient CPAC measurement configuration is solved, and the CPAC triggering opportunities and communication quality are improved.
Patent Information
- Application Number
- CN202210738508.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-06-24
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2042-06-24
AI Technical Summary
When terminal equipment switches cells, existing technologies fail to effectively consider the measurement configuration requirements for Conditional Primary and Secondary Cell Addition and Change (CPAC), which may result in only measuring some candidate SN frequency points, reducing the chance of CPAC triggering and affecting communication quality.
The source master node sends a CHO request to the candidate master node, receives the response and configures the measurement object and gap, and coordinates with the candidate auxiliary node to perform frequency point measurement, ensuring that the terminal device evaluates the CPAC triggering conditions and increases the chance of CPAC triggering.
It improves the speed and communication quality of terminal devices accessing more suitable cells, increases the chance of CPAC triggering, and ensures faster CPAC completion.
Smart Images

Figure CN117336800B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of cell handover technology, and in particular to a measurement configuration method and a communication device. Background Technology
[0002] A terminal device can access two or more nodes simultaneously. A terminal device accessing both the master node (MN) and a secondary node (SN) simultaneously is called dual-connectivity (DC). A terminal device accessing both the MN and at least two SNs simultaneously is called multi-connectivity (MC). In either DC or MC, the MN has a control plane signaling connection to the core network. The MN provides the terminal device with a master cell group (MCG), which contains the primary cell (PCell). The SN provides the terminal device with a secondary cell group (SCG), which contains the primary secondary cell (PSCell).
[0003] When a terminal device switches cells, it needs to measure the frequency to be measured according to the measurement configuration to determine whether the handover triggering conditions are met. When the terminal device is configured with conditional handover (CHO) and conditional primary / secondary cell addition and change (CPAC), it needs to determine whether there are candidate MNs that meet the CHO triggering conditions and whether there are candidate SNs under the candidate MNs that meet the CPAC triggering conditions. However, MNs only consider the measurement configuration requirements of CHO and not the measurement configuration requirements of CPAC. This may result in the terminal device only measuring some of the SNs to be measured in the CPAC or not measuring any of the SNs to be measured in the CPAC, reducing the chance of CPAC triggering. Summary of the Invention
[0004] This application provides a measurement configuration method and communication device, which increases the chance of CPAC triggering when the terminal device is configured with CHO and CPAC, thereby completing CPAC more quickly.
[0005] In a first aspect, embodiments of this application provide a measurement configuration method, which can be executed by a first communication device. The first communication device can be a communication equipment or a communication device capable of supporting the functions required for the method to be implemented, such as a chip system. The following description uses a source master node as an example. Exemplarily, the first communication device is a source master node, or a chip disposed in a source master node, or other components used to implement the functions of the source master node.
[0006] The measurement configuration method includes: a source master node sending a CHO request to one or more candidate master nodes, receiving a CHO request response from a first candidate master node, and sending a first radio resource control (RRC) configuration message to a terminal device. The first candidate master node belongs to one or more candidate master nodes. The CHO request response includes CHO configuration, a first CPAC configuration, and the frequency point to be measured for the candidate auxiliary node. The first RRC configuration message includes CHO configuration, a second CPAC configuration, and measurement configuration. The second CPAC configuration is determined based on the first CPAC configuration. The measurement configuration includes the measurement object and the corresponding first measurement gap configuration. The measurement object includes the frequency point to be measured for the source master node, the frequency point to be measured for the first candidate master node, the frequency point to be measured for the auxiliary master node, and the frequency point to be measured for the candidate auxiliary node.
[0007] In this method, the first candidate master node is the candidate master node that receives a CHO request from the source master node. After receiving the CHO request, the first candidate master node can initiate a conditional primary / secondary cell addition (CPA) request or a conditional primary / secondary cell change (CPC) request to the candidate secondary nodes to obtain the test frequency points of the candidate secondary nodes. The first candidate master node can feed back the obtained test frequency points of the candidate secondary nodes to the source master node, so that the source master node can subsequently configure appropriate measurement objects and measurement gaps based on the test frequency points of the source master node, the candidate master node, the secondary master node, and the candidate secondary nodes. Through this method, when evaluating whether the CHO triggering conditions are met, the terminal device can measure not only the test frequency points of the candidate master node but also the test frequency points of the candidate secondary nodes, that is, it can also evaluate whether the CPAC triggering conditions are met, thereby increasing the CPAC triggering opportunity and helping the terminal device complete CPAC more quickly. Furthermore, it facilitates the connection of terminal devices to more suitable cells, thereby improving the communication quality after the terminal devices are connected to the cell.
[0008] In a possible implementation, the method further includes: the source master node determining a first measurement gap configuration based on the measurement object, and sending the first measurement gap configuration and measurement gap type to the source slave node, wherein the measurement gap type includes a measurement type configured for the terminal device or a measurement gap type configured for a frequency range. The measurement gap is the duration from when the terminal device stops communicating with the serving cell to when it measures a neighboring cell frequency. During the measurement gap, the terminal device does not send or receive data, but instead tunes its receiver to the frequency to be measured and performs frequency measurement. When the measurement gap ends, the terminal device tunes its receiver to the serving cell's frequency.
[0009] In this method, the source master node can configure a measurement gap based on the measurement objects, such as the frequency points to be measured of the source master node, the frequency points to be measured of candidate master nodes, the frequency points to be measured of auxiliary master nodes, and the frequency points to be measured of candidate auxiliary nodes. That is, the source master node configures measurement gaps based on multiple frequency points to be measured to avoid the configured measurement gaps being insufficient to measure some frequency points, resulting in the inability to measure some frequency points. In addition, the source master node can also provide the source auxiliary node with a first measurement gap configuration and a measurement gap type to assist the source auxiliary node in determining whether to configure a gap for the terminal device, and if so, which gap to configure. For example, in Evolved Universal Terrestrial Radio Access with New Radio Dual Connectivity (E-UTRA NR dual connectivity, EN-DC) scenarios or Next Generation RAN with Evolved Universal Terrestrial Radio Access Dual Connectivity (NGEN-DC) scenarios, if the first measurement gap is configured as a gap configuration for the first frequency range (FR), and the measurement gap type is a measurement gap type specific to the first FR, then the source and secondary nodes can also configure another FR gap measurement for the terminal device, such as a second FR gap measurement. The first FR is also called FR1, and the second FR is also called FR2. The lowest frequency of FR1 is 450MHz, and the highest frequency is 6GHz; the lowest frequency of FR2 is 24.25GHz, and the highest frequency is 52.6GHz.
[0010] In a possible implementation, the CHO request response further includes a second measurement gap configuration, which is determined based on the frequency points to be measured of the first candidate master node and the candidate auxiliary node. The method further includes: the source master node determining a first measurement gap configuration based on the second measurement gap configuration, and sending the first measurement gap configuration and measurement gap type to the source auxiliary node, wherein the measurement gap type includes a measurement type configured for the terminal device or a measurement gap type configured for a frequency range. The first candidate master node can also configure a gap, such as a second measurement gap, based on the frequency points to be measured of the first candidate master node and the candidate auxiliary node, and provide it to the source master node. The source master node can configure a more suitable gap for the terminal device based on the second measurement gap. For example, if the first measurement gap is greater than the second measurement gap, the source master node can configure the first measurement gap for the terminal device; conversely, if the second measurement gap is greater than the first measurement gap, the source master node can configure the second measurement gap for the terminal device, thereby allowing measurement of more frequency points to be measured, to avoid missing measurements of frequency points with better communication quality.
[0011] In a possible implementation, the CHO request response also includes a third measurement gap configuration, which is configured based on the frequency points within FR2 among the test frequencies of the candidate secondary nodes. If the first candidate primary node obtains the third measurement gap configuration, it can provide it to the source primary node, which in turn provides the third measurement gap configuration to the source secondary node to assist the source secondary node in configuring the FR2 measurement gap to the terminal device.
[0012] In a possible implementation, the method further includes: the source master node sending measurement frequency information to the source auxiliary node, the measurement frequency information indicating the frequency points within FR2 among the candidate auxiliary node's test frequencies. By providing the test frequencies within FR2 to the source auxiliary node, the source auxiliary node can configure the measurement gap of FR2 to the terminal device based on the test frequencies within FR2, thus enabling measurement gap configuration for more scenarios. For example, the source master node can be responsible for configuring the gap within FR1, while the auxiliary node can be responsible for configuring the gap within FR2. This allows the source master node and source auxiliary node to negotiate and complete the gap configuration, enabling measurement gap configuration in both EN-DC and NGEN-DC scenarios.
[0013] In a possible implementation, the method further includes: the source master node determines the fourth measurement gap configuration based on the test frequency of the candidate auxiliary node, wherein the test frequency of the candidate auxiliary node is a frequency located within FR1.
[0014] In a possible implementation, the CHO request response includes the identifier and / or data forwarding address of the candidate secondary node. That is, the first candidate primary node can provide the identifier and / or data forwarding address of the candidate secondary node to the source primary node. When notifying the source secondary node to perform data forwarding, the source primary node provides the identifier and / or data forwarding address of the candidate secondary node to the source secondary node. Thus, the source secondary node forwards data to the candidate secondary node based on the identifier and / or data forwarding address of the candidate secondary node, enabling direct data forwarding under CPAC.
[0015] Among the possible implementations, the first RRC configuration message has the following three implementation forms. The specific implementation form used is not limited in the embodiments of this application.
[0016] In implementation form one, the first RRC configuration message includes a second RRC configuration message and a first execution triggering condition corresponding to the first candidate master node. The second RRC configuration message includes the radio interface configuration of the first candidate master node and the second execution triggering condition corresponding to the candidate PSCell. Furthermore, the information elements in the first RRC configuration message, excluding the second RRC configuration message, also include the identifier information of the candidate PSCell and the second execution triggering condition corresponding to the candidate PSCell. The candidate PSCell is managed by the candidate secondary node. The first execution triggering condition is the execution triggering condition of the CHO (Confirmation of Host Request), that is, the triggering condition that the terminal device must meet to switch to a PCell managed by the first candidate master node. The terminal device triggers the switch to that PCell only when it meets the first execution triggering condition corresponding to that PCell. Similarly, the second execution triggering condition is the execution triggering condition of the CPAC (Confirmation of Host Request), that is, the triggering condition that the terminal device must meet to switch to a PSCell managed by the candidate secondary node. The terminal device triggers the switch to that PSCell only when it meets the second execution triggering condition corresponding to that PSCell. In the first implementation, when evaluating the execution trigger conditions of CHO and CPAC, the terminal device only needs to obtain the second execution trigger condition from the first RRC configuration message, without parsing the second RRC configuration message. If CHO is triggered but CPAC is not triggered, after the terminal device successfully performs primary cell handover, it can delete the configuration for the first execution trigger condition in the first RRC configuration message, that is, only retain the second RRC configuration message, so that subsequent CPAC evaluation can be performed according to the existing CPAC configuration.
[0017] In implementation method two, the first RRC configuration message includes a second RRC configuration message and a first execution trigger condition corresponding to the first candidate primary node. The second RRC configuration message includes the radio interface configuration of the first candidate primary node and the second execution trigger condition corresponding to the candidate PSCell. The information elements in the first RRC configuration message other than the second configuration RRC message do not include the identification information of the candidate PSCell or the second execution trigger condition corresponding to the candidate PSCell. The candidate PSCell is managed by the candidate secondary node. With implementation method two, if the CHO is triggered but CPAC is not triggered, after the terminal device successfully performs primary cell handover, it can retain only the second RRC configuration message and does not need to retain the configuration for the first execution trigger condition in the first RRC configuration message. Subsequent CPAC evaluation can be performed according to the existing CPAC configuration.
[0018] In implementation form three, the first RRC configuration message includes a second RRC configuration message and a first execution triggering condition corresponding to the first candidate master node. The second RRC configuration message includes the radio interface configuration of the first candidate master node and the radio interface configuration of the candidate secondary node, but does not include the second execution triggering condition corresponding to the candidate PSCell. Furthermore, the information elements in the first RRC configuration message other than the second RRC configuration message also include the identification information of the candidate PSCell and the second execution triggering condition corresponding to the candidate PSCell. The candidate PSCell is managed by the candidate secondary node. Using implementation form three, the terminal device evaluates the execution triggering conditions of the CHO and CPAC, and obtains the second execution triggering condition from the first RRC configuration message; parsing the second RRC configuration message is unnecessary.
[0019] Secondly, embodiments of this application provide a measurement configuration method, which can be executed by a second communication device. The second communication device can be a communication equipment or a communication device capable of supporting the functions required for the method to be implemented, such as a chip system. The following description uses the example of a candidate master node as the communication device. Exemplarily, the second communication device is a candidate master node, or a chip disposed in a candidate master node, or other components used to implement the functions of a candidate master node.
[0020] The measurement configuration method includes: a candidate master node receiving a CHO request sent by a source master node and sending a CHO request response to the source master node. The CHO request response includes CHO configuration, first CPAC configuration, and the frequency point to be measured for the candidate auxiliary node.
[0021] In a possible implementation, the method further includes: the candidate master node sending a CPA request to the candidate slave node and receiving a CPA request response from the candidate slave node; or the candidate master node sending a CPC request to the candidate slave node and receiving a CPC request response from the candidate slave node. The CPA request response or CPC request response includes the frequency point to be measured of the candidate slave node.
[0022] In a possible implementation, the CHO request response includes all test frequencies of the candidate auxiliary nodes.
[0023] In a possible implementation, the CHO request response includes the identifier and / or data forwarding address of the candidate secondary node.
[0024] In a possible implementation, the method further includes: the candidate master node determines the measurement gap configuration based on the frequency point to be measured of the candidate auxiliary node, and sends the measurement gap configuration to the source master node.
[0025] For the technical effects of the second aspect and its various possible implementations, please refer to the introduction of the technical effects of the first aspect and its various possible implementations.
[0026] Thirdly, embodiments of this application provide a communication device that has the function of implementing the behavior in any one of the method embodiments of the first to second aspects described above. The beneficial effects can be found in the descriptions of the first to second aspects, and will not be repeated here.
[0027] The communication device may be an access network device for executing the method performed by the source master node in the first aspect, or the communication device may be a device capable of implementing the method provided in the first aspect, such as a chip or chip system. In one possible design, the communication device includes corresponding means or modules for executing the method in the first aspect. For example, the communication device includes a processing unit (sometimes also called a processing module or processor) and / or a transceiver unit (sometimes also called a transceiver module or transceiver). The transceiver unit may include a sending unit and a receiving unit, or it can be understood that the sending unit and the receiving unit are the same functional module. Alternatively, the transceiver unit can also be understood as a collective term for the sending unit and the receiving unit, which may be different functional modules. These units (modules) can perform the corresponding functions in the above-described method examples of the first aspect, as detailed in the method examples, and will not be repeated here.
[0028] The communication device may be an access network device for executing the method performed by the candidate master node in the second aspect, or the communication device may be a device capable of implementing the method provided in the second aspect, such as a chip or chip system. In one possible design, the communication device includes corresponding means or modules for executing the method of the second aspect. For example, the communication device includes a processing unit (sometimes also called a processing module or processor) and / or a transceiver unit (sometimes also called a transceiver module or transceiver). The transceiver unit may include a sending unit and a receiving unit, or it can be understood that the sending unit and the receiving unit are the same functional module. Alternatively, the transceiver unit can also be understood as a collective term for the sending unit and the receiving unit, which may be different functional modules. These units (modules) can perform the corresponding functions in the above-described method examples of the second aspect, as detailed in the method examples, and will not be repeated here.
[0029] Fourthly, embodiments of this application provide a communication device capable of executing the methods described in any one of the first to second aspects. The communication device includes a communication interface and a processor, and optionally, a memory. The memory stores a computer program, and the processor is coupled to the memory and the communication interface. When the processor reads the computer program or instructions, it causes the communication device to execute the methods described above, which are performed by the source master node or the candidate master node.
[0030] Fifthly, embodiments of this application provide a communication device including an input / output interface and logic circuitry. The input / output interface is used for inputting and / or outputting information. The logic circuitry is used to execute the methods described in any one of the first to second aspects.
[0031] Sixthly, embodiments of this application provide a chip system including a processor, and may further include a memory and / or a communication interface for implementing the methods described in any one of the first to second aspects. In one possible implementation, the chip system further includes a memory for storing a computer program. The chip system may be composed of chips or may include chips and other discrete devices.
[0032] In a seventh aspect, embodiments of this application provide a communication system comprising a source master node, candidate master nodes, and terminal devices. The source master node is used to execute the method described in the first aspect above, and the candidate master node is used to execute the method described in the second aspect above. Of course, the communication system may include more nodes, such as source auxiliary nodes, candidate auxiliary nodes, etc.
[0033] Eighthly, this application provides a computer-readable storage medium storing a computer program that, when run, implements the method of any one of the first to second aspects described above.
[0034] Ninthly, a computer program product is provided, the computer program product comprising: computer program code, which, when executed, causes the method of any one of the first to second aspects to be performed.
[0035] The beneficial effects of the third to ninth aspects and their implementation methods can be referred to the description of the beneficial effects of the first to second aspects and their implementation methods. Attached Figure Description
[0036] Figure 1 This is a schematic diagram of a communication system to which embodiments of this application are applicable;
[0037] Figure 2 A schematic flowchart illustrating the measurement configuration method provided in an embodiment of this application;
[0038] Figure 3 A flowchart illustrating a measurement configuration method for a first example provided in an embodiment of this application;
[0039] Figure 4 A schematic flowchart illustrating a measurement configuration method as provided in the second example of an embodiment of this application;
[0040] Figure 5 A schematic flowchart illustrating the measurement configuration method of the third example provided in this application embodiment;
[0041] Figure 6 A schematic flowchart illustrating the measurement configuration method of the fourth example provided in this application embodiment;
[0042] Figure 7 A schematic block diagram of a communication device provided in an embodiment of this application;
[0043] Figure 8 Another schematic block diagram of the communication device provided in the embodiments of this application. Detailed Implementation
[0044] The technical solutions provided by the embodiments of this application can be applied to new radio (NR) mobile communication systems, or to long-term evolution (LTE) mobile communication systems, or to other next-generation mobile communication systems, such as the sixth generation (6G) communication system, or other similar communication systems. The technical solutions provided by the embodiments of this application can also be applied to internet of things (IoT) systems, vehicle-to-everything (V2X) systems, etc.
[0045] In this embodiment, a terminal device can communicate with multiple network devices. One network device is the primary network device, and the others are secondary network devices. The primary network device is the one that interacts with the core network via control plane signaling. The terminal device has a communication connection with the primary network device. The terminal device can establish communication connections with some or all of the secondary network devices. Both the primary and secondary network devices have radio resource control (RRC) entities and can generate RRC messages (e.g., cell measurement messages). Secondary network devices can directly send the RRC messages they generate to the terminal device, and conversely, the terminal device can also directly send its generated RRC messages to the secondary network devices. Alternatively, the secondary network devices can send their generated RRC messages to the primary network device, which then forwards them to the terminal device. Similarly, the terminal device sends the RRC messages intended for the secondary network devices to the primary network device, which then forwards them to the secondary network devices.
[0046] As an example, embodiments of this application can be applied to DC (Distributed Network) or MC (Multi-Channel Network) scenarios. DC refers to a terminal device simultaneously accessing two network devices, one of which is the primary network device and the other is the secondary network device. MC refers to a terminal device simultaneously accessing at least three network devices, one of which is the primary network device and the remaining devices are secondary network devices.
[0047] Please see Figure 1 This is an architecture diagram of the DC scenario to which the embodiments of this application are applicable. Figure 1Taking a terminal device and two network devices (i.e., the first network device and the second network device) as an example. The first network device is the primary network device, MN, and the second network device is the secondary network device, SN. The first and second network devices can belong to the same radio access technology (RAT). For example, both the first and second network devices can be LTE base stations or NR base stations. Alternatively, the first and second network devices can belong to different RATs; for example, the first network device can be an LTE base station, and the second network device can be an NR base station. Because the LTE system can be an evolved universal terrestrial radio access (E-UTRA) system, the access method where the terminal device simultaneously accesses both LTE and NR base stations is also called EN-DC. EN-DC is essentially a dual connection between the 4G radio access network (interfaced with the 4G core network) and 5G NR. In EN-DC mode, MN is an LTE base station connected to the evolved packet core (EPC), and SN is an NR base station. In another DC scenario, the terminal device supports NR E-UTRA dual connectivity (NE-DC). In this scenario, MN is an NR base station connected to the 5G core network (5G core, 5GC), and SN is an LTE base station. DC modes using different RATs for MN and SN can be collectively referred to as Multi-RAT dual connectivity (MR-DC). MR-DC has different types, such as EN-DC, or next-generation-RAN E-UTRA dual connectivity (NGEN-DC), which is dual connectivity between the 4G radio access network interfaced with the 5G core network and 5G NR. Furthermore, in yet another DC scenario, for a terminal device that only supports NR, the terminal device can simultaneously access two different NR network devices; this type of connection is called NR-DC. In NR-DC, MN is an NR base station connected to the 5GC, and SN is another NR base station.
[0048] by Figure 1 For example, when deploying both NR and LTE systems simultaneously, the first network device is the LTE base station, and the second network device is the NR base station. It should be noted that... Figure 1 Taking the network architecture of DC as an example, Figure 1The number of terminal devices mentioned is just an example; there could be more or fewer. The number of network devices is also just an example; there could be more or fewer. Figure 1 The communication system may also include a wider variety of devices, such as one or more core network devices, for example, LTE core network devices or NR core network devices. It is understood that LTE core network devices can communicate with LTE network devices. NR core network devices can communicate with NR network devices and / or LTE network devices. In this embodiment, the primary node connected to the terminal device (i.e., the node providing services to the terminal device) is called the source primary node (source MN, S-MN). Other primary nodes can be understood as candidate primary nodes (candidate MN, C-MN), and there can be one or more C-MNs. The secondary node connected to the terminal device is called the source secondary node (source SN, S-SN). Other secondary nodes are candidate secondary nodes (candidate SN, C-SN), and there can be one or more C-SNs. "Source primary node," "source base station," and "source network device" are the same concept and can be substituted unless otherwise specified. "Source secondary node," "source secondary base station," and "source secondary network device" are the same concept and can be substituted unless otherwise specified. "Candidate primary node," "candidate primary base station," and "candidate primary network device" are the same concept and can be substituted unless otherwise specified. "Candidate secondary node," "candidate secondary base station," and "candidate secondary network device" are the same concept and can be substituted unless otherwise specified.
[0049] One or more cells provided by an MN to a terminal device are called an MCG. When there is only one cell in an MCG, that cell is the PCell of the terminal device. An MN can provide one or more MCGs. One or more cells provided by an SN to a terminal device are called an SCG. When there is only one cell in an SCG, that cell is the PSCell of the terminal device. An SN can provide one or more SCGs. In 5G systems, PCells and PSCells can be collectively referred to as special cells (SpCells). When an MCG or an SCG contains multiple cells, each MCG and SCG has one cell as an SpCell, and all other cells are called secondary cells (SCells). In this case, the SCells and SpCells in each cell group perform carrier aggregation to jointly provide services to the terminal device.
[0050] A PCell refers to a cell operating on the primary frequency (or primary carrier). Terminal equipment initiates the initial connection establishment process or the connection reconstruction process on the PCell. During handover, the PCell is designated as the primary cell.
[0051] A PSCell, also known as a primary SCG cell, is a cell belonging to an SCG. A PSCell may include cells where a terminal device is instructed to perform random access or initial physical uplink shared channel (PUSCH) transmission. For example, a cell where the random access procedure is omitted during an SCG change process. A PSCell also includes cells where a terminal device initiates a random access procedure with a secondary network device, or cells where a terminal device skips the random access procedure and initiates data transmission during a secondary network device change process, or cells in a secondary network device that initiate random access during a synchronization reconfiguration process.
[0052] A secondary cell (SCell) is a cell that operates on a secondary carrier. Once an RRC connection is established, an SCell may be configured to provide additional radio resources. In a DC architecture, all cells in both the MCG and SCG, excluding the primary cell, can be referred to as SCells.
[0053] A serving cell can refer to either the primary cell or a secondary cell. The primary cell and all secondary cells of a terminal device constitute the serving cell set for that terminal device. A terminal device in RRC_CONNECTED state, without carrier aggregation (CA) and / or DC configured, has only one serving cell, i.e., PCell. If CA and / or DC are configured, the serving cell set consists of the primary cell and secondary cells. Each component carrier (CC) corresponds to an independent cell.
[0054] In this embodiment, the network device can be an access device, such as a base station or other access network (AN) device, that allows a terminal device to wirelessly access a mobile communication system. The network device can also refer to a device that communicates with the terminal device over the air interface. The network device can include evolved Node Bs (eNBs or e-NodeBs) in LTE systems or Long Term Evolution-Advanced (LTE-A); it can also include next-generation node Bs (gNBs) in NR systems; or, it can include access nodes in wireless-fidelity (Wi-Fi) systems; or, it can be a station, relay station, vehicle-mounted equipment, and future Public Land Mobile Network (PLMN) equipment, device-to-device (D2D) network equipment, machine-to-machine (M2M) network equipment, IoT network equipment, or unmanned aerial vehicle (UAV) equipment. In a V2X system, the access network device can be a roadside unit (RSU). The embodiments of this application do not limit the specific technology or device form used in the network device.
[0055] Furthermore, the base station in this application embodiment may include a centralized unit (CU) and a distributed unit (DU), and multiple DUs may be centrally controlled by a single CU. The CU and DU can be divided according to their respective wireless network protocol layer functions. For example, the functions of the Packet Data Convergence Protocol (PDCP) layer and above are located in the CU, while the functions of protocol layers below PDCP, such as the Radio Link Control (RLC) layer and the Medium Access Control (MAC) layer, are located in the DU. It should be noted that this protocol layer division is merely an example, and other protocol layer divisions are also possible. The radio frequency device may be located remotely, not in the DU, or integrated into the DU, or partially remote and partially integrated into the DU; this application embodiment does not impose any limitations. Additionally, in some embodiments, the control plane (CP) and user plane (UP) of the CU may be separated and implemented as different entities, namely the control plane CU entity (CU-CP entity) and the user plane CU entity (CU-UP entity). The CU's control plane CU-CP also includes a further segmented architecture, dividing the existing CU-CP into CU-CP1 and CU-CP2. CU-CP1 includes various radio resource management functions, while CU-CP2 only includes RRC and PDCP-C functions (i.e., basic control plane signaling functions at the PDCP layer). In this network architecture, signaling generated by the CU can be sent to terminal devices via DU, or signaling generated by terminal devices can be sent to the CU via DU. The DU can directly encapsulate the signaling through the protocol layer and pass it through to the terminal device or CU without parsing it.
[0056] In this embodiment, the terminal device is a device with wireless transceiver capabilities, capable of sending signals to or receiving signals from network devices. The terminal device may include user equipment (UE), sometimes also referred to as a terminal, access station, UE station, remote station, wireless communication device, or user device, etc. The terminal device is used to connect people, objects, machines, etc., and can be widely used in various scenarios, including but not limited to the following: cellular communication, D2D, V2X, machine-to-machine / machine-type communications (M2M / MTC), IoT, virtual reality (VR), augmented reality (AR), industrial control, self-driving, remote medical, smart grid, smart furniture, smart office, smart wearables, smart transportation, smart city, drones, robots, etc. For example, the terminal device may be a mobile phone, tablet, computer with wireless transceiver capabilities, VR terminal, or AR terminal, etc. By way of example and not limitation, in the embodiments of this application, the terminal device can also be a wearable device. The various terminal devices described above, if located in a vehicle (e.g., placed inside or installed inside a vehicle), can all be considered in-vehicle terminal devices. In-vehicle terminal devices are also called on-board units (OBUs). The terminal device of this application can also be an in-vehicle module, in-vehicle component, in-vehicle chip, or in-vehicle unit built into a vehicle as one or more components or units. The vehicle can implement the methods of this application through the built-in terminal device.
[0057] In this application embodiment, the communication device used to implement the functions of a network device or a terminal device can be the network device or terminal device itself, or it can be a device capable of supporting the network device or terminal device to implement the function, such as a chip system. This device can be installed in the network device or terminal device. In the technical solutions provided in the embodiments of this application, the device used to implement the functions of a network device is a base station, and the device used to implement the functions of a terminal device is a UE, are used as examples to describe the technical solutions provided in the embodiments of this application.
[0058] In this application embodiment, the number of nouns, unless otherwise specified, refers to "singular nouns or plural nouns," that is, "one or more." "At least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. For example, A / B means: A or B. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c means: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.
[0059] In this application's embodiments, ordinal numbers such as "first" and "second" are used to distinguish multiple objects, and are not used to limit the size, content, order, timing, application scenario, priority, or importance of the multiple objects. For example, the first measurement gap configuration and the second measurement gap configuration can be the same measurement gap configuration or different measurement gaps, and such names do not indicate differences in the length, priority, application scenario, or importance of these two measurement gaps.
[0060] This application mainly relates to cell handover and cell measurement configuration technologies in DC scenarios. To better understand the solutions provided in this application, the following describes the relevant content regarding cell handover and cell measurement configuration.
[0061] First, let's introduce the relevant information about cell handover.
[0062] 1) Condition-Based Cell Handover (CHO). In CHO, the source base station of the source cell sends CHO configuration information for at least one candidate cell to the UE. This CHO configuration information includes information about the candidate cells and the CHO execution trigger conditions. The CHO execution trigger conditions can be understood as the trigger conditions for the UE to perform cell handover; they are also called CHO trigger conditions, CHO execution conditions, execution conditions, or trigger conditions. Each candidate cell is configured with one or more CHO execution trigger conditions. The candidate cell information can be used to indicate the candidate cell, for example, including the candidate cell global identifier (CGI), or the candidate cell physical cell identifier (PCI) and the corresponding frequency information. Upon receiving the CHO configuration information, the UE measures the candidate cells indicated by the CHO configuration information. If the signal quality of a candidate cell meets the execution trigger conditions, the candidate cell is determined as the target cell. The target cell is the cell that the UE wants to hand over to. Afterward, the UE initiates access to the target cell.
[0063] 2) Primary and secondary cell addition and change (PAC) includes PSCell addition triggered by the MN and PSCell change triggered by the MN or SN. PSCell change refers to the handover of the PSCell accessed by the UE due to UE mobility. For example, the MN (or SN) determines, based on the UE's measurement results, that the signal quality of one PSCell has deteriorated while the signal quality of another PSCell has improved, and the MN (or SN) notifies the UE to perform a PSCell change. A PSCell change can be a handover from a cell of one SN to a cell of another SN, or a handover from a cell of one SN to another cell of the same SN.
[0064] 3) CPAC refers to the combination of CHO and PAC technologies, specifically using CHO technology for adding / changing PSCells. Similar to CHO, in CPAC, the triggering node (MN or SN) also sends CPAC configuration to the UE. This CPAC configuration includes the execution triggering conditions for cell handover, candidate PSCell information, and cell measurement configuration information. Upon receiving the CPAC configuration, if the UE finds a candidate cell that meets the execution triggering conditions (i.e., CPAC is triggered), then that candidate cell is used as the target cell to perform the PSCell addition / change procedure.
[0065] The following section introduces the relevant information regarding the measurement configuration for the community.
[0066] The network device sends a measurement configuration to the UE, which then performs measurements on candidate cells based on this configuration. When the measurement results meet certain conditions, the UE triggers a measurement event report, that is, reports the measurement results to the network device. After receiving the measurement results reported by the UE, the network device can send a handover command to the UE, instructing the UE to hand over from one cell to another. If the network device is configured with a Cell Handover Event (CHO), the UE will initiate a cell handover procedure when the measurement results meet certain triggering conditions. If the network device is configured with a Cell-Based Acceptance Control (CPAC), the UE will initiate a PSCell handover procedure when the measurement results meet certain triggering conditions.
[0067] Measurement configurations may include one or more of the following: measurement objects, measurement gaps, reporting configurations, triggering quantities, or measurement identities.
[0068] The measurement object is the object that the UE performs the measurement on, including the synchronization signal and physical broadcast channel block (SSB), SSB subcarrier spacing, SSB-based measurement timing configuration (SMTC), whitelisted cells or blacklisted cells, etc.
[0069] A measurement gap can be understood as the duration during which the UE tunes its receiver from its current frequency to the frequency to be measured (e.g., a neighboring cell frequency). During the measurement gap, the UE does not transmit or receive data; instead, it tunes its receiver to the frequency to be measured and performs the measurement. At the end of the measurement gap, the UE tunes its receiver to the frequency of the serving cell. For example, for connected inter-frequency and / or inter-system neighboring cell measurements, the UE stops transmitting and receiving signals on the serving cell during the measurement gap, tunes its receiver to the inter-frequency or inter-system frequency, and receives and measures signals from the inter-frequency or inter-system neighboring cell. Network devices can configure measurement gaps for the UE via RRC signaling.
[0070] Report configuration refers to the standards and format by which the UE is triggered to report measurement reports. Trigger quantity is the strategy for triggering event reporting. Measurement ID refers to the set of measurement objects and report configurations.
[0071] In this embodiment, the configuration of the measurement gap involves two frequency ranges (FRs), FR1 and FR2. FR1 includes FRs supported by both LTE and NR systems. FR2 is a higher frequency relative to FR1 and can be considered a FR supported by the NR system. The lowest frequency in FR1 is greater than or equal to 450MHz, and the highest frequency in FR1 is less than or equal to 6GHz. The lowest frequency in FR2 is greater than or equal to 24.25GHz, and the highest frequency in FR2 is less than or equal to 52.6GHz. The configuration of the measurement gap also involves two types of measurement gaps, one type configured for the UE (also called a per-UE gap) and the other type configured for the FRs (also called a per-FR gap). The per-UE gap applies to both FR1 and FR2. The per-FR gap refers to configuring two independent gap modes, namely the FR1 gap and the FR2 gap, for FR1 and FR2 respectively.
[0072] Depending on the UE's ability to support independent FR measurements and network preferences, a per-UE gap or a per-FR gap can be configured. If a per-UE gap is configured, the MN determines the gap mode and related gap-sharing configuration. If a per-FR gap is configured, the configuration of the measurement gap will vary depending on the connection scenario. Several connection scenarios are listed below for detailed explanation.
[0073] In EN-DC and NGEN-DC, MN determines the FR1 gap mode and the associated gap sharing configuration of FR1, while SN determines the FR2 gap mode and the associated gap sharing configuration of FR2; in NE-DC and NR-DC, MN determines the gap modes of FR1 and FR2 and the associated gap sharing configuration.
[0074] In EN-DC and NGEN-DC, the measurement gap configuration from the MN to the UE indicates whether the configuration from the MN is a per-UE gap configuration or an FR1 gap configuration. In other words, the MN provides the UE with the type of measurement gap. Additionally, the MN also indicates the configured measurement gap (per-UE measurement gap or FR1 measurement gap) and the type of measurement gap to the SN. The MN and SN can exchange auxiliary information regarding the measurement gap configuration. For the per-UE gap case, the SN can indicate to the MN the list of SN frequencies configured in FR1 and FR2 that the UE is to be measured. That is, for the MN, the auxiliary information for the measurement gap configuration includes the list of SN frequencies configured in FR1 and FR2 that the UE is to be measured, from the SN. For the per-FR gap case, the SN can indicate to the MN the list of SN frequencies configured in FR1 that the UE is to be measured, and the MN indicates to the SN the list of MN frequencies configured in FR2 that the UE is to be measured. Specifically, for the MN, the auxiliary information for the measurement gap configuration includes the list of SN frequencies configured in FR1 of the UE to be measured from the SN. Similarly, for the SN, the auxiliary information for the measurement gap configuration includes the list of SN frequencies configured in FR2 of the UE to be measured from the MN.
[0075] Understandably, in NE-DC, the MN will also indicate the configured per-UE measurement gap or FR1 measurement gap to the SN. The SN can provide gap confirmation to the MN; if the SN is configured with a per-FR measurement gap, this gap confirmation does not include any frequency list. In NR-DC, the MN can indicate the configured per-UE measurement gap, FR1 measurement gap, or FR2 measurement gap to the SN, as well as the measurement gap type. The SN can indicate to the MN the list of SN frequencies configured in FR1 for the UE to be measured and the list of SN frequencies configured in FR2 for the UE to be measured.
[0076] The content of the measurement objects varies depending on the scenario. For example, network devices configure CHOs, which are for handovers of PCells under the MN. The measurement configuration used by the UE when performing CHO evaluation (i.e., evaluating whether the CHO triggering conditions are met) is sent by the source MN (i.e., the base station providing the current serving cell). In this case, the measurement objects include the frequency points to be measured by the source MN and the frequency points to be measured by the candidate MNs determined by the source MN. In another possible scenario, network devices configure CHOs and CPACs. CPACs are for the addition or change of PSCells under the SN. The source MN configures a CHO for the UE, and for multiple candidate PCells, it can provide PSCell-related configurations corresponding to each candidate PCell. If a candidate PCell triggers a CHO handover, the UE attempts to access that candidate PCell, and if the PSCell under that PCell also meets the CPAC triggering conditions, the UE also attempts to change the PSCell. For example, assuming there are two candidate primary cells (e.g., PCell 1 and PCell 2), the PSCells corresponding to PCell 1 include PSCell 1, PSCell 2, and PSCell 3. The PSCells corresponding to PCell 2 include PSCell 4 and PSCell 5. The network device configures both CHO and CPAC. Accordingly, the specific relationship between the candidate cells of the CHO and CPAC configured by the network device can be: CHO PCell 1 + {CPAC PSCell 1, CPAC PSCell 2, CPAC PSCell 3}; CHO PCell 2 + {CPAC PSCell 4, CPAC PSCell 5}. If PCell 1 meets the CHO execution triggering condition, the UE attempts to access PCell 1. If PSCell 3 under PCell 1 meets the CPAC execution triggering condition, the UE also attempts to change the PSCell. It is understandable that the handover triggering conditions could be met by PCell 1 meeting the CHO execution triggering conditions, or by the corresponding PSCell meeting the CPAC execution triggering conditions. For example, both PCell 1 and PSCell 3 might meet the execution triggering conditions. It is unlikely that a PSCell would meet the CPAC execution triggering conditions while the PCell would not meet the CHO execution triggering conditions.
[0077] If the MN is configured with CHO and CPAC, the UE needs to continuously determine whether there are candidate MNs that meet the CHO execution triggering conditions and whether there are candidate SNs determined by the candidate MNs that meet the CPAC execution triggering conditions. However, the MN only considers the measurement configuration requirements of the CHO and not the measurement configuration requirements of the CPAC. That is, the measurement configuration sent by the MN to the UE does not consider the test frequencies of the candidate SNs. As a result, the UE may only measure some of the frequency points in the candidate SNs. For example, the UE may measure the test frequencies of the SNs that overlap with those of the MN; or the UE may not even measure the test frequencies of the candidate SNs. For example, if the test frequencies of the SNs and the test frequencies of the MNs do not overlap, this reduces the chance of CPAC triggering, i.e., reduces the chance of the UE accessing the PSCell. In addition, since the MN does not consider the test frequencies of the candidate SNs, the measurement gap configured by the MN may be unreasonable, which will affect the measurement performance of the UE.
[0078] In this embodiment, when the MN is configured with CHO and CPAC, the candidate MN can provide the source MN with the measurement frequency points of the candidate SN. The source MN can then configure appropriate measurement objects for the UE based on the measurement frequency points of the candidate SN. For example, the measurement objects configured by the source MN may include the measurement frequency points of the candidate SN. Thus, when the UE evaluates whether the CHO execution triggering conditions are met, it measures not only the frequency points to be measured by the candidate MN but also the frequency points to be measured by the candidate SN. That is, when evaluating whether the CHO execution triggering conditions are met, the CPAC execution triggering conditions are also evaluated, increasing the chance of CPAC triggering and helping the UE complete CPAC more quickly. Furthermore, this facilitates the UE accessing a more suitable cell, thereby improving the communication quality after the UE accesses the cell. Additionally, the source MN can also configure a measurement gap based on the frequency points to be measured by the candidate SN to minimize the impact on the UE's measurement performance.
[0079] The technical solutions provided by the embodiments of this application are described below with reference to the accompanying drawings.
[0080] This application provides a measurement configuration method that can be applied to DC or MC scenarios, for example, in... Figure 1 This method applies to DC scenarios in network equipment. Furthermore, it is suitable for situations where network devices are configured with CHO and CPAC. It is understandable that if a UE switches PCells, it may switch to another PCell provided by the S-MN, or it may switch to a PCell provided by the C-MN. Similarly, if a UE switches PSCells, it may switch to another PSCell provided by the S-SN, or it may switch to a PSCell provided by the C-SN.
[0081] Please see Figure 2This is a flowchart illustrating the measurement configuration method provided in the embodiments of this application. In the following description, the source primary node is denoted as S-MN, the source secondary node as S-SN, the candidate primary node as C-MN, the candidate secondary node as S-SN, and the UE is used as an example.
[0082] S201, S-MN sends a CHO request to one or more C-MNs, and correspondingly, the one or more C-MNs receive the CHO request sent by S-MN.
[0083] S-MN can send CHO requests to each C-MN separately.
[0084] S202, the first C-MN sends a CPA request or CPC request to one or more C-SNs, and correspondingly, the one or more C-SNs receive the CPA request or CPC request sent by the first C-MN.
[0085] It should be understood that if the first C-MN determines that the S-SN exists, then the first C-MN sends a CPC request to one or more C-SNs; if the first C-MN determines that the S-SN does not exist, then the first C-MN sends a CPA request to one or more C-SNs. Alternatively, the first C-MN sends a CPA request to one or more C-SNs by default, that is, regardless of whether the S-SN exists, the first C-MN sends a CPA request to one or more C-SNs.
[0086] The first C-MN is the C-MN that received the CHO request. It should be understood that the first C-MN belongs to one or more of the C-MNs. If one C-MN receives a CHO request, then the first C-MN is that C-MN; if multiple C-MNs receive CHO requests, then the first C-MN is one or more of the multiple C-MNs. After receiving a CHO request, the first C-MN may send a CPA request to the C-SN determined by the first C-MN. One C-MN can determine one or more C-SNs.
[0087] S203, the first C-SN sends a CPA request response to the first C-MN, and correspondingly, the first C-MN receives the CPA request response sent by the first C-SN.
[0088] In another example, S203 can be replaced by: the first C-SN sending a CPC request response to the first C-MN, and correspondingly, the first C-MN receiving the CPC request response sent by the first C-SN.
[0089] It should be understood that the first C-MN sends a CPA request / CPC request to one or more C-SNs, and the first C-MN receives a CPA request response / CPC request response from the first C-SN. The first C-SN is the C-SN that received the CPA request / CPC request. The first C-MN also sends a CPC request / CPC request to one or more C-SNs, and the first C-MN receives a CPC request response / CPC request response from the first C-SN. The first C-SN is the C-SN that received the CPC request / CPC request.
[0090] Taking the example of a first C-MN sending a CPA request to one or more C-SNs, if one C-SN receives the CPA request, then the first C-SN is that C-SN; if multiple C-SNs receive the CPA request, then the first C-SN is one or more of the multiple C-SNs. After receiving the CPA request, the first C-SN can send a CPA request response to the first C-MN. This CPA request response includes the frequency information of the first C-SN, such as the frequency to be tested of the first C-SN. It should be understood that multiple C-SNs that receive the CPA request can send CPA request responses to the first C-MN separately, and the CPA request response sent by any C-SN includes the frequency to be tested of that C-SN. Similarly, if the first C-MN sends a CPC request to one or more C-SNs, and one C-SN receives the CPC request, then the first C-SN is that C-SN; if multiple C-SNs receive the CPC request, then the first C-SN is one or more of the multiple C-SNs. After receiving a CPC request, the first C-SN can send a CPC request response to the first C-MN. This CPC request response includes the frequency information of the first C-SN, such as the frequency to be tested for the first C-SN. It should be understood that multiple C-SNs that have received a CPC request can send CPC request responses to the first C-MN separately, and any CPC request response sent by any C-SN includes the frequency to be tested for that C-SN.
[0091] S204. The first C-MN sends a CHO request response to the S-MN, and correspondingly, the S-MN receives the CHO request response sent by the first C-MN.
[0092] After receiving the CPA request response from the first C-SN, the first C-MN can generate an RRC configuration message for the first C-MN. The RRC configuration message for the first C-MN may include RRC configuration information related to the first C-MN (also called the MN-RRC configuration message) and CPAC configuration for the PSCell managed by the first C-SN (e.g., called the first CPAC configuration). The first CPAC configuration includes the SN-RRC configuration message corresponding to the first C-SN, such as the radio interface configuration corresponding to the first C-SN, and the execution triggering conditions corresponding to the first C-SN. Therefore, it can be considered that the RRC configuration message of the candidate MN includes: the MN-RRC configuration message corresponding to the first C-MN, the SN-RRC configuration message corresponding to the first C-SN, and the execution triggering conditions corresponding to the first C-SN.
[0093] After the first C-MN generates its RRC configuration message, it can send a CHO request response to the S-MN. This CHO request response may include the first C-MN's RRC configuration message, CPAC configuration, and the frequency point to be tested for the first C-SN. Alternatively, the CHO request response can be understood to include: the MN-RRC configuration message corresponding to the first C-MN, the SN-RRC configuration message corresponding to the first C-SN, the execution trigger condition corresponding to the first C-SN, and the frequency point to be tested for the first C-SN.
[0094] S205, S-MN sends the first RRC configuration message to UE, and correspondingly, UE receives the first RRC configuration message sent by S-MN.
[0095] After receiving the CHO request response, the S-MN can determine the measurement configuration, such as the measurement object and the measurement gap. For example, the measurement object may include the frequency points to be measured in the S-MN, the first C-MN, the S-SN, and the first C-SN. The UE measures some or all of the frequency points to be measured in the measurement object according to the measurement configuration to determine the target cell. Since the measurement object includes the frequency points to be measured in the first C-SN, when the UE evaluates whether the CHO triggering conditions are met, it measures not only the frequency points to be measured in the C-MN but also the frequency points to be measured in the first C-SN. That is, when the UE evaluates whether the CHO execution triggering conditions are met, it also evaluates whether the CPAC execution triggering conditions are met. How to configure the measurement gap for the UE will be described in detail below and will not be discussed here.
[0096] After receiving the CHO request response, the S-MN can also determine the CHO configuration and CPAC configuration. To distinguish it from the CPAC configuration in the CHO request response received by the S-MN, the CPAC configuration configured by the S-MN is referred to as the second CPAC configuration. It can be understood that the CHO configuration determined by the S-MN includes the radio interface configurations corresponding to all C-MNs, including the first C-MN, and the execution triggering conditions corresponding to all C-MNs. The second CPAC configuration may include the radio interface configurations corresponding to all C-SNs, including the first C-SN, and the execution triggering conditions corresponding to all C-SNs. The execution triggering conditions corresponding to MNs can also be understood as the execution triggering conditions corresponding to the PCells managed by the MN (also called candidate PCells). The execution triggering conditions corresponding to SNs can also be understood as the execution triggering conditions corresponding to the PSCells managed by the SN (also called candidate PSCells). Candidate PSCells include all PSCells managed by all C-SNs determined by the first C-MN.
[0097] The execution triggering condition corresponding to the candidate MN (e.g., the aforementioned first C-MN), i.e., the first execution triggering condition, is the execution triggering condition for the CHO, and is the triggering condition that the UE must satisfy to switch to a PCell. In other words, the UE only triggers the switch to a PCell if it satisfies the first execution triggering condition corresponding to that PCell. The execution triggering condition corresponding to the candidate SN (e.g., the aforementioned first C-SN), i.e., the second execution triggering condition, is the execution triggering condition for the CPAC, and is the triggering condition that the UE must satisfy to switch to a PSCell. In other words, the UE only triggers the switch to a PSCell if it satisfies the second execution triggering condition corresponding to that PSCell. It can be understood that one candidate PCell corresponds to one first execution triggering condition, and the first execution triggering conditions corresponding to different candidate PCells can be the same or different. Similarly, one candidate PSCell corresponds to one second execution triggering condition, and the second execution triggering conditions corresponding to different candidate PSCells can be the same or different.
[0098] After determining the measurement object and the corresponding measurement gap (e.g., referred to as the first measurement gap), CHO configuration, and second CPAC configuration, the S-MN can provide this information to the UE. For example, the S-MN sends a first RRC configuration message to the UE, which includes the CHO configuration, the second CPAC configuration, the measurement object, and the first measurement gap configuration corresponding to the measurement object. Alternatively, the first RRC configuration message can be understood to include: the radio interface configuration corresponding to all C-MNs, including the first C-MN, and the first execution trigger condition corresponding to all C-MNs; the radio interface configuration corresponding to all C-SNs, including the first C-SN, and the second execution trigger condition corresponding to all C-SNs (i.e., the second execution trigger condition corresponding to the candidate PSCell).
[0099] The first RRC configuration message has multiple implementation forms. The following description uses the CHO request response implementation as an example to illustrate the first RRC configuration message implementation. For ease of description, the second RRC configuration is introduced below, which is the MN RRC configuration message corresponding to the aforementioned first C-MN (also referred to as the C-MN RRC configuration message in this application). In one example, the second RRC configuration message may include: a Candidate Cell RRC configuration element carrying both the C-MN configuration and the C-SN configuration containing the CPAC execution trigger condition. The C-SN configuration containing the CPAC execution trigger condition can also be called the CPAC C-SN configuration. In another example, the Candidate Cell RRC configuration does not contain the CPAC C-SN configuration. For example, the Candidate Cell RRC configuration may only contain the C-MN configuration, or it may contain the C-MN configuration and the configuration of a blind-matched SN. The blind-matched SN refers to an SN that does not require execution trigger conditions. It is understood that the Candidate Cell RRC configuration is merely an illustrative representation of the element name; other names can be used to represent this element, and this application does not impose any limitations.
[0100] The first RRC configuration message can be understood as an RRC configuration message related to S-MN (also referred to as S-MN RRC configuration message in this application).
[0101] In implementation one, the first RRC configuration message includes a second RRC configuration message and a first execution trigger condition corresponding to the first C-MN. The second RRC configuration message includes the radio interface configuration of the first C-MN and the second execution trigger condition corresponding to the candidate PSCell. The information elements in the first RRC configuration message other than the second RRC configuration message also include the identification information of the candidate PSCell and the second execution trigger condition corresponding to the candidate PSCell. The identification information of the candidate PSCell can be the ID of the candidate PSCell, or it can be a list of candidate PSCells, including the IDs of each candidate PSCell. Alternatively, it can be understood that there are two sets of second execution trigger conditions corresponding to the candidate PSCells: one set is located in the information elements of the first RRC configuration message other than the second RRC configuration message, and the other set is located within the second RRC configuration message. In this case, when the UE evaluates the execution trigger conditions of the CHO and CPAC, it only needs to obtain the second execution trigger condition from the first RRC configuration message; there is no need to parse the second RRC configuration message. If CHO is triggered but CPAC is not triggered, after the UE successfully performs primary cell handover, the configuration for the first execution trigger condition in the first RRC configuration message can be deleted, that is, only the second RRC configuration message is retained, so that CPAC evaluation can be performed according to the existing CPAC configuration.
[0102] For example, the first RRC configuration message is implemented as follows:
[0103]
[0104] The Candidate Cell RRC configuration carries the CPAC C-SN configuration. It can be seen that the execution condition of CPAC is included not only in the second RRC configuration message but also in the information elements of the first RRC configuration message other than the second RRC configuration message itself. The second RRC configuration message, i.e., the Candidate Cell RRC configuration, can be encapsulated in a container. The UE obtains the execution condition of CPAC from the Source cell RRC configuration without parsing the Candidate Cell RRC configuration, thus obtaining and evaluating the CPAC execution trigger condition. If the CHO is triggered but the CPAC is not triggered, the UE can delete the configuration for the first execution trigger condition in the Source cell RRC configuration, i.e., only retain the Candidate Cell RRC configuration, so that subsequent CPAC evaluation can be performed according to the stored historical CPAC configuration.
[0105] Since the Candidate Cell RRC configuration element in the second RRC configuration message can carry both C-MN and CPAC C-SN configurations, or it can carry C-MN configurations but not CPAC C-SN configurations, the presence or absence of CPAC C-SN configurations can be indicated by a specification. For example, the Candidate Cell RRC configuration includes an indication of whether or not CPAC C-SN configurations are carried. If both CHO and CPAC are triggered simultaneously, the UE can use the Candidate Cell RRC configuration carrying CPAC C-SN configurations; if CHO is triggered but CPAC is not triggered, the UE can use the Candidate Cell RRC configuration without CPAC C-SN configurations; if the Candidate Cell RRC configuration only contains C-MN configurations, the UE can configure MN only and not SN; if the Candidate Cell RRC configuration includes both C-MN configurations and blind SN configurations, the UE can configure MN and blindly configure SN.
[0106] For example, the first RRC configuration message can be implemented as follows:
[0107]
[0108]
[0109] In the second implementation, the first RRC configuration message includes a second RRC configuration message and a first execution triggering condition corresponding to the first C-MN; wherein, the second RRC configuration message includes the radio air interface configuration of the first C-MN, and the second execution triggering condition corresponding to the candidate PSCell, and the information elements in the first RRC configuration message other than the second configuration RRC message do not include the identification information of the candidate PSCell and the second execution triggering condition corresponding to the candidate PSCell.
[0110] The difference from implementation form one is that the information elements in the first RRC configuration message, excluding the second RRC configuration message, do not include the candidate PSCell identification information and the second execution trigger condition corresponding to the candidate PSCell. That is, the second execution trigger condition corresponding to the candidate PSCell is only contained in the second RRC configuration message. In this case, the terminal device can only obtain the CPAC execution trigger condition by parsing the second RRC configuration message when evaluating the CHO execution trigger condition and the CPAC execution trigger condition. Generally, the second RRC configuration message is only parsed after the UE evaluates that the CHO execution trigger is satisfied; if the CHO is not triggered, there is no need to parse the second RRC configuration message. Similar to implementation form one, if the CHO is triggered but the CPAC is not triggered, after the UE successfully performs a primary cell handover, only the second RRC configuration message can be retained, that is, the configuration for the first execution trigger condition in the first RRC message can be deleted, and subsequent CPAC evaluation can be performed according to the existing CPAC configuration.
[0111] For example, the first RRC configuration message is implemented as follows:
[0112]
[0113] The Candidate Cell RRC configuration carries the CPAC C-SN configuration. It can be seen that the CPAC execution condition is only included in the second RRC configuration message; the first RRC configuration message, excluding the second RRC configuration message, does not include the CPAC execution condition in its information elements. In this case, the UE parses the Candidate Cell RRC configuration to obtain the CPAC execution trigger condition and performs an evaluation. Similar to implementation one, if the CHO is triggered but the CPAC is not triggered, after the UE successfully performs a primary cell handover, it can retain only the Candidate Cell RRC configuration, i.e., delete the configuration for the first execution trigger condition in the Source cell RRC configuration, and subsequently perform CPAC evaluation according to the stored historical CPAC configuration.
[0114] Similar to implementation one, the second RRC configuration message may include: a CandidateCell RRC configuration carrying the CPAC C-SN configuration, and may also include: a CandidateCell RRC configuration without carrying the CPAC C-SN configuration. For example, the first RRC configuration message is implemented as follows:
[0115]
[0116] In implementation form three, the first RRC configuration message includes the second RRC configuration message and the first execution triggering condition corresponding to the first C-MN. The second RRC configuration message includes the radio interface configuration of the first C-MN and the radio interface configuration of the C-SN, but does not include the second execution triggering condition corresponding to the candidate PSCell. Furthermore, the information elements in the first RRC configuration message, excluding the second RRC configuration message, also include the identifier information of the candidate PSCell and the second execution triggering condition corresponding to the candidate PSCell. The difference from implementation form one is that the second RRC configuration message does not include the second execution triggering condition corresponding to the candidate PSCell, but it does include the radio interface configuration of the C-SN. In this case, when the terminal device evaluates the execution triggering condition of CPAC, it can reuse the second execution triggering condition configured outside the second RRC configuration message. That is, the terminal device does not need to parse the second RRC configuration message. Moreover, if CHO is triggered but CPAC is not triggered, after the UE successfully performs primary cell handover, it can retain only the second RRC configuration message, but the terminal device will need to wait for the new CPAC configuration sent by the network device for CPAC evaluation.
[0117] For example, the first RRC configuration message is implemented as follows:
[0118]
[0119]
[0120] The Candidate Cell RRC configuration carries the CPAC C-SN configuration. It can be seen that the CPAC execution condition is only included in the information elements of the first RRC configuration message other than the second RRC configuration message; that is, the second RRC configuration message does not include the CPAC execution condition. In this case, when the UE evaluates the CPAC execution trigger condition, it can reuse the second execution trigger condition configured outside the Candidate Cell RRC configuration. That is, the UE does not need to parse the Candidate Cell RRC configuration. Furthermore, if the CHO is triggered, but the CPAC is not triggered, the UE can retain only the Candidate Cell RRC configuration, but the terminal device will subsequently need to wait for the network device to send a new CPAC configuration for CPAC evaluation.
[0121] Similar to implementation one, the second RRC configuration message may include a CandidateCell RRC configuration carrying the CPAC C-SN configuration, or it may include a Candidate Cell RRC configuration without carrying the CPAC C-SN configuration. For example, the first RRC configuration message is implemented as follows:
[0122]
[0123] It should be noted that the three implementation forms of the first RRC configuration message mentioned above are examples, and the embodiments of this application do not limit the use of any particular implementation method.
[0124] Based on the first RRC configuration message, the UE determines that the execution triggering conditions for CHO and / or CPAC are met, and then sends an RRC Reconfiguration Complete message to the source node. If the S-MN receives the RRC Reconfiguration Complete message from the UE, the S-MN performs early data forwarding; if the S-MN receives the CPAC RRC Reconfiguration Complete message from the UE, the S-MN notifies the S-SN to perform early data forwarding.
[0125] During the CHO (Confirmation of Hazard) procedure, the S-MN sends data to the UE and continuously forwards user data to the target node. Once the S-MN knows that the UE has successfully completed the CHO, it stops transmitting UE data and ceases early data forwarding to the target node. The target node continues to receive and store data from the S-MN and cleans up any user data already sent by the S-MN in its storage based on the early status transfer messages sent by the S-MN, allowing the S-MN to send one or more early status transfer messages to the target node. After the S-MN knows that the UE has successfully completed the CHO, it performs late data forwarding. By performing late data forwarding, the S-MN notifies the MN / SN that the data received after the successful handover has been numbered (i.e., the current data number), so that the MN / SN can number newly received unnumbered data starting from this latest number.
[0126] Similar to the CHO procedure, in the CPAC procedure, if the S-SN exists, the S-SN sends data to the UE and continuously forwards user data to the target node; if the S-SN does not exist, the S-MN continuously forwards user data to the target node. For details, please refer to the process of the S-MN sending data to the UE and forwarding user data to the target node in the aforementioned CHO procedure, which will not be repeated here.
[0127] To better understand the measurement configuration method provided in the embodiments of this application, the following specific examples illustrate a possible flow based on the measurement configuration method provided in the embodiments of this application. It should be understood that in order for the UE to have sufficient time to measure the required frequency points, a suitable measurement gap needs to be configured for the UE. The measurement gap is configured based on the measurement object, and different measurement objects have different configured measurement gaps. Furthermore, the nodes configuring the measurement gap may differ in different scenarios. For example, in EN-DC and NGEN-DC, MN determines the FR1 gap mode and the related gap sharing configuration for FR1, while SN determines the FR2 gap mode and the related gap sharing configuration for FR2; in NE-DC and NR-DC, MN determines the gap modes for FR1 and FR2 and the related gap sharing configuration. The following examples also involve how to configure the measurement gap for the UE.
[0128] Please see Figure 3 This is a flowchart of a first example of a measurement configuration method provided in an embodiment of this application. The example uses the S-MN determining the measurement gap based on the frequency points to be measured of the first S-SN reported by the first C-MN, the frequency points to be measured of the S-MN, the frequency points to be measured of the first C-MN, and the frequency points to be measured of the S-SN.
[0129] S301, S-MN sends a CHO request to one or more C-MNs, and correspondingly, the one or more C-MNs receive the CHO request sent by S-MN. See the relevant content of S201 above for details.
[0130] S302, the first C-MN sends a CPA request to one or more C-SNs, and correspondingly, the one or more C-SNs receive the CPA request sent by the first C-MN. See the relevant content of S202 above for details.
[0131] S303, the first C-SN sends a CPA request response to the first C-MN, and correspondingly, the first C-MN receives the CPA request response sent by the first C-SN. See the relevant content of S203 above for details.
[0132] In another example, the first C-MN can send CPC requests to one or more C-SNs, and the first C-SN can send CPC request responses to the first C-MN, which will not be elaborated further.
[0133] S304. The first C-MN sends a CHO request response to the S-MN, and correspondingly, the S-MN receives the CHO request response sent by the first C-MN.
[0134] The CHO request response includes the frequency point to be tested of the first C-SN. The first C-MN receives the CPA request response sent by the first C-SN, obtains the frequency point to be tested of the first C-SN, and sends it to the S-MN via the CHO request response. Specific parameters can be described in the aforementioned S204, and will not be repeated here. Optionally, the CHO request response includes the identifier of the candidate secondary node and / or the data forwarding address to enable direct data forwarding under CPAC.
[0135] S305 and S-MN send the first RRC configuration message to the UE, and the UE receives the first RRC configuration message sent by S-MN accordingly.
[0136] Upon receiving a CHO request response, the S-MN can generate a first RRC configuration message. This first RRC configuration message includes the configuration of the measurement object and a first measurement gap configuration. This first measurement gap configuration is the configuration of the first measurement gap. Other contents included in the first RRC configuration message can be referred to the relevant content in S205 above, and will not be repeated here. The first measurement gap configuration can be configured according to the frequency points to be measured of the S-MN, the first C-MN, the SN, and the C-SN. It should be understood that the more frequency points, the longer the required measurement time. In this embodiment, the first measurement gap configuration can be configured according to the frequency points to be measured of the S-MN, the first C-MN, the SN, and the C-SN, that is, sufficient time is configured for measurement, which can avoid missing some frequency points to be measured.
[0137] It should be noted that the S-MN can also send the configuration and type of the first measurement gap to the S-SN. The S-SN can then determine whether to configure a gap for the UE, and if so, which gap to configure. For example, in an EN-DC or NGEN-DC scenario, the first measurement gap configuration is for FR1, and the measurement gap type is for FR1. If at least one SN's frequency to be measured is within FR2, the S-SN can also configure FR2 gap measurements for the UE.
[0138] S306. The UE sends an RRC reconfiguration complete message to the S-MN, and the S-MN receives the RRC reconfiguration complete message sent by the UE.
[0139] After receiving the first RRC configuration message, the UE can complete the reconfiguration based on the first RRC configuration message. After completing the reconfiguration, the UE sends an RRC reconfiguration completion message to the S-MN.
[0140] Upon receiving the RRC reconfiguration completion message from the UE, the S-MN begins data forwarding between the S-MN and C-MN. The S-MN also notifies the S-SN to prepare for CPAC data forwarding, which is data forwarding between the S-SN and C-SN.
[0141] CPAC data forwarding includes two methods: direct data forwarding and indirect data forwarding. In direct data forwarding, when the S-MN notifies the S-SN of its readiness to perform data forwarding, it also provides the S-SN with one or more C-SN identifiers and / or corresponding C-SN data forwarding addresses. The S-SN then performs early data forwarding based on the data forwarding addresses of each C-SN. In this case, the CHO request response sent by the C-MN to the S-MN includes the identifiers and / or data forwarding addresses of the one or more C-SNs.
[0142] In an indirect data forwarding method, when the S-MN notifies the S-SN of its readiness to perform data forwarding, it does not provide the S-SN with a data forwarding address or its own data forwarding address. The S-SN forwards the data to the S-MN, which then forwards it to the C-MN, and finally the C-MN forwards it to the C-SN. Therefore, if an indirect data forwarding method is used, the CHO request response may not include the C-SN's identifier and / or data forwarding address.
[0143] S307. The UE determines the target cell and switches to the target cell.
[0144] The UE can measure the measurement objects in the first RRC configuration message, and then determine the target cell that meets the execution triggering conditions based on the measurement results. That is, the UE evaluates the execution triggering conditions of the CHO (first execution triggering condition) and the execution triggering conditions of the CPAC (second execution triggering condition). Depending on the execution triggering conditions met, several situations may exist. For example, both the first and second execution triggering conditions may be met simultaneously, or the first execution triggering condition may be met, but the second execution triggering condition may not be met; the subsequent procedures may differ. These are described below. In the following description, we take the existence of two PCells (e.g., PCell 1 and PCell 2) as an example. The PSCells corresponding to PCell 1 include PSCell 1, PSCell 2, and PSCell 3. The PSCells corresponding to PCell 2 include PSCell 4 and PSCell 5.
[0145] Case 1: The first execution trigger condition and the second execution trigger condition are met.
[0146] In S308a, the UE determines that both CHO and CPAC have been triggered. For example, PCell 2 meets the first execution trigger condition, and PSCell 4 meets the second execution trigger condition. In this case, the UE can attempt to access PCell 2, and can also attempt to change PSCell, i.e., change to PSCell 4. PCell 2 can be understood as the target PCell, and PSCell 4 can be understood as the target PSCell.
[0147] S309a, the UE sends an RRC configuration complete message to the second C-MN, and correspondingly, the second C-MN receives the RRC configuration complete message sent by the UE.
[0148] The second C-MN is the C-MN managing PCell 2. It should be understood that if multiple C-MNs send a CHO request response to the S-MN, the second C-MN is one of those C-MNs that sent the CHO request response. Optionally, the second C-MN is the aforementioned first C-MN. This RRC configuration complete message can be used by the UE to establish a connection with the second C-MN. Additionally, this RRC configuration complete message includes the identification information of the target PSCell. Continuing with the above example, this RRC configuration complete message may include the identifier (ID) of PSCell 4.
[0149] S310a, the second C-MN sends an SN reconfiguration complete message to the second C-SN, and correspondingly, the second C-SN receives the SN reconfiguration complete message sent by the second C-MN.
[0150] The second C-MN can determine, based on the ID of PSCell 4, to send an SN reconfiguration completion message to the second C-SN. This SN reconfiguration completion message can be used by the UE to change the PSCell. The second C-SN is the C-SN managing PSCell 4. It should be understood that the second C-SN belongs to at least one C-SN determined by the second C-MN. If the second C-MN determines a C-SN, then the second C-SN is that C-SN. If the second C-MN determines multiple C-SNs, the second C-SN is one of those multiple C-SNs.
[0151] S311a, the second C-MN sends a handover completion message to the S-MN.
[0152] Once the second C-MN determines that the UE has completed the cell handover, it can send a handover completion message to the S-MN.
[0153] Understandably, if the S-MN determines that late data forwarding will be used for this handover, then upon receiving the handover completion message, it will forward the user data and the corresponding SN status information to the second C-MN. The second C-MN can then use late data forwarding to forward the user data and the corresponding SN status information to the second C-SN.
[0154] Case 2: The first execution trigger condition is met, but the second execution trigger condition is not met.
[0155] In S308b, the UE determines that the CHO has been triggered, but the CPAC has not. For example, PCell 2 meets the first execution trigger condition, while PSCell 4 and PSCell 5 do not meet the second execution trigger condition. In this case, the UE can attempt to access PCell 2, i.e., use PCell 2 as the target PCell.
[0156] S309b: The UE sends an RRC configuration complete message to the second C-MN, and correspondingly, the second C-MN receives the RRC configuration complete message sent by the UE.
[0157] The second C-MN is the C-MN that manages PCell 2. This RRC configuration complete message can be used by the UE to establish a connection with the second C-MN. The UE only performs the handover of the PCell.
[0158] S310b and the second C-MN send a handover completion message to the S-MN.
[0159] The second C-MN determines that the UE has completed the cell handover and sends a handover completion message to the S-MN.
[0160] Understandably, in scenario 2, if the first RRC configuration message is implemented in either form one or form two, the UE can determine to retain the CPAC configuration, meaning it will subsequently use the existing CPAC configuration to determine whether to perform a cell handover. If the first RRC configuration message is implemented in form three, the UE can delete the stored CPAC configuration and subsequently wait for the new CPAC configuration to determine whether to perform a cell handover.
[0161] Please see Figure 4 This is a flowchart of a second example of the measurement configuration method provided in the embodiments of this application. The difference between Example 2 and Example 1 is that the first C-MN can configure a measurement gap according to the frequency point to be measured of the first S-SN and the frequency point to be measured of the first C-MN, and send the measurement gap to the S-MN.
[0162] S401, S-MN sends a CHO request to one or more C-MNs, and correspondingly, the one or more C-MNs receive the CHO request sent by S-MN. See the relevant content of S301 above for details.
[0163] S402, the first C-MN sends a CPA request to one or more C-SNs, and correspondingly, the one or more C-SNs receive the CPA request sent by the first C-MN. See the relevant content of S302 above for details.
[0164] S403, the first C-SN sends a CPA request response to the first C-MN, and correspondingly, the first C-MN receives the CPA request response sent by the first C-SN. See the relevant content of S303 above for details.
[0165] In another example, the first C-MN can send CPC requests to one or more C-SNs, and the first C-SN can send CPC request responses to the first C-MN, which will not be elaborated further.
[0166] S404. The first C-MN sends a CHO request response to the S-MN, and correspondingly, the S-MN receives the CHO request response sent by the first C-MN.
[0167] The CHO request response may include the frequency point to be tested of the first C-SN and a second measurement gap configuration. The second measurement gap is a measurement gap that the first C-MN can configure based on the frequency point to be tested of the first S-SN and the frequency point to be tested of the first C-MN. This can also be understood as the first C-MN, in addition to providing the frequency point to be tested of the first C-SN to the S-MN, can also configure a gap, such as the second measurement gap, based on the frequency point to be tested of the first C-SN and its own frequency point to be tested. For the S-MN, if it receives the second measurement gap configuration sent by the first C-MN, it can determine the first measurement gap based on the second measurement gap configuration, the frequency point to be tested of the S-MN, and the frequency point to be tested of the S-SN. This can also be understood as the second measurement gap being used to assist the S-MN in configuring a more suitable gap for the UE. For example, if the first measurement gap is greater than the second measurement gap, the S-MN can configure the first measurement gap for the UE; conversely, if the second measurement gap is greater than the first measurement gap, the S-MN can configure the second measurement gap for the UE, thus allowing the UE sufficient time to complete the measurement of the required frequency points.
[0168] In S405, the S-MN sends the first RRC configuration message to the UE, and correspondingly, the UE receives the first RRC configuration message sent by the S-MN. For details, please refer to the relevant content in S305 above; it will not be repeated here. Figure 3 The process is similar; the S-MN can also send the configuration and measurement gap type of the first measurement gap to the S-SN. See the attached document for details. Figure 3 The details of the embodiments will not be repeated here.
[0169] S406: The UE sends an RRC reconfiguration complete message to the S-MN, and the S-MN receives the RRC reconfiguration complete message sent by the UE. For details, please refer to the relevant content in S306 above; it will not be repeated here.
[0170] S407. The UE determines the target cell and switches to the target cell.
[0171] Similar to S307, there are two scenarios depending on the execution trigger conditions. Scenario 1 involves executing S408a-S411a, which will be detailed in S308a-S311a. Similarly, Scenario 2 involves executing S408b-S410b, which will be detailed in S308b-S310b.
[0172] Case 1: Both the first and second execution trigger conditions are met.
[0173] In S408a, the UE determines that both CHO and CPAC have been triggered. For example, PCell 2 meets the first execution trigger condition, and PSCell 4 meets the second execution trigger condition. In this case, the UE can attempt to access PCell 2, and can also attempt to change PSCell, i.e., change to PSCell 4. PCell 2 can be understood as the target PCell, and PSCell 4 can be understood as the target PSCell.
[0174] S409a, the UE sends an RRC configuration complete message to the second C-MN, and correspondingly, the second C-MN receives the RRC configuration complete message sent by the UE.
[0175] The second C-MN is the C-MN that manages PCell 2. This RRC configuration completion message includes the identification information of the target PSCell. Continuing with the example above, this RRC configuration completion message could include the ID of PSCell 4.
[0176] S410a, the second C-MN sends an SN reconfiguration complete message to the second C-SN, and correspondingly, the second C-SN receives the SN reconfiguration complete message sent by the second C-MN.
[0177] The second C-MN can determine the SN reconfiguration completion message to be sent to the second C-SN based on the ID of PSCell 4. This SN reconfiguration completion message can be used by the UE to change the PSCell.
[0178] S411a, the second C-MN sends a handover completion message to the S-MN.
[0179] Once the second C-MN determines that the UE has completed the cell handover, it can send a handover completion message to the S-MN.
[0180] Case 2: The first execution trigger condition is met, but the second execution trigger condition is not met.
[0181] In S408b, the UE determines that the CHO has been triggered, but the CPAC has not. For example, PCell 2 meets the first execution trigger condition, while PSCell 4 and PSCell 5 do not meet the second execution trigger condition. In this case, the UE can attempt to access PCell 2, i.e., use PCell 2 as the target PCell.
[0182] S409b: The UE sends an RRC configuration complete message to the second C-MN, and correspondingly, the second C-MN receives the RRC configuration complete message sent by the UE.
[0183] The second C-MN is the C-MN that manages PCell 2. This RRC configuration complete message can be used by the UE to establish a connection with the second C-MN. The UE only performs the handover of the PCell.
[0184] S410b, the second C-MN sends a handover completion message to the S-MN.
[0185] The second C-MN determines that the UE has completed the cell handover and sends a handover completion message to the S-MN.
[0186] The difference between Example 2 and Example 1 is that the first C-MN can be configured with a second measurement gap and provided to the S-MN. The similarities between Example 2 and Example 1 can be found in the relevant introduction to Example 1, and will not be repeated here.
[0187] Please see Figure 5 This is a flowchart illustrating a third example of the measurement configuration method provided in this application. In Example 3, the S-MN provides the frequency points to be measured within FR2 to the S-SN, which then configures the measurement gap within FR2 for the UE. The S-MN can configure the measurement gap within FR1. Alternatively, it can be understood that the S-MN and S-SN negotiate and complete the gap configuration, thereby enabling the configuration of measurement gaps in both EN-DC and NGEN-DC scenarios.
[0188] S501, S-MN sends a CHO request to one or more C-MNs, and correspondingly, the one or more C-MNs receive the CHO request sent by S-MN. See the relevant content of S301 above for details.
[0189] S502, the first C-MN sends a CPA request to one or more C-SNs, and correspondingly, the one or more C-SNs receive the CPA request sent by the first C-MN. See the relevant content of S302 above for details.
[0190] S503, the first C-SN sends a CPA request response to the first C-MN, and correspondingly, the first C-MN receives the CPA request response sent by the first C-SN. See the relevant content of S303 above for details.
[0191] In another example, the first C-MN can send CPC requests to one or more C-SNs, and the first C-SN can send CPC request responses to the first C-MN, which will not be elaborated further. In S504, the first C-MN sends a CHO request response to the S-MN, and correspondingly, the S-MN receives the CHO request response sent by the first C-MN. For details, please refer to the relevant content in S404 above, which will not be repeated here.
[0192] S505, S-MN sends measurement frequency information to S-SN, and correspondingly, S-SN receives the measurement frequency information sent by S-MN. This measurement frequency information indicates the frequency point to be measured within FR2 of the frequency points to be measured of the first C-SN. It can be understood that the frequency points to be measured of S-MN and the first C-MN are both located within FR1, and the frequency points to be measured of S-SN and the first C-SN can be located within FR1 or FR2. However, if a measurement gap is configured for FR, S-MN can only determine the measurement gap configuration within FR1. Therefore, S-MN can provide the frequency points to be measured within FR2 of the first C-SN's frequency points to be measured, so that S-SN can determine the measurement gap configuration within FR2.
[0193] S506 and S-SN determine the third measurement gap based on the measurement frequency information.
[0194] The S-SN determines the third measurement gap based on the frequency point within FR2 in the frequency point to be measured of the first C-SN.
[0195] S507, S-SN sends the third measurement gap configuration to the UE, and the UE receives the third measurement gap sent by S-SN accordingly.
[0196] The S-SN can provide the UE with the measurement gap of the frequency point to be measured within FR2, i.e., the third measurement gap.
[0197] S508 and S-MN send the first RRC configuration message to the UE, and the UE receives the first RRC configuration message sent by S-MN accordingly.
[0198] The difference from S405 is that the measurement configuration in the first RRC configuration message includes a measurement gap configuration corresponding to the frequency point to be tested within FR1, for example, referred to as the fourth measurement gap configuration, which is configured by the S-MN based on the frequency point to be tested located within FR1. For the UE, the measurement gap configuration comes from two sources: one part comes from the S-MN, i.e., the measurement gap configuration of the frequency point to be tested located within FR1, and the other part comes from the S-SN, i.e., the measurement gap configuration of the frequency point to be tested located within FR2. In this example, since the S-MN and S-SN negotiate to complete the configuration of the measurement gap, it is applicable to both EN-DC and NGEN-DC scenarios.
[0199] S509: The UE sends an RRC reconfiguration complete message to the S-MN, and the S-MN receives the RRC reconfiguration complete message sent by the UE. For details, please refer to the relevant content in S306 above, which will not be repeated here.
[0200] S510, the UE determines the target cell and switches to the target cell.
[0201] Similar to S307, there are two scenarios depending on the execution trigger conditions. Scenario 1 executes S511a-S514a, see S308a-S311a for details, which will not be repeated here. Similarly, scenario 2 executes S511b-S513b, see S308b-S310b for details, which will not be repeated here.
[0202] Case 1: The first execution trigger condition and the second execution trigger condition are met.
[0203] In S511a, the UE determines that both CHO and CPAC have been triggered. For example, PCell 2 meets the first execution trigger condition, and PSCell 4 meets the second execution trigger condition. In this case, the UE can attempt to access PCell 2, and can also attempt to change PSCell, i.e., change to PSCell 4. PCell 2 can be understood as the target PCell, and PSCell 4 can be understood as the target PSCell.
[0204] S512a, the UE sends an RRC configuration complete message to the second C-MN, and correspondingly, the second C-MN receives the RRC configuration complete message sent by the UE.
[0205] The second C-MN is the C-MN that manages PCell 2. This RRC configuration completion message includes the identification information of the target PSCell. Continuing with the example above, this RRC configuration completion message could include the ID of PSCell 4.
[0206] S513a, the second C-MN sends an SN reconfiguration complete message to the second C-SN, and correspondingly, the second C-SN receives the SN reconfiguration complete message sent by the second C-MN.
[0207] The second C-MN can determine the SN reconfiguration completion message to be sent to the second C-SN based on the ID of PSCell 4. This SN reconfiguration completion message can be used by the UE to change the PSCell.
[0208] S514a, the second C-MN sends a handover completion message to the S-MN.
[0209] Once the second C-MN determines that the UE has completed the cell handover, it can send a handover completion message to the S-MN.
[0210] Case 2: The first execution trigger condition is met, but the second execution trigger condition is not met.
[0211] In S511b, the UE determines that the CHO has been triggered, but the CPAC has not. For example, PCell 2 meets the first execution trigger condition, while PSCell 4 and PSCell 5 do not meet the second execution trigger condition. In this case, the UE can attempt to access PCell 2, i.e., use PCell 2 as the target PCell.
[0212] S512b: The UE sends an RRC configuration complete message to the second C-MN, and correspondingly, the second C-MN receives the RRC configuration complete message sent by the UE.
[0213] The second C-MN is the C-MN that manages PCell 2. This RRC configuration complete message can be used by the UE to establish a connection with the second C-MN. The UE only performs the handover of the PCell.
[0214] S513b, the second C-MN sends a handover completion message to the S-MN.
[0215] The second C-MN determines that the UE has completed the cell handover and sends a handover completion message to the S-MN.
[0216] The difference between Example 3 and Example 1 is that the S-MN can provide the S-SN with the test frequency points located within FR2 from the candidate SN's test frequency points. The S-SN then provides the UE with the measurement gap configuration corresponding to FR2, and the S-MN provides the UE with the measurement gap configuration corresponding to FR1, thus making it applicable to both EN-DC and NGEN-DC scenarios. The similarities between Example 3 and Example 1 can be found in the relevant introduction to Example 1, and will not be repeated here.
[0217] Please see Figure 6 This is a flowchart illustrating a fourth example of the measurement configuration method provided in this application. In Example 4, the first C-SN can configure a measurement gap corresponding to FR2 and instruct it to the first C-MN. The first C-MN instructs the S-MN to instruct the measurement gap corresponding to FR2. The S-MN instructs the S-SN to instruct the measurement gap corresponding to FR2. Finally, the S-SN configures the measurement gap for the UE based on the measurement gap instructing the S-MN to instruct the measurement gap corresponding to FR2.
[0218] S601, S-MN sends a CHO request (or CPC request) to one or more C-MNs, and correspondingly, the one or more C-MNs receive the CHO request (or CPC request) sent by S-MN. For details, please refer to the relevant content of S301 above, which will not be repeated here.
[0219] S602, the first C-MN sends a CPA request (or CPC request response) to one or more C-SNs, and correspondingly, the one or more C-SNs receive the CPA request (or CPC request response) sent by the first C-MN. For details, please refer to the relevant content of S302 above, which will not be repeated here.
[0220] S603, the first C-SN sends a CPA request response to the first C-MN, and correspondingly, the first C-MN receives the CPA request response sent by the first C-SN.
[0221] The difference from Example 1 is that the CPA request response includes the measurement gap configuration determined by the first C-SN based on the frequency point to be measured within FR2, i.e., the measurement gap configuration corresponding to FR2. For details regarding other contents included in the CAP request response, please refer to the aforementioned description of S303, which will not be repeated here.
[0222] S604. The first C-MN sends a CHO request response to the S-MN, and correspondingly, the S-MN receives the CHO request response sent by the first C-MN.
[0223] The difference from Example 1 is that this CHO request response also includes the measurement gap configuration corresponding to FR2. For details regarding other components included in the CHO request response, please refer to the aforementioned description in S304; they will not be repeated here.
[0224] S605, S-MN sends the third measurement gap configuration and measurement gap type to S-SN, and correspondingly, S-SN receives the third measurement gap configuration and measurement gap type sent by S-MN. The measurement gap type indicates the type of the third measurement gap configuration, such as per-UE gap or per-FR gap.
[0225] The third measurement gap configuration can be obtained by S-MN from the CHO request response, or it can be a measurement gap configuration redefined by S-MN based on the measurement gap configuration obtained from the CHO request response.
[0226] S606, S-SN sends the fifth measurement gap configuration to the UE, and the UE receives the fifth measurement gap sent by S-SN accordingly.
[0227] Upon receiving the third measurement gap configuration and its type, the S-SN can configure a measurement gap corresponding to FR2 for the UE, such as the fifth measurement gap. If the third measurement gap type indicates a per-FR gap, the S-SN can use the third measurement gap configuration as the fifth measurement gap configuration. Alternatively, the S-SN can determine the fifth measurement gap configuration based on the third measurement gap configuration and its own measured frequency point at FR2.
[0228] S607, S-MN sends the first RRC configuration message to UE, and correspondingly, UE receives the first RRC configuration message sent by S-MN.
[0229] The difference from Example 1 is that the measurement configuration in the first RRC configuration message includes the measurement gap configuration for the frequency point to be measured within FR1. For other contents included in the first RRC configuration message, please refer to the relevant description in S205 above, which will not be repeated here.
[0230] S608: The UE sends an RRC reconfiguration complete message to the S-MN, and the S-MN receives the RRC reconfiguration complete message sent by the UE. For details, please refer to the relevant content in S306 above, which will not be repeated here.
[0231] S609, The UE determines the target cell and switches to the target cell.
[0232] Similar to S510, there are two scenarios depending on the execution trigger conditions. Scenario 1 executes S610a-S613a, see S511a-S514a for details, which will not be elaborated further. Similarly, scenario 2 executes S610b-S612b, see S511b-S513b for details, which will not be elaborated further.
[0233] Case 1: The first execution trigger condition and the second execution trigger condition are met.
[0234] S610a, UE determines that both CHO and CPAC are triggered.
[0235] S611a, the UE sends an RRC configuration complete message to the second C-MN, and correspondingly, the second C-MN receives the RRC configuration complete message sent by the UE. The second C-MN is the C-MN that manages the target PCell. The RRC configuration complete message includes the identification information of the target PCell.
[0236] S612a, the second C-MN sends an SN reconfiguration complete message to the second C-SN, and correspondingly, the second C-SN receives the SN reconfiguration complete message sent by the second C-MN.
[0237] S613a, the second C-MN sends a handover completion message to the S-MN.
[0238] Case 2: The first execution trigger condition is met, but the second execution trigger condition is not met.
[0239] S610b and UE determine that CHO is triggered, but CPAC is not triggered.
[0240] S611b: The UE sends an RRC configuration complete message to the second C-MN, and correspondingly, the second C-MN receives the RRC configuration complete message sent by the UE. The second C-MN is the C-MN managing the target PCell. This RRC configuration complete message can be used by the UE to establish a connection with the second C-MN. The UE only performs PCell handover.
[0241] S612b, the second C-MN sends a handover completion message to the S-MN.
[0242] The difference between Example 4 and Example 3 is that the S-MN can determine the measurement gap based on the frequency point to be measured of the C-SN, and provide this measurement gap and its type to the S-SN. The S-SN then provides the UE with the measurement gap configuration corresponding to FR2, and the S-MN provides the UE with the measurement gap configuration corresponding to FR1, thus making it applicable to both EN-DC and NGEN-DC scenarios. The similarities between Example 4 and Example 3 can be found in the relevant introduction to Example 3, and will not be repeated here.
[0243] In this embodiment, to expedite CPAC execution, both CHO and CPAC can be configured. When both CHO and CPAC are configured, the C-MN can provide the C-SN's test frequency to the S-MN. The S-MN can then configure the measurement target based on the C-SN's test frequency, enabling the terminal device to measure both the C-SN and S-SN's test frequencies when evaluating whether the CHO trigger conditions are met. This means it also evaluates whether the CPAC trigger conditions are met, increasing the chance of CPAC triggering. This allows the terminal device to complete CPAC more quickly and facilitates access to a more suitable target cell, improving communication quality after accessing the target cell.
[0244] Furthermore, through the method provided in this application embodiment, S-MN and S-SN can negotiate and complete the configuration of the measurement gap. For example, S-MN can provide the frequency point to be measured located within FR2 to S-SN. S-SN configures the measurement gap corresponding to FR2 and provides it to the terminal device. S-MN provides the measurement gap corresponding to FR1 to the terminal device and provides it to the terminal device. This method can be applied to the measurement gap configuration in both EN-DC and NGEN-DC scenarios.
[0245] The embodiments provided in this application describe the methods from the perspectives of terminal devices, source master nodes, candidate master nodes, candidate auxiliary nodes, and the interaction between source and auxiliary nodes. To implement the functions of the methods provided in the embodiments of this application, the source master node and candidate master node may include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.
[0246] The following describes, with reference to the accompanying drawings, the communication device used to implement the above method in the embodiments of this application.
[0247] Figure 7 This is a schematic block diagram of a communication device 700 provided in an embodiment of this application. The communication device 700 may include a processing module 710 and a transceiver module 720. Optionally, it may also include a storage unit, which can be used to store instructions (code or program) and / or data. The processing module 710 and the transceiver module 720 may be coupled to the storage unit. For example, the processing module 710 may read instructions (code or program) and / or data from the storage unit to implement a corresponding method. The above modules may be set independently, or partially or completely integrated.
[0248] In some possible implementations, the communication device 700 can correspond to the behavior and function of the source master node (S-MN) in the above method embodiments. The communication device 700 can be the source master node, or a component (e.g., a chip or circuit) applied in the source master node, or a chip or chipset in the source master node, or a part of a chip used to perform related method functions.
[0249] For example, communication device 700 implements Figures 2-6The method executed by S-MN in any of the embodiments shown. The transceiver module 720 can be used to send CHO requests to one or more candidate master nodes and receive CHO request responses sent by a first candidate master node. The CHO request response includes CHO configuration, a first CPAC configuration, and the frequency point to be measured for the candidate auxiliary node. The first candidate master node belongs to the one or more candidate master nodes. The processing module 710 can be used to determine a first RRC configuration message, which includes CHO configuration, a second CPAC configuration, and a measurement configuration. The second CPAC configuration is determined based on the first CPAC configuration. The measurement configuration includes the measurement object and the corresponding first measurement gap configuration. The measurement object includes the frequency point to be measured for the source master node, the frequency point to be measured for the first candidate master node, the frequency point to be measured for the auxiliary master node, and the frequency point to be measured for the candidate auxiliary node. The transceiver module 720 is also used to send the first RRC configuration message to the terminal device.
[0250] As an optional implementation, the processing module 710 is further configured to determine a first measurement gap configuration based on the measurement object; the transceiver module 720 is further configured to send the first measurement gap configuration and measurement gap type to the source auxiliary node.
[0251] As an optional implementation, the CHO request response also includes a second measurement gap configuration, which is determined based on the test frequency of the first candidate primary node and the test frequency of the candidate secondary node. The processing module 710 is further configured to determine the first measurement gap configuration based on the second measurement gap configuration; the transceiver module 720 is further configured to send the first measurement gap configuration and the measurement gap type to the source secondary node.
[0252] As an optional implementation, the CHO request response also includes a third measurement gap configuration, which is configured based on the frequency points within FR2 of the candidate auxiliary node's test frequency points.
[0253] As an optional implementation, the transceiver module 720 is also used to send measurement frequency information to the source auxiliary node, which indicates the frequency point located within FR2 among the test frequencies of the candidate auxiliary node.
[0254] As an optional implementation, the lowest frequency of FR2 is greater than or equal to 24.25 GHz, and the highest frequency of FR2 is less than or equal to 52.6 GHz.
[0255] As an optional implementation, the processing module 710 is also used to determine the fourth measurement gap configuration based on the test frequency of the candidate auxiliary node, wherein the test frequency of the candidate auxiliary node is a frequency located within FR1.
[0256] As an optional implementation, the CHO request response includes the identifier of the candidate secondary node and / or the address for data forwarding.
[0257] As an optional implementation, the first RRC configuration message includes a second RRC configuration message and a first execution triggering condition corresponding to the first candidate master node. The second RRC configuration message includes the radio interface configuration of the first candidate master node, the radio interface configuration of the candidate secondary node, and the second execution triggering condition corresponding to the candidate PSCell. Furthermore, the information elements in the first RRC configuration message other than the second RRC configuration message also include the identification information of the candidate PSCell and the second execution triggering condition. The candidate PSCell is managed by the candidate secondary node.
[0258] As an optional implementation, the first RRC configuration message includes a second RRC configuration message and a first execution triggering condition corresponding to the first candidate master node. The second RRC configuration message includes the radio interface configuration of the first candidate master node, the radio interface configuration of the candidate secondary node, and the second execution triggering condition corresponding to the candidate PSCell. Furthermore, the information cells in the first RRC configuration message other than the second RRC configuration message do not include the identification information of the candidate PSCell or the second execution triggering condition. The candidate PSCell is managed by the candidate secondary node.
[0259] As an optional implementation, the first RRC configuration message includes a second RRC configuration message and a first execution triggering condition corresponding to the first candidate master node. The second RRC configuration message includes the radio interface configuration of the first candidate master node and the radio interface configuration of the candidate slave node. The second RRC configuration message does not include the second execution triggering condition corresponding to the candidate PSCell. Furthermore, the information cells in the first RRC configuration message other than the second RRC configuration message also include the identification information of the candidate PSCell and the second execution triggering condition. The candidate PSCell is managed by the candidate slave node.
[0260] For example, communication device 700 implements... Figures 2-6A method executed by the first candidate master node in any embodiment. The transceiver module 720 is configured to receive a CHO request sent by the source master node, send a CPA request to the candidate auxiliary node, and receive a CPA request response from the candidate auxiliary node, wherein the CPA request response includes the frequency point to be tested of the candidate auxiliary node. The processing module 710 is configured to determine the CHO request response, which includes CHO configuration, first CPAC configuration information, and the frequency point to be tested of the candidate auxiliary node. The transceiver module 720 is further configured to send a CHO request response to the source master node, which includes CHO configuration, first CPAC configuration, and the frequency point to be tested of the candidate auxiliary node. Alternatively, the transceiver module 720 is configured to receive a CHO request sent by the source master node, send a CPC request to the candidate auxiliary node, and receive a CPC request response from the candidate auxiliary node, wherein the CPC request response includes the frequency point to be tested of the candidate auxiliary node. The processing module 710 is configured to determine the CHO request response, which includes CHO configuration, first CPAC configuration, and the frequency point to be tested of the candidate auxiliary node. The transceiver module 720 is also used to send a CHO request response to the source master node. The CHO request response includes the CHO configuration, the first CPAC configuration, and the frequency point to be tested for the candidate auxiliary node.
[0261] As an optional implementation, the CHO request response includes all test frequencies of the candidate auxiliary nodes.
[0262] As an optional implementation, the CHO request response includes the identifier of the candidate secondary node and / or the address for data forwarding.
[0263] As an optional implementation, the processing module 710 is also used to determine the measurement gap configuration based on the frequency points to be measured of the candidate auxiliary nodes; the transceiver module 720 is also used to send the measurement gap configuration to the source master node.
[0264] It should be understood that the processing module 710 in the embodiments of this application can be implemented by a processor or processor-related circuit components, and the transceiver module 720 can be implemented by a transceiver or transceiver-related circuit components or a communication interface.
[0265] Figure 8This is a schematic block diagram of a communication device 800 provided in an embodiment of this application. The communication device 800 can be a source master node, capable of implementing the functions of the source master node in the method provided in this application. The communication device 800 can also be a device that supports the source master node in implementing the corresponding functions in the method provided in this application, wherein the communication device 800 can be a chip system. In this application embodiment, the chip system can be composed of chips or may include chips and other discrete devices. Specific functions can be found in the description of the above method embodiments. The communication device 800 can also be a candidate master node, capable of implementing the functions of the first candidate master node in the method provided in this application. The communication device 800 can also be a device that supports the candidate master node in implementing the corresponding functions in the method provided in this application, wherein the communication device 800 can be a chip system. In this application embodiment, the chip system can be composed of chips or may include chips and other discrete devices. Specific functions can be found in the description of the above method embodiments.
[0266] The communication device 800 includes one or more processors 801, which can be used to implement or support the communication device 800 in implementing the functions of the source master node in the method provided in the embodiments of this application. See the detailed description in the method examples for details, which will not be repeated here. The one or more processors 801 can also be used to implement or support the communication device 800 in implementing the functions of the first candidate master node in the method provided in the embodiments of this application. See the detailed description in the method examples for details, which will not be repeated here. The processor 801 can also be called a processing unit or processing module, and can implement certain control functions. The processor 801 can be a general-purpose processor or a dedicated processor, etc. For example, it includes: a central processing unit, an application processor, a modem processor, a graphics processor, an image signal processor, a digital signal processor, a video codec processor, a controller, a memory, and / or a neural network processor, etc. The central processing unit can be used to control the communication device 800, execute software programs, and / or process data. Different processors can be independent devices or integrated into one or more processors, for example, integrated on one or more application-specific integrated circuits.
[0267] Optionally, the communication device 800 includes one or more memories 802 for storing instructions 804, which can be executed on the processor 801 to cause the communication device 800 to perform the method described in the above method embodiments. The memories 802 and the processor 801 can be separately configured or integrated together, or they can be considered coupled. The coupling in this embodiment is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, used for information exchange between devices, units, or modules. The processor 801 may operate in conjunction with the memory 802. At least one of the at least one memories may be included in the processor. It should be noted that the memory 802 is not mandatory, so in... Figure 8 The image is indicated by a dashed line.
[0268] Optionally, the memory 802 may also store data. The processor and memory may be configured separately or integrated together. In this embodiment, the memory 802 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or it may be volatile memory, such as random-access memory (RAM). Memory is any other medium capable of carrying or storing desired program code in the form of instructions or data structures that can be accessed by a computer, but is not limited thereto. The memory in this embodiment may also be a circuit or any other device capable of implementing storage functions for storing program instructions and / or data.
[0269] Optionally, the communication device 800 may include instructions 803 (sometimes referred to as code or program), which can be executed on the processor to cause the communication device 800 to perform the methods described in the above embodiments. Data may be stored in the processor 801.
[0270] Optionally, the communication device 800 may further include a transceiver 805 and an antenna 806. The transceiver 805 may be referred to as a transceiver unit, transceiver module, transceiver, transceiver circuit, transceiver, input / output interface, etc., and is used to realize the transmission and reception functions of the communication device 800 through the antenna 806.
[0271] The processor 801 and transceiver 805 described in this application can be implemented on integrated circuits (ICs), analog ICs, radio frequency identification (RFID) integrated circuits, mixed-signal ICs, ASICs, printed circuit boards (PCBs), or electronic devices. The communication apparatus described herein can be a standalone device (e.g., a standalone integrated circuit, a mobile phone, etc.) or a part of a larger device (e.g., a module embedded in other devices). For details, please refer to the foregoing descriptions of terminal devices and network devices; further details will not be repeated here.
[0272] Optionally, the communication device 800 may further include one or more of the following components: a wireless communication module, an audio module, an external memory interface, internal memory, a universal serial bus (USB) interface, a power management module, an antenna, a speaker, a microphone, an input / output module, a sensor module, a motor, a camera, or a display screen, etc. It is understood that in some embodiments, the communication device 800 may include more or fewer components, or some components may be integrated, or some components may be separated. These components may be implemented in hardware, software, or a combination of software and hardware.
[0273] It should be noted that the communication device in the above embodiments can be a source master node (or a first candidate master node), a circuit, a chip applied in the source master node (or the first candidate master node), or other combined devices or components having the above-mentioned source master node functions (or first candidate master node). When the communication device is a source master node (or the first candidate master node), the transceiver module can be a transceiver, which may include an antenna and radio frequency circuits, etc., and the processing module can be a processor, such as a central processing unit (CPU). When the communication device is a component having the above-mentioned source master node (or first candidate master node) functions, the transceiver module can be a radio frequency unit, and the processing module can be a processor. When the communication device is a chip system, it can be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-a-chip (SoC), a CPU, a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips. The processing module can be the processor of the chip system. The transceiver module or communication interface can be the input / output interface or interface circuit of the chip system. For example, the interface circuit can be a code / data read / write interface circuit. This interface circuit can be used to receive code instructions (stored in memory, which can be read directly from memory or through other devices) and transmit them to the processor; the processor can then execute the code instructions to perform the methods described in the above method embodiments. As another example, the interface circuit can also be a signal transmission interface circuit between the communication processor and the transceiver.
[0274] When the communication device is a chip-based device or circuit, it may include a transceiver unit and a processing unit. The transceiver unit may be an input / output circuit and / or a communication interface; the processing unit may be an integrated processor, microprocessor, or integrated circuit.
[0275] This application also provides a communication system, specifically, the communication system includes a source master node, at least one candidate master node, at least one candidate slave node, a source slave node, and a terminal device. Exemplarily, the communication system includes components for implementing the above. Figures 2-6The method involves one or more graphs, including the source master node, the first candidate master node, the first candidate auxiliary node, and the terminal device. Please refer to the relevant descriptions in the above method embodiments for details, which will not be repeated here.
[0276] This application also provides a computer-readable storage medium, including instructions that, when executed on a computer, cause the computer to perform... Figures 2-6 The method executed by one or more first candidate master nodes in the graph. Alternatively, when it runs on a computer, it causes the computer to execute... Figures 2-6 The method executed by one or more source master nodes in the graph.
[0277] This application also provides a computer program product, including instructions that, when run on a computer, cause the computer to perform... Figures 2-6 The method executed by one or more first candidate master nodes in the graph. Alternatively, when it runs on a computer, it causes the computer to execute... Figures 2-6 The method executed by one or more source master nodes in the graph.
[0278] This application provides a chip system including a processor and potentially a memory, for implementing the functions of the first candidate master node in the aforementioned method; or for implementing the functions of the source master node in the aforementioned method. The chip system can be composed of chips or may include chips and other discrete devices.
[0279] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.
[0280] Those skilled in the art will recognize that the various illustrative logical blocks and steps described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.
[0281] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.
[0282] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
[0283] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0284] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the essential contributing part of the technical solution of this application, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), RAM, magnetic disks, or optical disks.
[0285] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.
Claims
1. A measurement configuration method, characterized in that, include: The source master node sends a Condition Switching CHO request to one or more candidate master nodes; The source master node receives a CHO request response sent by the first candidate master node. The CHO request response includes CHO configuration and candidate auxiliary node information. The first candidate master node belongs to one or more candidate master nodes. The source master node sends a first RRC configuration message to the terminal device. The first RRC configuration message includes: a second RRC configuration message and a first execution trigger condition corresponding to the first candidate master node. The second RRC configuration message includes the radio interface configuration of the first candidate master node and the radio interface configuration of the first candidate slave node. The second RRC configuration message does not include the second execution triggering condition corresponding to the candidate PSCell. In addition, the information cells in the first RRC configuration message, excluding the second RRC configuration message, also include the second execution triggering condition of the candidate PSCell. The candidate PSCell is managed by the candidate slave node.
2. The method as described in claim 1, characterized in that, The candidate auxiliary node information includes the identifier and / or data forwarding address of the candidate auxiliary node.
3. The method as described in claim 1, characterized in that, The method further includes: The source master node determines the first measurement gap configuration based on the measurement object; The source master node sends the first measurement gap configuration and measurement gap type to the source slave node. The measurement gap type includes a measurement gap type configured for the terminal device or a measurement gap type configured for a frequency range.
4. The method as described in claim 3, characterized in that, The CHO request response further includes a second measurement gap configuration, which is determined based on the frequency point to be measured of the first candidate primary node and the frequency point to be measured of the first candidate secondary node. The method further includes: The source master node determines the first measurement gap configuration based on the second measurement gap configuration; The source master node sends the first measurement gap configuration and measurement gap type to the source slave node. The measurement gap type includes a measurement gap type configured for the terminal device or a measurement gap type configured for a frequency range.
5. The method as described in claim 1, characterized in that, The CHO request response also includes a third measurement gap configuration, which is configured based on the frequency points of the first candidate auxiliary node that are located within the second frequency range FR2.
6. The method as described in claim 1, characterized in that, The method further includes: The source master node sends measurement frequency information to the source auxiliary node, and the measurement frequency information indicates the frequency point located within FR2 among the frequency points to be measured of the first candidate auxiliary node.
7. The method as described in claim 5 or 6, characterized in that, The lowest frequency of FR2 is greater than or equal to 24.25 GHz, and the highest frequency of FR2 is less than or equal to 52.6 GHz.
8. The method as described in claim 7, characterized in that, The method further includes: The source master node determines the fourth measurement gap configuration based on the frequency point to be measured of the first candidate auxiliary node, wherein the frequency point to be measured of the first candidate auxiliary node is a frequency point located within the first frequency range FR1.
9. A communication device, characterized in that, Includes a send / receive module and a processing module; The transceiver module is configured to send a Conditional Handover (CHO) request to one or more candidate master nodes, receive a CHO request response from a first candidate master node, and send a first RRC configuration message to the terminal device; wherein the CHO request response includes CHO configuration and candidate secondary node information, and the first candidate master node belongs to one or more candidate master nodes; The processing module is used to determine the first RRC configuration message, wherein the first RRC configuration message includes a second RRC configuration message and a first execution triggering condition corresponding to the first candidate master node; The second RRC configuration message includes the radio interface configuration of the first candidate master node and the radio interface configuration of the first candidate slave node. The second RRC configuration message does not include the second execution triggering condition corresponding to the candidate PSCell. In addition, the information elements in the first RRC configuration message other than the second RRC configuration message also include the second execution triggering condition of the candidate PSCell. The candidate PSCell is managed by the candidate slave node.
10. The apparatus as claimed in claim 9, characterized in that, The candidate auxiliary node information also includes the identifier and / or data forwarding address of the candidate auxiliary node.
11. The apparatus as claimed in claim 9, characterized in that, The processing module is also configured to: determine the first measurement gap configuration based on the measurement object; The transceiver module is also used to send the first measurement gap configuration and measurement gap type to the source auxiliary node. The measurement gap type includes a measurement gap type configured for the terminal device or a measurement gap type configured for a frequency range.
12. The apparatus as claimed in claim 11, characterized in that, The CHO request response further includes a second measurement gap configuration, which is determined based on the frequency point to be measured of the first candidate primary node and the frequency point to be measured of the first candidate secondary node. The processing module is further configured to: determine the first measurement gap configuration based on the second measurement gap configuration; the transceiver module is further configured to send the first measurement gap configuration and the measurement gap type to the source secondary node, wherein the measurement gap type includes a measurement gap type configured for the terminal device or a measurement gap type configured for a frequency range.
13. The apparatus as claimed in claim 9, characterized in that, The CHO request response also includes a third measurement gap configuration, which is configured based on the frequency points of the first candidate auxiliary node that are located within the second frequency range FR2.
14. The apparatus as claimed in claim 13, characterized in that, The transceiver module is further configured to: send measurement frequency information to the source auxiliary node, wherein the measurement frequency information indicates the frequency point located within FR2 among the frequency points to be measured of the first candidate auxiliary node.
15. The apparatus as claimed in claim 13 or 14, characterized in that, The lowest frequency of FR2 is greater than or equal to 24.25 GHz, and the highest frequency of FR2 is less than or equal to 52.6 GHz.
16. The apparatus as claimed in claim 15, characterized in that, The processing module is further configured to: determine a fourth measurement gap configuration based on the frequency point to be measured of the first candidate auxiliary node, wherein the frequency point to be measured of the first candidate auxiliary node is a frequency point located in the first frequency range FR1.
17. A communication device, characterized in that, It includes a processor and a memory; wherein the memory is used to store one or more computer programs, the one or more computer programs including computer execution instructions, and when the communication device is running, the processor executes the one or more computer programs stored in the memory to cause the communication device to perform the method as described in any one of claims 1 to 8.
18. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program that, when run on a computer, causes the computer to perform the method as described in any one of claims 1 to 8.
19. A computer program product, characterized in that, The computer program product includes a computer program that, when run on a computer, causes the computer to perform the method as described in any one of claims 1 to 8.
Citation Information
Patent Citations
Measurement gap configuration and coordination
CN112771924A
Determining security key
CN114424620A
A system and method for mobility enhancements
WO2021109394A1
