Method and apparatus in communication node used for wireless communication

Abstract

The invention discloses a method and an apparatus in a communication node used for wireless communication. A communication node receives a first message, the first message comprising at least a first information block, the first information block comprising at least a first identifier, the first identifier being associated to the first node, the first information block being indicated to perform data transmission in an RRC inactive state; determining to execute data transmission in the RRC inactive state if any condition in the first condition set is not satisfied as a response to the reception of the first message; if each condition in the first condition set is satisfied, determining that the data transmission in the RRC inactive state is not executed; the first condition set comprises that the first message comprises a second information block, the second information block comprises at least a second identifier, the second identifier is associated to the first node, and the second information block is not indicated to perform data transmission in the RRC inactive state.

Description

[0001] This application is a divisional application of the following original application:

[0002] -- Filing date of original application: June 20, 2022

[0003] --Application number of the original application: 202210698146.2

[0004] --Title of the invention of the original application: A method and device used in a communication node for wireless communication Technical Field

[0005] The present application relates to a transmission method and apparatus in a wireless communication system, and in particular to a transmission method and apparatus in an RRC inactive state. Background Art

[0006] NR (New Radio) supports RRC (Radio Resource Control) inactive (RRC_INACTIVE) RRC state. Until 3GPP (the 3rd Generation Partnership Project) Rel-16 version, it does not support sending or receiving data in RRC inactive state. Rel-17 carried out the "NR Inactive State Small Data Transmission (SDT)" work item (Work Item, WI), and formulated corresponding technical specifications for MO (UL (Uplink))-SDT, allowing small packet transmission (small packet transmission) of uplink (UL-oriented) packets (packets) in RRC inactive state. In order to reduce power consumption, reduce signaling overhead and shorten latency, Rel-18 established the "MT (DL (Downlink))-SDT (Mobile Terminated-Small Data Transmission)" work project to study the triggering mechanism of MT-SDT, support RA (Random Access)-SDT and CG (Configured Grant)-SDT as uplink responses, and study the MT-SDT process for initial downlink data reception (initial DL data reception) and subsequent uplink or downlink data transmissions (subsequent UL / DL data transmissions) in the RRC inactive state. Rel-17 launched a work item (WI) on “MBS (Multicast / Broadcast Service) Reception in RRC Connected State”. To reduce power consumption, signaling overhead and latency, Rel-18 established a work item on “Enhancements of NR Multicast and Broadcast Services” to study MBS reception in RRC inactive state. Summary of the invention

[0007] In the existing protocol, after receiving a paging message in the RRC inactive state, the UE initiates the RRC recovery process and enters the RRC connected state to perform data transmission. How to trigger MT-SDT through a downlink message and how to determine the radio bearer used for MT-SDT need to be enhanced; similarly, how to trigger MBS reception in the RRC inactive state through a downlink message and how to determine the radio bearer used for MBS reception in the RRC inactive state need to be enhanced; further, when MT-SDT and MBS reception in the RRC inactive state coexist, the trigger mechanism needs to be enhanced.

[0008] In response to the above problems, the present application provides a solution for performing data transmission in the RRC inactive state. In the description of the above problems, the NR system is used as an example; the present application is also applicable to scenarios such as the LTE (Long-Term Evolution) system; further, although the original intention of the present application is for the Uu air interface, the present application can also be used for the PC5 port. Furthermore, although the original intention of the present application is for the terminal and base station scenario, the present application is also applicable to the V2X (Vehicle-to-Everything) scenario, the communication scenario between the terminal and the relay, and the relay and the base station, to achieve similar technical effects in the terminal and base station scenario. Furthermore, although the original intention of the present application is for the terminal and base station scenario, the present application is also applicable to the IAB (Integrated Access and Backhaul) communication scenario, to achieve similar technical effects in the terminal and base station scenario. Furthermore, although the original intention of this application is for terrestrial network scenarios, this application is also applicable to non-terrestrial network (NTN) communication scenarios, achieving similar technical effects in TN scenarios. In addition, adopting a unified solution for different scenarios also helps reduce hardware complexity and costs.

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

[0010] 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.

[0011] 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.

[0012] 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).

[0013] 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.

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

[0015] receiving a first message, the first message comprising at least a first information block, the first information block comprising at least a first identifier, the first identifier being associated with the first node, the first information block being indicated to perform data transmission in an RRC inactive state; determining, in response to the first message being received, whether to perform data transmission in the RRC inactive state according to whether a first condition set is satisfied;

[0016] Among them, the first condition set includes: the first message includes a second information block, the second information block includes at least a second identifier, the second identifier is associated with the first node, and the second information block is not indicated to perform data transmission in the RRC inactive state; the behavior determines whether to perform data transmission in the RRC inactive state according to whether the first condition set is met, including: if any condition in the first condition set is not met, determine to perform data transmission in the RRC inactive state; if each condition in the first condition set is met, determine that data transmission in the RRC inactive state is not performed.

[0017] As an embodiment, the problem to be solved by the present application includes: how to trigger the transmission for unicast (Unicast) and multicast (Multicast) through a first message.

[0018] As an embodiment, the problem to be solved by the present application includes: how to realize data transmission in the RRC inactive state triggered by a first message.

[0019] As an embodiment, the problem to be solved by the present application includes: how to determine whether to perform data transmission in the RRC inactive state.

[0020] As an embodiment, the problem to be solved by the present application includes: how to shorten the transmission delay.

[0021] As an embodiment, the problem to be solved by the present application includes: how to reduce state transitions.

[0022] As an embodiment, the problem to be solved by the present application includes: how to reduce signaling overhead.

[0023] As an embodiment, the characteristics of the above method include: when the first message includes multiple identifiers associated with the first node, and the information block associated with at least one of the multiple identifiers indicates that the first node transmits data in the RRC inactive state, determining whether to perform data transmission in the RRC inactive state based on the number of information blocks indicating that the first node transmits data in the RRC inactive state.

[0024] As an embodiment, the benefits of the above method include: if at least the first information block and the second information block both indicate that the first node performs data transmission in the RRC inactive state, the transmission delay is shortened, the state transition is reduced, and the signaling overhead is reduced by performing data transmission in the RRC inactive state.

[0025] As an embodiment, the benefits of the above method include: taking into account data transmission that cannot be executed in the RRC inactive state, and shortening the transmission delay of data that cannot be executed in the RRC inactive state.

[0026] According to one aspect of the present application, it is characterized in that the first identifier is used to indicate the first node, and the second identifier indicates an MBS session (Session) in which the first node participates.

[0027] According to one aspect of the present application, it is characterized in that the first identifier indicates an MBS session in which the first node participates, and the second identifier is used to indicate the first node.

[0028] According to one aspect of the present application, it is characterized in that the first identifier indicates an MBS session in which the first node participates, and the second identifier indicates another MBS session in which the first node participates.

[0029] According to one aspect of the present application, it is characterized in that the first information block is configured with a first indication which is used to determine that the first information block is instructed to perform data transmission in the RRC inactive state.

[0030] According to one aspect of the present application, it is characterized in that the second information block is not configured with a second indication which is used to determine that the second information block does not indicate data transmission in the RRC inactive state.

[0031] As an embodiment, the first indication and the second indication are different.

[0032] As an embodiment, the first indication and the second indication are the same.

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

[0034] If it is determined to perform data transmission in the RRC inactive state, sending a second message; along with the second message, restoring each radio bearer in the first radio bearer set, or, along with the first data block, restoring each radio bearer in the first radio bearer set;

[0035] The second message is used to request the restoration of the RRC connection; the first radio bearer set includes at least one DRB ((user) Data Radio Bearer) of the first node or SRB2 (Signalling Radio Bearer 2) of the first node or at least one multicast MRB (MBS Radio Bearer) of the first node; the first message is received within the time interval between the restoration of each radio bearer in the first radio bearer set, and the first node does not receive any RRC message indicating that the first node restores the RRC connection.

[0036] As an embodiment, the first data block is received as a response to the second message being sent; the first data block includes at least user data.

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

[0038] If it is determined that data transmission in the RRC inactive state is not performed, sending a fourth message; receiving a third message as a response to the fourth message being sent; and resuming each radio bearer in the second radio bearer set as a response to the third message being received;

[0039] The fourth message is used to request the restoration of the RRC connection; the second radio bearer set includes all DRBs of the first node or at least one of all multicast MRBs of the first node; within the time interval between the first message being received and the third message being received, any radio bearer in the second radio bearer set is not restored; and the third message instructs the first node to restore the RRC connection.

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

[0041] Sending a first message, the first message including at least a first information block, the first information block including at least a first identifier, the first identifier being associated with a first node, and the first information block being indicated to perform data transmission in an RRC inactive state;

[0042] Among them, the first node is a recipient of the first message; whether the first condition set is satisfied is used to determine whether data transmission in the RRC inactive state is executed; the first condition set includes: the first message includes a second information block, the second information block includes at least a second identifier, the second identifier is associated with the first node, and the second information block is not indicated to perform data transmission in the RRC inactive state; the phrase whether the first condition set is satisfied is used to determine whether data transmission in the RRC inactive state is executed includes: the first condition set is satisfied and is used to determine that data transmission in the RRC inactive state is executed; the first condition set is not satisfied and is used to determine that data transmission in the RRC inactive state is not executed.

[0043] According to one aspect of the present application, it is characterized in that the first identifier is used to indicate a recipient of the first message, and the second identifier indicates an MBS session in which the recipient of the first message participates.

[0044] According to one aspect of the present application, it is characterized in that the first identifier indicates an MBS session in which the first node participates, and the second identifier is used to indicate the first node.

[0045] According to one aspect of the present application, it is characterized in that the first identifier indicates an MBS session in which the first node participates, and the second identifier indicates another MBS session in which the first node participates.

[0046] According to one aspect of the present application, it is characterized in that the first information block is configured with a first indication which is used to determine that the first information block is indicated to perform data transmission in the RRC inactive state; and the second information block is not configured with a second indication which is used to determine that the second information block is not indicated to perform data transmission in the RRC inactive state.

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

[0048] receiving a second message;

[0049] Among them, the first node determines that the data transmission performed in the RRC inactive state is used to determine the sending of the second message; along with the second message, each radio bearer in the first radio bearer set is restored, or, along with the first data block, each radio bearer in the first radio bearer set is restored; the first radio bearer set includes at least one DRB of the first node or SRB2 of the first node or at least one multicast MRB of the first node; the second message is used to request the restoration of the RRC connection; the first message is received within the time interval between the restoration of each radio bearer in the first radio bearer set, and the first node does not receive any RRC message indicating that the first node restores the RRC connection.

[0050] As an embodiment, a first data block is sent in response to receipt of the second message; the first data block includes at least user data.

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

[0052] receiving a fourth message;

[0053] In response to the fourth message being received, sending a third message;

[0054] Among them, the first node determines that data transmission in the RRC inactive state is not performed and is used to determine the sending of the fourth message; as a response to the third message being received, each radio bearer in the second radio bearer set is restored by the first node; the fourth message is used to request the restoration of the RRC connection; the second radio bearer set includes all DRBs of the first node or at least one of all multicast MRBs of the first node; within the time interval between the first message being received and the third message being received, any radio bearer in the second radio bearer set is not restored; the third message instructs the first node to restore the RRC connection.

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

[0056] A first processor receives a first message, the first message includes at least a first information block, the first information block includes at least a first identifier, the first identifier is associated with the first node, and the first information block is indicated to perform data transmission in an RRC inactive state; in response to the first message being received, determines whether to perform data transmission in the RRC inactive state according to whether a first condition set is satisfied;

[0057] Among them, the first condition set includes: the first message includes a second information block, the second information block includes at least a second identifier, the second identifier is associated with the first node, and the second information block is not indicated to perform data transmission in the RRC inactive state; the behavior determines whether to perform data transmission in the RRC inactive state according to whether the first condition set is met, including: if any condition in the first condition set is not met, determine to perform data transmission in the RRC inactive state; if each condition in the first condition set is met, determine that data transmission in the RRC inactive state is not performed.

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

[0059] A second transmitter sends a first message, wherein the first message includes at least a first information block, the first information block includes at least a first identifier, the first identifier is associated with a first node, and the first information block is indicated to perform data transmission in an RRC inactive state;

[0060] Among them, the first node is a recipient of the first message; whether the first condition set is satisfied is used to determine whether data transmission in the RRC inactive state is executed; the first condition set includes: the first message includes a second information block, the second information block includes at least a second identifier, the second identifier is associated with the first node, and the second information block is not indicated to perform data transmission in the RRC inactive state; the phrase whether the first condition set is satisfied is used to determine whether data transmission in the RRC inactive state is executed, including: any condition in the first condition set is not satisfied and is used to determine that data transmission in the RRC inactive state is executed; each condition in the first condition set is satisfied and is used to determine that data transmission in the RRC inactive state is not executed.

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

[0062] -. Shorten transmission delay;

[0063] -.Reduce state transitions;

[0064] -.Reduce signaling overhead.

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

[0066] Receive a first message, the first message including at least a first information block, the first information block including at least a first identifier, the first identifier being associated with the first node, and the first information block being indicated to perform data transmission in an RRC inactive state; determine to perform data transmission in the RRC inactive state as a response to the first message being received; send a second message as a response to the determination to perform data transmission in the RRC inactive state; along with the second message, restore each radio bearer in the first radio bearer set, or, along with the first data block, restore each radio bearer in the first radio bearer set;

[0067] The second message is used to request the restoration of the RRC connection; the first radio bearer set includes at least one of at least one DRB of the first node or the SRB2 of the first node or at least one multicast MRB of the first node; the first message is received within the time interval between the restoration of each radio bearer in the first radio bearer set, and the first node does not receive any RRC message indicating that the first node restores the RRC connection.

[0068] According to one aspect of the present application, it is characterized in that, as a response to the second message being sent, a first data block is received; the first data block includes at least user data.

[0069] According to one aspect of the present application, it is characterized in that the first identifier is used to indicate the first node, and the first message does not include an identifier indicating an MBS session in which the first node participates.

[0070] According to one aspect of the present application, it is characterized in that the first identifier indicates an MBS session in which the first node participates, and the first message does not include an identifier indicating the first node.

[0071] According to one aspect of the present application, it is characterized in that the first information block is configured with a first indication which is used to determine that the first information block is instructed to perform data transmission in the RRC inactive state.

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

[0073] Sending a first message, the first message including at least a first information block, the first information block including at least a first identifier, the first identifier being associated with the first node, and the first information block being indicated to perform data transmission in an RRC inactive state; receiving a second message;

[0074] In which, as a response to the data transmission in the RRC inactive state being determined to be executed by the recipient of the first message, the second message is sent by the recipient of the first message; the second message is used to request the restoration of the RRC connection; accompanied by the second message, each radio bearer in the first radio bearer set is restored by the recipient of the first message, or, accompanied by the first data block, each radio bearer in the first radio bearer set is restored by the recipient of the first message; the first radio bearer set includes at least one DRB of the first node or SRB2 of the first node or at least one multicast MRB of the first node; within the time interval between the reception of the first message and the restoration of each radio bearer in the first radio bearer set, the first node does not receive any RRC message indicating that the first node restores the RRC connection.

[0075] According to one aspect of the present application, it is characterized in that, as a response to the second message being received, a first data block is sent; the first data block includes at least user data.

[0076] According to one aspect of the present application, it is characterized in that the first identifier is used to indicate the first node, and the first message does not include an identifier indicating an MBS session in which the first node participates.

[0077] According to one aspect of the present application, it is characterized in that the first identifier indicates an MBS session in which the first node participates, and the first message does not include an identifier indicating the first node.

[0078] According to one aspect of the present application, it is characterized in that whether the first information block includes a first indication is used to determine whether the first information block indicates that the first node performs data transmission in the RRC inactive state.

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

[0080] A first processor receives a first message, wherein the first message includes at least a first information block, the first information block includes at least a first identifier, the first identifier is associated with the first node, and the first information block is indicated to perform data transmission in an RRC inactive state; as a response to the first message being received, determines to perform data transmission in the RRC inactive state; as a response to determining to perform data transmission in the RRC inactive state, sends a second message; along with the second message, restores each radio bearer in the first radio bearer set, or, along with the first data block, restores each radio bearer in the first radio bearer set;

[0081] The second message is used to request the restoration of the RRC connection; the first radio bearer set includes at least one of at least one DRB of the first node or the SRB2 of the first node or at least one multicast MRB of the first node; the first message is received within the time interval between the restoration of each radio bearer in the first radio bearer set, and the first node does not receive any RRC message indicating that the first node restores the RRC connection.

[0082] According to one aspect of the present application, it is characterized in that, as a response to the second message being sent, a first data block is received; the first data block includes at least user data.

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

[0084] Sending a first message, the first message including at least a first information block, the first information block including at least a first identifier, the first identifier being associated with the first node, and the first information block being indicated to perform data transmission in an RRC inactive state; receiving a second message;

[0085] In which, as a response to the data transmission in the RRC inactive state being determined to be executed by the recipient of the first message, the second message is sent by the recipient of the first message; the second message is used to request the restoration of the RRC connection; accompanied by the second message, each radio bearer in the first radio bearer set is restored by the recipient of the first message, or, accompanied by the first data block, each radio bearer in the first radio bearer set is restored by the recipient of the first message; the first radio bearer set includes at least one DRB of the first node or SRB2 of the first node or at least one multicast MRB of the first node; within the time interval between the reception of the first message and the restoration of each radio bearer in the first radio bearer set, the first node does not receive any RRC message indicating that the first node restores the RRC connection.

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

[0087] -. MT-SDT is triggered by the first identifier in the paging message;

[0088] -. Receiving multicast MBS in RRC inactive state by triggering the first identifier in the paging message;

[0089] -. Determine a suitable set of restored radio bearers during data transmission in the RRC inactive state. BRIEF DESCRIPTION OF THE DRAWINGS

[0090] 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:

[0091] Figure 1A A flow chart showing the transmission of a first message according to an embodiment of the present application is shown;

[0092] Figure 1B A flow chart showing the transmission of a first message according to an embodiment of the present application;

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

[0094] 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;

[0095] 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;

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

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

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

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

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

[0101] Fig.10 A structural block diagram of a processing device used in a second node according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0102] 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.

[0103] Example 1A

[0104] Embodiment 1A illustrates a flow chart of the transmission of a first message according to an embodiment of the present application, as shown in the attached Figure 1A Attached Figure 1A 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.

[0105] In Example 1A, the first node in the present application receives a first message in step 101A, wherein the first message includes at least a first information block, the first information block includes at least a first identifier, the first identifier is associated with the first node, and the first information block is indicated to perform data transmission in an RRC inactive state; in step 102A, as a response to the first message being received, determining whether to perform data transmission in the RRC inactive state according to whether a first condition set is satisfied; wherein the first condition set includes: the first message includes a second information block, the second information block includes at least a second identifier, the second identifier is associated with the first node, and the second information block is not indicated to perform data transmission in the RRC inactive state; the behavior determines whether to perform data transmission in the RRC inactive state according to whether the first condition set is satisfied, including: if any condition in the first condition set is not satisfied, determining to perform data transmission in the RRC inactive state; if each condition in the first condition set is satisfied, determining that data transmission in the RRC inactive state is not performed.

[0106] As an embodiment, the first message is received in an RRC inactive state.

[0107] As an embodiment, the first message is used for RAN (Radio Access Network) paging.

[0108] As an embodiment, the first message is triggered by NG (Next Generation)-RAN.

[0109] As an embodiment, the first message is used for paging.

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

[0111] As an embodiment, the first message is an air interface message.

[0112] As an embodiment, the first message is a downlink message.

[0113] As an embodiment, the first message is transmitted via PCCH (Paging Control Channel).

[0114] As an embodiment, the first message is an RRC message.

[0115] As an embodiment, the first message is a Paging message.

[0116] As an embodiment, the first information block includes at least one RRC IE (Information Element).

[0117] As an embodiment, the first information block includes at least one RRC field.

[0118] As an embodiment, the first information block is an RRC IE.

[0119] As an embodiment, the first information block is an RRC domain.

[0120] As an embodiment, the name of the first information block includes Paging.

[0121] As an embodiment, the first information block is a PagingRecord or a PagingRecord-r18; the first identifier is a first-category identifier.

[0122] As an embodiment, the name of the first information block includes PagingRecord; the first identifier is a first-category identifier.

[0123] As an embodiment, the first information block is a field in a PagingRecordList; the first identifier is a first-category identifier.

[0124] As an embodiment, the first information block is a PagingGroup or a PagingGroup-r18; the first identifier is a second-category identifier.

[0125] As an embodiment, the name of the first information block includes PagingGroup; the first identifier is a second-category identifier.

[0126] As an embodiment, the first information block is a field in a PagingGroupList or a PagingGroupList-r17 or a PagingGroupList-r18; and the first identifier is a second-category identifier.

[0127] As an embodiment, the first information block is a TMGI or a TMGI-r17 or a TMGI-r18; the first identifier is a second-category identifier.

[0128] As an embodiment, the name of the first information block includes at least one of Paging, Group, or Record; and the first identifier is a second-category identifier.

[0129] As an embodiment, the second information block includes at least one RRC IE.

[0130] As an embodiment, the second information block includes at least one RRC domain.

[0131] As an embodiment, the second information block is an RRC IE.

[0132] As an embodiment, the second information block is an RRC domain.

[0133] As an embodiment, the name of the second information block includes Paging.

[0134] As an embodiment, the second information block is a PagingRecord or a PagingRecord-r18; and the second identifier is a first-category identifier.

[0135] As an embodiment, the name of the second information block includes PagingRecord; the second identifier is a first-category identifier.

[0136] As an embodiment, the second information block is a field in a PagingRecordList; and the second identifier is a first-category identifier.

[0137] As an embodiment, the second information block is a PagingGroup or a PagingGroup-r18; the second identifier is a second-category identifier.

[0138] As an embodiment, the name of the second information block includes PagingGroup; the second identifier is a second-category identifier.

[0139] As an embodiment, the first information block is a field in a PagingGroupList or a PagingGroupList-r17 or a PagingGroupList-r18; and the second identifier is a second-category identifier.

[0140] As an embodiment, the second information block is a TMGI or a TMGI-r17 or a TMGI-r18; the second identifier is a second-category identifier.

[0141] As an embodiment, the name of the second information block includes at least one of Paging, Group, or Record; and the second identifier is a second-category identifier.

[0142] As an embodiment, the first condition set is: the first message includes a second information block; wherein, the second information block includes at least a second identifier, the second identifier is associated with the first node, and the second information block is not indicated to perform data transmission in the RRC inactive state.

[0143] As an embodiment, the conditions in the first condition set include at least: the first message includes a second information block; wherein the second information block includes at least a second identifier, the second identifier is associated with the first node, and the second information block is not indicated to perform data transmission in the RRC inactive state.

[0144] As an embodiment, if the first message includes the second information block, the first set of conditions is met; if the first message does not include the second information block, the first set of conditions is not met.

[0145] As an embodiment, at least the first message includes a second information block used to determine whether the first set of conditions is met.

[0146] As an embodiment, the second information block is any entry in the first message that includes a first-category identifier other than the first identifier associated with the first node and is indicated to perform data transmission in the RRC inactive state.

[0147] As an embodiment, the second information block is any entry in the first message that includes a second type identifier other than the first identifier associated with the first node and is indicated to perform data transmission in the RRC inactive state.

[0148] As an embodiment, the second information block is any entry in the first message that includes a first type identifier other than the first identifier associated with the first node and is indicated to perform data transmission in the RRC inactive state, or the second information block is any entry in the first message that includes a second type identifier other than the first identifier associated with the first node and is indicated to perform data transmission in the RRC inactive state.

[0149] As an embodiment, if the first message does not contain any entry that includes a first-class identifier other than the first identifier associated with the first node and is not indicated to perform data transmission in the RRC inactive state, and the first message does not contain any entry that includes a second-class identifier other than the first identifier associated with the first node and is not indicated to perform data transmission in the RRC inactive state, the first message does not include the second information block.

[0150] As an embodiment, if the first message does not contain any entry including a first-category identifier other than the first identifier associated with the first node and is not indicated to perform data transmission in the RRC inactive state, the first message does not include the second information block.

[0151] As an embodiment, if the first message does not contain any entry including a second type identifier other than the first identifier associated with the first node and is not indicated to perform data transmission in the RRC inactive state, the first message does not include the second information block.

[0152] As an embodiment, the first identifier is a first-category identifier; the second identifier is a second-category identifier.

[0153] As a sub-embodiment of this embodiment, if the second list exists and there is at least one entry in the second list, the second type identifier in each entry of the at least one entry in the second list is associated with the first node, and at least one entry of the at least one entry in the second list is not indicated to perform data transmission in the RRC inactive state, the first message includes the second information block; the second information block is one of the at least one entry in the second list that is not indicated to perform data transmission in the RRC inactive state.

[0154] As a sub-embodiment of this embodiment, if the second list does not exist, the first message does not include the second information block.

[0155] As a sub-embodiment of this embodiment, if the second list exists, the second type of identifier in any entry in the second list is not associated with the first node, and the first message does not include the second information block.

[0156] As a sub-embodiment of this embodiment, if the second list exists, there is at least one entry in the second list, the second type identifier in each of the at least one entry in the second list is associated with the first node, each of the at least one entry in the second list is indicated to perform data transmission in an RRC inactive state, and the first message does not include the second information block.

[0157] As an embodiment, the first identifier is a first-category identifier; the second identifier is any one of a first-category identifier and a second-category identifier.

[0158] As a sub-embodiment of this embodiment, if the second list exists and there is at least one entry in the second list, the second type identifier in each entry of the at least one entry in the second list is associated with the first node, and at least one entry of the at least one entry in the second list is not indicated to perform data transmission in the RRC inactive state, the first message includes the second information block; the second information block is one of the at least one entry in the second list that is not indicated to perform data transmission in the RRC inactive state.

[0159] As a sub-embodiment of this embodiment, if there is at least one entry other than the first information block in the first list, the first type identifier in each entry of the at least one entry in the first list is associated with the first node, and at least one entry of the at least one entry in the first list is not indicated to perform data transmission in the RRC inactive state, and the first message includes the second information block; the second information block is one of the at least one entry in the first list that is not indicated to perform data transmission in the RRC inactive state.

[0160] As a sub-embodiment of this embodiment, if the first type of identifier in any entry other than the first information block in the first list is not associated with the first node, and the second list does not exist, the first message does not include the second information block.

[0161] As a sub-embodiment of this embodiment, if the first type of identifier in any entry other than the first information block in the first list is not associated with the first node, and the second list exists, and the second type of identifier in any entry in the second list is not associated with the first node, the first message does not include the second information block.

[0162] As a sub-embodiment of this embodiment, if the first type of identifier in any entry other than the first information block in the first list is not associated with the first node, and the second list exists, there is at least one entry in the second list, the second type of identifier in each of the at least one entry in the second list is associated with the first node, and each of the at least one entry in the second list is indicated to perform data transmission in an RRC inactive state, the first message does not include the second information block.

[0163] As a sub-embodiment of this embodiment, if there is at least one entry other than the first information block in the first list, the first type of identifier in each of the at least one entry in the first list is associated with the first node, each of the at least one entry is indicated to perform data transmission in an RRC inactive state, and the second list does not exist, the first message does not include the second information block.

[0164] As a sub-embodiment of this embodiment, if there is at least one entry other than the first information block in the first list, the first type of identifier in each of the at least one entry in the first list is associated with the first node, each of the at least one entry in the first list is indicated to perform data transmission in an RRC inactive state, and the second list exists, the second type of identifier in any entry in the second list is not associated with the first node, and the first message does not include the second information block.

[0165] As a sub-embodiment of this embodiment, if there is at least one entry other than the first information block in the first list, the first type of identifier in each of the at least one entry in the first list is associated with the first node, and each of the at least one entry in the first list is indicated to perform data transmission in an RRC inactive state, and the second list exists, there is at least one entry in the second list, the second type of identifier in each of the at least one entry in the second list is associated with the first node, and each of the at least one entry in the second list is indicated to perform data transmission in an RRC inactive state, the first message does not include the second information block.

[0166] As an embodiment, the first identifier is a second-category identifier; the second identifier is a first-category identifier.

[0167] As a sub-embodiment of this embodiment, if the second list exists, there is at least one entry in the second list, the first type identifier in each entry of the at least one entry in the second list is associated with the first node, at least one entry of the at least one entry in the second list is not indicated to perform data transmission in the RRC inactive state, and the first message includes the second information block; the second information block is one of the at least one entry in the second list that is not indicated to perform data transmission in the RRC inactive state.

[0168] As a sub-embodiment of this embodiment, if the second list does not exist, the first message does not include the second information block.

[0169] As a sub-embodiment of this embodiment, if the second list exists, and the first type of identifier in any entry in the second list is not associated with the first node, the first message does not include the second information block.

[0170] As a sub-embodiment of this embodiment, if the second list exists, there is at least one entry in the second list, the first type of identifier in each of the at least one entry in the second list is associated with the first node, each of the at least one entry in the second list is indicated to perform data transmission in an RRC inactive state, and the first message does not include the second information block.

[0171] As an embodiment, the first identifier is a second-category identifier; the second identifier is any one of a first-category identifier and a second-category identifier.

[0172] As a sub-embodiment of this embodiment, if the second list exists, there is at least one entry in the second list, the first type identifier in each entry of the at least one entry in the second list is associated with the first node, at least one entry of the at least one entry in the second list is not indicated to perform data transmission in the RRC inactive state, and the first message includes the second information block; the second information block is one of the at least one entry in the second list that is not indicated to perform data transmission in the RRC inactive state.

[0173] As a sub-embodiment of this embodiment, if there is at least one entry other than the first information block in the first list, the second type identifier in each of the at least one entry is associated with the first node, at least one of the at least one entry in the first list is not indicated to perform data transmission in the RRC inactive state, and the first message includes the second information block; the second information block is one of the at least one entry in the first list that is not indicated to perform data transmission in the RRC inactive state.

[0174] As a sub-embodiment of this embodiment, if the second type identifier in any entry other than the first information block in the first list is not associated with the first node, and the second list does not exist, the first message does not include the second information block.

[0175] As a sub-embodiment of this embodiment, if the second type of identifier in any entry other than the first information block in the first list is not associated with the first node, and the second list exists, and the first type of identifier in any entry in the second list is not associated with the first node, the first message does not include the second information block.

[0176] As a sub-embodiment of this embodiment, if the second type of identifier in any entry other than the first information block in the first list is not associated with the first node, and the second list exists, there is at least one entry in the second list, the first type of identifier in each of the at least one entry in the second list is associated with the first node, and each of the at least one entry in the second list is indicated to perform data transmission in an RRC inactive state, the first message does not include the second information block.

[0177] As a sub-embodiment of this embodiment, if there is at least one entry other than the first information block in the first list, the second type identifier in each of the at least one entry in the first list is associated with the first node, each of the at least one entry is indicated to perform data transmission in an RRC inactive state, and the second list does not exist, the first message does not include the second information block.

[0178] As a sub-embodiment of this embodiment, if there is at least one entry other than the first information block in the first list, the second type identifier in each of the at least one entry in the first list is associated with the first node, each of the at least one entry in the first list is indicated to perform data transmission in an RRC inactive state, and the second list exists, the first type identifier in any entry in the second list is not associated with the first node, and the first message does not include the second information block.

[0179] As a sub-embodiment of this embodiment, if there is at least one entry other than the first information block in the first list, the second type of identifier in each of the at least one entry in the first list is associated with the first node, and each of the at least one entry in the first list is indicated to perform data transmission in an RRC inactive state, and the second list exists, there is at least one entry in the second list, the first type of identifier in each of the at least one entry in the second list is associated with the first node, and each of the at least one entry in the second list is indicated to perform data transmission in an RRC inactive state, and the first message does not include the second information block.

[0180] As an embodiment, the first identifier is a second-category identifier; the second identifier is a second-category identifier.

[0181] As a sub-embodiment of this embodiment, if there is at least one entry other than the first information block in the first list, the second type identifier in each of the at least one entry is associated with the first node, at least one of the at least one entry in the first list is not indicated to perform data transmission in the RRC inactive state, and the first message includes the second information block; the second information block is one of the at least one entry in the first list that is not indicated to perform data transmission in the RRC inactive state.

[0182] As a sub-embodiment of this embodiment, if the second type identifier in any entry other than the first information block in the first list is not associated with the first node, the first message does not include the second information block. As a sub-embodiment of this embodiment, if there is at least one entry other than the first information block in the first list, the second type identifier in each of the at least one entry is associated with the first node, and each of the at least one entry in the first list is indicated to perform data transmission in an RRC inactive state, the first message does not include the second information block.

[0183] As an embodiment, each entry in the second list includes a first type identifier.

[0184] As an embodiment, each entry in the second list includes a second type identifier.

[0185] As an embodiment, if an entry in the second list includes a first-type identifier, and the first-type identifier matches the fullI-RNTI stored in the first node, the first-type identifier is associated with the first node.

[0186] As an embodiment, if an entry in the second list includes a second type identifier, and the first node participates in the MBS session indicated by the second type identifier, the second type identifier is associated with the first node.

[0187] As an embodiment, the first type of identifier is used to page a user equipment.

[0188] As an embodiment, the first type of identifier is used to indicate a user equipment.

[0189] As an embodiment, the first type of identification is a user identification.

[0190] As an embodiment, the first type of identifier is used to indicate a user equipment.

[0191] As an embodiment, the first type of identifier includes positive integer bits.

[0192] As an embodiment, the first type identifier is a non-negative integer.

[0193] As an embodiment, the first type of identifier is a bit string.

[0194] As an embodiment, the first type of identifier occupies 40 bits.

[0195] As an embodiment, the first type of identifier is ue-Identity.

[0196] As an embodiment, the first type of identification is PagingUE-Identity.

[0197] As an embodiment, the first type of identifier is fullI-RNTI.

[0198] As an embodiment, the first type of identifier is I-RNTI-Value.

[0199] As an embodiment, a first-class identity is indicated by a ue-Identity field.

[0200] As an embodiment, a first type identity is indicated by an RRC domain whose name includes ue-Identity.

[0201] As an embodiment, the second type of identifier is used to page a group of user equipment; the group of user equipment includes one or more user equipment.

[0202] As an embodiment, the second type of identifier is used to indicate a group of user equipment; the group of user equipment includes one or more user equipment.

[0203] As an embodiment, the second type of identifier is the temporary mobile group identifier (Temporary Mobile Group Identity, TMGI).

[0204] As an embodiment, the second type of identification includes a PLMN (Public Land Mobile Network) index and a service identification.

[0205] As an embodiment, the second type of identification includes a PLMN identification and a service identification.

[0206] As an embodiment, a second type identity is indicated by a TMGI field.

[0207] As an embodiment, a second type identifier is indicated by a TMGI-r17 field.

[0208] As an embodiment, a second type identifier is indicated by a TMGI-r18 field.

[0209] As an embodiment, a second type of identity is indicated by an RRC domain whose name includes TMGI.

[0210] As an embodiment, the index of the PLMN is an integer not less than 1 and not greater than maxPLMN.

[0211] As an embodiment, the identification of the PLMN is configured via PLMN-Identity.

[0212] As an embodiment, the service identifier is an octet string (OCTET STRING).

[0213] As an embodiment, the service identifier occupies 3 octets.

[0214] As an embodiment, the first identifier is configured.

[0215] As an embodiment, the first identifier is a first-category identifier.

[0216] As an embodiment, the first identifier is a second-category identifier.

[0217] As an embodiment, the first identifier being associated with the first node means that the first identifier is used to page the first node.

[0218] As an embodiment, the first identifier being associated with the first node includes: the first node being configured with the first identifier.

[0219] As an embodiment, the first identifier being associated with the first node includes: the first identifier is used to indicate the first node.

[0220] As an embodiment, the first identifier being associated with the first node includes: the first identifier indicates an MBS session in which the first node participates.

[0221] As an embodiment, the first identifier is used to indicate the first node, and the first identifier is a first-category identifier.

[0222] As an embodiment, the first identifier indicates an MBS session in which the first node participates, and the first identifier is a second-category identifier.

[0223] As an embodiment, the first identifier is used to indicate the first node, which means that the first identifier matches the fullI-RNTI stored in the first node.

[0224] As an embodiment, the second identifier is configured.

[0225] As an embodiment, the second identifier is a first-category identifier.

[0226] As an embodiment, the second identifier is a second-category identifier.

[0227] As an embodiment, the second identifier being associated with the first node means that the second identifier is used to page the first node.

[0228] As an embodiment, the second identifier being associated with the first node includes: the first node being configured with the second identifier.

[0229] As an embodiment, the second identifier being associated with the first node includes: the second identifier is used to indicate the first node.

[0230] As an embodiment, the second identifier being associated with the first node includes: the second identifier indicates an MBS session in which the first node participates.

[0231] As an embodiment, the second identifier is used to indicate the first node, and the second identifier is a first-category identifier.

[0232] As an embodiment, the second identifier indicates an MBS session in which the first node participates, and the second identifier is a second-category identifier.

[0233] As an embodiment, the second identifier is used to indicate the first node, which means that the second identifier matches the fullI-RNTI stored in the first node.

[0234] As an embodiment, the first identifier is used to indicate the first node, and the second identifier indicates an MBS session in which the first node participates.

[0235] As an embodiment, the first identifier indicates an MBS session in which the first node participates, and the second identifier is used to indicate the first node.

[0236] As an embodiment, the first identifier indicates an MBS session in which the first node participates, and the second identifier indicates another MBS session in which the first node participates.

[0237] As an embodiment, the first identifier is a first-category identifier; the second identifier is a second-category identifier.

[0238] As an embodiment, the first identifier is a first-category identifier; the second identifier is any one of a first-category identifier and a second-category identifier.

[0239] As an embodiment, the first identifier is a second-category identifier; the second identifier is a first-category identifier.

[0240] As an embodiment, the first identifier is a second-category identifier; the second identifier is any one of a first-category identifier and a second-category identifier.

[0241] As an embodiment, the first information block is displayed to indicate that data transmission is performed in the RRC inactive state.

[0242] As an embodiment, the first information block is implicitly indicated to perform data transmission in the RRC inactive state.

[0243] As an embodiment, a field in the first information block is used to determine that the first information block is instructed to perform data transmission in the RRC inactive state.

[0244] As an embodiment, a CG (Configured Grant)-SDT resource is configured to be used to determine that the first information block is instructed to perform data transmission in the RRC inactive state.

[0245] As an embodiment, the random access resource used to indicate the SDT is configured to be used to determine that the first information block is indicated to perform data transmission in the RRC inactive state.

[0246] As an embodiment, the first message indicates that at least one radio bearer in the first radio bearer set is used to determine that the first information block is indicated to perform data transmission in the RRC inactive state.

[0247] As an embodiment, the target message indicates that at least one radio bearer in the first radio bearer set is used to determine that the first information block is indicated for data transmission in the RRC inactive state.

[0248] As an embodiment, the first information block is configured with a first indication which is used to determine that the first information block is instructed to perform data transmission in the RRC inactive state.

[0249] As an embodiment, the second information block is not displayed to indicate that data transmission is performed in the RRC inactive state.

[0250] As an embodiment, the second information block is not implicitly indicated to perform data transmission in the RRC inactive state.

[0251] As an embodiment, a field in the second information block is used to determine that the second information block is not indicated to perform data transmission in the RRC inactive state.

[0252] As an embodiment, at least one of the CG-SDT resources or the random access resources used to indicate SDT is configured not to be configured to be used to determine that the first information block is indicated to perform data transmission in the RRC inactive state.

[0253] As an embodiment, the first message does not indicate that at least one radio bearer in the first radio bearer set is used to determine that the first information block is indicated to perform data transmission in the RRC inactive state.

[0254] As an embodiment, the target message does not indicate that at least one radio bearer in the first radio bearer set is used to determine that the first information block is indicated for data transmission in the RRC inactive state.

[0255] As an embodiment, the second information block is not configured with the first indication which is used to determine that the second information block is not indicated to perform data transmission in the RRC inactive state.

[0256] As an embodiment, the second information block is not configured with a second indication which is used to determine that the second information block does not indicate data transmission in the RRC inactive state.

[0257] As an embodiment, the first identifier is a first-category identifier, and the second identifier is a first-category identifier; the first-category identifier indicates an MBS session in which the first node participates.

[0258] As an embodiment, the first identifier is a first-category identifier, and the second identifier is a first-category identifier; the first-category identifier indicates the first node.

[0259] As an embodiment, the first identifier is a first-type identifier, and the second identifier is a second-type identifier; the first-type identifier indicates the first node, and the second-type identifier indicates the MBS session in which the first node participates.

[0260] As an embodiment, the first identifier is a first-type identifier, and the second identifier is a second-type identifier; the first-type identifier indicates an MBS session in which the first node participates, and the second-type identifier indicates the first node.

[0261] As an embodiment, the first message includes a first list, the first list includes Q1 entries, and the first information block is an entry in the first list.

[0262] As a sub-embodiment of this embodiment, the first list is the first candidate list.

[0263] As a sub-embodiment of this embodiment, the first list is the second candidate list.

[0264] As a sub-embodiment of this embodiment, Q1 is not greater than maxNrofPageRec.

[0265] As a sub-embodiment of this embodiment, Q1 is equal to 1.

[0266] As a sub-embodiment of this embodiment, Q1 is not less than 1.

[0267] As an embodiment, at least one entry in the first list is associated with the first node.

[0268] As an embodiment, each entry in the first list includes a first type identifier.

[0269] As an embodiment, each entry in the first list includes a second type identifier.

[0270] As an embodiment, if an entry in the first list includes a first-type identifier, and the first-type identifier matches the fullI-RNTI stored in the first node, the first-type identifier is associated with the first node.

[0271] As an embodiment, if an entry in the first list includes a second type identifier, and the first node participates in an MBS session indicated by the second type identifier, the second type identifier is associated with the first node.

[0272] As an embodiment, the first information block includes the first indication.

[0273] As a sub-embodiment of this embodiment, whether an entry in the first list includes the first indication is used to determine whether the entry is indicated to perform data transmission in an RRC inactive state.

[0274] As a sub-embodiment of this embodiment, if an entry in the first list includes the first indication, the entry is indicated to perform data transmission in an RRC inactive state; if an entry in the first list does not include the first indication, the entry is not indicated to perform data transmission in an RRC inactive state.

[0275] As a sub-embodiment of this embodiment, the first information block includes a first indication used to determine that the first information block is indicated to perform data transmission in the RRC inactive state.

[0276] As a sub-embodiment of this embodiment, the first information block includes the first identifier and the first information block includes the first indication used to determine that the first node is instructed to perform data transmission in the RRC inactive state.

[0277] As a sub-embodiment of this embodiment, the first information block being configured with the first indication means that: the first information block includes the first indication.

[0278] As an embodiment, the first message includes a first bit map, each entry in the first list corresponds to a bit in the first bit map; the first target bit is a bit in the first bit map corresponding to the first information block.

[0279] As a sub-embodiment of this embodiment, the size of the first bitmap is variable.

[0280] As a sub-embodiment of this embodiment, the first bit map occupies the Q1 bits.

[0281] As a sub-embodiment of this embodiment, the size of the first bitmap is fixed.

[0282] As a sub-embodiment of this embodiment, the first bitmap occupies the maxNrofPageRec bits.

[0283] As a sub-embodiment of this embodiment, one bit in the first bit map is used to determine whether to indicate data transmission in an RRC inactive state.

[0284] As a sub-embodiment of this embodiment, a bit in the first bitmap corresponding to an entry in the first list is used to determine whether the entry is indicated to perform data transmission in an RRC inactive state.

[0285] As a sub-embodiment of this embodiment, if a bit in the first bit map corresponding to an entry in the first list is set to 1, the entry is indicated to perform data transmission in an RRC inactive state; if a bit in the first bit map corresponding to an entry in the first list is set to 0, the entry is not indicated to perform data transmission in an RRC inactive state.

[0286] As a sub-embodiment of this embodiment, a position of an entry in the first list in the first list is used to determine a bit corresponding to the entry in the first bitmap.

[0287] As a sub-embodiment of this embodiment, the position of an entry in the first list in the first list refers to the order of the entry in the first list.

[0288] As a sub-embodiment of this embodiment, the position of the first information block in the first list is used to determine the first target bit in the first bit map.

[0289] As a sub-embodiment of this embodiment, the position of the first information block in the first list refers to the order of the first sub-information blocks in the first list.

[0290] As a sub-embodiment of this embodiment, if the first information block is the q1th entry in the first list, the first target bit is the q1th bit in the first bit map.

[0291] As a sub-embodiment of this embodiment, the first target bit is set to 1.

[0292] As a sub-embodiment of this embodiment, the first target bit is set to 1 and is used to determine that the first information block is instructed to perform data transmission in the RRC inactive state.

[0293] As a sub-embodiment of this embodiment, the first information block includes the first identifier and the first target bit is set to 1 to determine that the first node is instructed to perform data transmission in the RRC inactive state.

[0294] As a sub-embodiment of this embodiment, the first information block is configured with the first indication, which means that the first target bit is set to 1.

[0295] As an embodiment, the first message includes a first additional list, and the first additional list corresponds to the first list; the first additional information block is an entry in the first additional list corresponding to the first information block.

[0296] As a sub-embodiment of this embodiment, whether an entry in the first additional list includes the first indication is used to determine whether an entry in the first list corresponding to the entry in the first additional list is indicated to perform data transmission in an RRC inactive state.

[0297] As a sub-embodiment of this embodiment, if an entry in the first additional list includes a first indication, the entry in the first list corresponding to the entry in the first additional list is indicated to perform data transmission in an RRC inactive state; if an entry in the first additional list does not include the first indication, the entry in the first list corresponding to the entry in the first additional list is not indicated to perform data transmission in an RRC inactive state.

[0298] As a sub-embodiment of this embodiment, the number of entries in the first additional list is equal to the number of entries in the first list, and the order of the entries in the first additional list is the same as the order of the entries in the first list.

[0299] As a sub-embodiment of this embodiment, the first information block is the q1th entry in the first list, the first additional information block is the q1th entry in the first additional list, and q1 is a positive integer not greater than Q1.

[0300] As a sub-embodiment of this embodiment, the first additional information block is for the first information block.

[0301] As a sub-embodiment of this embodiment, the first additional information block includes the first indication which is used to determine that the first information block is indicated to perform data transmission in the RRC inactive state.

[0302] As a sub-embodiment of this embodiment, the first information block includes the first identifier and the first additional information block includes the first indication which is used to determine that the first node is instructed to perform data transmission in the RRC inactive state.

[0303] As a sub-embodiment of this embodiment, the first information block being configured with the first indication means that: the first additional information block includes the first indication.

[0304] As an embodiment, the first message includes the second information block.

[0305] As an embodiment, the first message does not include the second information block.

[0306] As an embodiment, the second information block is an entry in the first list.

[0307] As a sub-embodiment of this embodiment, the second information block does not include the first indication; the first information block includes the first indication.

[0308] As a subsidiary embodiment of this sub-embodiment, the second information block does not include the first indication, which is used to determine that the second information block does not indicate that data is transmitted in the RRC inactive state.

[0309] As a subsidiary embodiment of this sub-embodiment, the second information block includes the second identifier and the second information block does not include the first indication, which is used to determine that the first node is not instructed to perform data transmission in the RRC inactive state.

[0310] As a subsidiary embodiment of this sub-embodiment, the second information block is not configured with the first indication means that: the second information block does not include the first indication.

[0311] As a sub-embodiment of this embodiment, the second target bit is a bit in the first bit map corresponding to the second information block; the first message includes a first bit map, and each entry in the first list corresponds to a bit in the first bit map; the first target bit is a bit in the first bit map corresponding to the first information block.

[0312] As a subsidiary embodiment of this sub-embodiment, the second target bit is set to 0.

[0313] As a subsidiary embodiment of this sub-embodiment, the first target bit and the second target bit are set to different values.

[0314] As a subsidiary embodiment of this sub-embodiment, the first information block and the second information block are two different entries in the first list respectively.

[0315] As a subsidiary embodiment of this sub-embodiment, the second target bit is set to 0 to determine that the second information block is not indicated to perform data transmission in the RRC inactive state.

[0316] As a subsidiary embodiment of this sub-embodiment, the second information block includes the second identifier and the second target bit is set to 0 to determine that the first node is not instructed to perform data transmission in the RRC inactive state.

[0317] As a subsidiary embodiment of this sub-embodiment, the second information block is not configured with the first indication, which means that the second target bit is set to 0.

[0318] As a sub-embodiment of this embodiment, the second additional information block is an entry in the first additional list corresponding to the second information block; the first message includes a first additional list, and the first additional list corresponds to the first list; the first additional information block is an entry in the first additional list corresponding to the first information block.

[0319] As a subsidiary embodiment of this sub-embodiment, the second additional information block does not include the first indication.

[0320] As a subsidiary embodiment of this sub-embodiment, the second additional information block is directed to the second information block.

[0321] As a subsidiary embodiment of this sub-embodiment, the second information block is an entry other than the first information block in the first list.

[0322] As a subsidiary embodiment of this sub-embodiment, the second additional information block is an entry other than the first additional information block in the first additional list.

[0323] As a subsidiary embodiment of this sub-embodiment, the second additional information block does not include the first indication, which is used to determine that the second information block does not indicate that data is transmitted in the RRC inactive state.

[0324] As a subsidiary embodiment of this sub-embodiment, the second information block includes the second identifier and the second additional information block does not include the first indication, which is used to determine that the first node is not instructed to perform data transmission in the RRC inactive state.

[0325] As a subsidiary embodiment of this sub-embodiment, the second information block is not configured with the first indication, which means that the second additional information block does not include the first indication.

[0326] As an embodiment, the first message includes a second list, the second list includes Q2 entries, and the second information block is an entry in the second list.

[0327] As a sub-embodiment of this embodiment, the first list is the first candidate list, and the second list is the second candidate list.

[0328] As a sub-embodiment of this embodiment, the first list is the second candidate list, and the second list is the first candidate list.

[0329] As an embodiment, Q2 is not greater than at least one of maxNrofPageGroup or maxNrofPageGroup-r17 or maxNrofPageGroup-r18.

[0330] As a sub-embodiment of this embodiment, Q2 is equal to 1.

[0331] As a sub-embodiment of this embodiment, Q2 is not less than 1.

[0332] As an embodiment, each entry in the second list includes a first type identifier.

[0333] As an embodiment, each entry in the second list includes a second type identifier.

[0334] As an embodiment, if an entry in the second list includes a first-type identifier, and the first-type identifier matches the fullI-RNTI stored in the first node, the first-type identifier is associated with the first node.

[0335] As an embodiment, if an entry in the second list includes a second type identifier, and the first node participates in the MBS session indicated by the second type identifier, the second type identifier is associated with the first node.

[0336] As an embodiment, the second information block does not include a second indication.

[0337] As a sub-embodiment of this embodiment, whether an entry in the second list includes the second indication is used to determine whether the entry is indicated to perform data transmission in an RRC inactive state.

[0338] As a sub-embodiment of this embodiment, if an entry in the second list includes the second indication, the entry is indicated to perform data transmission in the RRC inactive state; if an entry in the second list does not include the second indication, the entry is not indicated to perform data transmission in the RRC inactive state.

[0339] As a sub-embodiment of this embodiment, the second information block does not include a second indication which is used to determine that the second information block does not indicate data transmission in the RRC inactive state.

[0340] As a sub-embodiment of this embodiment, the second information block includes the second identifier and the second information block does not include the second indication which is used to determine that the first node is not instructed to perform data transmission in the RRC inactive state.

[0341] As a sub-embodiment of this embodiment, the second information block is not configured with the second indication means that: the second information block does not include the second indication.

[0342] As an embodiment, the first message includes a second bit map, each entry in the second list corresponds to a bit in the second bit map; the second target bit is a bit in the second bit map corresponding to the second information block.

[0343] As a sub-embodiment of this embodiment, the size of the second bitmap is variable.

[0344] As a sub-embodiment of this embodiment, the second bit map occupies the Q2 bits.

[0345] As a sub-embodiment of this embodiment, the size of the second bitmap is fixed.

[0346] As a sub-embodiment of this embodiment, the second bitmap occupies the maxNrofPageRec bits.

[0347] As a sub-embodiment of this embodiment, a bit in the second bitmap corresponding to an entry in the second list is used to determine whether the entry indicates data transmission in an RRC inactive state.

[0348] As a sub-embodiment of this embodiment, if a bit in the second bit map corresponding to an entry in the second list is set to 1, the entry is indicated to perform data transmission in an RRC inactive state; if a bit in the second bit map corresponding to an entry in the second list is set to 0, the entry is not indicated to perform data transmission in an RRC inactive state.

[0349] As a sub-embodiment of this embodiment, a position of an entry in the second list in the second list is used to determine a bit corresponding to the entry in the second bit map.

[0350] As a sub-embodiment of this embodiment, the position of an entry in the second list refers to the order of the entry in the second list.

[0351] As a sub-embodiment of this embodiment, the position of the second information block in the second list is used to determine the second target bit in the second bit map.

[0352] As a sub-embodiment of this embodiment, the position of the second information block in the second list refers to the order of the second sub-information blocks in the second list.

[0353] As a sub-embodiment of this embodiment, if the second information block is the q2th entry in the second list, the second target bit is the q2th bit in the second bit map.

[0354] As a sub-embodiment of this embodiment, the second target bit is set to 0.

[0355] As a sub-embodiment of this embodiment, the second target bit is set to 0 and is used to determine that the second information block is not instructed to perform data transmission in the RRC inactive state.

[0356] As a sub-embodiment of this embodiment, the second information block includes the second identifier and the second target bit is set to 0 to determine that the first node is not instructed to perform data transmission in the RRC inactive state.

[0357] As a sub-embodiment of this embodiment, the second information block is not configured with the second indication, which means that the second target bit is set to 0.

[0358] As an embodiment, the first message includes a second additional list, and the second additional list corresponds to the second list; the second additional information block is an entry in the second additional list corresponding to the second information block.

[0359] As a sub-embodiment of this embodiment, whether an entry in the second additional list includes the second indication is used to determine whether an entry in the second additional list corresponding to the entry in the second additional list is indicated to perform data transmission in an RRC inactive state.

[0360] As a sub-embodiment of this embodiment, if an entry in the second additional list includes a second indication, the entry in the second list corresponding to the entry in the second additional list is indicated to perform data transmission in an RRC inactive state; if an entry in the second additional list does not include the second indication, the entry in the second list corresponding to the entry in the second additional list is not indicated to perform data transmission in an RRC inactive state.

[0361] As a sub-embodiment of this embodiment, the number of entries in the second additional list is equal to the number of entries in the second list, and the order of the entries in the second additional list is the same as the order of the entries in the second list.

[0362] As a sub-embodiment of this embodiment, the second information block is the q2th entry in the second list, the second additional information block is the q2th entry in the second additional list, and q2 is a positive integer not greater than Q2.

[0363] As a sub-embodiment of this embodiment, the second additional information block is for the second information block.

[0364] As a sub-embodiment of this embodiment, the second additional information block does not include the second indication.

[0365] As a sub-embodiment of this embodiment, the second additional information block does not include the second indication which is used to determine that the second information block does not indicate that data is transmitted in the RRC inactive state.

[0366] As a sub-embodiment of this embodiment, the second information block includes the second identifier and the second additional information block does not include the second indication which is used to determine that the first node is not instructed to perform data transmission in the RRC inactive state.

[0367] As a sub-embodiment of this embodiment, the second information block is not configured with the second indication means that: the second additional information block does not include the second indication.

[0368] As an embodiment, the second information block is an entry in the first list, or the second information block is an entry in the second list.

[0369] As an embodiment, the second information block is an entry in any one of the first list or the second list.

[0370] As an embodiment, the first candidate list is used for paging for multicast.

[0371] As a sub-embodiment of this embodiment, the name of the first candidate list includes at least one of Paging, Group, List, MBS, or r18.

[0372] As a sub-embodiment of this embodiment, the name of the first candidate list is PagingGroupList or PagingGroupList-r17 or PagingGroupList-r18.

[0373] As a sub-embodiment of this embodiment, the name of each entry in the first candidate list includes at least one of Paging or Group or multi or MBS or TMGI or r18.

[0374] As a sub-embodiment of this embodiment, the name of each entry in the first candidate list is PagingGroup-r18.

[0375] As a sub-embodiment of this embodiment, the name of each entry in the first candidate list is TMGI or TMGI-r18.

[0376] As a sub-embodiment of this embodiment, the name of each entry in the first candidate list is the same.

[0377] As a sub-embodiment of this embodiment, each entry in the first candidate list indicates a TMGI.

[0378] As an embodiment, the second candidate list is used for paging for unicast.

[0379] As a sub-embodiment of this embodiment, the name of the second candidate list includes at least one of Paging, Record, List, MBS, or r18.

[0380] As a sub-embodiment of this embodiment, the name of the second candidate list is PagingRecordList or PagingRecordList-r17 or PagingRecordList-r18.

[0381] As a sub-embodiment of this embodiment, the name of each entry in the second candidate list includes at least one of Paging, Record, or r18.

[0382] As a sub-embodiment of this embodiment, the name of each entry in the second candidate list is PagingRecord-r18 or PagingRecord.

[0383] As a sub-embodiment of this embodiment, each entry in the second candidate list includes a user identifier, and the user identifier included in each entry in the first list except the first sub-information block is any one of NG-5G-S-TMSI or I-RNTI-Value.

[0384] As a sub-embodiment of this embodiment, the name of each entry in the second candidate list is the same.

[0385] As an embodiment, the first candidate additional list is for the first candidate list.

[0386] As a sub-embodiment of this embodiment, the name of the first candidate additional list includes at least one of Paging, Group, List, MBS, or r18.

[0387] As a sub-embodiment of this embodiment, the name of the first candidate additional list is PagingGroupList or PagingGroupList-r17 or PagingGroupList-r18.

[0388] As a sub-embodiment of this embodiment, the name of each entry in the first candidate additional list includes at least one of Paging or Group or multi or MBS or TMGI or r18.

[0389] As a sub-embodiment of this embodiment, the name of each entry in the first candidate additional list is PagingGroup-r18.

[0390] As a sub-embodiment of this embodiment, the name of each entry in the first candidate additional list is TMGI or TMGI-r18.

[0391] As a sub-embodiment of this embodiment, the name of each entry in the first candidate additional list is the same.

[0392] As a sub-embodiment of this embodiment, each entry in the first candidate additional list indicates a TMGI.

[0393] As an embodiment, a second candidate additional list is used for the second candidate list.

[0394] As a sub-embodiment of this embodiment, the name of the second candidate additional list includes at least one of Paging, Record, List, MBS, or r18.

[0395] As a sub-embodiment of this embodiment, the name of the second candidate additional list is PagingRecordList or PagingRecordList-r17 or PagingRecordList-r18.

[0396] As a sub-embodiment of this embodiment, the name of each entry in the second candidate additional list includes at least one of Paging, Record, or r18.

[0397] As a sub-embodiment of this embodiment, the name of each entry in the second candidate additional list is PagingRecord-r18 or PagingRecord.

[0398] As a sub-embodiment of this embodiment, each entry in the second candidate additional list includes a user identifier, and the user identifier included in each entry in the second list except the second sub-information block is any one of NG-5G-S-TMSI or I-RNTI-Value.

[0399] As a sub-embodiment of this embodiment, the name of each entry in the second candidate additional list is the same.

[0400] As an embodiment, the first list is used for paging for unicast; and the second list is used for paging for multicast.

[0401] As an embodiment, the first list is used for paging for multicast; and the second list is used for paging for unicast.

[0402] As an embodiment, the first list is used for paging for multicast; the second list is used for paging for multicast.

[0403] As an embodiment, the first list is used for paging for unicast; the second list is used for paging for unicast.

[0404] As an embodiment, the first message includes a first list and a first additional list; the first list is used for paging for multicast.

[0405] As a sub-embodiment of this embodiment, the name of the first additional list includes at least one of Paging or Group or List or MBS or r1800 or r18.

[0406] As a sub-embodiment of this embodiment, the name of the first additional list is PagingGroupList-r1800.

[0407] As a sub-embodiment of this embodiment, the name of each entry in the first additional list includes at least one of Paging or Group or MBS or r1800 or r18.

[0408] As a sub-embodiment of this embodiment, the name of each entry in the first additional list is PagingGroup-r1800 or PagingGroup-r1801 or PagingGroup-r1802.

[0409] As a sub-embodiment of this embodiment, the name of each entry in the first additional list is the same.

[0410] As an embodiment, the first message includes a first list and a first additional list; the first list is used for paging for unicast.

[0411] As a sub-embodiment of this embodiment, the name of the first additional list includes at least one of Paging or Record or List or SDT or r1800 or r18.

[0412] As a sub-embodiment of this embodiment, the name of the first additional list is PagingRecordList-r1800.

[0413] As a sub-embodiment of this embodiment, the name of each entry in the first additional list includes at least one of Paging or Record or SDT or r1800 or r18.

[0414] As a sub-embodiment of this embodiment, the name of each entry in the first additional list is PagingRecord-r1800.

[0415] As a sub-embodiment of this embodiment, the name of each entry in the first additional list is the same.

[0416] As an embodiment, the name of the RRC domain to which the first indication belongs is different from the name of the RRC domain to which the second indication belongs.

[0417] As an embodiment, the name of the RRC domain to which the first indication belongs is the same as the name of the RRC domain to which the second indication belongs, and the value of the RRC domain to which the first indication belongs is different from the value of the RRC domain to which the second indication belongs.

[0418] As an embodiment, the name of the RRC domain to which the first indication belongs is different from the name of the RRC domain to which the second indication belongs, and the value of the RRC domain to which the first indication belongs is different from the value of the RRC domain to which the second indication belongs.

[0419] As an embodiment, the first indication includes an RRC domain.

[0420] As a sub-embodiment of this embodiment, the first indication is an RRC domain.

[0421] As a sub-embodiment of this embodiment, the first indication is a value of an RRC domain.

[0422] As a sub-embodiment of this embodiment, the name of the RRC domain includes at least one of Paging or Cause or r1800 or r18.

[0423] As a sub-embodiment of this embodiment, the value of the RRC domain is a string.

[0424] As a sub-embodiment of this embodiment, the value of the RRC domain includes at least one of mt or SDT or inactive or Data or Trans or Transmission or i or I or -r18 or or r1800.

[0425] As a sub-embodiment of this embodiment, the value of the RRC domain includes at least one of MBS or inactive or IMBS or i or I or r1800 or -r18.

[0426] As a sub-embodiment of this embodiment, the first indication is a bit in an RRC domain.

[0427] As a sub-embodiment of this embodiment, the RRC domain includes a bit map.

[0428] As a sub-embodiment of this embodiment, the RRC domain includes a bit string.

[0429] As an embodiment, the "response as to the first message being received" includes: if the first message is received.

[0430] As an embodiment, the "received as a response to the first message" includes: when the first message is received.

[0431] As an embodiment, the "received as a response to the first message" includes: after the first message is received.

[0432] As an embodiment, data transmission in the RRC inactive state includes: unicast transmission in the RRC inactive state.

[0433] As a sub-embodiment of this embodiment, the "unicast transmission in the RRC inactive state" includes: transmitting at least one of unicast data or unicast signaling in the RRC inactive state.

[0434] As a sub-embodiment of this embodiment, the "unicast transmission in the RRC inactive state" includes: transmitting unicast data or unicast signaling in the RRC inactive state.

[0435] As a sub-embodiment of this embodiment, the "unicast transmission in the RRC inactive state" includes: receiving at least one of unicast data or unicast signaling in the RRC inactive state.

[0436] As a sub-embodiment of this embodiment, the "unicast transmission in the RRC inactive state" includes: receiving at least one of unicast data or unicast signaling in the RRC inactive state, or sending at least one of unicast data or unicast signaling in the RRC inactive state.

[0437] As a sub-embodiment of this embodiment, the "unicast transmission in the RRC inactive state" includes: receiving at least one of unicast data or unicast signaling in the RRC inactive state, or / and, sending at least one of unicast data or unicast signaling in the RRC inactive state.

[0438] As a sub-embodiment of this embodiment, the "unicast transmission in the RRC inactive state" includes: receiving and / or sending at least one of unicast data or unicast signaling in the RRC inactive state.

[0439] As a sub-embodiment of this embodiment, the "unicast transmission in the RRC inactive state" includes: MT-SDT.

[0440] As a sub-embodiment of this embodiment, the "unicast transmission in the RRC inactive state" includes: SDT.

[0441] As a sub-embodiment of this embodiment, the unicast data refers to data transmitted through DRB.

[0442] As a sub-embodiment of this embodiment, the unicast signaling refers to signaling transmitted via SRB.

[0443] As an embodiment, the data transmission in the RRC inactive state includes: multicast transmission in the RRC inactive state.

[0444] As an embodiment, the "multicast transmission in the RRC inactive state" includes: transmitting at least one of multicast data or multicast signaling in the RRC inactive state.

[0445] As a sub-embodiment of this embodiment, the "multicast transmission in the RRC inactive state" includes: transmitting multicast data or multicast signaling in the RRC inactive state.

[0446] As a sub-embodiment of this embodiment, the "multicast transmission in the RRC inactive state" includes: receiving at least one of multicast data or multicast signaling in the RRC inactive state.

[0447] As a sub-embodiment of this embodiment, the "multicast transmission in the RRC inactive state" includes: receiving at least one of multicast data or multicast signaling in the RRC inactive state, or sending at least one of multicast data or multicast signaling in the RRC inactive state.

[0448] As a sub-embodiment of this embodiment, the "multicast transmission in the RRC inactive state" includes: receiving at least one of multicast data or multicast signaling in the RRC inactive state, or / and, sending at least one of multicast data or multicast signaling in the RRC inactive state.

[0449] As a sub-embodiment of this embodiment, the "multicast transmission in the RRC inactive state" includes: receiving and / or sending at least one of multicast data or multicast signaling in the RRC inactive state.

[0450] As a sub-embodiment of this embodiment, the multicast data refers to data transmitted via a multicast MRB.

[0451] As a sub-embodiment of this embodiment, the multicast signaling refers to signaling transmitted via a multicast MRB.

[0452] As an embodiment, if the first identifier is used to indicate the first node, the data transmission in the RRC inactive state includes: transmitting at least one of unicast data or unicast signaling in the RRC inactive state.

[0453] As an embodiment, if the first identifier indicates an MBS session in which the first node participates, the data transmission in the RRC inactive state includes: transmitting at least one of multicast data or multicast signaling in the RRC inactive state.

[0454] As an embodiment, the "first information block indicates that the first node performs data transmission in the RRC inactive state" means: the first information block indicates that the first node performs unicast transmission in the RRC inactive state; wherein, the first identifier is used to indicate the first node.

[0455] As an embodiment, the "first information block indicates that the first node performs data transmission in an RRC inactive state" means: the first information block indicates that the first node performs multicast transmission in the RRC inactive state; wherein, the first identifier indicates an MBS session in which the first node participates.

[0456] As an embodiment, the "second information block does not indicate that the first node performs data transmission in the RRC inactive state" means: the second information block does not indicate that the first node performs unicast transmission in the RRC inactive state; wherein the second identifier is used to indicate the first node.

[0457] As an embodiment, the "second information block does not indicate that the first node performs data transmission in the RRC inactive state" means: the second information block does not indicate that the first node performs multicast transmission in the RRC inactive state; wherein the second identifier indicates an MBS session in which the first node participates.

[0458] As an embodiment, the “second information block does not indicate the first node to perform data transmission in the RRC inactive state” means: the second information block does not indicate the first node to perform unicast transmission in the RRC inactive state, and the second information block does not indicate the first node to perform multicast transmission in the RRC inactive state.

[0459] As an embodiment, the first information block indicates the transmission of at least one of multicast data or multicast signaling in the RRC inactive state, and the second information block indicates the transmission of at least one of unicast data or unicast signaling in the RRC inactive state; the first identifier indicates an MBS session in which the first node participates, and the second identifier is used to indicate the first node.

[0460] As an embodiment, the first information block indicates the transmission of at least one of unicast data or unicast signaling in the RRC inactive state, and the second information block indicates the transmission of at least one of multicast data or multicast signaling in the RRC inactive state; the first identifier is used to indicate the first node, and the second identifier indicates an MBS session in which the first node participates.

[0461] As an embodiment, the first information block indicates at least one of multicast data or multicast signaling transmitted in the RRC inactive state, and the second information block indicates at least one of multicast data or multicast signaling transmitted in the RRC inactive state; the first identifier indicates an MBS session in which the first node participates, and the second identifier indicates another MBS session in which the first node participates.

[0462] As an embodiment, the "determining to perform data transmission in the RRC inactive state" includes: determining to transmit data or signaling through at least one radio bearer in the first radio bearer set in the RRC inactive state.

[0463] As an embodiment, the "determining to execute data transmission in the RRC inactive state" includes: determining to initiate data transmission in the RRC inactive state.

[0464] As an embodiment, the "determining to perform data transmission in the RRC inactive state" includes: determining to use random access resources of RA (Random Access)-SDT to initiate a random access process.

[0465] As an embodiment, the "determining to perform data transmission in the RRC inactive state" includes: determining to initiate a random access process using random access resources of CG-SDT.

[0466] As an embodiment, the "determining to execute data transmission in the RRC inactive state" includes: determining to initiate and execute the SDT process.

[0467] As an embodiment, the "determining to execute data transmission in the RRC inactive state" includes: determining to initiate and execute the MT-SDT process.

[0468] As an embodiment, the first node receives a Paging message, the Paging message includes a pagingRecordList, if the ue-Identity in a PagingRecord in the pagingRecordList matches the fullI-RNTI stored by the first node, and the PagingRecord is indicated to perform data transmission in an RRC inactive state, and the first message includes a pagingGroupList, and the first node participates in an MBS session indicated by a TMGI in the pagingGroupList, and the TMGI is not indicated to perform data transmission in an RRC inactive state, it is determined that data transmission in the RRC inactive state is not performed.

[0469] As an embodiment, the first node receives a Paging message, and the Paging message includes a pagingGroupList. If the first node participates in an MBS session indicated by a TMGI in the pagingGroupList, and the one TMGI is indicated to perform data transmission in an RRC inactive state, and the first node participates in an MBS session indicated by another TMGI in the pagingGroupList, and the other TMGI is not indicated to perform data transmission in an RRC inactive state, it is determined that data transmission in the RRC inactive state is not performed.

[0470] As an embodiment, the first node receives a Paging message, the Paging message includes a pagingGroupList, if the first node participates in an MBS session indicated by a TMGI in the pagingGroupList, and the TMGI is indicated to perform data transmission in an RRC inactive state, and the first message includes a pagingRecordList, and the ue-Identity in a PagingRecord in the pagingRecordList matches the fullI-RNTI stored by the first node, and the PagingRecord is not indicated to perform data transmission in an RRC inactive state, it is determined that data transmission in the RRC inactive state is not performed.

[0471] As an embodiment, the first node supports MT-SDT.

[0472] As an embodiment, the first node supports receiving multicast MBS in an RRC inactive state.

[0473] As an embodiment, the type of the first identifier is the same as the type of the second identifier.

[0474] As an embodiment, the type of the first identifier is different from the type of the second identifier.

[0475] As an embodiment, the priority of the radio bearer associated with the first identifier is the same as the priority of the radio bearer associated with the second identifier.

[0476] As an embodiment, the priority of the radio bearer associated with the first identifier is different from the priority of the radio bearer associated with the second identifier.

[0477] As an embodiment, a target message is received before the first message; the target message instructs the first node to enter or maintain the RRC inactive state.

[0478] As an embodiment, the target message is a RRCRelease message.

[0479] As an embodiment, within the time interval between when the target message is received and when the first message is received, the first node is always in an RRC inactive state.

[0480] As an embodiment, within the time interval between when the target message is received and when the first message is received, the first node does not send an RRC message through any one of CCCH or CCCH1.

[0481] As an embodiment, the target message is a RRCRelease message, and the RRCRelease message includes SuspendConfig.

[0482] As an embodiment, the SuspendConfig in the target message includes a first target domain.

[0483] As an embodiment, the first target domain is sdt-Config or sdt-Config-r17 or sdt-Config-r18.

[0484] As an embodiment, the first target domain is used to configure SDT.

[0485] As an embodiment, the first target domain is set to Setup.

[0486] As an embodiment, the first target domain is set to Release.

[0487] As an embodiment, the SuspendConfig in the target message does not include the first target domain.

[0488] Example 1B

[0489] Embodiment 1B illustrates a flow chart of the transmission of a first message according to an embodiment of the present application, as shown in the attached Figure 1B Attached Figure 1B 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.

[0490] In embodiment 1B, the first node in the present application receives a first message in step 101B, wherein the first message includes at least a first information block, the first information block includes at least a first identifier, the first identifier is associated with the first node, and the first information block is indicated to perform data transmission in an RRC inactive state; in step 102B, as a response to the first message being received, determining to perform data transmission in the RRC inactive state; as a response to determining to perform data transmission in the RRC inactive state, sending a second message; accompanied by the second message, restoring each radio bearer in the first radio bearer set; wherein the second message is used to request restoration of the RRC connection; the first radio bearer set includes at least one DRB of the first node or SRB2 of the first node or at least one multicast MRB of the first node; within the time interval between the restoration of each radio bearer in the first radio bearer set when the first message is received, the first node does not receive any RRC message indicating that the first node restores the RRC connection.

[0491] As an embodiment, the first identifier is used to indicate the first node, and the first message does not include an identifier indicating an MBS session in which the first node participates.

[0492] As a sub-embodiment of this embodiment, the first radio bearer set includes all DRBs of the first node U01.

[0493] As a sub-embodiment of this embodiment, the first radio bearer set includes all DRBs of the first node U01 and SRB2 of the first node U01.

[0494] As a sub-embodiment of this embodiment, the first radio bearer set includes at least one DRB of the first node or at least one of SRB2 of the first node.

[0495] As a sub-embodiment of this embodiment, the first radio bearer set does not include at least one of DRB or SRB2.

[0496] As a sub-embodiment of this embodiment, the first message indicates at least one radio bearer in the first radio bearer set.

[0497] As a sub-embodiment of this embodiment, the target message indicates at least one radio bearer in the first radio bearer set.

[0498] As a sub-embodiment of this embodiment, a SIB1 (System Information Block 1) message indicates at least one radio bearer in the first radio bearer set.

[0499] As an embodiment, at least one of the first message or the target message or the SIB1 indicates at least one radio bearer in the first radio bearer set.

[0500] As an embodiment, the first identifier indicates an MBS session in which the first node participates, and the first message does not include an identifier indicating the first node.

[0501] As a sub-embodiment of this embodiment, the first radio bearer set includes all multicast MRBs of the first node U01.

[0502] As a sub-embodiment of this embodiment, the first radio bearer set includes at least one multicast MRB of the first node.

[0503] As a sub-embodiment of this embodiment, the first radio bearer set includes at least one multicast MRB of the first node or at least one of SRB2 of the first node.

[0504] As a sub-embodiment of this embodiment, the first radio bearer set does not include at least one of the multicast MRB or SRB2.

[0505] As a sub-embodiment of this embodiment, the first message indicates at least one radio bearer in the first radio bearer set.

[0506] As a sub-embodiment of this embodiment, the target message indicates at least one radio bearer in the first radio bearer set.

[0507] As a sub-embodiment of this embodiment, the SIB1 message indicates at least one radio bearer in the first radio bearer set.

[0508] As a sub-embodiment of this embodiment, at least one of the first message or the target message or the SIB1 indicates at least one radio bearer in the first radio bearer set.

[0509] As an embodiment, the first information block is displayed to indicate that data transmission is performed in the RRC inactive state.

[0510] As an embodiment, the first information block is implicitly indicated to perform data transmission in the RRC inactive state.

[0511] As an embodiment, a field in the first information block is used to determine that the first information block is instructed to perform data transmission in the RRC inactive state.

[0512] As an embodiment, the CG-SDT resources are configured to be used to determine that the first information block is instructed to perform data transmission in the RRC inactive state.

[0513] As an embodiment, the random access resource used to indicate the SDT is configured to be used to determine that the first information block is indicated to perform data transmission in the RRC inactive state.

[0514] As an embodiment, the first message indicates that at least one radio bearer in the first radio bearer set is used to determine that the first information block is indicated to perform data transmission in the RRC inactive state.

[0515] As an embodiment, the target message indicates that at least one radio bearer in the first radio bearer set is used to determine that the first information block is indicated for data transmission in the RRC inactive state.

[0516] As an embodiment, the first information block is configured with a first indication which is used to determine that the first information block is instructed to perform data transmission in the RRC inactive state.

[0517] Example 2

[0518] 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 2The network architecture 200 of a 5G NR (New Radio) / LTE (Long-Term Evolution) / LTE-A (Long-Term Evolution Advanced) system is illustrated. The 5G NR / LTE / LTE-A network architecture 200 may be referred to as a 5GS (5G System) / EPS (Evolved Packet System) 200 or some other suitable term. The 5GS / EPS 200 includes at least one of a UE (User Equipment) 201, a RAN (Radio Access Network) 202, a 5GC (5G Core Network) / EPC (Evolved Packet Core) 210, a HSS (Home Subscriber Server) / UDM (Unified Data Management) 220, and an Internet service 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 switching services, but it will be readily understood by those skilled in the art that the various concepts presented throughout this application can be extended to networks or other cellular networks that provide circuit switching services. RAN includes node 203 and other nodes 204. Node 203 provides user and control plane protocol terminations toward UE 201. Node 203 can be connected to other nodes 204 via an Xn interface (e.g., backhaul) / X2 interface. Node 203 may also be referred to as a base station, 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 terminology. Node 203 provides an access point to 5GC / EPC 210 for UE 201. Examples of UE 201 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, non-terrestrial base station communications, satellite mobile communications, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, drones, aircraft, narrowband Internet of Things devices, machine type communication devices, land vehicles, cars, wearable devices, or any other similar functional devices. Those skilled in the art may also refer to UE 201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable term.Node 203 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 a control node that handles 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 service 230. Internet service 230 includes operator-corresponding Internet protocol services, which may specifically include Internet, Intranet, IMS (IP Multimedia Subsystem) and packet-switched streaming services.

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

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

[0521] As an embodiment, the node 203 corresponds to the second node in the present application.

[0522] As an embodiment, the node 203 is a base station (BS).

[0523] As an embodiment, the node 203 is a user equipment.

[0524] As an embodiment, the node 203 is a relay.

[0525] As an embodiment, the node 203 is a gateway.

[0526] As an embodiment, the node 204 corresponds to the third node in the present application.

[0527] As an embodiment, the node 204 corresponds to the fourth node in the present application.

[0528] As an embodiment, the node 204 is a base station device.

[0529] As an embodiment, the node 204 is a user equipment.

[0530] As an embodiment, the node 204 is a relay.

[0531] As an embodiment, the node 204 is a gateway.

[0532] As an embodiment, the node 203 and the node 204 are connected via an ideal backhaul.

[0533] As an embodiment, the node 203 and the node 204 are connected via a non-ideal backhaul.

[0534] As an actual example, the node 203 and the node 204 provide wireless resources for the UE 201 at the same time.

[0535] As an actual example, the node 203 and the node 204 do not provide wireless resources for the UE 201 at the same time.

[0536] As an embodiment, the node 203 and the node 204 are the same node.

[0537] As an embodiment, the node 203 and the node 204 are two different nodes.

[0538] As an embodiment, the node 203 and the node 204 are of the same type.

[0539] As an embodiment, the node 203 and the node 204 are of different types.

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

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

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

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

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

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

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

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

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

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

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

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

[0552] As an embodiment, the base station equipment includes a base transceiver station (Base Transceiver Station, BTS).

[0553] As an embodiment, the base station device includes a Node B (NodeB, NB).

[0554] As an embodiment, the base station device includes a gNB.

[0555] As an embodiment, the base station device includes an eNB.

[0556] As an embodiment, the base station device includes ng-eNB.

[0557] As an embodiment, the base station device includes en-gNB.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0573] As an embodiment, the base station equipment includes an IAB (Integrated Access and Backhaul)-node.

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

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

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

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

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

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

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

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

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

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

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

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

[0586] Example 3

[0587] 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 in this article. 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 (Hybrid Automatic Repeat Request). 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 the 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.

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

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

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

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

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

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

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

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

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

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

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

[0599] Example 4

[0600] 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.

[0601] 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.

[0602] 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 .

[0603] 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.

[0604] 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.

[0605] 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.

[0606] 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.

[0607] 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: receives a first message, the first message includes at least a first information block, the first information block includes at least a first identifier, the first identifier is associated with the first node, and the first information block is indicated to perform data transmission in the RRC inactive state; as a response to the first message being received, determines whether to perform data transmission in the RRC inactive state according to whether a first condition set is met; wherein the first condition set includes: the first message includes a second information block, the second information block includes at least a second identifier, the second identifier is associated with the first node, and the second information block is not indicated to perform data transmission in the RRC inactive state; the behavior determines whether to perform data transmission in the RRC inactive state according to whether the first condition set is met, including: if any condition in the first condition set is not met, determines to perform data transmission in the RRC inactive state; if each condition in the first condition set is met, determines that data transmission in the RRC inactive state is not performed.

[0608] As an embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generates an action when executed by at least one processor, the action including: receiving a first message, the first message including at least a first information block, the first information block including at least a first identifier, the first identifier being associated with the first node, and the first information block being indicated to perform data transmission in an RRC inactive state; as a response to the first message being received, determining whether to perform data transmission in the RRC inactive state according to whether a first condition set is satisfied; wherein the first condition set includes: the first message including a second information block, the second information block including at least a second identifier, the second identifier being associated with the first node, and the second information block not being indicated to perform data transmission in the RRC inactive state; the behavior determining whether to perform data transmission in the RRC inactive state according to whether the first condition set is satisfied includes: if any condition in the first condition set is not satisfied, determining to perform data transmission in the RRC inactive state; if each condition in the first condition set is satisfied, determining that data transmission in the RRC inactive state is not performed.

[0609] 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: sends a first message, the first message includes at least a first information block, the first information block includes at least a first identifier, the first identifier is associated with a first node, and the first information block is indicated to perform data transmission in an RRC inactive state; wherein the first node is a recipient of the first message; whether a first condition set is satisfied is used to determine whether data transmission in the RRC inactive state is performed; the first condition set includes: the first message includes a second information block, the second information block includes at least a second identifier, the second identifier is associated with the first node, and the second information block does not indicate that data transmission is performed in the RRC inactive state; the phrase whether the first condition set is satisfied is used to determine whether data transmission in the RRC inactive state is performed includes: the first condition set is satisfied and is used to determine that data transmission in the RRC inactive state is performed; the first condition set is not satisfied and is used to determine that data transmission in the RRC inactive state is not performed.

[0610] As an embodiment, the second communication device 410 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generates an action when executed by at least one processor, the action including: sending a first message, the first message including at least a first information block, the first information block including at least a first identifier, the first identifier being associated with a first node, and the first information block being indicated to perform data transmission in an RRC inactive state; wherein the first node is a recipient of the first message; whether a first condition set is satisfied is used to determine whether data transmission in the RRC inactive state is executed; the first condition set includes: the first message includes a second information block, the second information block includes at least a second identifier, the second identifier is associated with the first node, and the second information block is not indicated to perform data transmission in the RRC inactive state; the phrase whether the first condition set is satisfied is used to determine whether data transmission in the RRC inactive state is executed includes: the first condition set is satisfied and is used to determine that data transmission in the RRC inactive state is executed; the first condition set is not satisfied and is used to determine that data transmission in the RRC inactive state is not executed.

[0611] As an embodiment, the antenna 452, the receiver 454, the receiving processor 456, and the controller / processor 459 are used to receive a first 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 first message.

[0612] 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.

[0613] 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0629] Example 5

[0630] 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.

[0631] for First node U01 , in step S5101, a first message is received; in step S5102, as a response to the first message being received, it is determined whether a first condition set is satisfied; if each condition in the first condition set is satisfied, the process proceeds to step S5103(a); if any condition in the first condition set is not satisfied, the process proceeds to step S5103(b); in step S5103(a), it is determined that data transmission in the RRC inactive state is not executed; in step S5103(b), it is determined that data transmission in the RRC inactive state is executed.

[0632] for Second node N02 , in step S5201, the first message is sent.

[0633] In Example 5, a first message is received, the first message includes at least a first information block, the first information block includes at least a first identifier, the first identifier is associated with the first node U01, and the first information block is indicated to perform data transmission in an RRC inactive state; the first condition set includes: the first message includes a second information block, the second information block includes at least a second identifier, the second identifier is associated with the first node U01, and the second information block is not indicated to perform data transmission in the RRC inactive state.

[0634] In Example 5, the behavior of determining whether to perform data transmission in the RRC inactive state according to whether the first condition set is satisfied includes: if any condition in the first condition set is not satisfied, determining to perform data transmission in the RRC inactive state; if each condition in the first condition set is satisfied, determining that data transmission in the RRC inactive state is not performed.

[0635] As an embodiment, the first node U01 is a user equipment.

[0636] As an embodiment, the first node U01 is a base station device.

[0637] As an embodiment, the first node U01 is a relay device.

[0638] As an embodiment, the second node N02 is a base station device.

[0639] As an embodiment, the second node N02 is a user equipment.

[0640] As an embodiment, the second node N02 is a relay device.

[0641] As an embodiment, the second node is a maintaining base station of the first cell.

[0642] Typically, the first node U01 is a user equipment and the second node N02 is a gNB.

[0643] Example 6

[0644] 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.

[0645] for First node U01 In step S6101, determine to perform data transmission in the RRC inactive state; in step S6102, if it is determined to perform data transmission in the RRC inactive state, send a second message; in step S6103, along with the second message, restore each radio bearer in the first radio bearer set.

[0646] for The third node N03 , in step S6301, receive the second message.

[0647] In Example 6, the second message is used to request the restoration of the RRC connection; the first radio bearer set includes at least one of at least one DRB of the first node U01 or SRB2 of the first node U01 or at least one multicast MRB of the first node U01; the first message is received within the time interval between the restoration of each radio bearer in the first radio bearer set, and the first node U01 does not receive any RRC message indicating that the first node U01 restores the RRC connection.

[0648] As an embodiment, the third node N03 is a base station device.

[0649] As an embodiment, the third node N03 is a user equipment.

[0650] As an embodiment, the third node N03 is a relay device.

[0651] Typically, the first node U01 is a user equipment, the second node N02 is a gNB, and the third node N03 is a gNB.

[0652] As an embodiment, the third node N03 is the second node N02.

[0653] As an embodiment, the third node N03 is not the second node N02.

[0654] As an embodiment, the first message triggers the second message.

[0655] As an embodiment, the second message is a response to the first message.

[0656] As an embodiment, before determining to perform data transmission in the RRC inactive state, the first message is received, the first message includes at least a first information block, the first information block includes at least a first identifier, the first identifier is associated with the first node U01, and the first information block is indicated to perform data transmission in the RRC inactive state; any condition in the first condition set is not met; the first condition set includes: the first message includes a second information block, the second information block includes at least a second identifier, the second identifier is associated with the first node U01, and the second information block is not indicated to perform data transmission in the RRC inactive state.

[0657] As an embodiment, step S6102 is before step S6103.

[0658] As an embodiment, step S6102 is after step S6103.

[0659] As an embodiment, the first message triggers the second message.

[0660] As an embodiment, the second message is an RRC response to the first message.

[0661] As an embodiment, determining that data transmission is to be performed in the RRC inactive state is used to determine sending the second message.

[0662] As an embodiment, before sending the second message, a unified access control (UAC) process is performed, and the access attempt is considered as allowed.

[0663] As an embodiment, before sending the second message, the unified access control process is not executed.

[0664] As an embodiment, determining that the data transmission performed in the RRC inactive state is triggered by the first message is used to determine that the unified access control process is not performed.

[0665] As an embodiment, the second message includes at least the RRC connection recovery request message.

[0666] As an embodiment, the second message is the RRC connection recovery request message.

[0667] As an embodiment, the second message is an RRC message.

[0668] As an embodiment, the second message includes at least an RRC message.

[0669] As an embodiment, the second message includes at least one RRC IE.

[0670] As an embodiment, the second message includes at least one RRC domain.

[0671] As an embodiment, the second message is transmitted via CCCH (Common Control Channel), and the RRC connection recovery request message is a RRCResumeRequest message.

[0672] As an embodiment, the second message is transmitted via CCCH1, and the RRC connection recovery request message is a RRCResumeRequest1 message.

[0673] As an embodiment, the second message is transmitted via CCCH2, and the RRC connection recovery request message is a RRCResumeRequest2 message.

[0674] As an embodiment, the second message is transmitted via SRB0 (Signalling Radio Bearer 0).

[0675] As an embodiment, the second message includes a resumeIdentity field, and the resumeIdentity field is set to a bit string.

[0676] As an embodiment, the above-mentioned one bit string is the shortI-RNTI of the first node U01.

[0677] As an embodiment, the above-mentioned one bit string is the fullI-RNTI of the first node U01.

[0678] As an embodiment, the above-mentioned bit string includes 24 bits.

[0679] As an embodiment, the above-mentioned one bit string includes 40 bits.

[0680] As an embodiment, the second message includes a resumeMAC-I field, and the resumeMAC-I is set to a bit string.

[0681] As an embodiment, the second message includes a resumeCause field.

[0682] As an embodiment, the value of the resumeCause field in the second message is set to a string.

[0683] As a sub-embodiment of this embodiment, the character string is one of mps-PriorityAccess, mcs-PriorityAccess, highPriorityAccess, or mt-Access.

[0684] As a sub-embodiment of this embodiment, the one character string is mt-Sdt.

[0685] As a sub-embodiment of this embodiment, the name of the character string includes at least one of mt or SDT or Sdt or sdt or dl or DL ​​or Inactive.

[0686] As a sub-embodiment of this embodiment, the one character string is used to indicate data transmission in an RRC inactive state.

[0687] As a sub-embodiment of this embodiment, the one character string is used to indicate unicast transmission in the RRC inactive state.

[0688] As a sub-embodiment of this embodiment, the one character string is used to indicate multicast transmission in the RRC inactive state.

[0689] As a sub-embodiment of this embodiment, the name of the character string includes at least one of MBS or mbs or Mbs or Inactive.

[0690] As an embodiment, the second message is sent via Msg3 (Message 3) or MSGA (Message A) in a random access process.

[0691] As a sub-embodiment of this embodiment, the random access preamble resources in the random access process are not used to indicate SDT.

[0692] As a subsidiary embodiment of this sub-embodiment, the random access preamble resources in the random access process are not configured through FeatureCombinationPreambles.

[0693] As a sub-embodiment of this embodiment, the random access preamble resources in the random access process are used to indicate SDT.

[0694] As a subsidiary embodiment of this sub-embodiment, the random access preamble resources in the random access process are configured through FeatureCombinationPreambles.

[0695] As an embodiment, the second message is sent via the CG resources of CG-SDT.

[0696] As a sub-embodiment of this embodiment, the target message is used to determine the CG resource.

[0697] As an embodiment, along with the second message, the PDCP entity for each radio bearer in the first radio bearer set is rebuilt, and each radio bearer in the first radio bearer set is restored.

[0698] As an embodiment, a PDCP status report is not triggered when the PDCP entity for each radio bearer in the first radio bearer set is reestablished.

[0699] As an embodiment, the “accompanied by the second message” means that the second message is delivered by the RRC layer of the first node U01 to a lower layer of the RRC layer of the first node U01.

[0700] As an embodiment, "accompanied by the second message" means: after the content in the second message is set, and before the second message is delivered to a lower layer of the RRC layer.

[0701] As an embodiment, “accompanied by the second message” means: before the second message is sent.

[0702] As an embodiment, "accompanied by the second message" means: before the second message is sent at the MAC layer.

[0703] As an embodiment, the "accompanying the second message" means: just when the second message is sent at the MAC layer.

[0704] As an embodiment, the “accompanying the second message” means: at least before a confirmation message for the second message is received.

[0705] As an embodiment, the "accompanied by the second message" means that the second message is delivered to a lower layer of the RRC layer after a period of time.

[0706] As an embodiment, the "accompanied by the second message" means: when a lower layer of the RRC layer sends the second message for the first time.

[0707] As an embodiment, the “restoring each radio bearer in the first radio bearer set” includes: restoring all radio bearers in the first radio bearer set.

[0708] As an embodiment, the “restoring each radio bearer in the first radio bearer set” includes: if the first radio bearer set includes at least one multicast MRB, restoring the at least one multicast MRB.

[0709] As an embodiment, the "restoring each radio bearer in the first radio bearer set" includes: if the first radio bearer set includes at least one DRB, restoring the at least one DRB.

[0710] As an embodiment, the "restoring each radio bearer in the first radio bearer set" includes: if the first radio bearer set includes SRB2, restoring the SRB2.

[0711] As an embodiment, before the second message is delivered by the RRC layer of the first node U01 to a lower layer of the RRC layer of the first node U01, SRB1 is restored.

[0712] As an embodiment, along with the second message, the suspended radio bearers outside the SRB1, SRB0 and the first radio bearer set are not restored.

[0713] As an embodiment, the first radio bearer set does not include SRB1 and SRB0.

[0714] As an embodiment, the radio bearers included in the first radio bearer set are explicitly indicated.

[0715] As an embodiment, the radio bearers included in the first radio bearer set are determined by the first node U01.

[0716] As an embodiment, the radio bearers included in the first radio bearer set are implicitly indicated.

[0717] As an embodiment, the number of radio bearers included in the first radio bearer set is configurable.

[0718] As an embodiment, the types of radio bearers included in the first radio bearer set are configurable.

[0719] As an embodiment, the radio bearers included in the first radio bearer set are indicated.

[0720] As an embodiment, the radio bearers included in the first radio bearer set are not indicated.

[0721] As an embodiment, the first radio bearer set includes at least one of at least one DRB of the first node U01 or at least one multicast MRB of the first node U01.

[0722] As an embodiment, the first radio bearer set includes at least one DRB of the first node U01 or at least one of SRB2 of the first node U01, and the first radio bearer set includes at least one multicast MRB of the first node U01.

[0723] As an embodiment, the first radio bearer set includes at least one DRB of the first node U01 or at least one of SRB2 of the first node U01, and the first radio bearer set includes at least one multicast MRB of the first node.

[0724] As an embodiment, the at least one DRB of the first node U01 includes a portion of the DRBs of the first node U01 or all of the DRBs of the first node U01.

[0725] As an embodiment, the at least one multicast MRB of the first node U01 includes some multicast MRBs of the first node U01 or all multicast MRBs of the first node U01.

[0726] As an embodiment, the first radio bearer set includes all DRBs of the first node U01.

[0727] As an embodiment, the first radio bearer set includes all DRBs of the first node U01 and SRB2 of the first node U01.

[0728] As an embodiment, the first radio bearer set includes all multicast MRBs of the first node U01.

[0729] As an embodiment, the first radio bearer set includes the radio bearer associated with the TMGI included in the first message.

[0730] As an embodiment, if a radio bearer is configured with a TMGI, the radio bearer is associated with the TMGI.

[0731] As an embodiment, the first message indicates at least one radio bearer in the first radio bearer set.

[0732] As an embodiment, the target message indicates at least one radio bearer in the first radio bearer set.

[0733] As an embodiment, the SIB1 message indicates at least one radio bearer in the first radio bearer set.

[0734] As an embodiment, at least one of the first message or the target message or the SIB1 indicates at least one radio bearer in the first radio bearer set.

[0735] As an embodiment, the "RRC message instructing the first node U01 to restore the RRC connection" refers to an RRCResume message.

[0736] As an embodiment, the "RRC message instructing the first node U01 to restore the RRC connection" includes at least an RRCResume message.

[0737] As an embodiment, the "RRC message instructing the first node U01 to resume the RRC connection" includes any one of an RRCResume message or an RRCConnectionResume message.

[0738] As an embodiment, the first message is received within a time interval between each radio bearer in the first radio bearer set being restored, and timer T319 or timer T319a or one of the first timers is started.

[0739] As a sub-embodiment of this embodiment, before initiating the sending of the second message, the timer T319 or the timer T319a or one of the first timers is started.

[0740] As a sub-embodiment of this embodiment, before the second message is delivered by the RRC layer of the first node U01 to a lower layer of the RRC layer of the first node U01, the timer T319 or the timer T319a or one of the first timers is started.

[0741] As a sub-embodiment of this embodiment, when the second message is sent for the first time by a lower layer of the RRC layer of the first node U01, the timer T319 or the timer T319a or one of the first timers is started.

[0742] As an embodiment, the timer T319 is T319 in 3GPP TS 38.331.

[0743] As an embodiment, the timer T319a is T319a in 3GPP TS 38.331.

[0744] As an embodiment, the first timer is not T319, and the first timer is not T319a.

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

[0746] As an embodiment, the first timer is T319b.

[0747] As an embodiment, the first timer is T319c.

[0748] As an embodiment, the name of the first timer includes T319.

[0749] As an embodiment, the first timer is a MAC layer timer.

[0750] As an embodiment, within the time interval between when the first message is received and when each radio bearer in the first radio bearer set is restored, any one of the timer T319 or the timer T319a or the first timer is not started.

[0751] Example 7

[0752] 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.

[0753] for First node U01 In step S7101, determine to perform data transmission in the RRC inactive state; in step S7102, if it is determined to perform data transmission in the RRC inactive state, send a second message; in step S7103, receive a first data block as a response to the second message being sent; in step S7104, restore each radio bearer in the first radio bearer set along with the first data block.

[0754] for The third node N03 , in step S7301, receive the second message; in step S7302, send the first data block.

[0755] In Example 7, the second message is used to request the restoration of the RRC connection; the first radio bearer set includes at least one of at least one DRB of the first node U01 or SRB2 of the first node U01 or at least one multicast MRB of the first node U01; the first message is received within the time interval between the restoration of each radio bearer in the first radio bearer set, and the first node U01 does not receive any RRC message indicating that the first node U01 restores the RRC connection.

[0756] As an embodiment, the first data block is a MAC SDU (Service data unit).

[0757] As an embodiment, the first data block is not a CCCH SDU.

[0758] As an embodiment, the first data block is a DTCH (Dedicated Traffic Channel) SDU.

[0759] As an embodiment, the first data block is an MTCH (MBS Traffic Channel) SDU.

[0760] As an embodiment, the first data block is a candidate SDU in a first candidate SDU set.

[0761] As an embodiment, the first candidate SDU set includes at least DTCH SDU.

[0762] As an embodiment, the first candidate SDU set includes at least MTCH SDU.

[0763] As an embodiment, the first candidate SDU set includes a DCCH (Dedicated Control Channel, dedicated control signaling) SDU.

[0764] As an embodiment, the first candidate SDU set includes MCCH (MBS Control Channel) SDU.

[0765] As an embodiment, the first candidate SDU set does not include a DCCH SDU.

[0766] As an embodiment, the first candidate SDU set does not include MCCH SDU.

[0767] As an embodiment, the first candidate SDU set does not include CCCH SDU.

[0768] As an embodiment, the behavior of restoring each radio bearer in the first radio bearer set is independent of whether the first candidate SDU includes a CCCH SDU or a MCCH SDU.

[0769] As an embodiment, accompanying the first data block means: as a response to the first data block being received, the MAC layer of the first node U01 sends a notification to the upper layer of the first node U01, and when the RRC layer of the first node U01 receives the notification.

[0770] As an embodiment, accompanying the first data block means: when the first data block is received.

[0771] As an embodiment, accompanying the first data block means: after the first data block is received.

[0772] As an embodiment, accompanying the first data block means: if the MAC SDU corresponding to the second message is sent through message 3 or message A in a random access process, when the random access process is successfully completed.

[0773] As an embodiment, accompanying the first data block means: if the MAC SDU corresponding to the second message is sent through the CG resources of the CG-SDT process, when the initial transmission of the CG-SDT process is successfully completed.

[0774] As an embodiment, accompanying the first data block means: if the MAC SDU corresponding to the second message is sent through message 3 or message A in a random access process, as a response to the successful completion of the random access process, the MAC layer of the first node U01 sends a notification to the upper layer of the first node U01, and when the RRC layer of the first node U01 receives the notification.

[0775] As an embodiment, accompanying the first data block means: if the MAC SDU corresponding to the second message is sent through the CG resources of the CG-SDT process, as a response to the successful completion of the initial transmission of the CG-SDT process, the MAC layer of the first node U01 sends a notification to the upper layer of the first node U01, and when the RRC layer of the first node U01 receives the notification.

[0776] As an embodiment, the upper layer of the first node U01 includes at least one of an RLC layer, a PDCP layer, or an RRC layer.

[0777] As an embodiment, along with the first data block, a PDCP entity for each radio bearer in the first radio bearer set is rebuilt, and each radio bearer in the first radio bearer set is restored.

[0778] As an embodiment, a PDCP status report is not triggered when the PDCP entity for each radio bearer in the first radio bearer set is reestablished.

[0779] As an embodiment, the first message is received within a time interval between each radio bearer in the first radio bearer set being restored, and timer T319 or timer T319a or one of the first timers is started.

[0780] As an embodiment, within the time interval between when the first message is received and when each radio bearer in the first radio bearer set is restored, any one of the timer T319 or the timer T319a or the first timer is not started.

[0781] Example 8

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

[0783] for First node U01 In step S8101, determine that data transmission in the RRC inactive state is not executed; in step S8102, send a fourth message; in step S8103, receive a third message as a response to the fourth message being sent; in step S8104, restore each radio bearer in the second radio bearer set as a response to the third message being received.

[0784] for Fourth node N04 , in step S8401, receive the fourth message; in step S8402, send the third message.

[0785] In Example 8, the fourth message is used to request the restoration of the RRC connection; the second radio bearer set includes all DRBs of the first node U01 or at least one of all multicast MRBs of the first node U01; within the time interval between the first message being received and the third message being received, any radio bearer in the second radio bearer set is not restored; and the third message instructs the first node U01 to restore the RRC connection.

[0786] As an embodiment, the fourth node N04 is a base station device.

[0787] As an embodiment, the fourth node N04 is a user equipment.

[0788] As an embodiment, the fourth node N04 is a relay device.

[0789] Typically, the first node U01 is a user equipment, the second node N02 is a gNB, and the fourth node N04 is a gNB.

[0790] As an embodiment, the fourth node N04 is the second node N02.

[0791] As an embodiment, the fourth node N04 is not the second node N02.

[0792] As an embodiment, before determining that data transmission in the RRC inactive state is not executed, the first message is received, the first message includes at least a first information block, the first information block includes at least a first identifier, the first identifier is associated with the first node U01, and the first information block is indicated to perform data transmission in the RRC inactive state; each condition in the first condition set is met; the first condition set includes: the first message includes a second information block, the second information block includes at least a second identifier, the second identifier is associated with the first node U01, and the second information block is not indicated to perform data transmission in the RRC inactive state.

[0793] As an embodiment, the first message triggers the fourth message.

[0794] As an embodiment, the fourth message is an RRC response to the first message.

[0795] As an embodiment, determining that data transmission in the RRC inactive state is not performed is used to determine sending the fourth message.

[0796] As an embodiment, before sending the fourth message, a unified access control process is performed, and the access attempt is considered to be allowed.

[0797] As an embodiment, the fourth message includes at least an RRC connection recovery request message.

[0798] As an embodiment, the fourth message is the RRC connection recovery request message.

[0799] As an embodiment, the fourth message is an RRC message.

[0800] As an embodiment, the fourth message includes at least an RRC message.

[0801] As an embodiment, the fourth message includes at least one RRC IE.

[0802] As an embodiment, the fourth message includes at least one RRC domain.

[0803] As an embodiment, the fourth message is transmitted via CCCH, and the fourth message is a RRCResumeRequest message.

[0804] As an embodiment, the fourth message is transmitted via CCCH1, and the fourth message is a RRCResumeRequest1 message.

[0805] As an embodiment, the fourth message is transmitted via SRB0.

[0806] As an embodiment, the fourth message is sent during a random access process.

[0807] As an embodiment, the random access preamble resources in the random access process cannot be used to indicate SDT.

[0808] As an embodiment, the random access preamble resources in the random access process are not configured through FeatureCombinationPreambles.

[0809] As an embodiment, the fourth message includes a resumeIdentity field, and the resumeIdentity field is set to a bit string.

[0810] As an embodiment, the above-mentioned one bit string is the shortI-RNTI of the first node U01.

[0811] As an embodiment, the above-mentioned one bit string is the fullI-RNTI of the first node U01.

[0812] As an embodiment, the above-mentioned bit string includes 24 bits.

[0813] As an embodiment, the above-mentioned one bit string includes 40 bits.

[0814] As an embodiment, the fourth message includes a resumeMAC-I field, and the resumeMAC-I is set to a bit string.

[0815] As an embodiment, the fourth message includes a resumeCause field.

[0816] As an embodiment, the resumeCause field in the fourth message is set to one of mps-PriorityAccess, mcs-PriorityAccess, highPriorityAccess or mt-Access.

[0817] As an embodiment, the first node U01 receives the third message at the RRC layer.

[0818] As an embodiment, the third message is used to resume the suspended RRC connection.

[0819] As an embodiment, the third message is an RRC message.

[0820] As an embodiment, the third message is transmitted via DCCH.

[0821] As an embodiment, the third message is transmitted via SRB1.

[0822] As an embodiment, the name of the third message includes RRCResume.

[0823] As an embodiment, the third message is a RRCResume message.

[0824] As an embodiment, the third message is a downlink message.

[0825] As an embodiment, the third message includes at least one RRC domain.

[0826] As an embodiment, the third message includes at least one RRC IE.

[0827] As an embodiment, the third message is an RRC response to the fourth message.

[0828] As an embodiment, the fourth message triggers the third message.

[0829] As an embodiment, the third message is received while the timer T319 is running.

[0830] As an embodiment, in response to the third message being received, the timer T319 is stopped.

[0831] As an embodiment, the "in response to the third message being received" includes: if the third message is received.

[0832] As an embodiment, the "received as a response to the third message" includes: after the third message is received.

[0833] As an embodiment, the second radio bearer set includes all DRBs of the first node U01 or all multicast MRBs of the first node U01 or at least one of SRB2 of the first node U01 or SRB3 of the first node U01.

[0834] As an embodiment, the second wireless bearer set includes all DRBs of the first node U01, all multicast MRBs of the first node U01, and SRB2 of the first node U01; wherein, SRB3 of the first node U01 is not configured.

[0835] As an embodiment, the second wireless bearer set includes all DRBs of the first node U01, all multicast MRBs of the first node U01, SRB2 of the first node U01, and SRB3 of the first node U01; wherein, SRB3 of the first node is configured.

[0836] As an embodiment, before initiating the sending of the fourth message, start timer T319.

[0837] As an embodiment, before the fourth message is delivered by the RRC layer of the first node U01 to a lower layer of the RRC layer of the first node U01, the timer T319 is started.

[0838] As an embodiment, before the fourth message is delivered by the RRC layer of the first node U01 to a lower layer of the RRC layer of the first node U01, SRB1 is restored.

[0839] As an embodiment, within the time interval between when the first message is received and when the third message is received, the PDCP entity for each radio bearer in the second radio bearer set is not reestablished.

[0840] Example 9

[0841] Embodiment 9 illustrates a structural block diagram of a processing device used in a first node according to an embodiment of the present application; Fig. 9 As shown in the attached Fig. 9 In the example, the processing device 900 in the first node includes a first processor 901 .

[0842] The first processor 901 receives a first message, wherein the first message includes at least a first information block, the first information block includes at least a first identifier, the first identifier is associated with the first node, and the first information block is indicated to perform data transmission in an RRC inactive state; as a response to the first message being received, determining whether to perform data transmission in the RRC inactive state based on whether a first condition set is met.

[0843] In Example 9, the first condition set includes: the first message includes a second information block, the second information block includes at least a second identifier, the second identifier is associated with the first node, and the second information block is not indicated to perform data transmission in the RRC inactive state; the behavior determines whether to perform data transmission in the RRC inactive state according to whether the first condition set is met, including: if any condition in the first condition set is not met, determining to perform data transmission in the RRC inactive state; if each condition in the first condition set is met, determining that data transmission in the RRC inactive state is not performed.

[0844] As an embodiment, the first identifier is used to indicate the first node, and the second identifier indicates an MBS session in which the first node participates.

[0845] As an embodiment, the first identifier indicates an MBS session in which the first node participates, and the second identifier is used to indicate the first node.

[0846] As an embodiment, the first identifier indicates an MBS session in which the first node participates, and the second identifier indicates another MBS session in which the first node participates.

[0847] As an embodiment, the first information block is configured with a first indication which is used to determine that the first information block is instructed to perform data transmission in the RRC inactive state.

[0848] As an embodiment, the second information block is not configured with a second indication which is used to determine that the second information block does not indicate data transmission in the RRC inactive state.

[0849] As an embodiment, the first indication and the second indication are different.

[0850] As an embodiment, the first indication and the second indication are the same.

[0851] As an embodiment, if the first processor 901 determines to perform data transmission in the RRC inactive state, it sends a second message; along with the second message, each radio bearer in the first radio bearer set is restored, or, along with the first data block, each radio bearer in the first radio bearer set is restored; wherein the second message is used to request the restoration of the RRC connection; the first radio bearer set includes at least one DRB of the first node or SRB2 of the first node or at least one multicast MRB of the first node; within the time interval between the restoration of each radio bearer in the first radio bearer set when the first message is received, the first node does not receive any RRC message indicating that the first node restores the RRC connection.

[0852] As an embodiment, the first data block is received as a response to the second message being sent; the first data block includes at least user data.

[0853] As an embodiment, the first processor 901, if it is determined that data transmission in the RRC inactive state is not executed, sends a fourth message; receives a third message as a response to the fourth message being sent; the first processor 901, in response to the third message being received, restores each radio bearer in the second radio bearer set; wherein the fourth message is used to request restoration of the RRC connection; the second radio bearer set includes at least one of all DRBs of the first node or all multicast MRBs of the first node; within the time interval between the first message being received and the third message being received, any radio bearer in the second radio bearer set is not restored; the third message instructs the first node to restore the RRC connection.

[0854] As an embodiment, the first processor 901 includes a first receiver.

[0855] As an embodiment, the first processor 901 includes a first transmitter.

[0856] As an embodiment, the first processor 901 includes at least one of a first receiver or a first transmitter.

[0857] As an embodiment, the first receiver 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.

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

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

[0860] As an embodiment, the first transmitter 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.

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

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

[0863] Example 10

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

[0865] The second transmitter 1001 sends a first message, wherein the first message includes at least a first information block, the first information block includes at least a first identifier, the first identifier is associated with a first node, and the first information block is indicated to perform data transmission in an RRC inactive state.

[0866] In embodiment 10, the first node is a recipient of the first message; whether the first condition set is satisfied is used to determine whether data transmission in the RRC inactive state is executed; the first condition set includes: the first message includes a second information block, the second information block includes at least a second identifier, the second identifier is associated with the first node, and the second information block is not indicated to perform data transmission in the RRC inactive state; the phrase whether the first condition set is satisfied is used to determine whether data transmission in the RRC inactive state is executed includes: the first condition set is satisfied and is used to determine that data transmission in the RRC inactive state is executed; the first condition set is not satisfied and is used to determine that data transmission in the RRC inactive state is not executed.

[0867] As an embodiment, the first identifier is used to indicate a recipient of the first message, and the second identifier indicates an MBS session in which the recipient of the first message participates.

[0868] As an embodiment, the first identifier indicates an MBS session in which the first node participates, and the second identifier is used to indicate the first node.

[0869] As an embodiment, the first identifier indicates an MBS session in which the first node participates, and the second identifier indicates another MBS session in which the first node participates.

[0870] As an embodiment, the first information block is configured with a first indication which is used to determine that the first information block is instructed to perform data transmission in the RRC inactive state.

[0871] As an embodiment, the second information block is not configured with a second indication which is used to determine that the second information block does not indicate data transmission in the RRC inactive state.

[0872] As an embodiment, the first indication and the second indication are different.

[0873] As an embodiment, the first indication and the second indication are the same.

[0874] As an embodiment, the second receiver 1002 receives a second message; wherein, the first node determines that the data transmission performed in the RRC inactive state is used to determine the sending of the second message; along with the second message, each radio bearer in the first radio bearer set is restored, or, along with the first data block, each radio bearer in the first radio bearer set is restored; the first radio bearer set includes at least one DRB of the first node or SRB2 of the first node or at least one multicast MRB of the first node; the second message is used to request the restoration of the RRC connection; within the time interval between the restoration of each radio bearer in the first radio bearer set when the first message is received, the first node does not receive any RRC message indicating that the first node restores the RRC connection.

[0875] As an embodiment, the second transmitter 1001, in response to the second message being received, sends a first data block; the first data block includes at least user data.

[0876] As an embodiment, the second receiver 1002 receives a fourth message; the second transmitter 1001 sends a third message in response to the fourth message being received; wherein, the first node determines that data transmission in the RRC inactive state is not performed and is used to determine the sending of the fourth message; as a response to the third message being received, each radio bearer in the second radio bearer set is restored by the first node; the fourth message is used to request the restoration of the RRC connection; the second radio bearer set includes at least one of all DRBs of the first node or all multicast MRBs of the first node; within the time interval between the first message being received and the third message being received, any radio bearer in the second radio bearer set is not restored; the third message instructs the first node to restore the RRC connection.

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

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

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

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

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

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

[0883] 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.

[0884] 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 processor receives a first message, the first message includes at least a first information block, the first information block includes at least a first identifier, the first identifier is associated with the first node, and the first information block is indicated to perform data transmission in an RRC inactive state; in response to the first message being received, determines whether to perform data transmission in the RRC inactive state according to whether a first condition set is satisfied; Among them, the first condition set includes: the first message includes a second information block, the second information block includes at least a second identifier; the behavior determines whether to perform data transmission in the RRC inactive state according to whether the first condition set is met, including: if any condition in the first condition set is not met, determine to perform data transmission in the RRC inactive state; if each condition in the first condition set is met, determine that data transmission in the RRC inactive state is not performed.

2. The first node according to claim 1, characterized in that: The first identifier is used to indicate the first node, and the second identifier indicates an MBS session in which the first node participates.

3. The first node according to claim 1, characterized in that: The first identifier indicates an MBS session in which the first node participates, and the second identifier is used to indicate the first node.

4. The first node according to claim 1, characterized in that: The first identifier indicates an MBS session in which the first node participates, and the second identifier indicates another MBS session in which the first node participates.

5. The first node according to any one of claims 1 to 4, characterized in that: The first information block is configured with a first indication which is used to determine that the first information block is indicated to perform data transmission in the RRC inactive state; the second information block is not configured with a second indication which is used to determine that the second information block is not indicated to perform data transmission in the RRC inactive state.

6. The first node according to any one of claims 1 to 5, characterized in that: include: The first processor, if determining to perform data transmission in the RRC inactive state, sends a second message; Along with the second message, resuming each radio bearer in the first radio bearer set; The second message is used to request the restoration of the RRC connection; the first radio bearer set includes at least one of at least one DRB of the first node or the SRB2 of the first node or at least one multicast MRB of the first node; the first message is received within the time interval between the restoration of each radio bearer in the first radio bearer set, and the first node does not receive any RRC message indicating that the first node restores the RRC connection.

7. The first node according to any one of claims 1 to 5, characterized in that: include: The first processor, if determining that data transmission in the RRC inactive state is not to be performed, sends a fourth message; receiving a third message in response to the fourth message being sent; In response to receiving the third message, resuming each radio bearer in the second set of radio bearers; The fourth message is used to request the restoration of the RRC connection; the second radio bearer set includes all DRBs of the first node or at least one of all multicast MRBs of the first node; within the time interval between the first message being received and the third message being received, any radio bearer in the second radio bearer set is not restored; and the third message instructs the first node to restore the RRC connection.

8. A second node used for wireless communication, characterized in that: include: A second transmitter sends a first message, wherein the first message includes at least a first information block, the first information block includes at least a first identifier, the first identifier is associated with a first node, and the first information block is indicated to perform data transmission in an RRC inactive state; Among them, the first node is a recipient of the first message; whether the first condition set is satisfied is used to determine whether data transmission in the RRC inactive state is executed; the first condition set includes: the first message includes a second information block, and the second information block includes at least a second identifier; whether the first condition set is satisfied is used to determine whether data transmission in the RRC inactive state is executed, including: the first condition set is satisfied and is used to determine that data transmission in the RRC inactive state is executed; the first condition set is not satisfied and is used to determine that data transmission in the RRC inactive state is not executed.

9. A method in a first node for wireless communication, characterized in that: include: receiving a first message, the first message comprising at least a first information block, the first information block comprising at least a first identifier, the first identifier being associated with the first node, the first information block being indicated to perform data transmission in an RRC inactive state; determining, in response to the first message being received, whether to perform data transmission in the RRC inactive state according to whether a first condition set is satisfied; Among them, the first condition set includes: the first message includes a second information block, the second information block includes at least a second identifier; the behavior determines whether to perform data transmission in the RRC inactive state according to whether the first condition set is met, including: if any condition in the first condition set is not met, determine to perform data transmission in the RRC inactive state; if each condition in the first condition set is met, determine that data transmission in the RRC inactive state is not performed.

10. A method in a second node for wireless communication, characterized in that: include: Sending a first message, the first message including at least a first information block, the first information block including at least a first identifier, the first identifier being associated with a first node, and the first information block being indicated to perform data transmission in an RRC inactive state; Among them, the first node is a recipient of the first message; whether the first condition set is satisfied is used to determine whether data transmission in the RRC inactive state is executed; the first condition set includes: the first message includes a second information block, and the second information block includes at least a second identifier; whether the first condition set is satisfied is used to determine whether data transmission in the RRC inactive state is executed, including: the first condition set is satisfied and is used to determine that data transmission in the RRC inactive state is executed; the first condition set is not satisfied and is used to determine that data transmission in the RRC inactive state is not executed.

Images