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

Abstract

This application discloses a method and apparatus for use in a communication node for wireless communication. The communication node receives a first message indicating at least a first bearer; in response to receiving the first message, it enters or remains in an RRC inactive state; during data transmission through the first bearer in the RRC inactive state, it receives a first signaling and a second message, the first signaling including scheduling information for a first channel, and at least the second message being transmitted on the first channel, the second message being used to trigger data transmission through a second bearer; one of the first bearer and the second bearer is an MRB, and the other is a DRB; the first signaling is scrambled by a first RNTI; if the first bearer is an MRB, the first RNTI belongs to a first candidate RNTI set; if the first bearer is a DRB, the first RNTI belongs to a second candidate RNTI set; the first candidate RNTI set includes at least a G-RNTI; the second candidate RNTI set includes at least a C-RNTI.

Description

Technical Field

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

[0002] NR (New Radio) supports the RRC (Radio Resource Control) INACTIVE state until 3GPP (3rd Generation Partnership Project) Rel-16, but does not support sending or receiving data in the RRC inactive state. Rel-17 initiated a work item (WI) on "Small Data Transmission (SDT) in Inactive NR State," investigating small data transmission techniques in the RRC_INACTIVE state. This included transmitting uplink data on pre-configured PUSCH (Physical Uplink Shared Channel) resources or using Message 3 (Msg3) or Message B (MsgB) during the Random Access (RA) procedure to carry data. Rel-17 also initiated a work item (WI) on "Receiving MBS (Multicast / Broadcast Service) in Connected RRC State." Rel-18 investigated MBS reception in the RRC_INACTIVE state and downlink data transmission in the RRC_INACTIVE state. Summary of the Invention

[0003] When a base station has MBS service, it sends a paging message. When a UE receives the paging message, if the paging message includes a TMGI (Temporary Mobile Group Identity) and the UE participates in that TMGI, the UE initiates an RRC Resume procedure and enters the RRC connected state to receive MBS. However, existing protocols do not support UEs receiving paging messages during SDT (Short-Terminal Data Transmission) in the RRC_INACTIVE state, thus preventing UEs from receiving MBS service during SDT. Similarly, Rel-18 will investigate receiving MBS in the RRC_INACTIVE state. If paging messages cannot be received during MBS reception, the base station cannot notify the UE via paging messages when it has downlink data transmission. Therefore, enhancements are needed to support other service transmissions during SDT or MBS reception in the RRC_INACTIVE state.

[0004] To address the aforementioned issues, this application provides a solution. While the NR scenario is used as an example in the problem description, this application is also applicable to scenarios such as LTE (Long Term Evolution) or NB-IoT (Narrow Band Internet of Things), achieving similar technical effects to the NR scenario. Furthermore, using a unified solution across different scenarios helps reduce hardware complexity and cost.

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

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

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

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

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

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

[0011] Receive a first message indicating at least a first bearer; in response to receiving the first message, enter or remain in an RRC inactive state;

[0012] During the transmission of data through the first bearer while the RRC is inactive, at least the former of a first signaling or a second message is received; the first signaling or the second message is used to trigger the transmission of data through the second bearer.

[0013] Wherein, one of the first bearer and the second bearer is an MRB (MBS Radio Bearer), and the other is a DRB ((user) Data Radio Bearer); the first signaling is scrambled by a first RNTI (Radio Network Temporary Identifier); the first RNTI is related to the first bearer; if the first bearer is an MRB, the first RNTI is an RNTI in a first candidate RNTI set; if the first bearer is a DRB, the first RNTI is an RNTI in a second candidate RNTI set; the first candidate RNTI set includes at least a G-RNTI; the second candidate RNTI set includes at least a C-RNTI (Cell RNTI).

[0014] As an example, both the first signaling and the second message are received.

[0015] As a sub-example of this embodiment, the first channel is PDSCH (Physical downlink shared channel), and the second message is used to trigger data transmission through the second bearer.

[0016] As a sub-implementation of this embodiment, the first channel is PDSCH or PUSCH, and the first signaling is used to trigger data transmission through the second bearer.

[0017] As one embodiment, only the first signaling is received, and the second message is not received; the first signaling is used to trigger data transmission through the second bearer.

[0018] As an example, the first bearer is an MRB, and the second bearer is a DRB; the first signaling is scrambled by a first RNTI; the first RNTI is related to the first bearer; the first RNTI is an RNTI in a first candidate RNTI set; the first candidate RNTI set includes at least a G-RNTI (Group RNTI).

[0019] As an example, the first bearer is a DRB, the second bearer is an MRB; the first signaling is scrambled by a first RNTI; the first RNTI is related to the first bearer; the first RNTI is an RNTI in a second set of candidate RNTIs; the second set of candidate RNTIs includes at least C-RNTIs.

[0020] As one embodiment, the first signaling includes scheduling information for a first channel, and at least the second message is transmitted on the first channel.

[0021] As an example, the problem this application aims to solve includes: how to notify the UE that data needs to be transmitted via a second bearer during the period when the RRC is inactive and data is transmitted via the first bearer.

[0022] As an example, the problem this application aims to solve includes: how to reduce the power consumption of the UE in the RRC inactive state.

[0023] As an example, the problem this application aims to solve includes: how to achieve a compatible design between SDT and MBS.

[0024] As an example, the features of the above method include: during the transmission of data through the first bearer in the RRC inactive state, using a signaling other than a paging message to notify the UE to transmit data through the second bearer.

[0025] As an example, the features of the above method include: during the reception of MBS services in the RRC inactive state, using the MBS-related channel to notify the UE that data needs to be transmitted via DRB.

[0026] As an example, the features of the above method include: during the execution of SDT in the RRC inactive state, using an SDT-related channel to notify the UE that data needs to be transmitted via MRB.

[0027] As an example, the features of the above method include: using a message other than the paging message to perform the function of the paging message.

[0028] As an example, the advantages of the above method include: avoiding the use of paging messages and reducing the power consumption of other UEs in the RRC inactive state.

[0029] As an example, the advantages of the above method include: enabling the UE to trigger MBS reception during SDT for scenarios where paging messages are not listened to during SDT.

[0030] As an example, the advantages of the above method include: improved paging efficiency.

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

[0032] In response to receiving the second message, a third message is sent, which is used in the RRC connection recovery process;

[0033] In response to the sending of the third message, monitor the fourth message;

[0034] During the RRC connection recovery process, the second bearer is restored;

[0035] The fourth message belongs to the RRC connection recovery process.

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

[0037] In response to receiving the second message, the second bearer is restored; however, receiving the second message does not trigger the RRC connection restoration process.

[0038] According to one aspect of this application, the second message includes a first identity of the first node, the first identity of the first node being unique within at least one cell; the first bearer is an MRB, and the first RNTI is an RNTI in the first set of candidate RNTIs.

[0039] According to one aspect of this application, the second message includes a second identity used to indicate a first MBS session, wherein the first node participates in the first MBS session; the first bearer is a DRB, and the first RNTI is an RNTI in the second set of candidate RNTIs.

[0040] According to one aspect of this application, the second message indicates that data is transmitted via the second bearer in the RRC inactive state.

[0041] According to one aspect of this application, the second message indicates that data is transmitted via the second bearer in an RRC connection state.

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

[0043] Send a first message, the first message indicating at least a first bearer;

[0044] Send a first signaling message and a second message, wherein the first signaling message includes scheduling information for a first channel, and at least the second message is sent on the first channel, and the second message is used to trigger data transmission through a second bearer;

[0045] In this context, as a response to the receipt of the first message, the recipient of the first message enters or remains in an RRC inactive state; the first signaling and the second message are received by the recipient of the first message during data transmission via the first bearer in the RRC inactive state; one of the first bearer and the second bearer is an MRB, and the other is a DRB; the first signaling is scrambled with a first RNTI; the first RNTI is associated with the first bearer; if the first bearer is an MRB, the first RNTI is an RNTI in a first candidate RNTI set; if the first bearer is a DRB, the first RNTI is an RNTI in a second candidate RNTI set; the first candidate RNTI set includes at least a G-RNTI; and the second candidate RNTI set includes at least a C-RNTI.

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

[0047] Receive a third message, which is used in the RRC connection recovery process;

[0048] In response to the receipt of the third message, determine whether to send a fourth message;

[0049] During the RRC connection recovery process, the second bearer is restored; the fourth message belongs to the RRC connection recovery process; the second message is used to trigger the third message.

[0050] According to one aspect of this application, the second bearer is restored in response to the second message being received by the recipient of the first message; the receipt of the second message by the recipient of the first message does not trigger the RRC connection restoration process.

[0051] According to one aspect of this application, the second message includes a first identity of the recipient of the first message, the first identity of the recipient of the first message being unique within at least one cell; the first bearer is an MRB, and the first RNTI is an RNTI in the first set of candidate RNTIs.

[0052] According to one aspect of this application, the second message includes a second identity used to indicate a first MBS session, wherein the recipient of the first message participates in the first MBS session; the first bearer is a DRB, and the first RNTI is an RNTI in the second set of candidate RNTIs.

[0053] According to one aspect of this application, the second message indicates that data is transmitted via the second bearer in the RRC inactive state.

[0054] According to one aspect of this application, the second message indicates that data is transmitted via the second bearer in an RRC connection state.

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

[0056] A first receiver receives a first message indicating at least a first bearer; in response to receiving the first message, it enters or remains in an RRC inactive state; during data transmission through the first bearer in the RRC inactive state, it receives a first signaling and a second message, the first signaling including scheduling information for a first channel, at least the second message being transmitted on the first channel, and the second message being used to trigger data transmission through a second bearer;

[0057] Wherein, one of the first bearer and the second bearer is an MRB, and the other is a DRB; the first signaling is scrambled by a first RNTI; the first RNTI is related to the first bearer; if the first bearer is an MRB, the first RNTI is an RNTI in a first candidate RNTI set; if the first bearer is a DRB, the first RNTI is an RNTI in a second candidate RNTI set; the first candidate RNTI set includes at least a G-RNTI; the second candidate RNTI set includes at least a C-RNTI.

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

[0059] The second transmitter sends a first message indicating at least a first bearer; sends a first signaling and a second message, the first signaling including scheduling information for a first channel, at least the second message being sent on the first channel, and the second message being used to trigger data transmission through the second bearer;

[0060] In this context, as a response to the receipt of the first message, the recipient of the first message enters or remains in an RRC inactive state; the first signaling and the second message are received by the recipient of the first message during data transmission via the first bearer in the RRC inactive state; one of the first bearer and the second bearer is an MRB, and the other is a DRB; the first signaling is scrambled with a first RNTI; the first RNTI is associated with the first bearer; if the first bearer is an MRB, the first RNTI is an RNTI in a first candidate RNTI set; if the first bearer is a DRB, the first RNTI is an RNTI in a second candidate RNTI set; the first candidate RNTI set includes at least a G-RNTI; and the second candidate RNTI set includes at least a C-RNTI.

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

[0062] - Avoid using paging messages to reduce power consumption of other UEs in RRC inactive states;

[0063] - For scenarios where paging messages are not listened to during SDT, the UE can trigger MBS reception during SDT;

[0064] - Improve paging efficiency. Attached Figure Description

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

[0066] Figure 1 A flowchart illustrating the transmission of a first message, a first signaling, and a second message according to an embodiment of this application is shown;

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

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

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

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

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

[0072] Figure 7 A schematic diagram is shown showing a second message including a first identity of a first node according to an embodiment of this application;

[0073] Figure 8 A schematic diagram showing a second identity included in a second message according to an embodiment of this application is illustrated;

[0074] Figure 9 A schematic diagram illustrating the transmission of data via a second bearer in an RRC inactive state according to an embodiment of this application is shown.

[0075] Figure 10 A schematic diagram illustrating a second message indication transmitting data via a second bearer in an RRC connection state according to an embodiment of this application is shown.

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

[0077] Figure 12 A structural block diagram of a processing apparatus for a second node according to an embodiment of this application is shown;

[0078] Figure 13 A flowchart illustrating the transmission of a first message and a first signaling according to an embodiment of this application is shown. Detailed Implementation

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

[0080] Example 1

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

[0082] In Embodiment 1, the first node in this application receives a first message in step 101, the first message indicating at least a first bearer; in step 102, in response to receiving the first message, it enters or remains in an RRC inactive state; in step 103, during data transmission through the first bearer in the RRC inactive state, it receives a first signaling and a second message, the first signaling including scheduling information for a first channel, at least the second message being sent on the first channel, and the second message being used to trigger data transmission through a second bearer; wherein, one of the first bearer and the second bearer is an MRB, and the other is a DRB; the first signaling is scrambled by a first RNTI; the first RNTI is associated with the first bearer; if the first bearer is an MRB, the first RNTI is an RNTI in a first candidate RNTI set, and if the first bearer is a DRB, the first RNTI is an RNTI in a second candidate RNTI set; the first candidate RNTI set includes at least a G-RNTI; and the second candidate RNTI set includes at least a C-RNTI.

[0083] As an example, the recipient of the first message is the second node in this application.

[0084] As an example, the recipient of the first message is the same as the recipient of the first signaling.

[0085] As an example, the recipient of the first message is different from the recipient of the first signaling.

[0086] As an example, the recipient of the first signaling is the same as the recipient of the second message.

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

[0088] As an example, the logical channel of the first message is DCCH (Dedicated Control Channel).

[0089] As an example, the signaling radio bearer of the first message is SRB1.

[0090] As an example, the first message includes an RRCRelease message.

[0091] As an example, the first message includes an RRCConnectionRelease message.

[0092] As an example, the first message includes at least one RRC IE (Information Element).

[0093] As one example, the first message includes at least one RRC field.

[0094] As an example, the first message includes an RRC field whose name includes suspendConfig.

[0095] As an example, at least one RRC IE or at least one RRC field in the first message indicates the first DRB.

[0096] As an example, the first message includes the suspendConfig field from the RRCRelease message.

[0097] As an example, the first message is the suspendConfig field in the RRCRelease message.

[0098] As an example, the first message includes a field whose name in the RRCConnectionRelease message includes RRC-InactiveConfig.

[0099] As an example, the first message is an RRCConnectionRelease message whose name includes the field RRC-InactiveConfig.

[0100] As an example, the first message is an RRCConnectionRelease message whose name includes the RRCConnectionRelease field.

[0101] As an example, the first message indicates the first bearer.

[0102] As an example, the first message implicitly indicates the first bearer.

[0103] As one embodiment, the phrase "the first message indicates at least a first bearer" includes: the first message indicates the first bearer, and the first bearer indicates the second bearer.

[0104] As a sub-example of this embodiment, the first message indicates the second bearer.

[0105] As a sub-implementation of this embodiment, the first message implicitly indicates the second bearer.

[0106] As one embodiment, the phrase "the first message indicates at least a first bearer" includes: the first message indicates the first bearer, and the first bearer does not indicate the second bearer.

[0107] As one embodiment, the first message indicates that the first bearer includes: the first message includes configuration information of the first bearer.

[0108] As one embodiment, the first message indicates that the first bearer includes: the first message includes an identifier of the first bearer.

[0109] As one embodiment, the first bearer indicates that the second bearer includes: the first message includes configuration information of the second bearer.

[0110] As one embodiment, the first bearer indicating the second bearer includes: the first message includes an identifier of the second bearer.

[0111] As an example, the first message including drb-ContinueROHC is used to indicate the first bearer.

[0112] As an example, the first message includes a field whose name includes drb-ContinueROHC, which is used to indicate the first bearer.

[0113] As an example, the first message including mrb-ContinueROHC is used to indicate the first bearer.

[0114] As an example, the first message includes a field whose name includes mrb-ContinueROHC, which is used to indicate the first bearer.

[0115] As an example, the first message indicates that the first bearer can be used to transmit data via the first bearer in the RRC inactive state.

[0116] As an example, the first message indicates that the second bearer can be used to transmit data via the second bearer in the RRC inactive state.

[0117] As one embodiment, the first message indicates at least one first-class DRB, and the first message does not indicate any first-class MRB; the first bearer is any one of the at least one first-class DRBs.

[0118] As one embodiment, the first message indicates at least one first-class MRB, and the first message does not indicate any first-class DRB; the first bearer is any one of the at least one first-class MRB.

[0119] As one embodiment, the first message indicates at least one first type DRB, and the first message indicates at least one first type MRB; the first bearer is any one of the at least one first type DRB, and the second bearer is any one of the at least one first type MRB.

[0120] As one embodiment, the first message indicates at least one first type DRB, and the first message indicates at least one first type MRB; the first bearer is any one of the at least one first type MRB, and the second bearer is any one of the at least one first type DRB.

[0121] As an example, the second bearer is not released during the time interval between the moment the first message is received and the moment the first signaling is received.

[0122] As an example, during the time interval between the moment the first message is received and the moment the first signaling is received, the second bearer is in a suspended state.

[0123] As an example, the second bearer is not released before the first signaling is received.

[0124] As an example, the second bearer is in a suspended state before the first signaling is received.

[0125] As an example, in response to receiving the first message, all first-type bearers are suspended.

[0126] As an example, in response to receiving the first message, all second-type bearers are suspended.

[0127] As one example, in response to receiving the first message, the first bearer is suspended.

[0128] As one example, in response to receiving the first message, the second bearer is suspended.

[0129] As one embodiment, in response to receiving the first message, the first bearer and the second bearer are suspended.

[0130] As one embodiment, in response to receiving the first message, the first bearer is held and the second bearer is suspended.

[0131] As an example, maintaining the first bearer means that if the first bearer is in a suspended state, after receiving the first message, the first bearer remains in a suspended state.

[0132] As an example, maintaining the first bearer means that if the first bearer is not in a suspended state, the first bearer is not suspended after receiving the first message.

[0133] As an example, in response to receiving the first message, the system enters an RRC inactive state.

[0134] As an example, in response to receiving the first message, the system remains in an RRC inactive state.

[0135] As an example, in response to the receipt of the first message, the first node U01 is in an RRC inactive state.

[0136] As an example, the first message is used to cause the first node U01 to enter the RRC inactive state from the RRC connected state.

[0137] As an example, the first message is used to keep the first node U01 in an RRC inactive state.

[0138] As an example, before the first message is received, the first node U01 is in an RRC connection state.

[0139] As an example, before the first message is received, the first node U01 is in an RRC inactive state.

[0140] As an example, after the first message is received, the first node U01 is in an RRC inactive state.

[0141] As an example, during the transmission of data through the first bearer in the RRC inactive state, the first bearer is configured and is not suspended.

[0142] As an example, during the transmission of data through the first bearer in the RRC inactive state, at least one uplink data is sent, or at least one downlink data is received.

[0143] As an example, SRB1 is not suspended during the transmission of data through the first bearer while the RRC is inactive.

[0144] As an example, SRB1 is suspended during data transmission through the first bearer while the RRC is inactive.

[0145] As an example, SRB2 is not suspended during the transmission of data through the first bearer while the RRC is inactive.

[0146] As an example, SRB2 is suspended during the transmission of data through the first bearer while the RRC is inactive.

[0147] As an example, the second bearer is suspended during data transmission through the first bearer while the RRC is inactive.

[0148] As an example, the first timer is running during the transmission of data through the first bearer while the RRC is inactive.

[0149] As an example, transmitting data through the first bearer in the RRC inactive state means: performing EDT (Early Data Transmission) in the RRC inactive state; the first bearer is a first type DRB.

[0150] As an example, transmitting data through the first bearer in the RRC inactive state means: performing SDT in the RRC inactive state; the first bearer is a first type DRB.

[0151] As an example, transmitting data through the first bearer in the RRC inactive state means: performing MT-SDT in the RRC inactive state; the first bearer is a first type DRB.

[0152] As an example, transmitting data through the first bearer in the RRC inactive state means: performing MO-SDT in the RRC inactive state; the first bearer is a first type DRB.

[0153] As an example, transmitting data through the first bearer in the RRC inactive state means: receiving MBS in the RRC inactive state; the first bearer is a first type MRB.

[0154] As an example, the recovery of the first bearer in the RRC inactive state is used to determine that data is transmitted through the first bearer in the RRC inactive state.

[0155] As an example, a first timer is running to determine that data is being transmitted through the first bearer in the RRC inactive state, and the first timer is not T319.

[0156] As an example, transmitting data through the first bearer in the RRC inactive state belongs to the first RRC update process.

[0157] As an example, the first RRC update process includes: sending a first target message, which is transmitted via CCCH (Common Control Channel).

[0158] As a sub-implementation of this embodiment, the first target message includes an RCResumeRequest message or an RCResumeRequest1 message.

[0159] As a sub-implementation of this embodiment, the first target message includes an RRCConnectionResumeRequest message or an RRCEarlyDataRequest message.

[0160] As an example, the first RRC update process includes: receiving a second target message.

[0161] As a sub-implementation of this embodiment, the second target message includes an RRCRelease message, or an RRCReject message, or an RRCSetup message.

[0162] As a sub-implementation of this embodiment, the second target message includes one of the following: RRCConnectionResume message, RRCCEarlyDataComplete message, RRCConnectionReject message, RRCConnectionSetup message, or RRCConnectionRelease message.

[0163] As an example, the first RRC update process includes: starting the first timer along with the first target message.

[0164] As an example, the first RRC update process includes: if the second target message is received, stopping the first timer.

[0165] As an example, the first RRC update process includes: restoring the first bearer along with the first target message.

[0166] As an example, the first RRC update process includes: restoring the first bearer along with the second target message.

[0167] As an example, the expiration of the first timer is used to determine whether to enter the RRC idle (RRC_IDLE) state.

[0168] As an example, the expiration of the first timer is used to determine the entry into an RRC inactive state.

[0169] As one embodiment, the expiration of the first timer is used to determine whether the first bearer is suspended.

[0170] As an example, the first timer is running when the first signaling and the second message are received.

[0171] As an example, when the first signaling and the second message are received, the first target message is sent, but the second target message is not received.

[0172] As an example, when the first signaling and the second message are received, the second timer has not expired and the second target message has not been received.

[0173] As an example, data transmitted through the first bearer in the RRC inactive state does not belong to the first RRC update process.

[0174] As one example, in response to receiving the first paging message, the first bearer is restored.

[0175] As an example, during the time interval between receiving the first paging message and restoring the first bearer, the first node does not send an RRC message transmitted via CCCH.

[0176] As an example, the first paging message includes the identity of the first node.

[0177] As an example, the first paging message includes the first identity of the first node.

[0178] As an example, the first paging message includes a TMGI, and the first node participates in one or more MBS sessions identified by the TMGI.

[0179] As an example, the first paging message includes a second identity.

[0180] As one embodiment, receiving a first paging message is used to trigger the first RRC update process, which is used to determine that data is transmitted through the first bearer in the RRC inactive state.

[0181] As an example, each condition in the first set of conditions is satisfied to trigger the first RRC update process, which is used to determine that data is transmitted through the first bearer in the RRC inactive state.

[0182] As one embodiment, receiving a first paging message is used to determine that data is being transmitted through the first bearer in the RRC inactive state.

[0183] As an example, the first paging message is received.

[0184] As an example, the first paging message was not received.

[0185] As an example, the first RRC update process is executed.

[0186] As an example, the first RRC update process was not executed.

[0187] As one embodiment, in response to receiving the first message, the first bearer is suspended; the first bearer is resumed before data is transmitted through the first bearer in the RRC inactive state.

[0188] As an example, in response to receiving the first message, the first bearer is not suspended.

[0189] As an example, the first channel includes a PDSCH.

[0190] As an example, the first channel is PDSCH.

[0191] As an example, the first signaling is used for PDSCH scheduling.

[0192] As an example, the first signaling is used to indicate the physical layer scheduling information of the first channel.

[0193] As an example, the first signaling is not DCI format 1_0 with CRC (Cyclic redundancy check) scrambled by P-RNTI (Paging RNTI).

[0194] As an example, the scheduling information of the first channel includes at least one of the following: frequency domain resource assignment, time domain resource assignment, VRB-to-PRB mapping, modulation and coding scheme (MCS), New data indicator (NDI), Redundancy version (RV), or HARQ process number.

[0195] As an example, the second message is not a paging message.

[0196] As an example, the logical channel of the second message is not PCCH.

[0197] As an example, the first signaling does not include a field used to indicate a short message.

[0198] As an example, the first signaling includes a DCI.

[0199] As an example, the first signaling is a DCI.

[0200] As one embodiment, the first signaling includes DCI Format 4_0; the first bearer is an MRB.

[0201] As one embodiment, the first signaling includes DCI Format 4_1; the first bearer is an MRB.

[0202] As one embodiment, the first signaling includes DCI Format 4_2; the first bearer is an MRB.

[0203] As one embodiment, the first signaling includes DCI format 1_0; the first bearer is a DRB.

[0204] As one embodiment, the first signaling includes DCI format 1_1; the first bearer is a DRB.

[0205] As one embodiment, the first signaling includes DCI format 1_2; the first bearer is a DRB.

[0206] As an example, the first signaling is a DCI scrambled by the first RNTI.

[0207] As an example, the first signaling is a DCI scrambled by the first RNTI with a CRC.

[0208] As an example, the first signaling is scrambled by the first RNTI.

[0209] As an example, the second message is an AS message.

[0210] As one example, the second message is a higher-level message.

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

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

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

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

[0215] As an example, the second message is a MAC CE (Control Element).

[0216] As an example, the second message is a MAC subheader.

[0217] As an example, the second message is a MAC domain in a MAC CE.

[0218] As an example, the second message is a MAC field in a MAC subheader.

[0219] As one example, the first bearer is a DRB.

[0220] As a sub-implementation of this embodiment, the second message is transmitted via SRB0.

[0221] As a sub-implementation of this embodiment, the second message is transmitted via SRB1.

[0222] As a sub-implementation of this embodiment, the second message is transmitted via SRB2.

[0223] As a sub-implementation of this embodiment, the second message is transmitted via a new SRB.

[0224] As a sub-implementation of this embodiment, the second message is transmitted via DRB.

[0225] As a sub-implementation of this embodiment, the logical channel of the second message is CCCH.

[0226] As a sub-implementation of this embodiment, the logical channel of the second message is DCCH.

[0227] As a sub-implementation of this embodiment, the logical channel of the second message is DTCH (Dedicated Traffic Channel).

[0228] As a sub-implementation of this embodiment, the recipient of the second message includes only the first node.

[0229] As an example, the first bearer is an MRB.

[0230] As a sub-implementation of this embodiment, the second message is transmitted via MRB.

[0231] As a sub-implementation of this embodiment, the second message is transmitted via multicast MRB.

[0232] As a sub-example of this embodiment, the second message is transmitted via broadcast MRB.

[0233] As a sub-example of this embodiment, the logical channel of the second message is MCCH (MBS Control Channel).

[0234] As a sub-example of this embodiment, the logical channel of the second message is MTCH (MBS Traffic Channel, MBS Service Channel).

[0235] As a sub-implementation of this embodiment, the recipient of the second message includes at least the first node.

[0236] As a sub-example of this embodiment, the recipients of the second message include the first node and other nodes.

[0237] As an example, if the second bearer is a first-class DRB, the phrase transmitting data through the second bearer means performing SDT in the RRC inactive state.

[0238] As an example, if the second bearer is a first-class DRB, the phrase transmitting data through the second bearer means performing MT-SDT in the RRC inactive state.

[0239] As an example, if the second bearer is a first-class DRB, the phrase transmitting data through the second bearer means performing MO-SDT in the RRC inactive state.

[0240] As an example, if the second bearer is a first-class DRB, the phrase transmitting data through the second bearer means receiving downlink data in the RRC connection state.

[0241] As an example, if the second bearer is a first-class MRB, the phrase transmitting data through the second bearer means receiving an MBS in the RRC inactive state.

[0242] As one embodiment, the phrase "the second message is used to trigger data transmission via the second bearer" can be replaced with: "the second message is used to trigger data transmission via the second bearer in the RRC connection state".

[0243] As one embodiment, the phrase "the second message is used to trigger the transmission of data through the second bearer" can be replaced with: "the second message is used to trigger the transmission of data through the second bearer in the RRC inactive state".

[0244] As one embodiment, the phrase "the second message is used to trigger data transmission via the second bearer" can be replaced with: "the second message is used to trigger an RRC connection recovery process, which is used to transmit data via the second bearer in the RRC inactive state."

[0245] As one embodiment, the phrase "the second message is used to trigger data transmission through the second bearer" can be replaced with: "the second message is used to trigger an RRC connection recovery process, which is used to transmit data through the second bearer in the RRC connection state."

[0246] As one embodiment, the phrase "the second message is used to trigger the transmission of data through the second bearer" can be replaced with: "the second message is used to trigger an RRC recovery process, which is used to switch from the RRC inactive state to the RRC connected state."

[0247] As one example, in response to receiving the second message, data is transmitted via the second bearer in the RRC connection state.

[0248] As an example, in response to receiving the second message, the RRC inactive state transmits data via the second bearer.

[0249] As an example, the MRB includes a multicast MRB.

[0250] As an example, the MRB includes a broadcast MRB.

[0251] As an example, the MRB includes only multicast MRBs and excludes broadcast MRBs.

[0252] As an example, the first bearer is configured in an RRC connection state.

[0253] As one embodiment, the second bearer is configured in an RRC connection state.

[0254] As an example, the first bearer is configured in an RRC inactive state.

[0255] As one embodiment, the second bearer is configured in an RRC inactive state.

[0256] As one embodiment, the first bearer is an MRB and the second bearer is a DRB.

[0257] As one embodiment, the first bearer is a DRB and the second bearer is an MRB.

[0258] As one embodiment, the first bearer is a bearer identified by MRB-Identity, and the second bearer is a bearer identified by DRB-Identity.

[0259] As one embodiment, the first bearer is a bearer identified by DRB-Identity, and the second bearer is a bearer identified by MRB-Identity.

[0260] As an example, the MRB-Identity is used to identify a multicast MRB.

[0261] As an example, the MRB-Identity is used to identify a broadcast MRB.

[0262] As an example, the DRB-Identity is used to identify a DRB.

[0263] As an example, the DRB-Identity is an integer not less than 1 and not greater than 32.

[0264] As an example, the MRB-Identity is an integer not less than 1 and not greater than 32.

[0265] As an example, the DRB-Identity is an integer not less than 1 and not greater than 64.

[0266] As an example, the MRB-Identity is an integer not less than 1 and not greater than 64.

[0267] As an example, the DRB-Identity is an integer not less than 1 and not greater than 16.

[0268] As an example, the MRB-Identity is an integer not less than 1 and not greater than 16.

[0269] As one embodiment, the first bearer is a Class I DRB, and the second bearer is a Class I MRB.

[0270] As one embodiment, the first bearer is a Class I MRB, and the second bearer is a Class I DRB.

[0271] As an example, the first type of DRB is a DRB.

[0272] As an example, the first type of DRB is a DRB that can be used in SDT.

[0273] As an example, the first type of DRB is a DRB that can be used in MT-SDT.

[0274] As an example, the first type of DRB is a DRB that can be used in MO-SDT.

[0275] As an example, the first type of DRB is a DRB that can be used to receive downlink data in an RRC inactive state.

[0276] As an example, the first type of DRB is a DRB that can be used to send uplink data or receive downlink data in an RRC inactive state.

[0277] As an example, the first type of MRB is an MRB.

[0278] As an example, the first type of MRB is an MRB that can be used to receive MBS in an RRC inactive state.

[0279] As an example, the CRC of the first signaling is scrambled by the first RNTI.

[0280] As an example, the first signaling is indicated by the first RNTI.

[0281] As an example, the first signaling is addressed to the first RNTI.

[0282] As an example, the phrase "the first RNTI is related to the first bearer" means that if the first bearer is an MRB, the first RNTI is an RNTI in a first set of candidate RNTIs, and if the first bearer is a DRB, the first RNTI is an RNTI in a second set of candidate RNTIs.

[0283] As an example, any RNTI in the first candidate RNTI set belongs to multiple cells.

[0284] As an example, any RNTI in the first candidate RNTI set belongs to a cell.

[0285] As an example, any RNTI in the first candidate RNTI set is valid within a cell.

[0286] As an example, any RNTI in the first candidate RNTI set is associated with MBS.

[0287] As an example, any RNTI in the first candidate RNTI set is used to receive MBS scheduling.

[0288] As an example, any RNTI in the first candidate RNTI set is used to monitor MBS scheduling.

[0289] As an example, any RNTI in the first candidate RNTI set is used for broadcast PDSCH scheduling.

[0290] As an example, any RNTI in the first candidate RNTI set is used to scramble the CRC of the physical layer scheduling information of the MBS.

[0291] As an example, any RNTI in the second candidate RNTI set is used to receive SDT scheduling.

[0292] As an example, any RNTI in the second candidate RNTI set is used to monitor MT-SDT scheduling.

[0293] As an example, any RNTI in the second candidate RNTI set is used to monitor MO-SDT scheduling.

[0294] As an example, any RNTI in the second candidate RNTI set is used for PDSCH scheduling.

[0295] As an example, any RNTI in the second candidate RNTI set is used for PUSCH scheduling.

[0296] As an example, any RNTI in the second candidate RNTI set is used to scramble the CRC of the physical layer scheduling information of the SDT.

[0297] As an example, any RNTI in the second candidate RNTI set is used for PDSCH scheduling or PDSCH scheduling.

[0298] As an example, the first candidate RNTI set includes G-RNTIs.

[0299] As an example, the first candidate RNTI set includes MCCH-RNTI.

[0300] As an example, the first candidate RNTI set includes G-CS-RNTI.

[0301] As an example, the first candidate RNTI set includes only G-RNTIs.

[0302] As an example, the first candidate RNTI set includes at least one RNTI other than a G-RNTI.

[0303] As an example, the first candidate RNTI set includes at least one G-RNTI.

[0304] As an example, the first candidate RNTI set includes only one G-RNTI.

[0305] As an example, the first candidate RNTI set includes one or more G-RNTIs.

[0306] As an example, the first candidate RNTI set does not include MCCH-RNTI.

[0307] As an example, the first candidate RNTI set does not include P-RNTIs.

[0308] As an example, the first candidate RNTI set does not include SI-RNTI (System RNTI).

[0309] As an example, the first candidate RNTI set does not include RA-RNTI (Random Access RNTI).

[0310] As an example, the first candidate RNTI set does not include MsgB-RNTI.

[0311] As an example, the first candidate RNTI set includes MsgB-RNTI.

[0312] As an example, the G-RNTI is configured by MBS-SessionInfo.

[0313] As an example, the G-RNTI is configured by G-RNTI-Config.

[0314] As an example, the G-RNTI is configured with G-CS-RNTI.

[0315] As an example, the second candidate RNTI set includes C-RNTIs.

[0316] As an example, the second candidate RNTI set includes CS-RNTI.

[0317] As an example, the second candidate RNTI set includes MCS-C-RNTI.

[0318] As an example, the second candidate RNTI set includes MsgB-RNTI.

[0319] As an example, the second candidate RNTI set includes TC-RNTI.

[0320] As an example, the second candidate RNTI set includes CG-RNTI.

[0321] As an example, the second candidate RNTI set includes only C-RNTIs.

[0322] As an example, the second candidate RNTI set includes at least one RNTI other than a C-RNTI.

[0323] As an example, the second candidate RNTI set does not include P-RNTIs.

[0324] As an example, the second candidate RNTI set does not include SI-RNTI.

[0325] As an example, the second candidate RNTI set does not include RA-RNTI.

[0326] As an example, the second candidate RNTI set does not include MsgB-RNTI.

[0327] Example 2

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

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

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

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

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

[0333] As an example, node 203 is a base transceiver station (BTS).

[0334] As an example, node 203 is a node B (NodeB, NB).

[0335] As an example, node 203 is a gNB.

[0336] As an example, node 203 is an eNB.

[0337] As an example, node 203 is an ng-eNB.

[0338] As an example, node 203 is an en-gNB.

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

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

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

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

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

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

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

[0346] As one embodiment, the user equipment includes a mobile terminal, or the user equipment includes an aircraft, or the user equipment includes a vehicle-mounted terminal, or the user equipment includes a ship, or the user equipment includes an Internet of Things (IoT) terminal, or the user equipment includes an Industrial Internet of Things (IIoT) terminal, or the user equipment includes a device supporting low-latency, high-reliability transmission, or the user equipment includes testing equipment, or the user equipment includes a signaling tester.

[0347] As one embodiment, the base station device is a BS, or the base station device is a Base Transceiver Station (BTS), or the base station device is a NodeB (NB), or the base station device is a gNB, or the base station device is an eNB, or the base station device is an ng-eNB, or the base station device is an en-gNB.

[0348] As one embodiment, the base station equipment includes testing equipment, or the base station equipment includes a signaling tester, or the base station equipment includes satellite equipment, or the base station equipment includes flight platform equipment, or the base station equipment includes a macrocell base station, or the base station equipment includes a microcell base station, or the base station equipment includes a picocell base station, or the base station equipment includes a femtocell.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0368] Example 3

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

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

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

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

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

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

[0375] As an example, the first signaling in this application is generated in the PHY301 or PHY351.

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

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

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

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

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

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

[0382] As an example, the fourth message in this application is generated in the RRC306.

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

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

[0385] Example 4

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

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

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

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

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

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

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

[0393] As one embodiment, the first communication device 450 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used with the at least one processor, and the first communication device 450 at least: receives a first message, the first message indicating at least a first bearer; in response to receiving the first message, enters or remains in an RRC inactive state; during data transmission through the first bearer in the RRC inactive state, receives a first signaling and a second message, the first signaling including scheduling information for a first channel, at least the second message being transmitted on the first channel, the second message being used to trigger data transmission through a second bearer; wherein, one of the first bearer and the second bearer is an MRB, and the other is a DRB; the first signaling is scrambled by a first RNTI; the first RNTI is associated with the first bearer; if the first bearer is an MRB, the first RNTI is an RNTI in a first candidate RNTI set, and if the first bearer is a DRB, the first RNTI is an RNTI in a second candidate RNTI set; the first candidate RNTI set includes at least a G-RNTI; the second candidate RNTI set includes at least a C-RNTI.

[0394] As one embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program that, when executed by at least one processor, produces actions including: receiving a first message indicating at least a first bearer; entering or remaining in an RRC inactive state in response to receiving the first message; and receiving a first signaling and a second message during data transmission through the first bearer in the RRC inactive state, the first signaling including scheduling information for a first channel, the second message being transmitted on the first channel at least once, and the second message being used to trigger data transmission through a second bearer; wherein one of the first bearer and the second bearer is an MRB and the other is a DRB; the first signaling is scrambled by a first RNTI; the first RNTI is associated with the first bearer; if the first bearer is an MRB, the first RNTI is an RNTI in a first set of candidate RNTIs, and if the first bearer is a DRB, the first RNTI is an RNTI in a second set of candidate RNTIs; the first set of candidate RNTIs includes at least G-RNTIs; and the second set of candidate RNTIs includes at least C-RNTIs.

[0395] As one embodiment, the second communication device 410 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used with the at least one processor. The second communication device 410 at least: sends a first message, the first message indicating at least a first bearer; sends a first signaling and a second message, the first signaling including scheduling information for a first channel, the second message being sent on the first channel at least, the second message being used to trigger data transmission via a second bearer; wherein, in response to the reception of the first message, the receiver of the first message enters or remains in an RRC inactive state; the first signaling and the second message are received by the receiver of the first message during data transmission via the first bearer in the RRC inactive state; one of the first bearer and the second bearer is an MRB, and the other is a DRB; the first signaling is scrambled with a first RNTI; the first RNTI is associated with the first bearer; if the first bearer is an MRB, the first RNTI is an RNTI in a first candidate RNTI set, and if the first bearer is a DRB, the first RNTI is an RNTI in a second candidate RNTI set; the first candidate RNTI set includes at least a G-RNTI; the second candidate RNTI set includes at least a C-RNTI.

[0396] As one embodiment, the second communication device 410 includes: a memory storing a computer-readable instruction program that, when executed by at least one processor, produces actions including: sending a first message indicating at least a first bearer; sending a first signaling and a second message, the first signaling including scheduling information for a first channel, at least the second message being sent on the first channel, the second message being used to trigger data transmission via a second bearer; wherein, in response to the first message being received, the receiver of the first message enters or remains in an RRC inactive state; the first signaling and the second message are received by the receiver of the first message during data transmission via the first bearer in the RRC inactive state; one of the first bearer and the second bearer is an MRB, and the other is a DRB; the first signaling is scrambled with a first RNTI; the first RNTI is associated with the first bearer; if the first bearer is an MRB, the first RNTI is an RNTI in a first candidate RNTI set, and if the first bearer is a DRB, the first RNTI is an RNTI in a second candidate RNTI set; the first candidate RNTI set includes at least G-RNTIs; the second candidate RNTI set includes at least C-RNTIs.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0417] Example 5

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

[0419] for First node U01In step S5101, a first message is received, indicating at least a first bearer; in step S5102, in response to receiving the first message, an RRC inactive state is entered or maintained; in step S5103, data is transmitted through the first bearer in the RRC inactive state; in step S5104, during data transmission through the first bearer in the RRC inactive state, a first signaling is received; in step S5105, during data transmission through the first bearer in the RRC inactive state, a second message is received; in step S5106, in response to receiving the second message, a third message is sent, the third message being used in the RRC connection recovery process; in step S5107, in response to the sending of the third message, a fourth message is monitored; in step S5108, the fourth message is received; in step S5109, the second bearer is restored along with the RRC connection recovery process; in step S5110, data is transmitted through the second bearer.

[0420] for Second node N02 In step S5201, the first message is sent; in step S5202, the first signaling is sent; in step S5203, the second message is sent; in step S5204, the third message is sent; and in step S5205, the fourth message is sent.

[0421] In embodiment 5, the first signaling includes scheduling information for a first channel, at least the second message is sent on the first channel, and the second message is used to trigger data transmission through a second bearer; one of the first bearer and the second bearer is an MRB, and the other is a DRB; the first signaling is scrambled by a first RNTI; the first RNTI is related to the first bearer; if the first bearer is an MRB, the first RNTI is an RNTI in a first candidate RNTI set; if the first bearer is a DRB, the first RNTI is an RNTI in a second candidate RNTI set; the first candidate RNTI set includes at least a G-RNTI; the second candidate RNTI set includes at least a C-RNTI; the fourth message belongs to the RRC connection recovery process.

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

[0423] As an example, the first node U01 is a terminal.

[0424] As an example, the first node U01 is a test device.

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

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

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

[0428] As an example, the second node N02 is an IAB node.

[0429] As an example, the recipient of the third message is the same as the sender of the first signaling.

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

[0431] As an example, the third message includes an RRC message.

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

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

[0434] As an example, the third message is downlink signaling.

[0435] As an example, the third message includes either the RRCResumeRequest message or the RRCResumeRequest1 message.

[0436] As an example, the third message includes an RRCConnectionResumeRequest message or an RRCEarlyDataRequest message.

[0437] As an example, the logical channel of the third message is CCCH.

[0438] As an example, the logical channel of the third message is DCCH.

[0439] As an example, the signaling radio bearer of the third message is SRB0.

[0440] As an example, the signaling radio bearer of the third message is SRB1.

[0441] As an example, the signaling radio bearer of the third message is SRB2.

[0442] As an example, the third message is used to notify the second node N02 to transmit data through the second bearer.

[0443] As an example, the third message is used to determine whether data is transmitted via the second bearer.

[0444] As one example, in response to receiving the second message, the second bearer is restored.

[0445] As one embodiment, in response to receiving the second message, an RRC connection recovery process is initiated; during the RRC connection recovery process, a third message is sent.

[0446] As an example, in response to receiving the second message, an RRC connection recovery process is initiated, and resumeCause is set to the first string.

[0447] As a sub-implementation of this embodiment, the name of the first string includes at least one of MT, mt, SDT, sdt, inactive, data, or transmission.

[0448] As a sub-implementation of this embodiment, the first string includes MT-SDT.

[0449] As a sub-implementation of this embodiment, the first string includes mt-sdt.

[0450] As an example, in response to receiving the second message, an RRC connection recovery process is initiated, and resumeCause is set to the second string.

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

[0452] As a sub-example of this embodiment, the second string is mps-PriorityAccess.

[0453] As a sub-example of this embodiment, the second string is mcs-PriorityAccess.

[0454] As a sub-implementation of this embodiment, the second string is highPriorityAccess.

[0455] As a sub-implementation of this embodiment, the second string is mt-Access.

[0456] As an example, if resumeCause is set to the first string, the second bearer is restored in the RRC inactive state.

[0457] As an example, if resumeCause is set to the second string, the second bearer is restored only upon receiving an RRCResume message.

[0458] As an example, the fourth message is downlink signaling.

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

[0460] As an example, the fourth message includes an RRC message.

[0461] As an example, the logical channel of the fourth message is CCCH.

[0462] As an example, the logical channel of the fourth message is DCCH.

[0463] As an example, the signaling radio bearer of the fourth message is SRB0.

[0464] As an example, the signaling radio bearer of the fourth message is SRB1.

[0465] As an example, the signaling radio bearer of the fourth message is SRB2.

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

[0467] As an example, the fourth message is triggered by the third message.

[0468] As an example, both the fourth message and the third message belong to the RRC connection recovery process.

[0469] As one embodiment, the behavior of listening to the fourth message includes: determining whether the fourth message has been received by listening to the PDCCH.

[0470] As one embodiment, the behavior of listening to the fourth message includes: determining at the RRC layer whether the fourth message has been received.

[0471] As one embodiment, the behavior of listening to the fourth message includes: determining whether the fourth message has been received.

[0472] As one embodiment, the behavior monitoring of the fourth message includes: detecting the fourth message.

[0473] As an example, the sentence "During the RRC connection recovery process, the second bearer is restored" includes: During the RRC connection recovery process, the second bearer is restored.

[0474] As an example, the sentence "Restore the second bearer during the RRC connection recovery process" includes: "Restore the second bearer during the third message."

[0475] As a sub-implementation of this embodiment, the fourth message includes one of the following: RRCRelease message, RRCResume message, RRCReject message, or RRCSetup message.

[0476] As a sub-implementation of this embodiment, the fourth message includes one of the following: RRCConnectionResume message, RRCCEarlyDataComplete message, RRCConnectionReject message, RRCConnectionSetup message, or RRCConnectionRelease message.

[0477] As a sub-example of this embodiment, during the time interval between the sending of the third message and the receiving of the fourth message, the first node U01 receives at least one downlink data through the first bearer.

[0478] As a sub-example of this embodiment, during the time interval between the sending of the third message and the receiving of the fourth message, the first node U01 sends at least one downlink data through the first bearer.

[0479] As a sub-implementation of this embodiment, the second bearer is restored after the third message is set and before the third message is delivered to a lower layer.

[0480] As a sub-implementation of this embodiment, the second bearer is restored after the third message is set and before the third message is sent.

[0481] As a sub-implementation of this embodiment, the second bearer is restored in response to the sending of the third message.

[0482] As a sub-implementation of this embodiment, the second bearer is restored just before the third message is sent.

[0483] As a sub-implementation of this embodiment, the second bearer is restored after the third message is sent and before the fourth message is received.

[0484] As a sub-implementation of this embodiment, after the third message is sent, the second bearer is restored in response to receiving a PDCCH scrambled by the first identifier.

[0485] As a sub-implementation of this embodiment, Msg3 is sent during random access, wherein Msg3 includes a CCCH SDU, and the CCCH SDU includes the third message; as a response to the sending of Msg3, UEContention Resolution Identity in the MAC CE is received, wherein UEContention Resolution Identity in the MAC CE includes at least a portion of the CCCH SDU; as a response to receiving the UEContention Resolution Identity in the MAC CE, the second bearer is restored.

[0486] As a sub-implementation of this embodiment, MsgA is sent during random access, wherein MsgA includes a CCCH SDU, and the CCCH SDU includes the third message; in response to the transmission of MsgA, MsgB is received, wherein MsgB includes a successRAR MAC subPDU, and the successRAR MAC subPDU includes at least a portion of the CCCH SDU; in response to receiving the UE Contention Resolution Identity in the MAC CE, the second bearer is restored.

[0487] As a sub-implementation of this embodiment, the third message is sent during the random access procedure; as a response to the successful completion of the random access procedure, the second bearer is restored.

[0488] As a sub-implementation of this embodiment, the third message is sent during the random access procedure; as a response to the successful completion of the random access procedure, the second bearer is restored.

[0489] As an example, the sentence "In conjunction with the RRC connection recovery process, the second bearer is restored" includes: In conjunction with the fourth message, the second bearer is restored.

[0490] As a sub-implementation of this embodiment, the fourth message includes the RRCResume message.

[0491] As a sub-implementation of this embodiment, the fourth message includes an RRCConnectionResume message or an RRCEarlyDataComplete message.

[0492] As a sub-implementation of this embodiment, within at least one time slot after the fourth message is received, the first node U01 receives at least one downlink data through the first bearer.

[0493] As a sub-implementation of this embodiment, within at least one time slot after the fourth message is received, the first node U01 transmits at least one downlink data through the first bearer.

[0494] As a sub-implementation of this embodiment, the second bearer is restored after the fourth message is received.

[0495] As a sub-implementation of this embodiment, in response to the receipt of the fourth message, the second bearer is restored.

[0496] As an example, if the second message indicates that data is being transmitted through the second bearer in the RRC inactive state, the second bearer is restored along with the third message.

[0497] As an example, if the second message indicates that data is being transmitted through the second bearer in the RRC inactive state, the second bearer is restored along with the fourth message.

[0498] As an example, if the second message indicates that data is transmitted through the second bearer in the RRC connection state, the second bearer is restored along with the fourth message.

[0499] As an example, step S5109 occurs before step S5106.

[0500] As an example, step S5109 is after step S5106 and before step S5107.

[0501] As an example, the dashed box F5.1 is optional.

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

[0503] As an example, the dashed box F5.1 does not exist.

[0504] As an example, the fourth message is received.

[0505] As an example, the fourth message was not received.

[0506] Example 6

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

[0508] for First node U01 In step S6101, a first message is received, the first message indicating at least a first bearer; in step S6102, in response to receiving the first message, entering or remaining in an RRC inactive state; in step S6103, data is transmitted through the first bearer in the RRC inactive state; in step S6104, during data transmission through the first bearer in the RRC inactive state, a first signaling is received; in step S6105, during data transmission through the first bearer in the RRC inactive state, a second message is received; in step S6106, in response to receiving the second message, the second bearer is restored; in step S6107, data is transmitted through the second bearer.

[0509] for Second node N02 In step S6201, the first message is sent; in step S6202, the first signaling is sent; and in step S6203, the second message is sent.

[0510] In embodiment 6, the first signaling includes scheduling information for a first channel, at least the second message is sent on the first channel, and the second message is used to trigger data transmission through a second bearer; one of the first bearer and the second bearer is an MRB, and the other is a DRB; the first signaling is scrambled by a first RNTI; the first RNTI is related to the first bearer; if the first bearer is an MRB, the first RNTI is an RNTI in a first candidate RNTI set; if the first bearer is a DRB, the first RNTI is an RNTI in a second candidate RNTI set; the first candidate RNTI set includes at least a G-RNTI; the second candidate RNTI set includes at least a C-RNTI; the action of receiving the second message does not trigger an RRC connection recovery process.

[0511] As an example, during the time interval between receiving the second message and restoring the second bearer, the first node U01 does not send an RRCResumeRequest message, or an RRCResumeRequest1 message, or an RRCConnectionResumeRequest message, or an RRCEarlyDataRequest message.

[0512] As an example, the behavior receives the second message as not triggering an RRCResumeRequest message, or an RRCResumeRequest1 message, or an RRCConnectionResumeRequest message, or an RRCEarlyDataRequest message.

[0513] As one embodiment, the action of receiving the second message is used to trigger the action to restore the second bearer.

[0514] As an example, after the second bearer is restored, at least one downlink data is received through the second bearer.

[0515] As an example, after the second bearer is restored, at least one downlink data is received through the second bearer in an RRC inactive state.

[0516] As one embodiment, the second bearer being restored is used to determine the data transmitted through the second bearer.

[0517] Example 7

[0518] Example 7 illustrates a schematic diagram of a first identity of a first node in a second message according to an embodiment of this application.

[0519] In Embodiment 7, the second message includes the first identity of the first node, which is unique within at least one cell; the first bearer is an MRB, and the first RNTI is an RNTI from the first set of candidate RNTIs.

[0520] As one embodiment, the first node receives a first message indicating at least a first bearer; in response to receiving the first message, it enters or remains in an RRC inactive state; during data transmission through the first bearer in the RRC inactive state, it receives a first signaling and a second message, the first signaling including scheduling information for a first channel, at least the second message being sent on the first channel, and the second message being used to trigger data transmission through a second bearer; wherein the second message includes a first identity of the first node, the first identity of the first node being unique within at least one cell; the first bearer is an MRB, and the second bearer is a DRB; the first signaling is scrambled with a first RNTI; the first RNTI is an RNTI in a first candidate RNTI set; the first candidate RNTI set includes at least a G-RNTI.

[0521] As an example, the first identity of the first node is used to identify the first node in the RRC inactive state.

[0522] As an example, the at least one cell may include only one cell.

[0523] As one example, the at least one cell includes one or more cells.

[0524] As an example, the at least one cell is a single cell.

[0525] As an example, the at least one cell is a RAN (Radio Access Network) notification area (RNA).

[0526] As an example, the at least one cell is a tracking area (TA).

[0527] As an example, the at least one cell is predefined.

[0528] As an example, the at least one cell is pre-configured.

[0529] As an example, the phrase "the first identity of the first node is unique in at least one cell" means that the first identity of the first node is not used by other user equipment in the at least one cell.

[0530] As an example, the phrase "the first identity of the first node is unique in at least one cell" means that in at least one cell, there is no user equipment with the same identity as the first identity of the first node.

[0531] As an example, the phrase "the first identity of the first node is unique within at least one cell" means that within the at least one cell, the first identity of the first node is uniquely identified as the first node.

[0532] As an example, the second message includes the identity of at least one user device, which is used to indicate a user device, the at least one user device including the first node.

[0533] As an example, the identity of a user equipment includes one of: NG-5G-S-TMSI, I-RNTI-Value, or ShortI-RNTI-Value.

[0534] As an example, the identity of a user equipment includes one of: S-TMSI (SAE (System Architecture Evolution) Temporary Mobile Station Identifier), NG-5G-S-TMSI-r15, or I-RNTI-r15.

[0535] As one example, the identity of a user equipment may include 40 bits, 48 ​​bits, 24 bits, or 16 bits.

[0536] As an example, the second message includes a PagingRecord field, which includes at least the former of a ue-Identity field and an accessType field; the ue-Identity field includes the first identity of the first node.

[0537] As an example, the second message includes a PagingRecord field, which includes at least the former of a ue-Identity field and an accessType field; the ue-Identity field includes a PagingUE-Identity field, which indicates the first identity of the first node.

[0538] As an example, the second message includes an RRC field, which includes the first identity of the first node.

[0539] As a sub-implementation of this embodiment, the name of the RRC field includes PagingUE-Identity.

[0540] As a sub-example of this embodiment, the name of the RRC field includes PagingRecord.

[0541] As a sub-implementation of this embodiment, the RRC field is the PagingUE-Identity field.

[0542] As a sub-implementation of this embodiment, the RRC field is a PagingRecord field.

[0543] As a sub-example of this embodiment, the RRC field indicates the first identity of the first node.

[0544] As a sub-example of this embodiment, the RRC domain is set as the first identity of the first node.

[0545] As an example, the first identity of the first node includes the NG-5G-S-TMSI of the first node.

[0546] As an example, the first identity of the first node includes the I-RNTI-Value of the first node.

[0547] As an example, the first identity of the first node includes the ShortI-RNTI-Value of the first node.

[0548] As an example, the first identity of the first node includes the S-TMSI of the first node.

[0549] As an example, the first identity of the first node includes the IMSI of the first node.

[0550] As an example, the first identity of the first node includes the NG-5G-S-TMSI-r15 of the first node.

[0551] As an example, the first identity of the first node includes the I-RNTI-r15 of the first node.

[0552] As an example, the first identity of the first node is used to identify the UE context of a user equipment in an RRC inactive state.

[0553] As one embodiment, the first identity of the first node includes a 5G S-Temporary Mobile Subscription Identifier (5G-S-TMSI), which is provided by 5GC, and the first identity of the first node is unique within the Tracking Area.

[0554] As an example, the first identity of the first node includes a bit string.

[0555] As an example, the first identity of the first node includes 40 bits.

[0556] As an example, the first identity of the first node includes 48 bits.

[0557] As an example, the first identity of the first node includes 24 bits.

[0558] As an example, the first identity of the first node includes 16 bits.

[0559] Example 8

[0560] Example 8 illustrates a schematic diagram of a second message including a second identity according to an embodiment of this application.

[0561] In embodiment 8, the second message includes a second identity, which is used to indicate a first MBS session, in which the first node participates in the first MBS session; the first bearer is a DRB, and the first RNTI is an RNTI in the second set of candidate RNTIs.

[0562] As one embodiment, the first node receives a first message indicating at least a first bearer; in response to receiving the first message, it enters or remains in an RRC inactive state; during data transmission through the first bearer in the RRC inactive state, it receives a first signaling and a second message, the first signaling including scheduling information for a first channel, at least the second message being sent on the first channel, and the second message being used to trigger data transmission through a second bearer; wherein the second message includes a second identity, the second identity being used to indicate a first MBS session, and the first node participating in the first MBS session; the first bearer is a DRB, and the second bearer is an MRB; the first signaling is scrambled by a first RNTI; the first RNTI is an RNTI in a second set of candidate RNTIs; the second set of candidate RNTIs includes at least a C-RNTI.

[0563] As an example, the first node determines that an MBS session is the first MBS session based on the second identity.

[0564] As one example, the second identity is the index of the first MBS session.

[0565] As an example, the second identity is the identity of the first MBS session.

[0566] As one example, the second identity is the identifier of the first MBS session.

[0567] As one example, the second identity is associated with the second bearer.

[0568] As an example, the second identity is associated with a G-RNTI.

[0569] As one embodiment, the second bearer is configured to be used to determine whether the first node participates in the first MBS session.

[0570] As an example, the first node sends an MBS-InterestIndication message to the second node, and the MBS-InterestIndication message includes the second identity, which is used to determine that the first node participates in the first MBS session.

[0571] As an example, the second identity is TMGI (Temporary Mobile Group Identity).

[0572] As an example, the TMGI includes plmn-Id and serviceId.

[0573] As one example, the second identity indicates a PLMN (Public Land Mobile Network).

[0574] As an example, the second identity indicates an index of a PLMN.

[0575] As one example, the second identity indicates a service identifier (serviceId).

[0576] As an example, the MBS data.

[0577] As an example, the first MBS session is an MBS broadcast session.

[0578] As an example, the first MBS session is an MBS multicast session.

[0579] As an example, the first MBS session is directed to at least one user device.

[0580] As one example, the first MBS session is for one or more user devices.

[0581] As an example, the first MBS session is for a group of user devices.

[0582] As one example, the first MBS session is for a group of user equipment participating in the first MBS session.

[0583] As an example, the first MBS session is associated with a G-RNTI.

[0584] As an example, the second identity is the identity of the first MBS session.

[0585] As one example, the second identity is the identifier of the first MBS session.

[0586] As an example, the first node determines the first MBS session based on the second identity.

[0587] As one embodiment, the second bearer is configured to instruct the first node to participate in the first MBS session.

[0588] As one embodiment, the second bearer is used to instruct the first node to participate in the first MBS session.

[0589] As an example, the second message includes an RRC field, the name of which includes pagingGroupList; the RRC field includes the second identity.

[0590] As an example, the second message includes an RRC field, and the RRC field includes the second identity.

[0591] As a sub-example of this embodiment, the name of the RRC field includes PagingGroupList.

[0592] As a sub-example of this embodiment, the name of the RRC field includes TMGI.

[0593] As a sub-implementation of this embodiment, the name of the RRC field includes at least one of TMGI or List.

[0594] As a sub-implementation of this embodiment, the name of the RRC field includes at least one of MBS, Session, or List.

[0595] As a sub-implementation of this embodiment, the name of the RRC field includes at least one of Group or List.

[0596] As a sub-implementation of this embodiment, the name of the RRC field includes MBS-SessionInfoList.

[0597] As one embodiment, the second message includes M1 TMGIs, which are associated with N1 first-class MRBs; in response to receiving the second message, the N1 first-class MRBs are restored; the second bearer is one of the N1 first-class MRBs.

[0598] As a sub-example of this embodiment, M1 is equal to N1.

[0599] As a sub-example of this embodiment, M1 is not equal to N1.

[0600] As a sub-example of this embodiment, any two TMGIs among the M1 TMGIs are associated with two different first-class MRBs among the N1 first-class MRBs.

[0601] As a sub-example of this embodiment, any two of the N1 first-class MRBs are associated with two different TMGIs among the M1 TMGIs.

[0602] As a sub-implementation of this embodiment, there is a one-to-one correspondence between a first-class MRB and a TMGI.

[0603] Example 9

[0604] Example 9 illustrates a schematic diagram of a second message indicating data transmission via a second bearer in an RRC inactive state according to an embodiment of this application, as shown in the attached diagram. Figure 9 As shown.

[0605] In Example 9, the second message indicates that data is transmitted via the second bearer in the RRC inactive state.

[0606] As an example, the phrase "the second message is used to trigger data transmission via the second bearer" means that the second message is used to trigger data transmission via the second bearer in the RRC inactive state.

[0607] As an example, if the second message indicates that data is transmitted through the second bearer in the RRC inactive state, the second bearer is restored in response to receiving the second message; the action of receiving the second message does not trigger the RRC connection restoration process.

[0608] As an example, the second message indicates that data is transmitted via the second bearer during the RRC inactive state.

[0609] As an example, the second message implicitly indicates that data is transmitted via the second bearer during the RRC inactive state.

[0610] Example 10

[0611] Example 10 illustrates a schematic diagram of a second message indicating data transmission via a second bearer in an RRC connection state according to an embodiment of this application, as shown in the attached diagram. Figure 10 As shown.

[0612] In Embodiment 10, the second message indicates that data is transmitted through the second bearer in the RRC connection state.

[0613] As an example, the phrase "the second message is used to trigger data transmission via the second bearer" means that the second message is used to trigger data transmission via the second bearer in the RRC connection state.

[0614] As one embodiment, if the second message indicates that data is transmitted through the second bearer in the RRC connection state, a third message is sent in response to receiving the second message, and the third message is used in the RRC connection recovery process; in response to the sending of the third message, a fourth message is monitored; the second bearer is restored along with the RRC connection recovery process; the fourth message belongs to the RRC connection recovery process.

[0615] As one embodiment, the phrase "the second message indicates that data is transmitted through the second bearer in the RRC connected state" includes: in response to receiving the second message, switching from the RRC inactive state to the RRC connected state, and then transmitting data through the second bearer.

[0616] As one embodiment, in response to receiving the fourth message, the second bearer is restored; wherein the fourth message is an RRCResume message.

[0617] As an example, the second bearer is restored after the fourth message is received.

[0618] As an example, the second message indicates that data is transmitted through the second bearer in the RRC connection state.

[0619] As an example, the second message implicitly indicates that data is transmitted through the second bearer in the RRC connection state.

[0620] Example 11

[0621] Example 11 illustrates a structural block diagram of a processing apparatus for a first node according to an embodiment of this application; as shown in the appendix. Figure 11 As shown. In the appendix Figure 11 In the first node, the processing device 1100 includes a first receiver 1101 and a first transmitter 1102.

[0622] A first receiver 1101 receives a first message indicating at least a first bearer; in response to receiving the first message, it enters or remains in an RRC inactive state; during data transmission through the first bearer in the RRC inactive state, it receives a first signaling and a second message, the first signaling including scheduling information for a first channel, at least the second message being transmitted on the first channel, and the second message being used to trigger data transmission through a second bearer.

[0623] In Example 11, one of the first bearer and the second bearer is an MRB, and the other is a DRB; the first signaling is scrambled by a first RNTI; the first RNTI is related to the first bearer; if the first bearer is an MRB, the first RNTI is an RNTI in a first candidate RNTI set; if the first bearer is a DRB, the first RNTI is an RNTI in a second candidate RNTI set; the first candidate RNTI set includes at least a G-RNTI; the second candidate RNTI set includes at least a C-RNTI.

[0624] As one embodiment, a first transmitter 1102 sends a third message in response to receiving the second message, the third message being used in the RRC connection recovery process; a first receiver 1101 monitors a fourth message in response to the sending of the third message; and a first processor restores the second bearer in conjunction with the RRC connection recovery process; wherein the fourth message is part of the RRC connection recovery process.

[0625] As one embodiment, the first processor is the first receiver 1101.

[0626] As an example, the first processor is the first transmitter 1102.

[0627] As one embodiment, the first processor includes at least one of the first receiver 1101 or the first transmitter 1102.

[0628] As one embodiment, the first receiver 1101, in response to receiving the second message, restores the second bearer; the action of receiving the second message does not trigger the RRC connection restoration process.

[0629] As an example, the second message includes the first identity of the first node, which is unique within at least one cell; the first bearer is an MRB, and the first RNTI is an RNTI from the first set of candidate RNTIs.

[0630] As one embodiment, the second message includes a second identity, which is used to indicate a first MBS session, in which the first node participates in the first MBS session; the first bearer is a DRB, and the first RNTI is an RNTI in the second set of candidate RNTIs.

[0631] As one example, the second message indicates that data is transmitted via the second bearer during the RRC inactive state.

[0632] As one example, the second message indicates that data is transmitted through the second bearer in the RRC connection state.

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

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

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

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

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

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

[0639] Example 12

[0640] Example 12 illustrates a structural block diagram of a processing apparatus for a second node according to an embodiment of this application; as shown in the appendix. Figure 12 As shown. In the appendix Figure 12 In the second node, the processing device 1200 includes a second transmitter 1201 and a second receiver 1202.

[0641] The second transmitter 1201 sends a first message indicating at least a first bearer; sends a first signaling and a second message, the first signaling including scheduling information of a first channel, at least the second message being sent on the first channel, and the second message being used to trigger data transmission through the second bearer;

[0642] In Example 12, in response to the receipt of the first message, the receiver of the first message enters or remains in an RRC inactive state; the first signaling and the second message are received by the receiver of the first message during data transmission via the first bearer in the RRC inactive state; one of the first bearer and the second bearer is an MRB, and the other is a DRB; the first signaling is scrambled by a first RNTI; the first RNTI is associated with the first bearer; if the first bearer is an MRB, the first RNTI is an RNTI in a first candidate RNTI set; if the first bearer is a DRB, the first RNTI is an RNTI in a second candidate RNTI set; the first candidate RNTI set includes at least G-RNTIs; the second candidate RNTI set includes at least C-RNTIs.

[0643] As one embodiment, the second receiver 1202 receives a third message, which is used in the RRC connection recovery process; the second transmitter 1201, in response to the receipt of the third message, determines whether to send a fourth message; wherein, the second bearer is restored along with the RRC connection recovery process; the fourth message belongs to the RRC connection recovery process; the second message is used to trigger the third message.

[0644] As one example, the second bearer is restored in response to the second message being received by the recipient of the first message; the receipt of the second message by the recipient of the first message does not trigger the RRC connection restoration process.

[0645] As an example, the second message includes the first identity of the recipient of the first message, which is unique within at least one cell; the first bearer is an MRB, and the first RNTI is an RNTI in the first set of candidate RNTIs.

[0646] As one embodiment, the second message includes a second identity, which is used to indicate a first MBS session, and the recipient of the first message participates in the first MBS session; the first bearer is a DRB, and the first RNTI is an RNTI in the second set of candidate RNTIs.

[0647] As one example, the second message indicates that data is transmitted via the second bearer during the RRC inactive state.

[0648] As one example, the second message indicates that data is transmitted through the second bearer in the RRC connection state.

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

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

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

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

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

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

[0655] Example 13

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

[0657] In Embodiment 13, the first node in this application receives a first message in step 1301, the first message indicating at least a first bearer; in step 1302, in response to receiving the first message, enters or remains in an RRC inactive state; in step 1303, during data transmission through the first bearer in the RRC inactive state, receives a first signaling, the first signaling being used to trigger data transmission through a second bearer; wherein, one of the first bearer and the second bearer is an MRB, and the other is a DRB; the first signaling is scrambled by a first RNTI; the first RNTI is associated with the first bearer; if the first bearer is an MRB, the first RNTI is an RNTI in a first candidate RNTI set; if the first bearer is a DRB, the first RNTI is an RNTI in a second candidate RNTI set; the first candidate RNTI set includes at least a G-RNTI; the second candidate RNTI set includes at least a C-RNTI.

[0658] As one embodiment, the first signaling includes scheduling information for a first channel, and at least a second message is transmitted on the first channel.

[0659] As an example, the first channel is PUSCH.

[0660] As an example, the first channel is PDSCH.

[0661] As an example, the first signaling is a field in DCI.

[0662] As an example, the first signaling is a DCI.

[0663] As one embodiment, the first signaling indicates that data is transmitted through the second bearer.

[0664] As one embodiment, the first signaling indicates that data is transmitted via the second bearer in an RRC inactive state.

[0665] As one embodiment, the first signaling indicates that data is transmitted through the second bearer in the RRC connection state.

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

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

Claims

1. A first node configured for wireless communication, the first node comprising: include: A first receiver receives a first message, the first message indicating at least a first bearer; In response to receiving the first message, enter or remain in the RRC inactive state; During the transmission of data through the first bearer in the RRC inactive state, a first signaling and a second message are received. The first signaling includes scheduling information for the first channel, and at least the second message is sent on the first channel. The second message is used to trigger the transmission of data through the second bearer. Wherein, one of the first bearer and the second bearer is an MRB, and the other is a DRB; the first signaling is scrambled by the first RNTI; The first RNTI is related to the first bearer; if the first bearer is an MRB, the first RNTI is an RNTI in a first candidate RNTI set; if the first bearer is a DRB, the first RNTI is an RNTI in a second candidate RNTI set; the first candidate RNTI set includes at least G-RNTIs; the second candidate RNTI set includes at least C-RNTIs.

2. The first node of claim 1, characterized in that, include: The first transmitter, in response to receiving the second message, sends a third message, which is used in the RRC connection recovery process; The first receiver, in response to the transmission of the third message, monitors the fourth message; The first processor, during the RRC connection recovery process, restores the second bearer; The fourth message belongs to the RRC connection recovery process.

3. The first node of claim 1, wherein, include: In response to receiving the second message, the first receiver restores the second bearer; Receiving the second message did not trigger the RRC connection recovery process.

4. The first node of any of claims 1 to 3, wherein, The second message includes the first identity of the first node, which is unique within at least one cell; the first bearer is an MRB, and the first RNTI is an RNTI from the first set of candidate RNTIs.

5. The first node of any of claims 1 to 3, wherein, The second message includes a second identity, which is used to indicate the first MBS session in which the first node participates; the first bearer is a DRB, and the first RNTI is an RNTI in the second set of candidate RNTIs.

6. The first node of claim 1, wherein, The second message indicates that data is transmitted via the second bearer during the RRC inactive state.

7. The first node of claim 1, wherein, The second message indicates that data is transmitted through the second bearer in the RRC connection state.

8. A second node configured for wireless communication, the second node comprising: include: The second transmitter sends a first message, the first message indicating at least the first bearer; Send a first signaling message and a second message, wherein the first signaling message includes scheduling information for a first channel, and at least the second message is sent on the first channel, and the second message is used to trigger data transmission through a second bearer; In response to the receipt of the first message, the recipient of the first message enters or remains in an RRC inactive state; the first signaling and the second message are received by the recipient of the first message during data transmission via the first bearer in the RRC inactive state; one of the first bearer and the second bearer is an MRB and the other is a DRB; the first signaling is scrambled by a first RNTI. The first RNTI is related to the first bearer; if the first bearer is an MRB, the first RNTI is an RNTI in a first candidate RNTI set; if the first bearer is a DRB, the first RNTI is an RNTI in a second candidate RNTI set; the first candidate RNTI set includes at least G-RNTIs; the second candidate RNTI set includes at least C-RNTIs.

9. The second node according to claim 8, characterized in that, The second receiver receives the third message, which is used in the RRC connection recovery process. The second transmitter, in response to the receipt of the third message, determines whether to send a fourth message; During the RRC connection recovery process, the second bearer is restored; the fourth message belongs to the RRC connection recovery process; the second message is used to trigger the third message.

10. The second node according to claim 8 or 9, characterized in that, As a response to the second message being received by the recipient of the first message, the second bearer is restored; the receipt of the second message by the recipient of the first message does not trigger the RRC connection restoration process.

11. The second node according to claim 8, characterized in that, The second message includes the first identity of the recipient of the first message, which is unique within at least one cell; the first bearer is an MRB, and the first RNTI is an RNTI in the first set of candidate RNTIs.

12. The second node according to claim 8, characterized in that, The second message includes a second identity, which is used to indicate the first MBS session, and the recipient of the first message participates in the first MBS session; The first bearer is a DRB, and the first RNTI is an RNTI in the second set of candidate RNTIs.

13. The second node according to claim 8, characterized in that, The second message indicates that data is transmitted via the second bearer during the RRC inactive state.

14. The second node according to claim 8, characterized in that, The second message indicates that data is transmitted through the second bearer in the RRC connection state.

15. A method in a first node used for wireless communication, characterized by, include: Receive a first message, the first message indicating at least a first bearer; In response to receiving the first message, enter or remain in the RRC inactive state; During the transmission of data through the first bearer in the RRC inactive state, a first signaling and a second message are received. The first signaling includes scheduling information for the first channel, and at least the second message is sent on the first channel. The second message is used to trigger the transmission of data through the second bearer. Wherein, one of the first bearer and the second bearer is an MRB, and the other is a DRB; the first signaling is scrambled by the first RNTI; The first RNTI is related to the first bearer; if the first bearer is an MRB, the first RNTI is an RNTI in a first candidate RNTI set; if the first bearer is a DRB, the first RNTI is an RNTI in a second candidate RNTI set; the first candidate RNTI set includes at least G-RNTIs; the second candidate RNTI set includes at least C-RNTIs.

16. The method in the first node according to claim 15, characterized in that, In response to receiving the second message, a third message is sent, which is used in the RRC connection recovery process; In response to the sending of the third message, monitor the fourth message; During the RRC connection recovery process, the second bearer is restored; The fourth message belongs to the RRC connection recovery process.

17. The method in the first node according to claim 15 or 16, characterized in that, In response to receiving the second message, the second bearer is restored; receiving the second message does not trigger the RRC connection restoration process.

18. The method in the first node according to claim 15, characterized in that, The second message includes the first identity of the first node, which is unique within at least one cell; the first bearer is an MRB, and the first RNTI is an RNTI from the first set of candidate RNTIs.

19. The method in the first node according to claim 15, characterized in that, The second message includes a second identity, which is used to indicate the first MBS session in which the first node participates; the first bearer is a DRB, and the first RNTI is an RNTI in the second set of candidate RNTIs.

20. The method in the first node according to claim 15, characterized in that, The second message indicates that data is transmitted via the second bearer during the RRC inactive state.

21. The method in the first node according to claim 15, characterized in that, The second message indicates that data is transmitted through the second bearer in the RRC connection state.

22. A method in a second node used for wireless communication, characterized by, include: Send a first message, the first message indicating at least a first bearer; Send a first signaling message and a second message, wherein the first signaling message includes scheduling information for a first channel, and at least the second message is sent on the first channel, and the second message is used to trigger data transmission through a second bearer; In response to the receipt of the first message, the recipient of the first message enters or remains in an RRC inactive state; the first signaling and the second message are received by the recipient of the first message during data transmission via the first bearer in the RRC inactive state; one of the first bearer and the second bearer is an MRB and the other is a DRB; the first signaling is scrambled by a first RNTI. The first RNTI is related to the first bearer; if the first bearer is an MRB, the first RNTI is an RNTI in a first candidate RNTI set; if the first bearer is a DRB, the first RNTI is an RNTI in a second candidate RNTI set; the first candidate RNTI set includes at least G-RNTIs; the second candidate RNTI set includes at least C-RNTIs.

23. The method in the second node according to claim 22, characterized in that, Receive a third message, which is used in the RRC connection recovery process; In response to the receipt of the third message, determine whether to send a fourth message; During the RRC connection recovery process, the second bearer is restored; the fourth message belongs to the RRC connection recovery process; the second message is used to trigger the third message.

24. The method in the second node according to claim 22 or 23, characterized in that, As a response to the second message being received by the recipient of the first message, the second bearer is restored; the receipt of the second message by the recipient of the first message does not trigger the RRC connection restoration process.

25. The method in the second node according to claim 22, characterized in that, The second message includes the first identity of the recipient of the first message, which is unique within at least one cell; the first bearer is an MRB, and the first RNTI is an RNTI in the first set of candidate RNTIs.

26. The method in the second node according to claim 22, characterized in that, The second message includes a second identity, which is used to indicate the first MBS session, and the recipient of the first message participates in the first MBS session; The first bearer is a DRB, and the first RNTI is an RNTI in the second set of candidate RNTIs.

27. The method in the second node according to claim 22, characterized in that, The second message indicates that data is transmitted via the second bearer during the RRC inactive state.

28. The method in the second node according to claim 27, characterized in that, The second message indicates that data is transmitted through the second bearer in the RRC connection state.

Images