Method and device used for wireless communication

Abstract

Disclosed are a method and device for wireless communication, comprising: receiving a first signaling, the first signaling comprising at least one RRC information block, each RRC information block in the at least one RRC information block being used for configuring a cell group; executing compatibility detection, wherein the time for executing the compatibility detection depends on the at least one RRC information block; wherein the meaning that the time of the behavior execution compatibility detection of the sentence depends on the at least one RRC information block comprises that when the application of any RRC information block in the at least one RRC information block depends on receiving a second signaling, the time of the behavior execution compatibility detection is predefined; when the application of any RRC information block in the at least one RRC information block does not depend on the reception of the second signaling, the time for the behavior to execute compatibility detection is not defined; the second signaling is a signaling of a protocol layer below the RRC layer. According to the invention, better mobility management can be realized.

Description

Technical Field

[0001] The present application relates to a transmission method and device in a wireless communication system, to mobility management, and in particular to compatibility detection to avoid communication interruption. Background Art

[0002] In the future, the application scenarios of wireless communication systems will become more and more diversified, and different application scenarios will put forward different performance requirements for the system. In order to meet the different performance requirements of various application scenarios, the 3GPP (3rd Generation Partner Project) RAN (Radio Access Network) #72 plenary meeting decided to study the new radio (NR) (or Fifth Generation, 5G) technology, and the NR WI (Work Item) was passed at the 3GPP RAN #75 plenary meeting, and the standardization work on NR began.

[0003] In communication, both LTE (Long Term Evolution) and 5G NR involve accurate reception of reliable information, optimized energy efficiency, determination of information validity, flexible resource allocation, scalable system structure, efficient non-access layer information processing, low service interruption and drop rate, and support for low power consumption. This is of great significance to the normal communication between base stations and user equipment, the reasonable scheduling of resources, and the balancing of system loads. It can be said to be the cornerstone of high throughput, meeting the communication needs of various services, improving spectrum utilization, and improving service quality. It is indispensable for eMBB (ehanced Mobile BroadBand), URLLC (Ultra Reliable Low Latency Communication) and eMTC (enhanced Machine Type Communication). At the same time, in IIoT (Industrial Internet of Things, Industrial Internet of Things, V2X (Vehicular to X, vehicle-mounted communication), device-to-device communication, unlicensed spectrum communication, user communication quality monitoring, network planning optimization, NTN (Non Territerial Network, non-terrestrial network communication), TN (Territerial Network, terrestrial network communication), dual connectivity (Dual connectivity) system, wireless resource management and multi-antenna codebook selection, signaling design, neighbor management, business management, beamforming, there are extensive needs, information transmission methods are divided into broadcast and unicast, both transmission methods are essential for 5G systems, because they are very helpful to meet the above requirements. The UE can be connected to the network directly or through a relay.

[0004] As the scenarios and complexity of the system continue to increase, higher requirements are placed on reducing interruption rates, reducing latency, enhancing reliability, enhancing system stability, business flexibility, and power saving. At the same time, compatibility between different versions of different systems also needs to be considered during system design.

[0005] The meanings of the concepts, terms and abbreviations in this application may refer to the 3GPP standards, including but not limited to:

[0006] https: / / www.3gpp.org / ftp / Specs / archive / 21_series / 21.905 / 21905-h10.zip

[0007] https: / / www.3gpp.org / ftp / Specs / archive / 38_series / 38.300 / 38300-h10.zip

[0008] https: / / www.3gpp.org / ftp / Specs / archive / 38_series / 38.331 / 38331-h10.zip Summary of the invention

[0009] The researchers found that in the scenario of applying RRC information blocks, how to determine the time of compatibility detection is a problem that needs to be solved. The researchers also found that for some RRC information blocks, the impact on performance is not obvious when performing compatibility detection when receiving, applying, or storing. In order to achieve flexibility, it is better not to define the time of compatibility detection. However, for RRC information blocks triggered by the second signaling, the time of compatibility detection needs to be defined, because if the compatibility detection is performed too late, it may cause repeated initiation of RRC connection reconstruction, and if the RRC information blocks with compatibility problems need to be executed during the RRC connection reconstruction process, the RRC connection reconstruction may be triggered again, and may even fall into an infinite loop of RRC reconstruction, which will have a huge impact on the performance of the terminal. The researchers found that compatibility detection is a very important issue for the terminal, because the network may not have all the information of the terminal, or an error may occur during the network execution process, resulting in the configuration of the terminal being incompatible with the terminal. In such a case, if forced execution leads to unpredictable problems, so the terminal needs to perform compatibility detection on at least one RRC information block. The researchers further found that this is especially true for L1L2 triggered mobility. In this scenario, since the received RRC information block is not executed immediately, it is particularly necessary to define the time for compatibility detection. The method proposed in this application reasonably determines the time for compatibility detection according to different RRC information blocks, solving the above problem.

[0010] In view of the above-mentioned problems, this application provides a solution.

[0011] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of any node of the present application can be applied to any other node. In the absence of conflict, the embodiments and features in the embodiments of the present application can be arbitrarily combined with each other. At the same time, the method proposed in the present application can also be used to solve other problems in communication.

[0012] As an embodiment, the interpretation of the terminology in the present application refers to the definition of the TS38 series of specification protocols of 3GPP.

[0013] As an example, the interpretation of the terms in the present application refers to the definitions of the TS37 series of specification protocols of 3GPP.

[0014] The present application discloses a method in a first node used for wireless communication, comprising:

[0015] receiving first signaling, where the first signaling includes at least one RRC information block, each RRC information block in the at least one RRC information block is used to configure a cell group;

[0016] Performing compatibility detection, wherein the time for performing the compatibility detection depends on the at least one RRC information block;

[0017] Among them, the meaning of the sentence that the time for the behavior to perform compatibility check depends on the at least one RRC information block includes: when the application of any RRC information block in the at least one RRC information block depends on receiving the second signaling, the time for the behavior to perform compatibility check is predefined; when the application of any RRC information block in the at least one RRC information block does not depend on receiving the second signaling, the time for the behavior to perform compatibility check is not defined; the second signaling is the signaling of the protocol layer below the RRC layer, and the second signaling indicates any RRC information block in the at least one RRC information block.

[0018] As an embodiment, the problems to be solved by the present application include: how to determine the time of compatibility detection; how to determine the time of compatibility detection when receiving the at least one RRC information block; how to determine the time of compatibility detection according to different RRC information blocks; how to better support the compatibility detection of the RRC information block triggered by the second signaling; how to avoid communication interruption or error.

[0019] As an embodiment, the benefits of the above method include: determining the time for compatibility detection based on whether the at least one RRC information block is triggered by the second signaling application, which is conducive to avoiding communication interruption, avoiding repeated execution of RRC connection reconstruction, and maintaining the flexibility of terminal implementation; improving performance, ensuring business continuity, better supporting mobility management, and avoiding errors and accidents.

[0020] Specifically, according to one aspect of the present application, at least when the behavior performs compatibility detection, the first timer is not in a running state, and the start condition of the first timer includes initiating an RRC reconstruction process.

[0021] Specifically, according to one aspect of the present application, in response to the at least one RRC information block failing the compatibility check, RRC connection reestablishment is initiated;

[0022] The behavior of initiating RRC connection reconstruction includes starting a first timer.

[0023] Specifically, according to one aspect of the present application, as a response to the at least one RRC information block failing the compatibility test, the first attempt is abandoned and RRC connection reconstruction is initiated; in the RRC connection reconstruction, whether the triggering application of the RRC information block in the at least one RRC information block is allowed to depend on whether the first attempt is configured;

[0024] Among them, when the first attempt is configured, in the RRC connection reconstruction, triggering the application of the RRC information block in the at least one RRC information block is allowed; when the first attempt is not configured or the first attempt is abandoned, triggering the application of the RRC information block in the at least one RRC information block is not allowed in the RRC connection reconstruction.

[0025] Specifically, according to one aspect of the present application, as a response to at least one RRC information block failing the compatibility check, a first operation is performed, and the first operation depends on the number of consecutive failures of the compatibility check; when the number of consecutive failures of the compatibility check is not less than a first threshold, the first operation is to enter the RRC idle state; when the number of consecutive failures of the compatibility check is less than the first threshold, the first operation is to initiate RRC connection reconstruction.

[0026] Specifically, according to one aspect of the present application, as a response to the at least one RRC information block failing the compatibility check, only the RRC information block that failed the compatibility check in the at least one RRC information block is discarded;

[0027] The first transmitter sends a first report, where the first report indicates a discarded RRC information block, or the first report indicates an RRC information block among the at least one RRC information block that fails compatibility detection.

[0028] Specifically, according to one aspect of the present application, as a response to the at least one RRC information block failing the compatibility check, all RRC information blocks in the at least one RRC information block are discarded.

[0029] Specifically, according to one aspect of the present application, the first timing advance indicated by the second signaling is applied; after the first timing advance indicated by the second signaling is applied, as a response to the at least one RRC information block failing the compatibility check, only the configuration before the compatibility check except the first timing advance is restored.

[0030] Specifically, according to one aspect of the present application, a reference RRC information block is received;

[0031] Among them, the behavior execution compatibility detection only includes any one of the at least one RRC information block and the former of the reference RRC information block; the phrase applying any one of the at least one RRC information block means that any one of the at least one RRC information block needs to be merged with the reference RRC information block and then applied.

[0032] Specifically, according to one aspect of the present application, the first node is an Internet of Things terminal.

[0033] Specifically, according to one aspect of the present application, the first node is a user equipment.

[0034] Specifically, according to one aspect of the present application, the first node is a relay.

[0035] Specifically, according to one aspect of the present application, the first node is an access network device.

[0036] Specifically, according to one aspect of the present application, the first node is a vehicle-mounted terminal.

[0037] Specifically, according to one aspect of the present application, the first node is an aircraft.

[0038] Specifically, according to one aspect of the present application, the first node is a mobile phone.

[0039] The present application discloses a first node used for wireless communication, comprising:

[0040] A first receiver receives a first signaling, wherein the first signaling includes at least one RRC (radio resource control) information block, each of the at least one RRC information block is used to configure a cell group;

[0041] A first processor performs compatibility detection, wherein the time for performing the compatibility detection depends on the at least one RRC information block;

[0042] Among them, the meaning of the sentence that the time for the behavior to perform compatibility check depends on the at least one RRC information block includes: when the application of any RRC information block in the at least one RRC information block depends on receiving the second signaling, the time for the behavior to perform compatibility check is predefined; when the application of any RRC information block in the at least one RRC information block does not depend on receiving the second signaling, the time for the behavior to perform compatibility check is not defined; the second signaling is the signaling of the protocol layer below the RRC layer, and the second signaling indicates any RRC information block in the at least one RRC information block.

[0043] As an embodiment, compared with the traditional solution, this application has the following advantages:

[0044] This avoids communication interruption, and in particular avoids RRC connection reestablishment from entering an endless loop.

[0045] RRC re-establishment due to compatibility issues of certain RRC information blocks is avoided.

[0046] Flexibility is guaranteed.

[0047] Better support for L1L2 mobility management.

[0048] Better support is provided for recovery using the at least one RRC information block during RRC connection reestablishment, and such recovery is controlled, especially controlled by receiving the result of compatibility detection.

[0049] Ensures the continuity of communication. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Other features, objects and advantages of the present application will become more apparent by reading the detailed description of non-limiting embodiments with reference to the following drawings:

[0051] Figure 1 A flowchart of receiving a first signaling and performing compatibility detection according to an embodiment of the present application is shown;

[0052] Figure 2 A schematic diagram of a network architecture according to an embodiment of the present application is shown;

[0053] Figure 3 A schematic diagram showing an embodiment of a wireless protocol architecture of a user plane and a control plane according to an embodiment of the present application;

[0054] Figure 4 A schematic diagram showing a first communication device and a second communication device according to an embodiment of the present application is shown;

[0055] Figure 5 A flow chart showing wireless signal transmission according to an embodiment of the present application is shown;

[0056] Figure 6 A schematic diagram of an LTM according to an embodiment of the present application is shown;

[0057] Figure 7 A schematic diagram showing an RRC information block structure according to an embodiment of the present application is shown;

[0058] Figure 8 A schematic diagram showing a RRC information block in which a first report indication is discarded according to an embodiment of the present application;

[0059] Fig. 9 A schematic diagram showing a first signaling carrying or used to generate a reference RRC information block according to an embodiment of the present application;

[0060] Fig.10 A schematic diagram illustrating a processing device in a first node according to an embodiment of the present application is illustrated;

[0061] Fig.11 The following is a schematic diagram illustrating a processing device used in a first node according to an embodiment of the present application.

[0062] Implementation

[0063] The technical solution of the present application will be further described in detail below in conjunction with the accompanying drawings. It should be noted that, unless there is a conflict, the embodiments in the present application and the features in the embodiments can be combined with each other arbitrarily.

[0064] Example 1

[0065] Embodiment 1 illustrates a flowchart of receiving a first signaling and performing compatibility detection according to an embodiment of the present application, as shown in the attached Figure 1 Attached Figure 1 In the figure, each box represents a step. It should be emphasized that the order of the boxes in the figure does not represent the temporal relationship between the steps represented.

[0066] In Embodiment 1, the first node in the present application receives a first signaling in step 101 ; and performs a compatibility check in step 102 .

[0067] As an embodiment, the first signaling includes at least one RRC information block; each RRC information block in the at least one RRC information block is used to configure a cell group; the time for the behavior to perform compatibility detection depends on the at least one RRC information block; the sentence "the time for the behavior to perform compatibility detection depends on the at least one RRC information block" means: when the application of any RRC information block in the at least one RRC information block depends on receiving the second signaling, the time for the behavior to perform compatibility detection is predefined; when the application of any RRC information block in the at least one RRC information block does not depend on receiving the second signaling, the time for the behavior to perform compatibility detection is not defined; the second signaling is the signaling of the protocol layer below the RRC layer, and the second signaling indicates any RRC information block in the at least one RRC information block.

[0068] As an embodiment, the first signaling includes a reference RRC information block and at least one RRC (radioresource control) information block, each of the at least one RRC information block is used to configure a cell group; the time for the behavior to perform compatibility detection depends on the first signaling; wherein, the sentence "the time for the behavior to perform compatibility detection depends on the first signaling" means: when the application of any RRC information block in the at least one RRC information block depends on the receipt of a second signaling, at least the time for the compatibility detection performed on the reference RRC information block is predefined; when the application of any RRC information block in the at least one RRC information block does not depend on the receipt of a second signaling, the time for the behavior to perform compatibility detection is not defined; the second signaling is the signaling of the protocol layer below the RRC layer, and the second signaling indicates any RRC information block in the at least one RRC information block; the phrase "the application of any RRC information block in the at least one RRC information block" means: any RRC information block in the at least one RRC information block needs to be merged with the reference RRC information block first, and then the merger of any RRC information block in the at least one RRC information block and the reference RRC information block is applied.

[0069] As an embodiment, the first node is a UE (User Equipment).

[0070] As an embodiment, the first node is in an RRC connected state.

[0071] As an embodiment, any parameter in the present application may be either configured by the network or generated by the first node according to an internal algorithm, such as randomly.

[0072] As an embodiment, the present application is directed to NR.

[0073] As an embodiment, the present application is directed to wireless communication networks after NR.

[0074] As an embodiment, the serving cell refers to the cell where the UE resides. Performing a cell search includes the UE searching for a suitable cell of the selected PLMN (Public Land Mobile Network) or SNPN (Stand-alone Non-Public Network), selecting the suitable cell to provide available services, and monitoring the control channel of the suitable cell. This process is defined as residing on the cell; that is, a residing cell is the serving cell of the UE relative to the UE. Residing on a cell in the RRC idle state or the RRC inactive state has the following benefits: it enables the UE to receive system messages from the PLMN or SNPN; after registration, if the UE wishes to establish an RRC connection or continue a suspended RRC connection, the UE can do so by performing initial access on the control channel of the residing cell; the network can page the UE; and the UE can receive ETWS (Earthquake and Tsunami Warning System) and CMAS (Commercial Mobile Alert System) notifications.

[0075] As an embodiment, for a UE in an RRC connected state that is not configured with CA / DC (carrier aggregation / dual connectivity), there is only one service cell including a primary cell. For a UE in an RRC connected state that is configured with CA / DC (carrier aggregation / dual connectivity), the service cell is used to indicate a set of cells including a special cell (SpCell) and all cells from the small cell. The primary cell (Primary Cell) is an MCG (Master Cell Group) cell that operates on the main frequency. The UE performs an initial connection establishment process or initiates connection reconstruction on the primary cell. For dual connection operations, the special cell refers to the PCell (Primary Cell) of the MCG or the PSCell (Primary SCGCell) of the SCG (Secondary Cell Group); if it is not a dual connection operation, the special cell refers to the PCell.

[0076] As an embodiment, the operating frequency of the SCell (Secondary Cell) is a secondary frequency.

[0077] As an example, individual contents of an information element are referred to as fields.

[0078] As an embodiment, MR-DC (Multi-Radio Dual Connectivity) refers to dual connectivity between E-UTRA and NR nodes, or dual connectivity between two NR nodes.

[0079] As an embodiment, in MR-DC, the wireless access node that provides the control plane connection to the core network is the master node, which may be a master eNB, a master ng-eNB, or a master gNB.

[0080] As an embodiment, MCG refers to a group of service cells associated with a master node in MR-DC, including SpCells, and may also, optionally, include one or more SCells.

[0081] As an embodiment, PCell is the SpCell of MCG.

[0082] As an embodiment, the PSCell is the SpCell of the SCG.

[0083] As an embodiment, in MR-DC, the control plane connection to the core network is not provided, and the radio access node that provides additional resources to the UE is a slave node. The slave node can be an en-gNB, a slave ng-eNB or a slave gNB.

[0084] As an embodiment, in MR-DC, a group of service cells associated with a slave node is a SCG (secondary cell group), including a SpCell and, optionally, one or more SCells.

[0085] As an embodiment, the SpCell is a PCell or the SpCell is a PSCell.

[0086] As an embodiment, the RRC information block refers to an information block (information element) in an RRC message.

[0087] As an embodiment, SSB may be referred to as SS / PBCH block, or SS block.

[0088] As an embodiment, one RRC information block may include one or more RRC information blocks.

[0089] As an embodiment, an RRC information block may not include any RRC information block, but only include at least one parameter.

[0090] As an embodiment, the radio bearer includes at least a signaling radio bearer and a data radio bearer.

[0091] As an embodiment, the radio bearer is a service or an interface of a service provided by the PDCP layer to a higher layer.

[0092] As a sub-embodiment of this embodiment, the higher layer includes one of the RRC layer, NAS, and SDAP layer.

[0093] As an embodiment, the signaling radio bearer is a service or an interface of services provided by PDCP to a higher layer.

[0094] As a sub-embodiment of this embodiment, the higher layer includes the RRC layer, at least the former in the NAS.

[0095] As an embodiment, the data radio bearer is a service or an interface of services provided by PDCP to a higher layer.

[0096] As a sub-embodiment of this embodiment, the higher layer includes the SDAP layer, at least the former in NAS.

[0097] As an embodiment, the first signaling is RRC layer signaling.

[0098] As an embodiment, the first signaling is transmitted using SRB1 (signaling radio bearer 1).

[0099] As an embodiment, the first signaling is or includes an RRCReconfiguration message.

[0100] As an embodiment, the first signaling is or includes an RRCConnectionReconfiguration message.

[0101] As an embodiment, the first signaling includes measurement configuration.

[0102] As an embodiment, the first signaling includes serving cell configuration.

[0103] As an embodiment, the first signaling includes frequency domain configuration.

[0104] As an embodiment, the first signaling is sent via a dedicated logical channel.

[0105] As an embodiment, the first signaling includes configuring a multimedia broadcast multicast service.

[0106] As an embodiment, the first signaling includes configuring MAC.

[0107] As an embodiment, the first signaling is downlink.

[0108] As an embodiment, the at least one RRC information block includes only one RRC information block.

[0109] As an embodiment, the at least one RRC information block includes multiple RRC information blocks.

[0110] As an embodiment, the at least one RRC information block includes at least one information block in an RRCReconfiguration message.

[0111] As an embodiment, the at least one RRC information block includes only one information block in the RRCReconfiguration message.

[0112] As an embodiment, the name of each RRC information block in the at least one RRC information block is the same.

[0113] As an embodiment, the at least one RRC information block is carried by an RRC message.

[0114] As an embodiment, the at least one RRC information block is carried by an RRCReconfiguration message.

[0115] As an embodiment, each RRC information block in the at least one RRC information block is carried by an RRCReconfiguration message.

[0116] As an embodiment, the at least one RRC information block is or includes CellGroupConfig.

[0117] As an embodiment, each RRC information block in the at least one RRC information block is or includes CellGroupConfig.

[0118] As an embodiment, the at least one RRC information block constitutes a list of RRC information blocks.

[0119] As a sub-embodiment of this embodiment, the name of the list includes AddMod.

[0120] As an embodiment, each RRC information block in the at least one RRC information block includes an RRCReconfiguration message.

[0121] As a sub-embodiment of this embodiment, the RRCReconfiguration message included in each RRC information block in the at least one RRC information block exists in a container.

[0122] As a sub-embodiment of this embodiment, the RRCReconfiguration message carrying the at least one RRC information block carries the RRCReconfiguration message included in the at least one RRC information block through a container.

[0123] As a sub-embodiment of this embodiment, the RRCReconfiguration message included in the at least one RRC information block comes from the candidate target cell.

[0124] As an embodiment, the phrase that each of the at least one RRC information block is used to configure a cell group includes: each of the at least one RRC information block includes at least CellGroupConfig.

[0125] As an embodiment, multiple RRC information in the at least one RRC information block can be used to configure the same cell group.

[0126] As a sub-embodiment of this embodiment, the phrase configuring the same cell group means that the SpCells included in the configured cell group are the same, but the configuration parameters of the cell group are different.

[0127] As a sub-embodiment of this embodiment, the phrase configuring the same cell group means that the SpCells and SCells included in the configured cells are the same, but the configuration parameters of the cell group are different.

[0128] As a sub-embodiment of this embodiment, the configuration parameters of the cell group include at least one parameter, such as time-frequency resources, such as the value of a timer.

[0129] As an embodiment, the phrase each RRC information block in the at least one RRC information block is used to configure a cell group includes: each RRC information block in the at least one RRC information block is used to configure the SpCell of a cell group.

[0130] As an embodiment, the one cell group is either for a primary cell group or a candidate primary cell group, or for a secondary cell group or a candidate secondary cell group.

[0131] As an embodiment, the phrase each of the at least one RRC information block is used to configure a cell group includes: each of the at least one RRC information block is used to configure the value of at least one timer of a cell group.

[0132] As a sub-embodiment of this embodiment, the at least one timer includes T304.

[0133] As a sub-embodiment of this embodiment, the at least one timer includes T310.

[0134] As a sub-embodiment of this embodiment, each RRC information block in the at least one RRC information block is used to configure the value of N310 of a cell group.

[0135] As a sub-embodiment of this embodiment, the T310 timer is used for wireless link failure, that is, T310 expiration triggers wireless link failure; the T310 is started after receiving an indication of the number of N310s from the physical layer, and when the assessment of the wireless link quality is lower than a specific threshold, the physical layer sends the indication to a higher layer; the specific threshold is predefined or network configured.

[0136] As an embodiment, the phrase each RRC information block in the at least one RRC information block is used to configure a cell group includes: each RRC information block in the at least one RRC information block is used to configure random access resources of a cell group.

[0137] As a sub-embodiment of this embodiment, the random access resource includes at least one of a contention-free random access resource and a contention-based random access resource.

[0138] As an embodiment, the phrase each RRC information block in the at least one RRC information block is used to configure a cell group includes: each RRC information block in the at least one RRC information block is used to configure reference signal resources of a cell group.

[0139] As an embodiment, the phrase each of the at least one RRC information block is used to configure a cell group includes: each of the at least one RRC information block is used to configure the value of the first timer of a cell group.

[0140] As an embodiment, the phrase each RRC information block in the at least one RRC information block is used to configure a cell group includes: each RRC information block in the at least one RRC information block is used to configure an RLC bearer or RLC entity of a cell group.

[0141] As an embodiment, the phrase each RRC information block in the at least one RRC information block is used to configure a cell group includes: each RRC information block in the at least one RRC information block is used to configure the MAC of a cell group.

[0142] As an embodiment, the phrase each of the at least one RRC information block is used to configure a cell group includes: each of the at least one RRC information block is used to configure the identity or index of a cell group.

[0143] As an embodiment, the phrase each RRC information block in the at least one RRC information block is used to configure a cell group includes: each RRC information block in the at least one RRC information block is used to configure the SCell of a cell group.

[0144] As an embodiment, the phrase each RRC information block in the at least one RRC information block is used to configure a cell group includes: each RRC information block in the at least one RRC information block is used to configure reconfigurationWithSync (synchronous reconfiguration) of the SpCell of a cell group.

[0145] As an embodiment, the phrase each of the at least one RRC information block is used to configure a cell group includes: each of the at least one RRC information block is used to configure measurements of a cell group and / or parameters for mobility management.

[0146] As an embodiment, the phrase that each RRC information block in the at least one RRC information block is used to configure a cell group includes: each RRC information block is used to configure a target SpCell.

[0147] As a sub-embodiment of this embodiment, each RRC information block is CellGroupConfig, and each RRC information block includes SpCellConfig for configuring the target SpCell.

[0148] As a sub-embodiment of this embodiment, the target SpCell is the SpCell of the one cell group.

[0149] As a sub-embodiment of this embodiment, the target SpCell is a target SpCell in cell switching or LTM.

[0150] As a sub-embodiment of this embodiment, the target SpCell is a target SpCell of cell switching or LTM cell switching.

[0151] As an embodiment, the cell group configured by each RRC information block in the at least one RRC information block is MCG and / or SCG.

[0152] As an embodiment, the phrase "application of any one of the at least one RRC information block depends on receiving the second signaling" means or includes: the at least one RRC information block does not include the second signaling; the RRC message to which the at least one RRC information block belongs does not include the second signaling.

[0153] As an embodiment, the phrase application of any one of the at least one RRC information block depends on receiving a second signaling means or includes: the second signaling is signaling of a protocol layer below the RRC layer.

[0154] As an embodiment, the phrase application of any one of the at least one RRC information block depends on receiving a second signaling means or includes: the second signaling is a signaling of the MAC layer.

[0155] As an embodiment, the phrase application of any one of the at least one RRC information block depends on receiving a second signaling means or includes: the second signaling is signaling of the MAC layer and the physical layer.

[0156] As an embodiment, the phrase "application of any one of the at least one RRC information block depends on receiving a second signaling" means or includes: the second signaling is a MAC CE (Control element, control block).

[0157] As an embodiment, the phrase application of any one of the at least one RRC information block depends on receipt of the second signaling means or includes: the at least one RRC information block will not be applied immediately after receipt.

[0158] As an embodiment, the phrase application of any one of the at least one RRC information block depends on receiving the second signaling means or includes: the at least one RRC information block will be first stored in a state variable after being received.

[0159] As an embodiment, the phrase "application of any one of the at least one RRC information block depends on receiving the second signaling" means or includes: application of any one of the at least one RRC information block needs to be triggered.

[0160] As an embodiment, the phrase "application of any one of the at least one RRC information block depends on receipt of a second signaling" means or includes: if the second signaling is not received, none of the at least one RRC information block will be applied.

[0161] As a sub-embodiment of this embodiment, under normal circumstances, for example, when no failure occurs or RRC connection reestablishment is performed, the second signaling is not received, and then none of the RRC information blocks in the at least one RRC information block will be applied.

[0162] As an embodiment, the phrase "application of any one of the at least one RRC information block depends on receipt of a second signaling" means or includes: upon receipt of a second signaling, one or at least one of the at least one RRC information block will be applied, and the second signaling indicates the one or at least one of the at least one RRC information block.

[0163] As an embodiment, the phrase "the application of any one of the at least one RRC information block depends on the receipt of the second signaling" means or includes: "the application of any one of the at least one RRC information block depends on the receipt of the second signaling" only when the first timer is not running.

[0164] As an embodiment, the phrase "application of any one of the at least one RRC information block depends on receiving the second signaling" means or includes: when none of the at least one RRC information block has been applied, application of any one of the at least one RRC information block depends on receiving the second signaling.

[0165] As an embodiment, the phrase "application of any one of the at least one RRC information block depends on receipt of the second signaling" means or includes: when no RRC information block of the at least one RRC information block is attempted to be applied, application of any one of the at least one RRC information block depends on receipt of the second signaling.

[0166] As an embodiment, the phrase "the application of any one of the at least one RRC information block depends on receiving the second signaling" means or includes: when the first RRC information block of the at least one RRC information block is applied, the application of any one of the at least one RRC information block depends on receiving the second signaling.

[0167] As an embodiment, the phrase "the application of any one of the at least one RRC information block depends on the receipt of the second signaling" means or includes: after the last successful execution of LTM, the application of any one of the at least one RRC information block depends on the receipt of the second signaling.

[0168] As an embodiment, the phrase "the application of any one of the at least one RRC information block depends on the receipt of the second signaling" means or includes: at least when no LTM failure occurs in the at least one RRC information block, the application of any one of the at least one RRC information block depends on the receipt of the second signaling.

[0169] As an embodiment, the phrase application of any one of the at least one RRC information block depends on receiving the second signaling means or includes: application of any one of the at least one RRC information block needs to be triggered by the second signaling.

[0170] As an embodiment, the at least one RRC information block includes only one RRC information block.

[0171] Typically, the at least one RRC information block comprises a plurality of RRC information blocks.

[0172] As an embodiment, the first RRC information block and the second signaling are not sent at the same time.

[0173] As an embodiment, the sending of the second signaling is later than the sending of the first RRC information block.

[0174] As an embodiment, the second signaling and the first RRC information block belong to different MAC PDUs (protocol data units).

[0175] As an embodiment, the second signaling is the signaling outside the at least one RRC information block.

[0176] As an embodiment, the name of each RRC information block in the at least one RRC information block is the same.

[0177] As an embodiment, the second signaling does not include a PDU (protocol data unit) of the RRC layer.

[0178] As an embodiment, the second signaling does not include a PDU (protocol data unit) of the RLC layer.

[0179] As an embodiment, the second signaling includes an index or a configuration index of one of the at least one RRC information blocks.

[0180] As an embodiment, the second signaling includes an index or a configuration index or an identity of a cell group configured by one of the at least one RRC information blocks.

[0181] As an embodiment, the second signaling includes an index or a configuration index or an identity of a cell included in a cell group configured by one of the at least one RRC information blocks.

[0182] As an embodiment, the logical channel occupied by the at least one RRC information block includes a DCCH (dedicated control channel).

[0183] As an embodiment, the at least one RRC information block uses encryption.

[0184] As an embodiment, the at least one RRC information block uses integrity protection.

[0185] As an embodiment, the second signaling uses encryption.

[0186] As an embodiment, the second signaling uses integrity protection.

[0187] As an embodiment, the second signaling does not use encryption.

[0188] As an embodiment, the second signaling does not use integrity protection.

[0189] As an embodiment, the second signaling is directed to the first node.

[0190] As an embodiment, the second signaling is only directed to the first node.

[0191] As an embodiment, the physical channel occupied by the second signaling includes PDCCH (physical downlink control channel).

[0192] As an embodiment, the physical channel occupied by the second signaling includes PDSCH (physical downlink shared channel).

[0193] As an embodiment, the second signaling is MAC CE (control element).

[0194] As an embodiment, the second signaling is MAC CE and DCI (downlink control information).

[0195] As a sub-embodiment of this embodiment, the phrase that the second signaling is MAC CE and DCI means that the second signaling includes both MAC CE and DCI.

[0196] As a sub-embodiment of this embodiment, the phrase that the second signaling is MAC CE and DCI means that the second signaling includes a first sub-signaling and a second sub-signaling, the first sub-signaling is MAC CE; the second sub-signaling is DCI.

[0197] As an embodiment, after receiving the second signaling, the MAC layer of the first node sends an indication to the RRC layer of the first node.

[0198] As a sub-embodiment of this embodiment, the indication includes receiving the second signaling.

[0199] As a sub-embodiment of this embodiment, the indication includes receiving the second signaling, and the second signaling indicates the application of the first RRC information block.

[0200] As a sub-embodiment of this embodiment, the indication includes a request or a need to apply one of the at least one RRC information blocks.

[0201] As a sub-embodiment of this embodiment, the indication includes one RRC information block among the at least one RRC information block.

[0202] As a sub-embodiment of this embodiment, the indication includes an identity or a configuration identity or a configuration index of one RRC information block in at least one RRC information block.

[0203] As a sub-embodiment of this embodiment, the indication includes the identity of the cell group configured by one RRC information block in the at least one RRC information block.

[0204] As a sub-embodiment of this embodiment, the indication includes the identity of the SpCell included in the cell group configured by one RRC information block in the at least one RRC information block.

[0205] As an embodiment, the phrase application of any one of the at least one RRC information block includes: executing any one of the at least one RRC information block.

[0206] As an embodiment, the phrase "application of any one of the at least one RRC information block" means: applying parameters and / or configurations in any one of the at least one RRC information block.

[0207] As an embodiment, the phrase "application of any one of the at least one RRC information block" means: saving the current configuration, and applying the configuration indicated by any one of the at least one RRC information block.

[0208] As an embodiment, the phrase application of any one of the at least one RRC information block means or includes: applying each parameter indicated by any one of the at least one RRC information block.

[0209] As an embodiment, applying any RRC information block of the at least one RRC information block includes stopping at least one timer other than the first timer.

[0210] As an embodiment, the second signaling is generated by a protocol layer below the RRC layer.

[0211] As an embodiment, the second signaling is not RRC signaling.

[0212] As an embodiment, the second signaling indicates any one of the at least one RRC information blocks.

[0213] As an embodiment, the phrase that the second signaling indicates any one of the at least one RRC information block means or includes: the second signaling explicitly indicates the identity or index of any one of the at least one RRC information block indicated by the second signaling.

[0214] As an embodiment, the phrase "the second signaling indicates any one of the at least one RRC information block" means or includes: the second signaling explicitly indicates the identity or index associated with the any one of the at least one RRC information block indicated by the second signaling.

[0215] As an embodiment, the phrase "the second signaling indicates any one of the at least one RRC information block" means or includes: the second signaling includes a first identity, the first identity is the identity of the any one of the at least one RRC information block indicated by the second signaling, or the first identity is associated with the any one of the at least one RRC information block indicated by the second signaling.

[0216] As a sub-embodiment of this embodiment, the first identity is associated only with any one of the at least one RRC information blocks indicated by the second signaling.

[0217] As a sub-embodiment of this embodiment, the first identity is a configuration identity.

[0218] As a sub-embodiment of this embodiment, the first identity is an index.

[0219] As a sub-embodiment of this embodiment, the first identity is the first identity indicated by the second signaling.

[0220] As a sub-embodiment of this embodiment, the first identity is a priority identity indicated by the second signaling.

[0221] As a sub-embodiment of this embodiment, the first identity is a configuration index.

[0222] As a sub-embodiment of this embodiment, the first identity is a cell identity.

[0223] As a sub-embodiment of this embodiment, the first identity is the identity of the cell indicated by the second signaling.

[0224] As a sub-embodiment of this embodiment, the first identity is the identity of the cell group configured by any one of the at least one RRC information blocks.

[0225] As a sub-embodiment of this embodiment, the first identity is the identity of the SpCell of the cell group configured by any one of the RRC information blocks in the at least one RRC information block.

[0226] As a sub-embodiment of this embodiment, the first identity is the index of any one of the at least one RRC information block in the at least one RRC information block.

[0227] As a sub-embodiment of this embodiment, the first identity is an index of any RRC information block in the at least one RRC information block in the RRC information block indicated by the second signaling.

[0228] As a sub-embodiment of this embodiment, the information block including the first identity in the at least one RRC information block is determined to be any one of the RRC information blocks in the at least one RRC information block.

[0229] As a sub-embodiment of this embodiment, each RRC information block in the at least one RRC information block includes an identity.

[0230] As a sub-embodiment of this embodiment, only one RRC information block among the at least one RRC information block includes the first identity, and the only one RRC information block is the first RRC information block.

[0231] As a sub-embodiment of this embodiment, each RRC information block in the at least one RRC information block is associated with an identity, and the RRC information block associated with the first identity in the at least one RRC information block is determined to be the first RRC information block.

[0232] As a sub-embodiment of this embodiment, each RRC information block in the at least one RRC information block has a mapping relationship with an identity, and the RRC information block in the at least one RRC information block that has a mapping relationship with the first identity is determined as any one of the at least one RRC information blocks.

[0233] As an embodiment, the application of any RRC information block in the at least one RRC information block does not include random access.

[0234] As an embodiment, the phrase "application of any one of the at least one RRC information block does not include random access" means or includes: application of any one of the at least one RRC information block does not involve and / or does not require random access.

[0235] As an embodiment, the phrase "application of any one of the at least one RRC information block does not include random access" means or includes: application of any one of the at least one RRC information block is not accompanied by random access.

[0236] As an embodiment, the phrase "application of any one of the at least one RRC information block does not include random access" means or includes: application of any one of the at least one RRC information block triggers random access.

[0237] As an embodiment, the phrase "application of any one of the at least one RRC information block does not include random access" means or includes: any one of the at least one RRC information block indicates that random access is not used.

[0238] As an embodiment, the phrase that application of any one of the at least one RRC information block does not include random access means or includes: any one of the at least one RRC information block indicates RACH-less.

[0239] As an embodiment, the phrase "application of any one of the at least one RRC information block does not include random access" means or includes: any one of the at least one RRC information block does not indicate a random access resource.

[0240] As an embodiment, the phrase "application of any one of the at least one RRC information block does not include random access" means or includes: when the first RRC information block is used for cell exchange, and the cell group configured by the first RRC information block is applied as a main cell group or a slave cell group, there is no need to perform random access on the target cell configured by the first RRC information block.

[0241] As a sub-embodiment of this embodiment, the target cell is the SpCell of the cell group configured by any one of the RRC information blocks in the at least one RRC information block.

[0242] As an embodiment, the phrase application of any one of the at least one RRC information block does not include random access means or includes: whether the first RRC information block is successfully applied does not depend on initiating random access.

[0243] As an embodiment, the phrase application of any one of the at least one RRC information block does not include random access means or includes: whether any one of the at least one RRC information block is successfully applied does not depend on the completion of random access.

[0244] As an embodiment, the at least one RRC information block is received in the source cell; and any RRC information block in the at least one RRC information block is applied in the target cell.

[0245] As a sub-embodiment of this embodiment, each RRC information block in the at least one RRC information block is used to indicate switching from a source cell to a target cell.

[0246] As an embodiment, the first node receives a second signaling, and the second signaling triggers the application of the first RRC information block in the at least one RRC information block.

[0247] As an embodiment, after the first RRC information block is successfully applied, the at least one RRC information block will not be automatically released.

[0248] As an embodiment, after the first RRC information block is successfully applied, only the first RRC information block among the at least one RRC information block will be released.

[0249] As an embodiment, after the first RRC information block is successfully applied, at least one RRC information block among the at least one RRC information block will be activated.

[0250] As an embodiment, after the first RRC information block is successfully applied, at least one RRC information block among the at least one RRC information block will be deactivated.

[0251] As an embodiment, after the first RRC information block is successfully applied, if there is no further instruction by the network, the at least one RRC information block will not be released.

[0252] As an embodiment, after the first RRC information block is successfully applied, the RRC message blocks other than the first RRC message block in the at least one RRC information block will not be automatically released.

[0253] As an embodiment, after the first RRC information block is successfully applied, under the condition that there is no further instruction by the network, the RRC message blocks other than the first RRC message block in the at least one RRC information block will not be released.

[0254] As an embodiment, the benefits of the above method include that it is helpful to reduce signaling overhead, and is particularly useful for intra-CU and / or intra-DU scenarios.

[0255] As an embodiment, executing an RRC message means applying an RRC message.

[0256] As an embodiment, executing an RRC information block means applying an RRC information block.

[0257] As an embodiment, the compatibility check is to check whether the received RRC reconfiguration message is supported.

[0258] As an embodiment, the compatibility check is to check whether the received RRC reconfiguration message can be identified or recognized.

[0259] As an embodiment, the compatibility detection is to detect whether it is compatible with the at least one received RRC message block.

[0260] As an embodiment, the compatibility detection is to detect whether the at least one received RRC information block is supported.

[0261] As an embodiment, the compatibility detection is to detect whether the at least one received RRC information block can be identified or recognized.

[0262] As an embodiment, the compatibility detection includes detecting all RRC information blocks that need to be detected but have not been detected.

[0263] As an embodiment, the compatibility detection includes detecting all RRC information blocks that have not been detected.

[0264] As an embodiment, the compatibility detection includes detecting all RRC configurations that have not been detected.

[0265] As an embodiment, the compatibility detection includes detecting all RRC information blocks that need to be detected but have not been detected.

[0266] As an embodiment, the compatibility check is to check whether it is compatible with the received RRC reconfiguration message.

[0267] As a sub-embodiment of this embodiment, the at least one RRC information block is carried by an RRC reconfiguration message.

[0268] As a sub-embodiment of this embodiment, the first node detects compatibility according to whether each configuration included in the received RRC reconfiguration message is supported.

[0269] As an embodiment, passing the compatibility check means being compatible with every configuration in the received RRC reconfiguration message.

[0270] As an embodiment, failure to pass the compatibility check means being incompatible with at least one configuration in the received RRC reconfiguration message.

[0271] As an embodiment, the compatibility detection is to detect whether it is compatible with the at least one received RRC information block.

[0272] As a sub-embodiment of this embodiment, the first node detects compatibility according to whether each configuration or parameter included in each RRC information block in the at least one received RRC information block is supported.

[0273] As an embodiment, passing the compatibility detection means being compatible with each of the at least one received RRC information block.

[0274] As an embodiment, failure to pass the compatibility check means incompatibility with at least one of the at least one received RRC information block.

[0275] As an embodiment, being incompatible with an RRC information block means being incompatible with at least one configuration in the RRC information block.

[0276] As an embodiment, being incompatible with an RRC information block means that at least one configuration in the RRC information block is not supported.

[0277] As an embodiment, each RRC information in the at least one RRC information block is not ServingCellConfigCommon.

[0278] As an embodiment, each RRC information in the at least one RRC information block is not ServingCellConfigCommon of 3GPP Release 16 (Rel-16) and after 3GPP Release 16.

[0279] As an embodiment, each RRC information in the at least one RRC information block is not PDCCH-ConfigCommon.

[0280] As an embodiment, each RRC information in the at least one RRC information block is not PDCCH-ConfigCommon defined in 3GPP Release 17 (Rel-17).

[0281] As an embodiment, each RRC information in the at least one RRC information block is not PDCCH-ConfigCommon defined in the protocol after 3GPP Release 17 (Rel-17).

[0282] As an embodiment, each RRC information in the at least one RRC information block is not searchSpaceMCCH.

[0283] As an embodiment, each RRC information in the at least one RRC information block is not the searchSpaceMCCH defined by 3GPP Release 17 (Rel-17).

[0284] As an embodiment, each RRC information in the at least one RRC information block is not the searchSpaceMCCH defined by the protocol after 3GPP Release 17 (Rel-17).

[0285] As an embodiment, each RRC information in the at least one RRC information block is not searchSpaceMTCH.

[0286] As an embodiment, each RRC information in the at least one RRC information block is not searchSpaceMTCH defined by 3GPP Release 17 (Rel-17).

[0287] As an embodiment, each RRC information in the at least one RRC information block is not searchSpaceMTCH defined by the protocol after 3GPP Release 17 (Rel-17).

[0288] As an embodiment, the phrase "time when the behavior performs compatibility check" means: when the compatibility check is performed.

[0289] As an embodiment, the phrase "time when the behavior performs compatibility checking" means: when the execution of the compatibility checking is completed.

[0290] As an embodiment, compatibility checking is atomic.

[0291] As an embodiment, the sentence "application of any one of the at least one RRC information block does not depend on receipt of the second signaling" means or includes: the at least one RRC information block is executed or applied immediately after receipt.

[0292] As an embodiment, the sentence that the application of any one of the at least one RRC information blocks does not depend on the receipt of the second signaling means or includes: the at least one RRC information block is immediately executed or applied when decoding is completed or decoding is in progress.

[0293] As an embodiment, the sentence "application of any one of the at least one RRC information block does not depend on receiving the second signaling" means or includes: the at least one RRC information block is not an RRC information block of a candidate cell for configuring LTM.

[0294] As an embodiment, the sentence that the application of any one of the at least one RRC information blocks does not depend on the receipt of the second signaling means or includes: if the second signaling is not received, at least one of the at least one RRC information block can also be applied.

[0295] As a sub-embodiment of this embodiment, at least under normal circumstances, that is, when no failure occurs and RRC connection reestablishment is not performed.

[0296] As an embodiment, the sentence that application of any one of the at least one RRC information block does not depend on receiving the second signaling means or includes: the at least one RRC information block is an RRC information block related to conditional reconfiguration.

[0297] As an embodiment, the sentence that application of any one of the at least one RRC information block does not depend on receiving the second signaling means or includes: the at least one RRC information block belongs to ConditionalReconfiguration.

[0298] As an embodiment, the sentence that application of any one of the at least one RRC information block does not depend on receiving the second signaling means or includes: each of the at least one RRC information block belongs to ConditionalReconfiguration.

[0299] As an embodiment, the at least one RRC information block does not belong to ConditionalReconfiguration.

[0300] As an embodiment, the sentence when the application of any one of the at least one RRC information block depends on the receipt of the second signaling means or includes: the name of each of the at least one RRC information block includes LTM.

[0301] As an embodiment, the sentence when the application of any one of the at least one RRC information block does not depend on the receipt of the second signaling means or includes: the name of the at least one RRC information block does not include LTM.

[0302] As an embodiment, the sentence when the application of any one of the at least one RRC information block does not depend on the receipt of the second signaling means or includes: the name of the at least one RRC information block includes Cond.

[0303] As an embodiment, the predefined refers to: default.

[0304] As an embodiment, the predefined means: fixed.

[0305] As an embodiment, the predefined means: determined.

[0306] As an embodiment, the predefined means: required.

[0307] As an embodiment, the predefined means: needs to be defined.

[0308] As an embodiment, the time for the behavior to perform compatibility detection is predefined and includes: the behavior to perform compatibility detection needs to be performed when merging the reference RRC information block.

[0309] As an embodiment, the time for the behavior to perform compatibility detection is predefined and includes: the behavior to perform compatibility detection needs to be performed before merging the reference RRC information block.

[0310] As an embodiment, the time for the behavior to perform compatibility detection is predefined and includes: the behavior to perform compatibility detection needs to be performed when receiving the reference RRC information block.

[0311] As an embodiment, the time for the behavior to perform compatibility check is predefined and includes: the behavior to perform compatibility check needs to be performed immediately upon just receiving the reference RRC information block.

[0312] As an embodiment, the time for the behavior to perform compatibility detection is predefined, including: the behavior to perform compatibility detection needs to be started during the process of receiving the reference RRC information block.

[0313] As an embodiment, the time for the behavior to perform compatibility detection is predefined and includes: the behavior to perform compatibility detection needs to be performed before applying any of the RRC information blocks in the at least one RRC information block.

[0314] As an embodiment, the time for the behavior to perform compatibility detection is predefined and includes: the behavior to perform compatibility detection needs to be performed when receiving the at least one RRC information block.

[0315] As an embodiment, the time for the behavior to perform compatibility detection is predefined and includes: the behavior to perform compatibility detection needs to be performed immediately upon just receiving the at least one RRC information block.

[0316] As an embodiment, the time for the behavior to perform compatibility detection is predefined and includes: the behavior to perform compatibility detection needs to be performed during the process of receiving the at least one RRC information block.

[0317] As an embodiment, the time for the behavior to perform compatibility detection is predefined, including: the behavior to perform compatibility detection needs to be performed when the second signaling is received.

[0318] As an embodiment, using a predefined compatibility detection time is helpful to discover problems early, avoid accidents, and avoid repeated RRC connection reestablishment dead loops.

[0319] As an embodiment, the time for performing the compatibility check of the behavior is not defined, including: whether the compatibility check of the behavior needs to be performed before applying any of the RRC information blocks in the at least one RRC information block is not required.

[0320] As an embodiment, the time for performing the compatibility check of the behavior is not defined, including: the compatibility check of the behavior can be performed when the at least one RRC information block is received, and can also be performed when the at least one RRC information block is applied.

[0321] As an embodiment, adopting an undefined compatibility detection time is beneficial to achieving flexibility.

[0322] As an embodiment, the first node receives a first parameter, and the first parameter is used to determine that "when the application of any RRC information block in the at least one RRC information block depends on receiving a second signaling, the time for the behavior to perform compatibility detection is predefined" is established.

[0323] As an embodiment, the benefits of the above method include: making the compatibility detection time controllable to some extent, and helping the first node to better determine which compatibility detection time to adopt.

[0324] As an embodiment, the behavior of performing compatibility detection includes compatibility detection on an RRC information block in the at least one RRC information block.

[0325] As an embodiment, the behavior performs compatibility detection on an RRC information block in the at least one RRC information block.

[0326] As an embodiment, the behavior performs compatibility detection on each RRC information block in the at least one RRC information block.

[0327] As an embodiment, each RRC information block in the at least one RRC information block is configured with a different cell group.

[0328] As an embodiment, each RRC information block in the at least one RRC information block is respectively configured with a cell group including different SpCells.

[0329] As an embodiment, the multiple RRC information blocks in the at least one RRC information block are configured to include a cell group of the same SpCell.

[0330] As an embodiment, when the at least one RRC information block is received, no radio link failure occurs to the first node.

[0331] As an embodiment, when the at least one RRC information block is received, the first node does not initiate RRC connection reconstruction.

[0332] As an embodiment, the phrase application of any one of the at least one RRC information block depends on receipt of the second signaling means that when any one of the at least one RRC information block is applied, no wireless link failure occurs to the first node.

[0333] As an embodiment, the phrase application of any one of the at least one RRC information block depends on receiving the second signaling means that when any one of the at least one RRC information block is applied, the first node does not initiate RRC connection reconstruction.

[0334] As an embodiment, the first timer is not in a running state, and the starting condition of the first timer includes initiating an RRC reconstruction process.

[0335] As an embodiment, at least when the behavior performs compatibility detection, the first timer is not in a running state, and the start condition of the first timer includes initiating an RRC reconstruction process.

[0336] As an embodiment, the first timer is an RRC timer.

[0337] As an embodiment, the first timer is a T311 timer.

[0338] As an embodiment, the stop condition of the first timer includes: selecting a suitable NR cell.

[0339] As an embodiment, the stop condition of the first timer includes: selecting a suitable cell using other wireless access technologies.

[0340] As an embodiment, the stop condition of the first timer includes: selecting a suitable L2 U2N relay UE.

[0341] As an embodiment, expiration of the first timer triggers entering the RRC idle state.

[0342] Example 2

[0343] Embodiment 2 illustrates a schematic diagram of a network architecture according to the present application, as shown in the attached Figure 2 shown.

[0344] Attached Figure 2A diagram of a network architecture 200 for 5G NR, LTE (Long-Term Evolution) and LTE-A (Long-Term Evolution Advanced) systems is illustrated. The 5G NR or LTE network architecture 200 may be referred to as 5GS (5G System) / EPS (Evolved Packet System) 200 or some other suitable terminology. The 5GS / EPS 200 may include one or more UEs (User Equipment) 201, NG-RAN (Next Generation Radio Access Network) 202, 5GC (5G Core Network) / EPC (Evolved Packet Core) 210, HSS (Home Subscriber Server) / UDM (Unified Data Management) 220, and Internet services 230. The 5GS / EPS may be interconnected with other access networks, but these entities / interfaces are not shown for simplicity. As shown, 5GS / EPS provides packet-switched services, however, those skilled in the art will readily appreciate that the various concepts presented throughout this application can be extended to networks providing circuit-switched services or other cellular networks. NG-RAN includes NR Node B (gNB) 203 and other gNBs 204. gNB 203 provides user and control plane protocol terminations toward UE 201. gNB 203 can be connected to other gNBs 204 via an Xn interface (e.g., backhaul). gNB 203 may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP (transmitting receiving node), or some other suitable term. gNB 203 provides an access point to 5GC / EPC 210 for UE 201. Examples of UE 201 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, non-terrestrial base station communications, satellite mobile communications, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, drones, aircraft, narrowband Internet of Things devices, machine type communication devices, land vehicles, cars, wearable devices, or any other similar functional devices. Those skilled in the art may also refer to UE 201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable term.gNB203 is connected to 5GC / EPC210 via the S1 / NG interface. 5GC / EPC210 includes MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MME / AMF / SMF214, S-GW (Service Gateway) / UPF (User Plane Function) 212, and P-GW (Packet Data Network Gateway) / UPF213. MME / AMF / SMF211 is the control node that handles signaling between UE201 and 5GC / EPC210. ​​In general, MME / AMF / SMF211 provides bearer and connection management. All user IP (Internet Protocol) packets are transmitted through S-GW / UPF212, which itself is connected to P-GW / UPF213. P-GW provides UE IP address allocation and other functions. P-GW / UPF213 is connected to Internet service 230. Internet service 230 includes operator-corresponding Internet protocol services, which may specifically include Internet, Intranet, IMS (IP Multimedia Subsystem) and packet-switched streaming services.

[0345] As an embodiment, the first node in the present application is UE201.

[0346] As an embodiment, the base station of the second node in the present application is gNB203.

[0347] As an embodiment, the wireless link from the UE201 to the NR Node B is an uplink.

[0348] As an embodiment, the wireless link from the NR Node B to UE201 is a downlink.

[0349] As an embodiment, the UE 201 supports relay transmission.

[0350] As an embodiment, the UE 201 includes a mobile phone.

[0351] As an embodiment, the UE 201 is a vehicle including a car.

[0352] As an embodiment, the gNB203 is a macrocellular base station.

[0353] As an embodiment, the gNB203 is a micro cell base station.

[0354] As an embodiment, the gNB203 is a pico cell base station.

[0355] As an embodiment, the gNB203 is a flying platform device.

[0356] As an embodiment, the gNB203 is a satellite device.

[0357] Example 3

[0358] Embodiment 3 shows a schematic diagram of an embodiment of a wireless protocol architecture of a user plane and a control plane according to the present application, as shown in the attached Figure 3 shown. Figure 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300, Figure 3The radio protocol architecture of the control plane 300 for a first node (UE, satellite or aircraft in gNB or NTN) and a second node (satellite or aircraft in gNB, UE or NTN), or between two UEs is shown in three layers: Layer 1, Layer 2, and Layer 3. Layer 1 (L1 layer) is the lowest layer and implements various PHY (physical layer) signal processing functions. The L1 layer will be referred to as PHY301 in this article. Layer 2 (L2 layer) 305 is above PHY301 and is responsible for the link between the first node and the second node and the two UEs through PHY301. The L2 layer 305 includes a MAC (Medium Access Control) sublayer 302, an RLC (Radio Link Control) sublayer 303, and a PDCP (Packet Data Convergence Protocol) sublayer 304, which terminate at the second node. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by encrypting data packets, and provides support for inter-zone mobility of the first node between the second node. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to HARQ. The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) in a cell between the first nodes. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in layer 3 (L3 layer) in the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring the lower layer using RRC signaling between the second node and the first node. The PC5-S (PC5 Signaling Protocol) sublayer 307 is responsible for processing the signaling protocol of the PC5 interface. The radio protocol architecture of the user plane 350 includes Layer 1 (L1 layer) and Layer 2 (L2 layer). The radio protocol architecture for the first node and the second node in the user plane 350 is substantially the same as the corresponding layers and sublayers in the control plane 300 for the physical layer 351, the PDCP sublayer 354 in the L2 layer 355, the RLC sublayer 353 in the L2 layer 355, and the MAC sublayer 352 in the L2 layer 355, but the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead.The L2 layer 355 in the user plane 350 also includes an SDAP (Service Data Adaptation Protocol) sublayer 356, which is responsible for mapping between QoS flows and data radio bearers (DRBs) to support the diversity of services. SRB can be regarded as a service or interface provided by the PDCP layer to a higher layer, such as the RRC layer. In the NR system, SRBs include SRB1, SRB2, SRB3, and SRB4 when it comes to sidelink communication, which are used to transmit different types of control signaling. SRB is a bearer between the UE and the access network, and is used to transmit control signaling including RRC signaling between the UE and the access network. SRB1 has special significance for the UE. After each UE establishes an RRC connection, there will be SRB1 for transmitting RRC signaling. Most of the signaling is transmitted through SRB1. If SRB1 is interrupted or unavailable, the UE must perform RRC reconstruction. SRB2 is generally only used to transmit NAS signaling or signaling related to security. The UE may not configure SRB3. Except for emergency services, the UE must establish an RRC connection with the network for subsequent communications. Although not shown in the figure, the first node may have several upper layers above the L2 layer 355. In addition, it also includes a network layer (e.g., IP layer) terminated at the P-GW on the network side and an application layer terminated at the other end of the connection (e.g., remote UE, server, etc.). For UEs involved in relay services, its control plane may also include an adaptation sublayer SRAP (Sidelink Relay Adaptation Protocol, sidelink relay adaptation) 308, and its user plane may also include an adaptation sublayer SRAP358. The introduction of the adaptation layer helps lower layers, such as the MAC layer, such as the RLC layer, to multiplex and / or distinguish data from multiple source UEs. For nodes not involved in relay communications, PC5-S307, SRAP308, and SRAP358 are not required during the communication process.

[0359] As an example, Figure 3 The wireless protocol architecture in is applicable to the first node in this application.

[0360] As an example, Figure 3 The wireless protocol architecture in is applicable to the second node in this application.

[0361] As an embodiment, the first signaling in the present application is generated in RRC306.

[0362] As an embodiment, the at least one RRC information block in the present application is generated in RRC306.

[0363] As an embodiment, the reference RRC information block in the present application is generated in RRC306.

[0364] As an embodiment, the second signaling in the present application is generated in MAC302 or PHY301.

[0365] As an embodiment, the at least one report in the present application is generated in RRC306.

[0366] As an embodiment, the reference RRC information block in the present application is generated in RRC306.

[0367] Example 4

[0368] Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to an embodiment of the present application, as shown in the attached figure. Figure 4 shown. Figure 4 is a block diagram of a first communication device 450 and a second communication device 410 communicating with each other in an access network.

[0369] The first communication device 450 includes a controller / processor 459, a memory 460, a data source 467, a transmit processor 468, a receive processor 456, and may optionally also include a multi-antenna transmit processor 457, a multi-antenna receive processor 458, a transmitter / receiver 454 and an antenna 452.

[0370] The second communication device 410 includes a controller / processor 475 , a memory 476 , a receiving processor 470 , a transmitting processor 416 , and may optionally also include a multi-antenna receiving processor 472 , a multi-antenna transmitting processor 471 , a transmitter / receiver 418 and an antenna 420 .

[0371] In the transmission from the second communication device 410 to the first communication device 450, at the second communication device 410, the upper layer data packets from the core network are provided to the controller / processor 475. The controller / processor 475 implements the functionality of the L2 (Layer-2) layer. In the transmission from the second communication device 410 to the first communication device 450, the controller / processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the first communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for the retransmission of lost packets and signaling to the first communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., the physical layer). The transmit processor 416 implements coding and interleaving to facilitate forward error correction (FEC) at the second communication device 410, as well as mapping of signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing on the coded and modulated symbols to generate one or more spatial streams. The transmit processor 416 then maps each spatial stream to a subcarrier, multiplexes it with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then uses an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain multi-carrier symbol stream. The multi-antenna transmit processor 471 then performs a transmit analog precoding / beamforming operation on the time-domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multi-carrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream, and then provides it to a different antenna 420.

[0372] In the transmission from the second communication device 410 to the first communication device 450, at the first communication device 450, each receiver 454 receives a signal through its corresponding antenna 452. Each receiver 454 recovers the information modulated onto the RF carrier and converts the RF stream into a baseband multi-carrier symbol stream and provides it to the receiving processor 456. The receiving processor 456 and the multi-antenna receiving processor 458 implement various signal processing functions of the L1 layer. The multi-antenna receiving processor 458 performs a receiving analog precoding / beamforming operation on the baseband multi-carrier symbol stream from the receiver 454. The receiving processor 456 uses a fast Fourier transform (FFT) to convert the baseband multi-carrier symbol stream after the receiving analog precoding / beamforming operation from the time domain to the frequency domain. In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receiving processor 456, wherein the reference signal will be used for channel estimation, and the data signal is recovered after multi-antenna detection in the multi-antenna receiving processor 458 to any spatial stream destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered in the receiving processor 456, and soft decisions are generated. The receiving processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communication device 410 on the physical channel. The upper layer data and control signals are then provided to the controller / processor 459. The controller / processor 459 implements the functions of the L2 layer. The controller / processor 459 may be associated with a memory 460 that stores program codes and data. The memory 460 may be referred to as a computer-readable medium. In the transmission from the second communication device 410 to the second communication device 450, the controller / processor 459 provides multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover the upper layer data packets from the core network. The upper layer data packets are then provided to all protocol layers above the L2 layer. Various control signals may also be provided to L3 for L3 processing.

[0373] In the transmission from the first communication device 450 to the second communication device 410, at the first communication device 450, a data source 467 is used to provide upper layer data packets to the controller / processor 459. The data source 467 represents all protocol layers above the L2 layer. Similar to the transmission function at the second communication device 410 described in the transmission from the second communication device 410 to the first communication device 450, the controller / processor 459 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocation, and implements L2 layer functions for user plane and control plane. The controller / processor 459 is also responsible for the retransmission of lost packets and signaling to the second communication device 410. The transmit processor 468 performs modulation mapping and channel coding processing, and the multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing. Then, the transmit processor 468 modulates the generated spatial stream into a multi-carrier / single-carrier symbol stream, which is then provided to different antennas 452 via the transmitter 454 after analog precoding / beamforming operations in the multi-antenna transmit processor 457. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a radio frequency symbol stream, and then provides it to the antenna 452.

[0374] In the transmission from the first communication device 450 to the second communication device 410, the function at the second communication device 410 is similar to the reception function at the first communication device 450 described in the transmission from the second communication device 410 to the first communication device 450. Each receiver 418 receives a radio frequency signal through its corresponding antenna 420, converts the received radio frequency signal into a baseband signal, and provides the baseband signal to the multi-antenna reception processor 472 and the reception processor 470. The reception processor 470 and the multi-antenna reception processor 472 jointly implement the functions of the L1 layer. The controller / processor 475 implements the L2 layer functions. The controller / processor 475 can be associated with a memory 476 storing program codes and data. The memory 476 can be referred to as a computer-readable medium. In the transmission from the first communication device 450 to the second communication device 410, the controller / processor 475 provides multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover the upper layer data packets from the UE 450. Upper layer packets from controller / processor 475 may be provided to the core network.

[0375] As an embodiment, the first communication device 450 apparatus includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor, and the first communication device 450 apparatus at least: receives a first signaling, the first signaling includes at least one RRC information block, each of the at least one RRC information block is used to configure a cell group; performs a compatibility check, and the time for the behavior to perform the compatibility check depends on the at least one RRC information block; wherein, the sentence that the time for the behavior to perform the compatibility check depends on the at least one RRC information block means: when the application of any RRC information block in the at least one RRC information block depends on the receipt of a second signaling, the time for the behavior to perform the compatibility check is predefined; when the application of any RRC information block in the at least one RRC information block does not depend on the receipt of the second signaling, the time for the behavior to perform the compatibility check is not defined; the second signaling is a signaling of a protocol layer below the RRC layer, and the second signaling indicates any of the at least one RRC information block.

[0376] As an embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generates an action when executed by at least one processor, the action including: receiving a first signaling, the first signaling including at least one RRC information block, each of the at least one RRC information block being used to configure a cell group; performing a compatibility check, the time for the behavior to perform the compatibility check being dependent on the at least one RRC information block; wherein, the sentence that the time for the behavior to perform the compatibility check is dependent on the at least one RRC information block means: when the application of any RRC information block in the at least one RRC information block depends on the receipt of a second signaling, the time for the behavior to perform the compatibility check is predefined; when the application of any RRC information block in the at least one RRC information block does not depend on the receipt of the second signaling, the time for the behavior to perform the compatibility check is not defined; the second signaling is a signaling of a protocol layer below the RRC layer, the second signaling indicates any of the at least one RRC information block.

[0377] As an embodiment, the first communication device 450 corresponds to the first node in this application.

[0378] As an embodiment, the second communication device 410 corresponds to the second node in this application.

[0379] As an embodiment, the first communication device 450 is a UE.

[0380] As an embodiment, the first communication device 450 is a vehicle-mounted terminal.

[0381] As an embodiment, the first communication device 450 is a mobile phone.

[0382] As an embodiment, the second communication device 450 is a relay.

[0383] As an embodiment, the second communication device 410 is a satellite.

[0384] As an embodiment, the second communication device 410 is an aircraft.

[0385] As an embodiment, the second communication device 410 is a base station.

[0386] As an embodiment, the receiver 454 (including the antenna 452), the receiving processor 456 and the controller / processor 459 are used to receive the first signaling in the present application.

[0387] As an embodiment, the receiver 454 (including the antenna 452), the receiving processor 456 and the controller / processor 459 are used to receive the second signaling in the present application.

[0388] As an embodiment, the receiver 454 (including the antenna 452), the receiving processor 456 and the controller / processor 459 are used to receive the reference RRC information block in the present application.

[0389] As an embodiment, the transmitter 454 (including the antenna 452), the transmit processor 468 and the controller / processor 459 are used to send the first report in the present application.

[0390] Example 5

[0391] Embodiment 5 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in the attached Figure 5 Attached Figure 5 In the example, U01 corresponds to the first node of the present application. It is particularly noted that the order in this example does not limit the signal transmission order and implementation order in the present application, wherein the steps in F51 are optional.

[0392] for First node U01 , receiving the first signaling in step S5101; performing compatibility detection in step S5102; initiating RRC connection reconstruction in step S5103; sending the first report in step S5104; receiving the second signaling in step S5105; and applying the first RRC information block in step S5106.

[0393] for Second node U02 , sending a first signaling in step S5201; sending a second signaling in step S5202; receiving a first report in step S5203.

[0394] In embodiment 5, the first signaling includes at least one RRC information block; each RRC information block in the at least one RRC information block is used to configure a cell group; the time for the behavior to perform compatibility detection depends on the at least one RRC information block; wherein, the sentence "the time for the behavior to perform compatibility detection depends on the at least one RRC information block" means that: when the application of any RRC information block in the at least one RRC information block depends on receiving the second signaling, the time for the behavior to perform compatibility detection is predefined; when the application of any RRC information block in the at least one RRC information block does not depend on receiving the second signaling, the time for the behavior to perform compatibility detection is not defined; the second signaling is the signaling of the protocol layer below the RRC layer, and the second signaling indicates any RRC information block in the at least one RRC information block.

[0395] As an embodiment, the second node U02 is a base station.

[0396] As an embodiment, the second node U02 is a network device.

[0397] As an embodiment, the second node U02 is the source cell of the first node U01.

[0398] As an embodiment, the second node U02 is the source SpCell of the first node U01.

[0399] As an embodiment, the second node U02 is the primary cell group of the first node U01.

[0400] As an embodiment, the second node U02 is the PCell of the first node U01 when receiving the at least one RRC information block.

[0401] As an embodiment, the first node U01 switches from the second node U02 to the target SpCell.

[0402] As a sub-embodiment of this embodiment, the first node U01 switches to the target SpCell through LTM.

[0403] As an embodiment, each RRC information block of the at least one RRC information block includes pre-configuration parameters for switching.

[0404] As an embodiment, the switching includes LTM.

[0405] As an embodiment, the SpCell of the first node U01 after successfully executing step S5103 is the SpCell configured by the first RRC information block.

[0406] As an embodiment, the first signaling optionally includes a reference RRC information block.

[0407] As an embodiment, the first signaling may not be configured with a reference RRC information block.

[0408] As an embodiment, the first signaling is used for RRC reconfiguration.

[0409] As an embodiment, the first signaling is an RRCReconfiguration message.

[0410] As an embodiment, the second node U02 configures at least one RRC information block for each UE through an RRCReconfiguration message.

[0411] As an embodiment, the reference RRC information block may not include any content.

[0412] As an embodiment, the reference RRC information block is used to configure a cell group.

[0413] As an embodiment, the reference RRC information block provides a basic configuration.

[0414] As an embodiment, the reference RRC information block configures the radio bearer of the cell group, for example, configures the length of the sequence number of the PDCP, configures which QoS flows the radio bearer is used to carry, and the like.

[0415] As an embodiment, the reference RRC information block configures the T311 timer of the cell group.

[0416] As an embodiment, the reference RRC information block configures a T310 timer of a cell group, and the T310 timer is used for radio link failure.

[0417] As an embodiment, the reference RRC information block configures the value of the N311 counter of the cell group. When the RRC layer receives an indication of poor quality of N311 links from the physical layer, the T310 timer is started. Expiration of the T310 timer triggers a wireless link failure.

[0418] As an embodiment, after a wireless link failure occurs, the first node U01 needs to initiate RRC connection reconstruction.

[0419] As an embodiment, in the merging of the at least one RRC information block and the reference RRC information block, the configuration in the at least one RRC information block overwrites the configuration for the same matter in the reference RRC information block.

[0420] As an embodiment, the behavior execution compatibility detection only includes the former of any one of the at least one RRC information block and the reference RRC information block.

[0421] As an embodiment, the sentence that the behavior of performing compatibility detection only includes any one of the at least one RRC information block and the reference RRC information block means that the first node U01 ignores that the reference RRC information block fails the compatibility detection.

[0422] As an embodiment, the sentence that the behavior of performing compatibility detection only includes any one of the at least one RRC information block and the reference RRC information block means that the first node U01 ignores that the reference RRC information block is not supported or not recognized.

[0423] As an embodiment, the above method has the following benefits: it can improve the speed of compatibility detection and reduce latency; it is helpful to avoid RRC connection reconstruction caused by overly strict detection of the reference RRC information block.

[0424] As an embodiment, the sentence that the behavior of performing compatibility check only includes any one of the at least one RRC information block and the former of the reference RRC information block includes: even if the compatibility check is performed on the reference RRC information block and fails, and the RRC configurations other than the reference RRC information block pass the compatibility check, the first node U01 does not take any action.

[0425] As an embodiment, the phrase applying any one of the at least one RRC information block means that any one of the at least one RRC information block needs to be combined with the reference RRC information block and then applied.

[0426] As an embodiment, the first node receives 2 RRC information blocks, each RRC information block configures a cell group respectively, including configuring random access resources of the cell group and a timer for wireless link failure detection and a timer related to RRC connection reconstruction; the first node U01 performs compatibility detection, and the compatibility detection includes detecting whether the at least one received RRC information block is supported. For example, the first node U01 only supports the timer related to the RRC connection reconstruction to be configured within 5 seconds, and cannot support it if it is configured to exceed 5 seconds; the execution of each RRC information block in the at least one RRC information block depends on receiving the second signaling, that is, only after the receiving end receives the second signaling, the RRC information block in the at least one RRC information block will be applied, then the first node U01 receives the Step S5102 is performed immediately after receiving the at least one RRC information block; if the compatibility test fails, the first node U01 initiates RRC connection reconstruction and sends a first report, the RRC connection reconstruction is used to re-establish the RRC connection, including sending an RRC connection reconstruction request and starting the timer related to the RRC reconstruction, the first report indicates that the compatibility test fails, the first node U01 uses the configuration before receiving the at least one RRC information block to initiate the RRC reconstruction process and send the first report, for example, including the value of the timer related to the RRC reconstruction; if the compatibility test passes, the first node U01 waits for a second signaling, and after receiving the second signaling, applies the first RRC information block, the second signaling indicates the first RRC information block, and the second signaling is MAC CE.

[0427] As a sub-embodiment of this embodiment, in this embodiment, RRC connection reconstruction may also include selecting a service cell. If this service cell happens to be the SpCell of the cell group configured by one of the at least one RRC information blocks, partial configuration of the one RRC information block is applied. For example, the cell selected by the first node U01 itself can only use contention-based random access, and contention-free random access can be applied when indicated by the second signaling.

[0428] As a sub-embodiment of this embodiment, depending on the second signaling, the at least one RRC information block will be stored after being received and wait to be applied. If the compatibility check is performed late and the compatibility check fails, using the configuration before the compatibility check does not affect the at least one RRC information block stored.

[0429] As a sub-embodiment of this embodiment, those skilled in the art can easily understand that the second node U02 can indicate which of the at least one RRC information block the first RRC information block is through the second signaling according to the channel quality.

[0430] As an embodiment, the first node receives two RRC information blocks, each RRC information block configures a cell group, namely MCG and SCG, including configuring random access resources of the cell group and a timer for wireless link failure detection and a timer related to RRC connection reconstruction; the first node U01 performs compatibility detection, and the compatibility detection includes detecting whether the at least one received RRC information block is supported, for example, the first node U01 only supports the timer related to the RRC connection reconstruction to be configured within 5 seconds, and cannot support it if it is configured to exceed 5 seconds; the execution of each RRC information block in the at least one RRC information block does not depend on the receipt of the second signaling, and the first node U01 can decide when to execute the at least one RRC information block, for example, when the CPU is idle, for example, when the channel quality deteriorates. time, for example, immediately apply, for example, when the data in the cache is sent; then the first node U01 executes step S5102 when executing the at least one RRC information block; if the compatibility test fails, the first node U01 initiates RRC connection reconstruction, and the RRC connection reconstruction is used to re-establish the RRC connection, including sending an RRC connection reconstruction request and starting the timer related to the RRC reconstruction. The first node U01 uses the configuration before receiving the at least one RRC information block to initiate the RRC reconstruction process, for example, including the value of the timer related to the RRC reconstruction; if the compatibility test passes, the first node U01 applies the at least one RRC information block; obviously in this embodiment, step S5105 is not required; the first RRC information block is any RRC information block in the at least one RRC information block.

[0431] As an embodiment, since at least one RRC information block applied by relying on the second signaling may cause an infinite loop of RRC connection reconstruction if it fails the compatibility check, it is necessary to define the time for the compatibility check. In this way, the time for the compatibility check is predefined, which is conducive to avoiding such an infinite loop. When not relying on the second signaling, it generally does not cause an infinite loop of RRC connection reconstruction, and the time for the compatibility check may not be defined, providing sufficient flexibility for implementation.

[0432] As an embodiment, the first RRC information block is any RRC information block among the at least one RRC information block.

[0433] As an embodiment, the first RRC information block is the RRC information block indicated by the second signaling in the at least one RRC information block.

[0434] As an embodiment, the first RRC information block is any one of the at least one RRC information blocks indicated by the second signaling.

[0435] As an embodiment, the first RRC information block is the first or highest priority RRC information block indicated by the second signaling among the at least one RRC information block.

[0436] As an embodiment, the first RRC information block includes SpCellConfig.

[0437] As an embodiment, the first RRC information block includes ReconfigurationWithSync.

[0438] As an embodiment, the air interface between the first node U01 and the second node U02 is a Uu interface.

[0439] As an embodiment, the first node U01 is in an RRC connected state.

[0440] As an embodiment, each RRC information block in the at least one RRC information block is used to configure a target cell group.

[0441] As an embodiment, each RRC information block in the at least one RRC information block is used to configure a candidate target cell group.

[0442] As an embodiment, the cells included in the cell group configured by the at least one RRC information block are nodes other than the second node U02.

[0443] As an embodiment, the cells included in the cell group configured by the at least one RRC information block are not restricted to be nodes other than the second node U02.

[0444] As an embodiment, the method proposed in the present application does not limit whether the SpCell of the cell group configured by the at least one RRC information block is the second node U02 or a cell other than the second node U02.

[0445] As an embodiment, after the second node U02 applies the first RRC information block, it is determined that the cell switch is successful.

[0446] As an embodiment, the cell switching is or includes LTM.

[0447] As an example, Figure 5 The order of the steps in is one implementation method.

[0448] As an embodiment, step S5101 precedes step S5102.

[0449] As an embodiment, the reference RRC information block and the at least one RRC information block are carried by the same RRC message.

[0450] As an embodiment, step S5102 may be performed simultaneously with step S5101, that is, when the at least one RRC information block has not been completely received, the compatibility check is started, for example, the compatibility check is generally started when the at least one RRC information is decoded.

[0451] As a sub-embodiment of this embodiment, the at least one RRC information block depends on the second signaling.

[0452] As an embodiment, step S5103 is after step S5102.

[0453] As an embodiment, step S5104 is after step S5102.

[0454] As an embodiment, step S5105 is after step S5101.

[0455] As an embodiment, step S5105 and step S5103 do not exist at the same time, and step S5104 is triggered by the failure of compatibility detection.

[0456] As an embodiment, step S5106 is after step S5105.

[0457] As an embodiment, when the application of the at least one RRC information block does not depend on the second signaling, step S5105 does not exist.

[0458] As an embodiment, step S5202 precedes step S5203.

[0459] As an embodiment, step S5202 and step S5203 do not exist at the same time.

[0460] As an embodiment, there is no clear order requirement for step S5202 and step S5203.

[0461] As an embodiment, the sentence "application of any one of the at least one RRC information block depends on receiving the second signaling" means that execution of each of the at least one RRC information block depends on the second signaling.

[0462] As an embodiment, the execution of each of the at least one RRC information block depends on the second signaling, including: the at least one RRC information block is not executed immediately or automatically after being received, but waits for the second signaling, and one of the at least one RRC information blocks is executed only when triggered by the second signaling.

[0463] As an embodiment, the second signaling includes DCI.

[0464] As an embodiment, the second signaling is or includes MAC CE.

[0465] As an embodiment, those skilled in the art can easily understand that, similar to other transmissions, the first node U01 may need to monitor the PDCCH to receive the second signaling.

[0466] As an embodiment, the second signaling is unicast.

[0467] As an embodiment, the second signaling indicates the reference signal resources of the target SpCell.

[0468] As an embodiment, the second signaling indicates the beam information of the target SpCell.

[0469] As an embodiment, in step S5106, applying the first RRC information block includes applying a TCI (transmission configuration indication) state.

[0470] As an embodiment, in step S5106, applying the first RRC information block includes applying a TCI (transmission configuration indication) state of the SpCell of the cell group configured for the first RRC information block.

[0471] As an embodiment, in step S5106, applying the first RRC information block includes applying a TCI (transmission configuration indication) state associated with the SpCell of the cell group configured by the first RRC information block.

[0472] As an embodiment, step S5106 includes applying a unified TCI state.

[0473] As an embodiment, as an embodiment, step S5106 includes sending a random access signal to the SpCell of the cell group configured by the first RRC information block; when the SpCell configured by the first RRC information block is or includes the second node U02, the recipient of the random access signal is the second node U02; when the SpCell configured by the first RRC information block is not the second node U02, the recipient of the random access signal is a node other than the second node U02.

[0474] As a sub-embodiment of this embodiment, the recipient of the first signal is the SpCell of the cell group configured by the first RRC information block.

[0475] As an embodiment, step S5103 includes sending an RRC connection reestablishment request, wherein the RRC connection reestablishment request indicates that there is an available report, and the second node U02 sends a message requesting the available report, thereby triggering the first report.

[0476] As an embodiment, when the first node U01 stores information for generating the first report, the first node U01 indicates that there is an available report in the RRC reestablishment request message.

[0477] As an embodiment, the first report includes a UEAssistanceInformation message.

[0478] As an embodiment, the first report includes at least part of the fields of the UEAssistanceInformation message.

[0479] As an embodiment, the UEAssistanceInformation message is an RRC message.

[0480] As an embodiment, the UEAssistanceInformation message is generated by the RRC layer.

[0481] As an embodiment, step S5103 is a response to the at least one RRC information block failing the compatibility check.

[0482] As an embodiment, the behavior of initiating RRC connection reconstruction includes starting the first timer.

[0483] As an embodiment, the first timer is a timer related to RRC connection reconstruction.

[0484] As an embodiment, the first timer is a T311 timer.

[0485] As an embodiment, in response to the at least one RRC information block failing the compatibility check, the first attempt is abandoned; in step S5103, whether to allow the triggering application of the RRC information block in the at least one RRC information block depends on whether the first attempt is configured.

[0486] As an embodiment, when the first attempt is configured, in step S5103, triggering the application of the RRC information block in the at least one RRC information block is allowed; when the first attempt is not configured or the first attempt is abandoned, triggering the application of the RRC information block in the at least one RRC information block is not allowed in the RRC connection reconstruction.

[0487] As an embodiment, in step S5103, in response to the at least one RRC information block failing the compatibility check, the first attempt is abandoned, and whether the triggering application of the RRC information block in the at least one RRC information block is allowed depends on whether the first attempt is configured.

[0488] As an embodiment, when the first attempt is configured, in step S5103, triggering the application of the RRC information block in the at least one RRC information block is allowed; when the first attempt is not configured or the first attempt is abandoned, triggering the application of the RRC information block in the at least one RRC information block is not allowed in the RRC connection reconstruction.

[0489] As an embodiment, the at least one RRC information block configures or does not configure the first attempt.

[0490] As an embodiment, the RRC message carrying the at least one RRC information block configures or does not configure the first attempt.

[0491] As an embodiment, the first attempt is a configuration item.

[0492] As an embodiment, the phrase allowing triggering the application of an RRC information block in the at least one RRC information block means or includes: when the cell selected by the first node U01 in step S5103 is the SpCell of the cell group configured by the RRC information block in the at least one RRC information, triggering the execution of at least partial configuration of the RRC information block in the at least one RRC information block.

[0493] As an embodiment, not allowing the triggering application of the RRC information block in the at least one RRC information block means or includes: regardless of whether the cell selected by the first node U01 in step S5103 is the SpCell of the cell group configured by the RRC information block in the at least one RRC information, the execution of the RRC information block in the at least one RRC information block will not be triggered.

[0494] As an embodiment, the benefits of the above method include avoiding falling into an infinite loop of RRC connection reestablishment, that is, the first node U01 can determine on its own not to perform the first attempt, making the RRC connection reestablishment more robust.

[0495] As an embodiment, in response to at least one RRC information block failing the compatibility check, a first operation is performed, and the first operation depends on the number of consecutive failures of the compatibility check; when the number of consecutive failures of the compatibility check is not less than a first threshold, the first operation is to enter the RRC idle state; when the number of consecutive failures of the compatibility check is less than the first threshold, the first operation is to initiate RRC connection reconstruction.

[0496] As a sub-embodiment of this embodiment, when the first operation is to initiate RRC reconstruction, it corresponds to step S5103.

[0497] As a sub-embodiment of this embodiment, when the first operation is to enter the RRC idle state, step S5103 does not exist, and step S5104 occurs after the next access to the network.

[0498] As a sub-embodiment of this embodiment, the continuous failure of the compatibility test refers to the failure to trigger the initiation of RRC connection reconstruction. During the RRC connection reconstruction, since the compatibility test is performed again when executing at least part of the configuration of at least one RRC information block and the compatibility test fails, it is regarded as a continuous failure of the compatibility test.

[0499] As a sub-embodiment of this embodiment, the continuous failure of compatibility detection refers to multiple compatibility detections on items included in the RRC reconfiguration message that has been received rather than compatibility detections performed on newly received or subsequently received RRC reconfiguration messages.

[0500] As an embodiment, RRC connection reestablishment is initiated in response to the RRC message carrying the at least one RRC information block failing compatibility detection and the at least one RRC information block having no compatibility issues.

[0501] As an embodiment, the first threshold is configurable.

[0502] As an embodiment, the first threshold is a positive integer.

[0503] As an embodiment, the first threshold is a positive integer greater than 1.

[0504] As an embodiment, the benefits of the above method include avoiding falling into an endless loop of RRC connection reestablishment and being controlled by a first threshold.

[0505] As an embodiment, in response to the at least one RRC information block failing the compatibility check, only the RRC information block that failed the compatibility check among the at least one RRC information block is discarded.

[0506] As an embodiment, the first report indicates a discarded RRC information block, or the first report indicates an RRC information block among the at least one RRC information block that fails the compatibility check.

[0507] As an embodiment, failure of the at least one RRC information block to pass the compatibility check will not trigger RRC connection reconstruction.

[0508] As a sub-embodiment of this embodiment, in this embodiment, step S5103 does not exist.

[0509] As an embodiment, the at least one RRC information block is stored in a state variable, and the behavior of discarding the RRC information block that fails to pass the compatibility check in the at least one RRC information block includes: deleting the RRC information block that fails to pass the compatibility check in the at least one RRC information block from the stored state variable.

[0510] As an embodiment, the benefits of the above method include that available configurations can be saved as much as possible, interruptions can be reduced as much as possible, and the impact of compatibility detection failure on the terminal can be reduced.

[0511] As an embodiment, in response to the at least one RRC information block failing the compatibility check, all RRC information blocks in the at least one RRC information block are discarded.

[0512] As a sub-embodiment of this embodiment, the at least one RRC information block is stored in a state variable, and the behavior of discarding the at least one RRC information block includes: deleting the at least one RRC information block from the stored state variable.

[0513] As a sub-embodiment of this embodiment, the at least one RRC information block is stored in a state variable, and the behavior of discarding the at least one RRC information block includes: deleting or clearing the state variable storing the at least one RRC information block.

[0514] As a sub-embodiment of this embodiment, the benefits of the above method include: reducing the impact of the at least one RRC information block on communication as much as possible; maintaining consistency in signaling processing between the base station and the terminal, that is, for the at least one RRC information block, either use it or not use it.

[0515] As an embodiment, the first timing advance indicated by the second signaling is applied; after the first timing advance indicated by the second signaling is applied, as a response to the at least one RRC information block failing the compatibility check, only the configuration before the compatibility check except the first timing advance is restored.

[0516] As a sub-embodiment of this embodiment, step S5105 precedes step S5102.

[0517] As a sub-embodiment of this embodiment, the sentence "only restore the configuration before the compatibility check except the first timing advance" means: do not restore the timing advance before receiving the second signaling.

[0518] As a sub-embodiment of this embodiment, the compatibility detection does not include or target the second signaling.

[0519] As a sub-embodiment of this embodiment, the second signaling is executed immediately after being received.

[0520] As a sub-embodiment of this embodiment, the benefits of the method proposed in this embodiment include: the latest timing advance information can be used to reduce delay.

[0521] As a sub-embodiment of this embodiment, step S5102 is at least before step S5106.

[0522] As a sub-embodiment of this embodiment, step S5102 is an atypical case at least before step S5106.

[0523] As a sub-embodiment of this embodiment, the configuration before the compatibility detection is a configuration of the RRC layer.

[0524] Example 6

[0525] Example 6 illustrates a schematic diagram of an LTM according to an embodiment of the present application, as shown in the attached Figure 6 As shown, attached Figure 6 The mobile phone in the figure corresponds to the first node of the present application, and the straight line with an arrow indicates that the first node moves from the source SpCell to the target SpCell.

[0526] As an embodiment, LTM is layer 1 and / or layer 2 triggered mobility.

[0527] As a sub-embodiment of this embodiment, the layer 1 refers to layer 1 signaling.

[0528] As a sub-embodiment of this embodiment, the layer 1 signaling refers to DCI.

[0529] As a sub-embodiment of this embodiment, the layer 2 refers to layer 2 signaling.

[0530] As a sub-embodiment of this embodiment, the layer 2 signaling refers to MAC CE.

[0531] As a sub-embodiment of this embodiment, the layer 2 signaling refers to the second signaling.

[0532] As an embodiment, the LTM includes switching from a source SpCell to a target SpCell.

[0533] As a sub-embodiment of this embodiment, the phrase switching from a source SpCell to a target SpCell means switching from a source PCell to a target PCell.

[0534] As a sub-embodiment of this embodiment, the phrase switching from a source SpCell to a target SpCell means switching from a source PSCell to a target PSCell.

[0535] As a sub-embodiment of this embodiment, since each SpCell is the SpCell of a cell group, it also means switching from one cell group to another cell group.

[0536] As an embodiment, the source SpCell is the PCell of the MCG when the first node receives the second signaling.

[0537] As a sub-embodiment of this embodiment, the first RRC information block is used to configure MCG.

[0538] As an embodiment, whether to send the second signaling and the RRC information block in the at least one RRC information block indicated by the second signaling is based on network implementation, for example, based on network load, based on channel conditions, based on measurement results of the first node, based on time, or randomly, or based on other internal algorithms.

[0539] As an embodiment, the source SpCell is the PSCell of the SCG of the first node when receiving the second signaling.

[0540] As a sub-embodiment of this embodiment, the first RRC information block is used to configure the SCG.

[0541] As an embodiment, the SpCell of the cell group configured by the first RRC information block is the target SpCell.

[0542] As an embodiment, after the LTM is successfully executed, the target SpCell becomes the SpCell of the first node, and the source SpCell is no longer the SpCell of the first node.

[0543] As an example, Figure 6 The source SpCell is the cell that sends the at least one RRC information block.

[0544] As an embodiment, the first node receives the at least one RRC information block from the source SpCell, sends the measurement result near the boundary between the source SpCell and the target SpCell, and then receives the second signaling from the source SpCell, the second signaling instructing the execution of the first RRC information block, and after the execution of the first RRC information block is completed, the first node switches to the target SpCell.

[0545] As an embodiment, when the first node fails to successfully execute the first RRC information block, the first node determines whether to perform RRC connection reconstruction based on configuration, internal algorithm, predefined method, etc.

[0546] As an embodiment, when the first node fails to successfully execute the first RRC information block, the first node initiates RRC connection reconstruction.

[0547] As an embodiment, when the first node fails to successfully execute the first RRC information block, the first node does not initiate RRC connection reconstruction.

[0548] As a sub-embodiment of this embodiment, the first node selects a cell from the SpCell of the cell group configured by the at least one RRC information block and applies the cell group RRC information block configured for this SpCell in the at least one RRC information block.

[0549] As a sub-embodiment of this embodiment, along with the reception of the second signaling, the first node starts a fourth timer.

[0550] As a sub-embodiment of this embodiment, before the fourth timer expires, the first node may select and apply one of the at least one RRC information blocks when failing to successfully apply the first RRC information block in the at least one RRC information block.

[0551] As a sub-embodiment of this embodiment, expiration of the fourth timer triggers RRC connection reestablishment.

[0552] As a sub-embodiment of this embodiment, the fourth timer is a timer of the MAC layer or a timer of the RRC layer.

[0553] As an embodiment, the identities of the cell groups to which the source SpCell and the target SpCell respectively belong are different.

[0554] As an embodiment, the identities of the cell groups to which the source SpCell and the target SpCell respectively belong are the same.

[0555] As an embodiment, during the process of switching from a source SpCell to a target SpCell, the first node does not need to initiate random access to the target SpCell.

[0556] As an embodiment, the phrase switch in the present application is or includes LTM.

[0557] As an embodiment, the phrase handover in the present application is or includes LTM cell switching.

[0558] As an embodiment, the phrase handover in the present application is or includes cell switching.

[0559] As an embodiment, the second node of the present application is the source SpCell.

[0560] Example 7

[0561] Embodiment 7 illustrates a schematic diagram of an RRC information block structure according to an embodiment of the present application, as shown in the attached Figure 7 shown.

[0562] Attached Figure 7 field1,field2,field11,field12,field21 are all fields.

[0563] The format of RRC messages is based on the relevant specifications of ISO ASN.1.

[0564] Attached Figure 7 InformationElement1, InformationElement2, InformationElement11, and InformationElement12 are all RRC IEs, and RRC IE is an RRC information block.

[0565] Attached Figure 7 The structure of an RRC information block included in an RRC message is shown.

[0566] As an embodiment, an RRC information block is an information block of an RRC message.

[0567] As an embodiment, an RRC message includes one or more RRC IE (Information Element, information block), such as Figure 7 RRCMessage-IEs in.

[0568] As an embodiment, a field of an RRC message must correspond to an RRC IE.

[0569] As an embodiment, an RRC message includes an RRC IE, which means that the RRC message includes a domain corresponding to the RRC IE.

[0570] As an example, Figure 7 The RRCMessage-IEs in is an RRC IE.

[0571] As an example, Figure 7 The RRCMessage-IEs in is any IE of an RRC message.

[0572] As an embodiment, an RRC IE is the content or value of a field in an RRC message.

[0573] As an embodiment, an RRC IE includes one or more fields, such as Figure 7 Field1 and field2 included in the RRCMessage-IEs, such as Information.

[0574] As an example, Figure 7 The RRC IE in is applicable to the at least one RRC information block of the present application.

[0575] As an example, Figure 7 The RRC IE in is applicable to the first RRC information block of the present application.

[0576] As an embodiment, the value of a field in the RRC message may be an RRC IE, such as Figure 7 In the example, the value of field1 is InformationElement1.

[0577] As an embodiment, a field in an RRC message carries or carries an RRC IE, such as an attached Figure 7 In the example, field1 hosts or carries InformationElement1.

[0578] As an embodiment, a field in an RRC message corresponds to an RRC IE, such as Figure 7In the example, field1 corresponds to InformationElement1.

[0579] As an embodiment, in an RRC message, different fields may correspond to or carry or take the value of the same RRC IE, for example, field11 and field21 are both set to InformationElement11.

[0580] As an embodiment, the RRC IE in the RRC message may include one or more layers.

[0581] As an embodiment, the RRC IE in the RRC message may include one or more sub-IEs.

[0582] As an embodiment, the RRC IE in the RRC message may include one or more sub-IEs, and / or deeper-level IEs.

[0583] As an embodiment, the RRC IE in the RRC message may include one or more subdomains and / or granddomains, for example, field1 is a first-level sub-item of RRCMessage-IEs, and field11 is a second-level sub-item of RRCMessage-IE; the subdomain of an IE in an RRC message may also include its own first-level subdomain or second-level subdomain, and so on.

[0584] As an example, Figure 7 The RRCMessage-IEs in the RRCMessage-IEs apply to the at least one RRC information block.

[0585] As an example, Figure 7 The RRCMessage-IEs in the RRCMessage-IEs apply to the first RRC information block.

[0586] As an embodiment, a sub-item of an RRC IE is a first-level sub-item included in the RRC IE.

[0587] As an embodiment, a grandchild of an RRC IE is a second-level sub-item included in the RRC IE.

[0588] As an embodiment, the sub-item of a grandchild of an RRC IE is a third-level sub-item included in the RRC IE.

[0589] As an example, Figure 7 The RRC signaling structure in is applicable to this application.

[0590] As an embodiment, an RRC message includes an attached Figure 7 The RRC IE of the example in, namely RRCMessage-IEs.

[0591] As an embodiment, each RRC information block of the at least one RRC information block includes an embedded RRCReconfiguration message.

[0592] As an embodiment, the first-level sub-item of the RRC message refers to the sub-item of the RRC message that does not belong to any of the RRC message sub-items.

[0593] As an embodiment, the first-level sub-item of any RRC message refers to a sub-item that does not belong to any sub-item of any RRC message.

[0594] As an embodiment, the first-level sub-item of any RRC message is a sub-item of any RRC message and the first-level sub-item does not belong to any sub-item of any RRC message.

[0595] As an embodiment, the message structure in Embodiment 7 is applicable to the first signaling of the present application.

[0596] As a sub-embodiment of this embodiment, the first signaling is an RRCReconfiguration message, each of the at least one RRC information block is an RRC IE in the first signaling, and each of the at least one RRC information block includes an embedded RRCReconfiguration message.

[0597] As a sub-embodiment of this embodiment, the embedded RRCReconfiguration message included in any RRC information block of the at least one RRC information block no longer further includes an RRCReconfiguration message.

[0598] As an embodiment, the message structure in Embodiment 7 is applicable to the reference RRC information block of the present application.

[0599] As an embodiment, the message structure in Embodiment 7 is applicable to the at least one RRC information block of the present application.

[0600] As an embodiment, the message structure in Embodiment 7 is applicable to the first report of the present application.

[0601] Example 8

[0602] Embodiment 8 illustrates a schematic diagram of a RRC information block in which a first report indication is discarded according to an embodiment of the present application, as shown in the attached figure. Figure 8 shown.

[0603] As an embodiment, the discarded RRC information block indicated by the first report includes an information block in the at least one RRC information block.

[0604] As an embodiment, the first report indicates the discarded RRC information block only in the at least one RRC information block.

[0605] As an embodiment, the discarded RRC information block indicated by the first report is only for the reference RRC information block.

[0606] As a sub-embodiment of this embodiment, the at least one RRC information block is not merged with the reference RRC information block when applied.

[0607] As a sub-embodiment of this embodiment, the at least one RRC information block is merged with an empty reference RRC information block when applied.

[0608] As an embodiment, the first report indicates the discarded RRC information block by indicating the index of the discarded RRC information block.

[0609] As an embodiment, the first report indicates the discarded RRC information block by indicating the identity of the cell group configured by the discarded RRC information block.

[0610] As an embodiment, the first report indicates the discarded RRC information block by indicating the identity of the SpCell of the cell group configured by the discarded RRC information block.

[0611] As an embodiment, the first report includes a bit map, and the K bits in the bit map respectively correspond to whether each RRC information block in the at least one RRC information block is discarded, and the at least one RRC information block includes K RRC information blocks, and K is a positive integer.

[0612] As an embodiment, the first node initiates RRC connection reconstruction only when the at least one RRC information block is discarded.

[0613] As an embodiment, when at least one of the at least one RRC information blocks is discarded, the first node initiates RRC connection reconstruction.

[0614] As an embodiment, when the second signaling indicates a non-existent RRC information block, for example, the index of the indicated RRC information block does not correspond to an RRC information block in the at least one RRC information block, or for example, the indicated SpCell does not belong to the SpCell of any cell group configured by the at least one RRC information block, the second signaling is triggered to be ignored.

[0615] As an embodiment, when the second signaling indicates a non-existent RRC information block, for example, the index of the indicated RRC information block does not correspond to an RRC information block in the at least one RRC information block, or for example, the indicated SpCell does not belong to the SpCell of any cell group configured by the at least one RRC information block, the first report is triggered.

[0616] As an embodiment, when the second signaling indicates a non-existent RRC information block, for example, the index of the indicated RRC information block does not correspond to an RRC information block in the at least one RRC information block, or for example, the indicated SpCell does not belong to the SpCell of any cell group configured by the at least one RRC information block, RRC connection reconstruction is triggered.

[0617] As an embodiment, when the second signaling indicates a non-existent RRC information block, for example, the index of the indicated RRC information block does not correspond to an RRC information block in the at least one RRC information block, or for example, the indicated SpCell does not belong to the SpCell of any cell group configured by the at least one RRC information block, the first signal is triggered.

[0618] As a sub-embodiment of this embodiment, the first signal is a physical layer signal.

[0619] As a sub-embodiment of this embodiment, the first signal is MAC CE.

[0620] As a sub-embodiment of this embodiment, the first signal is an RRC message.

[0621] As a sub-embodiment of this embodiment, the first signal indicates that the second signaling is unavailable.

[0622] As a sub-embodiment of this embodiment, the first signal is a layer 1 measurement result.

[0623] Example 9

[0624] Embodiment 9 illustrates a schematic diagram of a first signaling according to an embodiment of the present application carrying or used to generate a reference RRC information block, as shown in the attached Fig. 9 shown.

[0625] As an embodiment, the first signaling carries the at least one RRC information block via a container.

[0626] As an embodiment, the first signaling carries the reference RRC information block via a container.

[0627] As an embodiment, the reference RRC information block is an RRCReconfiguration message.

[0628] As an embodiment, the reference RRC information block is an RRCConnectionReconfiguration message.

[0629] As an embodiment, the reference RRC information block is an RRCReconfiguration template.

[0630] As an embodiment, the first signaling carries at least one field included in the RRCReconfiguration message, and the at least one field is used to determine the reference RRC information block.

[0631] As an embodiment, the first signaling carries at least one field included in the RRCReconfiguration message, and the at least one field is used to determine the value of the same-name field of the reference RRC information block.

[0632] As an embodiment, the first signaling carries at least one field included in the RRCReconfiguration message, and the reference RRC information block includes the at least one field.

[0633] As an embodiment, the first signaling carries at least one domain included in the RRCReconfiguration message, and the value domain of the domain with the same name as the at least one domain included in the reference RRC information block is the same as the at least one domain.

[0634] As an embodiment, the first node generates the reference RRC information block locally.

[0635] As a sub-embodiment of this embodiment, the first node generates the reference RRC information block according to at least one parameter included in the first signaling.

[0636] As an embodiment, generating the reference RRC information block includes determining the domains included in the reference RRC information block and the values ​​of the domains.

[0637] As an embodiment, the first signaling indicates the domains included in the reference RRC information block and the values ​​of the domains.

[0638] As an embodiment, the reference RRC information block includes a transaction identity (RRC-TransactionIdentifier).

[0639] As an embodiment, the reference RRC information block does not include otherConfig.

[0640] As an embodiment, the reference RRC information block includes a masterCellGroup, and the value of the masterCellGroup is the first RRC information block.

[0641] As an embodiment, the reference RRC information block includes secondaryCellGroup, and the value of the secondaryCellGroup is the first RRC information block.

[0642] As an embodiment, the reference RRC information block does not indicate fullConfig.

[0643] As an embodiment, the reference RRC information block does not include masterKeyUpdate.

[0644] As an embodiment, the reference RRC information block does not include t316 or indicates the release of t316.

[0645] As an embodiment, the reference RRC information block does not include appLayerMeasConfig.

[0646] As an embodiment, the first RRC information block is used to generate a reference RRC information block that is executed along with the application of the first RRC information block.

[0647] As an embodiment, the first signaling indicates a template for generating the reference RRC information block.

[0648] As a sub-embodiment of this embodiment, the first RRC information block includes a value of at least one field of a reference RRC information block executed along with the application of the first RRC information block.

[0649] As an embodiment, the execution of the reference RRC information block includes applying one of the at least one RRC information block.

[0650] As an embodiment, the execution of the reference RRC information block includes applying the first RRC information block.

[0651] As an embodiment, when any RRC information block in the at least one RRC information block is applied, it is first merged with the reference RRC information block and then the merged result is applied.

[0652] As a sub-embodiment of this embodiment, the first signaling indicates how the reference RRC information block is merged with the at least one RRC information block.

[0653] As a sub-embodiment of this embodiment, the merging result of the reference RRC information block and any RRC information block in the at least one RRC information block includes the configuration of the at least one RRC information block in the reference RRC information block other than the any RRC information block, and also includes the configuration of the at least one RRC information block in any RRC information block of the at least one RRC information block other than the reference RRC information block.

[0654] As a sub-embodiment of this embodiment, if the reference RRC information block and any RRC information block to be applied in the at least one RRC information block both have different configurations for a certain function, the combination of the reference RRC information block and any RRC information block to be applied in the at least one RRC information block only includes the configuration for the certain function included in any RRC information block to be applied in the at least one RRC information block.

[0655] As an embodiment, the behavior execution compatibility check is performed on the result after the reference RRC information block is merged with the RRC information block in the at least one RRC information block, rather than being performed solely on the reference RRC information block or the RRC information block in the at least one RRC information block.

[0656] Example 10

[0657] Embodiment 10 illustrates a structural block diagram of a processing device used in a first node according to an embodiment of the present application; Fig.10 As shown in the attached Fig.10 In the embodiment 10, the processing device 1000 in the first node includes a first receiver 1001, a first transmitter 1002 and a first processor 1003.

[0658] A first receiver 1001 receives a first signaling, where the first signaling includes at least one RRC (radioresource control) information block, where each RRC information block in the at least one RRC information block is used to configure a cell group;

[0659] The first processor 1003 performs compatibility detection, wherein the time for performing the compatibility detection depends on the at least one RRC information block;

[0660] Among them, the meaning of the sentence that the time for the behavior to perform compatibility check depends on the at least one RRC information block includes: when the application of any RRC information block in the at least one RRC information block depends on receiving the second signaling, the time for the behavior to perform compatibility check is predefined; when the application of any RRC information block in the at least one RRC information block does not depend on receiving the second signaling, the time for the behavior to perform compatibility check is not defined; the second signaling is the signaling of the protocol layer below the RRC layer, and the second signaling indicates any RRC information block in the at least one RRC information block.

[0661] As an embodiment, at least when the behavior performs compatibility detection, the first timer is not in a running state, and the start condition of the first timer includes initiating an RRC reconstruction process.

[0662] As an embodiment, the first processor 1003, in response to the at least one RRC information block failing the compatibility check, initiates RRC connection reestablishment;

[0663] The behavior of initiating RRC connection reconstruction includes starting a first timer.

[0664] As an embodiment, the first processor 1003, in response to the at least one RRC information block failing the compatibility test, abandons the first attempt and initiates RRC connection reconstruction; in the RRC connection reconstruction, whether to allow triggering the application of the RRC information block in the at least one RRC information block depends on whether the first attempt is configured;

[0665] Among them, when the first attempt is configured, in the RRC connection reconstruction, triggering the application of the RRC information block in the at least one RRC information block is allowed; when the first attempt is not configured or the first attempt is abandoned, triggering the application of the RRC information block in the at least one RRC information block is not allowed in the RRC connection reconstruction.

[0666] As an embodiment, the first processor 1003, in response to the at least one RRC information block failing the compatibility check, performs a first operation, and the first operation depends on the number of consecutive failures of the compatibility check; when the number of consecutive failures of the compatibility check is not less than a first threshold, the first operation is to enter the RRC idle state; when the number of consecutive failures of the compatibility check is less than the first threshold, the first operation is to initiate RRC connection reconstruction.

[0667] As an embodiment, the first processor 1003, in response to the at least one RRC information block failing the compatibility check, discards only the RRC information block that fails the compatibility check among the at least one RRC information block;

[0668] The first transmitter 1002 sends a first report, where the first report indicates a discarded RRC information block, or the first report indicates an RRC information block in the at least one RRC information block that fails compatibility detection.

[0669] As an embodiment, the first processor 1003, in response to the at least one RRC information block failing the compatibility check, discards all RRC information blocks in the at least one RRC information block.

[0670] As an embodiment, the first processor 1003 applies the first timing advance indicated by the second signaling; after the first timing advance indicated by the second signaling is applied, as a response to the at least one RRC information block failing the compatibility check, only the configuration before the compatibility check except the first timing advance is restored.

[0671] As an embodiment, the first receiver 1001 receives a reference RRC information block;

[0672] Among them, the behavior execution compatibility detection only includes any one of the at least one RRC information block and the former of the reference RRC information block; the phrase applying any one of the at least one RRC information block means that any one of the at least one RRC information block needs to be merged with the reference RRC information block and then applied.

[0673] As an embodiment, the first node is a user equipment (UE).

[0674] As an embodiment, the first node is a terminal supporting a large delay difference.

[0675] As an embodiment, the first node is a terminal supporting NTN.

[0676] As an embodiment, the first node is an aircraft or a ship.

[0677] As an embodiment, the first node is a mobile phone or a vehicle-mounted terminal.

[0678] As an embodiment, the first node is a relay UE and / or a U2N remote UE.

[0679] As an embodiment, the first node is an Internet of Things terminal or an industrial Internet of Things terminal.

[0680] As an embodiment, the first node is a device supporting low-latency and high-reliability transmission.

[0681] As an embodiment, the first node is a secondary link communication node.

[0682] As an embodiment, the first receiver 1001 includes at least one of the antenna 452, receiver 454, receiving processor 456, multi-antenna receiving processor 458, controller / processor 459, memory 460, or data source 467 in Example 4.

[0683] As an embodiment, the first transmitter 1002 includes at least one of the antenna 452, transmitter 454, transmit processor 468, multi-antenna transmit processor 457, controller / processor 459, memory 460, or data source 467 in Embodiment 4.

[0684] Embodiment 11

[0685] Embodiment 11 illustrates a structural block diagram of a processing device used in a first node according to an embodiment of the present application; Fig.11 As shown in the attached Fig.11 In the embodiment 11, the processing device 1100 in the first node includes a first receiver 1101, a first transmitter 1102 and a first processor 1103.

[0686] A first receiver 1101 receives a first signaling, where the first signaling includes a reference RRC information block and at least one RRC (radio resource control) information block, where each RRC information block in the at least one RRC information block is used to configure a cell group;

[0687] The first processor 1103 performs compatibility detection, and the time for performing the compatibility detection depends on the first signaling;

[0688] Among them, the sentence "the time for performing compatibility check of the behavior depends on the first signaling" means that: when the application of any RRC information block in the at least one RRC information block depends on the receipt of the second signaling, the time for performing compatibility check on at least the reference RRC information block is predefined; when the application of any RRC information block in the at least one RRC information block does not depend on the receipt of the second signaling, the time for performing compatibility check of the behavior is not defined; the second signaling is the signaling of the protocol layer below the RRC layer, and the second signaling indicates any RRC information block in the at least one RRC information block; the phrase "application of any RRC information block in the at least one RRC information block" means that any RRC information block in the at least one RRC information block needs to be merged with the reference RRC information block first, and then the merger of any RRC information block in the at least one RRC information block and the reference RRC information block is applied; the first signaling is RRCReconfiguration.

[0689] As an embodiment, the benefits of the above method include: compatibility issues in the reference RRC information block can be discovered as early as possible.

[0690] As an embodiment, at least when the behavior performs compatibility detection, the first timer is not in a running state, and the start condition of the first timer includes initiating an RRC reconstruction process.

[0691] As an embodiment, the meaning of the sentence that the time for performing compatibility check depends on the first signaling includes: when the application of any RRC information block in the at least one RRC information block depends on receiving the second signaling, the time for performing compatibility check on the at least one RRC information block is predefined.

[0692] As an embodiment, an advantage of the above method is that it can better ensure that at least one RRC information block does not have compatibility issues.

[0693] As an embodiment, the meaning of the sentence that the time for performing compatibility check depends on the first signaling includes: when the application of any RRC information block in the at least one RRC information block depends on receiving the second signaling, the time for the compatibility check performed on only the former of the reference RRC information block and the at least one RRC information block is predefined, that is, the compatibility check for the at least one RRC information block is not defined.

[0694] As an embodiment, the advantage of the above method is that it increases the scope of implementation and improves flexibility while ensuring minimal compatibility testing.

[0695] As an embodiment, the first processor 1103, in response to the reference RRC information block failing the compatibility check, initiates RRC connection reestablishment;

[0696] The behavior of initiating RRC connection reconstruction includes starting a first timer.

[0697] As an embodiment, the first processor 1103, in response to the at least one RRC information block failing the compatibility test, abandons the first attempt and initiates RRC connection reconstruction; in the RRC connection reconstruction, whether to allow triggering the application of the RRC information block in the at least one RRC information block depends on whether the first attempt is configured;

[0698] Among them, when the first attempt is configured, in the RRC connection reconstruction, triggering the application of the RRC information block in the at least one RRC information block is allowed; when the first attempt is not configured or the first attempt is abandoned, triggering the application of the RRC information block in the at least one RRC information block is not allowed in the RRC connection reconstruction.

[0699] As an embodiment, the first processor 1103, in response to the at least one RRC information block failing the compatibility check, performs a first operation, and the first operation depends on the number of consecutive failures of the compatibility check; when the number of consecutive failures of the compatibility check is not less than a first threshold, the first operation is to enter the RRC idle state; when the number of consecutive failures of the compatibility check is less than the first threshold, the first operation is to initiate RRC connection reconstruction.

[0700] As an embodiment, the first processor 1103, as a response to the at least one RRC information block failing the compatibility check, discards only the RRC information block that fails the compatibility check in the at least one RRC information block;

[0701] The first transmitter 1102 sends a first report, where the first report indicates a discarded RRC information block, or the first report indicates an RRC information block in the at least one RRC information block that fails compatibility detection.

[0702] As an embodiment, the first processor 1103, in response to the at least one RRC information block failing the compatibility check, discards all RRC information blocks in the at least one RRC information block.

[0703] As an embodiment, the first processor 1103 applies the first timing advance indicated by the second signaling; after the first timing advance indicated by the second signaling is applied, as a response to the at least one RRC information block failing the compatibility check, only the configuration before the compatibility check except the first timing advance is restored.

[0704] As an embodiment, the first node is a user equipment (UE).

[0705] As an embodiment, the first node is a terminal supporting a large delay difference.

[0706] As an embodiment, the first node is a terminal supporting NTN.

[0707] As an embodiment, the first node is an aircraft or a ship.

[0708] As an embodiment, the first node is a mobile phone or a vehicle-mounted terminal.

[0709] As an embodiment, the first node is a relay UE and / or a U2N remote UE.

[0710] As an embodiment, the first node is an Internet of Things terminal or an industrial Internet of Things terminal.

[0711] As an embodiment, the first node is a device supporting low-latency and high-reliability transmission.

[0712] As an embodiment, the first node is a secondary link communication node.

[0713] As an embodiment, the first receiver 1101 includes at least one of the antenna 452, receiver 454, receiving processor 456, multi-antenna receiving processor 458, controller / processor 459, memory 460, or data source 467 in Example 4.

[0714] As an embodiment, the first transmitter 1102 includes at least one of the antenna 452, transmitter 454, transmit processor 468, multi-antenna transmit processor 457, controller / processor 459, memory 460, or data source 467 in Embodiment 4.

[0715] A person of ordinary skill in the art can understand that all or part of the steps in the above method can be completed by instructing the relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk or an optical disk. Optionally, all or part of the steps in the above embodiment can also be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiment can be implemented in the form of hardware or in the form of a software function module, and the present application is not limited to any specific form of software and hardware combination. The user equipment, terminal and UE in the present application include but are not limited to drones, communication modules on drones, remote-controlled aircraft, aircraft, small aircraft, mobile phones, tablet computers, notebooks, vehicle-mounted communication equipment, wireless sensors, Internet cards, Internet of Things terminals, RFID terminals, NB-IoT terminals, MTC (Machine Type Communication, machine type communication) terminals, eMTC (enhancedMTC, enhanced MTC) terminals, data cards, Internet cards, vehicle-mounted communication equipment, low-cost mobile phones, low-cost tablet computers, satellite communication equipment, ship communication equipment, NTN user equipment and other wireless communication equipment. The base stations or system equipment in this application include but are not limited to macrocell base stations, microcell base stations, home base stations, relay base stations, gNB (NR Node B) NR Node B, TRP (Transmitter Receiver Point, sending and receiving node), NTN base stations, satellite equipment, flight platform equipment and other wireless communication equipment.

[0716] The present invention may be implemented in other specified forms without departing from its core or essential features. Therefore, the embodiments disclosed herein should be considered as illustrative rather than restrictive in any way. The scope of the invention is determined by the appended claims rather than the preceding description, and all modifications within their equivalent meanings and regions are considered to be included therein.

Claims

1. A first node for wireless communication, wherein: include: A first receiver receives a first signaling, wherein the first signaling includes at least one RRC (radioresourcecontrol) information block, each of the at least one RRC information block is used to configure a cell group; A first processor performs compatibility detection, wherein the time for performing the compatibility detection depends on the at least one RRC information block; Among them, the meaning of the sentence that the time for the behavior to perform compatibility check depends on the at least one RRC information block includes: when the application of any RRC information block in the at least one RRC information block depends on receiving the second signaling, the time for the behavior to perform compatibility check is predefined; when the application of any RRC information block in the at least one RRC information block does not depend on receiving the second signaling, the time for the behavior to perform compatibility check is not defined; the second signaling is the signaling of the protocol layer below the RRC layer, and the second signaling indicates any RRC information block in the at least one RRC information block.

2. The first node according to claim 1, characterized in that: At least when the behavior performs compatibility detection, the first timer is not in a running state, and the start condition of the first timer includes initiating an RRC reconstruction process.

3. The first node according to claim 1 or 2, characterized in that: include: The first processor, in response to the at least one RRC information block failing the compatibility check, initiates RRC connection reestablishment; The behavior of initiating RRC connection reconstruction includes starting a first timer.

4. The first node according to claim 1 or 2, characterized in that: include: The first processor abandons the first attempt and initiates RRC connection reestablishment as a response to the at least one RRC information block failing the compatibility check; in the RRC connection reestablishment, whether to allow triggering application of the RRC information block in the at least one RRC information block depends on whether the first attempt is configured; Among them, when the first attempt is configured, in the RRC connection reconstruction, triggering the application of the RRC information block in the at least one RRC information block is allowed; when the first attempt is not configured or the first attempt is abandoned, triggering the application of the RRC information block in the at least one RRC information block is not allowed in the RRC connection reconstruction.

5. The first node according to any one of claims 1 to 4, characterized in that: include: the first processor, in response to the at least one RRC information block failing the compatibility check, performing a first operation, the first operation being dependent on a number of consecutive failures to pass the compatibility check; When the number of consecutive failures to pass the compatibility check is not less than a first threshold, the first operation is to enter the RRC idle state; When the number of consecutive failures to pass the compatibility check is less than a first threshold, the first operation is to initiate RRC connection reconstruction.

6. The first node according to claim 1 or 2, characterized in that: include: The first processor, in response to the at least one RRC information block failing the compatibility check, discards only the RRC information block that fails the compatibility check among the at least one RRC information block; The first transmitter sends a first report, where the first report indicates a discarded RRC information block, or the first report indicates an RRC information block among the at least one RRC information block that fails compatibility detection.

7. The first node according to claim 1 or 2, characterized in that: include: The first processor, in response to the at least one RRC information block failing the compatibility check, discards all RRC information blocks in the at least one RRC information block.

8. The first node according to any one of claims 1 to 7, characterized in that: The first processor applies the first timing advance indicated by the second signaling; after the first timing advance indicated by the second signaling is applied, as a response to the at least one RRC information block failing the compatibility check, only restores the configuration before the compatibility check except the first timing advance.

9. The first node according to any one of claims 1 to 8, characterized in that: include: The first receiver receives a reference RRC information block; Among them, the behavior execution compatibility detection only includes any one of the at least one RRC information block and the former of the reference RRC information block; the phrase applying any one of the at least one RRC information block means that any one of the at least one RRC information block needs to be merged with the reference RRC information block and then applied.

10. A method in a first node for wireless communication, wherein: include: receiving first signaling, where the first signaling includes at least one RRC information block, where each RRC information block in the at least one RRC information block is used to configure a cell group; Performing compatibility detection, wherein the time for performing the compatibility detection depends on the at least one RRC information block; Among them, the meaning of the sentence that the time for the behavior to perform compatibility check depends on the at least one RRC information block includes: when the application of any RRC information block in the at least one RRC information block depends on receiving the second signaling, the time for the behavior to perform compatibility check is predefined; when the application of any RRC information block in the at least one RRC information block does not depend on receiving the second signaling, the time for the behavior to perform compatibility check is not defined; the second signaling is the signaling of the protocol layer below the RRC layer, and the second signaling indicates any RRC information block in the at least one RRC information block.

Images