A method and device used in a communication node for wireless communication

Abstract

The present application discloses a method and apparatus in a communication node used for wireless communication. The communication node sends a first message and a second message; receives a third message, the third message being used to update an RRC connection; determines whether to execute a first set of actions based on whether a first set of conditions is satisfied; executes the first set of actions when the first set of conditions is satisfied; the first message and the second message are used to request a first RRC connection update and a second RRC connection update, respectively; the first set of conditions includes one of the first message and the second message being used to trigger the third message; the behavior of executing the first set of actions includes monitoring control signaling in a first set of time-frequency resources; the time domain resources occupied by the second message are orthogonal to the time domain resources occupied by the first message; between the sending of the first message and the sending of the second message, the first node does not receive a message for updating the RRC connection.

Description

Technical Field

[0001] The present application relates to a transmission method and device in a wireless communication system, and in particular to a transmission method and device for a small data packet service. Background Art

[0002] NR (New Radio) supports the RRC (Radio Resource Control) inactive (RRC_INACTIVE) state. Until 3GPP Rel-16, the RRC inactive state does not support data transmission. When the user equipment (UE) has periodic or non-periodic infrequent small data packets to send in the RRC_INACTIVE state, it needs to resume the connection first, that is, switch to the RRC connected (RRC_CONNECTED) state, and then switch to the RRC_INACTIVE state after the data is sent. The 3GPP RAN#86 meeting decided to carry out the "NR INACTIVE state small data packet transmission (SDT)" work item (WI) to study the small data packet transmission technology in the RRC_INACTIVE state, including sending uplink data on the pre-configured PUSCH (Physical Uplink Shared Channel) resources, or using Message 3 (Msg3) or Message B (MsgB) in the random access (RA) process to carry data. Summary of the invention

[0003] During the SDT process, if new data arrives and cannot be transmitted using SDT, the UE needs to be switched from the RRC_INACTIVE state to the RRC_CONNECTED state. If a new RRC recovery process is initiated, the SDT process will be affected. Therefore, this needs to be enhanced.

[0004] In view of the above problems, this application provides a solution. In the description of the above problems, the NR scenario is used as an example; this application is also applicable to scenarios such as LTE (Long Term Evolution) or NB-IoT (NarrowBand Internet of Things), achieving similar technical effects in the NR scenario. In addition, the use of a unified solution for different scenarios can also help reduce hardware complexity and costs.

[0005] As an embodiment, the interpretation of the terminology in the present application refers to the definition of the 3GPP specification protocol TS36 series.

[0006] As an example, the interpretation of the terms in the present application refers to the definition of the TS38 series of specification protocols of 3GPP.

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

[0008] As an embodiment, the interpretation of the terms in this application refers to the definition of the standard protocol of IEEE (Institute of Electrical and Electronics Engineers).

[0009] It should be noted that, in the absence of conflict, the embodiments and features in any node of the present application can be applied to any other node. In the absence of conflict, the embodiments and features in the embodiments of the present application can be arbitrarily combined with each other.

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

[0011] Sending a first message and a second message;

[0012] receiving a third message, the third message being used to update an RRC connection; determining whether to execute a first set of actions according to whether a first set of conditions is satisfied; and executing the first set of actions when the first set of conditions is satisfied;

[0013] Among them, the first message is used to request a first RRC connection update, and the second message is used to request a second RRC connection update; the first condition set includes one of the first message and the second message being used to trigger the third message; the behavior execution first action set includes monitoring control signaling in a first time-frequency resource set, and the first time-frequency resource set is allocated to a first search space; the time domain resources occupied by the second message are orthogonal to the time domain resources occupied by the first message; between the sending of the first message and the sending of the second message, the first node did not receive a message for updating the RRC connection.

[0014] As an embodiment, the problem to be solved by the present application includes: how to avoid data interruption during the SDT process.

[0015] As an embodiment, the problem to be solved by the present application includes: how to avoid the reconstruction of DRB (Data Radio Bearer).

[0016] As an embodiment, the problem to be solved by the present application includes: how to avoid repeated operations.

[0017] As an embodiment, the problem to be solved by the present application includes: how to avoid interrupting the RRC link recovery process being executed.

[0018] As an embodiment, the characteristics of the above method include: when the SDT process is completed, if the RRC connection recovery process is being executed, executing the first action set.

[0019] As an embodiment, the benefits of the above method include: avoiding repeated operations.

[0020] As an embodiment, the benefits of the above method include: avoiding interruption of the ongoing RRC link recovery process.

[0021] As an embodiment, the benefits of the above method include: avoiding the reconstruction of DRB.

[0022] As an embodiment, the benefits of the above method include: avoiding data interruption during the SDT process.

[0023] According to one aspect of the present application, it is characterized by comprising:

[0024] receiving a first signaling and a second signaling;

[0025] Sending the first message and starting a first timer; sending the second message and starting a second timer;

[0026] Among them, the behavior performs the first action set including stopping at least one of the first timer or the second timer; the first signaling indicates the expiration value of the first timer; and the second signaling indicates the expiration value of the second timer.

[0027] According to one aspect of the present application, it is characterized by comprising:

[0028] When requesting the first RRC connection update, reestablishing the PDCP entity of SRB1 and restoring the SRB1, reestablishing the PDCP entity of the first DRB and restoring the first DRB;

[0029] The first condition set includes that only the first message of the first message and the second message is used to trigger the third message.

[0030] According to one aspect of the present application, it is characterized in that the behavior of executing the first action set includes suspending the first DRB.

[0031] According to one aspect of the present application, it is characterized in that the behavior performs a first set of actions including restoring a first bearer; the first bearer is a bearer other than the first DRB and the SRB1.

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

[0033] The first receiver determines, according to the number of messages used for updating the RRC connection received between the reference message and the reception of the third message, whether only the first message of the first message and the second message is used to trigger the third message;

[0034] The reference message is a message sent later between the first message and the second message.

[0035] According to one aspect of the present application, it is characterized in that the third message includes a first field, and the first field is used to determine whether only the first message of the first message and the second message is used to trigger the third message or whether only the second message of the first message and the second message is used to trigger the third message.

[0036] The present application discloses a method used in a second node of wireless communication, characterized by comprising:

[0037] receiving a first message and a second message;

[0038] Sending a third message, where the third message is used to update the RRC connection;

[0039] Among them, whether the first action set is executed is determined based on whether the first condition set is met; when the first condition set is met, the first action set is executed; the first message is used to request a first RRC connection update, and the second message is used to request a second RRC connection update; the first condition set includes one of the first message and the second message being used to trigger the third message; the behavior of executing the first action set includes monitoring control signaling in a first time-frequency resource set, and the first time-frequency resource set is allocated to a first search space; the time domain resources occupied by the second message are orthogonal to the time domain resources occupied by the first message; between the sending of the first message and the sending of the second message, the recipient of the third message did not receive the message for updating the RRC connection.

[0040] According to one aspect of the present application, it is characterized by comprising:

[0041] Sending a first signaling and a second signaling;

[0042] receiving the first message; receiving the second message;

[0043] Among them, the first timer is started, and the second timer is started; the behavior performs a first action set including stopping at least one of the first timer or the second timer; the first signaling indicates the expiration value of the first timer; the second signaling indicates the expiration value of the second timer.

[0044] According to one aspect of the present application, it is characterized in that when the first RRC connection update is requested, the PDCP entity of SRB1 is rebuilt and the SRB1 is restored, the PDCP entity of the first DRB is rebuilt and the first DRB is restored; wherein, the first condition set includes only the first message among the first message and the second message being used to trigger the third message.

[0045] According to one aspect of the present application, it is characterized in that the behavior of executing the first action set includes suspending the first DRB.

[0046] According to one aspect of the present application, it is characterized in that the behavior performs a first set of actions including restoring a first bearer; the first bearer is a bearer other than the first DRB and the SRB1.

[0047] According to one aspect of the present application, it is characterized in that whether only the first message among the first message and the second message is used to trigger the third message is determined according to the number of messages used for updating the RRC connection received between the reception of the reference message and the third message;

[0048] The reference message is a message sent later between the first message and the second message.

[0049] According to one aspect of the present application, it is characterized in that the third message includes a first field, and the first field is used to determine whether only the first message of the first message and the second message is used to trigger the third message or whether only the second message of the first message and the second message is used to trigger the third message.

[0050] The present application discloses a first node used for wireless communication, characterized in that it includes:

[0051] A first transmitter sends a first message and a second message;

[0052] A first receiver receives a third message, where the third message is used to update an RRC connection; determines whether to execute a first action set according to whether a first condition set is satisfied; and executes the first action set when the first condition set is satisfied;

[0053] Among them, the first message is used to request a first RRC connection update, and the second message is used to request a second RRC connection update; the first condition set includes one of the first message and the second message being used to trigger the third message; the behavior execution first action set includes monitoring control signaling in a first time-frequency resource set, and the first time-frequency resource set is allocated to a first search space; the time domain resources occupied by the second message are orthogonal to the time domain resources occupied by the first message; between the sending of the first message and the sending of the second message, the first node did not receive a message for updating the RRC connection.

[0054] The present application discloses a second node used for wireless communication, characterized in that it includes:

[0055] A second receiver receives the first message and the second message;

[0056] A second transmitter sends a third message, where the third message is used to update the RRC connection;

[0057] Among them, whether the first action set is executed is determined based on whether the first condition set is met; when the first condition set is met, the first action set is executed; the first message is used to request a first RRC connection update, and the second message is used to request a second RRC connection update; the first condition set includes one of the first message and the second message being used to trigger the third message; the behavior of executing the first action set includes monitoring control signaling in a first time-frequency resource set, and the first time-frequency resource set is allocated to a first search space; the time domain resources occupied by the second message are orthogonal to the time domain resources occupied by the first message; between the sending of the first message and the sending of the second message, the recipient of the third message did not receive the message for updating the RRC connection.

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

[0059] -.Avoid repeated operations;

[0060] -.Avoid interrupting the ongoing RRC link recovery process;

[0061] -.Avoid DRB reconstruction;

[0062] -.Avoid data interruption during SDT process. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0064] Figure 1 A flow chart showing the transmission of a first message, a second message and a third message according to an embodiment of the present application is shown;

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

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

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

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

[0069] Figure 6 A wireless signal transmission flow chart according to another embodiment of the present application is shown;

[0070] Figure 7 A wireless signal transmission flow chart according to another embodiment of the present application is shown;

[0071] Figure 8 A schematic diagram showing that executing a first action set includes stopping a first timer according to an embodiment of the present application;

[0072] Fig. 9 A schematic diagram showing that executing a first action set includes stopping a second timer according to an embodiment of the present application;

[0073] Fig.10 A schematic diagram showing that executing a first action set includes stopping a first timer and a second timer according to an embodiment of the present application;

[0074] Fig.11 A schematic diagram showing that a third message includes a first field according to an embodiment of the present application;

[0075] Fig.12 A schematic diagram showing that the number of received messages used to update the RRC connection is used to determine whether only the first message is used to trigger the third message according to an embodiment of the present application;

[0076] Fig.13 A structural block diagram of a processing device used in a first node according to an embodiment of the present application is shown;

[0077] Fig.14 A structural block diagram of a processing device used in a second node according to an embodiment of the present application is shown;

[0078] Fig.15 A structural block diagram showing a second message including a first MAC CE according to an embodiment of the present application is shown. DETAILED DESCRIPTION

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

[0080] Example 1

[0081] Embodiment 1 illustrates a flow chart of the transmission of the first message, the second message, and the third message according to an embodiment of the present application, as shown in the attached Figure 1 Attached Figure 1 In the figure, each box represents a step. It should be emphasized that the order of the boxes in the figure does not represent the temporal relationship between the steps represented.

[0082] In Example 1, the first node in the present application sends a first message and a second message in step 101; in step 102, receives a third message, and the third message is used to update the RRC connection; determines whether to execute a first action set according to whether a first condition set is satisfied; when the first condition set is satisfied, executes the first action set; wherein the first message is used to request a first RRC connection update, and the second message is used to request a second RRC connection update; the first condition set includes one of the first message and the second message being used to trigger the third message; the behavior of executing the first action set includes monitoring control signaling in a first time-frequency resource set, and the first time-frequency resource set is allocated to a first search space; the time domain resources occupied by the second message are orthogonal to the time domain resources occupied by the first message; between the sending of the first message and the sending of the second message, the first node did not receive a message for updating the RRC connection.

[0083] As an embodiment, the SDT (Small Data Transmission) includes transmitting a small data packet (RRC_INACTIVE Data Transmission, IDT) in an RRC (Radio Resource Control) inactive state.

[0084] As an embodiment, the SDT includes transmitting a data packet via a DRB (Data Radio Bearer) in an RRC inactive state.

[0085] As an embodiment, the SDT includes transmitting a data packet via one or more DRBs in an RRC inactive state.

[0086] As an embodiment, the SDT includes restoring one or more DRBs in an RRC inactive state and transmitting data packets through the one or more DRBs.

[0087] As an embodiment, the SDT includes sending a data packet through at least one of Msg3 (Message 3) or MsgA (Message A) in a random access procedure (Random Access, RA) in an RRC inactive state.

[0088] As an embodiment, the SDT includes sending a data packet on a resource block configured in RRCRelease in an RRC inactive state.

[0089] As an embodiment, the phrase resuming a suspended RRC connection includes: entering an RRC connected state from an RRC inactive state.

[0090] As an embodiment, the phrase resuming a suspended RRC connection includes: entering an RRC connected state from an RRC idle state.

[0091] As an embodiment, the phrase "restoring a suspended RRC connection" includes: restoring all or part of the suspended RBs (Radio Bearer) except SRB0 (Signalling Radio Bearer0).

[0092] As an embodiment, the phrase that the first message is used to request a first RRC connection update includes: the first message is used to perform SDT.

[0093] As an embodiment, the phrase said first message is used to request a first RRC connection update includes: said first message is used to request resumption of a suspended RRC connection.

[0094] As an embodiment, the phrase that the first message is used to request a first RRC connection update includes: the first message is used to perform an RNA update.

[0095] As an embodiment, the first message is sent in an RRC inactive state.

[0096] As an embodiment, the first message is sent through an antenna port.

[0097] As an embodiment, the signaling radio bearer of the first message includes SRB0.

[0098] As an embodiment, the logical channel of the first message includes CCCH (Common Control Channel).

[0099] As an embodiment, the logical channel of the first message includes CCCH1 (Common Control Channel 1).

[0100] As an embodiment, the RLC-SAP of the first message includes TM (Transparent Mode).

[0101] As an embodiment, the first message is delivered to a lower layer, and the lower layer includes at least one of a PDCP (Packet Data Convergence Protocol) layer, an RLC (Radio Link Control) layer, a MAC (Medium Access Control) layer, or a PHY (Physical) layer.

[0102] As an embodiment, the first message includes an uplink signaling.

[0103] As an embodiment, the first message includes all or part of higher layer signaling.

[0104] As an embodiment, the first message includes an RRC message.

[0105] As an embodiment, the first message includes an RRC message, and the name of the RRC message includes RRCResumeRequest.

[0106] As an embodiment, the first message includes an RRC message, and the name of the RRC message includes RRCResumeRequest1.

[0107] As an embodiment, the first message includes an RRC message, and the name of the RRC message includes RRCSmallDataTransmissionRequest.

[0108] As an embodiment, the first message includes an RRC message, and the name of the RRC message includes RRCInactiveDataTransmissionRequest.

[0109] As an embodiment, the first message includes an RRC message, and the name of the RRC message includes at least one of RRC or Resume or Request or 1 or SDT or IDT or Inactive or Small or Data or Transmission.

[0110] As an embodiment, the first message includes an IE (Information Element) in an RRC message, and the name of the IE includes ShortI-RNTI-Value.

[0111] As an embodiment, the first message includes an IE in an RRC message, and the name of the IE includes I-RNTI-Value.

[0112] As an embodiment, the first message includes a field in an RRC message, and the name of the field includes resumeMAC-I.

[0113] As an embodiment, the first message includes a field in an RRC message, and the name of the field includes resumeIdentity.

[0114] As an embodiment, the first message includes a field in an RRC message, and the name of the field includes resumeCause.

[0115] As an embodiment, the first message includes an IE in an RRC message, and the name of the IE includes ResumeCause.

[0116] As a sub-embodiment of this embodiment, the value of the ResumeCause is set to at least one of emergency, or highPriorityAccess, or mt-Access, mo-Signalling, or mo-Data, or mo-VoiceCall, or mo-VideoCall, or mo-SMS, or rna-Update, or mps-PriorityAccess, or mcs-PriorityAccess.

[0117] As a sub-embodiment of this embodiment, the value of resumeCause is set to a name, and the name includes at least one of sdt or idt or inactive or small or Data or transmission.

[0118] As an embodiment, the first message includes a field in an RRC message, and the name of the field includes spare.

[0119] As an embodiment, the phrase that the second message is used to request a second RRC connection update includes: the second message is used to perform SDT.

[0120] As an embodiment, the phrase said second message is used to request a second RRC connection update includes: said second message is used to request resumption of a suspended RRC connection.

[0121] As an embodiment, the phrase said second message is used to request a second RRC connection update includes: said second message is used to perform RNA update.

[0122] As an embodiment, the first RRC connection update is different from the second RRC connection update.

[0123] As an embodiment, the first RRC connection update and the second RRC connection update are triggered by different reasons.

[0124] As an embodiment, the second message is sent in an RRC inactive state.

[0125] As an embodiment, the second message is sent through the antenna port.

[0126] As an embodiment, the signaling radio bearer of the second message includes SRB0.

[0127] As an embodiment, the signaling radio bearer of the first message includes SRB1.

[0128] As an embodiment, the signaling radio bearer of the first message includes SRB2.

[0129] As an embodiment, the signaling radio bearer of the first message includes SRB3.

[0130] As an embodiment, the logical channel of the second message includes CCCH.

[0131] As an embodiment, the logical channel of the second message includes CCCH1.

[0132] As an embodiment, the logical channel of the first message includes a DCCH (Dedicated Control Channel).

[0133] As an embodiment, the RLC-SAP of the second message includes TM.

[0134] As an embodiment, the second message is delivered to a lower layer, and the lower layer includes at least one of a PDCP layer, an RLC layer, a MAC layer, or a PHY layer.

[0135] As an embodiment, the second message includes an uplink signaling.

[0136] As an embodiment, the second message includes all or part of higher layer signaling.

[0137] As an embodiment, the second message includes an RRC message.

[0138] As an embodiment, the second message includes an RRC message, and the name of the RRC message includes RRCResumeRequest.

[0139] As an embodiment, the second message includes an RRC message, and the name of the RRC message includes RRCResumeRequest1.

[0140] As an embodiment, the second message includes an RRC message, and the name of the RRC message includes RRCSmallDataTransmissionRequest.

[0141] As an embodiment, the second message includes an RRC message, and the name of the RRC message includes RRCInactiveDataTransmissionRequest.

[0142] As an embodiment, the second message includes an RRC message, and the name of the RRC message includes at least one of RRC or Resume or Request or 1 or SDT or IDT or Inactive or Small or Data or Transmission.

[0143] As an embodiment, the second message includes an IE in an RRC message, and the name of the IE includes ShortI-RNTI-Value.

[0144] As an embodiment, the second message includes an IE in an RRC message, and the name of the IE includes I-RNTI-Value.

[0145] As an embodiment, the second message includes a field in an RRC message, and the name of the field includes resumeMAC-I.

[0146] As an embodiment, the second message includes a field in an RRC message, and the name of the field includes resumeIdentity.

[0147] As an embodiment, the second message includes a field in an RRC message, and the name of the field includes resumeCause.

[0148] As an embodiment, the second message includes an IE in an RRC message, and the name of the IE includes ResumeCause.

[0149] As a sub-embodiment of this embodiment, the value of the ResumeCause is set to at least one of emergency, or highPriorityAccess, or mt-Access, mo-Signalling, or mo-Data, or mo-VoiceCall, or mo-VideoCall, or mo-SMS, or rna-Update, or mps-PriorityAccess, or mcs-PriorityAccess.

[0150] As a sub-embodiment of this embodiment, the value of resumeCause is set to a name, and the name includes at least one of sdt or idt or inactive or small or Data or transmission.

[0151] As an embodiment, the second message includes a field in an RRC message, and the name of the field includes spare.

[0152] As an embodiment, the first message and the second message are triggered for different reasons.

[0153] As an embodiment, the value of ResumeCause in the first message is the same as the value of ResumeCause in the second message.

[0154] As an embodiment, the value of ResumeCause in the first message is different from the value of ResumeCause in the second message.

[0155] As an embodiment, the reason why the first message is triggered includes executing SDT, and the reason why the second message is triggered does not include executing SDT.

[0156] As an embodiment, the reason why the first message is triggered does not include executing SDT, and the reason why the second message is triggered includes executing SDT.

[0157] As an embodiment, the first RRC connection update is related to the RRC inactive state transmission data packet, and the second RRC connection update is not related to the RRC inactive state transmission data packet.

[0158] As a sub-embodiment of this embodiment, the phrase that the first RRC connection update is related to the RRC inactive state transmission data packet includes: the first RRC connection update is used for SDT.

[0159] As a sub-embodiment of this embodiment, the phrase "the second RRC connection update is independent of the RRC inactive state transmission data packet" includes: the second RRC connection update includes RNA (RAN (Radio Access Network)-basedNotification Area, notification area based on wireless access network) update (Update).

[0160] As a sub-embodiment of this embodiment, the phrase the second RRC connection update is independent of the RRC inactive state transmission data packet includes: the second RRC connection update includes resuming a suspended RRC connection.

[0161] As an embodiment, the first RRC connection update is independent of the RRC inactive state transmission data packet, and the second RRC connection update is related to the RRC inactive state transmission data packet.

[0162] As a sub-embodiment of this embodiment, the phrase that the second RRC connection update is related to the RRC inactive state transmission data packet includes: the second RRC connection update is used for SDT.

[0163] As a sub-embodiment of this embodiment, the phrase "the first RRC connection update is independent of the RRC inactive state transmission data packet" includes: the first RRC connection update includes RNA (RAN (Radio Access Network)-basedNotification Area, notification area based on wireless access network) update (Update).

[0164] As a sub-embodiment of this embodiment, the phrase that the first RRC connection update is independent of the RRC inactive state transmission data packet includes: the first RRC connection update includes resuming a suspended RRC connection.

[0165] As an embodiment, the phrase that the third message is used to update the RRC connection includes: the third message is used to command to release an RRC connection.

[0166] As an embodiment, the phrase that the third message is used to update the RRC connection includes: the third message is used to command suspension of an RRC connection.

[0167] As an embodiment, the phrase that the third message is used to update the RRC connection includes: the third message is used to resume a suspended RRC connection.

[0168] As an embodiment, the phrase that the third message is used to update the RRC connection includes: the third message is used to establish SRB1.

[0169] As an embodiment, the phrase that the third message is used to update the RRC connection includes: the third message is used to reject an RRC connection recovery.

[0170] As an embodiment, the third message is received in the RRC connected state.

[0171] As an embodiment, the third message is received in an RRC inactive state.

[0172] As an embodiment, the third message is sent through the antenna port.

[0173] As an embodiment, the signaling radio bearer of the third message includes SRB0.

[0174] As an embodiment, the signaling radio bearer of the third message includes SRB1.

[0175] As an embodiment, the logical channel of the third message includes CCCH.

[0176] As an embodiment, the logical channel of the third message includes DCCH.

[0177] As an embodiment, the RLC-SAP of the third message includes TM.

[0178] As an embodiment, the RLC-SAP of the third message includes AM (Acknowledged Mode).

[0179] As an embodiment, the third message is delivered to a lower layer, and the lower layer includes at least one of a PDCP layer, an RLC layer, a MAC layer, or a PHY layer.

[0180] As an embodiment, the third message includes a downlink signaling.

[0181] As an embodiment, the third message includes all or part of higher layer signaling.

[0182] As an embodiment, the third message includes an RRC (Radio Resource Control) message.

[0183] As an embodiment, the third message includes an RRC message, and the name of the RRC message includes RRCRelease.

[0184] As an embodiment, the third message includes an RRC message, and the name of the RRC message includes RRCResume.

[0185] As an embodiment, the third message includes an RRC message, and the name of the RRC message includes RRCSetup.

[0186] As an embodiment, the third message includes an RRC message, and the name of the RRC message includes RRCReject.

[0187] As an embodiment, the phrase determining whether to execute a first action set according to whether a first condition set is satisfied includes: whether executing the first action set is related to the first condition set.

[0188] As an embodiment, the phrase determining whether to execute a first set of actions according to whether a first set of conditions is satisfied includes: the first set of conditions is used to determine whether to execute the first set of actions.

[0189] As an embodiment, the sentence “when the first condition set is met, the first action set is executed” means: if the first condition set is met, the first action set is executed.

[0190] As an embodiment, the sentence "when the first condition set is met, the first action set is executed" means: when all conditions in the first condition set are met, the first action set is executed.

[0191] As an embodiment, the sentence "when the first condition set is met, the first action set is executed" means: when each condition in the first condition set is met, the first action set is executed.

[0192] As an embodiment, when the first set of conditions is not met, a second set of actions is executed.

[0193] As an embodiment, if at least one condition in the first set of conditions is not satisfied, a second set of actions is executed.

[0194] As an embodiment, when the first set of conditions is not satisfied, execution of the first set of actions is abandoned.

[0195] As a sub-embodiment of this embodiment, the sentence "when the first condition set is not met, abandon the execution of the first action set" means: if the first condition set is not met, abandon the execution of the first action set.

[0196] As a sub-embodiment of this embodiment, the sentence "when the first condition set is not met, abandon the execution of the first action set" means: if at least one condition in the first condition set is not met, abandon the execution of the first action set.

[0197] As an embodiment, the phrase that the first condition set includes that one of the first message and the second message is used to trigger the third message includes: the first condition set includes that only the first message of the first message and the second message is used to trigger the third message.

[0198] As an embodiment, the phrase that the first condition set includes that one of the first message and the second message is used to trigger the third message includes: the first condition set includes that only the second message of the first message and the second message is used to trigger the third message.

[0199] As an embodiment, the phrase that the first condition set includes that one of the first message and the second message is used to trigger the third message includes: the first condition set includes that only the second message of the first message and the second message is used to trigger the third message.

[0200] As an embodiment, the phrase the first condition set includes one of the first message and the second message is used to trigger the third message to include: the first condition set includes the third message being a response to one of the first message and the second message.

[0201] As an embodiment, the phrase the first condition set includes one of the first message and the second message being used to trigger the third message includes: the first condition set includes the third message being a response to the first message.

[0202] As an embodiment, the phrase the first condition set includes one of the first message and the second message being used to trigger the third message includes: the first condition set includes the third message being a response to the second message.

[0203] As an embodiment, the behavior of monitoring control signaling in the first time-frequency resource set includes: monitoring the control signaling on the time domain resources and / or frequency domain resources corresponding to the first time-frequency resource set.

[0204] As an embodiment, the behavior of monitoring control signaling in the first time-frequency resource set includes: receiving the control signaling on the first time-frequency resource set.

[0205] As an embodiment, the monitoring includes searching.

[0206] As an embodiment, the monitoring includes monitoring.

[0207] As an embodiment, the monitoring means including checking through CRC (Cyclic Redundancy Check).

[0208] As an embodiment, the behavior monitoring control signaling includes determining whether the control signaling exists through energy monitoring.

[0209] As an embodiment, the behavior monitoring control signaling includes determining whether the control signaling exists through coherent detection.

[0210] As an embodiment, the behavior monitoring control signaling includes determining whether the control signaling exists through broadband detection.

[0211] As an embodiment, the behavior monitoring control signaling includes determining whether the control signaling exists through relevant detection.

[0212] As an embodiment, the behavior monitoring control signaling includes determining whether the control signaling exists through synchronous detection.

[0213] As an embodiment, the behavior monitoring control signaling includes determining whether the control signaling exists through waveform detection.

[0214] As an embodiment, the behavior monitoring control signaling includes determining whether the control signaling exists by maximum likelihood detection.

[0215] As an embodiment, the control signaling includes DCI (Downlink Control Information).

[0216] As an embodiment, the control signaling includes PDCCH (Physical Downlink Control Channel).

[0217] As an embodiment, the control signaling includes a PDCCH candidate (Candidate).

[0218] As an embodiment, the control signaling is encrypted by a first identifier.

[0219] As a sub-embodiment of this embodiment, the phrase that the control signaling is encrypted by the first identifier includes: the control signaling is encrypted by the first identifier.

[0220] As a sub-embodiment of this embodiment, the phrase that the control signaling is encrypted by the first identifier includes: the control signaling is associated with the first identifier.

[0221] As a sub-embodiment of this embodiment, the first identifier includes at least one of C-RNTI, or RA-RNTI, or MsgB-RNTI, or TC-RNTI, or PS-RNTI, or CS-RNTI(s), or SDT-RNTI, or IDT-RNTI, or PUR-RNTI, or I-RNTI, or S-RNTI.

[0222] As a sub-embodiment of this embodiment, the first identifier is only valid in the RRC_INACTIVE state.

[0223] As a sub-embodiment of this embodiment, the first identifier is only used for SDT.

[0224] As a sub-embodiment of this embodiment, the first identifier is associated with a first resource block used for SDT in the RRC_INACTIVE state, and the first resource block is configured through an RRCRelease message.

[0225] As an embodiment, the control signaling includes a reference signal.

[0226] As a sub-embodiment of this embodiment, the reference signal includes an SS / PBCH block.

[0227] As a sub-embodiment of this embodiment, the reference signal includes CSI-RS.

[0228] As a sub-embodiment of this embodiment, the reference signal includes an SSB (Synchronization Signal Block).

[0229] As a sub-embodiment of this embodiment, the reference signal includes a CSI-RS (Channel State Information Reference Signal) indexed by NZP-CSI-RS-ResourceId.

[0230] As a sub-embodiment of this embodiment, the reference signal includes an SSB indexed by SSB-Index.

[0231] As a sub-embodiment of this embodiment, the reference signal is used for measurement in an RRC inactive state or an RRC idle state.

[0232] As a sub-embodiment of this embodiment, the reference signal is configured through an IE in an RRC message, and the name of the IE includes MeasIdleConfig.

[0233] As a sub-embodiment of this embodiment, the reference signal is configured through a domain in an RRC message, and the name of the domain includes at least one of MeasIdleCarrierNR, or MeasIdleCarrierEUTRA, or BeamMeasConfigIdle-NR, or ssb-MeasConfig, or SSB-ToMeasure.

[0234] As a sub-embodiment of this embodiment, the reference signal includes one or more SSBs indicated in SSB-ToMeasure.

[0235] As an embodiment, the first time-frequency resource set includes at least one of time domain resources or frequency domain resources.

[0236] As an embodiment, the first time-frequency resource set includes a continuous period of time domain resources.

[0237] As an embodiment, the first time-frequency resource set includes a segment of non-continuous time domain resources.

[0238] As an embodiment, the first time-frequency resource set includes a continuous frequency domain resource.

[0239] As an embodiment, the first time-frequency resource set includes a segment of non-continuous frequency domain resources.

[0240] As an embodiment, the first time-frequency resource set is configured through an RRC message.

[0241] As an embodiment, the first time-frequency resource set is periodic.

[0242] As an embodiment, the first time-frequency resource set is non-periodic.

[0243] As an embodiment, the first time-frequency resource set includes one or more REs (Resource Element, information element).

[0244] As an embodiment, the first time-frequency resource set is allocated to a first search space.

[0245] As an embodiment, the first time-frequency resource set is configured through an IE in an RRC message, and the name of the IE includes ARFCN-ValueNR or ARFCN-ValueEUTRA.

[0246] As an embodiment, the first time-frequency resource set is configured through one or more domains in an RRC message, and the name of the one or more domains includes at least one of ValidityArea, or carrierFreq, or SubcarrierSpacing, or MultiFrequencyBandListNR, or carrierFreqEUTRA, or EUTRA-AllowedMeasBandwidth, or CellListEUTRA, or CellListNR.

[0247] As an embodiment, the first time-frequency resource set includes an NR global frequency raster.

[0248] As an embodiment, the first time-frequency resource set includes an E-UTRA carrier frequency.

[0249] As an embodiment, the first time-frequency resource set is associated with at least one cell.

[0250] As a sub-embodiment of this embodiment, the one cell includes a service cell of the first node, and the service cell includes at least one of a PCell, a PSCell, or a SCell.

[0251] As a sub-embodiment of this embodiment, the one cell includes a neighboring cell of the serving cell.

[0252] As an embodiment, the first time-frequency resource set is configured via an RRC message, and the RRC message includes MIB.

[0253] As an embodiment, the first time-frequency resource set is configured via an RRC message, and the RRC message includes SIB1.

[0254] As an embodiment, the first time-frequency resource set is configured through an RRC message, and the one RRC message includes RRCReconfiguration.

[0255] As an embodiment, the first time-frequency resource set is configured through an RRC message, and the RRC message includes RRCResume.

[0256] As an embodiment, the first time-frequency resource set is configured through an RRC message, and the RRC message includes RRCSetup.

[0257] As an embodiment, the first time-frequency resource set is configured through one or more IEs in an RRC message, and the names of the one or more IEs include CellGroupConfig, or ControlResourceSet, or ControlResourceSetZero, or ControlResourceSetId, or PDCCH-Config, or PDCCH-ConfigCommon, or PDCCH-ConfigSIB1, or BWP-DownlinkDedicated, or BWP-DownlinkCommon, or ServingCellConfig, or DownlinkConfigCommonSIB, or DownlinkConfigCommon, or ServingCellConfigCommonSIB.

[0258] As an embodiment, the first time-frequency resource set is configured through one or more domains in an RRC message, and the name of the one or more domains includes at least one of frequencyDomainResources, or duration, or cce-REG-MappingType, or precoderGranularity, or pdcch-DMRS-ScramblingID, or coresetPoolIndex, or controlResourceSetId.

[0259] As an embodiment, the phrase that the first time-frequency resource set is allocated to a first search space includes: the first search space is associated with the first time-frequency resource set.

[0260] As an embodiment, the phrase that the first time-frequency resource set is allocated to a first search space includes: the first search space corresponds to the first time-frequency resource set.

[0261] As an embodiment, the phrase that the first set of time-frequency resources is allocated to the first search space includes: the first set of time-frequency resources is a part of the time-frequency resources allocated to the first search space.

[0262] As an embodiment, the first search space includes a CSS (Common search space) set.

[0263] As an embodiment, the first search space includes a USS (UE-specific search space) set.

[0264] As an embodiment, the first search space includes a Type0-PDCCH CSS set.

[0265] As an embodiment, the first search space includes a Type0A-PDCCH CSS set.

[0266] As an embodiment, the first search space includes a Type1-PDCCH CSS set.

[0267] As an embodiment, the first search space includes a Type2-PDCCH CSS set.

[0268] As an embodiment, the first search space includes a Type3-PDCCH CSS set.

[0269] As an embodiment, the first search space includes a USS set.

[0270] As an embodiment, the first search space includes SearchSpace.

[0271] As an embodiment, the first search space is used to search for PDCCH candidates.

[0272] As an embodiment, the first time-frequency resource set includes ControlResourceSet.

[0273] As an embodiment, the first search space is associated with the first identifier.

[0274] As an embodiment, the first time-frequency resource set is used to configure a time (time) or frequency (frequency) control resource set (Control resource set, CORESET) for searching downlink control information.

[0275] As an embodiment, the downlink control information includes DCI.

[0276] As an embodiment, the downlink control information includes the control signaling.

[0277] As an embodiment, the downlink control information includes PDCCH candidates.

[0278] As an embodiment, the phrase that the time domain resources occupied by the second message are orthogonal to the time domain resources occupied by the first message includes: the second message and the first message are sent on different time domain resources.

[0279] As an embodiment, the phrase that the time domain resources occupied by the second message are orthogonal to the time domain resources occupied by the first message includes: the second message and the first message are not sent at the same time.

[0280] As an embodiment, the phrase that the time domain resources occupied by the second message are orthogonal to the time domain resources occupied by the first message includes: the time domain resources occupied by the first message are associated with the resource blocks configured by RRCRelease, and the time domain resources occupied by the second message are associated with the resource blocks scheduled by Msg2 or the resource blocks corresponding to MsgA.

[0281] As an embodiment, the phrase that the time domain resources occupied by the second message are orthogonal to the time domain resources occupied by the first message includes: the time domain resources occupied by the first message are associated with the resource block corresponding to MsgA, and the time domain resources occupied by the second message are associated with the resource block scheduled by Msg2.

[0282] As an embodiment, the phrase that the time domain resources occupied by the second message are orthogonal to the time domain resources occupied by the first message includes: the time domain resources occupied by the first message are associated with the resource blocks scheduled by Msg2, and the time domain resources occupied by the second message are associated with the resource blocks corresponding to MsgA.

[0283] As an embodiment, the frequency domain resources occupied by the second message are orthogonal to the frequency domain resources occupied by the first message.

[0284] As an embodiment, the frequency domain resources occupied by the second message overlap with the frequency domain resources occupied by the first message.

[0285] As an embodiment, the time domain resources occupied by the second message are not orthogonal to the time domain resources occupied by the first message.

[0286] As an embodiment, the first message is sent before the second message.

[0287] As an embodiment, the second message is sent before the first message.

[0288] As an embodiment, the message used to update the RRC connection includes: one of: RRCResume, or RRCRelease, or RRCSetup, or RRCReject.

[0289] As an embodiment, between sending the first message and sending the second message, the first node does not receive the message for updating the RRC connection.

[0290] As an embodiment, the sentence "between the sending of the first message and the sending of the second message, the first node did not receive the message for updating the RRC connection" includes: between the sending of the first message and the sending of the second message, the first node did not receive a response to the first message.

[0291] As an embodiment, the first RRC connection update is related to the RRC inactive state transmission data packet, and the second RRC connection update is not related to the RRC inactive state transmission data packet; the name of the third message is used to determine whether only the first message of the first message and the second message is used to trigger the third message or whether only the second message of the first message and the second message is used to trigger the third message.

[0292] As a sub-embodiment of this embodiment, when the name of the third message includes RRC and Release, only the first message among the first message and the second message is used to trigger the third message.

[0293] As a sub-embodiment of this embodiment, when the name of the third message includes RRC and Resume, only the second message of the first message and the second message is used to trigger the third message.

[0294] As a sub-embodiment of this embodiment, when the name of the third message includes RRC and Reject, only the second message of the first message and the second message is used to trigger the third message.

[0295] As a sub-embodiment of this embodiment, when the name of the third message includes RRC and Setup, only the second message of the first message and the second message is used to trigger the third message.

[0296] As an embodiment, the first node is in an RRC inactive state.

[0297] As an embodiment, the RRC inactive state includes RRC_INACTIVE.

[0298] As an embodiment, the RRC inactive state includes the RRC idle state.

[0299] Example 2

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

[0301] As an embodiment, the UE201 corresponds to the first node in the present application.

[0302] As an embodiment, the UE 201 is a user equipment (User Equipment, UE).

[0303] As an embodiment, the gNB203 corresponds to the second node in this application.

[0304] As an embodiment, the gNB203 is a base station device (BaseStation, BS).

[0305] As an embodiment, the gNB203 is a user equipment.

[0306] As an embodiment, the gNB203 is a relay.

[0307] As an embodiment, the gNB203 is a gateway.

[0308] As an embodiment, the user equipment supports transmission of a terrestrial network (Non-Terrestrial Network, NTN).

[0309] As an embodiment, the user equipment supports transmission of a non-terrestrial network (Terrestrial Network).

[0310] As an embodiment, the user equipment supports transmission in a network with a large delay difference.

[0311] As an embodiment, the user equipment supports dual connection (DC) transmission.

[0312] As an embodiment, the user equipment includes an aircraft.

[0313] As an embodiment, the user equipment includes a vehicle-mounted terminal.

[0314] As an embodiment, the user equipment includes a vessel.

[0315] As an embodiment, the user equipment includes an Internet of Things terminal.

[0316] As an embodiment, the user equipment includes a terminal of the industrial Internet of Things.

[0317] As an embodiment, the user equipment includes a device supporting low-latency and high-reliability transmission.

[0318] As an embodiment, the user equipment includes a test device.

[0319] As an embodiment, the user equipment includes a signaling tester.

[0320] As an embodiment, the user equipment includes an NB-IOT (Narrow Band Internet of Things) device.

[0321] As an embodiment, the user equipment includes an IAB (Integrated Access and Backhaul)-node.

[0322] As an embodiment, the user equipment includes an IAB-DU.

[0323] As an embodiment, the user equipment includes an IAB-MT.

[0324] As an embodiment, the base station device supports transmission in a non-terrestrial network.

[0325] As an embodiment, the base station device supports transmission in a network with a large delay difference.

[0326] As an embodiment, the base station device supports transmission of a terrestrial network.

[0327] As an embodiment, the base station device includes a macro cellular (Marco Cellular) base station.

[0328] As an embodiment, the base station device includes a micro cell base station.

[0329] As an embodiment, the base station device includes a pico cell (Pico Cell) base station.

[0330] As an embodiment, the base station device includes a home base station (Femtocell).

[0331] As an embodiment, the base station device includes a base station device that supports a large delay difference.

[0332] As an embodiment, the base station device includes a flying platform device.

[0333] As an embodiment, the base station device includes a satellite device.

[0334] As an embodiment, the base station device includes a TRP (Transmitter Receiver Point).

[0335] As an embodiment, the base station device includes a CU (Centralized Unit).

[0336] As an embodiment, the base station device includes a DU (Distributed Unit).

[0337] As an embodiment, the base station device includes a testing device.

[0338] As an embodiment, the base station equipment includes a signaling tester.

[0339] As an embodiment, the base station device includes an IAB-node.

[0340] As an embodiment, the base station device includes an IAB-donor.

[0341] As an embodiment, the base station device includes an IAB-donor-CU.

[0342] As an embodiment, the base station device includes an IAB-donor-DU.

[0343] As an embodiment, the base station device includes an IAB-DU.

[0344] As an embodiment, the base station device includes IAB-MT.

[0345] As an embodiment, the relay includes a relay.

[0346] As an embodiment, the relay includes an L3 relay.

[0347] As an embodiment, the relay includes an L2 relay.

[0348] As an embodiment, the relay includes a router.

[0349] As an embodiment, the relay includes a switch.

[0350] As an embodiment, the relay includes a user equipment.

[0351] As an embodiment, the relay includes a base station device.

[0352] Example 3

[0353] Embodiment 3 shows a schematic diagram of an embodiment of a wireless protocol architecture of a user plane and a control plane according to the present application, as shown in the attached Figure 3 shown. Figure 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300, Figure 3The radio protocol architecture for the control plane 300 is shown in three layers: Layer 1, Layer 2, and Layer 3. Layer 1 (L1 layer) is the lowest layer and implements various PHY (physical layer) signal processing functions. The L1 layer will be referred to as PHY 301 herein. 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 by encrypting data packets, and provides inter-zone mobility support. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to HARQ. The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) in a cell. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in layer 3 (L3 layer) in the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and using RRC signaling to configure lower layers. The radio protocol architecture of the user plane 350 includes layer 1 (L1 layer) and layer 2 (L2 layer). In the user plane 350, the radio protocol architecture is substantially the same as the corresponding layers and sublayers in the control plane 300 for the physical layer 351, the PDCP sublayer 354 in the L2 layer 355, the RLC sublayer 353 in the L2 layer 355, and the MAC sublayer 352 in the L2 layer 355, but the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead. The L2 layer 355 in the user plane 350 also includes a SDAP (Service Data Adaptation Protocol) sublayer 356. The SDAP sublayer 356 is responsible for mapping between QoS flows and data radio bearers (DRBs) to support service diversity.

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

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

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

[0357] As an embodiment, the first signaling in the present application is generated by the MAC302 or MAC352.

[0358] As an embodiment, the first signaling in the present application is generated in the PHY301 or PHY351.

[0359] As an embodiment, the second signaling in the present application is generated in the RRC306.

[0360] As an embodiment, the second signaling in the present application is generated by the MAC302 or MAC352.

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

[0362] As an embodiment, the first message in the present application is generated in the RRC306.

[0363] As an embodiment, the first message in the present application is generated by the MAC302 or MAC352.

[0364] As an embodiment, the first message in the present application is generated by the PHY301 or PHY351.

[0365] As an embodiment, the second message in the present application is generated in the RRC306.

[0366] As an embodiment, the second message in the present application is generated by the MAC302 or MAC352.

[0367] As an embodiment, the second message in the present application is generated by the PHY301 or PHY351.

[0368] As an embodiment, the third message in the present application is generated in the RRC306.

[0369] As an embodiment, the third message in the present application is generated by the MAC302 or MAC352.

[0370] As an embodiment, the third message in the present application is generated by the PHY301 or PHY351.

[0371] Example 4

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

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

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

[0375] In 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 the functionality of the L2 layer. In 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 retransmission of lost packets and signaling to the first communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., the physical layer). The transmit processor 416 implements coding and interleaving to facilitate forward error correction (FEC) at the second communication device 410, as well as mapping of signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing on the coded and modulated symbols to generate one or more spatial streams. The transmit processor 416 then maps each spatial stream to a subcarrier, multiplexes it with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then uses an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain multi-carrier symbol stream. The multi-antenna transmit processor 471 then performs a transmit analog precoding / beamforming operation on the time-domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multi-carrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream, and then provides it to a different antenna 420.

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

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

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

[0379] As an 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 together with the at least one processor, and the first communication device 450 at least: sends a first message and a second message; receives a third message, the third message is used to update the RRC connection; determines whether to execute a first set of actions according to whether a first set of conditions is satisfied; when the first set of conditions is satisfied, executes the first set of actions; wherein the first message is used to request a first RRC connection update, and the second message is used to request a second RRC connection update; the first set of conditions includes that one of the first message and the second message is used to trigger the third message; the behavior of executing the first set of actions includes monitoring control signaling in a first time-frequency resource set, the first time-frequency resource set is allocated to a first search space; the time domain resources occupied by the second message are orthogonal to the time domain resources occupied by the first message; between the sending of the first message and the sending of the second message, the first node did not receive a message for updating the RRC connection.

[0380] As an embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generates actions when executed by at least one processor, the actions including: sending a first message and a second message; receiving a third message, the third message being used to update the RRC connection; determining whether to execute a first set of actions based on whether a first set of conditions is met; executing the first set of actions when the first set of conditions is met; wherein the first message is used to request a first RRC connection update, and the second message is used to request a second RRC connection update; the first set of conditions includes one of the first message and the second message being used to trigger the third message; the behavior of executing the first set of actions includes monitoring control signaling in a first set of time-frequency resources, the first set of time-frequency resources being allocated to a first search space; the time domain resources occupied by the second message are orthogonal to the time domain resources occupied by the first message; between the sending of the first message and the sending of the second message, the first node did not receive a message for updating the RRC connection.

[0381] As an 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: receives a first message and a second message; sends a third message, the third message is used to update the RRC connection; wherein, whether the first action set is executed is determined according to whether the first condition set is satisfied; when the first condition set is satisfied, the first action set is executed; the first message is used to request a first RRC connection update, and the second message is used to request a second RRC connection update; the first condition set includes one of the first message and the second message being used to trigger the third message; the behavior of executing the first action set includes monitoring control signaling in a first time-frequency resource set, the first time-frequency resource set being allocated to a first search space; the time domain resources occupied by the second message are orthogonal to the time domain resources occupied by the first message; between the sending of the first message and the sending of the second message, the recipient of the third message did not receive the message for updating the RRC connection.

[0382] As an embodiment, the second communication device 410 includes: a memory storing a computer-readable instruction program, wherein the computer-readable instruction program generates actions when executed by at least one processor, the actions including: receiving a first message and a second message; sending a third message, wherein the third message is used to update the RRC connection; wherein whether the first action set is executed is determined based on whether the first condition set is satisfied; when the first condition set is satisfied, the first action set is executed; the first message is used to request a first RRC connection update, and the second message is used to request a second RRC connection update; the first condition set includes one of the first message and the second message being used to trigger the third message; the behavior of executing the first action set includes monitoring control signaling in a first time-frequency resource set, wherein the first time-frequency resource set is allocated to a first search space; the time domain resources occupied by the second message are orthogonal to the time domain resources occupied by the first message; between the sending of the first message and the sending of the second message, the recipient of the third message did not receive the message for updating the RRC connection.

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

[0384] As an embodiment, the antenna 452, the receiver 454, the receiving processor 456, and the controller / processor 459 are used to receive a second signaling; and at least one of the antenna 420, the transmitter 418, the transmitting processor 416, and the controller / processor 475 is used to send a second signaling.

[0385] As an embodiment, the antenna 452, the receiver 454, the receiving processor 456, and the controller / processor 459 are used to receive a third message; and at least one of the antenna 420, the transmitter 418, the transmitting processor 416, and the controller / processor 475 is used to send a third message.

[0386] As an implementation, the antenna 452, the transmitter 454, the transmit processor 468, and the controller / processor 459 are used to send a first message; and at least one of the antenna 420, the receiver 418, the receive processor 470, and the controller / processor 475 is used to receive a first message.

[0387] As an implementation, the antenna 452, the transmitter 454, the transmit processor 468, and the controller / processor 459 are used to send a second message; and at least one of the antenna 420, the receiver 418, the receive processor 470, and the controller / processor 475 is used to receive a second message.

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

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

[0390] As an embodiment, the first communication device 450 is a user equipment.

[0391] As an embodiment, the first communication device 450 is a user equipment supporting a large delay difference.

[0392] As an embodiment, the first communication device 450 is a user equipment supporting NTN.

[0393] As an embodiment, the first communication device 450 is an aircraft device.

[0394] As an embodiment, the first communication device 450 has a positioning capability.

[0395] As an embodiment, the first communication device 450 does not have a fixed energy capability.

[0396] As an embodiment, the first communication device 450 is a user equipment supporting TN.

[0397] As an embodiment, the second communication device 410 is a base station device (gNB / eNB / ng-eNB).

[0398] As an embodiment, the second communication device 410 is a base station device supporting a large delay difference.

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

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

[0401] As an embodiment, the second communication device 410 is a flying platform device.

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

[0403] Example 5

[0404] Embodiment 5 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in the attached Figure 5 It is particularly noted that the order in this example does not limit the signal transmission order and implementation order in this application.

[0405] for First node U01 In step S5101, a first message is sent; in step S5102, a second message is sent; in step S5103, a third message is received; in step S5104, whether a first set of conditions is satisfied is determined, and whether a first set of actions is executed based on whether the first set of conditions is satisfied; when the first set of conditions is satisfied, step S5105 is entered; when the first set of conditions is not satisfied, step S5106 is entered; in step S5105, the first set of actions is executed; in step S5106, the second set of actions is executed.

[0406] for Second node N02 In step S5201, the first message is received; in step S5202, the second message is received; in step S5203, the third message is sent.

[0407] In Example 5, the third message is used to update the RRC connection; the first message is used to request a first RRC connection update, and the second message is used to request a second RRC connection update; the first condition set includes one of the first message and the second message being used to trigger the third message; the behavior execution first action set includes monitoring control signaling in a first time-frequency resource set, and the first time-frequency resource set is allocated to a first search space; the time domain resources occupied by the second message are orthogonal to the time domain resources occupied by the first message; between the sending of the first message and the sending of the second message, the first node did not receive a message for updating the RRC connection.

[0408] As an embodiment, the behavior of executing the second action set includes: giving up executing all actions in the first action set.

[0409] As an embodiment, the behavior of executing the second action set includes: giving up executing some actions in the first action set.

[0410] As an embodiment, there is at least one different action in the second action set of the behavior execution and the first action set of the behavior execution.

[0411] As an embodiment, the second action set for executing the behavior and the first action set for executing the behavior contain a same action.

[0412] As an embodiment, there is no same action in the second action set executed by the behavior and in the first action set executed by the behavior.

[0413] As an embodiment, the sentence "When the first set of conditions is met, execute the first set of actions" includes: when the third message is received, if one of the first message and the second message is used to trigger the third message, monitor control signaling in the first time-frequency resource set.

[0414] As an embodiment, the sentence "When the first set of conditions is met, execute the first set of actions" includes: when the third message is received, if one of the first message and the second message is used to trigger the third message, and the first timer and the second timer in the present application are both running, monitor control signaling in the first time-frequency resource set and stop at least one of the first timer or the second timer.

[0415] As an embodiment, the sentence "When the first set of conditions is met, execute the first set of actions" includes: when the third message is received, if only the first message between the first message and the second message is used to trigger the third message, monitor control signaling in the first time-frequency resource set, and suspend the first DRB in this application.

[0416] As an embodiment, the sentence "When the first set of conditions is met, execute the first set of actions" includes: when the third message is received, if only the first message between the first message and the second message is used to trigger the third message, monitor control signaling in the first time-frequency resource set, stop the first timer, and suspend the first DRB in this application.

[0417] As an embodiment, the phrase and the name of the third message include RRC and Release, and the third message includes an RRCRelease message.

[0418] As an embodiment, the phrase wherein the name of the third message includes RRC and Release includes: the third message includes an RRCConnectionRelease message.

[0419] As an embodiment, the first condition set includes that the name of the third message includes RRC and Release.

[0420] As an embodiment, the phrase "the first condition set includes that the name of the third message includes RRC and Release" includes: when the first condition set includes that the name of the third message includes RRC and Release, the first condition set is satisfied.

[0421] As an embodiment, the phrase "the first condition set includes that the name of the third message includes RRC and Release" includes: when the first condition set includes that the name of the third message includes RRC and Release and the third message includes the first domain, the first condition set is satisfied.

[0422] As an embodiment, when one of the first message and the second message is used to trigger the third message, and the name of the third message includes RRC and Release, the first condition set is met.

[0423] As an embodiment, when only the first message among the first message and the second message is used to trigger the third message, and the name of the third message includes RRC and Release, the first condition set is satisfied.

[0424] As a sub-embodiment of this embodiment, the first action set includes monitoring control signaling in a first time-frequency resource set.

[0425] As a sub-embodiment of this embodiment, the first action set includes monitoring control signaling in a first time-frequency resource set and stopping at least one of the first timer or the second timer.

[0426] As a sub-embodiment of this embodiment, the first action set includes monitoring control signaling in a first time-frequency resource set and suspending the first DRB in this application.

[0427] As a sub-embodiment of this embodiment, the first action set includes monitoring control signaling in a first time-frequency resource set, stopping the first timer, and suspending the first DRB in this application.

[0428] As an embodiment, when only the second message among the first message and the second message is used to trigger the third message, and the name of the third message includes RRC and Release, the first condition set is satisfied.

[0429] As a sub-embodiment of this embodiment, the first action set includes monitoring control signaling in a first time-frequency resource set.

[0430] As a sub-embodiment of this embodiment, the first action set includes monitoring control signaling in a first time-frequency resource set and stopping at least one of the first timer or the second timer.

[0431] As a sub-embodiment of this embodiment, the first action set includes monitoring control signaling in a first time-frequency resource set and suspending the first DRB in this application.

[0432] As a sub-embodiment of this embodiment, the first action set includes monitoring control signaling in a first time-frequency resource set, stopping the first timer, and suspending the first DRB in this application.

[0433] As an embodiment, step S5101 is before step S5102.

[0434] As an embodiment, step S5101 is performed after step S5102.

[0435] Example 6

[0436] Embodiment 6 illustrates a wireless signal transmission flow chart according to another embodiment of the present application, as shown in the attached Figure 6 It is particularly noted that the order in this example does not limit the signal transmission order and implementation order in this application.

[0437] for First node U01 In step S6101, a first signaling is received; in step S6102, a second signaling is received; in step S6103, a first message is sent; in step S6104, a first timer is started; in step S6105, a second message is sent; in step S6106, a second timer is started; in step S6107, a third message is received; in step S6108, whether a first condition set is satisfied is determined, and whether a first action set is executed according to whether the first condition set is satisfied; when the first condition set is satisfied, the first action set is executed and the process goes to step S6109; when the first condition set is not satisfied, the process goes to step S6110; in step S6109, control signaling is monitored in a first time-frequency resource set; in step S6110, at least one of the first timer or the second timer is stopped; in step S6111, a second action set is executed.

[0438] for Second node N02 In step S6201, a first signaling is sent; in step S6202, a second signaling is sent; in step S6203, a first message is received; in step S6204, a second message is received; in step S6205, a third message is sent.

[0439] In Example 6, the first signaling indicates the expiration value of the first timer; the second signaling indicates the expiration value of the second timer; the third message is used to update the RRC connection; the first message is used to request a first RRC connection update, and the second message is used to request a second RRC connection update; the first condition set includes one of the first message and the second message being used to trigger the third message; the first time-frequency resource set is allocated to a first search space; the time domain resources occupied by the second message are orthogonal to the time domain resources occupied by the first message; between the sending of the first message and the sending of the second message, the first node did not receive a message for updating the RRC connection.

[0440] As an embodiment, the first condition set includes that both the first timer and the second timer are running.

[0441] As an embodiment, the first set of conditions being satisfied includes: one of the first message and the second message being used to trigger the third message.

[0442] As an embodiment, the first set of conditions being satisfied includes: one of the first message and the second message is used to trigger the third message, and both the first timer and the second timer are running.

[0443] As an embodiment, the first condition set is not satisfied including: the first timer or the second timer is not running.

[0444] As an embodiment, the first set of conditions not being met includes: neither the first message nor the second message is used to trigger the third message.

[0445] As an embodiment, the first set of conditions not being met includes: the third message is triggered by a message other than the first message and the second message.

[0446] As an embodiment, the behavior of executing the second action set includes: giving up executing the first action set.

[0447] As a sub-embodiment of this embodiment, the behavior of giving up executing the first action set includes: giving up executing all actions in the first action set.

[0448] As a sub-embodiment of this embodiment, the behavior of giving up executing the first action set includes: giving up executing some actions in the first action set.

[0449] As an embodiment, the behavior of executing the second action set includes: not stopping the first timer and the second timer.

[0450] As an embodiment, the behavior of executing the second action set includes: stopping the first timer and the second timer.

[0451] As an embodiment, the behavior performs the second action set and the behavior performs the first action set, and there is at least one different action.

[0452] As an embodiment, the second action set for executing the behavior and the first action set for executing the behavior have at least one same action.

[0453] As an embodiment, the second action set executed by the behavior does not have the same action as the first action set executed by the behavior.

[0454] As an embodiment, the behavior of executing the first action set includes monitoring control signaling in a first time-frequency resource set and stopping at least one of the first timer or the second timer.

[0455] As an embodiment, when the first timer is not running, the second timer is stopped.

[0456] As an embodiment, when the second timer is not running, the first timer is stopped.

[0457] As an embodiment, the first signaling is received in an RRC (Radio Resource Control) connection state.

[0458] As an embodiment, the first signaling is received in an RRC inactive state.

[0459] As an embodiment, the first signaling is sent through an antenna port.

[0460] As an embodiment, the signaling radio bearer of the first signaling includes N / A.

[0461] As an embodiment, the signaling radio bearer of the first signaling includes SRB1 (Signalling Radio Bearer 1).

[0462] As an embodiment, the logical channel of the first signaling includes BCCH (Broadcast Control Channel).

[0463] As an embodiment, the logical channel of the first signaling includes a DCCH (Dedicated Control Channel).

[0464] As an embodiment, the RLC-SAP of the first signaling includes AM.

[0465] As an embodiment, the RLC-SAP of the first signaling includes TM.

[0466] As an embodiment, the first signaling is delivered to a lower layer, and the lower layer includes at least one of a PDCP layer, an RLC layer, a MAC layer, or a PHY layer.

[0467] As an embodiment, the first signaling includes a downlink signaling.

[0468] As an embodiment, the first signaling includes all or part of higher layer signaling.

[0469] As an embodiment, the first signaling includes an RRC message.

[0470] As an embodiment, the first signaling includes an RRC message, and the name of the RRC message includes SIB1.

[0471] As an embodiment, the first signaling includes an RRC message, and the name of the RRC message includes RRCReconfiguration.

[0472] As an embodiment, the first signaling includes an RRC message, and the name of the RRC message includes RRCRelease.

[0473] As an embodiment, the first signaling includes an IE (Information Element) in an RRC message, and the name of the IE includes UE-TimersAndConstants.

[0474] As an embodiment, the first signaling includes a field (Field) in an RRC message, and the name of the field includes suspendConfig.

[0475] As an embodiment, the first signaling includes a field in an RRC message, and the name of the field includes the first timer.

[0476] As an embodiment, the phrase that the first signaling indicates the expiration value of the first timer includes: the expiration value of the first timer is configured through the first signaling.

[0477] As an embodiment, the phrase that the first signaling indicates the expiration value of the first timer includes: the expiration value of the first timer is a field in the first signaling.

[0478] As an embodiment, the second signaling is received in an RRC connected state.

[0479] As an embodiment, the second signaling is received in an RRC inactive state.

[0480] As an embodiment, the second signaling is sent through the antenna port.

[0481] As an embodiment, the signaling radio bearer of the second signaling includes N / A.

[0482] As an embodiment, the signaling radio bearer of the second signaling includes SRB1.

[0483] As an embodiment, the logical channel of the second signaling includes BCCH.

[0484] As an embodiment, the logical channel of the second signaling includes DCCH.

[0485] As an embodiment, the RLC-SAP of the second signaling includes AM.

[0486] As an embodiment, the RLC-SAP of the second signaling includes TM.

[0487] As an embodiment, the second signaling is delivered to a lower layer, and the lower layer includes at least one of a PDCP layer, an RLC layer, a MAC layer, or a PHY layer.

[0488] As an embodiment, the second signaling includes a downlink signaling.

[0489] As an embodiment, the second signaling includes all or part of higher layer signaling.

[0490] As an embodiment, the second signaling includes an RRC (Radio Resource Control) message.

[0491] As an embodiment, the second signaling includes an RRC message, and the name of the RRC message includes SIB1.

[0492] As an embodiment, the second signaling includes an RRC message, and the name of the RRC message includes RRCReconfiguration.

[0493] As an embodiment, the second signaling includes an RRC message, and the name of the RRC message includes RRCRelease.

[0494] As an embodiment, the second signaling includes an IE in an RRC message, and the name of the IE includes UE-TimersAndConstants.

[0495] As an embodiment, the second signaling includes a field in an RRC message, and the name of the field includes suspendConfig.

[0496] As an embodiment, the second signaling includes a field in an RRC message, and the name of the field includes the second timer.

[0497] As an embodiment, the first signaling and the second signaling are two different RRC messages.

[0498] As an embodiment, the first signaling and the second signaling are the same RRC message.

[0499] As an embodiment, the first signaling and the second signaling are two different fields in the same RRC message.

[0500] As an embodiment, the first signaling and the second signaling are two different IEs in the same RRC message.

[0501] As an embodiment, the first signaling and the second signaling have the same name.

[0502] As an embodiment, the names of the first signaling and the second signaling are different.

[0503] As an embodiment, the phrase that the second signaling indicates the expiration value of the second timer includes: the expiration value of the second timer is configured through the second signaling.

[0504] As an embodiment, the phrase that the second signaling indicates the expiration value of the second timer includes: the expiration value of the second timer is a field in the second signaling.

[0505] As an embodiment, when RNA update is performed, the first message is sent and the first timer is started.

[0506] As an embodiment, when requesting to resume a suspended RRC connection, the first message is sent and the first timer is started.

[0507] As an embodiment, when the SDT process is executed, the first message is sent and the first timer is started.

[0508] As an embodiment, when RNA update is performed, the second message is sent and the second timer is started.

[0509] As an embodiment, when requesting to resume a suspended RRC connection, the second message is sent and the second timer is started.

[0510] As an embodiment, when the SDT process is executed, the second message is sent and the second timer is started.

[0511] As an embodiment, the SDT process belongs to the recovery of a suspended RRC connection.

[0512] As an embodiment, the SDT process does not belong to the recovery of a suspended RRC connection.

[0513] As an embodiment, the SDT process and the resuming of a suspended RRC connection use the same RRC message name.

[0514] As an embodiment, the SDT process and the resuming of a suspended RRC connection use different RRC message names.

[0515] As an embodiment, the action of starting a first timer includes: the first timer starts timing.

[0516] As an embodiment, the action of starting the first timer includes: starting the first timer.

[0517] As an embodiment, the meaning of starting includes start.

[0518] As an embodiment, the starting means including restarting.

[0519] As an embodiment, the meaning of starting includes recovery.

[0520] As an embodiment, the first timer includes T319, and the second timer includes T3xy.

[0521] As an embodiment, the first timer includes T3xy, and the second timer includes T319.

[0522] As an embodiment, x is an integer not less than 0 and not more than 9, and y is an integer not less than 0 and not more than 9.

[0523] As an embodiment, at least one of the first timer and the second timer includes T319.

[0524] As a sub-embodiment of this embodiment, the first timer includes T319, and the second timer does not include T319.

[0525] As a sub-embodiment of this embodiment, the second timer includes T319, and the first timer does not include T319.

[0526] As a sub-embodiment of this embodiment, the first timer includes the T319, and the second timer includes the T319.

[0527] As a subsidiary embodiment of this sub-embodiment, the expiration value of the first timer and the expiration value of the second timer are not equal.

[0528] As a subsidiary embodiment of this sub-embodiment, the expiration value of the first timer is equal to the expiration value of the second timer.

[0529] As a subsidiary embodiment of this sub-embodiment, the expiration value of the first timer is equal to the expiration value of the second timer.

[0530] As an embodiment, at least one of the first timer or the second timer is an RRC layer timer.

[0531] As an embodiment, one of the first timer or the second timer is a PDCP layer timer.

[0532] As an embodiment, one of the first timer or the second timer is an RLC layer timer.

[0533] As an embodiment, one of the first timer or the second timer is a MAC layer timer.

[0534] As an embodiment, the first timer and the second timer are the same.

[0535] As an embodiment, the first timer and the second timer are different.

[0536] As an embodiment, the expiration value of the first timer and the expiration value of the second timer are not equal.

[0537] As an embodiment, the expiration value of the first timer is equal to the expiration value of the second timer.

[0538] As an embodiment, the first timer does not include T319, and the second timer includes T319.

[0539] As a sub-embodiment of this embodiment, the first node sends all or part of the data of the first message or the first DRB, and starts or restarts the first timer.

[0540] As a sub-embodiment of this embodiment, the first timer is stopped for each uplink transmission after the first message is sent.

[0541] As an embodiment, the first timer includes T319, and the second timer does not include T319.

[0542] As a sub-embodiment of this embodiment, the first node sends the second message or all or part of the data of the first DRB, and starts or restarts the second timer.

[0543] As a sub-embodiment of this embodiment, the second timer is stopped for each uplink transmission after the second message is sent.

[0544] As an embodiment, the phrase, the behavior, performing the first action set includes stopping at least one of the first timer or the second timer, includes: the behavior, performing the first action set includes stopping the first timer, and not stopping the second timer.

[0545] As an embodiment, the phrase, the behavior, performing the first action set includes stopping at least one of the first timer or the second timer, includes: the behavior, performing the first action set includes stopping the second timer, and not stopping the first timer.

[0546] As an embodiment, the phrase, the behavior, performing a first action set includes stopping at least one of the first timer or the second timer, includes: the behavior, performing a first action set includes stopping the first timer and the second timer.

[0547] As an embodiment, when the third message is a response to the first message, the first timer is stopped.

[0548] As an embodiment, when the third message is a response to the second message, the second timer is stopped.

[0549] As an embodiment, when the third message is a response to the first message, the first timer is stopped and the second timer is not stopped.

[0550] As an embodiment, when the third message is a response to the second message, the second timer is stopped and the first timer is not stopped.

[0551] As an embodiment, when the third message is a response to the first message, the first timer is stopped and the second timer is stopped.

[0552] As an embodiment, when the third message is a response to the second message, the second timer is stopped and the first timer is stopped.

[0553] As an embodiment, the first node receives a first signaling and a second signaling; sends a first message and starts a first timer; sends a second message and starts a second timer; receives a third message, wherein the third message is used to update an RRC connection; determines whether to execute a first set of actions based on whether a first set of conditions is satisfied; and executes the first set of actions when the first set of conditions is satisfied; wherein the first message is used to request an update of a first RRC connection; the second message is used to request an update of a second RRC connection; the first set of conditions includes that one of the first message and the second message is used to trigger the third message, and the first set of conditions includes that both the first timer and the second timer are running; the behavior of executing the first set of actions includes monitoring control signaling in a first set of time-frequency resources, and the behavior of executing the first set of actions includes stopping at least one of the first timer or the second timer, and the first set of time-frequency resources is allocated to a first search space; the time domain resources occupied by the second message are orthogonal to the time domain resources occupied by the first message; between the sending of the first message and the sending of the second message, the first node does not receive a message for updating the RRC connection; the first signaling indicates an expiration value of the first timer; the second signaling indicates the expiration value of the second timer.

[0554] As an embodiment, the first node receives a first signaling and a second signaling; sends a first message and starts a first timer; sends a second message and starts a second timer; receives a third message, wherein the third message is used to update the RRC connection; when one of the first message and the second message is used to trigger the third message, and both the first timer and the second timer are running, monitors control signaling in a first time-frequency resource set, and stops at least one of the first timer or the second timer; wherein the first message is used to request a first RRC connection update; the second message is used to request a second RRC connection update; the first time-frequency resource set is allocated to a first search space; the time domain resources occupied by the second message are orthogonal to the time domain resources occupied by the first message; between the sending of the first message and the sending of the second message, the first node did not receive a message for updating the RRC connection; the first signaling indicates an expiration value of the first timer; the second signaling indicates the expiration value of the second timer.

[0555] As an embodiment, the phrase that the first condition set includes that both the first timer and the second timer are running includes: the first timer is running, and the second timer is running.

[0556] As an embodiment, the phrase that the first condition set includes that both the first timer and the second timer are running includes that neither the first timer nor the second timer has expired.

[0557] As an embodiment, the phrase that the first condition set includes that both the first timer and the second timer are running includes that neither the first timer nor the second timer is stopped.

[0558] As an embodiment, the phrase that the first condition set includes that both the first timer and the second timer are running includes: before the third message is received, the first node has not received a message for updating the RRC connection.

[0559] As an embodiment, the expiration value of a timer includes a positive integer number of milliseconds, and the timer includes the first timer or the second timer.

[0560] As an embodiment, the expiration value of a timer includes a positive integer number of time slots, and the time slot includes a solt, or a radio subframe, or a radio frame, or a plurality of OFDM (Orthogonal Frequency Division Multiplexing) symbols, or at least one of a plurality of SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, and the timer includes the first timer or the second timer.

[0561] As an embodiment, the behavior of sending the first message is related to the behavior of starting the first timer, and the behavior of sending the first message is unrelated to the behavior of starting the second timer.

[0562] As a sub-embodiment of this embodiment, the first timer is associated with the first message.

[0563] As a sub-embodiment of this embodiment, when the first message is sent, the first timer is started.

[0564] As a sub-embodiment of this embodiment, after sending the first message, the first timer is started.

[0565] As a sub-embodiment of this embodiment, before sending the first message, the first timer is started.

[0566] As a sub-embodiment of this embodiment, when the first message is ready to be sent, the first timer is started.

[0567] As a sub-embodiment of this embodiment, the first timer is started before setting the content of the first message.

[0568] As a sub-embodiment of this embodiment, when the first RRC connection update is initiated, the first timer is started.

[0569] As an embodiment, the behavior of sending the second message is related to the behavior of starting the second timer, and the behavior of sending the second message is unrelated to the behavior of starting the first timer.

[0570] As a sub-embodiment of this embodiment, the second timer is associated with the second message.

[0571] As a sub-embodiment of this embodiment, when the second message is sent, the second timer is started.

[0572] As a sub-embodiment of this embodiment, after sending the second message, the second timer is started.

[0573] As a sub-embodiment of this embodiment, the second timer is started before sending the second message.

[0574] As a sub-embodiment of this embodiment, when the second message is ready to be sent, the second timer is started.

[0575] As a sub-embodiment of this embodiment, the second timer is started before setting the content of the second message.

[0576] As a sub-embodiment of this embodiment, when the second RRC connection update is initiated, the second timer is started.

[0577] As an embodiment, when preparing to send the second message, the second timer is started and the first timer is stopped.

[0578] As an embodiment, before setting the content of the second message, the second timer is started and the first timer is stopped.

[0579] As an embodiment, when the second RRC connection update is initiated, the second timer is started and the first timer is stopped.

[0580] As an embodiment, the behavior of sending the second message and starting the second timer includes: sending the second message, starting the second timer and stopping the first timer.

[0581] As an embodiment, the first node receives a first signaling and a second signaling; sends the first message and starts a first timer; sends the second message and starts a second timer and stops the first timer; wherein the behavior performs a first action set including stopping at least one of the first timer or the second timer; the first signaling indicates an expiration value of the first timer; and the second signaling indicates the expiration value of the second timer.

[0582] As an embodiment, step S6103 is before step S6104.

[0583] As an embodiment, step S6103 is after step S6104.

[0584] As an embodiment, step S6105 is before step S6106.

[0585] As an embodiment, step S6105 is after step S6106.

[0586] As an embodiment, step S6109 is before step S6110.

[0587] As an embodiment, step S6109 is after step S6110.

[0588] Example 7

[0589] Embodiment 7 illustrates a wireless signal transmission flow chart according to another embodiment of the present application, as shown in the attached Figure 7 It is particularly noted that the order in this example does not limit the signal transmission order and implementation order in this application.

[0590] for First node U01 In step S7101, when requesting the first RRC connection update, reconstruct the PDCP entity of SRB1 and restore the SRB1, reconstruct the PDCP entity of the first DRB and restore the first DRB; in step S7102, send a first message; in step S7103, send a second message; in step S7104, receive a third message; in step S7105, determine whether the first condition set is met, and determine whether to execute the first action set based on whether the first condition set is met. When the first condition set is met, execute the first action set and enter step S7106; in step S7106, monitor control signaling in the first time-frequency resource set; in step S7107, suspend the first DRB; in step S7108, restore the first bearer; in step S7109, execute the second action set.

[0591] for Second node N02 In step S7201, the first message is received; in step S7202, the second message is received; in step S7203, the third message is sent.

[0592] In Embodiment 7, the first condition set includes that only the first message of the first message and the second message is used to trigger the third message; the third message is used to update the RRC connection; the first message is used to request a first RRC connection update, and the second message is used to request a second RRC connection update; the first time-frequency resource set is allocated to a first search space; the time domain resources occupied by the second message are orthogonal to the time domain resources occupied by the first message; and between the sending of the first message and the sending of the second message, the first node did not receive a message for updating the RRC connection.

[0593] As an embodiment, the first DRB is used for SDT.

[0594] As an embodiment, the first DRB is a DRB.

[0595] As an embodiment, the first DRB is configured through an RRCRelease message.

[0596] As an embodiment, the first DRB includes an SDT-DRB.

[0597] As an embodiment, the first DRB is associated with a DRB-Identity, and the DRB-Identity is an integer greater than 0 and not greater than 32.

[0598] As an embodiment, the first DRB is associated with a LogicalChannelIdentity, the LogicalChannelIdentity is an integer greater than 0 and not greater than maxLC-ID, and the maxLC-ID is a positive integer.

[0599] As an embodiment, the first DRB is configured through PDCP-Config.

[0600] As an embodiment, the first DRB is configured through SecurityConfig.

[0601] As an embodiment, the first node saves the first configuration set of the first DRB in the RRC_INACTIVE state.

[0602] As a sub-embodiment of this embodiment, the first configuration set includes RLC configuration.

[0603] As a sub-embodiment of this embodiment, the first configuration set includes an IE or a domain in an RRC message, and the name of the IE or the domain includes one of SDAP-Config, or RLC-BearerConfig, or RLC-Config, or RadioBearerConfig, or SecurityConfig, or eps-BearerIdentity, or recoverPDCP, or PDCP-Config, or keyToUse, or SecurityAlgorithmConfig, or discardTimer, or pdcp-SN-SizeUL, or pdcp-SN-SizeDL, or headerCompression, or drb-ContinueEHC-DL, or drb-ContinueEHC-UL, or LogicalChannelConfig.

[0604] As a sub-embodiment of this embodiment, the first configuration set includes multiple IEs or multiple domains in an RRC message, and the names of the multiple IEs or the multiple domains include at least one of SDAP-Config, or RLC-BearerConfig, or RLC-Config, or RadioBearerConfig, or SecurityConfig, or eps-BearerIdentity, or recoverPDCP, or PDCP-Config, or keyToUse, or SecurityAlgorithmConfig, or discardTimer, or pdcp-SN-SizeUL, or pdcp-SN-SizeDL, or headerCompression, or drb-ContinueEHC-DL, or drb-ContinueEHC-UL, or LogicalChannelConfig.

[0605] As an embodiment, the SRB1 includes signaling radio bearer 1.

[0606] As an embodiment, the SRB1 is an SRB.

[0607] As an embodiment, the SRB1 is associated to the DCCH.

[0608] As an embodiment, the action of re-establishing the PDCP entities for SRB1 includes: re-establishing PDCP entities for SRB1.

[0609] As an embodiment, the action of re-establishing the PDCP entities for the first DRB includes: re-establishing PDCP entities for the first DRB.

[0610] As an embodiment, the action of resuming the SRB1 includes: resume SRB1.

[0611] As an embodiment, the action of restoring the first DRB includes: resume the first DRB.

[0612] As an embodiment, the re-establishment includes re-establishment.

[0613] As an embodiment, the recovery includes resume.

[0614] As an embodiment, when the RRC connection recovery process is initiated, the PDCP entity of SRB1 is rebuilt and the SRB1 is restored; the PDCP entity of the first DRB is rebuilt and the first DRB is restored.

[0615] As an embodiment, when the SDT process is initiated, the PDCP entity of SRB1 is rebuilt and the SRB1 is restored; the PDCP entity of the first DRB is rebuilt and the first DRB is restored.

[0616] As an embodiment, before delivering the first message to the lower layer, the PDCP entity of SRB1 is rebuilt and the SRB1 is restored; the PDCP entity of the first DRB is rebuilt and the first DRB is restored.

[0617] As an embodiment, when the content of the first message is set, the PDCP entity of SRB1 is rebuilt and the SRB1 is restored; the PDCP entity of the first DRB is rebuilt and the first DRB is restored.

[0618] As an embodiment, when the content of the first message is set, the PDCP entity of SRB1 is rebuilt and the SRB1 is restored; the PDCP entity of the first DRB is rebuilt and the first DRB is restored.

[0619] As an embodiment, when it is determined to send the first message, the PDCP entity of SRB1 is rebuilt and the SRB1 is restored; the PDCP entity of the first DRB is rebuilt and the first DRB is restored.

[0620] As an embodiment, when requesting a first RRC connection update, the first node reconstructs the PDCP entity of SRB1 and restores the SRB1, reconstructs the PDCP entity of the first DRB and restores the first DRB, sends a first message and starts a first timer; when requesting a second RRC connection update, the first node sends a second message and starts the second timer.

[0621] As a sub-embodiment of this embodiment, the first RRC connection update is related to the RRC inactive state transmission data packet, and the second RRC connection update is not related to the RRC inactive state transmission data packet.

[0622] As a sub-embodiment of this embodiment, the first timer includes T3xy, and the second timer includes T319.

[0623] As an embodiment, when requesting a first RRC connection update, the first node reconstructs the PDCP entity of SRB1 and restores the SRB1, sends a first message and starts a first timer; when requesting a second RRC connection update, the first node sends a second message and starts the second timer, reconstructs the PDCP entity of the first DRB and restores the first DRB.

[0624] As a sub-embodiment of this embodiment, the first RRC connection update is independent of the RRC inactive state transmission data packet, and the second RRC connection update is related to the RRC inactive state transmission data packet.

[0625] As a sub-embodiment of this embodiment, the first timer includes T319, and the second timer includes T3xy.

[0626] As an embodiment, the behavior of performing a first set of actions includes suspending the first DRB.

[0627] As an embodiment, the meaning of suspending includes suspend.

[0628] As an embodiment, the behavior of performing the first action set includes indicating to a lower layer the PDCP suspension of the first DRB.

[0629] As an embodiment, the behavior of performing a first set of actions includes reestablishing the RLC entity of the first DRB.

[0630] As an embodiment, the behavior of performing the first action set includes at least one of reestablishing the RLC entity of the first DRB, or suspending the first DRB, or indicating the PDCP suspension of the first DRB to a lower layer.

[0631] As an embodiment, the first condition set includes that the name of the third message includes RRC and Release.

[0632] As an embodiment, the first RRC connection update is related to the RRC inactive state transmission data packet, and the second RRC connection update is not related to the RRC inactive state transmission data packet; the first condition set includes that only the first message of the first message and the second message is used to trigger the third message, and the first condition set includes that the name of the third message includes RRC and Release; the behavior execution first action set includes suspending the first DRB.

[0633] As an embodiment, the first RRC connection update is related to the RRC inactive state transmission data packet, and the second RRC connection update is not related to the RRC inactive state transmission data packet; the first condition set includes that only the second message of the first message and the second message is used to trigger the third message, and the first condition set includes that the name of the third message includes RRC and Release; the behavior execution first action set does not include suspending the first DRB.

[0634] As an embodiment, the first RRC connection update is related to the RRC inactive state transmission data packet, and the second RRC connection update is not related to the RRC inactive state transmission data packet; the first condition set includes that only the first message of the first message and the second message is used to trigger the third message, and the first condition set includes that the name of the third message includes RRC and Release; the behavior execution first action set includes suspending the first DRB, and does not include suspending the SRB1.

[0635] As an embodiment, the first RRC connection update is related to the RRC inactive state transmission data packet, and the second RRC connection update is not related to the RRC inactive state transmission data packet; the first condition set includes that only the second message of the first message and the second message is used to trigger the third message, and the first condition set includes that the name of the third message includes RRC and Release; the behavior execution first action set does not include suspending the first DRB, and does not suspend the SRB1.

[0636] As an embodiment, the phrase that only the first message among the first message and the second message is used to trigger the third message includes: the third message is a response to the first message.

[0637] As an embodiment, the phrase that only the second message among the first message and the second message is used to trigger the third message includes: the third message is a response to the second message.

[0638] As an embodiment, the behavior of performing a first set of actions includes suspending the first DRB.

[0639] As a sub-embodiment of this embodiment, the first condition set includes that the name of the third message includes RRC and Release.

[0640] As a sub-embodiment of this embodiment, the first condition set includes that the third message includes RRCRelease.

[0641] As an embodiment, the behavior of performing a first action set includes restoring a first bearer; the first bearer is a bearer other than the first DRB and the SRB1.

[0642] As a sub-embodiment of this embodiment, the first condition set includes that the name of the third message includes RRC and Resume.

[0643] As a sub-embodiment of this embodiment, the first condition set includes that the third message includes RRCResume.

[0644] As an embodiment, the phrase that the first bearer is a bearer other than the first DRB and the SRB1 includes: the first bearer is not the SRB1, and the first bearer is not the first DRB.

[0645] As an embodiment, the phrase that the first bearer is a bearer other than the first DRB and the SRB1 includes: the first bearer does not include the first DRB and the SRB1.

[0646] As an embodiment, the first bearer includes a radio bearer (Radio Bearer, RB).

[0647] As an embodiment, the first bearer includes a signaling radio bearer.

[0648] As an embodiment, the first bearer includes a data radio bearer (Data Radio Bearer, DRB).

[0649] As an embodiment, the first bearer includes SRB2 (Signaling Radio Bearer 2).

[0650] As an embodiment, the first bearer includes SRB3 (Signaling Radio Bearer 3).

[0651] As an embodiment, the first bearer includes a DRB other than the first DRB.

[0652] As an embodiment, the first bearer includes all DRBs other than the first DRB.

[0653] As an embodiment, the first bearer includes all DRBs except the currently restored DRB.

[0654] As an embodiment, the first bearer includes all DRBs except the first type of DRBs, the first type of DRBs are used for SDT, and the first type of DRBs include the first DRBs.

[0655] As an embodiment, the dashed box F7.1 is optional.

[0656] As an embodiment, the dashed box F7.2 is optional.

[0657] As an embodiment, the dashed box F7.1 exists.

[0658] As an embodiment, the dotted box F7.1 does not exist.

[0659] As an embodiment, the dashed box F7.2 exists.

[0660] As an embodiment, the dotted box F7.2 does not exist.

[0661] As an embodiment, one of the dotted box F7.1 and the dotted box F7.2 exists.

[0662] As a sub-embodiment of this embodiment, the dotted box F7.1 exists, and the dotted box F7.2 does not exist.

[0663] As a sub-embodiment of this embodiment, the dotted box F7.1 does not exist, and the dotted box F7.2 exists.

[0664] As an embodiment, step S7101 is before step S7102.

[0665] As an embodiment, step S7101 is performed after step S7102.

[0666] As an embodiment, step S7106 is before step S7107.

[0667] As an embodiment, step S7106 is performed after step S7107.

[0668] As an embodiment, step S7106 is before step S7108.

[0669] As an embodiment, step S7106 is performed after step S7108.

[0670] Example 8

[0671] Embodiment 8 illustrates a schematic diagram of executing a first action set including stopping a first timer according to an embodiment of the present application, as shown in the attached Figure 8 As shown in the attached Figure 8 In the figure, the horizontal axis represents time, the box filled with slashes represents the first timer, and the box filled with diamonds represents the second timer; t8.1, t8.2 and t8.3 are three moments increasing in time; at moment t8.1, the first timer is started; at moment t8.2, the second timer is started; at moment t8.3, the third message is received and the first timer is stopped.

[0672] In Embodiment 8, the first condition set includes that only the first message of the first message and the second message is used to trigger the third message.

[0673] As an embodiment, the time interval between the time t8.1 and the time t8.3 is less than the expiration value of the first timer.

[0674] As an embodiment, the time interval between the time t8.2 and the time t8.3 is less than the expiration value of the second timer.

[0675] As an embodiment, the third message is a response to the first message.

[0676] As an embodiment, the first message is sent and a first timer is started; the second message is sent and a second timer is started; a third message is received, and the third message is used to update the RRC connection; when only the first message between the first message and the second message is used to trigger the third message, control signaling is monitored in a first time-frequency resource set, and the first timer is stopped.

[0677] As a sub-embodiment of this embodiment, the first RRC connection update is related to the RRC inactive state transmission data packet, and the second RRC connection update is not related to the RRC inactive state transmission data packet.

[0678] As a sub-embodiment of this embodiment, the third message includes RRCRelease.

[0679] As a sub-embodiment of this embodiment, the third message includes one of RRCResume, or RRCSetup, or RRCReject.

[0680] As a sub-embodiment of this embodiment, the name of the third message includes at least one of RRC or SDT or IDT or Inactive or Small or Data or Transmission or Complete.

[0681] As a sub-embodiment of this embodiment, the second timer is not stopped.

[0682] As a sub-embodiment of this embodiment, the control signaling is associated with a PDCCH scrambled by a C-RNTI.

[0683] As a sub-embodiment of this embodiment, the control signaling is associated with a PDCCH scrambled by RA-RNTI.

[0684] As a sub-embodiment of this embodiment, the control signaling is associated with a PDCCH scrambled by MsgB-RNTI.

[0685] As a sub-embodiment of this embodiment, the control signaling is associated with a PDCCH scrambled by a TC-RNTI.

[0686] As a sub-embodiment of this embodiment, the control signaling is associated with a PDCCH scrambled by a CS-RNTI.

[0687] As a sub-embodiment of this embodiment, the control signaling is associated with a fourth message, and the fourth message is a response to the second message.

[0688] Example 9

[0689] Embodiment 9 illustrates a schematic diagram of executing a first action set including stopping a second timer according to an embodiment of the present application, as shown in the attached Fig. 9 As shown in the attached Fig. 9 In the figure, the horizontal axis represents time, the box filled with slashes represents the first timer, and the box filled with diamonds represents the second timer; t9.1, t9.2 and t9.3 are three moments increasing in time; at moment t9.1, the first timer is started; at moment t9.2, the second timer is started; at moment t9.3, the third message is received and the second timer is stopped.

[0690] In Embodiment 9, the first condition set includes that of the first message and the second message, only the second message is used to trigger the third message.

[0691] As an embodiment, the time interval between the time t9.1 and the time t9.3 is less than the expiration value of the first timer.

[0692] As an embodiment, the time interval between the time t9.2 and the time t9.3 is less than the expiration value of the second timer.

[0693] As an embodiment, the third message is a response to the second message.

[0694] As an embodiment, the first message is sent and a first timer is started; the second message is sent and a second timer is started; a third message is received, and the third message is used to update the RRC connection; when only the second message among the first message and the second message is used to trigger the third message, control signaling is monitored in a first time-frequency resource set, and the second timer is stopped.

[0695] As a sub-embodiment of this embodiment, the first RRC connection update is related to the RRC inactive state transmission data packet, and the second RRC connection update is not related to the RRC inactive state transmission data packet.

[0696] As a sub-embodiment of this embodiment, the third message includes RRCRelease.

[0697] As a sub-embodiment of this embodiment, the third message includes one of RRCResume, or RRCSetup, or RRCReject.

[0698] As a sub-embodiment of this embodiment, the name of the third message includes at least one of RRC or SDT or IDT or Inactive or Small or Data or Transmission or Complete.

[0699] As a sub-embodiment of this embodiment, the first timer is not stopped.

[0700] As a sub-embodiment of this embodiment, the control signaling is associated with a PDCCH scrambled by a C-RNTI.

[0701] As a sub-embodiment of this embodiment, the control signaling is associated with a PDCCH scrambled by RA-RNTI.

[0702] As a sub-embodiment of this embodiment, the control signaling is associated with a PDCCH scrambled by MsgB-RNTI.

[0703] As a sub-embodiment of this embodiment, the control signaling is associated with a PDCCH scrambled by a TC-RNTI.

[0704] As a sub-embodiment of this embodiment, the control signaling is associated with a PDCCH scrambled by a CS-RNTI.

[0705] As a sub-embodiment of this embodiment, the control signaling is associated with the PDCCH scrambled by the CG-RNTI.

[0706] As a sub-embodiment of this embodiment, the control signaling is associated with a PDCCH scrambled by an SDT-RNTI, an IDT-RNTI, a PUR-RNTI, an I-RNTI, or an S-RNTI.

[0707] As a sub-embodiment of this embodiment, the control signaling is associated with a fourth message, and the fourth message is a response to the first message.

[0708] Example 10

[0709] Embodiment 10 illustrates a schematic diagram of executing a first action set including stopping a first timer and a second timer according to an embodiment of the present application. Fig.10 In the figure, the horizontal axis represents time, the box filled with slashes represents the first timer, and the box filled with diamonds represents the second timer; t10.1, t10.2 and t10.3 are three moments increasing in time; at moment t10.1, the first timer is started; at moment t10.2, the second timer is started; at moment t10.3, the third message is received and the first timer and the second timer are stopped.

[0710] In Embodiment 10, the first set of conditions includes that one of the first message and the second message is used to trigger the third message.

[0711] As an embodiment, the time interval between the time t10.1 and the time t10.3 is less than the expiration value of the first timer.

[0712] As an embodiment, the time interval between the time t10.2 and the time t10.3 is less than the expiration value of the second timer.

[0713] As an embodiment, the first condition set includes that only the first message of the first message and the second message is used to trigger the third message.

[0714] As an embodiment, the first condition set includes that of the first message and the second message, only the second message is used to trigger the third message.

[0715] As an embodiment, the third message is a response to the first message or the third message is a response to the second message.

[0716] As an embodiment, the first message is sent and a first timer is started; the second message is sent and a second timer is started; a third message is received, and the third message is used to update the RRC connection; when one of the first message and the second message is used to trigger the third message, control signaling is monitored in a first time-frequency resource set, and the first timer and the second timer are stopped.

[0717] As an embodiment, the first message is sent and a first timer is started; the second message is sent and a second timer is started; a third message is received, and the third message is used to update the RRC connection; when only the first message between the first message and the second message is used to trigger the third message, control signaling is monitored in a first time-frequency resource set, and the first timer and the second timer are stopped.

[0718] As a sub-embodiment of this embodiment, the first RRC connection update is related to the RRC inactive state transmission data packet, and the second RRC connection update is not related to the RRC inactive state transmission data packet.

[0719] As a sub-embodiment of this embodiment, the third message includes RRCRelease.

[0720] As a sub-embodiment of this embodiment, the third message includes one of RRCResume, or RRCSetup, or RRCReject.

[0721] As a sub-embodiment of this embodiment, the name of the third message includes at least one of RRC or SDT or IDT or Inactive or Small or Data or Transmission or Complete.

[0722] As an embodiment, the first message is sent and a first timer is started; the second message is sent and a second timer is started; a third message is received, and the third message is used to update the RRC connection; when only the second message among the first message and the second message is used to trigger the third message, control signaling is monitored in a first time-frequency resource set, and the first timer and the second timer are stopped.

[0723] As a sub-embodiment of this embodiment, the first RRC connection update is related to the RRC inactive state transmission data packet, and the second RRC connection update is not related to the RRC inactive state transmission data packet.

[0724] As a sub-embodiment of this embodiment, the third message includes one of RRCResume, or RRCSetup, or RRCReject.

[0725] As a sub-embodiment of this embodiment, the third message includes RRCRelease.

[0726] As a sub-embodiment of this embodiment, the name of the third message includes at least one of RRC or SDT or IDT or Inactive or Small or Data or Transmission or Complete.

[0727] As a sub-embodiment of this embodiment, as an embodiment, the control signaling includes a reference signal.

[0728] As a sub-embodiment of this embodiment, the reference signal includes at least one of SS / PBCH block, or CSI-RS, or SSB (Synchronization Signal Block), or a CSI-RS (Channel State Information Reference Signal) indexed by NZP-CSI-RS-ResourceId, or an SSB indexed by SSB-Index.

[0729] As a sub-embodiment of this embodiment, the reference signal includes a paging message.

[0730] As a sub-embodiment of this embodiment, the control signaling includes DCI (Downlink Control Information, downlink control information).

[0731] As a sub-embodiment of this embodiment, the control signaling includes PDCCH (Physical Downlink Control Channel).

[0732] As a sub-embodiment of this embodiment, the control signaling includes a PDCCH candidate (Candidate).

[0733] As a sub-embodiment of this embodiment, the control signaling is scrambled by the first identifier.

[0734] Embodiment 11

[0735] Embodiment 11 illustrates a schematic diagram of a third message including a first domain according to an embodiment of the present application, as shown in the attached Fig.11 shown.

[0736] In embodiment 11, the third message includes a first field, and the first field is used to determine whether only the first message of the first message and the second message is used to trigger the third message or whether only the second message of the first message and the second message is used to trigger the third message.

[0737] As an embodiment, the phrase first domain is used to determine whether only the first message of the first message and the second message is used to trigger the third message or whether only the second message of the first message and the second message is used to trigger the third message, including: the first domain is used to determine that the third message is a response to the first message or the third message is a response to the second message.

[0738] As an embodiment, the phrase first domain is used to determine that the third message is a response to the first message or the third message is a response to the second message, including: the first domain explicitly indicates that the third message is a response to the first message or the third message is a response to the second message.

[0739] As a sub-embodiment of this embodiment, the first field includes an integer, the integer includes 1 bit, the integer is set to 1 to indicate that the third message is a response to the first message, and the integer is set to 0 to indicate that the third message is a response to the second message.

[0740] As a sub-embodiment of this embodiment, the first field includes an integer, the integer includes 1 bit, the integer is set to 0 to indicate that the third message is a response to the first message, and the integer is set to 1 to indicate that the third message is a response to the second message.

[0741] As a sub-embodiment of this embodiment, the first field includes an integer, the integer includes greater than 1 bit, the integer is set to a first integer to indicate that the third message is a response to the first message, the one bit is set to a second integer to indicate that the third message is a response to the second message, the first integer and the second integer are different, and the first integer and the second integer are respectively an integer.

[0742] As a sub-embodiment of this embodiment, the first field is set to indicate that the third message is a response to the first message, and the first field is not set to indicate that the third message is a response to the second message.

[0743] As a sub-embodiment of this embodiment, the first field is not set to indicate that the third message is a response to the first message, and the first field is set to indicate that the third message is a response to the second message.

[0744] As an embodiment, the phrase the first domain is used to determine that the third message is a response to the first message or the third message is a response to the second message, including: the first domain implicitly indicates that the third message is a response to the first message or the third message is a response to the second message.

[0745] As a sub-embodiment of this embodiment, the first field includes suspendConfig indicating that the third message is a response to the first message.

[0746] As a sub-embodiment of this embodiment, the first field includes suspendConfig indicating that the third message is a response to the second message.

[0747] The first field is used to determine whether the third message is a response to the first message or whether the third message is a response to the second message.

[0748] Example 12

[0749] Embodiment 12 illustrates a schematic diagram of a method in which the number of messages received for updating an RRC connection according to an embodiment of the present application is used to determine whether only the first message is used to trigger the third message, as shown in the attached figure. Fig.12 shown.

[0750] In embodiment 12, whether only the first message of the first message and the second message is used to trigger the third message is determined based on the number of messages used for updating the RRC connection received between the reception of the reference message and the third message; wherein the reference message is the later one of the first message and the second message.

[0751] As an embodiment, when the number of messages received between the reception of the reference message and the reception of the third message used for updating the RRC connection is equal to 0, whether only the first message among the first message and the second message is used to trigger the third message.

[0752] As an embodiment, when the number of messages received between the reception of the reference message and the third message used for updating the RRC connection is equal to 1, whether only the first message among the first message and the second message is used to trigger the third message.

[0753] As an embodiment, the first message is sent before the second message, and the reference message includes the second message.

[0754] As a sub-embodiment of this embodiment, when the number of messages received between the reception of the reference message and the third message used for updating the RRC connection is equal to 0, whether only the first message among the first message and the second message is used to trigger the third message.

[0755] As a sub-embodiment of this embodiment, when the number of messages received between the reception of the reference message and the third message used for updating the RRC connection is equal to 1, whether only the second message among the first message and the second message is used to trigger the third message.

[0756] As an embodiment, the first message is sent after the second message, and the reference message includes the first message.

[0757] As a sub-embodiment of this embodiment, when the number of messages received between the reception of the reference message and the third message used for updating the RRC connection is equal to 1, whether only the first message among the first message and the second message is used to trigger the third message.

[0758] As a sub-embodiment of this embodiment, when the number of messages received between the reception of the reference message and the third message used for updating the RRC connection is equal to 0, whether only the second message among the first message and the second message is used to trigger the third message.

[0759] As an embodiment, the message used for updating the RRC connection includes one of RRCRelease, or RRCResume, or RRCSetup, or RRCReject.

[0760] As an embodiment, the name of the message used for updating the RRC connection includes at least one of RRC or SDT or IDT or Inactive or Small or Data or Transmission or Complete.

[0761] Example 13

[0762] Embodiment 13 illustrates a structural block diagram of a processing device used in a first node according to an embodiment of the present application; Fig.13 As shown in the attached Fig.13 In the embodiment, the processing device 1300 in the first node includes a first receiver 1301 and a first transmitter 1302.

[0763] A first transmitter 1302 sends a first message and a second message;

[0764] The first receiver 1301 receives a third message, where the third message is used to update the RRC connection; determines whether to execute a first action set according to whether a first condition set is satisfied; and executes the first action set when the first condition set is satisfied;

[0765] In Example 13, the first message is used to request a first RRC connection update, and the second message is used to request a second RRC connection update; the first condition set includes one of the first message and the second message being used to trigger the third message; the behavior execution first action set includes monitoring control signaling in a first time-frequency resource set, and the first time-frequency resource set is allocated to a first search space; the time domain resources occupied by the second message are orthogonal to the time domain resources occupied by the first message; between the sending of the first message and the sending of the second message, the first node did not receive a message for updating the RRC connection.

[0766] As an embodiment, the first receiver 1301 receives a first signaling and a second signaling; the first transmitter 1302 sends the first message and starts a first timer; sends the second message and starts a second timer; wherein the behavior performs a first action set including stopping at least one of the first timer or the second timer; the first signaling indicates an expiration value of the first timer; and the second signaling indicates the expiration value of the second timer.

[0767] As an embodiment, the first transmitter 1302, when requesting the first RRC connection update, reconstructs the PDCP entity of SRB1 and restores the SRB1, reconstructs the PDCP entity of the first DRB and restores the first DRB; wherein, the first condition set includes that only the first message among the first message and the second message is used to trigger the third message.

[0768] As an embodiment, the behavior of performing a first set of actions includes suspending the first DRB.

[0769] As an embodiment, the behavior of performing a first action set includes restoring a first bearer; the first bearer is a bearer other than the first DRB and the SRB1.

[0770] As an embodiment, the first receiver 1301 determines whether only the first message of the first message and the second message is used to trigger the third message based on the number of messages used for updating the RRC connection received between the reception of the reference message and the third message; wherein the reference message is the later one of the first message and the second message.

[0771] As an embodiment, the third message includes a first field, and the first field is used to determine whether only the first message of the first message and the second message is used to trigger the third message or whether only the second message of the first message and the second message is used to trigger the third message.

[0772] As an embodiment, the first receiver 1301 includes the attached Figure 4 Antenna 452, receiver 454, multi-antenna reception processor 458, reception processor 456, controller / processor 459, memory 460 and data source 467.

[0773] As an embodiment, the first receiver 1301 includes the attached Figure 4 Antenna 452, receiver 454, multi-antenna receive processor 458, and receive processor 456.

[0774] As an embodiment, the first receiver 1301 includes the attached Figure 4 Antenna 452, receiver 454, and receive processor 456.

[0775] As an embodiment, the first transmitter 1302 includes the attached Figure 4 Antenna 452, transmitter 454, multi-antenna transmit processor 457, transmit processor 468, controller / processor 459, memory 460 and data source 467.

[0776] As an embodiment, the first transmitter 1302 includes the attached Figure 4 Antenna 452, transmitter 454, multi-antenna transmit processor 457, and transmit processor 468.

[0777] As an embodiment, the first transmitter 1302 includes the attached Figure 4 Antenna 452, transmitter 454, and transmit processor 468.

[0778] Embodiment 14

[0779] Embodiment 14 illustrates a structural block diagram of a processing device used in a second node according to an embodiment of the present application; Fig.14 As shown in the attached Fig.14 In the embodiment, the processing device 1400 in the second node includes a second transmitter 1401 and a second receiver 1402.

[0780] A second receiver 1402 receives a first message and a second message;

[0781] The second transmitter 1401 sends a third message, where the third message is used to update the RRC connection;

[0782] In Example 14, whether a first action set is executed is determined based on whether a first condition set is met; when the first condition set is met, the first action set is executed; the first message is used to request a first RRC connection update, and the second message is used to request a second RRC connection update; the first condition set includes one of the first message and the second message being used to trigger the third message; the behavior of executing the first action set includes monitoring control signaling in a first time-frequency resource set, and the first time-frequency resource set is allocated to a first search space; the time domain resources occupied by the second message are orthogonal to the time domain resources occupied by the first message; between the sending of the first message and the sending of the second message, the recipient of the third message did not receive the message for updating the RRC connection.

[0783] As an embodiment, whether the first action set is executed by the first node is determined according to whether the first condition set is satisfied.

[0784] As an embodiment, when the first set of conditions is met, the first set of actions is executed by the first node.

[0785] As an embodiment, the second transmitter 1401 sends a first signaling and a second signaling; the second receiver 1402 receives the first message; receives the second message; wherein, the first timer is started, and the second timer is started; the behavior performs a first action set including stopping at least one of the first timer or the second timer; the first signaling indicates the expiration value of the first timer; and the second signaling indicates the expiration value of the second timer.

[0786] As an embodiment, the first timer is started by the first node.

[0787] As an embodiment, the second timer is started by the second node.

[0788] As an embodiment, when the first RRC connection update is requested, the PDCP entity of SRB1 is rebuilt and the SRB1 is restored, the PDCP entity of the first DRB is rebuilt and the first DRB is restored; wherein, the first condition set includes that only the first message among the first message and the second message is used to trigger the third message.

[0789] As an embodiment, when the first RRC connection update is requested by the first node, the PDCP entity of SRB1 is rebuilt by the first node and the SRB1 is restored by the first node, and the PDCP entity of the first DRB is rebuilt by the first node and the first DRB is restored by the first node.

[0790] As an embodiment, the behavior of performing a first set of actions includes suspending the first DRB.

[0791] As an embodiment, the behavior of performing a first action set includes restoring a first bearer; the first bearer is a bearer other than the first DRB and the SRB1.

[0792] As an embodiment, whether only the first message among the first message and the second message is used to trigger the third message is determined based on the number of messages used for updating the RRC connection received between the reception of the reference message and the third message; wherein, the reference message is the message sent later between the first message and the second message.

[0793] As an embodiment, the third message includes a first field, and the first field is used to determine whether only the first message of the first message and the second message is used to trigger the third message or whether only the second message of the first message and the second message is used to trigger the third message.

[0794] As an embodiment, the second transmitter 1401 includes the attached Figure 4 Antenna 420, transmitter 418, multi-antenna transmit processor 471, transmit processor 416, controller / processor 475, and memory 476.

[0795] As an embodiment, the second transmitter 1401 includes the attached Figure 4 Antenna 420, transmitter 418, multi-antenna transmit processor 471, and transmit processor 416.

[0796] As an embodiment, the second transmitter 1401 includes the attached Figure 4 Antenna 420, transmitter 418, and transmit processor 416.

[0797] As an embodiment, the second receiver 1402 includes the attached Figure 4 Antenna 420, receiver 418, multi-antenna reception processor 472, reception processor 470, controller / processor 475, and memory 476.

[0798] As an embodiment, the second receiver 1402 includes the attached Figure 4 Antenna 420, receiver 418, multi-antenna receive processor 472, receive processor 470.

[0799] As an embodiment, the second receiver 1402 includes the attached Figure 4 Antenna 420, receiver 418, and receive processor 470.

[0800] Embodiment 15

[0801] Embodiment 15 illustrates a schematic diagram of a second message including a first MAC CE according to an embodiment of the present application, as shown in the attached Fig.15 shown.

[0802] As an embodiment, the first RRC connection update is related to the RRC inactive state transmission data packet, and the second RRC connection update is not related to the RRC inactive state transmission data packet.

[0803] As an embodiment, the second message includes a MAC PDU (Protocol Data Unit).

[0804] As an embodiment, the second message includes a MAC sub-PDU (subPDU).

[0805] As an embodiment, the second message includes multiple MAC sub-PDUs.

[0806] As an embodiment, the second message includes a MAC subheader.

[0807] As an embodiment, the second message includes a first MAC CE (Control Element).

[0808] As an embodiment, the second message includes C-RNTI MAC CE and the second message does not include CCCH SDU (Service Data Unit).

[0809] As an embodiment, the second message includes CCCH SDU and the second message does not include C-RNTI MAC CE.

[0810] As an embodiment, the second message includes C-RNTI MAC CE and the second message includes CCCHSDU.

[0811] As an embodiment, the first MAC CE is triggered when an indication is received from an upper layer, and the upper layer includes an RRC layer.

[0812] As an embodiment, the first MAC CE is prioritized in logical channel prioritization in a higher order than BFRMAC CE or Configured Grant Confirmation MAC CE or Multiple Entry ConfiguredGrant Confirmation MAC CE.

[0813] As an embodiment, the order in which the first MAC CE is prioritized in logical channel prioritization is the same as the order of C-RNTI MAC CE or the order of data from UL-CCCH.

[0814] As an embodiment, the order in which the first MAC CE is prioritized in logical channel prioritization is not higher than the order of C-RNTI MAC CE or is the same as the order of data from UL-CCCH.

[0815] As an embodiment, when requesting to resume a suspended RRC connection, if SDT is being performed, the RRC layer of the first node sends the indication to a lower layer of the first node.

[0816] As a sub-embodiment of this embodiment, the lower layer includes a protocol layer below the RRC layer.

[0817] As a sub-embodiment of this embodiment, the lower layer includes a MAC layer.

[0818] As an embodiment, when requesting the second RRC connection update, if SDT is being performed, the RRC layer of the first node sends an indication to a lower layer of the first node.

[0819] As an embodiment, when requesting to resume a suspended RRC connection, if SDT is being executed, the RRC layer of the first node sends the indication to the lower layer of the first node and starts the second timer.

[0820] As an embodiment, when requesting a second RRC connection update, if SDT is being executed, the RRC layer of the first node sends the one indication to the lower layer of the first node and starts the second timer.

[0821] As an embodiment, the first timer being running is used to determine that the SDT is being executed.

[0822] As an embodiment, the first DRB is recovered and used to determine that SDT is being executed.

[0823] As an embodiment, the second message includes a first MAC CE, the first MAC CE includes field #1, and the field #1 indicates the reason for resuming an RRC connection.

[0824] As a sub-embodiment of this embodiment, the field #1 includes Resume Cause.

[0825] As a sub-embodiment of this embodiment, the field #1 includes 3 bits.

[0826] As a sub-embodiment of this embodiment, the field #1 includes 4 bits.

[0827] As a sub-embodiment of this embodiment, a value corresponding to the 3 bits or the 4 bits indicates a reason for restoring an RRC connection.

[0828] As a sub-embodiment of this embodiment, the field #1 includes 1 bitmap.

[0829] As a sub-embodiment of this embodiment, the length of the bit map is equal to 8 bits.

[0830] As a sub-embodiment of this embodiment, the length of the bit map is equal to 16 bits.

[0831] As a sub-embodiment of this embodiment, one bit in the bitmap corresponds to a reason for restoring an RRC connection.

[0832] As a sub-embodiment of this embodiment, one bit in the bit map is set to 1 to indicate that the reason for resuming an RRC connection is the reason for resuming an RRC connection corresponding to the bit set to 1, and the other bits are set to 0.

[0833] As a sub-embodiment of this embodiment, the reason for restoring an RRC connection includes one of emergency, or highPriorityAccess, or mt-Access, or mo-Signalling, or mo-Data, or mo-VoiceCall, or mo-VideoCall, or mo-SMS, or rna-Update, or mps-PriorityAccess, or mcs-PriorityAccess, or sdt, or idt.

[0834] As a sub-embodiment of this embodiment, the reason for resuming an RRC connection is the same as the reason for resuming an RRC connection corresponding to a value in the ResumeCause IE.

[0835] As an embodiment, the second message includes a first MAC CE, the first MAC CE includes a field #2, and the field #2 indicates an authentication token (Authentication token) for implementing UE authentication at the second node.

[0836] As a sub-embodiment of this embodiment, the domain #2 includes resumeMAC-I.

[0837] As a sub-embodiment of this embodiment, the field #2 includes the lowest 16 bits of the MAC-I calculated using the AS security configuration.

[0838] As a sub-embodiment of this embodiment, the field #2 includes the lowest 8 bits of the MAC-I calculated using the AS security configuration.

[0839] As a sub-embodiment of this embodiment, the field #2 occupies 16 bits.

[0840] As a sub-embodiment of this embodiment, the field #2 occupies 8 bits.

[0841] As an embodiment, the second message includes a first MAC CE, the first MAC CE includes field #3, and the field #3 indicates a user identifier.

[0842] As a sub-embodiment of this embodiment, the user identifier includes I-RNTI-Value.

[0843] As a sub-embodiment of this embodiment, the user identifier includes ShortI-RNTI-Value.

[0844] As a sub-embodiment of this embodiment, the field #3 occupies 24 bits.

[0845] As a sub-embodiment of this embodiment, the field #3 occupies 40 bits.

[0846] As an embodiment, the second message includes a first MAC CE, the first MAC CE includes field #4, and the field #4 includes an R (Reserved) field.

[0847] As a sub-embodiment of this embodiment, the R field includes 1 bit.

[0848] As a sub-embodiment of this embodiment, the R field includes 2 bits.

[0849] As a sub-embodiment of this embodiment, the R field includes 3 bits.

[0850] As a sub-embodiment of this embodiment, the R field includes 4 bits.

[0851] As an embodiment, the second message includes a first MAC CE, the first MAC CE includes 1 byte, and the one byte includes 8 bits.

[0852] As an embodiment, the second message includes a first MAC CE, the first MAC CE includes 2 bytes, and the one byte includes 16 bits.

[0853] As an embodiment, the second message includes a first MAC CE, and the first MAC CE includes at least one of the domain #1, the domain #2, the domain #3, or the domain #4.

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

[0855] The above is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A first node used for wireless communication, characterized in that: include: A first transmitter sends a first message and a second message; A first receiver receives a third message, where the third message is used to update the RRC connection; Determine whether to execute a first action set according to whether a first condition set is satisfied; when the first condition set is satisfied, execute the first action set; Among them, the first message is used to request a first RRC connection update, and the second message is used to request a second RRC connection update; the first condition set includes that one of the first message and the second message is used to trigger the third message; the execution of the first action set includes monitoring control signaling in a first time-frequency resource set, and the first time-frequency resource set is allocated to a first search space; the time domain resources occupied by the second message are orthogonal to the time domain resources occupied by the first message; between the sending of the first message and the sending of the second message, the first node did not receive a message for updating the RRC connection.

2. The first node according to claim 1, characterized in that: include: The first receiver receives the first signaling and the second signaling; The first transmitter sends the first message and starts a first timer; Sending the second message and starting a second timer; The executing of the first action set includes stopping at least one of the first timer or the second timer; the first signaling indicates the expiration value of the first timer; and the second signaling indicates the expiration value of the second timer.

3. The first node according to claim 2, characterized in that: include: The first transmitter, when requesting the first RRC connection update, reestablishes the PDCP entity of SRB1 and restores the SRB1, reestablishes the PDCP entity of the first DRB and restores the first DRB; The first condition set includes that only the first message of the first message and the second message is used to trigger the third message.

4. The first node according to claim 3, characterized in that: The performing of the first set of actions includes suspending the first DRB.

5. The first node according to claim 3, characterized in that: The executing the first action set includes restoring a first bearer; the first bearer is a bearer other than the first DRB and the SRB1.

6. The first node according to any one of claims 1 to 5, characterized in that: include: The first receiver determines, based on the number of messages used for updating the RRC connection received between the reference message and the reception of the third message, whether only the first message of the first message and the second message is used to trigger the third message; The reference message is a message sent later between the first message and the second message.

7. The first node according to any one of claims 1 to 5, characterized in that: The third message includes a first field, and the first field is used to determine whether only the first message of the first message and the second message is used to trigger the third message or whether only the second message of the first message and the second message is used to trigger the third message.

8. A second node used for wireless communication, characterized in that: include: A second receiver receives the first message and the second message; A second transmitter sends a third message, where the third message is used to update the RRC connection; Wherein, determining whether the first action set is executed according to whether the first condition set is satisfied; When the first condition set is met, the first action set is executed; the first message is used to request a first RRC connection update, and the second message is used to request a second RRC connection update; the first condition set includes one of the first message and the second message being used to trigger the third message; the execution of the first action set includes monitoring control signaling in a first time-frequency resource set, and the first time-frequency resource set is allocated to a first search space; the time domain resources occupied by the second message are orthogonal to the time domain resources occupied by the first message; between the sending of the first message and the sending of the second message, the recipient of the third message did not receive the message for updating the RRC connection.

9. The second node according to claim 8, characterized in that: The second transmitter sends the first signaling and the second signaling; The second receiver receives the first message; receives the second message; Among them, the first timer is started, and the second timer is started; the execution of the first action set includes stopping at least one of the first timer or the second timer; the first signaling indicates the expiration value of the first timer; the second signaling indicates the expiration value of the second timer.

10. The second node according to claim 9, characterized in that: When the first RRC connection update is requested, the PDCP entity of SRB1 is rebuilt and the SRB1 is restored, the PDCP entity of the first DRB is rebuilt and the first DRB is restored; wherein, the first condition set includes that only the first message among the first message and the second message is used to trigger the third message.

11. The second node according to claim 10, characterized in that: The performing of the first set of actions includes suspending the first DRB.

12. The second node according to claim 10, characterized in that: The executing the first action set includes restoring a first bearer; the first bearer is a bearer other than the first DRB and the SRB1.

13. The second node according to any one of claims 8 to 12, characterized in that: Whether only the first message among the first message and the second message is used to trigger the third message is determined based on the number of messages used for updating the RRC connection received between the reception of the reference message and the third message; wherein the reference message is the message sent later among the first message and the second message.

14. The second node according to any one of claims 8 to 12, characterized in that: The third message includes a first field, and the first field is used to determine whether only the first message of the first message and the second message is used to trigger the third message or whether only the second message of the first message and the second message is used to trigger the third message.

15. A method in a first node for wireless communication, characterized in that: include: Sending a first message and a second message; receiving a third message, wherein the third message is used to update the RRC connection; Determine whether to execute a first action set according to whether a first condition set is satisfied; when the first condition set is satisfied, execute the first action set; Among them, the first message is used to request a first RRC connection update, and the second message is used to request a second RRC connection update; the first condition set includes that one of the first message and the second message is used to trigger the third message; the execution of the first action set includes monitoring control signaling in a first time-frequency resource set, and the first time-frequency resource set is allocated to a first search space; the time domain resources occupied by the second message are orthogonal to the time domain resources occupied by the first message; between the sending of the first message and the sending of the second message, the first node did not receive a message for updating the RRC connection.

16. The method in the first node according to claim 15, characterized in that: include: receiving a first signaling and a second signaling; Sending the first message and starting a first timer; sending the second message and starting a second timer; The executing of the first action set includes stopping at least one of the first timer or the second timer; the first signaling indicates the expiration value of the first timer; and the second signaling indicates the expiration value of the second timer.

17. The method in the first node according to claim 16, characterized in that: include: When requesting the first RRC connection update, reestablishing the PDCP entity of SRB1 and restoring the SRB1, reestablishing the PDCP entity of the first DRB and restoring the first DRB; The first condition set includes that only the first message of the first message and the second message is used to trigger the third message.

18. The method in the first node according to claim 17, characterized in that: The performing of the first set of actions includes suspending the first DRB.

19. The method in the first node according to claim 17, characterized in that: The executing the first action set includes restoring a first bearer; the first bearer is a bearer other than the first DRB and the SRB1.

20. The method in the first node according to any one of claims 15 to 19, characterized in that: include: determining whether only the first message of the first message and the second message is used to trigger the third message according to the number of messages used for updating the RRC connection received between the reference message and the reception of the third message; The reference message is a message sent later between the first message and the second message.

21. The method in the first node according to any one of claims 15 to 19, characterized in that: The third message includes a first field, and the first field is used to determine whether only the first message of the first message and the second message is used to trigger the third message or whether only the second message of the first message and the second message is used to trigger the third message.

22. A method in a second node for wireless communication, characterized in that: include: receiving a first message and a second message; Sending a third message, where the third message is used to update the RRC connection; Wherein, determining whether the first action set is executed according to whether the first condition set is satisfied; When the first condition set is met, the first action set is executed; the first message is used to request a first RRC connection update, and the second message is used to request a second RRC connection update; the first condition set includes one of the first message and the second message being used to trigger the third message; the execution of the first action set includes monitoring control signaling in a first time-frequency resource set, and the first time-frequency resource set is allocated to a first search space; the time domain resources occupied by the second message are orthogonal to the time domain resources occupied by the first message; between the sending of the first message and the sending of the second message, the recipient of the third message did not receive the message for updating the RRC connection.

23. The method in the second node according to claim 22, characterized in that: include: Sending a first signaling and a second signaling; receiving the first message; receiving the second message; Among them, the first timer is started, and the second timer is started; the execution of the first action set includes stopping at least one of the first timer or the second timer; the first signaling indicates the expiration value of the first timer; the second signaling indicates the expiration value of the second timer.

24. The method in the second node according to claim 23, characterized in that: When the first RRC connection update is requested, the PDCP entity of SRB1 is rebuilt and the SRB1 is restored, the PDCP entity of the first DRB is rebuilt and the first DRB is restored; wherein, the first condition set includes that only the first message among the first message and the second message is used to trigger the third message.

25. The method in the second node according to claim 24, characterized in that: The performing of the first set of actions includes suspending the first DRB.

26. The method in the second node according to claim 24, characterized in that: The executing the first action set includes restoring a first bearer; the first bearer is a bearer other than the first DRB and the SRB1.

27. The method in the second node according to any one of claims 22 to 26, characterized in that: Whether only the first message among the first message and the second message is used to trigger the third message is determined according to the number of messages used for updating the RRC connection received between reception of the reference message and the third message; The reference message is a message sent later between the first message and the second message.

28. The method in the second node according to any one of claims 22 to 26, characterized in that: The third message includes a first field, and the first field is used to determine whether only the first message of the first message and the second message is used to trigger the third message or whether only the second message of the first message and the second message is used to trigger the third message.

Images