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

Abstract

A method and apparatus in a communication node used for wireless communication are disclosed. The communication node receives a first message comprising at least a first information block comprising at least a first identity associated to the first node, the first information block being indicated for data transmission in a RRC inactive state; in response to the first message being received, determines to perform data transmission in the RRC inactive state if any of a first set of conditions is not met, determines that data transmission in the RRC inactive state is not performed if each of the first set of conditions is met, the first set of conditions comprising that the first message comprises a second information block comprising at least a second identity associated to the first node, the second information block is not indicated for data transmission in the RRC inactive state.

Description

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

[0002] --Original application date: June 20, 2022

[0003] --Original application number: 202210698146.2

[0004] --Original Invention Title: A Method and Apparatus Used in a Communication Node for Wireless Communication Technical Field

[0005] This application relates to transmission methods and apparatus in wireless communication systems, and more particularly to transmission methods and apparatus in the RRC inactive state. Background Technology

[0006] NR (New Radio) supports the RRC (Radio Resource Control) inactive (RRC_INACTIVE) RRC state until 3GPP (3rd Generation Partnership Project) Rel-16, which does not support sending or receiving data in the RRC inactive state. Rel-17 launched the "NR Inactive State Small Data Transmission (SDT)" work item (WI), which developed corresponding technical specifications for MO (UL (Uplink))-SDT, allowing the transmission of small packet transmissions of uplink-oriented (UL-oriented) packets in the RRC inactive state. To reduce power consumption, signaling overhead, and latency, Rel-18 established the "MT (DL (Downlink))-SDT (Mobile Terminated-Small Data Transmission)" project to study the triggering mechanism of MT-SDT. Furthermore, it supports RA (Random Access)-SDT and CG (Configured Grant)-SDT as uplink responses, and investigates the MT-SDT process for the initial downlink data reception and subsequent uplink or downlink data transmissions in RRC inactive states. Rel-17 initiated a work item (WI) on "Receiving MBS (Multicast / Broadcast Service) in RRC Connected State". To reduce power consumption, signaling overhead, and latency, Rel-18 established the work item "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 an RRC inactive state, the UE initiates an RRC recovery process and enters the RRC connected state to perform data transmission. The methods for triggering MT-SDT via downlink messages and determining the radio bearers used for MT-SDT need enhancement; similarly, the methods for triggering MBS reception in an RRC inactive state and determining the radio bearers used for MBS reception in an RRC inactive state also need enhancement; furthermore, the triggering mechanism needs enhancement when MT-SDT and MBS reception in an RRC inactive state coexist.

[0008] To address the aforementioned problems, this application provides a solution for data transmission during the inactive state of the RRC. In the problem description above, an NR system is used as an example; this application is also applicable to scenarios such as LTE (Long-Term Evolution) systems. Furthermore, although this application is initially intended for the Uu air interface, it can also be used for the PC5 interface. Furthermore, although this application is initially intended for terminal-base station scenarios, it is also applicable to V2X (Vehicle-to-Everything) scenarios, communication scenarios between terminals and relays, and communication scenarios between relays and base stations, achieving similar technical effects as in terminal-base station scenarios. Furthermore, although this application is initially intended for terminal-base station scenarios, it is also applicable to IAB (Integrated Access and Backhaul) communication scenarios, achieving similar technical effects as in terminal-base station scenarios. Furthermore, although this application was initially intended for terrestrial network scenarios, it is also applicable to non-terrestrial network (NTN) communication scenarios, achieving similar technical effects as in TN scenarios. In addition, adopting a unified solution across different scenarios helps reduce hardware complexity and cost.

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

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

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

[0012] As an example, the interpretation of terms in this application is based on the definitions in the IEEE (Institute of Electrical and Electronics Engineers) specification protocols.

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

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

[0015] 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, the first information block being indicated to perform data transmission in an RRC inactive state; in response to the receipt of the first message, determine whether to perform data transmission in the RRC inactive state based on whether a first set of conditions is satisfied;

[0016] The first set of conditions 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 instructed to perform data transmission in the RRC inactive state; the behavior of determining whether to perform data transmission in the RRC inactive state based on whether the first set of conditions is satisfied includes: if any condition in the first set of conditions is not satisfied, determining to perform data transmission in the RRC inactive state; if each condition in the first set of conditions is satisfied, determining that data transmission in the RRC inactive state is not performed.

[0017] As an example, the problem this application aims to solve includes: how to implement transmission for unicast and multicast by triggering a first message.

[0018] As an example, the problem this application aims to solve includes: how to implement data transmission triggered by a first message in the inactive state of the RRC.

[0019] As an example, the problem this application aims to solve includes: how to determine whether to perform data transmission in the RRC inactive state.

[0020] As an example, the problem this application aims to solve includes: how to shorten transmission latency.

[0021] As an example, the problem this application aims to solve includes: how to reduce state transitions.

[0022] As an example, the problem this application aims to solve includes: how to reduce signaling overhead.

[0023] As an example, the features of the above method include: when the first message includes a plurality of identifiers associated with the first node, and at least one of the identifiers is associated with an information block that instructs the first node to transmit data in the RRC inactive state, determining whether to perform data transmission in the RRC inactive state based on the number of information blocks that instruct the first node to transmit data in the RRC inactive state.

[0024] As an example, the advantages of the above method include: if at least the first information block and the second information block both instruct the first node to transmit data in the RRC inactive state, the transmission delay is shortened, state transitions are reduced, and signaling overhead is lowered by performing data transmission in the RRC inactive state.

[0025] As an example, the advantages of the above method include: accommodating data transmission that cannot be performed in the RRC inactive state, and reducing the transmission latency of data that cannot be performed in the RRC inactive state.

[0026] According to one aspect of this application, the first identifier is used to indicate the first node, and the second identifier indicates an MBS session in which the first node participates.

[0027] According to one aspect of this application, 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 this application, 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 this application, the first information block is configured with a first indication to determine that the first information block is instructed to transmit data in the RRC inactive state.

[0030] According to one aspect of this application, the second information block is not configured with a second indication to determine that the second information block is not instructed to transmit data in the RRC inactive state.

[0031] As one example, the first instruction and the second instruction are different.

[0032] As an example, the first instruction and the second instruction are the same.

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

[0034] If it is determined that data transmission will be performed in the RRC inactive state, a second message is sent; accompanied by the second message, each radio bearer in the first radio bearer set is restored, or accompanied by the first data block, each radio bearer in the first radio bearer set is restored;

[0035] Wherein, the second message is used to request the restoration of the RRC connection; the first radio bearer set includes at least one of the following: 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; during the time interval between the receipt 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 instructing the first node to restore the RRC connection.

[0036] As one embodiment, in response to the sending of the second message, the first data block is received; the first data block includes at least user data.

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

[0038] If it is determined that data transmission in the RRC inactive state will not be performed, a fourth message is sent; in response to the sending of the fourth message, a third message is received; in response to the receiving of the third message, each radio bearer in the second radio bearer set is restored.

[0039] 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; during the time interval between the receipt of the first message and the receipt of the third message, none of the radio bearers in the second radio bearer set has been restored; the third message instructs the first node to restore the RRC connection.

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

[0041] Send 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, the first information block being indicated to transmit data in an RRC inactive state;

[0042] Wherein, the first node is a recipient of the first message; whether a first set of conditions is satisfied is used to determine whether data transmission in the RRC inactive state is performed; the first set of conditions 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 set of conditions is satisfied to determine whether data transmission in the RRC inactive state is performed includes: the first set of conditions being satisfied is used to determine that data transmission in the RRC inactive state is performed; the first set of conditions not being satisfied is used to determine that data transmission in the RRC inactive state is not performed.

[0043] According to one aspect of this application, the first identifier is used to indicate the 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 this application, 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 this application, 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 this application, the first information block is configured with a first indication to determine that the first information block is instructed to perform data transmission in the RRC inactive state; the second information block is not configured with a second indication to determine that the second information block is not instructed to perform data transmission in the RRC inactive state.

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

[0048] Receive the second message;

[0049] Wherein, the first node determines that the data transmission performed in the RRC inactive state is used to determine sending the second message; accompanied by the second message, each radio bearer in the first radio bearer set is restored, or accompanied by the first data block, each radio bearer in the first radio bearer set is restored; the first radio bearer set includes at least one of the first node's DRB or the first node's SRB2 or at least one of the first node's multicast MRB; the second message is used to request the restoration of the RRC connection; during the time interval between the receipt 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 instructing the first node to restore the RRC connection.

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

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

[0052] Received the fourth message;

[0053] In response to the receipt of the fourth message, a third message is sent;

[0054] Wherein, the first node determines that data transmission in the RRC inactive state is not performed to determine sending the fourth message; in response to the receipt of the third message, 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; during the time interval between the receipt of the first message and the receipt of the third message, no radio bearer in the second radio bearer set is restored; the third message instructs the first node to restore the RRC connection.

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

[0056] A first processor receives 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, the first information block being indicated to perform data transmission in an RRC inactive state; in response to the receipt of the first message, it determines whether to perform data transmission in the RRC inactive state based on whether a first set of conditions is satisfied.

[0057] The first set of conditions 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 instructed to perform data transmission in the RRC inactive state; the behavior of determining whether to perform data transmission in the RRC inactive state based on whether the first set of conditions is satisfied includes: if any condition in the first set of conditions is not satisfied, determining to perform data transmission in the RRC inactive state; if each condition in the first set of conditions is satisfied, determining that data transmission in the RRC inactive state is not performed.

[0058] This application discloses a second node used for wireless communication, characterized in that it comprises:

[0059] A second transmitter sends 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 transmit data in an RRC inactive state.

[0060] Wherein, the first node is a recipient of the first message; whether a first set of conditions is satisfied is used to determine whether data transmission in the RRC inactive state is performed; the first set of conditions 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 set of conditions is satisfied to determine whether data transmission in the RRC inactive state is performed includes: any condition in the first set not being satisfied is used to determine that data transmission in the RRC inactive state is performed; each condition in the first set being satisfied is used to determine that data transmission in the RRC inactive state is not performed.

[0061] As an example, compared with conventional solutions, this application has the following advantages:

[0062] - Reduce transmission latency;

[0063] - Reduce state transitions;

[0064] - Reduce signaling overhead.

[0065] This application discloses a method used in a first node of 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 associated with the first node, the first information block indicating data transmission in an RRC inactive state; in response to the receipt of the first message, determine to perform data transmission in the RRC inactive state; in response to the determination to perform data transmission in the RRC inactive state, send a second message; accompanied by the second message, restore each radio bearer in the first radio bearer set, or, accompanied by the first data block, restore each radio bearer in the first radio bearer set;

[0067] Wherein, the second message is used to request the restoration of the RRC connection; the first radio bearer set includes at least one of the first node's DRB or the first node's SRB2 or at least one of the first node's multicast MRB; during the time interval between the receipt 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 instructing the first node to restore the RRC connection.

[0068] According to one aspect of this application, a first data block is received in response to the sending of the second message; the first data block includes at least user data.

[0069] According to one aspect of this application, 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 this application, 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 this application, the first information block is configured with a first indication to determine that the first information block is instructed to transmit data in the RRC inactive state.

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

[0073] Send 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, the first information block being indicated to transmit data in an RRC inactive state; receive a second message;

[0074] In this context, as a response to the receiver of the first message determining that data transmission in the RRC inactive state is to be performed, the second message is sent by the receiver 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 receiver of the first message, or accompanied by a first data block, each radio bearer in the first radio bearer set is restored by the receiver of the first message; the first radio bearer set includes at least one of at least one of the first node's DRB, or the first node's SRB2, or at least one of the first node's multicast MRB; during the time interval between the receipt 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 instructing the first node to restore the RRC connection.

[0075] According to one aspect of this application, a first data block is sent in response to the receipt of the second message; the first data block includes at least user data.

[0076] According to one aspect of this application, 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 this application, 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 this application, the first information block includes a first indication used to determine whether the first information block instructs the first node to transmit data in the RRC inactive state.

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

[0080] A first processor receives a first message, the first message including at least a first information block, the first information block including at least a first identifier associated with the first node, the first information block indicating data transmission in an RRC inactive state; in response to the receipt of the first message, determines to perform data transmission in the RRC inactive state; in response to the determination to perform data transmission in the RRC inactive state, sends a second message; accompanied by the second message, recovers each radio bearer in a first radio bearer set, or, accompanied by the first data block, recovers each radio bearer in the first radio bearer set;

[0081] Wherein, the second message is used to request the restoration of the RRC connection; the first radio bearer set includes at least one of the first node's DRB or the first node's SRB2 or at least one of the first node's multicast MRB; during the time interval between the receipt 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 instructing the first node to restore the RRC connection.

[0082] According to one aspect of this application, a first data block is received in response to the sending of the second message; the first data block includes at least user data.

[0083] This application discloses a second node used for wireless communication, characterized in that it comprises:

[0084] Send 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, the first information block being indicated to transmit data in an RRC inactive state; receive a second message;

[0085] In this context, as a response to the receiver of the first message determining that data transmission in the RRC inactive state is to be performed, the second message is sent by the receiver 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 receiver of the first message, or accompanied by a first data block, each radio bearer in the first radio bearer set is restored by the receiver of the first message; the first radio bearer set includes at least one of at least one of the first node's DRB, or the first node's SRB2, or at least one of the first node's multicast MRB; during the time interval between the receipt 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 instructing the first node to restore the RRC connection.

[0086] As an example, compared with conventional solutions, this application has the following advantages:

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

[0088] - Trigger multicast MBS reception in RRC inactive state by the first identifier in the paging message;

[0089] - During data transmission in the RRC inactive state, determine the appropriate set of recovered radio bearers. Attached Figure Description

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

[0091] Figure 1A A flowchart illustrating the transmission of a first message according to an embodiment of this application is shown;

[0092] Figure 1B A flowchart illustrating the transmission of a first message according to an embodiment of this application is shown;

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

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

[0095] Figure 4 A schematic diagram of a first communication device and a second communication device according to an embodiment of this application is shown;

[0096] Figure 5 A flowchart illustrating a wireless signal transmission process according to an embodiment of this application is shown;

[0097] Figure 6 A flowchart illustrating a wireless signal transmission process according to another embodiment of this application is shown;

[0098] Figure 7 A flowchart illustrating a wireless signal transmission process according to yet another embodiment of this application is shown;

[0099] Figure 8 A flowchart illustrating a wireless signal transmission process according to another embodiment of this application is shown;

[0100] Figure 9 A structural block diagram of a processing apparatus for a first node according to an embodiment of this application is shown;

[0101] Figure 10 A structural block diagram of a processing apparatus for a second node according to an embodiment of this application is shown. Detailed Implementation

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

[0103] Example 1A

[0104] Example 1A illustrates a flowchart of the transmission of a first message according to an embodiment of this application, as shown in the attached diagram. Figure 1A As shown. (Attached) Figure 1A In the diagram, each box represents a step. It is particularly important to emphasize that the order of the boxes does not represent the chronological order of the steps they represent.

[0105] In Embodiment 1A, in step 101A, the first node of this application receives 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 the RRC inactive state; in step 102A, in response to the receipt of the first message, it is determined whether to perform data transmission in the RRC inactive state based on whether a first set of conditions is satisfied; wherein, the first set of conditions 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 of determining whether to perform data transmission in the RRC inactive state based on whether the first set of conditions is satisfied includes: if any condition in the first set of conditions is not satisfied, determining to perform data transmission in the RRC inactive state; if each condition in the first set of conditions is satisfied, determining that data transmission in the RRC inactive state is not performed.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0119] As an example, the first information block is an RRC field.

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

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

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

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

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

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

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

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

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

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

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

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

[0132] As an example, the second information block is an RRC field.

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

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

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

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

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

[0138] As one embodiment, the name of the second information block includes PagingGroup; the second identifier is a second type identifier.

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

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

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

[0142] As an example, the first set of conditions 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 instructed to transmit data in the RRC inactive state.

[0143] As an example, the conditions in the first set of conditions 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 instructed to transmit data in the RRC inactive state.

[0144] As an example, if the first message includes a second information block, the first condition set is satisfied; if the first message does not include a second information block, the first condition set is not satisfied.

[0145] As an example, at least the first message including a second information block is used to determine that the first set of conditions is satisfied.

[0146] As an example, the second information block is any entry in the first message that includes a first-class identifier other than the first identifier associated with the first node and is instructed to transmit data in the RRC inactive state.

[0147] As an example, the second information block is any entry in the first message that includes a second type of identifier in addition to the first identifier associated with the first node and is instructed to transmit data in the RRC inactive state.

[0148] As one embodiment, the second information block is any entry in the first message that includes a first-class 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-class 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 example, 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 transmit data in the RRC inactive state, and if 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 transmit data in the RRC inactive state, the first message does not include the second information block.

[0150] As an example, if the first message does not contain a first-class identifier other than the first identifier associated with the first node and is not indicated to transmit data in the RRC inactive state, the first message does not include the second information block.

[0151] As an example, if the first message does not contain a second type of identifier other than the first identifier associated with the first node and is not indicated to transmit data in the RRC inactive state, the first message does not include the second information block.

[0152] As an example, the first identifier is a first-class identifier; the second identifier is a second-class identifier.

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

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

[0155] As a sub-implementation of this embodiment, if the second list exists, the second type identifier in any entry of 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-implementation of this embodiment, if the second list exists, and at least one entry exists in the second list, a second type 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 instructed to transmit data in an RRC inactive state, the first message does not include the second information block.

[0157] As an example, the first identifier is a first-class identifier; the second identifier is either a first-class identifier or a second-class identifier.

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

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

[0160] As a sub-implementation 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-implementation of this embodiment, if a first 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 exists, and a second type identifier in any entry in the second list is not associated with the first node, then the first message does not include the second information block.

[0162] As a sub-implementation of this embodiment, if the first 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 exists, the second list contains at least one entry, the second type 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 transmit data in an RRC inactive state, the first message does not include the second information block.

[0163] As a sub-implementation of this embodiment, if at least one entry other than the first information block exists in the first list, the first 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 transmit data in an RRC inactive state, and the second list does not exist, and the first message does not include the second information block.

[0164] As a sub-implementation of this embodiment, if at least one entry other than the first information block exists in the first list, a first 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 transmit data in an RRC inactive state, and if the second list exists, a second 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.

[0165] As a sub-implementation of this embodiment, if at least one entry other than the first information block exists in the first list, a first type 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 transmit data in an RRC inactive state, and if the second list exists, at least one entry exists in the second list, a second type 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 transmit data in an RRC inactive state, the first message does not include the second information block.

[0166] As one embodiment, the first identifier is a second type identifier; the second identifier is a first type identifier.

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

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

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

[0170] As a sub-implementation of this embodiment, if the second list exists, and at least one entry exists in the second list, a first-class 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 transmit data in an RRC inactive state, the first message does not include the second information block.

[0171] As one embodiment, the first identifier is a second type identifier; the second identifier is either a first type identifier or a second type identifier.

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

[0173] As a sub-implementation of this embodiment, if at least one entry other than the first information block exists 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 entry in the first list is not indicated to transmit data 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 entries in the first list that is not indicated to transmit data in the RRC inactive state.

[0174] As a sub-implementation 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-implementation 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 exists, and the first type identifier in any entry in the second list is not associated with the first node, then the first message does not include the second information block.

[0176] As a sub-implementation 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 exists, the second list contains at least one entry, the first type 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 transmit data in an RRC inactive state, the first message does not include the second information block.

[0177] As a sub-implementation of this embodiment, if at least one entry other than the first information block exists 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 transmit data in an RRC inactive state, and the second list does not exist, and the first message does not include the second information block.

[0178] As a sub-implementation of this embodiment, if at least one entry other than the first information block exists 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 transmit data in an RRC inactive state, and if 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-implementation of this embodiment, if at least one entry other than the first information block exists 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 transmit data in an RRC inactive state, and the second list exists, at least one entry exists in the second list, the first 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 transmit data in an RRC inactive state, and the first message does not include the second information block.

[0180] As an example, the first identifier is a second type identifier; the second identifier is a second type identifier.

[0181] As a sub-implementation of this embodiment, if at least one entry other than the first information block exists 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 entry in the first list is not indicated to transmit data 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 entries in the first list that is not indicated to transmit data in the RRC inactive state.

[0182] As a sub-implementation 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-implementation of this embodiment, if at least one entry other than the first information block exists in the first list, and 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 transmit data in an RRC inactive state, the first message does not include the second information block.

[0183] As an example, each entry in the second list includes a first-class identifier.

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

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

[0186] As an example, if an entry in the second 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.

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

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

[0189] As an example, the first type of identifier is a user identifier.

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

[0191] As one example, the first type of identifier includes positive integer bits.

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

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

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

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

[0196] As an example, the first type of identifier is PagingUE-Identity.

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

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

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

[0200] As an example, a first-class identifier is indicated by an RRC field whose name includes the ue-Identity.

[0201] As one 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 one 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 example, the second type of identifier is the Temporary Mobile Group Identity (TMGI).

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

[0205] As an example, the second type of identifier includes the identifier of the PLMN and the service identifier.

[0206] As an example, a second-class identifier is indicated by a TMGI field.

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

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

[0209] As an example, a second-class identifier is indicated by an RRC field whose name includes TMGI.

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

[0211] As an example, the PLMN's identifier is configured via PLMN-Identity.

[0212] As an example, the service identifier is an octet string.

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

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

[0215] As an example, the first identifier is a first-class identifier.

[0216] As an example, the first identifier is a second-class identifier.

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

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

[0219] As one embodiment, associating the first identifier with the first node includes: the first identifier being used to indicate the first node.

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

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

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

[0223] As an example, the first identifier is used to indicate that the first node refers to a node whose first identifier matches the fullI-RNTI stored in the first node.

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

[0225] As an example, the second identifier is a first-class identifier.

[0226] As one embodiment, the second identifier is a second type of identifier.

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

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

[0229] As one embodiment, the association of the second identifier with the first node includes: the second identifier being used to indicate the first node.

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

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

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

[0233] As an example, the second identifier is used to indicate that the first node refers to a node whose second identifier matches the fullI-RNTI stored in the first node.

[0234] As an example, 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 one example, 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 one example, 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 example, the first identifier is a first-class identifier; the second identifier is a second-class identifier.

[0238] As an example, the first identifier is a first-class identifier; the second identifier is either a first-class identifier or a second-class identifier.

[0239] As one embodiment, the first identifier is a second type identifier; the second identifier is a first type identifier.

[0240] As one embodiment, the first identifier is a second type identifier; the second identifier is either a first type identifier or a second type identifier.

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

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

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

[0244] As an example, the CG (Configured Grant)-SDT resource is configured to determine that the first information block is instructed to transmit data in the RRC inactive state.

[0245] As an example, the random access resources used to instruct the SDT are configured to determine that the first information block is instructed to transmit data in the RRC inactive state.

[0246] As an example, 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 instructed to transmit data in the RRC inactive state.

[0247] As an example, 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 instructed to transmit data in the RRC inactive state.

[0248] As an example, the first information block is configured with a first indication to determine that the first information block is instructed to transmit data in the RRC inactive state.

[0249] As an example, the second information block is not explicitly indicated to transmit data during the RRC inactive state.

[0250] As an example, the second information block is not implicitly instructed to transmit data in the RRC inactive state.

[0251] As an example, a field in the second information block is used to determine that the second information block is not instructed to transmit data in the RRC inactive state.

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

[0253] As an example, 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 instructed to transmit data in the RRC inactive state.

[0254] As an example, 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 instructed to transmit data in the RRC inactive state.

[0255] As an example, the second information block is not configured. The first indication is used to determine that the second information block is not instructed to transmit data in the RRC inactive state.

[0256] As one embodiment, the second information block is not configured with a second indication to determine that the second information block is not instructed to transmit data in the RRC inactive state.

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

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

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

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

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

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

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

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

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

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

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

[0268] As an example, each entry in the first list includes a first-class identifier.

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

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

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

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

[0273] As a sub-implementation 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-implementation 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-example of this embodiment, the first information block includes a first indication used to determine that the first information block is instructed to transmit data in the RRC inactive state.

[0276] As a sub-implementation 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-implementation of this embodiment, configuring the first information block with the first indication means that the first information block includes the first indication.

[0278] As an example, the first message includes a first bitmap, and each entry in the first list corresponds to a bit in the first bitmap; the first target bit is a bit in the first bitmap that corresponds to the first information block.

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

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

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

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

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

[0284] As a sub-implementation 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 for data transmission in an RRC inactive state.

[0285] As a sub-implementation of this embodiment, if a bit in the first bitmap 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 bitmap 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-implementation of this embodiment, the position of an entry in the first list is used to determine the bit corresponding to the entry in the first bit map.

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

[0288] As a sub-implementation 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-implementation 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-implementation 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-implementation of this embodiment, the first target bit is set to 1.

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

[0293] As a sub-example 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 transmit data in the RRC inactive state.

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

[0295] As one embodiment, the first message includes a first supplementary list, which corresponds to the first list; the first supplementary information block is an entry in the first supplementary list that corresponds to the first information block.

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

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

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

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

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

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

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

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

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

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

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

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

[0308] As a supplementary embodiment of this sub-example, the second information block does not include the first indication used to determine that the second information block was not instructed to transmit data in the RRC inactive state.

[0309] As a supplementary embodiment of this sub-example, the second information block includes the second identifier and the second information block does not include the first indication used to determine that the first node was not instructed to transmit data in the RRC inactive state.

[0310] As a supplementary embodiment of this sub-example, the fact that 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-implementation 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 supplementary embodiment of this sub-example, the second target bit is set to 0.

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

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

[0315] As a supplementary embodiment of this sub-example, the second target bit is set to 0 to determine that the second information block is not instructed to transmit data in the RRC inactive state.

[0316] As a supplementary embodiment of this sub-example, 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 transmit data in the RRC inactive state.

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

[0318] As a sub-implementation 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, the first additional list corresponding 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 supplementary embodiment of this sub-example, the second additional information block does not include the first indication.

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

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

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

[0323] As a supplementary embodiment of this sub-example, the second additional information block does not include the first indication used to determine that the second information block was not instructed to transmit data in the RRC inactive state.

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

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

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

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

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

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

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

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

[0332] As an example, each entry in the second list includes a first-class identifier.

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

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

[0335] As an example, if an entry in the second 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.

[0336] As an example, the second information block does not include a second instruction.

[0337] As a sub-implementation 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-implementation of this embodiment, if an entry in the second list includes the second indication, the entry is indicated to perform data transmission in an 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 an RRC inactive state.

[0339] As a sub-example of this embodiment, the second information block does not include a second indication used to determine that the second information block was not instructed to transmit data in the RRC inactive state.

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

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

[0342] As an example, the first message includes a second bitmap, and each entry in the second list corresponds to a bit in the second bitmap; the second target bit is a bit in the second bitmap that corresponds to the second information block.

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

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

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

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

[0347] As a sub-implementation 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-implementation of this embodiment, if a bit in the second bitmap 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 bitmap 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-implementation of this embodiment, the position of an entry in the second list is used to determine the bit corresponding to the entry in the second bit map.

[0350] As a sub-example 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-implementation 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-implementation 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-implementation 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-implementation of this embodiment, the second target bit is set to 0.

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

[0356] As a sub-implementation 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 transmit data in the RRC inactive state.

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

[0358] As one embodiment, the first message includes a second supplementary list, which corresponds to the second list; the second supplementary information block is an entry in the second supplementary list that corresponds to the second information block.

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

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

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

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

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

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

[0365] As a sub-example of this embodiment, the second additional information block does not include the second indication used to determine that the second information block was not instructed to transmit data in the RRC inactive state.

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

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

[0368] As one 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 one embodiment, the second information block is an entry in either the first list or the second list.

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

[0371] As a sub-implementation 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-implementation of this embodiment, the name of the first candidate list is PagingGroupList, PagingGroupList-r17, or PagingGroupList-r18.

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

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

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

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

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

[0378] As one example, the second candidate list is used for paging for unicast.

[0379] As a sub-implementation 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-implementation of this embodiment, the name of the second candidate list is PagingRecordList, PagingRecordList-r17, or PagingRecordList-r18.

[0381] As a sub-implementation 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-example of this embodiment, each entry in the second candidate list is named PagingRecord-r18 or PagingRecord.

[0383] As a sub-implementation 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 other than the first sub-information block is either NG-5G-S-TMSI or I-RNTI-Value.

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

[0385] As an example, the first candidate supplementary list is relative to the first candidate list.

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

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

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

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

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

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

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

[0393] As an example, a second candidate supplementary list is used for the second candidate list.

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

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

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

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

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

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

[0400] As one example, the first list is used for paging unicast; the second list is used for paging multicast.

[0401] As one example, the first list is used for paging for multicast; the second list is used for paging for unicast.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0417] As an example, the name of the RRC field to which the first indication belongs is the same as the name of the RRC field to which the second indication belongs, but the value of the RRC field to which the first indication belongs is different from the value of the RRC field to which the second indication belongs.

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

[0419] As an example, the first instruction includes an RRC field.

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

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

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

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

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

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

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

[0427] As a sub-implementation of this embodiment, the RRC field includes a bitmap.

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

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

[0430] As one embodiment, the "response as the first message being received" includes: when the first message is received.

[0431] As one embodiment, the "response as the first message being received" includes: after the first message is received.

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

[0433] As a sub-example 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-example 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-example 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-example 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-implementation 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-example of this embodiment, the "unicast transmission in the RRC inactive state" includes: receiving or / and sending at least one of unicast data or unicast signaling in the RRC inactive state.

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

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

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

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

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

[0444] As an example, 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-example 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-example 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-implementation 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-implementation 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-example of this embodiment, the "multicast transmission in the RRC inactive state" includes: receiving or / and sending at least one of multicast data or multicast signaling in the RRC inactive state.

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

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

[0452] As an example, if the first identifier is used to indicate the first node, 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 example, if the first identifier indicates an MBS session in which the first node participates, data transmission in the RRC inactive state includes at least one of transmitting multicast data or multicast signaling in the RRC inactive state.

[0454] As an example, the phrase "the first information block instructs the first node to transmit data in the RRC inactive state" means that the first information block instructs the first node to perform unicast transmission in the RRC inactive state; wherein, the first identifier is used to instruct the first node.

[0455] As an example, the phrase "the first information block instructs the first node to perform data transmission in the RRC inactive state" means that the first information block instructs the first node to perform multicast transmission in the RRC inactive state; wherein, the first identifier indicates an MBS session in which the first node participates.

[0456] As an example, the phrase "the second information block does not instruct the first node to perform data transmission in the RRC inactive state" means that the second information block does not instruct the first node to perform unicast transmission in the RRC inactive state; wherein, the second identifier is used to instruct the first node.

[0457] As an example, the phrase "the second information block does not instruct the first node to perform data transmission in the RRC inactive state" means that the second information block does not instruct the first node to perform multicast transmission in the RRC inactive state; wherein, the second identifier indicates an MBS session in which the first node participates.

[0458] As an example, the statement "the second information block does not instruct the first node to perform data transmission in the RRC inactive state" means that the second information block does not instruct the first node to perform unicast transmission in the RRC inactive state, and the second information block does not instruct the first node to perform multicast transmission in the RRC inactive state.

[0459] As an example, the first information block indicates at least one of multicast data or multicast signaling being transmitted in the RRC inactive state, and the second information block indicates at least one of unicast data or unicast signaling being transmitted 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 example, the first information block indicates at least one of unicast data or unicast signaling being transmitted in the RRC inactive state, and the second information block indicates at least one of multicast data or multicast signaling being transmitted 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 example, the first information block indicates at least one of multicast data or multicast signaling being transmitted in the RRC inactive state, and the second information block indicates at least one of multicast data or multicast signaling being 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 example, the "determining to perform data transmission in the RRC inactive state" includes: determining that data or signaling is transmitted through at least one radio bearer in the first radio bearer set in the RRC inactive state.

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

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

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

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

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

[0468] As an example, the first node receives a Paging message, which 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 transmit data 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 transmit data in an RRC inactive state, it is determined that data transmission in the RRC inactive state will not be performed.

[0469] As an example, the first node receives a Paging message, which includes a pagingGroupList. If the first node participates in an MBS session indicated by a TMGI in the pagingGroupList, and the TMGI is instructed 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 instructed to perform data transmission in an RRC inactive state, it is determined that data transmission in the RRC inactive state will not be performed.

[0470] As an example, the first node receives a Paging message, which includes a pagingGroupList. If the first node participates in an MBS session indicated by a TMGI in the pagingGroupList, and the TMGI is instructed 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 instructed to perform data transmission in an RRC inactive state, it is determined that data transmission in the RRC inactive state will not be performed.

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

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

[0473] As an example, the type of the first identifier and the type of the second identifier are the same.

[0474] As an example, the types of the first identifier and the second identifier are different.

[0475] As one 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 one 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 example, 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 example, the target message is the RRCRelease message.

[0479] As an example, during the time interval between the receipt of the target message and the receipt of the first message, the first node is always in an RRC inactive state.

[0480] As an example, during the time interval between the receipt of the target message and the receipt of the first message, the first node does not send an RRC message via either CCCH or CCCH1.

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

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

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

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

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

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

[0487] As an example, the first target domain is not included in the SuspendConfig of the target message.

[0488] Example 1B

[0489] Example 1B illustrates a flowchart of the transmission of a first message according to an embodiment of this application, as shown in the attached diagram. Figure 1B As shown. (Attached) Figure 1B In the diagram, each box represents a step. It is particularly important to emphasize that the order of the boxes does not represent the chronological order of the steps they represent.

[0490] In Embodiment 1B, in step 101B, the first node of this application receives 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, the first information block being indicated to perform data transmission in an RRC inactive state; in step 102B, in response to the receipt of the first message, it is determined to perform data transmission in the RRC inactive state; in response to the determination to perform data transmission in the RRC inactive state, a second message is sent; accompanied by the second message, each radio bearer in a first radio bearer set is restored; wherein, the second message is used to request the restoration of RRC connection; the first radio bearer set includes at least one of at least one DRB of the first node or SRB2 of the first node or at least one multicast MRB of the first node; during the time interval between the receipt 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 RRC connection.

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

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

[0493] As a sub-implementation 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-implementation of this embodiment, the first radio bearer set includes at least one of the first node's DRBs or at least one of the first node's SRB2s.

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

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

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

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

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

[0500] As an example, 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-implementation of this embodiment, the first radio bearer set includes all multicast MRBs of the first node U01.

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

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

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

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

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

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

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

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

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

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

[0512] As an example, CG-SDT resources are configured to determine that the first information block is instructed to transmit data in the RRC inactive state.

[0513] As an example, the random access resources used to instruct the SDT are configured to determine that the first information block is instructed to transmit data in the RRC inactive state.

[0514] As an example, 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 instructed to transmit data in the RRC inactive state.

[0515] As an example, 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 instructed to transmit data in the RRC inactive state.

[0516] As an example, the first information block is configured with a first indication to determine that the first information block is instructed to transmit data in the RRC inactive state.

[0517] Example 2

[0518] Example 2 illustrates a schematic diagram of a network architecture according to an embodiment of this application, as shown in the attached diagram. Figure 2 As shown. (Attached) Figure 2This describes the network architecture 200 of a 5G NR (New Radio) / LTE (Long-Term Evolution) / LTE-A (Long-Term Evolution Advanced) system. The 5G NR / LTE / LTE-A network architecture 200 can also be referred to as 5GS (5G System) / EPS (Evolved Packet System) 200, or some other suitable term. 5GS / EPS 200 includes at least one of UE (User Equipment) 201, RAN (Radio Access Network) 202, 5GC (5G Core Network) / EPC (Evolved Packet Core) 210, HSS (Home Subscriber Server) / UDM (Unified Data Management) 220, and Internet services 230. 5GS / EPS can interconnect with other access networks, but these entities / interfaces are not shown for simplicity. As shown in the figure, 5GS / EPS provides packet-switched services; however, those skilled in the art will readily understand that the various concepts presented throughout this application can be extended to networks providing circuit-switched services or other cellular networks. The RAN includes node 203 and other nodes 204. Node 203 provides user and control plane protocol termination to UE 201. Node 203 can be connected to other nodes 204 via an Xn interface (e.g., backhaul) / X2 interface. Node 203 may also be referred to as a base station, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP (transmitter-receiver node), or some other suitable term. Node 203 provides UE 201 with an access point to the 5GC / EPC 210. Examples of UE201 include cellular phones, smartphones, 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 IoT devices, machine-type communication devices, land vehicles, automobiles, wearable devices, or any other similar functional devices. Those skilled in the art may also refer to UE201 as a mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handheld device, user agent, mobile client, client, or any other suitable term.Node 203 connects to 5GC / EPC210 via the S1 / NG interface. 5GC / EPC210 includes MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MME / AMF / SMFs 214, S-GW (Service Gateway) / UPF (User Plane Function) 212, and P-GW (Packet Data Network Gateway) / UPF 213. MME / AMF / SMF 211 is the control node handling signaling between UE201 and 5GC / EPC210. ​​Generally, MME / AMF / SMF 211 provides bearer and connection management. All user IP (Internet Protocol) packets are transmitted through S-GW / UPF 212, which is itself connected to P-GW / UPF 213. The P-GW provides UE IP address allocation and other functions. The P-GW / UPF213 connects to Internet service 230. Internet service 230 includes carrier-compliant Internet protocol services, specifically including the Internet, intranet, IMS (IP Multimedia Subsystem), and packet-switched streaming services.

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

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

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

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

[0523] As one example, node 203 is a user equipment.

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

[0525] As one example, node 203 is a gateway.

[0526] As an example, node 204 corresponds to the third node in this application.

[0527] As an example, node 204 corresponds to the fourth node in this application.

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

[0529] As one example, node 204 is a user equipment.

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

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

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

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

[0534] As a practical example, nodes 203 and 204 simultaneously provide radio resources for UE201.

[0535] As a practical example, node 203 and node 204 do not simultaneously provide radio resources to UE 201.

[0536] In one embodiment, node 203 and node 204 are the same node.

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

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

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

[0540] As one example, the user equipment supports transmission over a non-terrestrial network (NTN).

[0541] As one example, the user equipment supports transmission over a non-terrestrial network (terrestrial network).

[0542] As an example, the user equipment supports transmission in networks with large latency differences.

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

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

[0545] As one embodiment, the user equipment includes an in-vehicle terminal.

[0546] As one example, the user equipment includes a vessel.

[0547] As one example, the user equipment includes an Internet of Things (IoT) terminal.

[0548] As one example, the user equipment includes a terminal for the Industrial Internet of Things (IIoT).

[0549] As one embodiment, the user equipment includes devices that support low-latency, high-reliability transmission.

[0550] As one embodiment, the user equipment includes testing equipment.

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

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

[0553] As one embodiment, the base station equipment includes a NodeB (NB).

[0554] As one embodiment, the base station equipment includes a gNB.

[0555] As one example, the base station equipment includes an eNB.

[0556] As one example, the base station equipment includes an ng-eNB.

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

[0558] As an example, the base station equipment supports transmission over non-terrestrial networks.

[0559] As one example, the base station equipment supports transmission in networks with large latency differences.

[0560] As one example, the base station equipment supports transmission over a terrestrial network.

[0561] As one example, the base station equipment includes a macrocell base station.

[0562] As one embodiment, the base station equipment includes a microcell base station.

[0563] As one example, the base station equipment includes a pico cell base station.

[0564] As one example, the base station equipment includes a femtocell.

[0565] As one embodiment, the base station equipment includes base station equipment that supports large latency differences.

[0566] As one embodiment, the base station equipment includes flight platform equipment.

[0567] As one example, the base station equipment includes satellite equipment.

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

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

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

[0571] As one embodiment, the base station equipment includes testing equipment.

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

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

[0574] As one example, the base station equipment includes an IAB-donor.

[0575] As one embodiment, the base station equipment includes IAB-donor-CU.

[0576] As one embodiment, the base station equipment includes IAB-donor-DU.

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

[0578] As one example, the base station equipment includes IAB-MT.

[0579] As one example, the relay includes a relay.

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

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

[0582] As one example, the relay includes a router.

[0583] As one example, the relay includes a switch.

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

[0585] As one example, the relay includes base station equipment.

[0586] Example 3

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

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

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

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

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

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

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

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

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

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

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

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

[0599] Example 4

[0600] Example 4 shows schematic diagrams of a first communication device and a second communication device according to this application, as shown in the appendix. Figure 4 As shown. Figure 4 This is a block diagram of a first communication device 450 and a second communication device 410 communicating with each other in the access network.

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

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

[0603] In the transmission from the second communication device 410 to the first communication device 450, at the second communication device 410, upper-layer data packets from the core network are provided to the controller / processor 475. The controller / processor 475 implements L2 layer functionality. In the transmission from the second communication device 410 to the first communication device 450, the controller / processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the first communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for retransmitting lost packets and signaling to the first communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., the physical layer). Transmit processor 416 performs encoding and interleaving to facilitate forward error correction (FEC) at the second communication device 410, and mapping of signal clusters based on various modulation schemes (e.g., Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), M-Phase Shift Keying (M-PSK), M-QAM). Multi-antenna transmit processor 471 performs digital spatial precoding on the encoded and modulated symbols, including codebook-based and non-codebook-based precoding, and beamforming processing, generating one or more spatial streams. Transmit processor 416 then maps each spatial stream to subcarriers, multiplexes it with a reference signal (e.g., a pilot) in the time and / or frequency domains, and subsequently uses inverse fast Fourier transform (IFFT) to generate a physical channel carrying the time-domain multicarrier symbol stream. Multi-antenna transmit processor 471 then performs transmit analog precoding / beamforming operations on the time-domain multicarrier symbol stream. Each transmitter 418 converts the baseband multicarrier symbol stream provided by the multi-antenna transmitter processor 471 into an radio frequency stream, which is then provided to different antennas 420.

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

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

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

[0607] As one embodiment, the first communication device 450 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used with the at least one processor, and the first communication device 450 at least: receives a first message, 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, the first information block being indicated to perform data transmission in an RRC inactive state; as a response to the receipt of the first message, determining whether to perform data transmission in the RRC inactive state based on whether a first set of conditions is satisfied; wherein, the first set of conditions 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, the second information block not being indicated to perform data transmission in the RRC inactive state; the action of determining whether to perform data transmission in the RRC inactive state based on whether a first set of conditions is satisfied includes: if any condition in the first set of conditions is not satisfied, determining to perform data transmission in the RRC inactive state; if each condition in the first set of conditions is satisfied, determining that data transmission in the RRC inactive state is not performed.

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

[0609] As one embodiment, the second communication device 410 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used with the at least one processor. The second communication device 410 at least: sends a first message, the first message including at least a first information block, the first information block including at least a first identifier associated with a first node, the first information block being indicated for data transmission in an RRC inactive state; wherein the first node is a receiver of the first message; whether a first set of conditions is satisfied is used to determine whether data transmission in the RRC inactive state is performed; the first set of conditions includes: the first message including a second information block, the second information block including at least a second identifier associated with the first node, the second information block not being indicated for data transmission in the RRC inactive state; the phrase whether the first set of conditions is satisfied to determine whether data transmission in the RRC inactive state is performed includes: the first set of conditions being satisfied is used to determine that data transmission in the RRC inactive state is performed; the first set of conditions not being satisfied is used to determine that data transmission in the RRC inactive state is not performed.

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

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

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

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

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

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

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

[0617] As an example, the first communication device 450 is a user equipment that supports large latency differences.

[0618] As an example, the first communication device 450 is a user device that supports NTN.

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

[0620] As an example, the first communication device 450 has positioning capabilities.

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

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

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

[0624] As an example, the second communication device 410 is a base station device that supports large latency differences.

[0625] As one embodiment, the second communication device 410 is a base station device that supports NTN.

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

[0627] As one embodiment, the second communication device 410 is a flight platform device.

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

[0629] Example 5

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

[0631] for First node U01 In step S5101, a first message is received; in step S5102, as a response to the receipt of the first message, it is determined whether a first set of conditions is satisfied; if each condition in the first set of conditions is satisfied, proceed to step S5103(a); if any condition in the first set of conditions is not satisfied, proceed to step S5103(b); in step S5103(a), it is determined that data transmission in the RRC inactive state will not be executed; in step S5103(b), it is determined that data transmission in the RRC inactive state will be 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 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 U01, the first information block being indicated to perform data transmission in the RRC inactive state; 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 U01, the second information block not being indicated to perform data transmission in the RRC inactive state.

[0634] In Example 5, the behavior of determining whether to execute data transmission in the RRC inactive state based on whether a first set of conditions is met includes: if any condition in the first set of conditions is not met, determining to execute data transmission in the RRC inactive state; if each condition in the first set of conditions is met, determining that data transmission in the RRC inactive state is not executed.

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

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

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

[0638] As one example, the second node N02 is a base station device.

[0639] As one example, the second node N02 is a user equipment.

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

[0641] In one embodiment, the second node is the sustaining 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] Example 6 illustrates a wireless signal transmission flowchart according to yet another embodiment of this application, as shown in the attached diagram. Figure 6 As shown. It should be noted that the order in this example does not limit the order of signal transmission and implementation in this application.

[0645] for First node U01 In step S6101, it is determined that data transmission will be performed in the RRC inactive state; in step S6102, if it is determined that data transmission will be performed in the RRC inactive state, a second message is sent; in step S6103, each radio bearer in the first radio bearer set is restored along with the second message.

[0646] for Third node N03 In step S6301, the second message is received.

[0647] In Embodiment 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 of the first node U01's DRB, or the first node U01's SRB2, or the first node U01's at least one multicast MRB; during the time interval between the receipt of the first message and the restoration of each radio bearer in the first radio bearer set, the first node U01 does not receive any RRC message instructing the first node U01 to restore the RRC connection.

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

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

[0650] As an example, 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 example, the third node N03 is the second node N02.

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

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

[0655] As one example, the second message is a response to the first message.

[0656] As an example, before determining whether to perform data transmission in the RRC inactive state, the first message is received, 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 U01, the first information block being indicated to perform data transmission in the RRC inactive state; any condition in the first condition set is not satisfied; 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 U01, the second information block not being indicated to perform data transmission in the RRC inactive state.

[0657] As an example, step S6102 occurs before step S6103.

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

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

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

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

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

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

[0664] As an example, determining that 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 executed.

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

[0666] As one example, the second message is the RRC connection recovery request message.

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

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

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

[0670] As an example, the second message includes at least one RRC field.

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

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

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

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

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

[0676] As an example, the aforementioned bit string is the shortI-RNTI of the first node U01.

[0677] As an example, the aforementioned bit string is the fullI-RNTI of the first node U01.

[0678] As an example, the bit string described above consists of 24 bits.

[0679] As an example, the bit string described above consists of 40 bits.

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

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

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

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

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

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

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

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

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

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

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

[0691] As a sub-example of this embodiment, the random access preamble resource in the random access procedure is not used to indicate SDT.

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

[0693] As a sub-example of this embodiment, the random access preamble resource in the random access procedure is used to indicate the SDT.

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

[0695] As an example, the second message is sent via CG-SDT's CG resources.

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

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

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

[0699] As an example, "accompanying the second message" means: 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.

[0700] As an example, "accompanying the second message" means: after the content of the second message has been set, and before the second message is delivered to a lower layer of the RRC layer.

[0701] As an example, "accompanying the second message" means before the second message is sent.

[0702] As an example, "accompanying the second message" means that the second message is sent before the MAC layer.

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

[0704] As an example, "accompanying the second message" means at least before an acknowledgment message for the second message is received.

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

[0706] As an example, "accompanying the second message" means when the second message is first sent by a lower layer of the RRC layer.

[0707] As one embodiment, "recovering each radio bearer in the first radio bearer set" includes: recovering all radio bearers in the first radio bearer set.

[0708] As one embodiment, the "recovering each radio bearer in the first radio bearer set" includes: if the first radio bearer set includes at least one multicast MRB, recovering the at least one multicast MRB.

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

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

[0711] As an example, SRB1 is restored 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.

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

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

[0714] As an example, the wireless bearers included in the first set of wireless bearers are explicitly indicated.

[0715] As an example, the wireless bearers included in the first set of wireless bearers are determined by the first node U01.

[0716] As an example, the wireless bearers included in the first set of wireless bearers are implicitly indicated.

[0717] As one embodiment, the number of wireless bearers included in the first set of wireless bearers is configurable.

[0718] As one embodiment, the types of wireless bearers included in the first set of wireless bearers are configurable.

[0719] As an example, the wireless bearers included in the first set of wireless bearers are indicated.

[0720] As an example, the wireless bearers included in the first set of wireless bearers are not indicated.

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

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

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

[0724] As one embodiment, 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 one embodiment, at least one multicast MRB of the first node U01 includes a portion of the multicast MRB of the first node U01 or all of the multicast MRBs of the first node U01.

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

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

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

[0729] As an example, the first set of radio bearers includes the radio bearers associated with the TMGI included in the first message.

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

[0731] As an example, the first message indicates at least one wireless bearer in the first set of wireless bearers.

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

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

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

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

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

[0737] As an example, the "RRC message instructing the first node U01 to restore the RRC connection" includes either the RRCResume message or the RRCConnectionResume message.

[0738] As an example, during the time interval between the receipt of the first message and the recovery of each radio bearer in the first radio bearer set, timer T319 or timer T319a or one of the first timers is started.

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

[0740] As a sub-implementation 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-implementation of this embodiment, when the second message is first sent 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 example, the timer T319 is T319 in 3GPP TS 38.331.

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

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

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

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

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

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

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

[0750] As an example, during the time interval between the receipt of the first message and the recovery of each radio bearer in the first radio bearer set, timer T319 or timer T319a or any one of the first timers is not started.

[0751] Example 7

[0752] Example 7 illustrates a wireless signal transmission flowchart according to yet another embodiment of this application, as shown in the attached diagram. Figure 7 As shown. It should be noted that the order in this example does not limit the order of signal transmission and implementation in this application.

[0753] for First node U01 In step S7101, it is determined that data transmission in the RRC inactive state will be performed; in step S7102, if it is determined that data transmission in the RRC inactive state will be performed, a second message is sent; in step S7103, in response to the sending of the second message, a first data block is received; in step S7104, each radio bearer in the first radio bearer set is restored along with the first data block.

[0754] for Third node N03 In step S7301, the second message is received; in step S7302, the first data block is sent.

[0755] In Embodiment 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 of the first node U01's DRB, or the first node U01's SRB2, or the first node U01's multicast MRB; during the time interval between the receipt of the first message and the restoration of each radio bearer in the first radio bearer set, the first node U01 does not receive any RRC message instructing the first node U01 to restore the RRC connection.

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

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

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

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

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

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

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

[0763] As an example, the first candidate SDU set includes DCCH (Dedicated Control Channel) SDUs.

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

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

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

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

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

[0769] As an example, accompanying the first data block means that, in response to the receipt of the first data block, the MAC layer of the first node U01 sends a notification to the upper layer of the first node U01 when the RRC layer of the first node U01 receives the notification.

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

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

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

[0773] As an example, the first data block refers to the following: 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 example, accompanying the first data block means that if the MAC SDU corresponding to the second message is sent through message 3 or message A in a random access procedure, as a response that the random access procedure has been successfully completed, the MAC layer of the first node U01 sends a notification to the upper layer of the first node U01 when the RRC layer of the first node U01 receives the notification.

[0775] As an example, the accompanying first data block means that 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 when the RRC layer of the first node U01 receives the notification.

[0776] As an example, 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 example, along with the first data block, the PDCP entity for each radio bearer in the first radio bearer set is reconstructed, and each radio bearer in the first radio bearer set is restored.

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

[0779] As an example, during the time interval between the receipt of the first message and the recovery of each radio bearer in the first radio bearer set, timer T319 or timer T319a or one of the first timers is started.

[0780] As an example, during the time interval between the receipt of the first message and the recovery of each radio bearer in the first radio bearer set, timer T319 or timer T319a or any one of the first timers is not started.

[0781] Example 8

[0782] Example 8 illustrates a wireless signal transmission flowchart according to another embodiment of this application, as shown in the attached diagram. Figure 8 As shown. It should be noted that the order in this example does not limit the order of signal transmission and implementation in this application.

[0783] for First node U01 In step S8101, it is determined that data transmission in the RRC inactive state will not be performed; in step S8102, a fourth message is sent; in step S8103, a third message is received in response to the sending of the fourth message; in step S8104, each radio bearer in the second radio bearer set is restored in response to the receiving of the third message.

[0784] for Fourth node N04 In step S8401, the fourth message is received; in step S8402, the third message is sent.

[0785] In Embodiment 8, 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 U01 or all multicast MRBs of the first node U01; during the time interval between the receipt of the first message and the receipt of the third message, none of the radio bearers in the second radio bearer set has been restored; the third message instructs the first node U01 to restore the RRC connection.

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

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

[0788] As an example, 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 example, the fourth node N04 is the second node N02.

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

[0792] As an example, before determining that data transmission in the RRC inactive state will not be performed, the first message is received, 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 U01, the first information block being indicated to perform data transmission in the RRC inactive state; each condition in the first condition set is satisfied; 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 U01, the second information block not being indicated to perform data transmission in the RRC inactive state.

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

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

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

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

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

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

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

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

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

[0802] As an example, the fourth message includes at least one RRC field.

[0803] As an example, the fourth message is transmitted via CCCH, and the fourth message is an RRRCResumeRequest message.

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

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

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

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

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

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

[0810] As an example, the aforementioned bit string is the shortI-RNTI of the first node U01.

[0811] As an example, the aforementioned bit string is the fullI-RNTI of the first node U01.

[0812] As an example, the bit string described above consists of 24 bits.

[0813] As an example, the bit string described above consists of 40 bits.

[0814] As an example, the fourth message includes a resumeMAC-I field, which is set to a bit string.

[0815] As an example, the fourth message includes a resumeCause field.

[0816] As an example, the resumeCause field in the fourth message is set to one of mps-PriorityAccess, mcs-PriorityAccess, highPriorityAccess, or mt-Access.

[0817] As an example, the first node U01 receives the third message at the RRC layer.

[0818] As an example, the third message is used to resume the suspended RRC connection.

[0819] As an example, the third message is an RRC message.

[0820] As an example, the third message is transmitted via DCCH.

[0821] As an example, the third message is transmitted via SRB1.

[0822] As an example, the name of the third message includes RRCResume.

[0823] As an example, the third message is an RRCResume message.

[0824] As an example, the third message is a downlink message.

[0825] As an example, the third message includes at least one RRC field.

[0826] As an example, the third message includes at least one RRC IE.

[0827] As an example, the third message is an RRC response to the fourth message.

[0828] As an example, the fourth message triggers the third message.

[0829] As an example, the third message is received during the operation of the timer T319.

[0830] As an example, in response to the receipt of the third message, the timer T319 is stopped.

[0831] As one embodiment, the "response as the third message being received" includes: if the third message is received.

[0832] As one embodiment, the "response as the third message being received" includes: after the third message is received.

[0833] As one embodiment, the second radio bearer set includes at least one of all DRBs of the first node U01, all multicast MRBs of the first node U01, SRB2 of the first node U01, or SRB3 of the first node U01.

[0834] As one embodiment, the second radio 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 one embodiment, the second radio 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 example, timer T319 is started before the fourth message is sent.

[0837] As an example, timer T319 is started 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.

[0838] As an example, SRB1 is restored 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.

[0839] As an example, during the time interval between the receipt of the first message and the receipt of the third message, the PDCP entity for each radio bearer in the second radio bearer set is not reconstructed.

[0840] Example 9

[0841] Example 9 illustrates a structural block diagram of a processing apparatus for a first node according to an embodiment of this application; as shown in the appendix. Figure 9 As shown. In the appendix Figure 9 In the first node, the processing device 900 includes a first processor 901.

[0842] A first processor 901 receives 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, the first information block being indicated to perform data transmission in an RRC inactive state; in response to the receipt of the first message, it determines whether to perform data transmission in the RRC inactive state based on whether a first set of conditions is satisfied.

[0843] In Example 9, the first set of conditions 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 of determining whether to perform data transmission in the RRC inactive state based on whether the first set of conditions is satisfied includes: if any condition in the first set of conditions is not satisfied, determining to perform data transmission in the RRC inactive state; if each condition in the first set of conditions is satisfied, determining that data transmission in the RRC inactive state is not performed.

[0844] As an example, 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 one example, 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 one example, 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 example, the first information block is configured with a first indication to determine that the first information block is instructed to transmit data in the RRC inactive state.

[0848] As one embodiment, the second information block is not configured with a second indication to determine that the second information block is not instructed to transmit data in the RRC inactive state.

[0849] As one example, the first instruction and the second instruction are different.

[0850] As an example, the first instruction and the second instruction are the same.

[0851] As one embodiment, if the first processor 901 determines that data transmission is to be performed in the RRC inactive state, it sends a second message; accompanied by the second message, it restores each radio bearer in the first radio bearer set, or, accompanied by a first data block, it restores each radio bearer in the first radio bearer set; wherein 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 of the first node's DRB or the first node's SRB2 or at least one of the first node's multicast MRB; during the time interval between the receipt 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 instructing the first node to restore the RRC connection.

[0852] As one embodiment, in response to the sending of the second message, the first data block is received; the first data block includes at least user data.

[0853] As one embodiment, if the first processor 901 determines that data transmission in the RRC inactive state will not be performed, it sends a fourth message; in response to the sending of the fourth message, it receives a third message; in response to the receiving of the third message, the first processor 901 restores each radio bearer in the second radio bearer set; wherein 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; during the time interval between the receiving of the first message and the receiving of the third message, none of the radio bearers in the second radio bearer set has been restored; the third message instructs the first node to restore the RRC connection.

[0854] As one embodiment, the first processor 901 includes a first receiver.

[0855] As one embodiment, the first processor 901 includes a first transmitter.

[0856] As one embodiment, the first processor 901 includes at least one of a first receiver or a first transmitter.

[0857] As one embodiment, the first receiver includes the appendix to this application. Figure 4 The components include antenna 452, receiver 454, multi-antenna receiver processor 458, receiver processor 456, controller / processor 459, memory 460, and data source 467.

[0858] As one embodiment, the first receiver includes the appendix to this application. Figure 4The antenna is 452, the receiver is 454, the multi-antenna receiver processor is 458, and the receiver processor is 456.

[0859] As one embodiment, the first receiver includes the appendix to this application. Figure 4 The antenna is 452, the receiver is 454, and the receiver processor is 456.

[0860] As one embodiment, the first transmitter includes the appendix to this application. Figure 4 The components include antenna 452, transmitter 454, multi-antenna transmission processor 457, transmission processor 468, controller / processor 459, memory 460, and data source 467.

[0861] As one embodiment, the first transmitter includes the appendix to this application. Figure 4 The antenna 452, transmitter 454, multi-antenna transmission processor 457, and transmission processor 468 are included.

[0862] As one embodiment, the first transmitter includes the appendix to this application. Figure 4 The antenna is 452, the transmitter is 454, and the transmitter processor is 468.

[0863] Example 10

[0864] Example 10 illustrates a structural block diagram of a processing apparatus for a second node according to an embodiment of this application; as shown in the appendix. Figure 10 As shown. In the appendix Figure 10 In the second node, the processing device 1000 includes a second transmitter 1001 and a second receiver 1002.

[0865] The second transmitter 1001 sends 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 instructed to transmit data in an RRC inactive state.

[0866] In Example 10, the first node is a receiver of the first message; whether a first set of conditions is satisfied is used to determine whether data transmission in the RRC inactive state is performed; the first set of conditions 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; whether the phrase "whether the first set of conditions is satisfied is used to determine whether data transmission in the RRC inactive state is performed" includes: the first set of conditions being satisfied is used to determine that data transmission in the RRC inactive state is performed; the first set of conditions not being satisfied is used to determine that data transmission in the RRC inactive state is not performed.

[0867] As one embodiment, the first identifier is used to indicate the recipient of the first message, and the second identifier indicates an MBS session in which the recipient of the first message participates.

[0868] As one example, 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 one example, 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 example, the first information block is configured with a first indication to determine that the first information block is instructed to transmit data in the RRC inactive state.

[0871] As one embodiment, the second information block is not configured with a second indication to determine that the second information block is not instructed to transmit data in the RRC inactive state.

[0872] As one example, the first instruction and the second instruction are different.

[0873] As an example, the first instruction and the second instruction are the same.

[0874] As one embodiment, the second receiver 1002 receives a second message; wherein, the first node's determination to perform data transmission in the RRC inactive state is used to determine sending the second message; accompanied by the second message, each radio bearer in the first radio bearer set is restored, or, accompanied by a first data block, each radio bearer in the first radio bearer set is restored; the first radio bearer set includes at least one of at least one of the first node's DRB or the first node's SRB2 or at least one of the first node's multicast MRB; the second message is used to request the restoration of the RRC connection; during the time interval between the first message being received and each radio bearer in the first radio bearer set being restored, the first node does not receive any RRC message instructing the first node to restore the RRC connection.

[0875] As one embodiment, the second transmitter 1001, in response to the receipt of the second message, sends a first data block; the first data block includes at least user data.

[0876] As one embodiment, a second receiver 1002 receives a fourth message; a second transmitter 1001, in response to the receipt of the fourth message, sends a third message; wherein, the first node determines that data transmission in the RRC inactive state will not be performed to determine to send the fourth message; in response to the receipt of the third message, 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; during the time interval between the receipt of the first message and the receipt of the third message, no radio bearer in the second radio bearer set is restored; the third message instructs the first node to restore the RRC connection.

[0877] As one embodiment, the second transmitter 1001 includes the appendix to this application. Figure 4 The antenna 420, transmitter 418, multi-antenna transmission processor 471, transmission processor 416, controller / processor 475, and memory 476 are included.

[0878] As one embodiment, the second transmitter 1001 includes the appendix to this application. Figure 4 The antenna 420, transmitter 418, multi-antenna transmission processor 471, and transmission processor 416 are included.

[0879] As one embodiment, the second transmitter 1001 includes the appendix to this application. Figure 4 The antenna is 420, the transmitter is 418, and the transmitter processor is 416.

[0880] As one embodiment, the second receiver 1002 includes the appendix to this application. Figure 4 The antenna 420, receiver 418, multi-antenna receiver processor 472, receiver processor 470, controller / processor 475, and memory 476 are included.

[0881] As one embodiment, the second receiver 1002 includes the appendix to this application. Figure 4 The antenna 420, receiver 418, multi-antenna receiver processor 472, and receiver processor 470 are included.

[0882] As one embodiment, the second receiver 1002 includes the appendix to this application. Figure 4 The antenna is 420, the receiver is 418, and the receiver processor is 470.

[0883] Those skilled in the art will understand that all or part of the steps in the above methods can be implemented by a program instructing related hardware, and the program can be stored in a computer-readable storage medium, such as a read-only memory, hard disk, or optical disk. Optionally, all or part of the steps in the above embodiments can also be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiments can be implemented in hardware or in the form of software functional modules. This application is not limited to any specific combination of software and hardware. The user equipment, terminal, and UE in this application include, but are not limited to, drones, communication modules on drones, remote-controlled aircraft, aircraft, small aircraft, mobile phones, tablets, laptops, vehicle-mounted communication devices, wireless sensors, internet cards, IoT terminals, RFID terminals, NB-IoT terminals, MTC (Machine Type Communication) terminals, eMTC (enhanced MTC) terminals, data cards, internet cards, vehicle-mounted communication devices, low-cost mobile phones, low-cost tablets, and other wireless communication devices. The base station or system equipment in this application includes, but is not limited to, macrocell base stations, microcell base stations, home base stations, relay base stations, gNB (NR Node B), TRP (Transmitter Receiver Point), and other wireless communication equipment.

[0884] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A user equipment (UE) used for wireless communication, characterized in that, include: The processor receives a first message, which is a paging message, including at least a first information block. The first information block includes at least a first identifier associated with the UE, and the first information block is instructed to perform data transmission in a Radio Resource Control (RRC) inactive state. In response to the receipt of the first message, the processor determines whether to perform data transmission in the RRC inactive state based on whether a first set of conditions is met. Wherein, the first condition set includes one condition: the first message includes a second information block, the second information block includes at least a second identifier; the second identifier indicates a multicast broadcast service (MBS) session in which the UE participates, and the step of determining whether to execute data transmission in the RRC inactive state based on whether the first condition set is satisfied includes: if any condition in the first condition set is not satisfied, determining to execute data transmission in the RRC inactive state; or, if each condition in the first condition set is satisfied, determining that data transmission in the RRC inactive state is not executed.

2. The UE according to claim 1, characterized in that, The first information block is configured with a first indication to determine that the first information block is instructed to transmit data in the RRC inactive state; the second information block is not configured with a second indication to determine that the second information block is not instructed to transmit data in the RRC inactive state.

3. The UE according to claim 1, characterized in that, include: If the processor determines that data transmission is to be performed in the inactive state of the RRC, it sends a second message; Along with the second message, 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 of the UE's data radio bearer DRB, the UE's SRB2, or the UE's multicast MRB; during the time interval between the receipt of the paging message and the restoration of each radio bearer in the first radio bearer set, the UE does not receive any RRC message instructing the UE to restore the RRC connection.

4. The UE according to claim 1, characterized in that, include: If the processor determines that data transmission in the RRC inactive state will not be performed, it sends a fourth message. In response to the sending of the fourth message, the third message is received; In response to the receipt of the third message, each radio bearer in the second radio bearer set is restored; 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 UE or all multicast MRBs of the UE; during the time interval between the paging message being received and the third message being received, none of the radio bearers in the second radio bearer set has been restored; the third message instructs the UE to restore the RRC connection.

5. A base station used for wireless communication, characterized in that, include: The transmitter sends a first message, which is a paging message, including at least a first information block. The first information block includes at least a first identifier associated with a user equipment (UE). The first information block is instructed to transmit data in a Radio Resource Control (RRC) inactive state. Wherein, the UE is a receiver of the first message; whether a first set of conditions is satisfied is used to determine whether data transmission in the RRC inactive state is performed; the first set of conditions includes a condition: the first message includes a second information block, the second information block includes at least a second identifier, the second identifier indicating a multicast broadcast service (MBS) session in which the UE participates; each condition in the first set being satisfied is used to determine that data transmission in the RRC inactive state is performed; or, any condition in the first set not being satisfied is used to determine that data transmission in the RRC inactive state is not performed.

6. A method used in a UE for wireless communication, characterized in that, include: Receive a first message, the first message being a paging 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 UE, the first information block being indicated to perform data transmission in an RRC inactive state; in response to the receipt of the first message, determine whether to perform data transmission in the RRC inactive state based on whether a first set of conditions is satisfied; The first condition set includes one condition: the first message includes a second information block, the second information block includes at least a second identifier, the second identifier indicates a multicast broadcast service (MBS) session in which the UE participates, and determining whether to execute data transmission in the RRC inactive state based on whether the first condition set is satisfied includes: if any condition in the first condition set is not satisfied, determining to execute data transmission in the RRC inactive state; or, if each condition in the first condition set is satisfied, determining that data transmission in the RRC inactive state is not executed.

7. A method used in a base station for wireless communication, characterized in that, include: Send a first message, which is a paging 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 UE, and the first information block being instructed to transmit data in an RRC inactive state; Wherein, the UE is a receiver of the first message; whether a first set of conditions is satisfied is used to determine whether data transmission in the RRC inactive state is performed, the first set of conditions includes a condition: the first message includes a second information block, the second information block includes at least a second identifier; the second identifier indicates a multicast broadcast service (MBS) session in which the UE participates, each condition in the first set being satisfied is used to determine that data transmission in the RRC inactive state is performed; or, any condition in the first set not being satisfied is used to determine that data transmission in the RRC inactive state is not performed.

Images