CN117098252A

CN117098252A - Method and apparatus in a communication node for wireless communication

Info

Publication number: CN117098252A
Application number: CN202210560312.2A
Authority: CN
Inventors: 于巧玲; 张晓博
Original assignee: Shanghai Langbo Communication Technology Co Ltd
Current assignee: Shanghai Langbo Communication Technology Co Ltd
Priority date: 2022-05-11
Filing date: 2022-05-23
Publication date: 2023-11-21

Abstract

A method and apparatus in a communication node for wireless communication is disclosed. The communication node receiving a first message in an RRC inactive state, the first message including a first identity, the first identity being associated to the first node; if the first message does not indicate data transmission in the RRC inactive state, setting the first field in the second message to a first value and not recovering each radio bearer in the first set of radio bearers; if the first message indicates data transmission in the RRC inactive state, setting a first field in the second message to a second value, and recovering each radio bearer in the first set of radio bearers, the second message including an RRC connection recovery request message; the first domain is used to indicate a cause of the RRC connection resume request; sending a second message; the first radio bearer set includes at least one of SRB2 or DRB or multicast MRB; the first value is one of a first set of candidate values and the second value is one of a second set of candidate values.

Description

Method and apparatus in a communication node for wireless communication

Technical Field

The present application relates to a transmission method and apparatus in a wireless communication system, and more particularly, to a transmission method and apparatus for small data.

Background

The NR (New Radio, new air interface) supports the RRC (Radio Resource Control ) _INACTIVE State (State) until release 3GPP (the 3rd Generation Partnership Project, third Generation partnership project) Rel-16 does not support transmitting or receiving data in the RRC INACTIVE State. Rel-17 developed a "NR inactive state small data transfer (Small Data Transmission, SDT)" Work Item (WI), and a corresponding technical specification was formulated for MO (UL) SDT, allowing small data packet transfer (small packet transmission) of Uplink (UL-oriented) packets to be sent in RRC inactive state. MO-SDT includes two modes, RA (Random Access) -SDT and CG (Configured Grant) -SDT, CG-SDT carries data by sending uplink data on a preconfigured PUSCH (Physical Uplink Shared Channel ) resource, RA-SDT uses Message 3 (Message 3, msg 3) or Message B (Message B, msg B) in a Random Access (RA) procedure; rel-17 developed a work item of "receiving MBS (Multicast/broadcast service) in RRC connected state". To reduce power consumption, reduce signaling overhead, shorten latency, rel-18 holds the work item "MT (DL) -SDT (Mobile Terminated-Small Data Transmission)", studies on the trigger mechanism of MT-SDT, and supports RA-SDT and CG-SDT as uplink responses, and studies on the MT-SDT procedure for initial Downlink data reception (initial DL data reception) and subsequent uplink or Downlink data transmission (subsequent UL/DL data transmissions) in RRC inactive state.

Disclosure of Invention

In the existing protocol, when the UE receives a Paging (Message) in an RRC inactive state, the UE initiates an RRC connection Resume (Resume) procedure in response to receiving the Paging Message, and sends an RRC connection Resume request Message in the RRC Resume procedure. For the RRC connection recovery procedure triggered by the paging message, the UE can perform downlink data reception only if it receives the RRC connection recovery message and recovers all radio bearers. For MT-SDT, one possible solution to shorten the delay is to recover the radio bearer for MT-SDT in advance, and the base station sends the downlink data in advance. The base station cannot determine whether the UE has recovered the radio bearer for the MT-SDT according to the existing RRC connection recovery request message, thereby affecting the initial downlink data transmission. Therefore, for MT-SDT, the RRC connection recovery procedure needs to be enhanced.

The present application provides a solution to the above-mentioned problems for small data transmissions. In the description for the above problems, MT-SDT in the RRC inactive state is taken as an example; the application is also applicable to the multicast MBS scene in the RRC inactive state, and achieves the technical effect similar to the MT-SDT in the RRC inactive state. Further, while the present application is initially directed to Uu air interfaces, the present application can also be used for PC5 interfaces. Further, although the present application is initially directed to a terminal and base station scenario, the present application is also applicable to a V2X (Vehicle-to-internet) scenario, a communication scenario between a terminal and a relay, and a communication scenario between a relay and a base station, and similar technical effects in the terminal and base station scenario are obtained. Further, although the present application is initially directed to the terminal and base station scenario, the present application is also applicable to the communication scenario of IAB (Integrated Access and Backhaul ), and achieves similar technical effects in the terminal and base station scenario. Further, although the present application is initially directed to a terrestrial network (Terrestrial Network ) scenario, the present application is equally applicable to a Non-terrestrial network (Non-Terrestrial Network, NTN) communication scenario, achieving similar technical effects in a TN scenario. Furthermore, the adoption of a unified solution for different scenarios also helps to reduce hardware complexity and cost.

As an embodiment, the explanation of the term (terminalogy) in the present application refers to the definition of the 3GPP specification protocol TS36 series.

As an embodiment, the explanation of the terms in the present application refers to the definition of the 3GPP specification protocol TS38 series.

As an embodiment, the explanation of the terms in the present application refers to the definition of the specification protocol TS37 series of 3 GPP.

As an example, the explanation of terms in the present application refers to the definition of the specification protocol of IEEE (Institute of Electrical and Electronics Engineers ).

It should be noted that, in the case of no conflict, the embodiments of any node of the present application and the features in the embodiments may be applied to any other node. The embodiments of the application and the features of the embodiments may be combined with each other arbitrarily without conflict.

As one embodiment, the problems to be solved by the present application include: how to indicate MT-SDT in RRC resume request message.

As one embodiment, the problems to be solved by the present application include: how to set resumeau in the RRC resume request message.

As one embodiment, the problems to be solved by the present application include: how to determine the radio bearer used for data transmission in the RRC inactive state.

As one embodiment, the problems to be solved by the present application include: how to detect transmission failure when the RRC is inactive for data transmission.

As one embodiment, the problems to be solved by the present application include: how to reduce power consumption.

The application discloses a method used in a first node of wireless communication, which is characterized by comprising the following steps:

receiving a first message in an RRC inactive state, the first message including a first identity, the first identity being associated with the first node;

transmitting a second message as a response to the first message being received, the second message including an RRC connection resume request message; setting a first domain in the second message according to at least whether the first message indicates that the first node performs data transmission in the RRC inactive state and determining whether to recover each radio bearer in a first set of radio bearers, the first domain being used to indicate a cause of an RRC connection recovery request;

wherein the act of setting the first domain in the second message and determining whether to resume each radio bearer in the first set of radio bearers based on at least whether the first message indicates that the first node is in the RRC inactive state comprises: if the first message does not indicate that the first node is in the RRC inactive state for data transmission, setting the first field in the second message to a first value, and not recovering each radio bearer in the first set of radio bearers; if the first message indicates that the first node performs data transmission in the RRC inactive state, setting the first domain in the second message to a second value, and recovering each radio bearer in the first radio bearer set; the first radio bearer set includes at least one of SRB2 (Signalling Radio Bearer, signaling radio bearer 2) or DRB (user Data Radio Bearer ) or multicast (multicast) MRB (MBS Radio Bearer); the first value is one of a first candidate value set, and the first candidate value set comprises at least one value; the second value is one of a second set of candidate values, the second set of candidate values including at least one value therein.

As one embodiment, the features of the above method include: the first identifier is indicated in a paging message, and the paging message can indicate that the first node performs data transmission in the RRC inactive state.

As one embodiment, the features of the above method include: the first identity indicates the first node.

As one embodiment, the features of the above method include: the first identity indicates TMGI (Temporary Mobile Group Identity) associated with the first node.

As one embodiment, the features of the above method include: the data transmission in the RRC inactive state refers to MT-SDT.

As one embodiment, the features of the above method include: transmitting data in the RRC inactive state refers to receiving a multicast MBS in the RRC inactive state.

As one embodiment, the features of the above method include: the first candidate set and the second candidate set are the same.

As one embodiment, the features of the above method include: the first set of candidate values and the second set of candidate values are different.

As one embodiment, the features of the above method include: before sending the RRC resume request message, all radio bearers in the first set of radio bearers are resumed.

As one embodiment, the features of the above method include: the MT-SDT is indicated in the RRC connection resume request message.

As one example, the benefits of the above method include: shortening the transmission delay.

As one example, the benefits of the above method include: the power consumption is reduced.

As one example, the benefits of the above method include: the signaling overhead is reduced.

According to one aspect of the application, a third message is received before the first message, the third message indicating the first set of radio bearers;

wherein the third message is used to determine to enter or remain in the RRC inactive state.

According to an aspect of the application, if the first message indicates that the first node is transmitting data in the RRC inactive state, a second domain is used to indicate that the first node is transmitting data in the RRC inactive state, the second domain being associated with the second message; the first candidate set and the second candidate set are the same.

As one embodiment, the features of the above method include: if the first message indicates that the first node performs data transmission in the RRC inactive state, the first domain is not used for indicating MT-SDT, and the second domain is used for indicating MT-SDT.

According to an aspect of the present application, if the first message indicates that the first node performs data transmission in the RRC inactive state, the first field in the second message is set to the second value to be used for indicating that data transmission is performed in the RRC inactive state; the first set of candidate values and the second set of candidate values are different.

As one embodiment, the features of the above method include: the first domain is used to indicate MT-SDT if the first message indicates that the first node is transmitting data in the RRC inactive state.

According to an aspect of the application, if the first message indicates that the first node is transmitting data in the RRC inactive state, whether the second candidate set of values and the first candidate set of values are the same relates to at least one of whether PUSCH resources carrying at least the second message are indicated by the third message or whether a random access preamble associated with the second message is associated to an SDT.

As one embodiment, the problems to be solved by the present application include: if the RA-SDT and CG-SDT are acting as uplink responses for the MT-SDT, the random access preamble of the RA-SDT or CG resources of the CG-SDT can indicate that the RRC connection recovery procedure is an SDT procedure, the existing recovery reasons can indicate that the RRC connection recovery procedure is triggered by downlink data, and the base station can know that the UE recovers the radio bearer for the MT-SDT. If a non-SDT (non-SDT) RRC connection recovery procedure is used as the uplink response, the existing recovery reasons can indicate that the RRC connection recovery procedure is triggered by downlink data, but no other information indicates that the RRC connection recovery procedure is an SDT procedure, the base station cannot know whether the UE recovers the radio bearer for the MT-SDT.

As one embodiment, the features of the above method include: if the first message indicates that the first node performs data transmission in the RRC inactive state, and a PUSCH resource carrying the second message is indicated by the third message or a random access preamble associated with the second message is associated to SDT, the second candidate value set is the same as the first candidate value set.

As one embodiment, the features of the above method include: if the first message indicates that the first node is in the RRC inactive state for data transmission, and a PUSCH resource carrying the second message is not indicated by the third message, and a random access preamble associated with the second message is not associated to an SDT, the second candidate value set is different from the first candidate value set.

As one embodiment, the features of the above method include: if the first message indicates that the first node performs data transmission in the RRC inactive state, and a PUSCH resource carrying the second message is indicated by the third message or a random access preamble associated with the second message is associated to an SDT, the first domain is not used to indicate MT-SDT.

As one embodiment, the features of the above method include: if the first message indicates that the first node performs data transmission in the RRC inactive state, and PUSCH resources carrying the second message are not indicated by the third message, and a random access preamble associated with the second message is not associated to SDT, the first domain is used to indicate MT-SDT.

As one example, the benefits of the above method include: indicating as much information as possible.

As one example, the benefits of the above method include: and the access probability is improved.

As one example, the benefits of the above method include: if the RRC connection recovery procedure of the non-SDT is not supported as an uplink response to the paging message of the MT-SDT, the first domain does not need to be enhanced, and the standardization effect is reduced.

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

if the first message indicates that the first node performs data transmission in the RRC inactive state, monitoring a fourth message during the operation of a first timer as a response to the second message being sent; stopping the first timer if a fourth message is received; if the first timer expires, entering an RRC idle state;

Wherein the fourth message is not associated to any radio bearer in the first set of radio bearers.

and starting the first timer along with the second message.

receiving a first data block after the second message is sent; restarting a first timer in response to the first data block being received;

wherein the first data block is associated to one radio bearer of the first set of radio bearers.

receiving a first data block after the second message is sent; starting or restarting a second timer in response to the first data block being received;

According to an aspect of the present application, the first message indicates the first set of radio bearers, or the target domain is used to determine the first set of radio bearers, or the third message indicates the first set of radio bearers, or the first identity is used to determine the first set of radio bearers.

The application discloses a method used in a second node of wireless communication, which is characterized by comprising the following steps:

transmitting a first message, the first message including a first identification, the first identification being associated with a recipient of the first message;

receiving a second message as a response to the first message being sent, the second message including an RRC connection resume request message;

wherein the receiver of the first message receives the first message in an RRC inactive state; with the second message, at least whether the first message indicates that the recipient of the first message is in the RRC inactive state for data transmission is used by the recipient of the first message to set a first field in the second message and determine whether to recover each radio bearer in a first set of radio bearers, the first field being used to indicate a cause of an RRC connection recovery request; the phrase whether at least the first message indicates that the recipient of the first message is in the RRC inactive state for data transmission is used by the recipient of the first message to set a first domain in the second message and to determine whether to resume each radio bearer in a first set of radio bearers includes: the first message not indicating that the data transmission by the recipient of the first message in the RRC inactive state is used to determine to set the first field in the second message to a first value and not to recover each radio bearer in the first set of radio bearers; the first message indicating that data transmission by a receiver of the first message in the RRC inactive state is used to determine to set the first field in the second message to a second value and to resume each radio bearer in the first set of radio bearers; the first radio bearer set includes at least one of SRB2 or DRB or multicast MRB; the first value is one of a first candidate value set, and the first candidate value set comprises at least one value; the second value is one of a second set of candidate values, the second set of candidate values including at least one value therein.

According to an aspect of the application, a third message is sent before the first message, the third message indicating the first set of radio bearers; the third message is used to determine to enter or remain in the RRC inactive state.

According to an aspect of the application, it is characterized in that if the first message indicates that the recipient of the first message is transmitting data in the RRC inactive state, a second domain is used to indicate that data is transmitting in the RRC inactive state, the second domain being associated to the second message; the first candidate set and the second candidate set are the same.

According to an aspect of the present application, if the first message indicates that the receiver of the first message is transmitting data in the RRC inactive state, the first field in the second message is set to the second value to indicate that data is being transmitted in the RRC inactive state; the first set of candidate values and the second set of candidate values are different.

According to an aspect of the application, if the first message indicates that the receiver of the first message is transmitting data in the RRC inactive state, whether the second candidate set and the first candidate set are the same is related to at least one of whether PUSCH resources carrying at least the second message are indicated by the third message or whether a random access preamble associated with the second message is associated to an SDT.

determining whether to send a fourth message as a response to the second message being received if the first message indicates that the recipient of the first message is transmitting data in the RRC inactive state;

wherein the fourth message is listened to by a recipient of the first message during operation of a first timer; if a fourth message is received by a recipient of the first message, the first timer is stopped; if the first timer expires, the receiver of the first message enters an RRC idle state; the fourth message is not associated to any radio bearer in the first set of radio bearers.

According to one aspect of the application, the first timer is started by the recipient of the first message accompanying the second message.

transmitting a first data block after the second message is received;

wherein a second timer is started or restarted by the recipient of the first message in response to the first data block being received by the recipient of the first message; the first data block is associated to one radio bearer of the first set of radio bearers.

The application discloses a first node used for wireless communication, which is characterized by comprising the following components:

a first receiver that receives a first message in an RRC inactive state, the first message including a first identity, the first identity being associated with the first node;

a first transmitter that transmits a second message as a response to the first message being received, the second message including an RRC connection restoration request message; setting a first domain in the second message according to at least whether the first message indicates that the first node performs data transmission in the RRC inactive state and determining whether to recover each radio bearer in a first set of radio bearers, the first domain being used to indicate a cause of an RRC connection recovery request;

wherein the act of setting the first domain in the second message and determining whether to resume each radio bearer in the first set of radio bearers based on at least whether the first message indicates that the first node is in the RRC inactive state comprises: if the first message does not indicate that the first node is in the RRC inactive state for data transmission, setting the first field in the second message to a first value, and not recovering each radio bearer in the first set of radio bearers; if the first message indicates that the first node performs data transmission in the RRC inactive state, setting the first domain in the second message to a second value, and recovering each radio bearer in the first radio bearer set; the first radio bearer set includes at least one of SRB2 or DRB or multicast MRB; the first value is one of a first candidate value set, and the first candidate value set comprises at least one value; the second value is one of a second set of candidate values, the second set of candidate values including at least one value therein.

The present application discloses a second node used for wireless communication, which is characterized by comprising:

a second transmitter that transmits a first message, the first message including a first identification, the first identification being associated with a recipient of the first message;

a second receiver that receives a second message as a response to the first message being transmitted, the second message including an RRC connection restoration request message;

As an embodiment, the present application has the following advantages over the conventional scheme:

shorten transmission delay;

reducing power consumption;

reducing signaling overhead;

indicate as much information as possible;

increasing the access probability;

reducing the effect of standardization.

Drawings

Other features, objects and advantages of the present application will become more apparent upon reading of the detailed description of non-limiting embodiments, made with reference to the following drawings in which:

FIG. 1 illustrates a flow chart of the transmission of a first message and a second message according to one embodiment of the application;

FIG. 2 shows a schematic diagram of a network architecture according to one embodiment of the application;

fig. 3 shows a schematic diagram of an embodiment of a radio protocol architecture of a user plane and a control plane according to an embodiment of the application;

FIG. 4 shows a schematic diagram of a first communication device and a second communication device according to one embodiment of the application;

fig. 5 shows a wireless signal transmission flow diagram according to one embodiment of the application;

fig. 6 shows a schematic diagram of a second field in a second message being used to indicate data transmission in an RRC inactive state according to an embodiment of the present application;

Fig. 7 shows a schematic diagram in which a first field in a second message is set to a second value to indicate data transmission in an RRC inactive state according to an embodiment of the present application;

fig. 8 shows a schematic diagram of whether the second candidate set and the first candidate set are the same in relation to at least one of whether PUSCH resources carrying at least the second message are indicated by the third message or whether a random access preamble associated with the second message is associated to the SDT, according to an embodiment of the application;

fig. 9 shows a wireless signal transmission flow diagram according to another embodiment of the application;

FIG. 10 shows a block diagram of a processing arrangement for use in a first node according to an embodiment of the application;

FIG. 11 shows a block diagram of a processing arrangement for use in a second node according to an embodiment of the application;

fig. 12 shows a wireless signal transmission flow chart according to yet another embodiment of the present application;

fig. 13 shows a wireless signal transmission flow chart according to still another embodiment of the present application.

Detailed Description

The technical scheme of the present application will be described in further detail with reference to the accompanying drawings, and it should be noted that, without conflict, the embodiments of the present application and features of the embodiments may be arbitrarily combined with each other.

Example 1

Embodiment 1 illustrates a flow chart of the transmission of a first message and a second message according to one embodiment of the application, as shown in fig. 1. In fig. 1, each block represents a step, and it is emphasized that the order of the blocks in the drawing does not represent temporal relationships between the represented steps.

In embodiment 1, a first node in the present application receives a first message in an RRC inactive state in step 101, the first message including a first identity, the first identity being associated to the first node; in step 102, sending a second message as a response to the first message being received, the second message including an RRC connection resume request message; setting a first domain in the second message according to at least whether the first message indicates that the first node performs data transmission in the RRC inactive state and determining whether to recover each radio bearer in a first set of radio bearers, the first domain being used to indicate a cause of an RRC connection recovery request; wherein the act of setting the first domain in the second message and determining whether to resume each radio bearer in the first set of radio bearers based on at least whether the first message indicates that the first node is in the RRC inactive state comprises: if the first message does not indicate that the first node is in the RRC inactive state for data transmission, setting the first field in the second message to a first value, and not recovering each radio bearer in the first set of radio bearers; if the first message indicates that the first node performs data transmission in the RRC inactive state, setting the first domain in the second message to a second value, and recovering each radio bearer in the first radio bearer set; the first radio bearer set includes at least one of SRB2 or DRB or multicast MRB; the first value is one of a first candidate value set, and the first candidate value set comprises at least one value; the second value is one of a second set of candidate values, the second set of candidate values including at least one value therein.

As an embodiment, the RRC INACTIVE state is an rrc_inactive state.

As an embodiment, the RRC inactive state is not an rrc_idle state.

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

As an embodiment, the first message comprises an RRC message.

As an embodiment, the first message is an RRC message.

As an embodiment, the first message comprises at least one RRC IE (Information Element ).

For one embodiment, the first message includes at least one RRC Field.

As an embodiment, the first message is a Paging message.

As an embodiment, the first message includes an RRC field including a name of Paging, group, or List.

As an embodiment, the first message includes an RRC field including a name of Paging, record, or List.

As an embodiment, the first message includes a pagerecord list.

As an embodiment, the first message includes a PagingGroupList-r17.

As an embodiment, a field in the first message indicates the first identity.

As an embodiment, a field in the first message is set to the first identity.

As a sub-embodiment of this embodiment, the one field in the first message is a pagerecord field.

As a sub-embodiment of this embodiment, the one field in the first message is a ue-Identity field.

As a sub-embodiment of this embodiment, the one field in the first message is an I-RNTI-Value field.

As a sub-embodiment of this embodiment, the one field in the first message is a paging ue-Identity field.

As a sub-embodiment of this embodiment, the one field in the first message is a fulll i-RNTI field.

As a sub-embodiment of this embodiment, the one domain in the first message is a TMGI domain.

As an embodiment, the phrase that the first identity is associated to the first node means: the first identity indicates the first node.

As a sub-embodiment of this embodiment, the first identification is a non-negative integer.

As a sub-embodiment of this embodiment, the first identification is a bit string.

As a sub-embodiment of this embodiment, the first identity is a fuse I-RNTI, which is set to I-RNTI-Value, which is a BIT STRING (BIT STRING).

As a sub-embodiment of this embodiment, the length of the one bit string is a positive integer number of bits.

As a sub-embodiment of this embodiment, the length of the one bit string is 48 bits.

As a sub-embodiment of this embodiment, the first identity is an I-RNTI-Value.

As a sub-embodiment of this embodiment, the I-RNTI-Value field is set to the first identity.

As a sub-embodiment of this embodiment, the first identity matches a fulll i-RNTI of the first node.

As a sub-embodiment of this embodiment, the first identity and the fulll i-RNTI of the first node are equal.

As a sub-embodiment of this embodiment, the first message includes a pagerecord list field, where the pagerecord list includes at least one pagerecord field, one pagerecord field of the at least one pagerecord field includes a ue-Identity field, the ue-Identity field includes a pageue-Identity field, the pageue-Identity field includes a fullI-RNTI field, and the fullI-RNTI field includes an I-RNTI-Value field, where the I-RNTI-Value field indicates the first identifier.

As an embodiment, the phrase that the first identity is associated to the first node means: the first identity is one TMGI (Temporary Mobile Group Identity) and the first node has been involved in (has joined) an MBS session indicated by the one TMGI.

As a sub-embodiment of this embodiment, one TMGI is used to indicate the multicast MRB associated MBS session (session).

As a sub-embodiment of this embodiment, the first message includes a paginggroupvist-r 17 field, and the paginggroupvist-r 17 field includes at least one TMGI field, and one TMGI field of the at least one TMGI field indicates the first identifier.

As a sub-embodiment of this embodiment, the one of the at least one TMGI domain is set to the first identity.

As a sub-embodiment of this embodiment, the at least one TMGI domain includes a PLMN index (PLMN-Id-r 17) and a service index (serviceId-r 17).

As an embodiment, if the first identity indicates the first node, at least one of SRB2 or DRB is included in the first set of radio bearers, and multicast MRB is not included in the first set of radio bearers.

As an embodiment, if the first identity indicates a TMGI, the first radio bearer set includes a multicast MRB, and the first radio bearer set does not include either SRB2 or DRB.

As an embodiment, if the first identity indicates a TMGI, at least a multicast MRB is included in the first set of radio bearers, and no DRB is included in the first set of radio bearers.

For one embodiment, the phrase received as a response to the first message includes: after the first message is received.

As an embodiment, the first message triggers the second message.

As an embodiment, the second message is an RRC message.

As an embodiment, the second message comprises at least an RRC message.

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

As an embodiment, the second message comprises at least one RRC domain.

As an embodiment, the second message is transmitted over CCCH (Common Control Channel ) and the RRC connection resume request message is an RRCResumeRequest message.

As an embodiment, the second message is transmitted over CCCH1 (Common Control Channel, common control channel 1), and the RRC connection resume request message is an RRCResumeRequest1 message.

As an embodiment, the second message is transmitted over SRB0 (Signalling Radio Bearer, signaling radio bearer 0).

As an embodiment, the second message includes at least the RRC connection resume request message.

As an embodiment, the second message is the RRC connection resume request message.

As an embodiment, the act of sending the second message includes: the second message is handed over to a lower layer comprising at least one of a PDCP (Packet Data Convergence Protocol ) layer or RLC (Radio Link Control, radio link layer control protocol) layer or MAC (Medium Access Control ) layer or PHY (Physical, physical layer) layer.

As an embodiment, the second message corresponds to a first SDU (Service data unit ), which is a CCCH SDU.

As a sub-embodiment of this embodiment, the second message is included in the first SDU.

As a sub-embodiment of this embodiment, the first SDU is a corresponding SDU after the second message is delivered to a protocol layer below the RRC layer.

As a sub-embodiment of this embodiment, LCID in the MAC sub-header corresponding to the first SDU is set to 0; the second message is transmitted over the CCCH.

As a sub-embodiment of this embodiment, LCID in the MAC sub-header corresponding to the first SDU is set to 52; the second message is transmitted over CCCH 1.

For one embodiment, the phrase accompanying the second message includes: in relation to the time at which the second message is sent.

For one embodiment, the phrase accompanying the second message includes: once the second message is sent.

For one embodiment, the phrase accompanying the second message includes: when the second message is sent.

For one embodiment, the phrase accompanying the second message includes: when the second message is sent at the MAC layer.

For one embodiment, the phrase accompanying the second message includes: when the first SDU is transmitted.

For one embodiment, the phrase accompanying the second message includes: when a MAC PDU including the first SDU is transmitted.

For one embodiment, the phrase accompanying the second message includes: at least until an RRC response to the second message is received.

For one embodiment, the phrase accompanying the second message includes: after the second message is sent, and before an RRC response to the second message is received.

For one embodiment, the phrase accompanying the second message includes: before the second message is sent.

For one embodiment, the phrase accompanying the second message includes: the second message is submitted to a protocol layer below the RRC layer.

For one embodiment, the phrase accompanying the second message includes: at least after the first message is received.

For one embodiment, the phrase accompanying the second message includes: after the first message is received and before the second message is sent.

As one embodiment, the act of setting the first domain in the second message and determining whether to resume each radio bearer in the first set of radio bearers based on at least whether the first message indicates that the first node is in the RRC inactive state comprises: setting the first domain in the second message according to at least whether the first message indicates that the first node is performing data transmission in the RRC inactive state, and determining whether to recover each radio bearer in the first set of radio bearers according to at least whether the first message indicates that the first node is performing data transmission in the RRC inactive state.

As an embodiment, along with the second message, whether to resume each radio bearer in the first set of radio bearers is related to at least whether the first message indicates that the first node is in the RRC inactive state for data transmission.

As an embodiment, accompanying the second message, the value of the first field in the second message relates to at least whether the first message indicates that the first node is in the RRC inactive state for data transmission.

As an embodiment, the behavior setting the first field in the second message includes: setting a value of a first field in the second message.

As an embodiment, the target domain in the first message is used to determine whether the first message indicates that the first node is in the RRC inactive state for data transmission.

As an embodiment, whether the first message includes the target domain is used to determine whether the first message indicates that the first node is transmitting data in the RRC inactive state.

As a sub-embodiment of this embodiment, if the target domain is included in the first message, the first message instructs the first node to perform data transmission in the RRC inactive state; and if the first message does not include the target domain, the first message does not indicate the first node to perform data transmission in the RRC inactive state.

As a sub-embodiment of this embodiment, if the target domain is present in the first message, the first message instructs the first node to perform data transmission in the RRC inactive state; and if the target domain does not exist in the first message, the first message does not indicate the first node to perform data transmission in the RRC inactive state.

As an embodiment, the first message includes a target domain, and whether the target domain in the first message is set to a target value is used to determine whether the first message indicates that the first node performs data transmission in the RRC inactive state.

As a sub-embodiment of this embodiment, if the target domain in the first message is set to the target value, the first message instructs the first node to perform data transmission in the RRC inactive state; if the target domain in the first message is set to any value other than the target value, the first message does not instruct the first node to perform data transmission in the RRC inactive state.

As a sub-embodiment of this embodiment, the target value is wire.

As a sub-embodiment of this embodiment, the target value is one of a set of candidate values, any one of the set of candidate values being used to indicate that data is received in the RRC inactive state.

As a sub-embodiment of this embodiment, only one candidate value is included in the set of candidate values.

As a sub-embodiment of this embodiment, the set of candidate values comprises at least 2 candidate values.

As a sub-embodiment of this embodiment, one candidate in the set of candidates is indicative of MT-SDT.

As a sub-embodiment of this embodiment, one candidate of the set of candidates indicates that a multicast MBS is received in the RRC inactive state.

As an embodiment, whether the first message indicates that the first set of radio bearers is used to determine whether the first message indicates that the first node is in the RRC inactive state for data transmission.

As a sub-embodiment of this embodiment, if the first message indicates the first set of radio bearers, the first message indicates that the first node is transmitting data in the RRC inactive state; if the first message does not indicate the first set of radio bearers, the first message does not indicate the first node to perform data transmission in the RRC inactive state.

As a sub-embodiment of this embodiment, if the first message indicates at least one radio bearer, the first message indicates that the first node is transmitting data in the RRC inactive state; if the first message is not displayed to indicate any radio bearer, the first message is not displayed to indicate the first node to perform data transmission in the RRC inactive state.

As a sub-embodiment of this embodiment, if the first message indicates an identification of at least one radio bearer, the first message indicates that the first node is performing data transmission in the RRC inactive state, and the first set of radio bearers includes the at least one radio bearer; and if the first message does not indicate the identification of any wireless bearer, the first message does not indicate the first node to perform data transmission in the RRC inactive state.

As an embodiment, the data transmission in the RRC inactive state means: transmitting data over at least one radio bearer in the first set of radio bearers in the RRC inactive state.

As an embodiment, the data transmission in the RRC inactive state means: unicast (unicasting) data is transmitted in the RRC inactive state.

As a sub-embodiment of this embodiment, if the first identifier in the first message indicates the first node, performing data transmission in the RRC inactive state means: unicast (unicasting) data is transmitted in the RRC inactive state.

As a sub-embodiment of this embodiment, the unicast data comprises user plane data.

As a sub-embodiment of this embodiment, the unicast data comprises control plane signaling.

As a sub-embodiment of this embodiment, said transmitting unicast data in said RRC inactive state comprises: data is transmitted over at least one of SRB2 or at least one DRB in the RRC inactive state.

As a sub-embodiment of this embodiment, said transmitting unicast data in said RRC inactive state comprises: and transmitting data through at least one DRB in the RRC inactive state.

As a sub-embodiment of this embodiment, said transmitting unicast data in said RRC inactive state comprises: unicast data is received in the RRC inactive state.

As a sub-embodiment of this embodiment, said transmitting unicast data in said RRC inactive state comprises: MT-SDT.

As a sub-embodiment of this embodiment, the first set of radio bearers includes all DRBs of the first node.

As a sub-embodiment of this embodiment, the first set of radio bearers includes SRB2 of the first node and all DRBs.

As a sub-embodiment of this embodiment, the first set of radio bearers consists of all DRBs of the first node.

As a sub-embodiment of this embodiment, the first set of radio bearers consists of SRB2 of the first node and all DRBs.

As a sub-embodiment of this embodiment, the first set of radio bearers includes at least one radio bearer of all DRBs of the first node.

As a sub-embodiment of this embodiment, the first set of radio bearers includes SRB2 of the first node and at least one radio bearer of all DRBs.

As an embodiment, the data transmission in the RRC inactive state means: and receiving the multicast MBS in the RRC inactive state.

As a sub-embodiment of this embodiment, if the first identity is one TMGI and the first node has engaged in an MBS session indicated by the one TMGI, transmitting data in the RRC inactive state means: and receiving the multicast MBS in the RRC inactive state.

As a sub-embodiment of this embodiment, said receiving the multicast MBS in said RRC inactive state comprises: data is received over at least one of SRB2 or at least one multicast MRB in the RRC inactive state.

As a sub-embodiment of this embodiment, said receiving the multicast MBS in said RRC inactive state comprises: data is received over at least one multicast MRB in the RRC inactive state.

As a sub-embodiment of this embodiment, the first set of radio bearers includes all MRBs of the first node.

As a sub-embodiment of this embodiment, the first set of radio bearers includes SRB2 of the first node and all MRBs.

As a sub-embodiment of this embodiment, the first set of radio bearers consists of all MRBs of the first node.

As a sub-embodiment of this embodiment, the first set of radio bearers consists of SRB2 of the first node and all MRBs.

As a sub-embodiment of this embodiment, the first set of radio bearers includes at least one radio bearer of all MRBs of the first node.

As a sub-embodiment of this embodiment, the first set of radio bearers includes SRB2 of the first node and at least one radio bearer of all MRBs.

As an embodiment, the first domain is a domain in the second message.

As an embodiment, the first domain is a resumecase domain.

As one embodiment, the name of the first domain includes resume and Cause.

As an embodiment, SRB1 is restored before the second message is delivered to a lower layer.

As an embodiment, the PDCP entity of SRB1 is rebuilt before the second message is delivered to a lower layer.

As an embodiment, any value of the first candidate set of values is used to determine that the first node enters an RRC CONNECTED (rrc_connected) state for data transmission.

As an embodiment, the first field in the second message is set to any value in the first candidate set of values to indicate that the second message is triggered by downlink data.

As an embodiment, the first field in the second message is set to any value in the first candidate set of values to indicate that the second message is triggered by a paging message.

As an embodiment, one value of the first candidate set of values is mps-priorityiaccess.

As one embodiment, one value in the first candidate set of values is mcs-priorityiaccess.

As an embodiment, one value of the first candidate set of values is highpriorityiaccess.

As an embodiment, one value of the first candidate set of values is mt-Access.

As an embodiment, the first candidate value set includes at least mps-PriorityAccess, mcs-PriorityAccess, highPriorityAccess, mt-Access.

As an embodiment, the second set of candidate values is the second set of candidate values.

As a sub-embodiment of this embodiment, any value in the first candidate set of values is the same as one value in the second candidate set of values, and any value in the second candidate set of values is the same as one value in the first candidate set of values.

As one embodiment, the first set of candidate values is different from the second set of candidate values.

As a sub-embodiment of this embodiment, only one candidate value is included in the second set of candidate values.

As a sub-embodiment of this embodiment, the second set of candidate values comprises at least 2 candidate values.

As a sub-embodiment of this embodiment, any value in the first candidate set of values is different from any value in the second candidate set of values.

As a sub-embodiment of this embodiment, any value in the second candidate set of values is not any of Emergency or highPrioritityAccess or mt-Access or mo-Signalling or mo-Data or mo-Voiceall or mo-video Call or mo-SMS or rn-Update or mps-PrioritityAccess or mcs-PrioritityAccess.

As a sub-embodiment of this embodiment, any value of the second set of candidate values is used to indicate that the second message is triggered by the RRC inactive state receiving downlink data.

As a sub-embodiment of this embodiment, any value of the second candidate set of values is used to indicate that the second message is triggered by data transmission by the RRC inactive state.

As a sub-embodiment of this embodiment, any value of the second set of candidate values is used to indicate that the second message is triggered by the target field in the first message.

As a sub-embodiment of this embodiment, any value of the second candidate set of values is used to determine that the first node remains in the RRC inactive state for data transmission.

As a sub-embodiment of this embodiment, any value in the second candidate set of values indicates data transmission in the RRC inactive state.

As a sub-embodiment of this embodiment, one value of the second set of candidate values indicates transmission of unicast data in the RRC inactive state.

As a sub-embodiment of this embodiment, one value of the second candidate set of values is mt-SDT.

As a sub-embodiment of this embodiment, the name of a value in the second candidate value set includes at least one of mt or SDT or-r 18.

As a sub-embodiment of this embodiment, one value of the second candidate set of values indicates that a multicast MBS is received in the RRC inactive state.

As a sub-embodiment of this embodiment, one value of the second candidate value set is at least one of mt or MBS or I or Inactive.

As an embodiment, if the first message does not indicate that the first node performs data transmission in the RRC inactive state, the first value is determined according to an Access Identity (Access Identity) of the first node configured by a higher layer.

As an embodiment, the act of determining the first value according to an access identity of the first node configured by a higher layer comprises: the first field in the second message is set to the first value according to an access identity of the first node configured by a higher layer.

As an embodiment, the act of determining the first value according to an access identity of the first node configured by a higher layer comprises: if the access identifier of the first node configured by a higher layer is equal to 1, the first value is mps-priorityiaccess; if the access identifier of the first node configured by a higher layer is equal to 2, the first value is mcs-priority access; if the access identifier of the first node configured by a higher layer is not less than 11 and not more than 15, the first value is highpriorityiccess; if the first node is not configured by a higher layer to Access the identification, the first value is mt-Access.

As an embodiment, if the first message indicates that the first node is transmitting data in the RRC inactive state, the second value is not determined according to an access identifier of the first node configured by a higher layer.

As an embodiment, if the first message indicates that the first node is transmitting data in the RRC inactive state, the access identity of the first node configured by higher layers is not used to determine the second value.

As an embodiment, if the first message indicates that the first node is transmitting data in the RRC inactive state, whether the first node is configured with an access identity by a higher layer is not used to determine the second value.

As an embodiment, if the first message indicates that the first node is transmitting data in the RRC inactive state, the second value is independent of an access identity of the first node configured by higher layers.

As an embodiment, if the first message indicates that the first node performs data transmission in the RRC inactive state, determining the second value according to an access identifier configured by a higher layer of the first node; the second value is the first value; the second set of candidate values is the second set of candidate values.

As an embodiment, SRB0 is not included in the first set of radio bearers.

As an embodiment, SRB1 (Signalling Radio Bearer 1, signaling radio bearer 1) is not included in the first set of radio bearers.

As an embodiment, SRB3 (Signalling Radio Bearer 3, signaling radio bearer 3) is not included in the first set of radio bearers.

As an embodiment, SRB0 is not included in the first set of radio bearers and SRB1 is not included in the first set of radio bearers.

As an embodiment, SRB0 is not included in the first set of radio bearers and SRB1 is not included in the first set of radio bearers and SRB3 is not included in the first set of radio bearers.

As one embodiment, each radio bearer in the first set of radio bearers is not SRB0 and each radio bearer in the first set of radio bearers is not SRB1.

As one embodiment, each radio bearer in the first set of radio bearers is not SRB0 and each radio bearer in the first set of radio bearers is not SRB1 and each radio bearer in the first set of radio bearers is not SRB3.

As an embodiment, the first radio bearer set does not include both multicast MRB and DRB.

As an embodiment, the first radio bearer set can include both multicast MRB and DRB.

As an embodiment, the first Radio Bearer set includes at least one Radio Bearer (RB).

As an embodiment, one of the at least one radio bearer included in the first set of radio bearers is at least one of MRB or DRB or SRB2.

As an embodiment, the first radio bearer set includes only SRB2.

As an embodiment, the first set of radio bearers includes only at least one DRB.

As an embodiment, the first set of radio bearers includes only at least one multicast MRB.

As an embodiment, the first radio bearer set includes only SRB2 and at least one DRB.

As an embodiment, the first radio bearer set includes only SRB2 and at least one multicast MRB.

As an embodiment, the first set of radio bearers includes all DRBs of the first node.

As an embodiment, the first set of radio bearers comprises a subset of all DRBs of the first node.

As an embodiment, at least one DRB of all DRBs of the first node is not included in the first set of radio bearers.

As an embodiment, the definition of SBR2 refers to 3gpp TS 38.331.

As an embodiment, the definition of the DRB refers to 3gpp TS 38.331.

As an embodiment, the DRB is a radio bearer identified by a DRB-Identity.

As one embodiment, the multicast MRB is a radio bearer identified by MRB-Identity.

As one embodiment, the multicast MRB is a radio bearer identified by MRB-Identity-r 17.

As one embodiment, the multicast MRB is a radio bearer identified by MRB-Identity-r 18.

As one embodiment, the multicast MRB is not a broadcast (broadcast) MRB.

As an embodiment, the definition of the multicast MRB refers to 3gpp TS 38.331.

Example 2

Embodiment 2 illustrates a schematic diagram of a network architecture according to one embodiment of the application, as shown in fig. 2. Fig. 2 illustrates a network architecture 200 of a 5G NR (New Radio)/LTE (Long-Term Evolution)/LTE-a (Long-Term Evolution Advanced, enhanced Long-Term Evolution) system. The 5G NR/LTE-a network architecture 200 may be referred to as 5GS (5G System)/EPS (Evolved Packet System ) 200, or some other suitable terminology. The 5GS/EPS 200 includes at least one of a UE (User Equipment) 201, a ran (radio access network) 202,5GC (5G Core Network)/EPC (Evolved Packet Core, evolved packet core) 210, an hss (Home Subscriber Server )/UDM (Unified Data Management, unified data management) 220, and an internet service 230. The 5GS/EPS may interconnect with other access networks, but these entities/interfaces are not shown for simplicity. As shown, 5GS/EPS provides packet switched services, however, those skilled in the art will readily appreciate that the various concepts presented throughout this disclosure may 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 towards UE 201. Node 203 may be connected to other nodes 204 via an Xn interface (e.g., backhaul)/X2 interface. Node 203 may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a Basic Service Set (BSS), an Extended Service Set (ESS), a TRP (transmit receive node), or some other suitable terminology. The node 203 provides the UE201 with an access point to the 5GC/EPC210. Examples of UE201 include a cellular telephone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a Personal Digital Assistant (PDA), a satellite radio, a non-terrestrial base station communication, a satellite mobile communication, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, an drone, an aircraft, a narrowband internet of things device, a machine-type communication device, a land-based vehicle, an automobile, a wearable device, or any other similar functional device. Those of skill in the art may also refer to the UE201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. The node 203 is connected to the 5GC/EPC210 through an S1/NG interface. The 5GC/EPC210 includes MME (Mobility Management Entity )/AMF (Authentication Management Field, authentication management domain)/SMF (Session Management Function ) 211, other MME/AMF/SMF214, S-GW (Service Gateway)/UPF (User Plane Function ) 212, and P-GW (Packet Date Network Gateway, packet data network Gateway)/UPF 213. The MME/AMF/SMF211 is a control node that handles signaling between the UE201 and the 5GC/EPC210. In general, the MME/AMF/SMF211 provides bearer and connection management. All user IP (Internet Protocal, internet protocol) packets are transported through the S-GW/UPF212, which S-GW/UPF212 itself is connected to the P-GW/UPF213. The P-GW provides UE IP address assignment as well as other functions. The P-GW/UPF213 is connected to the internet service 230. Internet services 230 include operator-corresponding internet protocol services, which may include, in particular, the internet, intranets, IMS (IP Multimedia Subsystem ) and packet-switched streaming services.

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

As an embodiment, the UE201 is a User Equipment (UE).

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

As an embodiment, the node 203 is a base station device (BS).

As an example, the node 203 is a base transceiver station (Base Transceiver Station, BTS).

As an embodiment, the node 203 is a node B (NodeB, NB).

As an embodiment, the node 203 is a gNB.

As an embodiment, the node 203 is an eNB.

As an embodiment, the node 203 is a ng-eNB.

As an embodiment, the node 203 is an en-gNB.

As an embodiment, the node 203 is a CU (Centralized Unit).

As an embodiment, the node 203 is a DU (Distributed Unit).

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

As an embodiment, the node 203 is a relay.

As an embodiment, the node 203 is a Gateway (Gateway).

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

As an example, the node 204 is a BS.

For one embodiment, the node 204 is a BTS.

As an example, the node 204 is an NB.

As an example, the node 204 is a gNB.

As an embodiment, the node 204 is an eNB.

As an example, the node 204 is a ng-eNB.

As one example, the node 204 is an en-gNB.

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

As an example, the node 204 is a relay.

As an embodiment, the node 204 is a Gateway (Gateway).

As an embodiment, the node 204 is a CU.

As an example, the node 204 is a DU.

As an embodiment, the node 203 and the node 204 are connected through an ideal backhaul connection.

As an embodiment, the node 203 and the node 204 are connected through a non-ideal backhaul connection.

As an example, the node 203 and the node 204 simultaneously provide radio resources for the UE 201.

As an example, the node 203 and the node 204 do not provide radio resources to the UE201 at the same time.

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

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

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

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

As an embodiment, the user equipment supports transmissions in a large latency difference network.

As an embodiment, the user equipment supports Dual Connection (DC) transmission.

As an embodiment, the user device comprises an aircraft.

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

As an embodiment, the user equipment comprises a watercraft.

As an embodiment, the user equipment includes an internet of things terminal.

As an embodiment, the user equipment includes a terminal of an industrial internet of things.

As an embodiment, the user equipment comprises a device supporting low latency high reliability transmissions.

As an embodiment, the user equipment comprises a test equipment.

As an embodiment, the user equipment comprises a signaling tester.

As an embodiment, the base station device supports transmissions on a non-terrestrial network.

As one embodiment, the base station apparatus supports transmissions in a large delay network.

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

As an embodiment, the base station device comprises a macro Cellular (Marco Cellular) base station.

As one embodiment, the base station apparatus includes a Micro Cell (Micro Cell) base station.

As one embodiment, the base station apparatus includes a Pico Cell (Pico Cell) base station.

As an embodiment, the base station device comprises a home base station (Femtocell).

As an embodiment, the base station apparatus includes a base station apparatus supporting a large delay difference.

As an embodiment, the base station device comprises a flying platform device.

As an embodiment, the base station device comprises a satellite device.

As an embodiment, the base station device comprises a TRP (Transmitter Receiver Point, transmitting receiving node).

As an embodiment, the base station apparatus includes a CU (Centralized Unit).

As an embodiment, the base station apparatus includes a DU (Distributed Unit).

As an embodiment, the base station device comprises a test device.

As an embodiment, the base station device comprises a signaling tester.

As an embodiment, the base station apparatus comprises a IAB (Integrated Access and Backhaul) -node.

As an embodiment, the base station device comprises an IAB-donor.

As an embodiment, the base station device comprises an IAB-donor-CU.

As an embodiment, the base station device comprises an IAB-donor-DU.

As an embodiment, the base station device comprises an IAB-DU.

As an embodiment, the base station device comprises an IAB-MT.

As an embodiment, the relay comprises a relay.

As an embodiment, the relay comprises an L3 relay.

As one embodiment, the relay comprises an L2 relay.

As an embodiment, the relay comprises a router.

As an embodiment, the relay comprises a switch.

As an embodiment, the relay comprises a user equipment.

As an embodiment, the relay comprises a base station device.

Example 3

Embodiment 3 shows a schematic diagram of an embodiment of a radio protocol architecture of a user plane and a control plane according to the application, as shown in fig. 3. Fig. 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300, fig. 3 shows the radio protocol architecture for the control plane 300 with three layers: layer 1, layer 2 and layer 3. Layer 1 (L1 layer) is the lowest layer and implements various PHY (physical layer) signal processing functions. The L1 layer will be referred to herein as PHY301. Layer 2 (L2 layer) 305 is above PHY301 and includes a MAC (Medium Access Control ) sublayer 302, an RLC (Radio Link Control, radio link layer control protocol) sublayer 303, and a PDCP (Packet Data Convergence Protocol ) sublayer 304. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by ciphering the data packets and handover support. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out of order reception due to HARQ. The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating the various radio resources (e.g., resource blocks) in one cell. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control ) sublayer 306 in layer 3 (L3 layer) in the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring the lower layers using RRC signaling. The radio protocol architecture of the user plane 350 includes layer 1 (L1 layer) and layer 2 (L2 layer), in which user plane 350 the radio protocol architecture is substantially the same for the physical layer 351, PDCP sublayer 354 in the L2 layer 355, RLC sublayer 353 in the L2 layer 355 and MAC sublayer 352 in the L2 layer 355 as the corresponding layers and sublayers in the control plane 300, but PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead. Also included in the L2 layer 355 in the user plane 350 is an SDAP (Service Data Adaptation Protocol ) sublayer 356, the SDAP sublayer 356 being responsible for mapping between QoS flows and data radio bearers (DRBs, data Radio Bearer) to support diversity of traffic.

As an embodiment, the radio protocol architecture in fig. 3 is applicable to the first node in the present application.

As an embodiment, the radio protocol architecture in fig. 3 is applicable to the second node in the present application.

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

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

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

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

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

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

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

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

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

As an embodiment, the fourth message in the present application is generated in the RRC306.

As an embodiment, the fourth message in the present application is generated in the MAC302 or the MAC352.

As an embodiment, the fourth message in the present application is generated in the PHY301 or the PHY351.

As an embodiment, the first data packet in the present application is generated in the RRC306.

As an embodiment, the first data packet in the present application is generated in the MAC302 or the MAC352.

As an embodiment, the first data packet in the present application is generated in the PHY301 or the PHY351.

Example 4

Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to the application, as shown in fig. 4. Fig. 4 is a block diagram of a first communication device 450 and a second communication device 410 communicating with each other in an access network.

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

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

In the transmission from the second communication device 410 to the first communication device 450, upper layer data packets from the core network are provided to a controller/processor 475 at the second communication device 410. The controller/processor 475 implements the functionality of the L2 layer. In the transmission from the second communication device 410 to the first communication device 450, a controller/processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the first communication device 450 based on various priority metrics. The controller/processor 475 is also responsible for retransmission of lost packets and signaling to the first communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., physical layer). Transmit processor 416 performs coding and interleaving to facilitate Forward Error Correction (FEC) at the second communication device 410, as well as 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-quadrature amplitude modulation (M-QAM). The multi-antenna transmit processor 471 digitally space-precodes the coded and modulated symbols, including codebook-based precoding and non-codebook-based precoding, and beamforming processing, to generate one or more spatial streams. A transmit processor 416 then maps each spatial stream to a subcarrier, multiplexes with reference signals (e.g., pilots) in the time and/or frequency domain, and then uses an Inverse Fast Fourier Transform (IFFT) to generate a physical channel carrying the time domain multicarrier symbol stream. The multi-antenna transmit processor 471 then performs transmit analog precoding/beamforming operations on the time domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multicarrier symbol stream provided by the multiple antenna transmit processor 471 to a radio frequency stream and then provides it to a different antenna 420.

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

In the transmission from the first communication device 450 to the second communication device 410, a data source 467 is used at the first communication device 450 to provide upper layer data packets to a controller/processor 459. Data source 467 represents all protocol layers above the L2 layer. Similar to the transmit 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 allocations, implementing L2 layer functions for the user and control planes. The controller/processor 459 is also responsible for retransmission of lost packets and signaling to the second communication device 410. The transmit processor 468 performs modulation mapping, channel coding, and digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming, with the multi-antenna transmit processor 457 performing digital multi-antenna spatial precoding, after which the transmit processor 468 modulates the resulting spatial stream into a multi-carrier/single-carrier symbol stream, which is analog precoded/beamformed in the multi-antenna transmit processor 457 before being provided to the different antennas 452 via the transmitter 454. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a radio frequency symbol stream and provides it to an antenna 452.

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 to baseband signals, and provides the baseband signals to a multi-antenna receive processor 472 and a receive processor 470. The receive processor 470 and the multi-antenna receive processor 472 collectively implement the functions of the L1 layer. The controller/processor 475 implements L2 layer functions. The controller/processor 475 may be associated with a memory 476 that stores program codes and data. Memory 476 may be referred to as a computer-readable medium. In the transmission from the first communication device 450 to the second communication device 410, a controller/processor 475 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover upper layer data packets from the UE 450. Upper layer packets from the controller/processor 475 may be provided to the core network.

As an embodiment, the first communication device 450 includes: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code are configured to, with the at least one processor, the first communication device 450 at least: receiving a first message in an RRC inactive state, the first message including a first identity, the first identity being associated with the first node; transmitting a second message as a response to the first message being received, the second message including an RRC connection resume request message; setting a first domain in the second message according to at least whether the first message indicates that the first node performs data transmission in the RRC inactive state and determining whether to recover each radio bearer in a first set of radio bearers, the first domain being used to indicate a cause of an RRC connection recovery request; wherein the act of setting the first domain in the second message and determining whether to resume each radio bearer in the first set of radio bearers based on at least whether the first message indicates that the first node is in the RRC inactive state comprises: if the first message does not indicate that the first node is in the RRC inactive state for data transmission, setting the first field in the second message to a first value, and not recovering each radio bearer in the first set of radio bearers; if the first message indicates that the first node performs data transmission in the RRC inactive state, setting the first domain in the second message to a second value, and recovering each radio bearer in the first radio bearer set; the first radio bearer set includes at least one of SRB2 or DRB or multicast MRB; the first value is one of a first candidate value set, and the first candidate value set comprises at least one value; the second value is one of a second set of candidate values, the second set of candidate values including at least one value therein.

As an embodiment, the first communication device 450 includes: a memory storing a program of computer-readable instructions that, when executed by at least one processor, produce acts comprising: receiving a first message in an RRC inactive state, the first message including a first identity, the first identity being associated with the first node; transmitting a second message as a response to the first message being received, the second message including an RRC connection resume request message; setting a first domain in the second message according to at least whether the first message indicates that the first node performs data transmission in the RRC inactive state and determining whether to recover each radio bearer in a first set of radio bearers, the first domain being used to indicate a cause of an RRC connection recovery request; wherein the act of setting the first domain in the second message and determining whether to resume each radio bearer in the first set of radio bearers based on at least whether the first message indicates that the first node is in the RRC inactive state comprises: if the first message does not indicate that the first node is in the RRC inactive state for data transmission, setting the first field in the second message to a first value, and not recovering each radio bearer in the first set of radio bearers; if the first message indicates that the first node performs data transmission in the RRC inactive state, setting the first domain in the second message to a second value, and recovering each radio bearer in the first radio bearer set; the first radio bearer set includes at least one of SRB2 or DRB or multicast MRB; the first value is one of a first candidate value set, and the first candidate value set comprises at least one value; the second value is one of a second set of candidate values, the second set of candidate values including at least one value therein.

As one embodiment, the second communication device 410 includes: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code are configured for use with the at least one processor. The second communication device 410 at least: transmitting a first message, the first message including a first identification, the first identification being associated with a recipient of the first message; receiving a second message as a response to the first message being sent, the second message including an RRC connection resume request message; wherein the receiver of the first message receives the first message in an RRC inactive state; with the second message, at least whether the first message indicates that the recipient of the first message is in the RRC inactive state for data transmission is used by the recipient of the first message to set a first field in the second message and determine whether to recover each radio bearer in a first set of radio bearers, the first field being used to indicate a cause of an RRC connection recovery request; the phrase whether at least the first message indicates that the recipient of the first message is in the RRC inactive state for data transmission is used by the recipient of the first message to set a first domain in the second message and to determine whether to resume each radio bearer in a first set of radio bearers includes: the first message not indicating that the data transmission by the recipient of the first message in the RRC inactive state is used to determine to set the first field in the second message to a first value and not to recover each radio bearer in the first set of radio bearers; the first message indicating that data transmission by a receiver of the first message in the RRC inactive state is used to determine to set the first field in the second message to a second value and to resume each radio bearer in the first set of radio bearers; the first radio bearer set includes at least one of SRB2 or DRB or multicast MRB; the first value is one of a first candidate value set, and the first candidate value set comprises at least one value; the second value is one of a second set of candidate values, the second set of candidate values including at least one value therein.

As one embodiment, the second communication device 410 includes: a memory storing a program of computer-readable instructions that, when executed by at least one processor, produce acts comprising: transmitting a first message, the first message including a first identification, the first identification being associated with a recipient of the first message; receiving a second message as a response to the first message being sent, the second message including an RRC connection resume request message; wherein the receiver of the first message receives the first message in an RRC inactive state; with the second message, at least whether the first message indicates that the recipient of the first message is in the RRC inactive state for data transmission is used by the recipient of the first message to set a first field in the second message and determine whether to recover each radio bearer in a first set of radio bearers, the first field being used to indicate a cause of an RRC connection recovery request; the phrase whether at least the first message indicates that the recipient of the first message is in the RRC inactive state for data transmission is used by the recipient of the first message to set a first domain in the second message and to determine whether to resume each radio bearer in a first set of radio bearers includes: the first message not indicating that the data transmission by the recipient of the first message in the RRC inactive state is used to determine to set the first field in the second message to a first value and not to recover each radio bearer in the first set of radio bearers; the first message indicating that data transmission by a receiver of the first message in the RRC inactive state is used to determine to set the first field in the second message to a second value and to resume each radio bearer in the first set of radio bearers; the first radio bearer set includes at least one of SRB2 or DRB or multicast MRB; the first value is one of a first candidate value set, and the first candidate value set comprises at least one value; the second value is one of a second set of candidate values, the second set of candidate values including at least one value therein.

As an example, the antenna 452, the receiver 454, the receive processor 456, the controller/processor 459 is used to receive a first message.

As one example, the antenna 420, the transmitter 418, the transmit processor 416, and at least one of the controller/processors 475 are used to transmit a first message.

As one implementation, the antenna 452, the transmitter 454, the transmit processor 468, and the controller/processor 459 are used to send a second message.

As an example, at least one of the antenna 420, the receiver 418, the receive processor 470, and the controller/processor 475 is used to receive a second message.

As an example, the antenna 452, the receiver 454, the receive processor 456, the controller/processor 459 is used to receive a third message.

As an example, the antenna 420, the transmitter 418, the transmit processor 416, and at least one of the controller/processors 475 are used to transmit a third message.

As an example, the antenna 452, the receiver 454, the receive processor 456, the controller/processor 459 is used to listen for or receive fourth messages.

As an example, at least one of the antenna 420, the transmitter 418, the transmit processor 416, and the controller/processor 475 is used to transmit a fourth message.

As an example, the antenna 452, the receiver 454, the receive processor 456, the controller/processor 459 is used to receive the first data block.

As an example, at least one of the antenna 420, the transmitter 418, the transmit processor 416, and the controller/processor 475 is used to transmit the first data block.

As an embodiment, the first communication device 450 corresponds to a first node in the present application.

As an embodiment, the second communication device 410 corresponds to a second node in the present application.

As an embodiment, the first communication device 450 is a user device.

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

As an embodiment, the first communication device 450 is a NTN-enabled user device.

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

For one embodiment, the first communication device 450 is provided with positioning capabilities.

For one embodiment, the first communication device 450 is not capable.

As an embodiment, the first communication device 450 is a TN enabled user device.

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

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

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

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

As an example, the second communication device 410 is a flying platform device.

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

Example 5

Embodiment 5 illustrates a wireless signal transmission flow diagram according to one embodiment of the application, as shown in fig. 5. It is specifically explained that the order in this example does not limit the order of signal transmission and the order of implementation in the present application.

For the followingFirst node U01In step S5101, a third message is received; in step S5102, a first message is received in an RRC inactive state, the first message including a first identity, the first identity being associated to the first node U01; in step S5103, as a response to the first message being received, determining whether the first message indicates that the first node U01 is performing data transmission in the RRC inactive state, if the first message does not indicate that the first node U01 is performing data transmission in the RRC inactive state, performing step S5104 (a), if the first message indicates that the first node U01 is performing data transmission in the RRC inactive state, performing step S5104 (b) and performing step S5105; in step S5104 (a), the first field in the second message is set to a first value; in step S5104 (b), the first field in the second message is set to a second value; in step S5105, each radio bearer in the first set of radio bearers is restored; in step S5106, as a response to the first message being received, a second message including an RRC connection restoration request message is transmitted.

For the followingSecond node N02In the step ofIn S5201, the first message is sent.

For the followingThird node N03In step S5301, the third message is transmitted.

For the followingFourth node N04In step S5401, the second message is received.

In embodiment 5, the first domain is used to indicate the cause of the RRC connection resume request; the third message is used to determine to enter or remain in the RRC inactive state; the first radio bearer set includes at least one of SRB2 or DRB or multicast MRB; the first value is one of a first candidate value set, and the first candidate value set comprises at least one value; the second value is one of a second set of candidate values, the second set of candidate values including at least one value therein.

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

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

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

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

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

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

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

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

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

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

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

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

Typically, the first node U01 is a user equipment, the second node N02 is a gNB, the third node N03 is a gNB, and the fourth node N04 is a gNB.

As an embodiment, the second node N02, the third node N03, and the fourth node N04 are all the same.

As an embodiment, at least two nodes among the second node N02, the third node N03, and the fourth node N04 are different.

As an embodiment, the second node N02 and the third node N03 are the same.

As an embodiment, the second node N02 and the third node N03 are different.

As an embodiment, the second node N02 and the fourth node N04 are the same.

As an embodiment, the second node N02 and the fourth node N04 are different.

As an embodiment, the first message indicates the first set of radio bearers, or the target domain is used to determine the first set of radio bearers, or the third message indicates the first set of radio bearers, or the first identity is used to determine the first set of radio bearers.

As an embodiment, the first set of radio bearers includes all DRBs configured by the first node U01.

As one embodiment, the first message indicates the first set of radio bearers.

As a sub-embodiment of this embodiment, the radio bearer indicated by the first message is one radio bearer of the first set of radio bearers.

As an embodiment, if the first identity is one TMGI and the first node U01 has engaged in an MBS session indicated by the one TMGI, the first identity is used to determine the first set of radio bearers.

As a sub-embodiment of this embodiment, the first identification being used to determine the first set of radio bearers refers to: the first identity is used to indicate one radio bearer in the first set of radio bearers.

As a sub-embodiment of this embodiment, the first message comprises at least one TMGI and the first node U01 has engaged in an MBS session indicated by each of the at least one TMGI, the first set of radio bearers comprising all multicast MRBs associated with the at least one TMGI; the first identity is one of the at least one TMGI.

As a sub-embodiment of this embodiment, the first set of radio bearers consists of all multicast MRBs associated with the at least one TMGI.

As a sub-embodiment of this embodiment, one TMGI and one multicast MRB are indicated by the same MRB-ToAddMod to be used to determine that the one TMGI is associated to the one multicast MRB.

As a sub-embodiment of this embodiment, the association of one TMGI to one multicast MRB means that the one multicast MRB is configured for the one TMGI.

As one embodiment, the target domain is used to determine the first set of radio bearers.

As a sub-embodiment of this embodiment, if the target field in the first message indicates that the first node U01 is transmitting data in the RRC inactive state, the first set of radio bearers includes all DRBs of the first node U01.

As a sub-embodiment of this embodiment, if the target field in the first message indicates that the first node U01 is transmitting data in the RRC inactive state, the first set of radio bearers includes SRB2 of the first node U01.

As a sub-embodiment of this embodiment, the first set of radio bearers includes all multicast MRBs of the first node U01 if the target field in the first message indicates that the first node U01 is transmitting data in the RRC inactive state.

As an embodiment, the first set of radio bearers is not indicated by the third message.

As an embodiment, the third message does not include an identification of any radio bearer in the first set of radio bearers.

As an embodiment, the third message does not include an identification of at least one radio bearer in the first set of radio bearers.

As one embodiment, the third message indicates the first set of radio bearers.

As an embodiment, if the target domain in the first message indicates that the first node U01 is transmitting data in the RRC inactive state, the third message indicates the first set of radio bearers.

As an embodiment, the third message indicates at least one radio bearer among all DRBs of the first node U01, and the first set of radio bearers consists of the at least one radio bearer.

As an embodiment, the third message indicates at least one radio bearer of SRB2 and all DRBs of the first node U01, and the first set of radio bearers consists of the at least one radio bearer.

As an embodiment, the third message indicates at least one radio bearer of all MRBs of the first node U01, the first set of radio bearers being comprised of the at least one radio bearer.

As an embodiment, the third message indicates at least one radio bearer of SRB2 and all MRBs of the first node U01, and the first set of radio bearers consists of the at least one radio bearer.

As an embodiment, the first node U01 determines the first set of radio bearers according to the third message.

As one embodiment, the third message is used to determine the first set of radio bearers.

As one embodiment, the third message indicates the first set of radio bearers.

As one embodiment, the third message explicitly indicates each radio bearer in the first set of radio bearers.

As an embodiment, the third message explicitly indicates one radio bearer of the first set of radio bearers.

As an embodiment, the third message implicitly indicates one radio bearer in the first set of radio bearers.

As an embodiment, the third message comprises a sdt-Config field, the sdt-Config field indicating the first set of radio bearers.

As an embodiment, the third message comprises a sdt-DRB-List, the sdt-DRB-List indicating all DRBs included in the first set of radio bearers.

As an embodiment, the third message comprises sdt-SRB2-Indication, the sdt-SRB2-Indication indicating all SRBs 2 comprised in the first set of radio bearers.

As an embodiment, the third message includes an identification of all radio bearers in the first set of radio bearers.

As an embodiment, the third message includes an identification of each radio bearer in the first set of radio bearers.

As one embodiment, the first message includes a first information block indicating each radio bearer in the first set of radio bearers; the first information block is associated to the first identity, which indicates the first node U01.

As a sub-embodiment of this embodiment, the first message includes a PagingRecord field, and the one PagingRecord field includes the first information block and the first identifier.

As one embodiment, the third message includes a first information block indicating each radio bearer in the first set of radio bearers.

As a sub-embodiment of this embodiment, the third message includes a supendconfig field, and the supendconfig field in the third message includes the first information block.

As an embodiment, the first information block includes at least one RRC domain.

As an embodiment, the first information block includes at least one RRC IE.

As an embodiment, the first information block comprises sdt-Config.

As an embodiment, the first information block is sdt-Config.

As an embodiment, the first information block comprises sdt-DRB-List.

As an embodiment, the first information block comprises sdt-SRB2-Indication.

As an embodiment, the first information block is sdt-DRB-List.

As an embodiment, the first information block is sdt-SRB2-Indication.

As an embodiment, the name of the first information block includes at least one of sdt or DRB or List or 1 or 2.

As an embodiment, the name of the first information block includes at least one of mbs or multicast or MRB or List or 1 or 2.

As an embodiment, the third message is received before the first message.

As an embodiment, the third message is received before the first message is received.

As an embodiment, the third message comprises an RRC message.

As an embodiment, the third message is an RRC message.

As an embodiment, the third message is received via SRB 1.

As an embodiment, the third message is transmitted on DCCH (Dedicated Control Channel, dedicated control signaling).

As an embodiment, the third message includes at least one RRC IE.

As an embodiment, the third message includes at least one RRC domain.

As an embodiment, the third message is an RRCRelease message.

As an embodiment, the third message includes a supendcon field.

As an embodiment, the third message comprises an RRC domain, which is used to determine to enter or remain in the RRC inactive state.

As an embodiment, the third message includes a susposcon field, which is used to determine to enter or remain in the RRC inactive state.

As an embodiment, the third message indicates entering or maintaining in the RRC inactive state.

As an embodiment, the third message indicates entering the RRC inactive state.

As an embodiment, the third message indicates to remain in the RRC inactive state.

As an embodiment, before the third message is received, if the third message is in an RRC CONNECTED (rrc_connected) state, the third message is used to determine to enter the RRC inactive state.

As an embodiment, before the third message is received, if the third message is in an RRC inactive state, the third message is used to determine to remain in the RRC inactive state.

As an embodiment, the RRC inactive state is entered as a response to the third message being received.

As an embodiment, the RRC inactive state is maintained as a response to the third message being received.

As an embodiment, the first node U01 is in the RRC inactive state in response to the third message being received.

As an embodiment, the first node U01 is always in the RRC inactive state during the time interval between when the third message is received and when the first message is received.

As an embodiment, the first node U01 does not send any one of the rrcruumerequest message or the rrcruumerequest 1 message during the time interval between the third message being received and the first message being received.

As an embodiment, all SRBs other than SRB0 are suspended, all DRBs are suspended, and all multicast MRBs are suspended in response to the third message being received.

As an embodiment, indicate PDCP suspend to lower layers of all DRBs is a response to the third message being received.

Example 6

Embodiment 6 illustrates a schematic diagram in which the second field in the second message is used to indicate data transmission in the RRC inactive state according to an embodiment of the present application, as shown in fig. 6.

In embodiment 6, if the first message indicates that the first node is transmitting data in the RRC inactive state, a second domain is used to indicate that the first node is transmitting data in the RRC inactive state, the second domain being associated with the second message; the first candidate set and the second candidate set are the same.

As one embodiment, a first message is received in an RRC inactive state, the first message including a first identification, the first identification being associated to the first node; transmitting a second message as a response to the first message being received, the second message including an RRC connection resume request message; setting the first field in the second message to a first value along with the second message, and determining whether to recover each radio bearer in a first set of radio bearers according to at least whether the first message indicates that the first node is in the RRC inactive state for data transmission, the first field being used to indicate a cause of an RRC connection recovery request; wherein the act of determining whether to recover each radio bearer in the first set of radio bearers based on at least whether the first message indicates that the first node is in the RRC inactive state for data transmission comprises: if the first message does not indicate that the first node performs data transmission in the RRC inactive state, not recovering each radio bearer in the first radio bearer set; restoring each radio bearer in the first radio bearer set if the first message indicates that the first node is transmitting data in the RRC inactive state; if the first message indicates that the first node is transmitting data in the RRC inactive state, a second domain is used to indicate that the first node is transmitting data in the RRC inactive state, the second domain being associated with the second message; the first radio bearer set includes at least one of SRB2 or DRB or multicast MRB; the first value is one of a first set of candidate values, the first set of candidate values including at least one value therein.

As an embodiment, the phrase second domain is used to indicate that data transmission in the RRC inactive state includes: and if the second domain exists, the second domain is used for indicating data transmission in the RRC inactive state.

As an embodiment, the phrase second domain is used to indicate that data transmission in the RRC inactive state includes: the value of the second field is set to a given value, which is used to indicate data transmission in the RRC inactive state.

As one embodiment, the phrase that the second domain is associated to the second message includes: the second field indicates the second message.

As one embodiment, the phrase that the second domain is associated to the second message includes: the second domain is set for the second message.

As one embodiment, the phrase that the second domain is associated to the second message includes: the second message includes the second field.

As a sub-embodiment of this embodiment, the second domain is an RRC domain.

As a sub-embodiment of this embodiment, the second field is a field in the second message.

As a sub-embodiment of this embodiment, the second field is a spark field in the second message.

As a sub-embodiment of this embodiment, the second domain is a domain subsequent to the resumecase domain in the second message.

As a sub-embodiment of this embodiment, the second field is a bit in the second message.

As a sub-embodiment of this embodiment, the second field is the last bit in the second message.

As one embodiment, the phrase that the second domain is associated to the second message includes: the second message corresponds to a first SDU, and the first SDU is a CCCH SDU; and the MAC sub-header corresponding to the first SDU comprises the second domain.

As a sub-embodiment of this embodiment, the second domain is a MAC domain.

As a sub-embodiment of this embodiment, the second domain is a domain in a MAC sub-header.

As a sub-embodiment of this embodiment, the MAC sub-header corresponding to the first SDU includes an LCID field, where the LCID field is set to 0 or the LCID field is set to 52; the second domain is not the LCID domain.

As a sub-embodiment of this embodiment, the second domain is an LCID domain, which is not set to either of 0 or 52.

As a sub-embodiment of this embodiment, the second domain is an LCID domain set to an integer of not less than 37 and not more than 43.

As a sub-embodiment of this embodiment, the second domain is an ellid domain set to an integer not less than 0 and not more than 227.

As one embodiment, the phrase that the second domain is associated to the second message includes: the second message corresponds to a first SDU, and the first SDU is a CCCH SDU; the second domain is one domain in a first MAC sub-PDU, and the first MAC sub-PDU and the MAC sub-PDU corresponding to the first SDU belong to the same MAC PDU.

As a sub-embodiment of this embodiment, the first MAC sub-PDU includes only MAC sub-headers, and the second field is one of the MAC sub-headers in the first MAC sub-PDU.

As an subsidiary embodiment of this sub-embodiment, said second domain is an LCID domain.

As an additional embodiment of this sub-embodiment, the second domain is an eclpid domain.

As a sub-embodiment of this embodiment, the first MAC sub-PDU includes a MAC sub-header and a MAC CE, and the second field is one of the MAC CEs in the first MAC sub-PDU.

As one embodiment, the first node receives a first message in an RRC inactive state, the first message including a first identification, the first identification being associated with the first node, the first message not indicating that the first node is transmitting data in the RRC inactive state; transmitting a second message as a response to the first message being received, the second message including an RRC connection resume request message; setting a first field in the second message to a first value with the second message and not recovering each radio bearer in the first set of radio bearers; the first domain is used to indicate a cause of an RRC connection resume request; the first value is one of a first candidate value set, and the first candidate value set comprises at least one value; at least one of SRB2 or DRB or multicast MRB is included in the first set of radio bearers.

As one embodiment, the first node receives a first message in an RRC inactive state, the first message including a first identification, the first identification being associated with the first node, the first message indicating that the first node is transmitting data in the RRC inactive state; transmitting a second message as a response to the first message being received, the second message including an RRC connection resume request message; setting a first field in the second message to a second value with the second message and recovering each radio bearer in the first set of radio bearers; the first domain is used to indicate a cause of an RRC connection resume request; the second value is one of a second set of candidate values, the second set of candidate values including at least one value therein; the first radio bearer set includes at least one of SRB2 or DRB or multicast MRB; a second domain is used to indicate data transmission in the RRC inactive state, the second domain being associated with the second message; the first candidate set and the second candidate set are the same.

As one embodiment, the first node receives a first message in an RRC inactive state, the first message including a first identification, the first identification being associated with the first node, the first message indicating that the first node is transmitting data in the RRC inactive state; transmitting a second message as a response to the first message being received, the second message including an RRC connection resume request message; setting a first field in the second message to a first value with the second message and recovering each radio bearer in the first set of radio bearers; the first domain is used to indicate a cause of an RRC connection resume request; the first value is one of a first candidate value set, and the first candidate value set comprises at least one value; the first radio bearer set includes at least one of SRB2 or DRB or multicast MRB; a second domain is used to indicate data transmission in the RRC inactive state, the second domain being associated with the second message.

Example 7

Embodiment 7 illustrates a schematic diagram in which the first field in the second message is set to the second value to indicate data transmission in the RRC inactive state according to an embodiment of the present application, as shown in fig. 7.

In embodiment 7, if the first message indicates that the first node performs data transmission in the RRC inactive state, the first field in the second message is set to the second value to be used for indicating data transmission in the RRC inactive state; the first set of candidate values and the second set of candidate values are different.

As an embodiment, the first field in the second message is set to the first value indicating that data transmission is not in the RRC inactive state.

As an embodiment, the first field in the second message is set to the first value not to indicate data transmission in the RRC inactive state.

As one embodiment, the first node receives a first message in an RRC inactive state, the first message including a first identification, the first identification being associated with the first node, the first message not indicating that the first node is transmitting data in the RRC inactive state; transmitting a second message as a response to the first message being received, the second message including an RRC connection resume request message; setting the first field in the second message to a first value with the second message and not recovering each radio bearer in the first set of radio bearers; the first value is one of a first candidate value set, and the first candidate value set comprises at least one value; at least one of SRB2 or DRB or multicast MRB is included in the first set of radio bearers.

As one embodiment, the first node receives a first message in an RRC inactive state, the first message including a first identification, the first identification being associated with the first node, the first message indicating that the first node is transmitting data in the RRC inactive state; transmitting a second message as a response to the first message being received, the second message including an RRC connection resume request message; setting the first field in the second message to a second value with the second message and recovering each radio bearer in the first set of radio bearers; the second value is one of a second set of candidate values, the second set of candidate values including at least one value therein; the first radio bearer set includes at least one of SRB2 or DRB or multicast MRB; the first field in the second message is set to the second value to indicate data transmission in the RRC inactive state.

Example 8

Embodiment 8 illustrates a schematic diagram of whether the second candidate set and the first candidate set are the same in relation to at least one of whether PUSCH resources carrying at least the second message are indicated by the third message or whether a random access preamble associated with the second message is associated to the SDT, as shown in fig. 8, according to an embodiment of the present application.

In embodiment 8, whether the second set of candidate values and the first set of candidate values are the same relates to at least one of whether PUSCH resources carrying at least the second message are indicated by the third message or whether a random access preamble associated with the second message is associated to an SDT.

As an embodiment, if each condition in the first set of conditions is met, PUSCH resources carrying the second message are indicated by the third message.

As an embodiment, PUSCH resources carrying the second message are not indicated by the third message if at least one condition of the first set of conditions is not met.

As one embodiment, the first set of conditions is used to determine whether to trigger CG-SDT.

As a sub-embodiment of this embodiment, the second message trigger CG-SDT is determined if each condition in the first set of conditions is satisfied.

As a sub-embodiment of this embodiment, the second message triggers CG-SDT if each condition in the first set of conditions is satisfied; the second message does not trigger CG-SDT if at least one condition of the first set of conditions is not satisfied.

As a sub-embodiment of this embodiment, if the second message triggers CG-SDT, PUSCH resources carrying the second message are indicated by the third message; and if the second message does not trigger CG-SDT, the PUSCH resource carrying the second message is not indicated by the third message.

As a sub-embodiment of this embodiment, one condition of the first set of conditions includes: CG-SDT is configured.

As an subsidiary embodiment of this sub-embodiment, said CG-SDT is configured to include: the third message indicates CG-SDT resources.

As an adjunct embodiment to this sub-embodiment, the CG-SDT resource is grant type 1 (configured grant Type 1).

As an subsidiary embodiment of this sub-embodiment, said CG-SDT is configured to include: the Suspenconfig field in the third message includes SDT-CG-Config or SDT-CG-Config-r17 or SDT-CG-Config-r18.

As an subsidiary embodiment of this sub-embodiment, said CG-SDT is configured to include: the SuptendConfig field in the third message includes sdt-MAC-PHY-CG-Config or sdt-MAC-PHY-CG-Config-r17 or sdt-MAC-PHY-CG-Config-r18.

As an subsidiary embodiment of this sub-embodiment, said CG-SDT is configured to include: the Suspenconfig field in the third message includes SDT-MAC-PHY-CG-Config or SDT-MAC-PHY-CG-Config-r17 or SDT-MAC-PHY-CG-Config-r18.

As an subsidiary embodiment of this sub-embodiment, said CG-SDT is configured to include: the SuspendConfig field in the third message comprises CG-SDT-TA-ValidiationConfig or CG-SDT-TA-ValidiationConfig-r 17 or CG-SDT-TA-ValidiationConfig-r 18.

As a sub-embodiment of this embodiment, one condition of the first set of conditions includes: the TA of CG-SDT resources is valid.

As an auxiliary embodiment of the sub-embodiment, CG-SDT-timealigntimer corresponding to the CG-SDT resource is running.

As an subsidiary embodiment of this sub-embodiment, the current RSRP value is increased or decreased by no more than cg-SDT-RSRP-ChangeThreshold as compared to the stored RSRP value.

As a sub-embodiment of this embodiment, one condition of the first set of conditions includes: the SS-RSRP of at least one SSB configuring the CG-SDT is higher than CG-SDT-RSRP-ThresholdSSB.

As a sub-embodiment of this embodiment, one condition of the first set of conditions includes: SIB1 includes sdt-ConfigCommon.

As a sub-embodiment of this embodiment, one condition of the first set of conditions includes: the first node is configured sdt-Config.

As a sub-embodiment of this embodiment, one condition of the first set of conditions includes: the lower layer indicates that the conditions for initiating SDT are satisfied.

As one embodiment, the random access preamble associated with the second message is associated to the SDT if each condition in the second set of conditions is satisfied.

As one embodiment, the random access preamble associated with the second message is not associated to the SDT if at least one condition of the second set of conditions is not satisfied.

As one embodiment, the second set of conditions is used to determine whether to trigger RA-SDT.

As a sub-embodiment of this embodiment, each condition of the second set of conditions is satisfied is used to determine that the second message triggers RA-SDT.

As a sub-embodiment of this embodiment, the second message triggers RA-SDT if each condition in the second set of conditions is satisfied; the second message does not trigger RA-SDT if at least one condition in the second set of conditions is not satisfied.

As a sub-embodiment of this embodiment, if the second message triggers RA-SDT, the random access preamble associated with the second message is associated to SDT; if the second message does not trigger RA-SDT, the random access preamble associated with the second message is associated to SDT.

As a sub-embodiment of this embodiment, one condition of the second set of conditions includes: SIB1 includes sdt-ConfigCommon.

As a sub-embodiment of this embodiment, one condition of the second set of conditions includes: the first node is configured sdt-Config.

As a sub-embodiment of this embodiment, one condition of the second set of conditions includes: the lower layer indicates that the conditions for initiating SDT are satisfied.

As an embodiment, if PUSCH resources carrying the second message are indicated by the third message, the second candidate set of values is the same as the first candidate set of values.

As an embodiment, the second candidate set of values is the same as the first candidate set of values if the random access preamble associated with the second message is associated to an SDT.

As an embodiment, if PUSCH resources carrying the second message are indicated by the third message, or if a random access preamble associated with the second message is associated to an SDT, the second candidate set of values is the same as the first candidate set of values.

As an embodiment, if PUSCH resources carrying the second message are not indicated by the third message and a random access preamble associated with the second message is not associated to an SDT, the second set of candidates and the first set of candidates are different.

As an embodiment, the second candidate set of values is the same as the first candidate set of values if each condition of the first set of conditions is met or if each condition of the second set of conditions is met.

As an embodiment, the second set of candidate values and the first set of candidate values are different if at least one condition of the first set of conditions is not met and at least one condition of the second set of conditions is not met.

As an embodiment, the second candidate value set is the same as the first candidate value set if the second message triggers CG-SDT or if the second message triggers RA-SDT.

As an embodiment, if the second message does not trigger CG-SDT and the second message does not trigger RA-SDT, the second set of candidate values and the first set of candidate values are different.

As one embodiment, a first message is received in an RRC inactive state, the first message including a first identification, the first identification being associated with the first node, the first message indicating that the first node is transmitting data in the RRC inactive state; transmitting a second message as a response to the first message being received, the second message including an RRC connection resume request message; setting the first field in the second message to a second value with the second message, and recovering each radio bearer in the first set of radio bearers, the first field being used to indicate a cause of an RRC connection recovery request; the first radio bearer set includes at least one of SRB2 or DRB or multicast MRB; the first value is one of a first candidate value set, and the first candidate value set comprises at least one value; the second value is one of a second set of candidate values, the second set of candidate values including at least one value therein; the second set of candidate values is different from the first set of candidate values; PUSCH resources carrying the second message are not indicated by the third message, and the random access preamble associated with the second message is not associated to an SDT.

As one embodiment, a first message is received in an RRC inactive state, the first message including a first identification, the first identification being associated with the first node, the first message indicating that the first node is transmitting data in the RRC inactive state; transmitting a second message as a response to the first message being received, the second message including an RRC connection resume request message; setting the first field in the second message to a second value with the second message, and recovering each radio bearer in the first set of radio bearers, the first field being used to indicate a cause of an RRC connection recovery request; the first radio bearer set includes at least one of SRB2 or DRB or multicast MRB; the first value is one of a first candidate value set, and the first candidate value set comprises at least one value; the second value is one of a second set of candidate values, the second set of candidate values including at least one value therein; the second candidate value set is the same as the first candidate value set; the PUSCH resource carrying the second message is indicated by the third message, or if the random access preamble associated with the second message is associated to an SDT.

Example 9

Embodiment 9 illustrates a wireless signal transmission flow diagram according to another embodiment of the present application, as shown in fig. 9. It is specifically explained that the order in this example does not limit the order of signal transmission and the order of implementation in the present application.

For the followingFirst node U01In step S9101, a first message is received in an RRC inactive state, the first message including a first identification, the first identification being associated to the first node U01, the first message not indicating that the first node U01 is transmitting data in the RRC inactive state; in step S9102, with the second message, setting a first field in the second message to a first value, the first field being used to indicate a cause of an RRC connection resume request; in step S9103, sending a second message as a response to the first message being received, the second message including an RRC connection resume request message; in step S9104, before the second message is delivered to a protocol layer below the RRC layer, starting the third timer; in step S9105, listening for a fourth message during operation of the first timer in response to the second message being sent; in step S9106, a fourth message is received; in step S9107, if a fourth message is received, stopping the third timer; in step S9108, the third timer expires; in step S9109, as expiration of the third timer In response, an RRC idle state is entered.

For the followingSecond node N02In step S9201, the first message is transmitted.

For the followingFourth node N04In step S9401, the second message is received; in step S9402, the fourth message is sent.

In embodiment 9, at least one of SRB2 or DRB or multicast MRB is included in the first set of radio bearers; the first value is one of a first set of candidate values, the first set of candidate values including at least one value therein.

As an embodiment, the second message triggers the starting of the third timer.

As an embodiment, the third timer is an RRC layer timer.

As one embodiment, the third timer is T319.

As an embodiment, if a cell reselection is performed, the third timer is stopped.

As an embodiment, if relay selection (relay selection) or relay reselection (relay reselection) is performed, the third timer is stopped.

As an example, the dashed box F9.1 is optional.

As an example, the dashed box F9.1 exists.

As a sub-embodiment of this embodiment, the fourth message is an RRC message.

As a sub-embodiment of this embodiment, the fourth message is an RRC response to the second message.

As a sub-embodiment of this embodiment, the fourth message is any one of a rrcrenulate message or a RRCSetup message or a rrcrenulate message or a RRCReject message carrying a supendcon.

As an example, the dashed box F9.1 does not exist.

As an example, the dashed box F9.2 is optional.

As an example, the dashed box F9.2 exists.

As an example, the dashed box F9.2 does not exist.

As an embodiment, the dashed box F9.1 and the dashed box F9.2 do not exist at the same time.

Example 10

Embodiment 10 illustrates a block diagram of a processing apparatus for use in a first node according to one embodiment of the application; as shown in fig. 10. In fig. 10, a processing means 1000 in a first node comprises a first receiver 1001 and a first transmitter 1002.

A first receiver 1001 receiving a first message in an RRC inactive state, the first message comprising a first identity, the first identity being associated to the first node;

A first transmitter 1002 that transmits a second message including an RRC connection restoration request message as a response to the first message being received; setting a first domain in the second message according to at least whether the first message indicates that the first node performs data transmission in the RRC inactive state and determining whether to recover each radio bearer in a first set of radio bearers, the first domain being used to indicate a cause of an RRC connection recovery request;

in embodiment 10, the act of setting the first domain in the second message and determining whether to resume each radio bearer in the first set of radio bearers based on at least whether the first message indicates that the first node is in the RRC inactive state comprises: if the first message does not indicate that the first node is in the RRC inactive state for data transmission, setting the first field in the second message to a first value, and not recovering each radio bearer in the first set of radio bearers; if the first message indicates that the first node performs data transmission in the RRC inactive state, setting the first domain in the second message to a second value, and recovering each radio bearer in the first radio bearer set; the first radio bearer set includes at least one of SRB2 or DRB or multicast MRB; the first value is one of a first candidate value set, and the first candidate value set comprises at least one value; the second value is one of a second set of candidate values, the second set of candidate values including at least one value therein.

As an embodiment, the first receiver 1001 receives a third message before the first message, the third message indicating the first set of radio bearers; wherein the third message is used to determine to enter or remain in the RRC inactive state.

As an embodiment, if the first message indicates that the first node is transmitting data in the RRC inactive state, a second domain is used to indicate that the first node is transmitting data in the RRC inactive state, the second domain being associated with the second message; the first candidate set and the second candidate set are the same.

As an embodiment, if the first message indicates that the first node is transmitting data in the RRC inactive state, the first field in the second message is set to the second value to be used for indicating that the first node is transmitting data in the RRC inactive state; the first set of candidate values and the second set of candidate values are different.

As an embodiment, if the first message indicates that the first node is transmitting data in the RRC inactive state, whether the second candidate set and the first candidate set are the same relates to at least one of whether PUSCH resources carrying at least the second message are indicated by the third message or whether a random access preamble associated with the second message is associated to an SDT.

As an embodiment, if the first message indicates that the first node is transmitting data in the RRC inactive state, the first receiver 1001 listens for a fourth message during the first timer run as a response to the second message being sent; stopping the first timer if a fourth message is received; if the first timer expires, entering an RRC idle state; wherein the fourth message is not associated to any radio bearer in the first set of radio bearers.

As an embodiment, the first transmitter 1002 starts the first timer with the second message.

As an embodiment, the first receiver 1001 receives a first data block after the second message is sent; starting or restarting a second timer in response to the first data block being received; wherein the first data block is associated to one radio bearer of the first set of radio bearers.

As an example, the first receiver 1001 includes the antenna 452, the receiver 454, the multi-antenna receive processor 458, the receive processor 456, the controller/processor 459, the memory 460 and the data source 467 of fig. 4 of the present application.

As an example, the first receiver 1001 includes the antenna 452, the receiver 454, the multi-antenna receive processor 458, and the receive processor 456 of fig. 4 of the present application.

As an example, the first receiver 1001 includes the antenna 452, the receiver 454, and the receive processor 456 of fig. 4 of the present application.

As an example, the first transmitter 1002 includes the antenna 452, the transmitter 454, the multi-antenna transmit processor 457, the transmit processor 468, the controller/processor 459, the memory 460, and the data source 467 of fig. 4 of the present application.

As an example, the first transmitter 1002 includes the antenna 452, the transmitter 454, the multi-antenna transmit processor 457, the transmit processor 468 of fig. 4 of the present application.

As an example, the first transmitter 1002 includes the antenna 452, the transmitter 454, and the transmit processor 468 of fig. 4 of the application.

Example 11

Embodiment 11 illustrates a block diagram of a processing apparatus for use in a second node according to one embodiment of the application; as shown in fig. 11. In fig. 11, the processing means 1100 in the second node comprises a second transmitter 1101 and a second receiver 1102.

A second transmitter 1101 that transmits a first message including a first identification, the first identification being associated with a recipient of the first message;

A second receiver 1102 that receives a second message as a response to the first message being transmitted, the second message including an RRC connection restoration request message;

in embodiment 11, the receiver of the first message receives the first message in an RRC inactive state; with the second message, at least whether the first message indicates that the recipient of the first message is in the RRC inactive state for data transmission is used by the recipient of the first message to set a first field in the second message and determine whether to recover each radio bearer in a first set of radio bearers, the first field being used to indicate a cause of an RRC connection recovery request; the phrase whether at least the first message indicates that the recipient of the first message is in the RRC inactive state for data transmission is used by the recipient of the first message to set a first domain in the second message and to determine whether to resume each radio bearer in a first set of radio bearers includes: the first message not indicating that the data transmission by the recipient of the first message in the RRC inactive state is used to determine to set the first field in the second message to a first value and not to recover each radio bearer in the first set of radio bearers; the first message indicating that data transmission by a receiver of the first message in the RRC inactive state is used to determine to set the first field in the second message to a second value and to resume each radio bearer in the first set of radio bearers; the first radio bearer set includes at least one of SRB2 or DRB or multicast MRB; the first value is one of a first candidate value set, and the first candidate value set comprises at least one value; the second value is one of a second set of candidate values, the second set of candidate values including at least one value therein.

As an embodiment, a third message is sent before the first message, the third message indicating the first set of radio bearers; the third message is used to determine to enter or remain in the RRC inactive state.

As an embodiment, the second transmitter 1101 sends the third message.

As an embodiment, the recipient of the third message is the recipient of the first message.

As an embodiment, if the first message indicates that the receiver of the first message is transmitting data in the RRC inactive state, a second domain is used to indicate that data is transmitted in the RRC inactive state, the second domain being associated with the second message; the first candidate set and the second candidate set are the same.

As an embodiment, if the first message indicates that the receiver of the first message is transmitting data in the RRC inactive state, the first field in the second message is set to the second value to be used for indicating that data is transmitted in the RRC inactive state; the first set of candidate values and the second set of candidate values are different.

As an embodiment, if the first message indicates that the receiver of the first message is transmitting data in the RRC inactive state, whether the second candidate set of values and the first candidate set of values are the same relates to at least one of whether PUSCH resources carrying at least the second message are indicated by the third message or whether a random access preamble associated with the second message is associated to an SDT.

As an embodiment, the second transmitter 1101 determines whether to transmit a fourth message as a response to the second message being received if the first message indicates that the receiver of the first message is transmitting data in the RRC inactive state; wherein the fourth message is listened to by a recipient of the first message during operation of a first timer; if a fourth message is received by a recipient of the first message, the first timer is stopped; if the first timer expires, the receiver of the first message enters an RRC idle state; the fourth message is not associated to any radio bearer in the first set of radio bearers.

As an embodiment, the first timer is started by a recipient of the first message accompanying the second message.

As an embodiment, the second transmitter 1101 sends a first data block after the second message is received; wherein a second timer is started or restarted by the recipient of the first message in response to the first data block being received by the recipient of the first message; the first data block is associated to one radio bearer of the first set of radio bearers.

As an example, the second transmitter 1101 includes the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416, the controller/processor 475, and the memory 476 of fig. 4 of the present application.

As an example, the second transmitter 1101 includes the antenna 420, the transmitter 418, the multi-antenna transmission processor 471, and the transmission processor 416 of fig. 4 of the present application.

As an example, the second transmitter 1101 includes the antenna 420 of fig. 4, the transmitter 418, and the transmitting processor 416 of the present application.

As an example, the second receiver 1102 includes the antenna 420, the receiver 418, the multi-antenna receive processor 472, the receive processor 470, the controller/processor 475, and the memory 476 of fig. 4 of the present application.

As an example, the second receiver 1102 includes the antenna 420, the receiver 418, the multi-antenna receive processor 472, and the receive processor 470 of fig. 4 of the present application.

As an example, the second receiver 1102 includes the antenna 420, the receiver 418, and the receive processor 470 of fig. 4 of the present application.

Example 12

Embodiment 12 illustrates a wireless signal transmission flow diagram according to yet another embodiment of the present application, as shown in fig. 12. It is specifically explained that the order in this example does not limit the order of signal transmission and the order of implementation in the present application.

For the followingFirst node U01In step S12101, receiving a first message in an RRC inactive state, the first message including a first identity, the first identity being associated to the first node U01, the first message indicating that the first node U01 is transmitting data in the RRC inactive state; in step S12102, with the second message, setting a first field in the second message to a second value, the first field being used to indicate a cause of the RRC connection resume request; in step S12103, recovering each radio bearer in the first set of radio bearers; in step S12104, as a response to the first message being received, a second message including an RRC connection restoration request message is transmitted; in step S12105, starting the first timer with the second message; in step S12106, listening for a fourth message during operation of the first timer in response to the second message being sent; in step S12107, after the second message is transmitted, receiving a first data block; restarting the first timer as a response to the first data block being received in step S12108; in step S12109, a fourth message is received; in step S12110, if a fourth message is received, stopping the first timer; in step S12111, the first timer expires; in step S12112, if the first timer expires, an RRC idle state is entered.

For the followingSecond node N02In step S12201, the first message is sent.

For the followingFourth node N04In step S12401, the second message is received; in step S12402, transmitting the first data block; in step S12403, the fourth message is sent.

In embodiment 12, at least one of SRB2 or DRB or multicast MRB is included in the first set of radio bearers; the second value is one of a second set of candidate values, the second set of candidate values including at least one value therein; the fourth message is not associated to any radio bearer in the first set of radio bearers; the first data block is associated to one radio bearer of the first set of radio bearers.

As an embodiment, the second set of candidate values is the first set of candidate values.

As one embodiment, the second set of candidate values is not the first set of candidate values.

As an example, the dashed box F12.1 is optional.

As an example, the dashed box F12.1 exists.

As a sub-embodiment of this embodiment, the first data packet is received.

As an example, the dashed box F12.1 does not exist.

As a sub-embodiment of this embodiment, the first data packet is not received.

As a sub-embodiment of this embodiment, the first data packet is not received until the first timer expires.

As an example, the dashed box F12.2 is optional.

As an example, the dashed box F12.2 exists.

As a sub-embodiment of this embodiment, the first timer is stopped in response to receiving the fourth message.

As a sub-embodiment of this embodiment, the fourth message is received and the first timer is stopped in response to receiving the fourth message.

As a sub-embodiment of this embodiment, the first data packet is received within a time interval between the second message being received and the fourth message being received.

As a sub-embodiment of this embodiment, the first timer is not restarted during a time interval between the second message being received and the fourth message being received.

As a sub-embodiment of this embodiment, the first timer is restarted during a time interval between the second message being received and the fourth message being received.

As an example, the dashed box F12.2 does not exist.

As an example, the dashed box F12.3 is optional.

As an example, the dashed box F12.3 exists.

As a sub-embodiment of this embodiment, the RRC idle state is entered in response to expiration of the first timer.

As a sub-embodiment of this embodiment, the RRC idle state is entered when the first timer expires.

As a sub-embodiment of this embodiment, the RRC IDLE state is an rrc_idle state.

As an example, the dashed box F12.3 does not exist.

As an embodiment, the dashed box F12.2 and the dashed box F12.3 do not exist at the same time.

As an embodiment, the step S12108 is optional.

As an embodiment, the step S12108 exists.

As a sub-embodiment of this embodiment, the first data block is received for triggering restarting the first timer.

As a sub-embodiment of this embodiment, the first timer is restarted when the first data block is received.

As a sub-embodiment of this embodiment, an indication is sent to the RRC layer when the first data block is received, and the first timer is restarted when the RRC layer receives the indication.

As a sub-embodiment of this embodiment, the first data block is user plane data.

As a sub-embodiment of this embodiment, the first data block is control plane data.

As a sub-embodiment of this embodiment, one radio bearer of the first set of radio bearers is used to carry the first data block.

As a sub-embodiment of this embodiment, the first data block is mapped to one radio bearer of the first set of radio bearers.

As a sub-embodiment of this embodiment, the first data block is transmitted over one radio bearer of the first set of radio bearers.

As a sub-embodiment of this embodiment, the first data block belongs to one radio bearer of the first set of radio bearers.

As a sub-embodiment of this embodiment, the first data block is a PDCP layer packet.

As a sub-embodiment of this embodiment, the first data block is an RLC layer packet.

As a sub-embodiment of this embodiment, the first data block is a MAC layer data packet.

As an embodiment, the step S12108 does not exist.

As a sub-embodiment of this embodiment, the first data block is received without being used to trigger restarting the first timer.

As a sub-embodiment of this embodiment, the first timer is not restarted in response to the first data block being received.

As an embodiment, the second message triggers the starting of the first timer.

As an embodiment, the accompanying the second message relates to the RRC layer sending the second message.

As an embodiment, the accompanying second message is related to the MAC layer transmitting the first SDU.

As an embodiment, the accompanying second message is related to the second message being sent in the air.

As an embodiment, accompanying the second message means sending the second message when it is sent.

As an embodiment, accompanying the second message means sending the second message before it is sent.

As an embodiment, accompanying the second message means that the content of the second message is set.

As an embodiment, the accompanying second message refers to when the MAC layer transmits the first SDU.

As an embodiment, the first timer is an RRC layer timer.

As an embodiment, the first timer is configurable.

As one embodiment, the first timer is T319.

As one embodiment, the first timer is T319a.

As one embodiment, the first timer is T319b.

As an embodiment, the maximum value of the first timer is configurable.

As an embodiment, the maximum value of the first timer is preconfigured.

As an embodiment, the maximum value of the first timer is configured by an RRC domain.

As one embodiment, SIB1 message is used to configure the first timer.

As an embodiment, one RRC domain in SIB1 message is used to configure the first timer.

As one embodiment, the ue-timersand timers field in SIB1 message is used to configure the first timer.

As one embodiment, the SDT-ConfigCommonSIB field in SIB1 message is used to configure the first timer.

As an embodiment, the listening comprises monitoring.

As one embodiment, the listening comprises decoding.

As an embodiment, the snoop includes a check by CRC (Cyclic Redundancy Check ).

As an embodiment, the listening comprises detecting.

As an embodiment, the act of listening for the fourth message includes: and monitoring DCI scrambled by C-RNTI on the PDCCH, wherein the C-RNTI is used for scheduling PDSCH, and the PDSCH is used for carrying the fourth message.

As an embodiment, the act of listening for the fourth message includes: and monitoring DCI scrambled by TC-RNTI on the PDCCH, wherein the TC-RNTI is used for scheduling PDSCH, and the PDSCH is used for carrying the fourth message.

As an embodiment, the act of listening for the fourth message during operation of the first timer comprises: monitoring for the fourth message while the first timer is running.

As an embodiment, the act of listening for the fourth message during operation of the first timer comprises: and if the first timer is running, monitoring the fourth message.

As an embodiment, the fourth message is an RRC message.

As an embodiment, the fourth message is an RRC response to the second message.

As an embodiment, the fourth message is associated to SRB1.

As an embodiment, the fourth message is associated to SRB0.

As an embodiment, SRB0 is used to carry the fourth message.

As an embodiment, SRB1 is used to carry the fourth message.

As an embodiment, the fourth message is associated to SRB1 or SRB0.

As an embodiment, the fourth message is any one of a rrcreseume message or a RRCSetup message or a RRCRelease message or a RRCReject message carrying a sustendconfig.

As an embodiment, any radio bearer of the first set of radio bearers is not used to carry the fourth message.

As an embodiment, the first data block is a first data block associated to one radio bearer of the first set of radio bearers received after the second message is sent.

As an embodiment, the act of starting a first timer means that the one timer starts counting.

As an embodiment, the act of starting a first timer means that the one timer counts up from 0.

As an embodiment, the act of starting a first timer means that the one timer counts down from a maximum value of the one timer.

As one example, a timer expires when the count of the timer equals 0.

As one embodiment, one timer expires when the count of the one timer is equal to the maximum value of the one timer.

As one embodiment, one timer expires when the running time of the one timer reaches the maximum value of the one timer.

As an embodiment, the achievement comprises equality.

As an embodiment, the reaching includes being equal to or greater than.

As an embodiment, the above one timer includes the first timer.

As an embodiment, the above one timer includes the second timer.

As an embodiment, the above-mentioned one timer includes the third timer in the present application.

As an embodiment, the act of restarting a timer means: the one timer restarts counting.

As an embodiment, the act of restarting a timer means: resetting the one timer is a start value.

As an embodiment, the act of restarting a timer means: the one timer counts up again from 0.

As an embodiment, the act of restarting a timer means: the one timer counts down again from the maximum value of the one timer.

Example 13

Embodiment 13 illustrates a wireless signal transmission flow diagram according to yet another embodiment of the present application, as shown in fig. 13. It is specifically explained that the order in this example does not limit the order of signal transmission and the order of implementation in the present application.

For the followingFirst node U01In step S13101, a first message is received in an RRC inactive state, the first message including a first identity, the first identity being associated to the first node U01, the first message indicating that the first node U01 is transmitting data in the RRC inactive state; in step S13102, with the second message, a first field in the second message is set to a second value, the first field being used to indicate a cause of an RRC connection restoration request; in step S13103, recovering each radio bearer in the first set of radio bearers; in step S13104, as a response to the first message being received, a second message including an RRC connection restoration request message is transmitted; in step S13105, a second timer is started; in step S13106, a first data block is received; in step S13107, a second timer is started as a response to the first data block being received; in step S13108, the second timer is restarted in response to the first data block being received.

For the followingSecond node N02In step S13201, the first message is sent.

For the followingFourth node N04In step S13401, receiving the second message; in step S13402, the first data block is transmitted.

In embodiment 13, at least one of SRB2 or DRB or multicast MRB is included in the first set of radio bearers; the second value is one of a second set of candidate values, the second set of candidate values including at least one value therein; the first data block is associated to one radio bearer of the first set of radio bearers.

As an embodiment, the first data block is received after the second message is sent.

As one embodiment, the first data block is received after the second message is sent; starting or restarting a second timer in response to the first data block being received; wherein the first data block is associated to one radio bearer of the first set of radio bearers.

As an embodiment, the second timer is a MAC layer timer.

As an embodiment, the second timer is datainactivatytimer.

As an embodiment, the second timer is maintained for data transmission in the RRC inactive state.

As an embodiment, the second timer is started after the second message is sent.

As one embodiment, the second timer is started after the second message is delivered to the MAC layer.

As an embodiment, the step S13105 is optional.

As an embodiment, the step S13105 exists.

As an embodiment, the step S13105 does not exist.

As an embodiment, the step S13107 is optional.

As an embodiment, the step S13107 exists.

As an embodiment, the step S13107 does not exist.

As an embodiment, the step S13108 is optional.

As an embodiment, the step S13108 exists.

As an embodiment, the step S13108 does not exist.

As an embodiment, the step S13105 and the step S13108 exist, and the step S13107 does not exist.

As a sub-embodiment of this embodiment, the second timer is started before the first data block is received.

As a sub-embodiment of this embodiment, the second timer is started as a response to the MAC entity transmitting the first SDU.

As a sub-embodiment of this embodiment, the second timer is restarted in response to the first data block being received.

As a sub-embodiment of this embodiment, restarting the second timer as a response to the MAC entity receiving the second SDU; the first data block corresponds to the second SDU.

As an embodiment, the step S13107 exists, and the step S13105 and the step S13108 do not exist.

As an embodiment, the second timer is not started before the first data block is received.

As a sub-embodiment of this embodiment, the second timer is started in response to the first data block being received.

As a sub-embodiment of this embodiment, starting the second timer as a response to the MAC entity receiving the second SDU; the first data block corresponds to the second SDU.

As an embodiment, the second SDU is one of a DTCH (Dedicated Traffic Channel ) SDU or DCCH SDU or multicast MTCH SDU.

As an embodiment, the second SDU is one of a DTCH SDU or DCCH SDU.

As an embodiment, the second SDU is one of multicast MTCH (MBS Traffic Channel ) SDUs.

As an embodiment, the second SDU is one of DCCH SDU or multicast MTCH SDU.

As an embodiment, if the radio bearer with which the first data block is associated is a DRB, the second SDU is a DTCH SDU.

As an embodiment, if the radio bearer with which the first data block is associated is SRB2, the second SDU is DCCH SDU.

As an embodiment, if the radio bearer with which the first data block is associated is a multicast MRB, the second SDU is a multicast MTCH SDU.

As an embodiment, the first timer is not started with the second message.

As an embodiment, the first timer is started with the second message; the first timer is stopped in response to the first data block being received.

As an embodiment, one SDU is a DTCH SDU, which means that the one SDU is directed to a DTCH logical channel.

As an embodiment, one SDU is a DCCH SDU, which means that the one SDU is directed to a DCCH logical channel.

As an embodiment, one SDU is a multicast MTCH SDU, which means that the one SDU is directed to a multicast MTCH logical channel.

As one embodiment, after the second message is sent, a first DCI (Downlink Control Information ) is received, the first DCI being scrambled by a first RNTI (Radio Network Temporary Identifier, radio network temporary identity); the first DCI indicates scheduling information of a PDSCH (Physical downlink shared channel ) used to carry at least the first data block.

As an embodiment, the first RNTI is C-RNTI (Cell RNTI).

As one embodiment, the format of the first DCI is DCI format (format) 1_0.

As an embodiment, the first RNTI is a TC-RNTI; the first data block and UE Contention Resolution Identity MAC CE (Control Element) belong to the same MAC PDU, and UE Contention Resolution Identity in UE Contention Resolution Identity MAC CE matches with the CCCH SDU corresponding to the second message.

As a sub-embodiment of this embodiment, the PDSCH indicated by the first DCI is used to carry the first data block and the UE Contention Resolution Identity MAC CE.

As a sub-embodiment of this embodiment, the random access procedure associated with the second message is considered to be successfully completed in response to the UE Contention Resolution Identity MAC CE being successfully received.

As an embodiment, the first RNTI is an MSGB-RNTI; the first data block and the success RAR belong to the same MAC PDU, and UE Contention Resolution Identity in the success RAR is matched with the CCCH SDU corresponding to the second message.

As a sub-embodiment of this embodiment, the PDSCH indicated by the first DCI is used to carry the first data block and the one success rar.

As a sub-embodiment of this embodiment, the random access procedure associated with the second message is considered to be successfully completed as a response to the success of the success rar.

As an embodiment, the first timer in the present application is not started with the second message.

As one embodiment, the first timer is started with the second message; and stopping the first timer as a response to the random access procedure associated with the second message being successfully completed.

As one embodiment, the first timer is started with the second message; the first timer is stopped in response to the first data block being received.

As one embodiment, the first timer is started with the second message; stopping the first timer as a response to the MAC entity receiving the second SDU; the first data block corresponds to the second SDU.

Those of ordinary skill in the art will appreciate that all or a portion of the steps of the above-described methods may be implemented by a program that instructs associated hardware, and the program may be stored on a computer readable storage medium, such as a read-only memory, a hard disk or an optical disk. Alternatively, all or part of the steps of the above embodiments may be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiment may be implemented in a hardware form or may be implemented in a software functional module form, and the present application is not limited to any specific combination of software and hardware. The user equipment, the terminal and the UE in the application comprise, but are not limited to, unmanned aerial vehicles, communication modules on unmanned aerial vehicles, remote control airplanes, aircrafts, mini-planes, mobile phones, tablet computers, notebooks, vehicle-mounted communication equipment, wireless sensors, network cards, internet of things terminals, RFID terminals, NB-IOT terminals, MTC (Machine Type Communication ) terminals, eMTC (enhanced MTC) terminals, data cards, network cards, vehicle-mounted communication equipment, low-cost mobile phones, low-cost tablet computers and other wireless communication equipment. The base station or system device in the present application includes, but is not limited to, a macro cell base station, a micro cell base station, a home base station, a relay base station, a gNB (NR node B) NR node B, a TRP (Transmitter Receiver Point, transmitting/receiving node), and other wireless communication devices.

The foregoing description is only of the preferred embodiments of the present application, and is not intended to limit the scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

1. A first node for wireless communication, comprising:

2. The first node of claim 1, comprising:

the first receiver receiving a third message prior to the first message, the third message indicating the first set of radio bearers;

3. The first node according to claim 1 or 2, characterized in that if the first message indicates that the first node is transmitting data in the RRC inactive state, a second domain is used for indicating that data is transmitting in the RRC inactive state, the second domain being associated to the second message; the first candidate set and the second candidate set are the same.

4. The first node according to claim 1 or 2, characterized in that if the first message indicates that the first node is transmitting data in the RRC inactive state, the first field in the second message is set to the second value to be used for indicating that data is transmitted in the RRC inactive state; the first set of candidate values and the second set of candidate values are different.

5. The first node of claim 2, wherein if the first message indicates that the first node is transmitting data in the RRC inactive state, whether the second candidate set and the first candidate set are the same relates to at least one of whether PUSCH resources carrying at least the second message are indicated by the third message or whether a random access preamble associated with the second message is associated with an SDT.

6. The first node according to any of claims 1 to 5, comprising:

the first receiver, if the first message indicates that the first node performs data transmission in the RRC inactive state, as a response to the second message being sent, listening for a fourth message during a first timer run; stopping the first timer if a fourth message is received; if the first timer expires, entering an RRC idle state;

7. The first node of claim 6, comprising:

the first transmitter starts the first timer with the second message.

8. The first node according to claim 6 or 7, comprising:

the first receiver receiving a first data block after the second message is sent; starting or restarting a second timer in response to the first data block being received;

9. A second node for wireless communication, comprising:

10. A method in a first node for wireless communication, comprising:

11. A method in a second node for wireless communication, comprising:

transmitting a first message, the first message comprising a first identification, the first identification being associated with a recipient of the first message;