Method and apparatus used for wireless communication

Abstract

Disclosed in the present application are a method and apparatus for wireless communication. The method comprises: a communication node receiving a first message in a first cell, wherein the first message comprises a WUS configuration of a second cell; in response to a radio link failure that has occurred at a first node, starting a first timer; and when the first timer is running, executing cell selection and initiating a random access process on the second cell, wherein the random access process is used for requesting SIB1 from the second cell, and the random access process comprises: sending a first RA sequence, and configuring a first information block in VarRLF-Report along with the sending of the first RA sequence. The WUS configuration of the second cell includes a time-frequency resource for the first RA sequence, and the first information block includes a first domain, which at least indicates the identity of the second cell. The method provided in the present application facilitates the storage of a larger quantity of information related to useful OD-SIB1, and optimizes the network performance.

Description

Methods and apparatus used for wireless communication Technical Field

[0001] This application relates to transmission methods and apparatus in wireless communication systems, and more particularly to methods and apparatus for maintaining wireless connection failure information. Background Technology

[0002] The 3GPP (3rd Generation Partnership Project) protocol supports SON (Self-Organizing Networks) / MDT (Minimization of Drive Test), including immediate MDT and logged MDT. This includes the storage and reporting of relevant information when a UE experiences a radio connection failure. TS38.331 explicitly stipulates that when a UE performs an RRC connection re-establishment procedure after a radio connection failure, relevant re-establishment information should be recorded in the VarRLF-Report.

[0003] Network energy saving (NES) is crucial for environmental sustainability, reducing environmental impact (greenhouse gas emissions), and saving operating costs. With the increasing prevalence of 5G across various industries and geographic regions, more advanced services and applications requiring very high data rates (such as XR) are being developed, leading to denser networks using more antennas, larger bandwidths, and more frequency bands. The environmental impact of 5G needs to be controlled, necessitating the development of new solutions to improve network energy efficiency. At its RAN#94 meeting, 3GPP (the 3rd Generation Partnership Project) approved the "Network Energy Saving Study" (SI) project. Considering the energy consumption caused by the periodic transmission of SIB1 messages to the network, Release 19 designated "on-demand SIB1 (System Information Block 1)" as an important research direction for NES. The UE receives the WUS (Wake Up Signal) configuration from cell A and sends a UL WU message to the NES cell to request the required SIB1 message. The UL WUS uses PRACH. At the RAN2#129 meeting, the following consensus was reached: UEs in connected state are allowed to obtain on-demand SIB1 (OD-SIB1) while T311 is running. Summary of the Invention

[0004] The inventors discovered through research that existing protocols do not consider the scenario where the UE acquires OD-SIB1 while T311 is running when recording relevant re-establishment information in VarRLF-Report, and therefore cannot store relevant information during the execution of the OD-SIB1 procedure. The execution of the OD-SIB1 procedure will cause a certain degree of delay in acquiring SIB1, thus affecting the completion of the RRC connection re-establishment procedure. Therefore, how to optimize the existing data collection mechanism and record information during the execution of the OD-SIB1 procedure is a problem that needs to be considered.

[0005] To address the aforementioned issues, this application provides a solution. While VarRLF-Report was used as an example in the problem description, this application is also applicable to other UE variables, such as UL WUS-specific UE variables, achieving similar technical effects to VarRLF-Report. Furthermore, using a unified solution across different scenarios helps reduce hardware complexity and cost.

[0006] As an example, the interpretation of terms in this application is based on the definitions in the 3GPP specification protocol TS38 series.

[0007] As an example, the interpretation of terms in this application is based on the definitions in the 3GPP specification protocol TS37 series.

[0008] As an example, the interpretation of terms in this application is based on the definitions in the 3GPP specification protocol TS36 series.

[0009] It should be noted that, unless otherwise specified, the embodiments and features in any node of this application can be applied to any other node. Furthermore, unless otherwise specified, the embodiments and features in any embodiment of this application can be arbitrarily combined with each other.

[0010] This application discloses a method used in a first node for wireless communication, characterized by comprising:

[0011] Receive a first message in the first cell; the first message includes the WUS configuration of the second cell;

[0012] In response to the wireless connection failure of the first node, a first timer is started; when the first timer is running, cell selection is performed and a random access procedure is initiated on the second cell, wherein the random access procedure is to request SIB1 of the second cell, and the random access procedure includes: sending a first RA sequence; accompanied by sending the first RA sequence, setting a first information block in the VarRLF-Report;

[0013] The WUS configuration of the second cell includes the time-frequency resources of the first RA sequence; the first information block includes a first field, which indicates at least the identity of the second cell.

[0014] This application addresses the issue that when the first timer runs and triggers the SIB1 procedure requesting the second cell, the VarRLF-Report does not collect information about this procedure, making it difficult for the network to optimize WUS configuration based on the information in the VarRLF-Report. Furthermore, adding new UE variables specifically for WUS configuration would increase protocol complexity and signaling overhead. To address this problem, this application proposes "setting a first information block in the VarRLF-Report" and "the first information block includes a first field, which indicates at least the identity of the second cell." By reusing existing VarRLF-Report variables and adding a first information block to collect information about the SIB1 procedure requesting the second cell, this approach effectively reduces modifications to existing protocols while improving data collection efficiency, thus contributing to better network performance optimization.

[0015] When to record the first information block in VarRLF-Report is a question that needs to be considered. This application proposes to "set the first information block in VarRLF-Report along with the transmission of the first RA sequence".

[0016] As an example, setting the first information block in VarRLF-Report along with sending the first RA sequence means setting the first information block in VarRLF-Report once the first RA sequence is sent; this method is beneficial for timely recording and collection of relevant information.

[0017] As an example, setting the first information block in VarRLF-Report along with sending the first RA sequence means: when a MAC RAR message is received after sending the first RA sequence, the first information block is set in VarRLF-Report; this method takes into account the balance between frequent recording and information validity, which is beneficial to saving UE energy consumption and resource occupation.

[0018] As an example, setting the first information block in VarRLF-Report along with sending the first RA sequence means setting the first information block in VarRLF-Report only after receiving the requested SIB1 message; this method helps to save storage resources and improve the effectiveness of stored information.

[0019] As an example, setting the first information block in the VarRLF-Report along with sending the first RA sequence means setting the first information block in the VarRLF-Report when the random access procedure fails; this method is beneficial for optimizing the random access configuration and reducing the possibility of random access failure.

[0020] As an example, setting the first information block in VarRLF-Report along with sending the first RA sequence means setting the first information block in VarRLF-Report when the request for SIB1 of the second cell fails; this method is beneficial for optimizing WUS configuration and reducing the possibility of OD-SIB1 failure.

[0021] According to one aspect of this application, the random access procedure initiated on the second cell includes a second field in the first information block, the second field indicating random access information of the second cell; wherein the random access information of the second cell depends on the WUS configuration of the second cell included in the first message.

[0022] In the above method, at least a portion of the random access information of the second cell comes from the first message, including the WUS configuration of the second cell.

[0023] In the existing VarRLF-Report, random access information is only recorded when the connection failure type is hof. The random access procedure plays an important role in the process of requesting the SIB1 procedure of the second cell. Recording the random access information during the process of requesting the SIB1 procedure of the second cell is beneficial to the optimization of WUS configuration. The above method records the random access information when the SIB1 procedure of requesting the second cell is triggered by "accompanying the initiation of the random access procedure, including a second field in the first information block, the second field indicating the random access information of the second cell".

[0024] This method provides more information for network optimization compared to "the first information block includes a first field, the first field indicating the identity of at least the second cell".

[0025] According to one aspect of this application, the first information block includes a first time interval as the random access procedure initiated on the second cell is completed; wherein the start time of the first time interval depends on the time when the first node experiences a wireless connection failure.

[0026] As one embodiment, the first time interval is from the time when the first node experiences a wireless connection failure to the time when the random access procedure is completed.

[0027] This application takes into account the time delay caused by WUS configuration triggering the random access process. In order to minimize the impact of the delay caused by WUS configuration, it is necessary to make the network aware of the time interval for the WUS configuration application to complete. This is beneficial to assist network optimization and reduce the impact of WUS configuration triggering the random access process on the RRC connection re-establishment process.

[0028] According to one aspect of this application, a third field is set in the first information block in response to the failure of the request for SIB1 of the second cell. The third field indicates that the request for SIB1 of the second cell has failed.

[0029] This application takes into account network optimization in the case of failure to request SIB1 for the second cell. The above method enables the network to know that the WUS configuration application has failed by "setting a third field in the first information block, the third field indicating that the request for SIB1 for the second cell has failed".

[0030] According to one aspect of this application, in response to the failure of the SIB1 request of the second cell, a fourth field is set in the first information block, the fourth field indicating the triggering condition of the second cell.

[0031] Based on the method of "setting a third field in the first information block, wherein the third field indicates that the request for SIB1 of the second cell has failed", the above method further adds trigger condition information by "setting a fourth field in the first information block, wherein the fourth field indicates the trigger condition of the second cell", which helps the auxiliary network reduce the probability of WUS configuration application failure.

[0032] According to one aspect of this application, it is characterized by comprising:

[0033] Along with sending the first RA sequence, the recipient of the first message sets a second information block in the VarRA-Report;

[0034] The second information block indicates that the WUS configuration of the second cell is applied; the second information block includes at least a first field, which indicates the identity information of the second cell.

[0035] This method takes into account that under the existing protocol, when a random access procedure is initiated, relevant random access information needs to be stored in VarRA-Report. By setting a second information block in VarRA-Report, the method reduces the modification to the existing protocol compared to setting a first information block in VarRLF-Report.

[0036] According to one aspect of this application, it is characterized by comprising:

[0037] Receive a second message; wherein the second message includes a first request instruction;

[0038] Send a third message;

[0039] The action of sending the third message depends on the second message including the first request indication.

[0040] As an example, the records described in this application include storage.

[0041] As an example, the record described in this application includes appending.

[0042] As an example, the record described in this application includes settings.

[0043] This application discloses a method used in a second node for wireless communication, characterized by comprising:

[0044] Send the first message; the first message includes the WUS configuration of the second cell;

[0045] Receive the first RA sequence;

[0046] In response to a wireless connection failure, the receiver of the first message starts a first timer. While the first timer is running, the receiver of the first message performs cell selection and initiates a random access procedure on the second cell. This random access procedure, in order to request SIB1 of the second cell, includes: sending a first RA sequence; accompanying the sending of the first RA sequence, the receiver of the first message sets a first information block in a VarRLF-Report; the WUS configuration of the second cell includes the time-frequency resources of the first RA sequence; the first information block includes a first field indicating at least the identity of the second cell.

[0047] According to one aspect of this application, the random access procedure initiated on the second cell is characterized in that the recipient of the first message includes a second field in the first information block, the second field indicating random access information of the second cell; wherein the random access information of the second cell depends on the WUS configuration of the second cell included in the first message.

[0048] According to one aspect of this application, the recipient of the first message includes a first time interval in the first information block as the random access procedure initiated on the second cell is completed; wherein the start time of the first time interval depends on the time when the first node experiences a wireless connection failure.

[0049] According to one aspect of this application, in response to the failure of the request for SIB1 of the second cell, the recipient of the first message sets a third field in the first information block, the third field indicating that the request for SIB1 of the second cell has failed.

[0050] According to one aspect of this application, in response to the request for the second cell's SIB1 failure, the recipient of the first message sets a fourth field in the first information block, the fourth field indicating the triggering condition of the second cell.

[0051] According to one aspect of this application, the recipient of the first message sets a second information block in the VarRA-Report along with the transmission of the first RA sequence; wherein the second information block includes at least a first field indicating the identity information of the second cell.

[0052] According to one aspect of this application, it is characterized by comprising:

[0053] Send a second message; wherein the second message includes a first request instruction;

[0054] Receive third message;

[0055] The action of the recipient of the first message sending the third message depends on the second message including the first request indication.

[0056] This application discloses a first node used for wireless communication, characterized in that it includes:

[0057] A first receiver receives a first message in a first cell; the first message includes the WUS configuration of a second cell.

[0058] A first processor, in response to a wireless connection failure at the first node, starts a first timer; while the first timer is running, it performs cell selection and initiates a random access procedure on the second cell, wherein the random access procedure is to request SIB1 of the second cell, and the random access procedure includes: sending a first RA sequence; accompanied by sending the first RA sequence, setting a first information block in the VarRLF-Report;

[0059] The WUS configuration of the second cell includes the time-frequency resources of the first RA sequence; the first information block includes a first field, which indicates at least the identity of the second cell.

[0060] This application discloses a second node used for wireless communication, characterized by comprising:

[0061] The second transmitter sends the first message; the first message includes the WUS configuration of the second cell;

[0062] The second receiver receives the first RA sequence;

[0063] In response to a wireless connection failure, the receiver of the first message starts a first timer. While the first timer is running, the receiver of the first message performs cell selection and initiates a random access procedure on the second cell. This random access procedure, in order to request SIB1 of the second cell, includes: sending a first RA sequence; accompanying the sending of the first RA sequence, the receiver of the first message sets a first information block in a VarRLF-Report; the WUS configuration of the second cell includes the time-frequency resources of the first RA sequence; the first information block includes a first field indicating at least the identity of the second cell.

[0064] This application discloses a method used in a first node of wireless communication, characterized by comprising:

[0065] Receive a first RRC message, the first RRC message being configured with a first time length;

[0066] The first timer begins as the RRC connection re-establishment process is initiated;

[0067] Whether actions upon going to RRC_IDLE are executed depends on whether at least the first node has a WUS configuration; the time length between the start time of the first timer and the first time is the first time length;

[0068] The decision on whether to execute the action when switching to RRC_IDLE at the first moment depends on at least whether the first node has a WUS configuration, including:

[0069] If the first node does not have a WUS configuration, perform the action when switching to RRC_IDLE at the first time.

[0070] If at least the first node has a WUS configuration, the action of transitioning to RRC_IDLE is not performed at the first time.

[0071] This application considers that if the first node has a WUS configuration, and the WUS configuration is applied during the RRC connection re-establishment process, it will lead to a longer time to obtain SIB1, making it more difficult for the first node to select a cell for re-establishment before the first time. If a cell for re-establishment is not selected in the first time, according to the existing protocol, the first node will enter the RRC_IDLE state, thereby increasing the possibility of communication interruption. The subsequent re-access to the network will also further increase signaling overhead, which is not conducive to energy saving for the base station and the first node. This application takes into account the delay caused by the application of WUS configuration by "whether the actions upon going to RRC_IDLE are executed in the first time depends on whether the first node has a WUS configuration". This makes it easier for the first node to select a cell for re-establishment before the first time, thereby reducing the possibility of communication interruption and avoiding the process of frequent re-access to the network to a certain extent.

[0072] According to one aspect of this application, if the first node does not have a WUS configuration, the action of performing the transition to RRC_IDLE at the first time depends on the first timer using the first time length; if at least the first node has a WUS configuration, the action of not performing the transition to RRC_IDLE at the first time depends on the first timer using a second time length; wherein the first RRC message configures the second time length; both the first time length and the second time length are configured for the first timer.

[0073] How to achieve "if at least the first node has WUS configuration, the action of switching to RRC_IDLE is not executed in the first time" is a problem that needs to be considered. The current RRC connection re-establishment process does not take into account the time delay caused by WUS configuration. The above method extends the time of the existing timer by configuring a second time length for the first timer, so that the action of switching to RRC_IDLE is not executed in the first time. The above method improves the flexibility of the existing first timer configuration.

[0074] According to one aspect of this application, if the first node does not have a WUS configuration, the action of executing the transition to RRC_IDLE at the first time depends on the first timer; the action of not executing the transition to RRC_IDLE at the first time depends on the second timer; wherein the first RRC message configures the first time length to the first timer; and the first RRC message configures the second time length to the second timer.

[0075] In the above method, if the first node does not have a WUS configuration, the action of switching to RRC_IDLE at the first time depends on the first timer.

[0076] In the above method, the action of not executing the transition to RRC_IDLE at the first time depends on the use of a second timer.

[0077] Considering that the current protocol only configures a first timer for the RRC connection re-establishment process, and the action of switching to RRC_IDLE is executed when the first timer expires; the above method configures a second timer for the scenario where the first node has WUS configuration, and starts different timers according to different scenarios, so as to prevent the action of switching to RRC_IDLE from being executed in the first time; the above method reduces the modification of the existing protocol.

[0078] According to one aspect of this application, if at least the first node has a WUS configuration, the action of not performing the transition to RRC_IDLE at the first time depends on the first timer being paused.

[0079] In the above method, by pausing the first timer, the first node is prevented from performing the action of switching to RRC_IDLE at the first time; the network does not need to configure timer information, saving configuration resources and making the implementation simpler.

[0080] According to one aspect of this application, if at least the first node has a WUS configuration, the action of not performing the transition to RRC_IDLE at the first time depends on the WUS configuration being applied at the first time.

[0081] The above method defines the conditions under which the action of switching to RRC_IDLE is not performed at the first time.

[0082] This application takes into account that if only the condition "the first node has WUS configuration" is considered, when the first node does not use the WUS configuration during RRC connection re-establishment, the configuration according to the existing protocol will not increase the risk of communication interruption; the above method adds the condition "the WUS configuration is being applied at the first time", which clarifies the use case.

[0083] According to one aspect of this application, it is characterized by comprising:

[0084] Send the first RA sequence;

[0085] In response to the sending of the first RA sequence, a first time window is opened; wherein, the first time window is for receiving RAR messages;

[0086] In response to the receipt of the RAR message, a second time window is opened; wherein, SIB1 is monitored within the second time window;

[0087] The application of the WUS configuration at the first time includes: either the first time window or the second time window is running at the first time.

[0088] This application discloses a method used in a second node for wireless communication, characterized by comprising:

[0089] Transmit a first RRC message, the first RRC message being configured with a first time length;

[0090] During the RRC connection re-establishment process, the receiver of the first RRC message starts a first timer; whether actions upon going to RRC_IDLE are executed at the first time depends on whether the receiver of the first RRC message has WUS configuration; the time length between the start time of the first timer and the first time is the first time length.

[0091] The decision on whether to execute the action upon transitioning to RRC_IDLE at the first moment depends on whether at least the recipient of the first RRC message has a WUS configuration, including:

[0092] If the recipient of the first RRC message does not have a WUS configuration, the action of switching to RRC_IDLE is performed at the first time.

[0093] If at least the recipient of the first RRC message has a WUS configuration, the action of switching to RRC_IDLE is not performed at the first time.

[0094] According to one aspect of this application, if the recipient of the first RRC message does not have a WUS configuration, the action of performing the transition to RRC_IDLE at the first time depends on the first timer using the first time length; if at least the recipient of the first RRC message has a WUS configuration, the action of not performing the transition to RRC_IDLE at the first time depends on the first timer using a second time length; wherein the first RRC message configures the second time length; both the first time length and the second time length are configured for the first timer.

[0095] According to one aspect of this application, if the recipient of the first RRC message does not have a WUS configuration, the action of performing the transition to RRC_IDLE at the first time depends on the first timer; the action of not performing the transition to RRC_IDLE at the first time depends on the second timer; wherein the first RRC message configures the first time length to the first timer; the first RRC message configures the second time length to the second timer.

[0096] According to one aspect of this application, if at least the recipient of the first RRC message has a WUS configuration, the action of not performing the transition to RRC_IDLE at the first time depends on the first timer being paused.

[0097] According to one aspect of this application, the action of not performing the transition to RRC_IDLE at the first time depends on the WUS configuration being applied at the first time, provided that at least the recipient of the first RRC message has a WUS configuration.

[0098] According to one aspect of this application, it is characterized by comprising:

[0099] Receive the first RA sequence;

[0100] In response to the receipt of the first RA sequence, a RAR message is sent;

[0101] Wherein, the sender of the first RA sequence opens a first time window; wherein, the first time window is for receiving RAR messages; in response to the RAR message being received, a second time window is opened; wherein, SIB1 is monitored within the second time window; wherein, the WUS configuration being applied at the first time includes: either the first time window or the second time window being running at the first time.

[0102] This application discloses a first node used for wireless communication, characterized in that it includes:

[0103] A first receiver receives a first RRC message, wherein the first RRC message is configured with a first time length.

[0104] The first processor, along with the initiation of the RRC connection re-establishment process, starts the first timer;

[0105] Whether actions upon going to RRC_IDLE are executed depends on whether at least the first node has a WUS configuration; the time length between the start time of the first timer and the first time is the first time length;

[0106] The decision on whether to execute the action when switching to RRC_IDLE at the first moment depends on at least whether the first node has a WUS configuration, including:

[0107] If the first node does not have a WUS configuration, perform the action when switching to RRC_IDLE at the first time.

[0108] If at least the first node has a WUS configuration, the action of transitioning to RRC_IDLE is not performed at the first time.

[0109] This application discloses a second node used for wireless communication, characterized by comprising:

[0110] The second transmitter transmits a first RRC message, which is configured with a first time length.

[0111] During the RRC connection re-establishment process, the receiver of the first RRC message starts a first timer; whether actions upon going to RRC_IDLE are executed at the first time depends on whether the receiver of the first RRC message has WUS configuration; the time length between the start time of the first timer and the first time is the first time length.

[0112] The decision on whether to execute the action upon transitioning to RRC_IDLE at the first moment depends on whether at least the recipient of the first RRC message has a WUS configuration, including:

[0113] If the recipient of the first RRC message does not have a WUS configuration, the action of switching to RRC_IDLE is performed at the first time.

[0114] If at least the recipient of the first RRC message has a WUS configuration, the action of switching to RRC_IDLE is not performed at the first time. Attached Figure Description

[0115] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:

[0116] Figure 1A shows a flowchart of the transmission of the first node according to an embodiment of this application;

[0117] Figure 1B shows a flowchart of the transmission of the first node according to an embodiment of this application;

[0118] Figure 2 shows a schematic diagram of a network architecture according to an embodiment of this application;

[0119] Figure 3 illustrates a schematic diagram of an embodiment of a wireless protocol architecture for the user plane and control plane according to an embodiment of this application;

[0120] Figure 4 shows a schematic diagram of a first communication device and a second communication device according to an embodiment of this application;

[0121] Figure 5A shows a flowchart of wireless signal transmission according to an embodiment of this application;

[0122] Figure 5B shows a flowchart of wireless signal transmission according to an embodiment of this application;

[0123] Figure 6A shows a schematic diagram of the first information block including a second field according to an embodiment of this application;

[0124] Figure 6B shows a schematic diagram of a first time length and a second time length being configured to the first timer according to an embodiment of the present application;

[0125] Figure 7A shows a schematic diagram of the first time interval according to an embodiment of this application;

[0126] Figure 7B shows a schematic diagram of configuring the first timer and the second timer in the first RRC message according to an embodiment of this application;

[0127] Figure 8A shows a schematic diagram of a third field included in the first information block according to an embodiment of this application;

[0128] Figure 8B shows a schematic diagram of the first timer being paused according to an embodiment of this application;

[0129] Figure 9A shows a schematic diagram of the fourth field indicating the triggering conditions of the second cell according to an embodiment of this application;

[0130] Figure 9B shows a schematic diagram of the WUS configuration being applied at the first moment according to an embodiment of this application;

[0131] Figure 10A shows a schematic diagram of setting up a second information block in VarRA-Report according to an embodiment of this application;

[0132] Figure 10B shows another wireless signal transmission flowchart according to an embodiment of this application;

[0133] Figure 11 shows another wireless transmission flowchart according to an embodiment of this application;

[0134] Figure 12A shows a structural block diagram of a processing apparatus for a first node according to an embodiment of the present application;

[0135] Figure 12B shows a structural block diagram of a processing apparatus for a first node according to an embodiment of the present application;

[0136] Figure 13A shows a structural block diagram of a processing apparatus for a second node according to an embodiment of this application;

[0137] Figure 13B shows a structural block diagram of a processing apparatus for a second node according to an embodiment of this application; Detailed Implementation

[0138] The technical solution of this application will be further described in detail below with reference to the accompanying drawings. It should be noted that, unless otherwise specified, the embodiments and features in the embodiments of this application can be arbitrarily combined with each other.

[0139] Example 1A

[0140] Example 1A illustrates a flowchart of the transmission of a first node according to an embodiment of this application, as shown in Figure 1A.

[0141] In Embodiment 1A, the first node in this application receives a first message in a first cell in step 101A; in step 102A, in response to a radio connection failure of the first node, a first timer is started, and when the first timer runs, cell selection is performed and a random access procedure is initiated on the second cell, wherein the random access procedure is to request SIB1 of the second cell, and the random access procedure includes: sending a first RA sequence (Random Access Sequence); in step 103A, along with sending the first RA sequence, a first information block is set in the VarRLF-Report; wherein the WUS configuration of the second cell includes the time-frequency resources of the first RA sequence; the first information block includes a first field, and the first field indicates at least the identity of the second cell.

[0142] As an example, the first node is in the RRC_CONNECTED state.

[0143] As an example, the first cell is the serving cell of the first node.

[0144] As an example, the first cell is referred to as Cell A.

[0145] As an example, the first cell is referred to as the anchor cell.

[0146] As an example, the first message is transmitted on the first cell.

[0147] As an example, the first message is transmitted via SRB0.

[0148] As an example, the first message is transmitted via SRB1.

[0149] As an example, the first message is transmitted via SRB3.

[0150] As an example, the first message is transmitted via BCCH.

[0151] As an example, the first message is transmitted via PDSCH.

[0152] As an example, the first message is an RRCReconfiguration message.

[0153] As an example, the first message is a SIB message.

[0154] As an example, the first message is a SIB1 message.

[0155] As an example, the first message is a SIBxx message, where xx is an integer greater than 25.

[0156] As one example, the first message includes the WUS configuration of the second cell.

[0157] As one embodiment, the first message includes WUS configurations for multiple cells, which are neighbor cells of the first cell.

[0158] As an example, the second cell is one of the neighboring cells of the first cell.

[0159] As an example, the WUS configuration of the second cell is the random access configuration of the second cell.

[0160] As an example, the WUS configuration of the second cell includes the random access configuration of the second cell.

[0161] As an example, the WUS configuration of the second cell includes the identity information of the second cell.

[0162] As an example, the identity information of the second cell refers to the physical cell identity of the second cell.

[0163] As an example, the identity information of the second cell refers to at least one of the physical cell identifier or frequency of the second cell.

[0164] As an example, the WUS configuration of the second cell includes the random access configuration of the second cell.

[0165] As an example, the random access configuration of the second cell indicates the time-frequency resources for initiating the random access procedure.

[0166] As one embodiment, the random access configuration includes SIB1-RequestConfig, which indicates the configuration required to request the SIB1.

[0167] As an example, the random access configuration indicates the first RA sequence.

[0168] As an example, the random access configuration indicates the time-frequency resources occupied by the first RA sequence.

[0169] As one embodiment, the random access configuration includes SIB1-RequestResources, which indicates the time-frequency resources occupied by the first RA sequence.

[0170] As an example, the random access configuration includes a ra-PreambleIndex, which indicates the first RA sequence.

[0171] As an example, the random access configuration includes a FrequencyInfoUL-SIB, which indicates the basic parameters of an uplink carrier of the first cell.

[0172] As an example, the random access configuration includes a SubcarrierSpacing, which indicates the subcarrier spacing of the PRACH.

[0173] As an example, the WUS configuration of the second cell includes the reference signal configuration of the second cell.

[0174] As an example, the reference signal configuration includes the configuration of the SSB associated with the first RA sequence.

[0175] As an example, the reference signal configuration includes time-domain resources of the SSB associated with the first RA sequence.

[0176] As an example, the first node experiences a wireless connection failure when the first cell detects a wireless connection failure.

[0177] As an example, the wireless connection failure is an RLF (Remote Link Failure).

[0178] As an example, the wireless connection failure of the first node is a failure to switch to a cell other than the first cell, and the cell other than the first cell is not the second cell.

[0179] As an example, the wireless connection failure is HOF.

[0180] As an example, when a switch to a cell other than the first cell begins, the WUS configuration of the first node is not released.

[0181] As an example, when a handover to a cell other than the first cell begins, the WUS configuration of the first node is valid.

[0182] As an example, whether the first node has a valid WUS configuration depends on the first node itself to determine.

[0183] As an example, the first node not having a valid WUS configuration means that the time for which the WUS configuration is not valid exceeds a first time threshold.

[0184] As an example, the first time threshold is fixed.

[0185] As an example, the unit of the first time threshold is hours.

[0186] As an example, the first time threshold is 48 hours.

[0187] As an example, the first time threshold is 24 hours.

[0188] As an example, the first time threshold is configured by the network.

[0189] As an example, the first node not having a valid WUS configuration means that the configured cell of the WUS configuration is not the currently serving cell.

[0190] As an example, the first node not having a valid WUS configuration means that the NES cell of the WUS configuration is not selected.

[0191] As an example, the first timer is T311.

[0192] As an example, the first timer is T311a.

[0193] As one example, the first timer is used when the first node experiences a wireless connection failure.

[0194] As an example, the first timer is started once the first node experiences a wireless connection failure.

[0195] As an example, the first timer is started when the first node experiences a wireless connection failure.

[0196] As an example, if the first node experiences a wireless connection failure and the first node has a WUS configuration, the first timer is started.

[0197] As an example, during the operation of the first timer, a random access procedure is initiated on the second cell.

[0198] As an example, "during the operation of the first timer" means that the first timer is not stopped.

[0199] As an example, "during the operation of the first timer" means that the first timer is not paused.

[0200] As an example, "during the operation of the first timer" means that the first timer has not been restarted.

[0201] As an example, when the random access procedure is initiated, the SIB1 of the second cell has not been obtained.

[0202] As an example, when the random access procedure is initiated, the SIB1 of the second cell is not stored.

[0203] As an example, before the random access procedure is initiated, the first node detects whether the SIB1 of the second cell has been sent.

[0204] As a sub-implementation, before the random access procedure is initiated, the first node may detect whether the SIB1 of the second cell has been sent. This method balances UE power consumption and SIB1 request latency.

[0205] As a sub-implementation, before the random access procedure is initiated, the first node needs to, or should, detect whether SIB1 has been sent. This method reduces unnecessary SIB1 requests and lowers UE power consumption.

[0206] As a sub-implementation, before the random access procedure is initiated, the first node determines by itself whether the SIB1 of the second cell has been sent. This method improves the flexibility of UE implementation.

[0207] As a sub-example, when the random access procedure is initiated, the first node does not detect that SIB1 of the second cell has been sent.

[0208] As a sub-example, if the first node does not detect that SIB1 has been sent, the first node assumes that SIB1 of the second cell has not been broadcast.

[0209] As a sub-example, the first node initiates the random access procedure if it does not detect that the SIB1 of the second cell has been sent.

[0210] As an example, SIB1 in this application refers to OD(on-demand)-SIB1.

[0211] As an example, the purpose of the random access procedure is to request SIB1 of the second cell.

[0212] As an example, before the random access procedure is initiated, the first node performs cell selection.

[0213] As an example, before the random access procedure is initiated, the first node cell selects the second cell.

[0214] As an example, the first node cell selecting the second cell means that the cell selection conditions of the second cell are met.

[0215] As an example, the cell selection condition is a cell reselection condition.

[0216] As an example, the cell selection criterion is the S criterion.

[0217] As one example, the cell selection criteria are derived from stored information.

[0218] As an example, the cell selection criteria are derived from the first cell, which reduces the overhead of configuration signaling.

[0219] As an example, the cell selection criteria are configured in the WUS configuration, which improves configuration flexibility.

[0220] As an example, the first node cell selecting the second cell means that the second cell and the first cell are on the same frequency.

[0221] As an example, the first node cell selecting the second cell means searching for the SSB information of the second cell.

[0222] As an example, during cell selection, a random access procedure is initiated on the second cell.

[0223] As an example, as a result of cell selection to the second cell, a random access procedure is initiated on the second cell.

[0224] As an example, once the cell selects the second cell, a random access procedure is initiated on the second cell.

[0225] As an example, if the cell selects the second cell, a random access procedure is initiated on the second cell.

[0226] As an example, initiating a random access procedure in the second cell includes sending a first RA sequence.

[0227] As an example, the first RA sequence is a Message 1 (Msg1).

[0228] As an example, the first RA sequence is a UL WUS.

[0229] As an example, the first RA sequence is a preamble, and the first RA sequence is transmitted on PRACH. This method is compatible with existing protocols and reduces the impact of standardization.

[0230] As an example, the first RA sequence is associated with the second cell.

[0231] As an example, the first RA sequence is associated with at least one of the second cell's PCI (Physical Cell Identity) or frequency.

[0232] As one embodiment, the random access procedure includes: listening to MAC RAR messages.

[0233] As a sub-implementation, in response to sending the first RA sequence, the MAC RAR message is listened to.

[0234] As a sub-example, the MAC RAR message is triggered by the first RA sequence.

[0235] As a sub-example, the MAC RAR (Random Access Response) message includes a MAC subPDU, which includes the Random Access Preamble identifier corresponding to the first RA sequence.

[0236] As a sub-example, the MAC RAR message includes a MAC subPDU carrying only a RAPID, which indicates the first RA sequence.

[0237] As a sub-example, the RNTI of the DCI that schedules the MAC RAR message depends on the time-frequency resources occupied by the first RA sequence.

[0238] As one embodiment, the random access procedure includes receiving the MAC RAR message.

[0239] As a sub-example, in response to receiving the MAC RAR message, the first node considers the request for SIB1 of the second cell to be successful.

[0240] As a sub-example, in response to receiving the MAC RAR message, the first node considers that SIB1 of the second cell has been sent.

[0241] As one embodiment, the random access procedure includes: monitoring SIB1 within a first time window.

[0242] As an example, in response to receiving the MAC RAR message, a first time window is opened; the first time window is for monitoring the SIB1 of the second cell.

[0243] As an example, the length of the first time window is configurable.

[0244] As an example, the length of the first time window is a positive integer number of milliseconds (ms).

[0245] As an example, the length of the first time window is a positive integer number of slots.

[0246] As an example, the length of the first time window depends on the period of SIB1.

[0247] As an example, the length of the first time window is a positive integer number of SIB1 periods.

[0248] As an example, the monitoring of SIB1 includes: monitoring PDCCH (Physical downlink control channel).

[0249] As one example, monitoring SIB1 includes monitoring the PDCCH that schedules SIB1.

[0250] As an example, monitoring SIB1 includes performing monitoring at the time of receiving the PDCCH that schedules SIB1.

[0251] As an example, the monitoring SIB1 includes performing monitoring on the time-frequency resources indicated by pdcch-ConfigSIB1 in the MIB (Master Information Block) message of the first cell.

[0252] As an example, monitoring SIB1 includes receiving a PDSCH (Physical downlink shared channel) carrying SIB1.

[0253] As an example, monitoring SIB1 includes decoding the TB (Transmission Block) carrying SIB1.

[0254] As an example, monitoring SIB1 includes: acquiring SIB1.

[0255] As one embodiment, the monitoring of SIB1 includes: receiving SIB1.

[0256] As one embodiment, the timing of receiving the PDCCH of the scheduling SIB1 is configured by pdcch-ConfigSIB1 in the MIB message of the first cell. This method reduces protocol impact and avoids affecting legitimate (legacy) UEs.

[0257] As an example, the timing of receiving the PDCCH for scheduling SIB1 is indicated by the MAC RAR. This method is advantageous for dynamically scheduling SIB1.

[0258] As an example, in response to cell selection to the second cell, a first information block is set in the VarRLF-Report.

[0259] As an example, once the first RA sequence is sent to the second cell, the first information block is set in the VarRLF-Report.

[0260] As an example, the first information block is rlf-Report.

[0261] As one example, the first information block includes rlf-Report.

[0262] As an example, the first information block belongs to rlf-Report.

[0263] As an example, the name of the first information block includes UL-WUS.

[0264] As an example, the name of the first information block includes NES.

[0265] As an example, the first information block is for the WUS configuration.

[0266] As one embodiment, the first information block includes information about the WUS configuration being applied.

[0267] As an example, the WUS configuration of the second cell indicates the time-frequency resources occupied by the first RA sequence.

[0268] As an example, the WUS configuration of the second cell includes the random access information of the second cell, which indicates the time-frequency resources occupied by the first RA sequence.

[0269] As an example, the name of the first domain includes CellId.

[0270] As an example, the name of the first domain includes NESCellId.

[0271] As an example, the name of the first domain includes NES.

[0272] As an example, the name of the first domain includes OD-SIB1CellId.

[0273] As an example, the name of the first domain includes OD-SIB1.

[0274] As an example, the first field indicates the identity information of the second cell to indicate that the second cell was selected by the cell.

[0275] As an example, the first field indicates the identity information of the second cell to indicate that the second cell is an OD-SIB1 cell.

[0276] As an example, the identity information of the second cell is the GCI (Global Cell Identity) of the second cell.

[0277] As an example, the identity information of the second cell is the PCI of the second cell.

[0278] As an example, the identity information of the second cell is the PCI of the second cell and the frequency information of the second cell.

[0279] As an example, the identity information of the second cell is the GCI and PCI of the second cell.

[0280] As an example, the first field only indicates the identity information of the second cell, which makes the signaling design simpler.

[0281] As one embodiment, the first field indicates the identity information of multiple cells including the second cell, which is beneficial for storing more and more complete information.

[0282] As an example, the first field indicates the identity information of the cell in which the first node initiated a random access procedure during the first timer operation. This method makes storage more specific and improves the utilization of storage resources.

[0283] As an example, in response to the first node's wireless connection failure, an RRC connection re-establishment procedure is executed; in response to the execution of the RRC connection re-establishment, a first timer is started; during the operation of the first timer, the cell selects the second cell and initiates the random access procedure on the second cell; in response to the cell selects the second cell, a first information block is set in the VarRLF-Report, the first information block including a first field indicating the identity information of the second cell.

[0284] As an example, in response to the first node experiencing a wireless connection failure, an RRC connection re-establishment procedure is executed; in response to the execution of the RRC connection re-establishment, a first timer is started; during the operation of the first timer, the cell selects the second cell and initiates the random access procedure on the second cell; in response to the cell selecting the second cell, an rlf-report is set in the VarRLF-Report, the rlf-report including a first field indicating the identity information of the second cell.

[0285] Example 1B

[0286] Example 1B illustrates a flowchart of communication of a first node according to an embodiment of this application, as shown in Figure 1B. In Figure 1B, each box represents a step, and it is particularly important to emphasize that the order of the boxes in the figure does not represent the temporal sequence of the steps represented.

[0287] In Example 1B, the first node in this application receives a first RRC message in step 101B; in step 102B, a first timer is started along with initiating an RRC connection re-establishment process; and in step S103B, it is determined whether to execute actions upon going to RRC_IDLE at the first moment. Whether to execute actions upon going to RRC_IDLE at the first moment depends on whether at least the first node has a WUS configuration; the time length between the start time of the first timer and the first moment is the first time length; wherein, the dependence on whether to execute actions upon going to RRC_IDLE at the first moment depends on whether at least the first node has a WUS configuration includes:

[0288] If the first node does not have a WUS configuration, perform the action when switching to RRC_IDLE at the first time.

[0289] If at least the first node has a WUS configuration, the action of transitioning to RRC_IDLE is not performed at the first time.

[0290] As an example, the first RRC message is transmitted via SRB0.

[0291] As an example, the first RRC message is transmitted via SRB1.

[0292] As an example, the first RRC message is transmitted via SRB3.

[0293] As an example, the first RRC message is transmitted via BCCH.

[0294] As an example, the first RRC message is transmitted via PDSCH.

[0295] As an example, the first RRC message is an RRCReconfiguration message.

[0296] As an example, the first RRC message is an RRC Resume message.

[0297] As an example, the first RRC message is an RRCSetup message.

[0298] As an example, the first RRC message includes an RRCReconfiguration message.

[0299] As an example, the first RRC message includes a SpCellConfig field.

[0300] As an example, the first RRC message includes an rlf-TimersAndConstants IE.

[0301] As an example, the first RRC message is a SIB message.

[0302] As an example, the first RRC message is a SIB1 message.

[0303] As an example, the first RRC message is a SIBxx message.

[0304] As an example, the first RRC message is a SIB26 message.

[0305] As an example, the first RRC message is a SIBxx message, where xx is an integer greater than 25.

[0306] As an example, the first RRC message includes the WUS configuration.

[0307] As an example, the first RRC message configures at least a first timer.

[0308] As an example, the first RRC message includes the first time length.

[0309] As an example, the first RRC message configures the first time length to the first timer.

[0310] As a sub-implementation of the above embodiments, the first time length is the value of the first timer.

[0311] As a sub-implementation of the above embodiments, the first time length is a candidate value of the first timer.

[0312] As an example, the first RRC message configures the first time length to the first timer.

[0313] As an example, the first RRC message indicates the first time length to the first timer.

[0314] As an example, the accompanying initiation of the RRC connection re-establishment process means that when a radio link failure (RLF) is detected, the RRC connection re-establishment process is initiated.

[0315] As an example, the accompanying initiation of the RRC connection re-establishment process means: when a wireless connection failure is detected and the SCG is suspended, the RRC connection re-establishment process is initiated.

[0316] As an example, the accompanying initiation of the RRC connection re-establishment process means that when a wireless connection failure is detected and the SCG is deactivated, the RRC connection re-establishment process is initiated.

[0317] As an example, the accompanying RRC connection re-establishment process means that when a wireless connection failure is detected and the PSCell changes, the RRC connection re-establishment process is initiated.

[0318] As an example, the accompanying initiation of the RRC connection re-establishment process means that when a wireless connection failure is detected and timer T316 expires, the RRC connection re-establishment process is initiated.

[0319] As an example, the accompanying initiation of the RRC connection re-establishment process means that when a wireless connection failure is detected and timer T316 is not configured, the RRC connection re-establishment process is initiated.

[0320] As an example, the phrase "starting the first timer while initiating the RRC connection re-establishment process" means that the first timer is started when the RRC connection re-establishment process is initiated.

[0321] As an example, the phrase "starting the first timer while initiating the RRC connection re-establishment process" means that the first timer is started once the RRC connection re-establishment process is initiated.

[0322] As an example, the phrase "starting the first timer while initiating the RRC connection re-establishment process" means that the first timer is started when at least the RRC connection re-establishment process is initiated.

[0323] As an example, the phrase "starting the first timer while initiating the RRC connection re-establishment process" means that the first timer is started when the RRC connection re-establishment process is initiated and there is no WUS configuration.

[0324] As one embodiment, starting the first timer includes: activating the first timer.

[0325] As one embodiment, starting the first timer includes: applying the value of the first timer; wherein the value of the first timer is a first time length.

[0326] As one embodiment, starting the first timer includes: the first timer starts running.

[0327] As an example, the first timer is started at the time when the RRC connection re-establishment process is initiated.

[0328] As an example, the time when the first timer is started is the time when the first timer is activated.

[0329] As an example, the time when the first timer is started is the time when it starts running.

[0330] As an example, when the action of switching to RRC_IDLE is performed at the first time, the first node is in a non-RRC_IDLE state.

[0331] As an example, when the action of switching to RRC_IDLE is performed at the first time, the first node is in the RRC_CONNECT state.

[0332] As an example, the action performed when transitioning to RRC_IDLE at the first time includes: stopping all timers.

[0333] As an example, the action performed when switching to RRC_IDLE at the first time includes: releasing all RRC configurations stored in the first node.

[0334] As an example, the action performed when switching to RRC_IDLE at the first time includes: not releasing the WUS configuration.

[0335] As an example, the action performed when transitioning to RRC_IDLE at the first time includes indicating the release cause.

[0336] As an example, the action performed when switching to RRC_IDLE at the first time includes: performing cell selection.

[0337] As an example, the first time is the time when the first timer expires.

[0338] As an example, the expiration of the first timer means that the first timer reaches a certain value.

[0339] As an example, the certain value is the first time length.

[0340] As an example, the first timer is used for at least the RRC connection re-establishment process.

[0341] As an example, the first timer is T311.

[0342] As an example, the first timer is configured for at least WUS.

[0343] As an example, the first timer is T311a, and the first timer is configured for the WUS.

[0344] As an example, the first time is the time when the action of switching to RRC_IDLE is performed.

[0345] As an example, the first time is the time when the action of transitioning to RRC_IDLE begins to be executed.

[0346] As an example, the first time is the time when the action of switching to RRC_IDLE is completed.

[0347] As an example, the first time is the time when the first time length ends.

[0348] As an example, the first time length is configured by the first RRC message.

[0349] As an example, the first time length is the duration of the RRC connection re-establishment process.

[0350] As an example, if the first node does not have the WUS configuration, the first time length is configured for the first timer for the RRC connection re-establishment process.

[0351] As an example, the first time length is the default, and the first timer uses the first time length.

[0352] As an example, the start time of the first time length is the time when the first timer is started.

[0353] As an example, the deadline of the first time length is the first time.

[0354] As an example, the first time length refers to the time elapsed from when the first timer is started to when the first time is reached.

[0355] As an example, if the first node does not have a WUS configuration, the first timer is T311, the first time length is configured to the first timer, and the first time is the time when the first timer expires.

[0356] As an example, the first timer is always running during the time interval from when the first timer is started to when the first time occurs.

[0357] As one example, the first timer does not expire and is not stopped during the time interval between the start time of the first timer and the first time.

[0358] As an example, during the time interval from when the first timer is started to when the first time is reached, no suitable NR cell is selected.

[0359] As an example, the cell is not considered as blocked during the time interval from when the first timer is started to when the first time is reached.

[0360] As an example, no cell re-selection was performed during the time interval from when the first timer was started to when the first time was reached.

[0361] As an example, if the first node has a WUS configuration, the first timer is T311, the first time length is configured for the first timer, and the first time is the time when the first timer expires.

[0362] As an example, during the time interval between the start time of the first timer and the first time, the first timer neither expires nor is paused.

[0363] As an example, during the time interval from when the first timer is started to when the first time is reached, no suitable cell has been selected, and the suitable cell is an R-19NES cell.

[0364] As an example, no random access procedure was initiated during the time interval from when the first timer was started to when the first time was reached.

[0365] As an example, the first node receives the WUS configuration in the current serving cell.

[0366] As an example, the first node receives the WUS configuration in a previously connected cell.

[0367] As an example, the first node receives the WUS configuration before initiating the RRC connection re-establishment process.

[0368] As an example, "the first node does not have WUS configuration" means that the first node has not received WUS configuration.

[0369] As an example, "the first node does not have WUS configuration" means that the first node is not configured with WUS.

[0370] As an example, the first node not having WUS configuration means that the first node releases the configured WUS configuration.

[0371] As an example, the first node not having a WUS configuration means that the first node considers the stored WUS configuration to be invalid.

[0372] As an example, having WUS configuration for the first node means that the first node is configured with WUS configuration.

[0373] As an example, the first node having WUS configuration means that the first node receives WUS configuration.

[0374] As an example, the first node having WUS configuration means that the first node receives WUS configuration in the serving cell.

[0375] As an example, the first node having WUS configuration means that the first node considers the stored WUS configuration to be valid.

[0376] As an example, as long as the first node has WUS configuration, the above method is beneficial to improve configuration utilization if the action of switching to RRC_IDLE is not performed at the first time.

[0377] As an example, when at least the first node has a WUS configuration, the action of switching to RRC_IDLE is not performed at the first time.

[0378] As an example, the statement that at least the first node has a WUS configuration includes: the first node has a WUS configuration, and the WUS configuration is applied within the first time length. The above method helps to reduce communication interruption time.

[0379] As one embodiment, the statement that at least the first node has a WUS configuration includes: if the WUS configuration is being applied at the first time.

[0380] As an example, the statement that at least the first node has a WUS configuration includes: the first node has a WUS configuration, and the first timer is paused within the first time length. The above method is simple to implement.

[0381] As an example, the statement that at least the first node has a WUS configuration includes: the first node has a WUS configuration, and if another timer is running at the first time, the above method helps to reduce the impact on legacy UEs.

[0382] As one embodiment, the statement that at least the first node has a WUS configuration includes: the first node has a WUS configuration, and the first timer does not use the first event length.

[0383] As an example, the activation of the other timer depends on the first node having a WUS configuration.

[0384] As an example, when the first node has a WUS configuration, once the RRC connection re-establishment process is initiated, the first timer and the other timer are started.

[0385] As an example, when the first node has a WUS configuration, the other timer is started once the RRC connection re-establishment process is initiated.

[0386] As an example, when the first node has a WUS configuration, the other timer is started at the first time.

[0387] As an example, the other timer is not the first timer.

[0388] As an example, the other timer is not T311.

[0389] As an example, the other timer has a WUS configuration for the first node.

[0390] As an example, the first time length is not configured for the other timer.

[0391] As an example, when the first node does not have a WUS configuration, the action of switching to RRC_IDLE is performed at the first time.

[0392] As an example, if the first node does not have a WUS configuration, the action of transitioning to RRC_IDLE is performed at the first time once the first timer expires.

[0393] Example 2

[0394] Example 2 illustrates a schematic diagram of a network architecture according to an embodiment of this application, as shown in Figure 2. Figure 2 illustrates network architecture 200. The network architecture 200 is a 5G NR (New Radio) / LTE (Long-Term Evolution) / LTE-A (Long-Term Evolution Advanced) system, or a 5G+ network architecture, or a 6G network architecture, or a future 3GPP network architecture; the network architecture 200 may be referred to as 5GS (5G System) / EPS (Evolved Packet System), or 6GS (6G System); the network architecture 200 includes at least one of UE (User Equipment) 201, RAN (Radio Access Network) 202, core network 210, HSS (Home Subscriber Server) / UDM (Unified Data Management) 220, and Internet service 230. The network architecture 200 can interconnect with other access networks, but these entities / interfaces are not shown for simplicity. As shown, the network architecture 200 provides packet-switched services; however, those skilled in the art will readily understand that the various concepts presented throughout this application can be extended to networks providing circuit-switched services or other cellular networks. The RAN includes node 203 and other nodes 204. Node 203 provides user and control plane protocol termination toward UE 201. Node 203 can be connected to other nodes 204 via an Xn interface (e.g., backhaul) / X2 interface. Node 203 may also be referred to as a base station, base transceiver station (BTS), radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), CU (Centralized Unit), DU (Distributed Unit), TRP (Transmitter Receiver Node), or some other suitable term. Instances of node 203 include node B (NB), gNB, eNB, ng-eNB, en-gNB, IAB network devices (e.g., IAB-node, IAB-donor, IAB-donor-CU, or IAB-donor-DU), test equipment, and signaling testers.Instances of node 203 may also include relay devices (e.g., L3 relay, L2 relay, or L1 relay), routers, switches, and gateway devices. The core network 210 is a 5GC (5G Core Network) / EPC (Evolved Packet Core), or the core network 210 is a 6GC; node 203 provides UE 201 with an access point to the core network 210. Examples of UE201 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, 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 IoT devices, IoT terminals, industrial IoT devices, machine-type communication devices, land vehicles, automobiles, ships, wearable devices (e.g., watches, rings, glasses, VR / XR devices), handsets, in-vehicle terminals, IAB terminal equipment (e.g., IAB-MT), test equipment, signaling testers, or any other similar functional devices. Those skilled in the art may also refer to UE201 as a mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handheld device, user agent, mobile client, client, or any other suitable term. Node 203 is connected to the core network 210 via the S1 / NG interface. The core network 210 includes an MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MMEs / AMFs / SMFs 214, an S-GW (Service Gateway) / UPF (User Plane Function) 212, and a P-GW (Packet Data Network Gateway) / UPF 213. The MME / AMF / SMF 211 is the control node that handles signaling between UE 201 and the core network 210. Generally, the MME / AMF / SMF 211 provides bearer and connection management.All user IP (Internet Protocol) packets are transmitted through the S-GW / UPF212, which is itself connected to the P-GW / UPF213. The P-GW provides UE IP address allocation and other functions. The P-GW / UPF213 is connected to Internet service 230. Internet service 230 includes operator-compliant Internet Protocol services, specifically including the Internet, intranet, IMS (IP Multimedia Subsystem), and packet-switched streaming services.

[0395] As an example, the UE201 corresponds to the first node in this application.

[0396] As an example, the first node in this application includes the UE201.

[0397] As an example, the UE201 is a user equipment (UE).

[0398] As an example, the UE201 includes a UE.

[0399] As an example, the UE201 is a relay device.

[0400] As an example, the UE201 is a gateway device.

[0401] As an example, the UE201 supports AI / ML.

[0402] As an example, the UE201 supports 5G.

[0403] As an example, the UE201 supports 6G.

[0404] As an example, node 203 corresponds to the second node in this application.

[0405] As an example, the second node in this application includes node 203.

[0406] As one example, node 203 is a base station device.

[0407] As an example, the second node in this application includes not only the node 203, but also at least one higher-level device; the higher-level device includes at least one of a core network device or an OAM device.

[0408] As an example, the second node in this application includes the node 203 and the core network 210.

[0409] As an example, the second node in this application includes the node 203 and the core network 214.

[0410] As an example, UE201 corresponds to the first node in this application, and node 203 corresponds to the second node in this application.

[0411] As an example, the first node in this application includes the UE201, and the second node in this application includes the node203.

[0412] Example 3

[0413] Example 3 illustrates a schematic diagram of an embodiment of a wireless protocol architecture for a user plane and control plane according to this application, as shown in Figure 3. 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 3 shows the radio protocol architecture for the control plane 300 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 herein as PHY 301. Layer 2 (L2 layer) 305 is above PHY 301 and includes a MAC (Medium Access Control) sublayer 302, an RLC (Radio Link Control) sublayer 303, and a PDCP (Packet Data Convergence Protocol) sublayer 304. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security through encrypted data packets and provides cross-area mobility support. RLC sublayer 303 provides upper-layer packet segmentation and reassembly, retransmission of lost packets, and packet reordering to compensate for out-of-order reception caused by HARQ (Hybrid Automatic Repeat Request). MAC sublayer 302 provides multiplexing between the logical and transport channels. MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) within a cell. MAC sublayer 302 is also responsible for HARQ operations. RRC (Radio Resource Control) sublayer 306 in Layer 3 (L3) of the control plane 300 is responsible for acquiring radio resources (i.e., radio bearers) and using RRC signaling to configure the lower layers. The radio protocol architecture of user plane 350 includes Layer 1 (L1 layer) and Layer 2 (L2 layer). In user plane 350, the radio protocol architecture for physical layer 351, PDCP sublayer 354 in L2 layer 355, RLC sublayer 353 in L2 layer 355, and MAC sublayer 352 in L2 layer 355 is largely the same as the corresponding layers and sublayers in control plane 300. However, PDCP sublayer 354 also provides header compression for upper layer packets to reduce radio transmission overhead. L2 layer 355 in user plane 350 also includes SDAP (Service Data Adaptation Protocol) sublayer 356. SDAP sublayer 356 is responsible for mapping between QoS streams and data radio bearers (DRBs) to support service diversity.

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

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

[0416] As an example, the first RA sequence in this application is generated in the PHY301 or PHY351.

[0417] As an example, the second message in this application is generated in the RRC306.

[0418] As an example, the second message in this application is generated in the PHY301 or PHY351.

[0419] As an example, the second message in this application is generated by MAC302 or MAC352.

[0420] As an example, the SIB1 in this application is generated in the RRC306.

[0421] As an example, the first message in this application is generated in the RRC306.

[0422] As an example, the third message in this application is generated in the RRC306.

[0423] Example 4

[0424] Embodiment 4 illustrates a schematic diagram of a first communication device and a second communication device according to this application, as shown in Figure 4. 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.

[0425] The first communication device 450 includes a controller / processor 459, a memory 460, a data source 467, a transmitting processor 468, a receiving processor 456, a multi-antenna transmitting processor 457, a multi-antenna receiving processor 458, a transmitter / receiver 454, and an antenna 452.

[0426] The second communication device 410 includes a controller / processor 475, a memory 476, a receiver processor 470, a transmitter processor 416, a multi-antenna receiver processor 472, a multi-antenna transmitter processor 471, a transmitter / receiver 418, and an antenna 420.

[0427] In the transmission from the second communication device 410 to the first communication device 450, at the second communication device 410, upper-layer data packets from the core network are provided to the controller / processor 475. The controller / processor 475 implements L2 layer functionality. 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 retransmitting 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). Transmit processor 416 performs encoding and interleaving to facilitate forward error correction (FEC) at the second communication device 410, and mapping of signal clusters based on various modulation schemes (e.g., Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), M-Phase Shift Keying (M-PSK), M-QAM). Multi-antenna transmit processor 471 performs digital spatial precoding on the encoded and modulated symbols, including codebook-based and non-codebook-based precoding, and beamforming processing, generating one or more spatial streams. Transmit processor 416 then maps each spatial stream to subcarriers, multiplexes it with a reference signal (e.g., a pilot) in the time and / or frequency domains, and subsequently uses inverse fast Fourier transform (IFFT) to generate a physical channel carrying the time-domain multicarrier symbol stream. Multi-antenna transmit processor 471 then performs transmit analog precoding / beamforming operations on the time-domain multicarrier symbol stream. Each transmitter 418 converts the baseband multicarrier symbol stream provided by the multi-antenna transmitter processor 471 into an radio frequency stream, which is then provided to different antennas 420.

[0428] 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 radio frequency carrier and converts the radio frequency stream into a baseband multicarrier symbol stream, which is then provided to the receiver processor 456. The receiver processor 456 and the multi-antenna receiver processor 458 implement various signal processing functions of the L1 layer. The multi-antenna receiver processor 458 performs receive analog precoding / beamforming operations on the baseband multicarrier symbol stream from the receiver 454. The receiver processor 456 uses a Fast Fourier Transform (FFT) to convert the baseband multicarrier symbol stream after the receive analog precoding / beamforming operations 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 receiver processor 456, where the reference signal is used for channel estimation, and the data signal is recovered in the multi-antenna receiver processor 458 after multi-antenna detection to recover any spatial stream destined for the first communication device 450. Symbols on each spatial stream are demodulated and recovered in the receive processor 456, generating soft decisions. The receive 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 over 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 Layer 2. The controller / processor 459 may be associated with a memory 460 storing program code and data. The memory 460 may be referred to as computer-readable media. In the transmission from the second communication device 410 to the first communication device 450, the controller / processor 459 provides multiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport and logical channels to recover upper-layer data packets from the core network. The upper-layer data packets are then provided to all protocol layers above Layer 2. Various control signals may also be provided to Layer 3 for Layer 3 processing.

[0429] 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 functions 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, implementing L2 layer functions for the user plane and control plane. The controller / processor 459 is also responsible for retransmitting lost packets and signaling to the second communication device 410. Transmit processor 468 performs modulation mapping and channel coding processing, while multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based and non-codebook-based precoding, and beamforming processing. Subsequently, transmit processor 468 modulates the generated spatial stream into a multi-carrier / single-carrier symbol stream. After analog precoding / beamforming operations in multi-antenna transmit processor 457, the stream is provided to different antennas 452 via transmitter 454. Each transmitter 454 first converts the baseband symbol stream provided by multi-antenna transmit processor 457 into a radio frequency symbol stream before providing it to antenna 452.

[0430] 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 receiving 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 radio frequency signals through its corresponding antenna 420, converts the received radio frequency signals into baseband signals, and provides the baseband signals to the multi-antenna receiving processor 472 and the receiving processor 470. The receiving processor 470 and the multi-antenna receiving processor 472 jointly implement the L1 layer functions. The controller / processor 475 implements the L2 layer functions. The controller / processor 475 may be associated with a memory 476 that stores program code and data. The memory 476 may be referred to as computer-readable media. In the transmission from the first communication device 450 to the second communication device 410, the controller / processor 475 provides multiplexing between the transmission and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover upper-layer data packets from the UE 450. Upper-layer packets from the controller / processor 475 can be provided to the core network.

[0431] As one embodiment, the first communication device 450 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 with the at least one processor, and the first communication device 450 at least: receives a first message in a first cell; the first message includes the WUS configuration of a second cell; starts a first timer in response to a radio connection failure of the first node; while the first timer is running, performs cell selection and initiates a random access procedure on the second cell, wherein the random access procedure is for requesting SIB1 of the second cell, the random access procedure including: sending a first RA sequence (Random Access Sequence); along with sending the first RA sequence, setting a first information block in a VarRLF-Report; wherein the WUS configuration of the second cell includes the time-frequency resources of the first RA sequence; the first information block includes a first field, the first field indicating at least the identity of the second cell.

[0432] As one embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program that, when executed by at least one processor, produces actions including: receiving a first message in a first cell; the first message including a WUS configuration of a second cell; starting a first timer in response to a wireless connection failure of the first node; and, while the first timer is running, performing cell selection and initiating a random access procedure on the second cell, wherein the random access procedure is for requesting SIB1 of the second cell, and the random access procedure includes: sending a first RA sequence; and, along with sending the first RA sequence, setting a first information block in a VarRLF-Report; wherein the WUS configuration of the second cell includes time-frequency resources of the first RA sequence; and the first information block includes a first field indicating the identity of at least the second cell.

[0433] As one embodiment, the second communication device 410 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 with the at least one processor. The second communication device 410 at least: transmits the first message; the first message includes the WUS configuration of the second cell; receives a first RA sequence; wherein, in response to a radio connection failure occurring at the receiver of the first message, a first timer is started; while the first timer is running, the receiver of the first message performs cell selection and initiates a random access procedure on the second cell, wherein the random access procedure is for requesting SIB1 of the second cell, the random access procedure including: transmitting the first RA sequence; accompanied by transmitting the first RA sequence, the receiver of the first message sets a first information block in a VarRLF-Report; wherein the WUS configuration of the second cell includes the time-frequency resources of the first RA sequence; the first information block includes a first field, the first field indicating at least the identity of the second cell.

[0434] As one embodiment, the second communication device 410 includes: a memory storing a computer-readable instruction program that, when executed by at least one processor, produces actions including: sending a first message; the first message including a WUS configuration of a second cell; receiving a first RA sequence; wherein, in response to a radio connection failure occurring at the receiver of the first message, a first timer is started; while the first timer is running, the receiver of the first message performs cell selection and initiates a random access procedure on the second cell, wherein the random access procedure is for requesting SIB1 of the second cell, the random access procedure including: sending the first RA sequence; accompanied by sending the first RA sequence, the receiver of the first message sets a first information block in a VarRLF-Report; wherein the WUS configuration of the second cell includes time-frequency resources of the first RA sequence; the first information block includes a first field indicating the identity of at least the second cell.

[0435] As one embodiment, at least one of the antenna 452, the transmitter 454, the transmitter processor 468, and the controller / processor 459 is used to transmit the first RA sequence; at least one of the antenna 420, the receiver 418, the receiver processor 470, and the controller / processor 475 is used to receive the first RA sequence.

[0436] As one embodiment, at least one of the antenna 452, the receiver 454, the receiving processor 456, and the controller / processor 459 is used to receive the first message; at least one of the antenna 420, the transmitter 418, the transmitting processor 416, and the controller / processor 475 is used to transmit the first message.

[0437] As one embodiment, at least one of the antenna 452, the receiver 454, the receiving processor 456, and the controller / processor 459 is used to receive the second message; at least one of the antenna 420, the transmitter 418, the transmitting processor 416, and the controller / processor 475 is used to transmit the second message.

[0438] As one embodiment, at least one of the antenna 452, the transmitter 454, the transmitter processor 468, and the controller / processor 459 is used to transmit a third message; at least one of the antenna 420, the receiver 418, the receiver processor 470, and the controller / processor 475 is used to receive a third message.

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

[0440] As an example, the first node in this application includes the first communication device 450.

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

[0442] As an example, the second node in this application includes the second communication device 410.

[0443] As an example, the first communication device 450 is a user equipment, and the second communication device 410 is a base station device.

[0444] As an example, the first communication device 450 is a base station device, and the second communication device 410 is a base station device.

[0445] As an example, the first communication device 450 is a user equipment, and the second communication device 410 is a user equipment.

[0446] Example 5A

[0447] Example 5A illustrates a wireless signal transmission flowchart according to an embodiment of the present application, as shown in Figure 5A.

[0448] For the first node U01A, in step S5101A, a first message is received in the first cell; the first message includes the WUS configuration of the second cell; in step S5102A, a first timer is started in response to the first node experiencing a radio connection failure; when the first timer runs, cell selection is performed and a random access procedure is initiated on the second cell, wherein the random access procedure is to request SIB1 of the second cell, and the random access procedure includes: sending a first RA sequence; in step S5103A, sending the first RA sequence; in step S5104A, along with sending the first RA sequence, setting a first information block in the VarRLF-Report; wherein the WUS configuration of the second cell includes the time-frequency resources of the first RA sequence; the first information block includes a first field, the first field indicating at least the identity of the second cell; in step S5105A, a MAC RAR message is received in response to sending the first RA sequence; in step S5106A, SIB1 is received.

[0449] For the second node N02A, in step S5201A, the first message is sent.

[0450] For the third node N03A, in step S5301A, the first RA sequence is received; in step S5302A, a MAC RAR message is sent; in step S5303A, SIB1 is sent.

[0451] As one example, the second node N02A is the sustaining base station of the first cell.

[0452] As an example, the third node N03A is the sustaining base station of the second cell.

[0453] As an example, the third node N03A is at least the sustaining base station of the second cell.

[0454] As an example, the third node N03A is the second node N02A.

[0455] As an example, the third node N03A is not the second node N02A.

[0456] As an example, if the first node includes the WUS configuration of the second cell, in response to a wireless connection failure of the first node, the first timer is started, and the first timer is not T311.

[0457] The above method takes into account the impact of the delay caused by the OD-SIB1 program on the operation of T311.

[0458] As an example, if the first node does not include the WUS configuration of the second cell, timer T311 is started in response to the first node experiencing a wireless connection failure.

[0459] As an example, the first timer and the timer T311 are different timers, and whether the first timer starts is related to whether the first node has a WUS configuration.

[0460] As an example, the first timer is T311.

[0461] As one embodiment, the first timer has a first value and a second value, and the application of the first value or the second value of the first timer is related to whether the first node has a WUS configuration.

[0462] As an example, once the first RA sequence is sent, a first information block is set in the VarRLF-Report.

[0463] As an example, in response to the transmission of the first RA sequence, a first information block is set in the VarRLF-Report.

[0464] As an example, once a MAC RAR message is received, the first information block is set in the VarRLF-Report.

[0465] As an example, in response to receiving a MAC RAR message, a first information block is set in the VarRLF-Report.

[0466] As an example, when the first time window is in effect, a first information block is set in VarRLF-Report.

[0467] As an example, in response to opening the first time window, a first information block is set in VarRLF-Report.

[0468] As an example, during the operation of the first time window, a first information block is set in VarRLF-Report.

[0469] As an example, once SIB1 is received, the first information block is set in the VarRLF-Report.

[0470] As an example, in response to receiving SIB1, a first information block is set in the VarRLF-Report.

[0471] As an example, in response to the successful request for SIB1 of the second cell, a first information block is set in the VarRLF-Report.

[0472] As an example, in response to the request for SIB1 failure of the second cell, a first information block is set in the VarRLF-Report.

[0473] As an example, the dashed box F5.1A is present.

[0474] As an example, step S5106A is present.

[0475] As a sub-implementation, SIB1 is sent.

[0476] As a sub-implementation, only one SIB1 is sent.

[0477] As a sub-implementation, multiple SIB1s are sent.

[0478] As a sub-implementation, the plurality of SIB1s are identical.

[0479] As a sub-example, at least two of the plurality of SIB1s are different.

[0480] As a sub-implementation, in response to the receipt of the first RA sequence, the third node N03A sends SIB1.

[0481] As a sub-example, after the MAC RAR message is sent, the third node N03A sends SIB1.

[0482] As a sub-example, in the transmission time window corresponding to the first time window, the third node N03A transmits SIB1.

[0483] As a sub-implementation, after the MAC RAR message is received, the first node opens the first time window after a second time interval.

[0484] As a sub-implementation, the length of the second time interval is indicated by the MAC RAR message, which helps to improve configuration flexibility.

[0485] As a sub-example, the MAC RAR message includes the length of the second time interval.

[0486] As a sub-example, the MAC RAR message includes parameters for calculating the length of the second time interval.

[0487] As a sub-example, the length of the second time interval is indicated by the WUS configuration of the second cell.

[0488] As a sub-example, the WUS configuration of the second cell includes the length of the second time interval.

[0489] As a sub-example, the WUS configuration of the second cell includes parameters for calculating the length of the second time interval.

[0490] As a sub-implementation, the length of the second time interval is indicated by the RRC message.

[0491] As a sub-example, the RRC message includes the length of the second time interval.

[0492] As a sub-example, the RRC message includes parameters for calculating the length of the second time interval.

[0493] As a sub-implementation, the length of the second time interval depends on the calculation of the first node.

[0494] As a sub-implementation, the length of the second time interval is defaulted, which saves configuration resources.

[0495] As a sub-example, in response to receiving the MAC RAR message, the first node considers the random access procedure initiated on the second cell to be successful.

[0496] As a sub-implementation, in response to receiving SIB1 in the first time window, the first node considers the random access procedure initiated on the second cell to be successful.

[0497] As a sub-implementation, in response to receiving SIB1 in the first time window, the first node considers the request for SIB1 of the second cell to be successful.

[0498] As a sub-implementation, when the random access procedure is successfully initiated on the second cell, the first node considers the request for SIB1 of the second cell to be successful.

[0499] As a sub-implementation, in response to successfully receiving SIB1 in the first time window, the successfully received SIB1 is stored.

[0500] As a sub-implementation, the successfully received SIB1 is processed as a response to the successful reception of SIB1 in the first time window.

[0501] As an additional embodiment, processing the successfully received SIB1 includes processing the fields in the successfully received SIB1.

[0502] As an alternative embodiment, the process includes reading.

[0503] As an additional embodiment, the process includes applying.

[0504] As a sub-implementation, in response to the successful reception of SIB1 in the first time window, information about the random access procedure is recorded in the VarRA-Report.

[0505] As a sub-implementation, in response to successfully receiving SIB1 in the first time window, information in SIB1 is read.

[0506] As a sub-implementation, if the RPLMN selected by a higher layer from the PLMNs included in the successfully received SIB1 plmn-IdentityList, or if the PLMN is not included in the plmn-IdentityList of the VarRA-Report, then all random access procedure information in the VarRA-Report except for the random access procedure itself is cleared.

[0507] As a sub-implementation, if the registered SNPN identifier selected by a higher layer from the PLMN included in the NPN-IdentityInfoList in the successfully received SIB1, or if the SNPN identifier is not included in the snpn-IdentityList of the VarRA-Report, then all random access procedure information in the VarRA-Report except for the random access procedure itself is cleared.

[0508] In one embodiment, step S5106A is not present.

[0509] As a sub-implementation, SIB1 was not sent.

[0510] As a sub-implementation, the first RA sequence is received.

[0511] As a sub-implementation, upon receiving the first RA sequence, the third node N03A is requested to send SIB1. This method helps maintain consistency in understanding between the first node U01A and the third node N03A.

[0512] As a sub-implementation, the third node N03A is not required to send SIB1 when the first RA sequence is received. This method improves the flexibility of the third node N03A implementation, especially by saving energy when SIB1 is not sent.

[0513] As a sub-example, the second node N02A is not required to send SIB1, including whether the third node N03A sends SIB1, which is determined by the third node N03A itself.

[0514] As a sub-example, the third node N03A not being required to send SIB1 includes the third node N03A determining whether to send SIB1 on its own.

[0515] As a sub-implementation, the third node N03A does not send SIB1 before the first RA sequence is received; the third node N03A sends SIB1 in response to the receipt of the first RA sequence. This method reduces the transmission of SIB1, which is beneficial for energy saving.

[0516] As an example, the dashed box F5.1A is not present.

[0517] In one embodiment, the first RA sequence was not received.

[0518] Example 5B

[0519] Example 5B illustrates a wireless signal transmission flowchart according to an embodiment of this application, as shown in Figure 5B. It should be noted that the order in this example does not limit the signal transmission order or the order of implementation in this application.

[0520] For the first node U01B, in step S5101B, a first RRC message is received, and the first RRC message is configured with a first time length; in step S5102B, a first timer is started along with the initiation of an RRC connection re-establishment process; in step S5103, a second timer is started; in step S5104B, it is determined whether to execute the action of switching to RRC_IDLE in the first time: if the first node does not have WUS configuration, the action of switching to RRC_IDLE is executed in the first time; if at least the first node has WUS configuration, the action of switching to RRC_IDLE is not executed in the first time.

[0521] For the second node N02B, in step S5201B, the first RRC message is sent.

[0522] In Example 5B, whether actions upon going to RRC_IDLE are executed at the first moment depends on whether at least the first node has a WUS configuration; the length of time between the start time of the first timer and the first moment is the first time length.

[0523] As an example, the second node N02B is the sustaining base station of the current serving cell.

[0524] As an example, the second node NO2 is a maintenance base station for a cell previously served by the first node U01B.

[0525] As an example, the first node receives a first RRC message.

[0526] As an example, the first RRC message is a SIB message.

[0527] As an example, the first RRC message configures the WUS configuration.

[0528] As an example, the WUS configuration is SIBxx.

[0529] As one example, the WUS configuration includes SIBxx.

[0530] As an example, the WUS configuration is SIB26.

[0531] As an example, the WUS configuration is SIBxx, where xx is an integer greater than 25.

[0532] As an example, the WUS configuration is SIBxx-r19.

[0533] As an example, the WUS configuration belongs to SIBxx.

[0534] As an example, the WUS configuration includes the configuration information of the R-19NES cell.

[0535] As an example, the WUS configuration includes OD-SIB1-CellConfig-r19.

[0536] As an example, the WUS configuration is OD-SIB1-CellConfig-r19.

[0537] As an example, the WUS configuration includes ul-WUS-Config-r19.

[0538] As an example, the WUS configuration is ul-WUS-Config-r19.

[0539] As an example, the WUS configuration includes first configuration information.

[0540] As an example, the first configuration information indicates the first RA sequence.

[0541] As an example, the WUS configuration includes a PhysCellId, which indicates the PCI of the first cell.

[0542] As an example, the WUS configuration includes the identity information of at least one cell, which is not the currently serving cell.

[0543] As an example, the identity information of the at least one cell is NES-CellId.

[0544] As an example, the identity information of the at least one cell includes a PhysCellId.

[0545] As an example, the identity information of the at least one cell includes an ARFCN-ValueNR.

[0546] As one embodiment, the WUS configuration includes first configuration information, which configures random access resources.

[0547] As an example, the first configuration information indicates the first RA sequence.

[0548] As an example, the first configuration information indicates the time-frequency resources occupied by the first RA sequence.

[0549] As one example, the first configuration information includes a RACH-ConfigGeneric.

[0550] As an example, the first configuration information includes a RACH-ConfigCommon.

[0551] As an example, the first configuration information includes a ra-PreambleIndex, which indicates the first RA sequence.

[0552] As an example, the first configuration information includes a FrequencyInfoUL-SIB, which indicates the basic parameters of an uplink carrier of the first cell.

[0553] As one embodiment, the first configuration information includes a SubcarrierSpacing, which indicates the subcarrier spacing of the PRACH.

[0554] As one embodiment, the first configuration information includes a ULSubcarrierSpacing, which indicates the subcarrier spacing of the PRACH.

[0555] As an example, the first configuration information includes an absoluteFrequencyPointA, which indicates the location of PointA.

[0556] As an example, the WUS configuration includes second configuration information, which configures the SSB of the second cell.

[0557] As one example, the second configuration information includes SIB1-RequestConfig-r19.

[0558] As an example, the name of the second configuration information is SIB1-RequestConfig-r19.

[0559] As one embodiment, the second configuration information includes an ss-PBCH-BlockPower, which indicates the average EPRE (Energy per resource element) of the REs (resource elements) carrying SSS (secondary synchronization signals) used by the first cell for SSB transmission. This method helps the first node U01B determine the transmit power of the first RA sequence.

[0560] As an example, the second configuration information includes an ssb-PositionsInBurst, which indicates the time domain positions of the SSB of the first cell.

[0561] As an example, the second configuration information includes an ssb-Periodicity.

[0562] As one embodiment, the second configuration information includes a SubcarrierSpacing, which indicates the subcarrier spacing of the SSB.

[0563] As an example, the first RRC message and the WUS configuration are two different RRC messages.

[0564] As an example, during the RRC connection re-establishment process, the first node starts the first timer.

[0565] As an example, step S5103 is optional.

[0566] As an example, if the first node is not configured with the second timer, step S5103 does not exist.

[0567] As an example, if the second timer is not turned on, step S5103 does not exist.

[0568] As an example, step S5103 is present.

[0569] As an example, during the RRC connection re-establishment process, the first node starts the second timer.

[0570] As an example, when the first node starts the second timer, the first timer is stopped.

[0571] As an example, when the first node starts the second timer, the first timer is paused.

[0572] As an example, when the first node starts the second timer, the first timer is started.

[0573] As an example, when the first node starts the second timer, the first timer continues to run.

[0574] As an example, the second timer is activated only when the first timer expires.

[0575] As an example, once the second timer is started, the first timer is considered invalid.

[0576] As an example, during the RRC connection re-establishment process, the first node starts the first timer and the second timer.

[0577] As one example, starting the second timer depends on the first node having a WUS configuration.

[0578] As one example, the WUS configuration includes the configuration of the second timer.

[0579] As an example, an RRC reconfiguration message includes the configuration of the second timer.

[0580] As an example, when the first node has a WUS configuration, the second timer is started during the RRC connection re-establishment process.

[0581] As an example, in step S5104, the first node determines whether to perform the action of switching to RRC_IDLE at the first time: if the first node does not have WUS configuration, the action of switching to RRC_IDLE is performed at the first time; if at least the first node has WUS configuration, the action of switching to RRC_IDLE is not performed at the first time.

[0582] As an example, the first node needs to determine whether to execute the action of switching to RRC_IDLE at the first time, only when the first node has WUS configuration.

[0583] As an example, if the first node is configured with a second timer, and the second timer is running at the first time, the action of transitioning to RRC_IDLE is not performed at the first time.

[0584] As an example, if the first timer is running at the first time, the action of transitioning to RRC_IDLE is not performed at the first time; wherein the value of the first timer is not the first time length.

[0585] As an example, if the first timer expires at the first moment and the WUS configuration is being applied, the action of switching to RRC_IDLE is not performed at the first moment.

[0586] As an example, if the first node does not have a WUS configuration, the first node does not need to determine whether to execute the action when switching to RRC_IDLE at the first time.

[0587] Example 6A

[0588] Example 6A illustrates a schematic diagram of the first information block including a second field according to another embodiment of this application, as shown in Figure 6A.

[0589] For the first node U01A, in step S6101A, if the first message includes the WUS configuration of the second cell; in step S6102A, the first node initiates the random access procedure on the second cell; in step S6103A, along with initiating the random access procedure on the second cell, the first information block includes a second field.

[0590] In embodiment 6A, the second field indicates the random access information of the second cell; wherein the random access information of the second cell depends on the first message including the WUS configuration of the second cell.

[0591] As an example, the initiation of the random access procedure on the second cell depends on the application of the WUS configuration of the second cell.

[0592] As one embodiment, in response to the application of the WUS configuration of the second cell, the random access procedure is initiated on the second cell; in response to the initiation of the random access procedure on the second cell, a second field is included in the first information block.

[0593] As an example, the WUS configuration information of the second cell is applied to initiate the random access procedure on the second cell, and in response to initiating the random access procedure on the second cell, the first information block includes a second field.

[0594] As an example, if the first message includes the WUS configuration of the second cell, and the random access procedure is initiated on the second cell, the first information block includes a second field indicating the random access information of the second cell; wherein the random access procedure is for requesting the SIB1 of the second cell.

[0595] As an example, the random access information of the second cell comes from the WUS configuration of the second cell.

[0596] As an example, part of the random access information of the second cell comes from the WUS configuration of the second cell.

[0597] As an example, in response to initiating the random access procedure on the second cell, the first information block includes a second field indicating information initiating the random access procedure on the second cell.

[0598] As an example, when the WUS configuration information of the second cell is applied, the first information block includes a second field.

[0599] As an example, the application of the WUS configuration information of the second cell is completed successfully.

[0600] As an example, the application of the WUS configuration information of the second cell is completed in the following ways: application failure.

[0601] As one example, the second field indicates random access information for multiple cells.

[0602] As one embodiment, the second domain includes at least the random access information of the second cell.

[0603] As an example, the second domain includes the ra-InformationCommon domain.

[0604] As an example, the second field is the ra-InformationCommon field.

[0605] As one embodiment, the second field includes an absoluteFrequencyPointA field, which indicates the absolute frequency of a reference resource block associated with the random access resources used in the random access procedure.

[0606] As one embodiment, the second field includes a SubcarrierSpacing field, wherein the SubcarrierSpacing indicates the subcarrier spacing of the UL BWP used.

[0607] As one embodiment, the second field includes an ssb-Index field, which indicates the selected SSB.

[0608] As one embodiment, the second field includes a raPurpose field, which indicates the purpose for initiating the random access procedure.

[0609] As a sub-implementation, raPurpose is a first value, which indicates SIB1.

[0610] As a sub-implementation, the first value of raPurpose indicates that the purpose of triggering the first random access procedure is for SIB1.

[0611] As a sub-example, the first value is a string.

[0612] As a sub-example, the name of the first value includes SIB1.

[0613] As a sub-implementation, the name of the first value is requestForSIB1, requestForOD SIB1, OD SIB1, or ondemandSIB1.

[0614] As a sub-implementation, the raPurpose field indicates requestForOtherSI, and the intendedSIBs indicate that the requested SI is SIB1.

[0615] As an example, the second field indicates whether the random access procedure initiated on the second cell was successful.

[0616] As a sub-implementation, in response to the successful initiation of the random access procedure on the second cell, the second field includes a second indication field, the presence of which indicates that the random access procedure on the second cell was successfully initiated; otherwise, the absence of the second indication field indicates that the random access procedure on the second cell failed to be initiated.

[0617] As an alternative embodiment, the second indication field is set to a third value to indicate that the random access procedure was successfully initiated on the second cell; the second indication field is set to a fourth value to indicate that the random access procedure was failed to be initiated on the second cell.

[0618] As an alternative embodiment, the second indication field indicates that the random access procedure was failed to be initiated on the second cell.

[0619] As a sub-implementation, in response to the successful initiation of the random access procedure on the second cell, the first information block includes a second field indicating the random access information of the second cell.

[0620] As a sub-implementation, if the random access procedure fails to be initiated on the second cell, the second information block is deleted from the first information block.

[0621] As a sub-implementation, a second field is included in the first information block only when the random access procedure fails to be initiated on the second cell. The second field indicates the random access information of the second cell.

[0622] As an example, during the operation of the first timer, in response to initiating a random access procedure in the second cell, a first information block is set in the VarRLF-Report. The first information block logs information for requesting SIB1 of the second cell. The first information block includes a first field indicating the identity information of the second cell and a second field indicating the random access information of the second cell. In this case, the first information block logs information for requesting SIB1 of the second cell when initiating a random access procedure in the second cell.

[0623] As an example, during the operation of the first timer, in response to initiating a random access procedure in the second cell, an rlf-report is set in the VarRLF-Report. The rlf-report includes a first field indicating the identity information of the second cell and a second field indicating the random access information of the second cell. The random access procedure is initiated in the second cell to request SIB1 of the second cell.

[0624] Example 6B

[0625] Example 6B illustrates a schematic diagram of an embodiment of the present application in which the first time length and the second time length are configured to the first timer, as shown in Figure 6B.

[0626] In step S6101B, it is determined whether the first node has a WUS configuration. If the first node does not have a WUS configuration, proceed to step S6103aB. In step S6102B, if the first node has a WUS configuration, it is determined whether the first timer uses a first time length. In step S6103aB, if the first timer uses the first time length, the action of switching to RRC_IDLE is executed during the first time. In step S6103bB, if the first timer uses the second time length, the action of switching to RRC_IDLE is not executed during the first time.

[0627] In Example 6B, the first RRC message configures the second time length; both the first time length and the second time length are configured for the first timer.

[0628] As an example, if the first node does not have a WUS configuration, the first timer uses the first time length; and the action of transitioning to RRC_IDLE is performed during the first time.

[0629] As an example, as long as the first node does not have a WUS configuration, the first timer uses the first time length; and the action of transitioning to RRC_IDLE is performed during the first time.

[0630] As an example, the first timer using the first time length means that the value of the first timer is the first time length.

[0631] As an example, the first timer using the first time length means that the value of the first timer is optional, and the value of the first timer is selected from the first time length.

[0632] As an example, the first timer expires at the first time; wherein the first timer uses the first time length.

[0633] As an example, in response to the expiration of the first timer at the first time, the action of transitioning to RRC_IDLE is performed at the first time.

[0634] As an example, if the first node has a WUS configuration, the first timer uses the second time length; the action of transitioning to RRC_IDLE is not performed during the first time.

[0635] As an example, the first timer using the second time length means that the value of the first timer is the second time length.

[0636] As an example, the first timer using the second time length means that the value of the first timer defaults to the second time length.

[0637] As an example, the first timer using the second time length means that the value of the first timer is optional, and the value of the first timer is selected to be the second time length.

[0638] As an example, the first time is the end time of the first time length, and the action of switching to RRC_IDLE is not performed during the first time; wherein, the first timer adopts the second time length.

[0639] As an example, the first timer did not expire at the first time.

[0640] As an example, the first timer is running at the first time.

[0641] As one example, the second time length is longer than the first time length.

[0642] As an example, the unit of the first time length is ms.

[0643] As an example, the unit of the first time length is seconds (s).

[0644] As an example, the first time length is a non-negative integer.

[0645] As an example, the first time length is optional.

[0646] As an example, the first time length is fixed.

[0647] As an example, the unit of the second time length is ms.

[0648] As an example, the unit of the second time length is seconds (s).

[0649] As an example, the second time length is a non-negative integer.

[0650] As one embodiment, the second time length is optional.

[0651] As one example, the second time length is fixed.

[0652] As an example, configuring the second time length in the first RRC message means that the first RRC message includes both the second time length and the first time length.

[0653] As an example, configuring the second time length in the first RRC message means configuring the second time length and the first time length in the first RRC message for the first timer.

[0654] As an example, configuring the second time length in the first RRC message means configuring the second time length in the first RRC message for the first timer.

[0655] As an example, configuring the second time length in the first RRC message means configuring one of the values ​​of the first timer in the first RRC message as the second time length.

[0656] As an example, the first RRC message configures the second time length as long as the first node has WUS configuration.

[0657] As an example, the first RRC message configures the second time length along with the WUS configuration.

[0658] As an example, the first RRC message includes the WUS configuration, which includes the second time length.

[0659] As one embodiment, the first RRC message includes the WUS configuration, and in response to the first RRC message including the WUS configuration, the WUS configuration includes the second time length.

[0660] As an example, as long as the first node has a WUS configuration, the first timer adopts the second time length; the action of switching to RRC_IDLE is not performed during the first time.

[0661] As an example, when the first node has a WUS configuration, the first timer uses the second time length; the action of switching to RRC_IDLE is not performed during the first time.

[0662] As an example, once the first node has a WUS configuration, the first timer adopts the second time length; the action of transitioning to RRC_IDLE is not performed during the first time.

[0663] As an example, if the first node does not have a WUS configuration, the first timer is configured with the first time length; if the first node has a WUS configuration, the first timer is configured with the second time length.

[0664] As an example, if the first node does not have a WUS configuration, the first timer is configured with the first time length; if the first node has a WUS configuration, the first timer is configured with both the first time length and the second time length.

[0665] As an example, as long as the first node has a WUS configuration, the first timer is configured with the first time length and the second time length.

[0666] As an example, if the first node has a WUS configuration and the WUS configuration is applied during the first timer's operation, the first timer uses the second time length; the action of transitioning to RRC_IDLE is not performed during the first time.

[0667] As an example, when the first node has a WUS configuration and the WUS configuration is being applied at the first time; the first timer uses the second time length; the action of switching to RRC_IDLE is not performed at the first time.

[0668] As an example, during the RRC connection re-establishment process, if the first node does not have a WUS configuration, the value of the first timer adopts a first time length; if the first node has a WUS configuration, the value of the first timer adopts a second time length.

[0669] As an example, during the RRC connection re-establishment process, if the first node does not have a WUS configuration, the value of the first timer is a first time length; if the first node has a WUS configuration but the WUS configuration is not applied, the value of the first timer is a first time length.

[0670] As an example, during the RRC connection re-establishment process, if the first node does not have a WUS configuration, the value of the first timer is a first time length; if the first node has a WUS configuration and the WUS configuration is applied, the value of the first timer is a second time length.

[0671] As an example, during the RRC connection re-establishment process, the value of the first timer adopts a first time length; if the WUS configuration is being applied during the first time, the value of the first timer adopts a second time length; the action of switching to RRC_IDLE is not performed during the first time.

[0672] As an example, the WUS configuration is not applied during the first time period, and the first timer uses a first time length.

[0673] As an example, during the RRC connection re-establishment process, the first timer uses the first time length; during the first time, if the WUS configuration is applied, the value of the first timer is the sum of the second time length and the first time length.

[0674] As an example, during the RRC connection re-establishment process, the first timer uses the sum of the second time length and the first time length; wherein, the first time is the end time of the first time length.

[0675] As an example, regardless of whether the first node has the WUS configuration, the first timer is configured with a first time length and a second time length.

[0676] As an example, if the first node does not have the WUS configuration, the first timer uses a first value; if the first node has the WUS configuration, the first timer uses a second value.

[0677] As an example, the first value is the first time length.

[0678] As an example, the second value is the second time length.

[0679] As an example, the first value is the difference between the first time length and the second time length.

[0680] As an example, the second value is the sum of the first time length and the second time length.

[0681] As an example, the second time length is independent of the first time length.

[0682] Example 7A

[0683] Example 7A illustrates a schematic diagram of the first time interval according to an embodiment of the present application, as shown in Figure 7A.

[0684] In Embodiment 7A, as the random access procedure initiated on the second cell is completed, the first information block includes a first time interval; wherein the start time of the first time interval depends on the time when the first node experiences a wireless connection failure.

[0685] As an example, if the random access procedure is successfully initiated on the second cell, the first time interval is included in the first information block.

[0686] As an example, when the random access procedure is successfully initiated on the second cell, the first time interval is included in the first information block.

[0687] As an example, in response to the successful request for SIB1 of the second cell, the first time interval is included in the first information block.

[0688] As an example, the successful request for SIB1 of the second cell means that SIB1 is successfully received within the first time window.

[0689] As an example, the successful request for SIB1 of the second cell means that the random access procedure initiated on the second cell is successful.

[0690] As an example, the successful initiation of the random access procedure on the second cell means the successful receipt of the MAC RAR message.

[0691] As an example, the successful initiation of the random access procedure on the second cell means that SIB1 is successfully received within the first time window.

[0692] As an example, the successful initiation of the random access procedure on the second cell means that the cell is selected to be the second cell.

[0693] As a sub-example, the cell selection to the second cell means that the triggering condition of the UL-WUS configuration of the second cell is met.

[0694] As a sub-example, the triggering conditions of the UL-WUS configuration are default.

[0695] As a sub-example, the triggering conditions of the UL-WUS configuration are configured in the WUS configuration of the second cell.

[0696] As a sub-example, the triggering condition for the UL-WUS configuration is the cell selection condition.

[0697] As a sub-example, the triggering condition for the UL-WUS configuration is the cell reselection condition.

[0698] As a sub-example, the triggering conditions of the UL-WUS configuration are stored in the first node.

[0699] As a sub-example, the cell selection to the second cell refers to the occurrence of the first RA sequence in the second cell.

[0700] As an example, the successful initiation of the random access procedure on the second cell refers to the time when the first timer is stopped.

[0701] As an example, in response to the successful initiation of the random access procedure on the second cell, the first information block includes a first time interval, which indicates the time interval between the time when the first timer is started and the time when the first timer is stopped.

[0702] As one embodiment, the first time interval is used to indicate the time interval between the time when the first node experiences a wireless connection failure and the time when the first timer stops.

[0703] As an example, the first time interval is used to indicate the time interval between the time when the first node experiences a wireless connection failure and the time when the random access procedure is successfully completed.

[0704] As a sub-implementation, the first time interval is used to indicate the time interval between the time when the first node experiences a wireless connection failure and the time when it successfully receives the MAC RAR.

[0705] As a sub-implementation, the first time interval is used to indicate the time interval between the time when the first node experiences a wireless connection failure and the time when SIB1 is successfully received within the first time window.

[0706] As a sub-implementation, the first time interval is used to indicate the time interval from the time when the first node experiences a wireless connection failure to the time when the cell is selected to the second cell.

[0707] As an example, the first time interval is used to indicate the time interval between the time from the selection of the second cell to the time when the random access procedure is successfully completed.

[0708] As an example, the first time interval is used to refer only to the time interval between the time when the WUS configuration of the second cell is applied and the time when the random access procedure is successfully completed.

[0709] As an example, the name of the first time interval includes "time".

[0710] As an example, the name of the first time interval includes NES.

[0711] As an example, the name of the first time interval includes OD-SIB1.

[0712] As an example, the name of the first time interval includes WUS.

[0713] As an example, the name of the first time interval includes UL-WUS.

[0714] As an example, the name of the first time interval includes timeSinceWUS-config.

[0715] As an example, the unit of the first time interval is seconds.

[0716] As an example, the first time interval is a non-negative integer.

[0717] As an example, the first time interval is a positive integer.

[0718] As an example, if the random access procedure fails to be initiated on the second cell, the first time interval is not set in the first information block.

[0719] Example 7B

[0720] Example 7B illustrates a schematic diagram of configuring a first timer and a second timer in the first RRC message according to an embodiment of this application, as shown in Figure 7B.

[0721] In step S7101B, it is determined whether the first node has a WUS configuration. If the first node does not have a WUS configuration, proceed to step S7103aB. In step S7102B, if the first node has a WUS configuration, it is determined whether to use the first timer. In step S7103aB, if the first node uses the first timer, the action of transitioning to RRC_IDLE is executed at the first time. In step S7103bB, if the first node uses the second timer, the action of transitioning to RRC_IDLE is not executed at the first time.

[0722] In Example 7B, the first RRC message configures the first time length to the first timer; the first RRC message configures the second time length to the second timer.

[0723] As an example, if the first node does not have a WUS configuration, during the RRC connection re-establishment process, the first timer is started, and the action of transitioning to RRC_IDLE is performed at the first time; wherein, the first time is the time when the first timer expires.

[0724] As an example, the first timer is used for the RRC connection re-establishment process.

[0725] As an example, the first timer is started once the RRC connection re-establishment process is initiated.

[0726] As an example, when the first timer expires, the action of transitioning to RRC_IDLE is performed.

[0727] As an example, if the first node has a WUS configuration, the second timer is started during the RRC connection re-establishment process, and the action of transitioning to RRC_IDLE is not performed during the first time; wherein, the first time is the end time of the first time length.

[0728] As one example, the configuration of the second timer depends on the first node having a WUS configuration.

[0729] As an example, if the first node has a WUS configuration, the second timer is used for the RRC connection re-establishment process.

[0730] As an example, if the first node has a WUS configuration, the second timer is considered valid.

[0731] As an example, if the first node has a WUS configuration, the second timer is activated.

[0732] As an example, the second timer is considered valid once the first node receives the WUS configuration.

[0733] As an example, the second timer is activated once the first node receives the WUS configuration.

[0734] As an example, the second timer is T311a.

[0735] As one embodiment, the second timer is a timer other than T311 for the RRC connection re-establishment process.

[0736] As an example, if the first node does not have WUS configuration, the first timer is started during the RRC connection re-establishment process, and the action of switching to RRC_IDLE is performed at the first time; if the first node has WUS configuration, the first timer and the second timer are started during the RRC connection re-establishment process, and the action of switching to RRC_IDLE is not performed at the first time; wherein, the first time is the time when the first timer expires.

[0737] As an example, if the second timer is running at the first time, the action of transitioning to RRC_IDLE is not performed at the first time.

[0738] As an example, if the first node does not have WUS configuration, the first timer is started during the RRC connection re-establishment process, and the action of switching to RRC_IDLE is performed at the first time; if the first node has WUS configuration, the first timer is started during the RRC connection re-establishment process; at the first time, if the WUS configuration is being applied, the second timer is started, and the action of switching to RRC_IDLE is not performed at the first time; wherein, the first time is the time when the first timer expires.

[0739] As an example, if the first node does not have WUS configuration, the first timer is started during the RRC connection re-establishment process, and the action of switching to RRC_IDLE is performed at the first time; if the first node has WUS configuration, the second timer is started during the RRC connection re-establishment process, and the action of switching to RRC_IDLE is not performed at the first time; wherein, the first time is the end time of the first time length.

[0740] As an example, if the first node has a WUS configuration, the first RRC message includes a first timer and a second timer; the first RRC message configures the first time length to the first timer; the first RRC message configures the second time length to the second timer.

[0741] As an example, if the first node does not have a WUS configuration, the first RRC message includes the first timer; the first RRC message configures the first time length to the first timer; if the first node has a WUS configuration, the first RRC message includes the second timer; the first RRC message configures the second time length to the second timer.

[0742] Example 8A

[0743] Example 8A illustrates a schematic diagram of the first information block according to this application including a third field, as shown in Figure 8A.

[0744] For the first node U01A, in step S8101A, if the first message includes the WUS configuration of the second cell; in step S8102A, the request for the SIB1 of the second cell fails; in step S8103A, as a response to the failure of the request for the SIB1 of the second cell, a third field is set in the first information block.

[0745] In Example 8A, the third field indicates that the request for SIB1 of the second cell has failed.

[0746] As an example, the failure to request SIB1 of the second cell includes: not receiving scheduling signaling triggered by the first RA sequence.

[0747] As an example, the scheduling signaling is a DCI (Downlink Control Information).

[0748] As a sub-implementation, the CRC (Cyclic Redundancy Check) of the DCI is scrambled by a RA-RNTI (Radio Network Temporary Identifier), which is calculated based on the time-frequency resources occupied by the first RA sequence.

[0749] As a sub-implementation, the DCI is used to schedule MAC RAR.

[0750] As a sub-example, the MAC RAR (Random Access Response) includes a MAC subPDU, which includes the Random Access Preamble identifier corresponding to the first RA sequence.

[0751] As a sub-example, the MAC RAR includes a MAC subPDU that carries only a RAPID, the RAPID indicating the first RA sequence.

[0752] As a sub-implementation, the DCI is used to schedule SIB1.

[0753] As a sub-example, the CRC of the DCI is scrambled by an SI-RNTI, where the SI-RNTI is a fixed value.

[0754] As an example, the failure to request SIB1 of the second cell includes: not receiving a MAC RAR message triggered by the first RA sequence.

[0755] As an example, the failure to request SIB1 of the second cell includes: not receiving the scheduled SIB1 within the first time window.

[0756] As an example, the failure to request SIB1 of the second cell includes receiving an invalid SIB1.

[0757] As an example, the invalid SIB1 is not the SIB1 of the second cell.

[0758] As an example, the invalid SIB1 refers to an incorrect SIB1.

[0759] As an example, in response to the failure of the request for SIB1 of the second cell, the second cell is considered to be barred.

[0760] As an example, in response to the failure of the request for SIB1 in the second cell, cell selection is not performed in the second cell for a period of time.

[0761] As a sub-example, the time period is 300 seconds.

[0762] As a sub-example, the time period is a maximum of 300 seconds.

[0763] As an example, in response to the failure of the request for SIB1 of the second cell, the first information block indicates that the request for SIB1 of the second cell has failed.

[0764] As an example, the third field includes the identity information of the second cell indicating that the request for SIB1 of the second cell failed.

[0765] As an example, the name of the third domain includes OD-SIB1.

[0766] As an example, the name of the third field includes Failure.

[0767] As an example, the name of the third domain includes WUS.

[0768] As an example, the value of the third field is set to true to indicate that the request for SIB1 of the second cell has failed.

[0769] As an example, setting the value of the third field to false indicates that the request for SIB1 of the second cell failed.

[0770] As an example, the presence of the third field indicates that the request for SIB1 of the second cell has failed.

[0771] As an example, when the first timer expires, noSuitableCellFound is set to true.

[0772] As an example, when the first timer expires, noSuitableCellFound is set to true in the first information block.

[0773] As an example, during the operation of the first timer, the request for SIB1 of the second cell fails; when the first timer expires, noSuitableCellFound is set to true and the first information block includes a third field indicating that the request for SIB1 of the second cell failed during the operation of the first timer.

[0774] As an example, when the first timer expires, the request for SIB1 of the second cell fails, noSuitableCellFound is set to true, and the first information block includes a third field indicating that the request for SIB1 of the second cell failed during the operation of the first timer.

[0775] As a sub-example, the failure to request SIB1 of the second cell when the first timer expires means that the process of requesting SIB1 of the second cell is in progress when the first timer expires.

[0776] As a sub-example, when the first timer expires, the failure to request SIB1 of the second cell means that when the first timer expires, the first node enters the RRC_IDLE state.

[0777] As a sub-example, if the process of requesting SIB1 of the second cell is in progress when the first timer expires, the process of requesting SIB1 of the second cell is terminated and the request for SIB1 of the second cell is considered to have failed.

[0778] As an example, during the execution of the first timer, in response to initiating a random access procedure in the second cell, a first information block is set in the VarRLF-Report. The first information block logs information for requesting SIB1 of the second cell. The first information block includes a first field indicating the identity information of the second cell and a second field indicating the random access information of the second cell. Specifically, when initiating a random access procedure in the second cell to request SIB1 of the second cell, the first information block logs information for requesting SIB1 of the second cell. In response to the expiration of the first timer, the first information block includes a third field indicating that the request for SIB1 of the second cell failed during the execution of the first timer.

[0779] As an example, in response to the expiration of the first timer, the first field and the second field in the first information block are deleted.

[0780] As an example, in response to the expiration of the first timer, the first and second fields in the first information block are deleted, and the first information block includes a third field indicating that the request for SIB1 of the second cell failed during the operation of the first timer.

[0781] Example 8B

[0782] Example 8B illustrates a schematic diagram of the first timer being paused according to an embodiment of the present application, as shown in Figure 8B.

[0783] In step S8101B, it is determined whether the first node has a WUS configuration. If the first node does not have a WUS configuration, proceed to step S8103aB. In step S8102B, if the first node has a WUS configuration, it is determined whether the first timer is paused. In step S8103aB, if the first timer is not paused, the action of transitioning to RRC_IDLE is executed at the first time. In step S8103bB, if the first timer is paused, the action of transitioning to RRC_IDLE is not executed at the first time.

[0784] In Example 8B, if at least the first node has a WUS configuration, the action of not performing the transition to RRC_IDLE at the first time depends on the first timer being paused.

[0785] As an example, if the first node has a WUS configuration and the first timer is paused, the action of transitioning to RRC_IDLE is not performed during the first time.

[0786] As one embodiment, pausing the first timer includes: pausing the first timer at a first time; wherein the first time is the time when the first timer expires, and the first time length is configured for the first timer.

[0787] As an example, the first timer is paused during the first time to determine whether the WUS configuration is being applied; wherein, the first time is the end time of the first time length.

[0788] As an example, the first timer uses the first time length, where the first time is the time the first timer expires; during the first time, the first timer is paused to determine whether the WUS configuration is being applied; if the WUS configuration is being applied, the action of switching to RRC_IDLE is not performed; if the WUS configuration is not being applied, the action of switching to RRC_IDLE is performed.

[0789] As an example, not performing the action when switching to RRC_IDLE includes: continuing to apply the WUS configuration.

[0790] As an example, not performing the action when transitioning to RRC_IDLE includes: not stopping the first timer.

[0791] As an example, the action of not performing the transition to RRC_IDLE includes: the first timer adopting the second time length.

[0792] As an example, the action of not performing the transition to RRC_IDLE includes: starting the second timer.

[0793] As an example, not performing the action when transitioning to RRC_IDLE includes: continuing to run the second timer.

[0794] As an example, the action of not performing the transition to RRC_IDLE includes: not releasing at least the WUS configuration.

[0795] As one embodiment, pausing the first timer includes: pausing the first timer at a second time depends on the WUS configuration being applied; wherein the second time is the time when the WUS configuration is applied, and the second time is during the operation of the first timer; the first time length is configured for the first timer.

[0796] As an example, once the WUS configuration is applied, the first timer is paused at the second time.

[0797] As an example, when the WUS configuration is applied, the first timer is paused during the second time.

[0798] As an example, when at least the WUS configuration is applied, the first timer is paused during the second time.

[0799] As an example, the first timer is stopped once the WUS configuration has been successfully applied.

[0800] As an example, the first timer is stopped when the WUS configuration is successfully applied.

[0801] As an example, the first timer is stopped when at least the WUS configuration has been successfully applied.

[0802] As an example, when the first timer is stopped, the first timer has not expired.

[0803] As an example, the first timer continues to run once the WUS configuration fails to be applied.

[0804] As an example, the first timer continues to run when the WUS configuration fails to be applied.

[0805] As an example, the first timer continues to run even when at least the WUS configuration fails to be applied.

[0806] As an example, if the WUS configuration fails to be applied and the first timer has not expired, the first timer continues to run.

[0807] As an example, if the first node has a WUS configuration, the first timer uses a duration other than the first time; when the first timer uses a duration other than the first time, the first timer can be paused.

[0808] As an example, the non-first time length is the second time length.

[0809] As an example, the non-first time length is for the WUS configuration.

[0810] As an example, if the first node does not have a WUS configuration, the action of transitioning to RRC_IDLE at the first time depends on the first timer not being paused.

[0811] As an example, the first timer is not allowed to be paused when the first node does not have a WUS configuration.

[0812] As an example, when the first timer is in the first time length, the first timer is not allowed to be paused.

[0813] As an example, the first timer is T311, and the first timer is not allowed to be paused.

[0814] As one embodiment, the first timer is paused during a first process; wherein the first process includes sending an RA sequence, the WUS configuration indicating the RA sequence.

[0815] As one embodiment, the first process includes selecting a suitable NES cell, and the WUS configuration includes the configuration information of the suitable NES cell.

[0816] Example 9A

[0817] Example 9A illustrates a schematic diagram of the fourth field indicating the triggering conditions of the second cell according to yet another embodiment of this application.

[0818] In Example 9A, as a response to the failure of the request for SIB1 of the second cell, a fourth field is set in the first information block, the fourth field indicating the triggering condition of the second cell.

[0819] As an example, the WUS configuration of the second cell includes the triggering conditions of the second cell.

[0820] As an example, the triggering condition for the second cell is the cell selection condition of the second cell.

[0821] As a sub-example, the cell selection criterion is the S criterion.

[0822] As a sub-example, the WUS configuration of the second cell includes a connEstFailureControl field, which indicates the S criterion parameter Qoffsettemp.

[0823] As a sub-example, the WUS configuration of the second cell includes a connEstFailOffset field, which indicates the S criterion parameter Qoffsettemp.

[0824] As a sub-example, the WUS configuration of the second cell includes a q-RxLevMin field, which indicates the S criterion parameter Qrxlevmin.

[0825] As a sub-example, the WUS configuration of the second cell includes a q-RxLevMinOffset field, which indicates the S criterion parameter Qrxlevminoffset.

[0826] As a sub-example, the WUS configuration of the second cell includes a q-QualMin field, which indicates the S criterion parameter Qqualmin.

[0827] As a sub-example, the WUS configuration of the second cell includes a q-QualMinOffset field, which indicates the S criterion parameter Qqualminoffset.

[0828] As an example, the triggering condition for the second cell is the cell reselection condition of the second cell.

[0829] As an example, the triggering conditions for the second cell are configured by the network.

[0830] As an example, the triggering condition for the second cell is specific to the second cell.

[0831] As one example, the triggering condition of the second cell depends on the stored information of the first node.

[0832] As one example, the information stored by the first node includes the frequency information of the first cell.

[0833] As an example, the frequency of the second cell is the same as that of the first cell.

[0834] As an example, the PLMN (Public Land Mobile Network) of the second cell is the same as that of the first cell.

[0835] As one example, the fourth domain includes the triggering conditions of the second cell.

[0836] As an example, the fourth domain includes the S criterion parameter in the WUS configuration of the second cell.

[0837] As an example, during the operation of the first timer, the request for SIB1 of the second cell fails; when the first timer expires, a fourth field is set in the first information block, the fourth field indicating the triggering condition of the second cell.

[0838] As an example, when the first timer expires, if the process of requesting the SIB1 of the second cell is in progress, the process of requesting the SIB1 of the second cell is stopped, and the process of requesting the SIB1 of the second cell is considered to have failed. As a response to the failure of the request for the SIB1 of the second cell, a fourth field is set in the first information block, and the fourth field indicates the triggering condition of the second cell.

[0839] As an example, when the first timer expires, if the SIB1 request for the second cell is in progress, wait for the SIB1 request for the second cell to be completed, and as a response to the failure of the SIB1 request for the second cell, set a fourth field in the first information block, the fourth field indicating the triggering condition of the second cell.

[0840] As an example, during the operation of the first timer, the request for SIB1 of the second cell fails; when the timer T311 expires, noSuitableCellFound is set to true and a third field is set to indicate that the request for SIB1 of the second cell failed during the operation of the first timer; a fourth field is set in the first information block, the fourth field indicating the triggering condition of the second cell.

[0841] As an example, when the first timer expires, if the process of requesting SIB1 for the second cell is in progress, the process of requesting SIB1 for the second cell is stopped, and the request for SIB1 for the second cell is considered to have failed. As a response to the failure of the request for SIB1 for the second cell, noSuitableCellFound is set to true and a third field is set to indicate that the request for SIB1 for the second cell failed during the operation of the first timer. A fourth field is set in the first information block, and the fourth field indicates the triggering condition of the second cell.

[0842] As an example, when the first timer expires, if the SIB1 request for the second cell is in progress, wait for the SIB1 request for the second cell to be completed. As a response to the failure of the SIB1 request for the second cell, set noSuitableCellFound to true and set a third field to indicate that the SIB1 request for the second cell failed during the first timer's operation; set a fourth field in the first information block, the fourth field indicating the triggering condition of the second cell.

[0843] Example 9B

[0844] Example 9B illustrates a schematic diagram of the WUS configuration being applied at the first moment according to an embodiment of this application, as shown in Figure 9B.

[0845] In step S9101B, it is determined whether the first node has a WUS configuration. If the first node does not have a WUS configuration, proceed to step S9103aB. In step S9102B, if the first node has a WUS configuration, it is determined whether the WUS configuration is being applied at the first time. In step S9103aB, if the WUS configuration is not being applied at the first time, the action of transitioning to RRC_IDLE is performed at the first time. In step S9103bB, if the WUS configuration is being applied at the first time, the action of transitioning to RRC_IDLE is not performed at the first time.

[0846] In Example 9B, if at least the first node has a WUS configuration, the action of not performing the transition to RRC_IDLE at the first time depends on the WUS configuration being applied at the first time.

[0847] As an example, if the first node has a WUS configuration and the WUS configuration is being applied at the first time, the action of not performing the transition to RRC_IDLE is not executed at the first time, where the first time is the time when the first timer expires.

[0848] As an example, the WUS configuration being applied means that the cell selects an NES cell whose configuration belongs to the WUS configuration.

[0849] As an example, the application of WUS configuration means that the first process is in progress, and the first process is a random access process.

[0850] As an example, the WUS configuration being applied means that the first process is in progress, and the first process is the process of obtaining SIB1.

[0851] As an example, the WUS configuration being applied means that the third timer is running for the application of the WUS configuration.

[0852] As an example, the third timer is started when a cell selects an NES cell.

[0853] As an example, the third timer is not the second timer.

[0854] As an example, the third timer is configured for the WUS.

[0855] As an example, if the first node has a WUS configuration and the WUS configuration is being applied at the first time, the first node waits for the WUS configuration to be applied completely.

[0856] As an example, the completion of the WUS configuration application includes: the WUS configuration being successfully applied.

[0857] As an example, the application of the WUS configuration is completed including: the application of the WUS configuration is failed.

[0858] As an example, the successful application of the WUS configuration means that the random access procedure is completed.

[0859] As an example, successful application of the WUS configuration means that the SIB1 of the selected NES cell is successfully obtained.

[0860] As an example, the successful application of the WUS configuration means that the first process is completed.

[0861] As an example, in response to the successful application of the WUS configuration, the RRC connection re-establishment process is considered to have been successfully completed.

[0862] As an example, in response to the successful application of the WUS configuration, the first node does not perform the action of transitioning to RRC_IDLE.

[0863] As an example, in response to the successful application of the WUS configuration, the first node does not consider the first timer to have expired.

[0864] As an example, the WUS configuration failure to apply means that the third timer expires.

[0865] As an example, the WUS configuration failure application means that the first process is aborted.

[0866] As an example, the WUS configuration failure application refers to SIB1 not obtaining the selected NES cell.

[0867] As an example, the WUS configuration failure application refers to an NES cell that has not recovered to the WUS configuration.

[0868] As an example, in response to the failure of the WUS configuration application, the RRC connection re-establishment process is considered to have failed, and the action of transitioning to RRC_IDLE is executed.

[0869] As an example, if the first node has a WUS configuration, but the WUS configuration is not being applied at the first time, the action of switching to RRC_IDLE is performed at the first time.

[0870] As an example, the WUS configuration not being applied at the first time means that the NES cell was not selected at the first time.

[0871] As an example, the WUS configuration not being applied at the first time means that the second timer is not running at the first time.

[0872] As an example, "the WUS configuration is not being applied at the first time" means that the first node does not have a valid WUS configuration at the first time.

[0873] As an example, whether the first node has a valid WUS configuration depends on the first node itself to determine.

[0874] As an example, the first node not having a valid WUS configuration means that the time for which the WUS configuration is not valid exceeds a first time threshold.

[0875] As an example, the first time threshold is fixed.

[0876] As an example, the unit of the first time threshold is hours.

[0877] As an example, the first time threshold is 48 hours.

[0878] As an example, the first time threshold is 24 hours.

[0879] As an example, the first time threshold is configured by the network.

[0880] As an example, the first node not having a valid WUS configuration means that the configured cell of the WUS configuration is not the currently serving cell.

[0881] As an example, the first node not having a valid WUS configuration means that the NES cell of the WUS configuration is not selected.

[0882] As an example, "the WUS configuration is not being applied at the first time" means that the WUS configuration failed to be applied before the first time.

[0883] Example 10A

[0884] Example 10A illustrates a schematic diagram of setting a second information block in VarRA-Report according to another embodiment of the present application, as shown in Figure 10A.

[0885] In embodiment 10A, along with sending the first RA sequence, a second information block is set in the VarRA-Report; wherein, the second information block indicates that the WUS configuration of the second cell is applied; the second information block includes at least a first field, the first field indicating the identity information of the second cell.

[0886] As an example, the first message includes the WUS configurations of the third cell and the second cell.

[0887] As an example, the first message includes the WUS configuration of at least the third cell and the second cell.

[0888] As an example, the non-RRC_CONNECT state means that no timer is running.

[0889] As an example, the non-RRC_CONNECT state refers to the RRC_IDLE state.

[0890] As an example, the non-RRC_CONNECT state refers to the RRC_INACTIVE state.

[0891] As an example, the non-RRC_CONNECT state refers to either the RRC_INACTIVE state or the RRC_IDLE state.

[0892] As an example, when the first node receives RRC dedicated signaling on the first cell, it enters a non-RRC_CONNECT state on the first cell.

[0893] As an example, when the first node receives the RRCLease signaling on the first cell, it enters a non-RRC_CONNECT state on the first cell.

[0894] As an example, when the first node fails to execute the RRC connection re-establishment procedure on the first cell, it enters a non-RRC_CONNECT state on the first cell.

[0895] As an example, when the first node receives RRC reconfiguration signaling on the first cell, AS security is not activated, and it enters a non-RRC_CONNECT state on the first cell.

[0896] As an example, the first message is received before the first node enters a non-RRC_CONNECT state on the first cell.

[0897] As an example, the first message is received at least before the first node enters a non-RRC_CONNECT state on the first cell.

[0898] As an example, the first node receives the first message when the first cell is in the RRC_CONNECT state.

[0899] As an example, when the first node enters a non-RRC_CONNECT state, it performs cell reselection; as a response to the cell reselection selecting the second cell, it initiates a random access procedure on the second cell, the random access procedure being to request SIB1 of the second cell.

[0900] As an example, when the first node enters a non-RRC_CONNECT state, it sets a second information block in VarRA-Report as a response to sending the first RA sequence.

[0901] As an example, if the WUS configuration of the second cell is not applied before the first node enters the non-RRC_CONNECT state, a second information block is set in the VarRA-Report in response to sending the first RA sequence.

[0902] As an example, once the first RA sequence is sent, a second information block is set in the VarRA-Report.

[0903] As an example, the second information block is set in VarRA-Report as soon as the first RA sequence is sent.

[0904] As an example, the second information block is ra-Report.

[0905] As one example, the second information block is ra-ReportList.

[0906] As one embodiment, the second information block includes ra-Report.

[0907] As one embodiment, the second information block includes ra-ReportList.

[0908] As an example, setting a second information block in VarRA-Report includes: the second information block includes a first field, the first field indicating the identity information of the second cell.

[0909] As an example, setting a second information block in VarRA-Report includes: the second information block includes a second field, which indicates the random access information of the third cell.

[0910] As an example, in response to the failure of the SIB1 request for the second cell, the second information block is deleted from the VarRA-Report.

[0911] As an example, when the request for SIB1 of the second cell fails, the second information block is deleted from the VarRA-Report.

[0912] As an example, the deletion described in this application refers to removal.

[0913] As an example, the deletion described in this application refers to discarding.

[0914] As an example, the deletion described in this application refers to release.

[0915] As an example, the deletion described in this application refers to clearing.

[0916] Example 10B

[0917] Example 10B illustrates another wireless transmission schematic diagram according to an embodiment of the present application, as shown in Figure 10B.

[0918] For the first node U01B, in step S10101B, the first RA sequence is sent; in step S10102B, the RAR message is received within the first time window; in step S10103, SIB1 is monitored within the second time window; and in step S10104B, SIB1 is received.

[0919] For the third node N03B, in step S10301B, the first RA sequence is received; in step S10302B, a RAR message is sent; and in step S10303B, SIB1 is sent.

[0920] In Example 10B, the WUS configuration being applied at the first time includes: either the first time window or the second time window is running at the first time.

[0921] As an example, the third node N03B is the sustaining base station of the first cell.

[0922] As an example, the third node N03B is not the second node.

[0923] As an example, the first node sends the first RA sequence to the first cell.

[0924] As an example, the first cell and the first RA sequence are associated.

[0925] As an example, the first cell is an NES cell.

[0926] As an example, the first cell is an NES cell configured by the WUS configuration.

[0927] As an example, the first RA sequence is indicated by ra-SIB1PreambleStartIndex in the WUS configuration.

[0928] As an example, the first RA sequence carries a root sequence.

[0929] As an example, the first RA sequence carries a ZC (Zadoff–Chu) sequence.

[0930] As an example, the first RA sequence is a Message 1 (Msg1).

[0931] As an example, the first RA sequence is a UL WUS.

[0932] As an example, the first RA sequence is a preamble, and the first RA sequence is transmitted on PRACH. This method is compatible with existing protocols and reduces the impact of standardization.

[0933] As an example, the first RA sequence is an OOK (On-Off Keying) signal. This method is simple to implement for the first node.

[0934] As an example, the first RA sequence is associated with at least one of the PCI (Physical Cell Identity) or frequency of the first cell.

[0935] As an example, the first node did not receive SIB1 before sending the first RA sequence.

[0936] As an example, the first node does not acquire SIB1 before sending the first RA sequence.

[0937] As an example, the first node did not detect SIB1 before sending the first RA sequence.

[0938] As an example, before sending the first RA sequence, the first node detects whether SIB1 has been sent.

[0939] As a sub-implementation, the first node may detect whether SIB1 has been sent before sending the first RA sequence. This method balances UE power consumption and SIB1 request latency.

[0940] As a sub-implementation, before sending the first RA sequence, the first node needs to, or should, detect whether SIB1 has been sent. This method reduces unnecessary SIB1 requests and lowers UE power consumption.

[0941] As a sub-implementation, before sending the first RA sequence, the first node determines whether SIB1 should be sent. This method improves the flexibility of UE implementation.

[0942] As a sub-example, when the first RA sequence is sent, the first node does not detect that SIB1 has been sent.

[0943] As a sub-example, if the first node does not detect that SIB1 has been sent, the first node assumes that SIB1 has not been broadcast.

[0944] As a sub-implementation, if the first node does not detect that SIB1 has been sent, the first node initiates the first random access procedure.

[0945] As an example, after the first RA sequence is sent, the first node opens the first time window.

[0946] As an example, once the first RA sequence is sent, the first node opens the first time window.

[0947] As an example, the first time window is the Random Access Response time window.

[0948] As an example, the length of the first time window is configured by the ra-ResponseWindow.

[0949] As an example, the first node listens for RAR messages within the first time window.

[0950] As an example, in response to receiving the RAR message in the first time window, the first node considers that SIB1 has been sent.

[0951] As an example, in response to receiving the RAR message in the first time window, the first node considers that SIB1 was sent in the first time window.

[0952] As an example, the first process is considered successful in response to receiving the RAR message in the first time window.

[0953] As an example, the success of the first process means that the random access process is successful.

[0954] As an example, the first process is for performing random access.

[0955] As an example, in response to receiving the RAR message in the first time window, the second time window is opened.

[0956] As an example, when the RAR message is received in the first time window, the second time window is immediately opened.

[0957] As an example, when the first time window receives the RAR message, the second time window is opened after a period of time.

[0958] As an example, the time period is based on the WUS configuration.

[0959] As an example, the time period is the default.

[0960] As an example, the time period is determined automatically by the UE.

[0961] As an example, SIB1 in this application refers to OD(on-demand)-SIB1.

[0962] As an example, SIB1 in this application refers to the SIB1 of the first cell.

[0963] As an example, SIB1 in this application refers to the SIB1 of the NES cell.

[0964] As one example, the length of the second time window is configurable.

[0965] As an example, the length of the second time window is a positive integer number of milliseconds (ms).

[0966] As one example, the length of the second time window is a positive integer number of slots.

[0967] As one example, the length of the second time window depends on the period of SIB1.

[0968] As an example, the length of the second time window is a positive integer number of SIB1 periods.

[0969] As an example, the monitoring of SIB1 includes: monitoring PDCCH (Physical downlink control channel).

[0970] As one example, monitoring SIB1 includes monitoring the PDCCH that schedules SIB1.

[0971] As an example, monitoring SIB1 includes performing monitoring at the time of receiving the PDCCH that schedules SIB1.

[0972] As an example, the monitoring SIB1 includes performing monitoring on the time-frequency resources indicated by pdcch-ConfigSIB1 in the MIB (Master Information Block) message of the first cell.

[0973] As an example, monitoring SIB1 includes receiving a PDSCH (Physical downlink shared channel) carrying SIB1.

[0974] As an example, monitoring SIB1 includes decoding the TB (Transmission Block) carrying SIB1.

[0975] As an example, monitoring SIB1 includes: acquiring SIB1.

[0976] As one embodiment, the monitoring of SIB1 includes: receiving SIB1.

[0977] As one embodiment, the timing of receiving the PDCCH of the scheduling SIB1 is configured by pdcch-ConfigSIB1 in the MIB message of the first cell. This method reduces protocol impact and avoids affecting legitimate (legacy) UEs.

[0978] As an example, the timing of receiving the PDCCH for scheduling SIB1 is indicated by the RAR message. This method is beneficial for dynamically scheduling SIB1.

[0979] As one embodiment, the timing of receiving the PDCCH of the SIB1 scheduling is indicated by the WUS configuration. This method improves the configuration flexibility of SIB1.

[0980] As an example, in response to triggering the first node to send the first RA sequence, a third timer is started.

[0981] As an example, in response to receiving the SIB1 message in the second time window, the third timer is stopped.

[0982] As an example, in response to receiving the SIB1 message in the second time window, the WUS configuration is considered to have been successfully applied.

[0983] As an example, the first process refers to the process of applying the WUS configuration.

[0984] As an example, the first process includes applying the WUS configuration.

[0985] As one embodiment, the first process includes sending the first RA sequence.

[0986] As one embodiment, the first process includes running the first time window.

[0987] As one embodiment, the first process includes running the second time window.

[0988] As one embodiment, the first process includes receiving the SIB1 message.

[0989] As an example, the first process ends in response to stopping the third timer.

[0990] As an example, the first process ends in response to the expiration of the third timer.

[0991] As an example, the WUS configuration being applied at the first time includes either the first time window or the second time window running at the first time.

[0992] As an example, the WUS configuration being applied during the first time includes the third timer being running during the first time.

[0993] As an example, the application of the WUS configuration at the first time includes the first process not being completed at the first time.

[0994] Example 11

[0995] Example 11 illustrates a schematic diagram of another wireless transmission flowchart according to an embodiment of the present application, as shown in Figure 11.

[0996] For the first node U01A, in step S11101, a fourth message is sent; in step S11102, a second message is received; wherein the second message includes a first request indication; in step S11103, a third message is sent.

[0997] For the third node N03A, in step S11301, a fourth message is received; in step S11302, a second message is sent; and in step S11303, a third message is received.

[0998] In embodiment 11, the action of sending the third message depends on the second message including a first request indication.

[0999] As an example, step S11101 is present.

[1000] As an example, the first node sends the fourth message before receiving the second message.

[1001] As a sub-implementation, the fourth message includes an rlf-InfoAvailable.

[1002] As a sub-example, the fourth message indicates that the first node has available RA information.

[1003] As a sub-implementation, the fourth message includes a field whose name includes InfoAvailable.

[1004] As a sub-example, the fourth message is an RRC reconfiguration completion message, an RRC re-establishment completion message, an RRC establishment completion message, or an RRC recovery completion message.

[1005] As a sub-example, the name of the fourth message includes RRC and Complete.

[1006] As a sub-implementation, the fourth message is either an RRCReconfigurationComplete message or an RRCConnectionReconfigurationComplete message.

[1007] As a sub-implementation, the fourth message is either an RRCReestablishmentComplete message or an RRCConnectionReestablishmentComplete message.

[1008] As a sub-implementation, the fourth message is either the RRCEstablishmentComplete message or the RRCConnectionEstablishmentComplete message.

[1009] As a sub-implementation, the fourth message is either an RRCSetupComplete message or an RRCConnectionSetupComplete message.

[1010] As a sub-implementation, the fourth message is the UEAssistanceInformation message.

[1011] As a sub-implementation, upon successful initiation of a random access procedure on the second cell, the first node sends the fourth message, which indicates that the stored variables are available in the first node.

[1012] As a sub-example, during the RRC connection re-establishment process, the fourth message is the RRCReestablishmentComplete message, which is a response to the successful initiation of a random access procedure on the second cell.

[1013] As a sub-implementation, in the non-RRC_CONNECT state, as a response to the successful initiation of a random access procedure on the second cell, the fourth message is either an RRCSetupComplete message or an RRCReconfigurationComplete message.

[1014] In one embodiment, step S11101 is not present.

[1015] As an example, the second message is an RRC message.

[1016] As an example, the second message is a protocol layer message below the RRC sublayer.

[1017] As an example, the dashed box F11.1 is present.

[1018] As an example, the second message is a UEInformationRequest message.

[1019] As one embodiment, the second message includes the first request indication; the first request indication is rlf-ReportReq, and the first request indication is set to true to indicate the first information block, which is rlf-Report.

[1020] As an example, in response to receiving the rlf-ReportReq, the third message includes the rlf-Report, which is a UEInformationResponse message.

[1021] As one embodiment, the second message includes the first request indication; the first request indication is ra-ReportReq, and the first request indication is set to true to indicate the second information block, the second information block being ra-Report.

[1022] As an example, in response to receiving the ra-ReportReq, the third message includes the ra-Report, which is a UEInformationResponse message.

[1023] As an example, the second message is an RRC reconfiguration message.

[1024] As an example, the first request instruction indicates that at least a portion of the information in the first information block be sent.

[1025] As an example, the third message is a UEAssistanceInformation message, which includes at least a portion of the information in the first information block; in response to sending the third message, at least a portion of the information in the first information block is deleted.

[1026] As one embodiment, the first request instruction indicates that at least a portion of the information in the second information block be sent.

[1027] As an example, the third message is a UEAssistanceInformation message, which includes at least a portion of the information in the second information block; in response to sending the third message, at least a portion of the information in the second information block is deleted.

[1028] As an example, the second message is a MAC CE; the third message is a UEAssistanceInformation message.

[1029] As an example, the dashed box F11.1 does not exist.

[1030] As an example, the second message is an RRCRelease message.

[1031] As an example, the second message is an RRC Release message, which carries suspendConfig, and the first node enters the RRC_INACTIVE state from the RRC_CONNECT state.

[1032] As an example, the second message is a core network message.

[1033] As an example, the first request in the second message instructs the first node to delete at least a portion of the information in the first information block.

[1034] As an example, the first request instruction in the second message instructs the first node to delete at least a portion of the information in the second information block.

[1035] As an example, at least a portion of the information in the first information block is deleted as information from the second cell.

[1036] As an example, at least a portion of the information in the first information block is deleted, which is the second field, and the second field indicates the random access information of the second cell.

[1037] As an example, if the first request instruction in the second message instructs the first node to delete at least a portion of the information in the first information block, the third message is not sent.

[1038] Example 12A

[1039] Example 12A illustrates a structural block diagram of a processing apparatus for a first node according to an embodiment of the present application; as shown in Figure 12A. In Figure 12A, the processing apparatus 1200A in the first node includes a first receiver 1201A and a first processor 1202A.

[1040] The first receiver 1201A receives a first message in the first cell; the first message includes the WUS configuration of the second cell;

[1041] The first processor 1202A, in response to the wireless connection failure of the first node, starts a first timer; when the first timer runs, it performs cell selection and initiates a random access procedure on the second cell, wherein the random access procedure is to request SIB1 of the second cell, and the random access procedure includes: sending a first RA sequence; accompanied by sending the first RA sequence, setting a first information block in the VarRLF-Report;

[1042] In embodiment 12A, the WUS configuration of the second cell includes time-frequency resources of the first RA sequence; the first information block includes a first field, the first field indicating at least the identity of the second cell.

[1043] As an example, along with the initiation of the random access procedure on the second cell, the first information block includes a second field indicating the random access information of the second cell; wherein the random access information of the second cell depends on the WUS configuration of the second cell included in the first message.

[1044] As an example, as the random access procedure initiated on the second cell is completed, the first information block includes a first time interval; wherein the start time of the first time interval depends on the time when the first node experiences a wireless connection failure.

[1045] As an example, in response to the failure of the request for SIB1 of the second cell, a third field is set in the first information block, the third field indicating that the request for SIB1 of the second cell has failed.

[1046] As an example, in response to the failure of the request for SIB1 of the second cell, a fourth field is set in the first information block, the fourth field indicating the triggering condition of the second cell.

[1047] As one embodiment, the first processor, while transmitting the first RA sequence, sets a second information block in the VarRA-Report; wherein the second information block indicates that the WUS configuration of the second cell is applied; the second information block includes at least a first field, the first field indicating the identity information of the second cell.

[1048] As one embodiment, the first receiver receives a second message, wherein the second message indicates the first information block; the first processor sends a third message, wherein the action of sending the third message depends on the second message.

[1049] As one embodiment, the first receiver 1201A includes at least one of the following in Figure 4 of this application: antenna 452, receiver 454, multi-antenna receiver processor 458, receiver processor 456, controller / processor 459, memory 460, or data source 467.

[1050] As one embodiment, the first receiver 1201A includes at least an antenna 452 and a receiver 454 as shown in Figure 4 of this application.

[1051] As one embodiment, the first processor 1202A includes at least one of the following in Figure 4 of this application: a receiving processor 456, a transmitting processor 468, a controller / processor 459, a memory 460, or a data source 467.

[1052] As one embodiment, the first processor 1202 includes at least a processor 459, a memory 460, and a data source 467 as shown in Figure 4 of this application.

[1053] Example 12B

[1054] Example 12B illustrates a structural block diagram of a processing apparatus for a first node according to an embodiment of the present application; as shown in Figure 12B. In Figure 12B, the processing apparatus 1200B in the first node includes a first receiver 1201B, a first processor 1202B, and a first transmitter 1203B.

[1055] The first receiver 1201B receives a first RRC message, which is configured with a first time length.

[1056] The first processor 1202B, along with initiating the RRC connection re-establishment process, starts the first timer;

[1057] In Example 12B, whether to execute actions upon going to RRC_IDLE depends on whether at least the first node has a WUS configuration; the time length between the start time of the first timer and the first time is the first time length; wherein, the decision to execute actions upon going to RRC_IDLE depends on whether at least the first node has a WUS configuration includes:

[1058] If the first node does not have a WUS configuration, perform the action when switching to RRC_IDLE at the first time.

[1059] If at least the first node has a WUS configuration, the action of transitioning to RRC_IDLE is not performed at the first time.

[1060] As an example, if the first node does not have a WUS configuration, the action of executing the transition to RRC_IDLE at the first time depends on the first timer using the first time length; if at least the first node has a WUS configuration, the action of not executing the transition to RRC_IDLE at the first time depends on the first timer using the second time length; wherein, the first RRC message configures the second time length; both the first time length and the second time length are configured for the first timer.

[1061] As an example, if the first node does not have a WUS configuration, the action of executing the transition to RRC_IDLE at the first time depends on the first timer; the action of not executing the transition to RRC_IDLE at the first time depends on the second timer; wherein, the first RRC message configures the first time length to the first timer; the first RRC message configures the second time length to the second timer.

[1062] As an example, if at least the first node has a WUS configuration, the action of not performing the transition to RRC_IDLE at the first time depends on the first timer being paused.

[1063] As an example, if at least the first node has a WUS configuration, the action of not performing the transition to RRC_IDLE at the first time depends on the WUS configuration being applied at the first time.

[1064] As one embodiment, the first transmitter 1203B transmits a first RA sequence;

[1065] The first processor 1202B, in response to the transmission of the first RA sequence, opens a first time window; wherein, the first time window is for receiving RAR messages;

[1066] The first processor 1202B, in response to the receipt of the RAR message, opens a second time window; wherein, SIB1 is monitored within the second time window;

[1067] As an example, the WUS configuration being applied at the first time includes: either the first time window or the second time window is running at the first time.

[1068] As one embodiment, the first receiver 1201B includes at least one of the following in Figure 4 of this application: antenna 452, receiver 454, multi-antenna receiver processor 458, receiver processor 456, controller / processor 459, memory 460, or data source 467.

[1069] As one embodiment, the first receiver 1201B includes at least an antenna 452 and a receiver 454 as shown in Figure 4 of this application.

[1070] As one embodiment, the first transmitter 1203B includes at least one of the following in Figure 4 of this application: antenna 452, transmitter 454, multi-antenna transmitter processor 457, transmitter processor 468, controller / processor 459, memory 460, or data source 467.

[1071] As one embodiment, the first transmitter 1203B includes at least an antenna 452 and a transmitter 454 as shown in Figure 4 of this application.

[1072] As one embodiment, the first processor 1202B includes at least one of the following in Figure 4 of this application: a receiving processor 456, a transmitting processor 468, a controller / processor 459, a memory 460, or a data source 467.

[1073] As one embodiment, the first processor 1202B includes at least a processor 459, a memory 460, and a data source 467 as shown in Figure 4 of this application.

[1074] Example 13A

[1075] Example 13A illustrates a structural block diagram of a processing apparatus for a second node according to an embodiment of the present application; as shown in Figure 13A. In Figure 13A, the processing apparatus 1300A in the second node includes a second transmitter 1301A and a second receiver 1302A.

[1076] The second transmitter 1301A sends the first message; the first message includes the WUS configuration of the second cell;

[1077] The second receiver 1302A receives the first RA sequence;

[1078] In Example 13A, in response to a wireless connection failure, the receiver of the first message starts a first timer; when the first timer runs, the receiver of the first message performs cell selection and initiates a random access procedure on the second cell, wherein the random access procedure requests SIB1 of the second cell, and the random access procedure includes: sending a first RA sequence; accompanied by sending the first RA sequence, the receiver of the first message sets a first information block in the VarRLF-Report; wherein the WUS configuration of the second cell includes the time-frequency resources of the first RA sequence; the first information block includes a first field, the first field indicating at least the identity of the second cell.

[1079] As an example, when the random access procedure is initiated on the second cell, the recipient of the first message includes a second field in the first information block, the second field indicating the random access information of the second cell; wherein, the random access information of the second cell depends on the WUS configuration of the second cell included in the first message.

[1080] As an example, as the random access procedure initiated on the second cell is completed, the recipient of the first message includes a first time interval in the first information block; wherein the start time of the first time interval depends on the time when the first node experiences a wireless connection failure.

[1081] As an example, in response to the failure of the request for SIB1 of the second cell, the recipient of the first message sets a third field in the first information block, the third field indicating that the request for SIB1 of the second cell has failed.

[1082] As an example, in response to the failure of the SIB1 request of the second cell, the recipient of the first message sets a fourth field in the first information block, the fourth field indicating the triggering condition of the second cell.

[1083] As an example, along with sending the first RA sequence, the recipient of the first message sets a second information block in the VarRA-Report; wherein the second information block indicates that the WUS configuration of the second cell is applied; the second information block includes at least a first field, the first field indicating the identity information of the second cell.

[1084] As one embodiment, the second transmitter 1301A sends a second message, wherein the second message includes a first request indication; the second receiver 1302A receives a third message, wherein the action of the receiver of the first message sending the third message depends on the second message including the first request indication.

[1085] As one embodiment, the second transmitter 1301A sends a second RRC message; wherein the second RRC message enables the RA-Report of SIB1.

[1086] As one embodiment, the second transmitter 1301A includes at least one of the following in Figure 4 of this application: antenna 420, transmitter 418, multi-antenna transmitter processor 471, transmitter processor 416, controller / processor 475, or memory 476.

[1087] As one embodiment, the second transmitter 1301A includes at least an antenna 420 and a transmitter 418 as shown in Figure 4 of this application.

[1088] As one embodiment, the second receiver 1302A includes at least one of the following in Figure 4 of this application: antenna 420, receiver 418, multi-antenna receiver processor 472, receiver processor 470, controller / processor 475, or memory 476.

[1089] As one embodiment, the second receiver 1302A includes at least an antenna 420 and a receiver 418 as shown in Figure 4 of this application.

[1090] Example 13B

[1091] Example 13B illustrates a structural block diagram of a processing apparatus for a second node according to an embodiment of this application; as shown in Figure 13B. In Figure 13B, the processing apparatus 1300B in the second node includes a second transmitter 1301B.

[1092] The second transmitter 1301B transmits a first RRC message, which is configured with a first time length.

[1093] In Example 13B, along with initiating the RRC connection re-establishment process, the receiver of the first RRC message starts a first timer; wherein, whether to execute actions upon going to RRC_IDLE at the first moment depends on whether at least the receiver of the first RRC message has a WUS configuration; the length of time between the start time of the first timer and the first moment is the first time length; wherein, the decision to execute actions upon going to RRC_IDLE at the first moment depends on whether at least the receiver of the first RRC message has a WUS configuration includes:

[1094] If the recipient of the first RRC message does not have a WUS configuration, the action of switching to RRC_IDLE is performed at the first time.

[1095] If at least the recipient of the first RRC message has a WUS configuration, the action of switching to RRC_IDLE is not performed at the first time.

[1096] As an example, if the recipient of the first RRC message does not have WUS configuration, the action of performing the transition to RRC_IDLE at the first time depends on the first timer using the first time length; if at least the recipient of the first RRC message has WUS configuration, the action of not performing the transition to RRC_IDLE at the first time depends on the first timer using the second time length; wherein, the first RRC message configures the second time length; both the first time length and the second time length are configured for the first timer.

[1097] As an example, if the recipient of the first RRC message does not have a WUS configuration, the action of executing the transition to RRC_IDLE at the first time depends on the first timer; the action of not executing the transition to RRC_IDLE at the first time depends on the second timer; wherein, the first RRC message configures the first time length to the first timer; the first RRC message configures the second time length to the second timer.

[1098] As an example, if at least the recipient of the first RRC message has a WUS configuration, the action of not performing the transition to RRC_IDLE at the first time depends on the first timer being paused.

[1099] As an example, if at least the recipient of the first RRC message has a WUS configuration, the action of not performing the transition to RRC_IDLE at the first time depends on the WUS configuration being applied at the first time.

[1100] As an example,

[1101] The second receiver 1302B receives the first RA sequence;

[1102] The second transmitter 1301B, in response to the receipt of the first RA sequence, sends a RAR message;

[1103] As one embodiment, the sender of the first RA sequence opens a first time window; wherein the first time window is for receiving RAR messages; in response to the RAR message being received, a second time window is opened; wherein SIB1 is monitored within the second time window; wherein the WUS configuration being applied at the first time includes: either the first time window or the second time window being running at the first time.

[1104] As one embodiment, the second transmitter 1301B includes at least one of the following in Figure 4 of this application: antenna 420, transmitter 418, multi-antenna transmitter processor 471, transmitter processor 416, controller / processor 475, or memory 476.

[1105] As one embodiment, the second transmitter 1301B includes at least an antenna 420 and a transmitter 418 as shown in Figure 4 of this application.

[1106] As one embodiment, the second receiver 1302B includes at least one of the following in Figure 4 of this application: antenna 420, receiver 418, multi-antenna receiver processor 472, receiver processor 470, controller / processor 475, or memory 476.

[1107] As one embodiment, the second receiver 1302B includes at least an antenna 420 and a receiver 418 as shown in Figure 4 of this application.

[1108] Those skilled in the art will understand that all or part of the steps in the above methods can be implemented by a program instructing related hardware, and the program can be stored in a computer-readable storage medium, such as a read-only memory, hard disk, or optical disk. Optionally, all or part of the steps in the above embodiments can also be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiments can be implemented in hardware or in the form of software functional modules. This application is not limited to any specific combination of software and hardware. The user equipment, terminal, and UE in this application include, but are not limited to, drones, communication modules on drones, remote-controlled aircraft, aircraft, small aircraft, mobile phones, tablets, laptops, vehicle-mounted communication devices, wireless sensors, internet cards, IoT terminals, RFID terminals, NB-IoT terminals, MTC (Machine Type Communication) terminals, eMTC (enhanced MTC) terminals, data cards, internet cards, vehicle-mounted communication devices, low-cost mobile phones, low-cost tablets, and other wireless communication devices. The base station or system equipment in this application includes, but is not limited to, macrocell base stations, microcell base stations, home base stations, relay base stations, gNB (NR Node B), TRP (Transmitter Receiver Point), and other wireless communication equipment.

[1109] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A first node used for wireless communication, characterized in that, include: The first receiver receives the first message in the first cell; The first message includes the WUS configuration of the second cell; The first processor, in response to the wireless connection failure of the first node, starts the first timer; When the first timer runs, cell selection is performed and a random access procedure is initiated on the second cell. The random access procedure is for requesting SIB1 of the second cell and includes: sending a first RA sequence; and setting a first information block in the VarRLF-Report along with sending the first RA sequence. The WUS configuration of the second cell includes the time-frequency resources of the first RA sequence; the first information block includes a first field, which indicates at least the identity of the second cell.

2. The first node according to claim 1, characterized in that, As the random access procedure is initiated on the second cell, the first information block includes a second field indicating the random access information of the second cell; wherein the random access information of the second cell depends on the WUS configuration of the second cell included in the first message.

3. The first node according to any one of claims 1 or 2, characterized in that, As the random access procedure initiated on the second cell is completed, the first information block includes a first time interval; wherein the start time of the first time interval depends on the time when the first node experiences a wireless connection failure.

4. The first node according to any one of claims 1-3, characterized in that, In response to the failure of the request for SIB1 of the second cell, a third field is set in the first information block, the third field indicating that the request for SIB1 of the second cell has failed.

5. The first node according to any one of claims 1-4, characterized in that, In response to the failure of the request for SIB1 of the second cell, a fourth field is set in the first information block, the fourth field indicating the triggering condition of the second cell.

6. The first node according to any one of claims 1-5, characterized in that, include: The first processor, while transmitting the first RA sequence, sets a second information block in the VarRA-Report; The second information block indicates that the WUS configuration of the second cell is applied; the second information block includes at least a first field, which indicates the identity information of the second cell.

7. The first node according to any one of claims 1-6, characterized in that, include: The first receiver receives a second message; wherein the second message indicates the first information block; The first processor sends a third message; The action of sending the third message depends on the second message.

8. A second node used for wireless communication, characterized in that, include: The second transmitter sends the first message; The first message includes the WUS configuration of the second cell; The second receiver receives the first RA sequence; In response to a wireless connection failure, the receiver of the first message starts a first timer. While the first timer is running, the receiver of the first message performs cell selection and initiates a random access procedure on the second cell. This random access procedure, in order to request SIB1 of the second cell, includes: sending a first RA sequence; accompanying the sending of the first RA sequence, the receiver of the first message sets a first information block in the VarRLF-Report; the WUS configuration of the second cell includes the time-frequency resources of the first RA sequence; the first information block includes a first field indicating at least the identity of the second cell.

9. The second node according to claim 8, characterized in that, As the random access procedure is initiated on the second cell, the recipient of the first message includes a second field in the first information block, the second field indicating the random access information of the second cell; wherein the random access information of the second cell depends on the WUS configuration of the second cell included in the first message.

10. The second node according to any one of claims 8 or 9, characterized in that, As the random access procedure initiated on the second cell is completed, the recipient of the first message includes a first time interval in the first information block; wherein the start time of the first time interval depends on the time when the first node experiences a wireless connection failure.

11. The second node according to any one of claims 8-10, characterized in that, In response to the failure of the request for SIB1 of the second cell, the recipient of the first message sets a third field in the first information block, the third field indicating that the request for SIB1 of the second cell has failed.

12. The second node according to any one of claims 8-11, characterized in that, In response to the failure of the request for SIB1 of the second cell, the recipient of the first message sets a fourth field in the first information block, the fourth field indicating the triggering condition of the second cell.

13. The second node according to any one of claims 8-12, characterized in that, Along with sending the first RA sequence, the recipient of the first message sets a second information block in the VarRA-Report; wherein the second information block indicates that the WUS configuration of the second cell is applied; the second information block includes at least a first field, the first field indicating the identity information of the second cell.

14. The second node according to any one of claims 8-13, characterized in that, include: The second transmitter sends a second message; wherein the second message includes a first request indication; The second receiver receives the third message; The action of the recipient of the first message sending the third message depends on the second message including the first request indication.

15. A method used in a first node of wireless communication, characterized in that, include: Receive the first message in the first cell; The first message includes the WUS configuration of the second cell; In response to the wireless connection failure of the first node, start the first timer; When the first timer runs, cell selection is performed and a random access procedure is initiated on the second cell. The random access procedure is for requesting SIB1 of the second cell and includes: sending a first RA sequence; and setting a first information block in the VarRLF-Report along with sending the first RA sequence. The WUS configuration of the second cell includes the time-frequency resources of the first RA sequence; the first information block includes a first field, which indicates at least the identity of the second cell.

16. The method in the first node according to claim 15, characterized in that, As the random access procedure is initiated on the second cell, the first information block includes a second field indicating the random access information of the second cell; wherein the random access information of the second cell depends on the WUS configuration of the second cell included in the first message.

17. The method in the first node according to any one of claims 15 or 16, characterized in that, As the random access procedure initiated on the second cell is completed, the first information block includes a first time interval; wherein the start time of the first time interval depends on the time when the first node experiences a wireless connection failure.

18. The method in the first node according to any one of claims 15-17, characterized in that, In response to the failure of the request for SIB1 of the second cell, a third field is set in the first information block, the third field indicating that the request for SIB1 of the second cell has failed.

19. The method in the first node according to any one of claims 15-18, characterized in that, In response to the failure of the request for SIB1 of the second cell, a fourth field is set in the first information block, the fourth field indicating the triggering condition of the second cell.

20. The method in the first node according to any one of claims 15-19, characterized in that, include: Along with sending the first RA sequence, a second information block is set in the VarRA-Report; The second information block indicates that the WUS configuration of the second cell is applied; the second information block includes at least a first field, which indicates the identity information of the second cell.

21. The method in the first node according to any one of claims 15-20, characterized in that, include: Receive a second message; wherein the second message indicates the first information block; Send a third message; The action of sending the third message depends on the second message.

22. A method used in a second node of wireless communication, characterized in that, include: Send the first message; the first message includes the WUS configuration of the second cell; Receive the first RA sequence; In response to a wireless connection failure, the receiver of the first message starts a first timer. While the first timer is running, the receiver of the first message performs cell selection and initiates a random access procedure on the second cell. This random access procedure, in order to request SIB1 of the second cell, includes: sending a first RA sequence; accompanying the sending of the first RA sequence, the receiver of the first message sets a first information block in the VarRLF-Report; the WUS configuration of the second cell includes the time-frequency resources of the first RA sequence; the first information block includes a first field indicating at least the identity of the second cell.

23. The method in the second node according to claim 22, characterized in that, As the random access procedure is initiated on the second cell, the recipient of the first message includes a second field in the first information block, the second field indicating the random access information of the second cell; wherein the random access information of the second cell depends on the WUS configuration of the second cell included in the first message.

24. The method in the second node according to any one of claims 22 or 23, characterized in that, As the random access procedure initiated on the second cell is completed, the recipient of the first message includes a first time interval in the first information block; wherein the start time of the first time interval depends on the time when the first node experiences a wireless connection failure.

25. The method in the second node according to any one of claims 22-24, characterized in that, In response to the failure of the request for SIB1 of the second cell, the recipient of the first message sets a third field in the first information block, the third field indicating that the request for SIB1 of the second cell has failed.

26. The method in the second node according to any one of claims 22-25, characterized in that, In response to the failure of the request for SIB1 of the second cell, the recipient of the first message sets a fourth field in the first information block, the fourth field indicating the triggering condition of the second cell.

27. The method in the second node according to any one of claims 22-26, characterized in that, Along with sending the first RA sequence, the recipient of the first message sets a second information block in the VarRA-Report; wherein the second information block indicates that the WUS configuration of the second cell is applied; the second information block includes at least a first field, the first field indicating the identity information of the second cell.

28. The method in the second node according to any one of claims 22-27, characterized in that, include: Send a second message; wherein the second message includes a first request instruction; Receive third message; The action of the recipient of the first message sending the third message depends on the second message including the first request indication.

Images