Method and apparatus in communication node used for wireless communication

Abstract

The invention discloses a method and an apparatus in a communication node used for wireless communication. The communication node receives the first MAC PDU; wherein the first MAC PDU comprises a first MAC subPDU, the first MAC subPDU indicates a first logic identifier, the first logic identifier is configured, and the first logic identifier is associated to a first bearer; as a response that the first MAC PDU is received, the first MAC subPDU is discarded; the discarding of the first MAC subPDU is suspended depending on the first bearer, and the first MAC PDU is received through non-unicast, and / or the first MAC PDU is received through an auxiliary link; or, the discarding of the first MAC subPDU is associated to an RNTI other than a first RNTI depending on the first bearer, and the first MAC PDU is associated to the first RNTI. According to the method and the device, a wrong MAC subPDU is prevented from being accepted.

Description

Technical Field

[0001] The present application relates to a transmission method and device in a wireless communication system, and in particular to a MAC PDU processing method and device. Background Art

[0002] When a user equipment (UE) receives a MAC (Medium Access Control) PDU (Protocol Data Unit), Section 5.13 of 3GPP (the 3rd Generation Partnership Project) TS38.321 specifies that the MAC entity should discard unknown, unforeseen and erroneous protocol data, and specifically defines the conditions that the unknown, unforeseen and erroneous protocol data must meet.

[0003] 3GPP Rel-17 carried out a work item (WI) for receiving MBS (Multicast / Broadcast Service) in the RRC connected state and completed the standardization work; in order to reduce power consumption, reduce signaling overhead and shorten latency, Rel-18 established the "Enhancements of NR Multicast and Broadcast Services" work item to support MBS reception in the RRC inactive state.

[0004] 3GPP RAN approved a study project in Rel-17, "NR Sidelink Relay Study", to cover the enhancements and solutions required to support UE-to-network relay and UE-to-UE relay coverage extension, while considering a wider range of V2X, public safety and commercial applications and services. Rel-18 supports multi-path relay, where remote terminals are connected to the network through direct and indirect paths to improve reliability / robustness and throughput. Summary of the invention

[0005] The inventors have found through research that, with the enhancement of communication scenarios, the existing protocols have at least one of the following problems:

[0006] -. The existing protocol does not consider the case where the RB associated with the multicast data received in RRC_INACTIVE is suspended;

[0007] -. The existing protocol does not consider the case where the RB associated with the unicast data received via the sidelink (Sidelink, DL) is suspended;

[0008] -. The existing protocol does not consider the situation where the configured LCID (Logical Channel ID) or eLCID (extended Logical Channel ID) associated with the received multicast data is not associated with the G (Group)-RNTI (Radio Network Temporary Identity) or G-CS-RNTI (Group Configured Scheduling RNTI) for this multicast data.

[0009] When the above situation occurs, the UE may receive unknown, unpredictable and erroneous protocol data, which may affect the UE.

[0010] In view of the above problems, the present application provides a solution for processing MAC PDU. In view of the above problem description, the NR system is used as an example. The present application is also applicable to scenarios such as LTE (Long-Term Evolution) or LTE-A (Long-Term Evolution Advanced) or future 5G+ or 6G systems, and achieves technical effects similar to those of the NR system; further, adopting a unified design scheme for different scenarios also helps to reduce hardware complexity and cost. Further, although the present application provides a specific implementation method for RRC_INACTIVE MBS, the present application can also be used in the scenario of RRC_IDLE MBS to achieve technical effects similar to those of RRC_INACTIVE MBS. Further, although the original intention of the present application is for the Uu air interface, the present application can also be used for the PC5 port to achieve technical effects similar to those of the Uu air interface. Further, although the original intention of the present application is for the terrestrial network (TN) scenario, the present application is also applicable to the communication scenario of the non-terrestrial network (NTN) to achieve technical effects similar to those in the TN scenario. In addition, using a unified solution for different scenarios can also help reduce hardware complexity and costs.

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

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

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

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

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

[0016] Receive a first MAC PDU; wherein the first MAC PDU includes a first MAC subPDU, the first MACsubPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer;

[0017] In response to receiving the first MAC PDU, discarding the first MAC subPDU;

[0018] wherein the discarding of the first MAC subPDU is dependent on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or, the first MAC PDU is received via a side link;

[0019] or,

[0020] The discarding of the first MAC subPDU is dependent on the first bearer being associated to an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

[0021] As an embodiment, the discarding of the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or the first MAC PDU is received via SL-SCH (Sidelink Shared Channel).

[0022] As an embodiment, the discarding of the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast and the first MAC PDU is received via SL-SCH.

[0023] As an embodiment, the discarding of the first MAC subPDU relies on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast.

[0024] As an embodiment, the discarding of the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast and the first MAC PDU is for MBS.

[0025] As an embodiment, the discarding of the first MAC subPDU relies on the first bearer being suspended, wherein the first MAC PDU is received via SL-SCH.

[0026] As an embodiment, the discarding of the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received via unicast and the first MAC PDU is received via SL-SCH.

[0027] As an embodiment, the discarding of the first MAC subPDU relies on the first bearer being associated with a G-RNTI other than the first G-RNTI, wherein the first MAC PDU is identified by the first G-RNTI.

[0028] The problems to be solved by this application include: how to process the first MAC subPDU.

[0029] The problems to be solved by the present application include: when the first MACsubPDU in the first MAC PDU received via non-unicast indicates a first logical identifier and the first logical identifier is configured and the first logical identifier is associated with a first bearer, if the first bearer is suspended, how to process the first MAC subPDU.

[0030] The problems to be solved by the present application include: when the first MACsubPDU in the first MAC PDU received via non-unicast indicates a first logical identifier and the first logical identifier is configured and the first logical identifier is associated with a first bearer, if the first bearer is associated with a G-RNTI other than the first G-RNTI, how to process the first MACsubPDU.

[0031] The above method solves the above problem by discarding the first MAC subPDU.

[0032] The above method regards the first MAC subPDU as an erroneous MAC subPDU.

[0033] The above method avoids executing the first MAC subPDU.

[0034] The above method avoids executing an erroneous MAC subPDU.

[0035] According to one aspect of the present application, it is characterized in that the first RNTI is a G-RNTI; the non-unicast is multicast; and the first MAC PDU is received through the first RNTI.

[0036] The problem to be solved by the present application includes: when the first MAC PDU is identified by a G-RNTI and the non-unicast is a multicast, how to process the first MAC subPDU.

[0037] The problems to be solved by the present application include: when the first MAC subPDU in the first MAC PDU identified by G-RNTI received via multicast indicates a first logical identifier and the first logical identifier is configured and the first logical identifier is associated with a first bearer, if the first bearer is suspended, how to handle the first MAC subPDU.

[0038] The above method solves the above problem by discarding the first MAC subPDU.

[0039] The above method regards the first MAC subPDU as an erroneous MAC subPDU.

[0040] The above method avoids executing the first MAC subPDU.

[0041] The above method avoids executing an erroneous MAC subPDU.

[0042] According to one aspect of the present application, it is characterized in that the first logical identifier is unicast; and the first MAC PDU is received through a secondary link.

[0043] According to one aspect of the present application, it is characterized in that the first MAC PDU is for MBS; the non-unicast is multicast; and the first MAC PDU is received via non-unicast.

[0044] The problem to be solved by the present application includes: how to process the first MAC subPDU when the first MAC PDU is identified by the RNTI for the secondary link and is received via unicast.

[0045] The problems to be solved by the present application include: when the first MAC subPDU in the first MAC PDU identified by the RNTI of the secondary link received via unicast indicates a first logical identifier and the first logical identifier is configured and the first logical identifier is associated with a first bearer, if the first bearer is suspended, how to process the first MAC subPDU.

[0046] The above method solves the above problem by discarding the first MAC subPDU.

[0047] The above method regards the first MAC subPDU as an erroneous MAC subPDU.

[0048] The above method avoids executing the first MAC subPDU.

[0049] The above method avoids executing an erroneous MAC subPDU.

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

[0051] receiving a first RRC message; and maintaining an RRC_INACTIVE state and suspending the first bearer in response to receiving the first RRC message;

[0052] The first RRC message indicates that data is transmitted through at least one bearer in the RRC_INACTIVE state; and the first bearer is a bearer other than the at least one bearer.

[0053] The problem to be solved by the present application includes: when the first bearer is not a bearer indicated by the first RRC message to transmit data in the RRC_INACTIVE state, how to process the first MAC subPDU.

[0054] The problem to be solved by this application includes: how to suspend the first bearer.

[0055] The above method solves the above problem by receiving the first RRC message indicating that data is transmitted through at least one bearer in the RRC_INACTIVE state, triggering the maintenance of the RRC_INACTIVE state and suspending the first bearer.

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

[0057] Determining that a connection failure occurs; and suspending the first bearer in response to the determining that a connection failure occurs.

[0058] The problem to be solved by this application includes: how to suspend the first bearer.

[0059] The above method solves the above problem by determining that a connection failure occurs to trigger the suspension of the first bearer.

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

[0061] Sending a first MAC PDU; wherein the first MAC PDU includes a first MAC subPDU, the first MACsubPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; as a response to the first MAC PDU being received, the receiver of the first MAC PDU discards the first MACsubPDU;

[0062] wherein the discarding of the first MAC subPDU is dependent on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or, the first MAC PDU is received via a side link;

[0063] or,

[0064] The discarding of the first MAC subPDU is dependent on the first bearer being associated to an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

[0065] According to one aspect of the present application, it is characterized in that the first RNTI is a G-RNTI; the non-unicast is multicast; and the first MAC PDU is received through the first RNTI.

[0066] According to one aspect of the present application, it is characterized in that the first logical identifier is unicast; and the first MAC PDU is received through a secondary link.

[0067] According to one aspect of the present application, it is characterized in that the first MAC PDU is for MBS; the non-unicast is multicast; and the first MAC PDU is received via non-unicast.

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

[0069] Sending a first RRC message;

[0070] In which, as a response to receiving the first RRC message, the recipient of the first MAC PDU maintains the RRC_INACTIVE state and suspends the first bearer; the first RRC message indicates that data is transmitted through at least one bearer in the RRC_INACTIVE state; and the first bearer is a bearer other than the at least one bearer.

[0071] According to one aspect of the present application, it is characterized in that the receiver of the first MAC PDU determines that a connection failure has occurred; in response to the determination of the connection failure, the receiver of the first MAC PDU suspends the first bearer.

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

[0073] A first receiver receives a first MAC PDU; wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer;

[0074] a first transmitter, in response to receiving the first MAC PDU, discarding the first MAC subPDU;

[0075] wherein the discarding of the first MAC subPDU is dependent on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or, the first MAC PDU is received via a side link;

[0076] or,

[0077] The discarding of the first MAC subPDU is dependent on the first bearer being associated to an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

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

[0079] A second transmitter sends a first MAC PDU; wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; as a response to the first MAC PDU being received, the receiver of the first MAC PDU discards the first MAC subPDU;

[0080] wherein the discarding of the first MAC subPDU is dependent on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or, the first MAC PDU is received via a side link;

[0081] or,

[0082] The discarding of the first MAC subPDU is dependent on the first bearer being associated to an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

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

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

[0091] Figure 8 A flowchart of suspending a first bearer according to an embodiment of the present application is shown;

[0092] Fig. 9 A flowchart of suspending a first bearer according to another embodiment of an embodiment of the present application is shown;

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

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

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

[0096] Example 1

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

[0098] In embodiment 1, the first node in the present application receives a first MAC PDU in step 101; wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; in step 102, as a response to the first MAC PDU being received, the first MAC subPDU is discarded;

[0099] wherein the discarding of the first MAC subPDU is dependent on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or, the first MAC PDU is received via a side link;

[0100] or,

[0101] The discarding of the first MAC subPDU is dependent on the first bearer being associated to an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

[0102] As an embodiment, the first MAC PDU for the first RNTI means: the first MAC PDU is received through the first RNTI.

[0103] As an embodiment, the first MAC PDU for the first RNTI means that: the first MAC PDU is identified by the first RNTI.

[0104] As an embodiment, the first MAC PDU for the first RNTI means that a CRC (Cyclic Redundancy Check) of a TB (Transmission Block) corresponding to the first MAC PDU is scrambled by the first RNTI.

[0105] As an embodiment, the first MAC PDU for the first RNTI means that the CRC of the DCI (Downlink Control Information) that schedules the first MAC PDU is scrambled by the first RNTI.

[0106] As an embodiment, the first RNTI is an RNTI.

[0107] As an embodiment, the first RNTI is a bit string (BIT string).

[0108] As an embodiment, the first RNTI is a sixteen-bit bit string.

[0109] As an embodiment, the first RNTI is a hexadecimal value.

[0110] As an embodiment, the value of the first RNTI is not less than 0001 (hexadecimal) and not greater than FFF2 (hexadecimal).

[0111] As an embodiment, the first RNTI is of the first MAC entity.

[0112] As an embodiment, the first RNTI is for the first MAC entity.

[0113] As an embodiment, the first MAC entity receives the first MAC PDU.

[0114] As an embodiment, the first MAC entity is a MAC entity corresponding to the secondary link.

[0115] As an embodiment, the first MAC entity is a MAC entity corresponding to MCG (Master Cell Group).

[0116] As an embodiment, the first MAC entity is a MAC entity corresponding to SCG (Secondary Cell Group).

[0117] As an embodiment, the definition of MAC PDU in the present application refers to the MAC PDU in Section 6 of 3GPP TS 38.321.

[0118] As an embodiment, the resources occupied by the first MAC PDU are dynamically scheduled.

[0119] As an embodiment, the resources occupied by the first MAC PDU are configured by RRC.

[0120] As an embodiment, the resources occupied by the first MAC PDU are configured by RRC and activated by DCI.

[0121] As an embodiment, the resources occupied by the first MAC PDU are configured downlink assignments.

[0122] As an embodiment, the first MAC PDU is for a secondary link.

[0123] As an embodiment, the first MAC PDU is received via PSSCH (Physical Sidelink Shared Channel).

[0124] As an embodiment, the first MAC PDU is received via SL-SCH (Sidelink Shared Channel).

[0125] As an embodiment, the first MAC PDU is a SL MAC PDU.

[0126] As an embodiment, the first MAC PDU is downlink (DL).

[0127] As an embodiment, the first MAC PDU is received via PDSCH (Physical Downlink Shared Channel).

[0128] As an embodiment, the first MAC PDU is received via DL-SCH (Downlink Shared Channel).

[0129] As an embodiment, the first MAC PDU is a DL MAC PDU.

[0130] As an embodiment, the definition of MAC subPDU in the present application refers to the MAC subPDU in Section 6 of 3GPP TS 38.321.

[0131] As an embodiment, the first MAC PDU is composed of a positive integer number of MAC subPDUs.

[0132] As an embodiment, the first MAC PDU consists of a MAC subPDU.

[0133] As an embodiment, the first MAC PDU is composed of multiple MAC subPDUs.

[0134] As an embodiment, the first MAC PDU includes a padding MAC SDU.

[0135] As an embodiment, the first MAC PDU does not include a padding MAC SDU.

[0136] As an embodiment, the first MAC PDU includes padding MAC CE.

[0137] As an embodiment, the first MAC PDU does not include padding MAC CE.

[0138] As an embodiment, the first MAC subPDU consists of one MAC SDU, and the one MAC SDU indicates the first logical identifier.

[0139] As an embodiment, the first MAC subPDU consists of a MAC SDU and a MAC subheader.

[0140] As an embodiment, the MAC subheader in the first MAC subPDU indicates the first logical identifier.

[0141] As an embodiment, a field in a MAC subheader in the first MAC subPDU indicates the first logical identifier.

[0142] As an embodiment, the MAC subheader in the first MAC subPDU includes an LCID field, and the LCID field indicates the first logical identifier.

[0143] As an embodiment, the MAC subheader in the first MAC subPDU includes an eLCID field, and the eLCID field indicates the first logical identifier.

[0144] As an embodiment, the MAC subheader in the first MAC subPDU includes an LCID field and an eLCID field, and the one LCID field and the one eLCID field indicate the first logical identifier.

[0145] As an embodiment, the first logical identifier is an identifier of a logical channel.

[0146] As an embodiment, the first logical identifier indicates a logical channel.

[0147] As an embodiment, the first logical identifier is a LogicalChannelIdentity.

[0148] As an embodiment, the first logical identifier corresponds to an LCID.

[0149] As an embodiment, the first logical identifier corresponds to an eLCID.

[0150] As an embodiment, the first logical identifier corresponds to any one of an LCID or an eLCID.

[0151] As an embodiment, the first logical identifier is configured by an RRC signaling.

[0152] As an embodiment, the first logical identity is configured by a domain whose name includes LogicalChannelIdentity.

[0153] As an embodiment, the first logical identifier is configured by a LogicalChannelIdentity.

[0154] As an embodiment, the first logical identifier is configured by a LogicalChannelIdentityExt.

[0155] As an embodiment, the first logical identifier is associated with the first bearer by an RRC signaling configuration.

[0156] As an embodiment, the first bearer corresponds to a PDCP entity.

[0157] As an embodiment, the first bearer corresponds to multiple PDCP entities.

[0158] As an embodiment, the first bearer corresponds to an RLC entity.

[0159] As an embodiment, the first bearer corresponds to multiple RLC entities.

[0160] As an embodiment, the first bearer is used to carry business data.

[0161] As an embodiment, the first bearer is used to carry control signaling.

[0162] As an embodiment, the first bearer is a wireless bearer.

[0163] As an embodiment, the first bearer is a Uu wireless bearer.

[0164] As an embodiment, the first bearer is a wireless bearer of NR Uu.

[0165] As an embodiment, the first bearer is an SRB (Signalling Radio Bearer).

[0166] As an embodiment, the first bearer is a DRB ((user) Data Radio Bearer).

[0167] As an embodiment, the first bearer is configured by a domain whose name includes pdcp-Config.

[0168] As an embodiment, the first bearer is configured by a pdcp-Config.

[0169] As an embodiment, the first bearer is configured by a RadioBearerConfig domain.

[0170] As an embodiment, the first bearer is configured by a DRB-Identity.

[0171] As an embodiment, the first logical identifier being associated with the first bearer means that the first logical identifier is configured for the first bearer.

[0172] As an embodiment, the first logical identifier being associated with the first bearer means that the first bearer is configured for the first logical identifier.

[0173] As an embodiment, the first logical identifier being associated with the first bearer means that: the first logical identifier is associated with the first bearer.

[0174] As an embodiment, the first logical identifier being associated with the first bearer means that: the first bearer is associated with at least one logical identifier, and the first logical identifier is one of the at least one logical identifier.

[0175] As an embodiment, the first logical identifier being associated with the first bearer means that: the first logical identifier is associated with at least one bearer, and the first bearer is one of the at least one bearer.

[0176] As an embodiment, the first logical identifier being associated with the first bearer means that the RLC entity corresponding to the first logical identifier is linked to the PDCP entity corresponding to the first bearer.

[0177] As an embodiment, the first logical identifier being associated with the first bearer means that the RLC entity corresponding to the first logical identifier can deliver the SDU to the PDCP entity corresponding to the first bearer.

[0178] As an embodiment, the first logical identifier being associated with the first bearer means that the PDCP entity corresponding to the first bearer can deliver the PDU to the RLC entity corresponding to the first logical identifier.

[0179] As an embodiment, the discarding is discard.

[0180] As an embodiment, the discard is clear.

[0181] As an embodiment, the discarding is clean.

[0182] As an embodiment, the discarding is delete.

[0183] As an embodiment, the first MAC subPDU is discarded at the MAC sublayer.

[0184] As an embodiment, the first MAC subPDU is discarded by the first MAC entity.

[0185] As an embodiment, discarding the first MAC subPDU includes: not reading the MAC SDU in the first MACsubPDU.

[0186] As an embodiment, the discarding of the first MAC subPDU includes: not delivering the MAC SDU in the first MACsubPDU to an upper layer.

[0187] As an embodiment, the discarding of the first MAC subPDU includes: not executing the MAC SDU in the first MACsubPDU.

[0188] As an embodiment, the discarding of the first MAC subPDU includes: considering the first MAC subPDU to be an erroneous MAC subPDU.

[0189] As an embodiment, discarding the first MAC subPDU includes: considering the first MAC subPDU as at least one of unknown, unforeseeable and erroneous protocol data.

[0190] As an embodiment, in response to the first MAC PDU being received, the first MAC subPDU is discarded when performing the disassembly and demultiplexing process.

[0191] As an embodiment, in response to the first MAC PDU being received, the first MAC subPDU is discarded when processing unknown, unforeseen and erroneous protocol data.

[0192] As an embodiment, as a response to the first MAC PDU being received, when to discard the first MAC subPDU depends on the UE implementation.

[0193] As an embodiment, in response to the first MAC PDU being received, when the last MAC subPDU in the first MAC PDU is received, the first MAC subPDU is discarded.

[0194] As an embodiment, as a response to the first MAC PDU being received, when the first MAC subPDU is received, the first MAC subPDU is discarded.

[0195] As an embodiment, in response to the first MAC PDU being received, when the MAC subheader in the first MACsubPDU is received, the first MAC subPDU is discarded.

[0196] As an embodiment, as a response to the first MAC PDU being received, when the first logical identifier is determined, the first MAC subPDU is discarded.

[0197] As an embodiment, in response to the first MAC PDU being received, when it is determined that the first logical identifier is associated with the first bearer and the first bearer is suspended, the first MAC subPDU is discarded.

[0198] As an embodiment, in response to the first MAC PDU being received, when it is determined that the first logical identifier is associated with the first bearer and the first bearer is only associated with a G-RNTI other than the first G-RNTI, the first MAC subPDU is discarded.

[0199] As an embodiment, in response to the first MAC PDU being received, the first MAC PDU is discarded; the discarding of the first MAC PDU includes discarding the first MAC subPDU.

[0200] As an embodiment, in response to the first MAC PDU being received, the first MAC subPDU in the first MAC PDU and all remaining MAC subPDUs in the first MAC PDU are discarded.

[0201] As an embodiment, in response to the first MAC PDU being received, only the first MAC subPDU in the first MAC PDU is discarded.

[0202] As an embodiment, the discarding of the first MAC subPDU relies on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast.

[0203] As an embodiment, "the discarding of the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast" means: if the first bearer is suspended and the first MAC PDU is received via non-unicast, the first MAC subPDU is discarded.

[0204] As an embodiment, the "discarding the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast" means: if at least the first bearer is suspended and the first MAC PDU is received via non-unicast, the first MAC subPDU is discarded.

[0205] As an embodiment, the discarding of the first MAC subPDU relies on the first bearer being suspended, wherein the first MAC PDU is received via a side link.

[0206] As an embodiment, the "discarding the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received through a side link" means: if the first bearer is suspended and the first MAC PDU is received through a side link, the first MAC subPDU is discarded.

[0207] As an embodiment, the "discarding the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received through the side link" means: if at least the first bearer is suspended and the first MAC PDU is received through the side link, the first MAC subPDU is discarded.

[0208] As an embodiment, the discarding of the first MAC subPDU depends on the first bearer being suspended, which means: when the first bearer is suspended, the first MAC subPDU is discarded.

[0209] As an embodiment, the discarding of the first MAC subPDU depends on the first bearer being suspended, which means: if the first bearer is suspended, discarding the first MAC subPDU.

[0210] As an embodiment, the discarding of the first MAC subPDU depends on the first bearer being suspended, which means that the suspension of the first bearer triggers the discarding of the first MAC subPDU.

[0211] As an embodiment, the first bearer being suspended means that the first bearer is paused.

[0212] As an embodiment, the first bearer being suspended means that the first bearer is stopped.

[0213] As an embodiment, the first bearer being suspended means that the first bearer is not allowed to at least one of send or receive.

[0214] As an embodiment, the non-unicast means that the receivers of the first MAC PDU include multiple nodes.

[0215] As an embodiment, the non-unicast means that the first MAC PDU is directed to multiple nodes.

[0216] As an embodiment, the non-unicast means that the first MAC PDU is common to multiple nodes.

[0217] As an embodiment, the first node is one of the multiple nodes.

[0218] As an embodiment, the non-unicast is group cast.

[0219] As an embodiment, the non-unicast is for V2X.

[0220] As an embodiment, the non-unicast is multicast.

[0221] As an embodiment, the non-unicast is for MBS.

[0222] As an embodiment, the non-unicast is for multicast MBS.

[0223] As an embodiment, the first MAC PDU is received through non-unicast, which means that the first MAC PDU is received through non-unicast.

[0224] As an embodiment, the first MAC PDU is received via non-unicast, which means that the first MAC PDU is received via non-unicast, and the first MAC PDU is received via a side link.

[0225] As an embodiment, the first MAC PDU is received via non-unicast, which means that: the first MAC PDU is received via non-unicast, and the first MAC PDU is for MBS.

[0226] As an embodiment, the first MAC PDU is received via non-unicast, which means that the first MAC PDU is received via a side link, and the first MAC PDU is received via unicast.

[0227] As an embodiment, the discarding of the first MAC subPDU relies on the first bearer being associated with an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

[0228] As an embodiment, "the discarding of the first MAC subPDU depends on the first bearer being associated to an RNTI other than the first RNTI, wherein the first MAC PDU is received through the first RNTI" means: if the first bearer is associated to an RNTI other than the first RNTI and the first MAC PDU is received through the first RNTI, the first MAC subPDU is discarded.

[0229] As an embodiment, "the discarding of the first MAC subPDU depends on the first bearer being associated with an RNTI other than the first RNTI, wherein the first MAC PDU is received through the first RNTI" means: if at least the first bearer is associated with an RNTI other than the first RNTI and the first MAC PDU is received through the first RNTI, the first MAC subPDU is discarded.

[0230] As an embodiment, the discarding of the first MAC subPDU depends on the first bearer being associated only with an RNTI other than the first RNTI, which means: when the first bearer is associated only with a G-RNTI other than the first RNTI, the first MAC subPDU is discarded.

[0231] As an embodiment, the discarding of the first MAC subPDU depends on the first bearer being associated only with an RNTI other than the first RNTI, which means: if the first bearer is associated only with a G-RNTI other than the first RNTI, discarding the first MAC subPDU.

[0232] As an embodiment, the discarding of the first MAC subPDU depends on the first bearer being associated only with an RNTI other than the first RNTI, which means that the first bearer is associated only with a G-RNTI other than the first RNTI, triggering the discarding of the first MAC subPDU.

[0233] As an embodiment, the first bearer being associated with an RNTI other than the first RNTI means that the first bearer is not associated with the first RNTI.

[0234] As an embodiment, the first bearer being associated with an RNTI other than the first RNTI means that any LCID associated with the first bearer is associated with an RNTI other than the first RNTI.

[0235] As an embodiment, the first bearer being associated with an RNTI other than the first RNTI means that any LCID associated with the first bearer is not associated with the first RNTI.

[0236] As an embodiment, the first bearer being associated with an RNTI other than the first RNTI means that: the first RNTI and the first bearer are not indicated by the same RRC domain.

[0237] As an embodiment, the first bearer being associated with an RNTI other than the first RNTI means that at least one bearer is configured for the first RNTI, and the first bearer is not any one of the at least one bearer.

[0238] As an embodiment, an RNTI other than the first RNTI to which the first bearer is associated is configured.

[0239] As an embodiment, the first bearer is associated with an RNTI other than the first RNTI.

[0240] As an embodiment, the first bearer is associated with multiple RNTIs other than the first RNTI.

[0241] As an embodiment, the discarding of the first MAC subPDU depends on the first bearer being suspended and the discarding of the first MAC subPDU depends on the first bearer being associated with an RNTI other than the first RNTI.

[0242] As an embodiment, "the discarding of the first MAC subPDU depends on the first bearer being suspended and the discarding of the first MAC subPDU depends on the first bearer being associated with an RNTI other than the first RNTI" means: if the first bearer is suspended and the first bearer is associated with an RNTI other than the first RNTI, the first MAC subPDU is discarded.

[0243] As an embodiment, "the discarding of the first MAC subPDU depends on the first bearer being suspended and the discarding of the first MAC subPDU depends on the first bearer being associated with an RNTI other than the first RNTI" means: if at least the first bearer is suspended and the first bearer is associated with an RNTI other than the first RNTI, the first MAC subPDU is discarded.

[0244] As an embodiment, a first MAC PDU is received; wherein the first MAC PDU includes a first MACsubPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; as a response to the first MAC PDU being received, if at least the first bearer is suspended and the first MAC PDU is received via non-unicast, the first MAC subPDU is discarded.

[0245] As an embodiment, a first MAC PDU is received; wherein the first MAC PDU includes a first MACsubPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; as a response to the first MAC PDU being received, if at least the first bearer is suspended and the first MAC PDU is received via a secondary link, the first MAC subPDU is discarded.

[0246] As an embodiment, a first MAC PDU is received; wherein the first MAC PDU includes a first MACsubPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; as a response to the first MAC PDU being received, if at least the first bearer is associated with an RNTI other than a first RNTI and the first MAC PDU is received via the first RNTI, the first MACsubPDU is discarded.

[0247] As an embodiment, a first MAC PDU is received; wherein the first MAC PDU includes a first MACsubPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; as a response to the first MAC PDU being received, if at least the first bearer is suspended and the first MAC PDU is received via non-unicast, or, if at least the first bearer is suspended and the first MAC PDU is received via a side link, the first MAC subPDU is discarded.

[0248] As an embodiment, a first MAC PDU is received; wherein the first MAC PDU includes a first MACsubPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; as a response to the first MAC PDU being received, if at least the first bearer is suspended and the first MAC PDU is received via non-unicast, or, if at least the first bearer is associated to an RNTI other than a first RNTI and the first MAC PDU is received via the first RNTI, the first MAC subPDU is discarded.

[0249] As an embodiment, a first MAC PDU is received; wherein the first MAC PDU includes a first MACsubPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; as a response to the first MAC PDU being received, if at least the first bearer is suspended and the first MAC PDU is received via a secondary link, or, if at least the first bearer is associated to an RNTI other than a first RNTI and the first MAC PDU is received via the first RNTI, the first MAC subPDU is discarded.

[0250] As an embodiment, a first MAC PDU is received; wherein the first MAC PDU includes a first MACsubPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; as a response to the first MAC PDU being received, if at least the first bearer is suspended and the first MAC PDU is received via non-unicast, or, if at least the first bearer is suspended and the first MAC PDU is received via a side link, or, if at least the first bearer is associated to an RNTI other than a first RNTI and the first MAC PDU is received via the first RNTI, the first MAC subPDU is discarded.

[0251] As an embodiment, optionally, as a response to the first MAC PDU being received, if the LCID or eLCID included in a MAC subPDU in the first MAC PDU is not configured, the MAC subPDU is discarded.

[0252] As an embodiment, optionally, as a response to the first MAC PDU being received, if an LCID or eLCID included in a MAC subPDU in the first MAC PDU is reserved, the MAC subPDU is discarded.

[0253] As an embodiment, optionally, as a response to the first MAC PDU being received, if the LCID or eLCID included in a MAC subPDU in the first MAC PDU is reserved, the one MAC subPDU and any remaining MAC subPDUs in the first MAC PDU are discarded.

[0254] As an embodiment, optionally, as a response to the first MAC PDU being received, if the first node does not support the LCID or eLCID included in a MAC subPDU in the first MAC PDU, the one MAC subPDU is discarded.

[0255] As an embodiment, optionally, as a response to the first MAC PDU being received, if the first node does not support the LCID or eLCID included in a MAC subPDU in the first MAC PDU, the one MAC subPDU and any remaining MAC subPDUs in the first MAC PDU are discarded.

[0256] As an embodiment, optionally, as a response to the first MAC PDU being received, if a MAC subPDU including a MAC CE in the first MAC PDU is located after a MACsubPDU including a MAC SDU in the first MAC PDU, at least one of the MAC subPDU including the MAC CE or the MACsubPDU including the MAC SDU is discarded; the first MAC PDU is identified by a first G-RNTI.

[0257] Example 2

[0258] Embodiment 2 illustrates a schematic diagram of a network architecture according to an embodiment of the present application, as shown in the attached Figure 2 Attached Figure 2The network architecture 200 is described. The network architecture 200 is a 5G NR (New Radio) / LTE (Long-Term Evolution) / LTE-A (Long-Term Evolution Advanced) system, or the network architecture 200 is a 5G+ network architecture, or the network architecture 200 is a 6G network architecture, or the network architecture 200 is a network architecture that 3GPP will continue to evolve in the future; the network architecture 200 may be called 5GS (5G System) / EPS (Evolved Packet System), or the network architecture 200 may be called 6GS (6G System); the network architecture 200 includes at least one of UE (User Equipment) 201, RAN (Radio Access Network) 202, core network 210, HSS (Home Subscriber Server) / UDM (Unified Data Management) 220 and Internet service 230. The network architecture 200 can be interconnected with other access networks, but these entities / interfaces are not shown for simplicity. As shown, the network architecture 200 provides packet switching services, but it will be readily understood by those skilled in the art that the various concepts presented throughout this application can be extended to networks or other cellular networks that provide circuit switching services. The RAN includes a node 203 and other nodes 204. The node 203 provides user and control plane protocol terminations toward the UE 201. The node 203 can be connected to other nodes 204 via an Xn interface (e.g., backhaul) / X2 interface. The node 203 may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP (transmitting and receiving node) or some other suitable term. The core network 210 is a 5GC (5G Core Network, 5G core network) / EPC (Evolved Packet Core), or, the core network 210 is a 6GC; the node 203 provides an access point to the core network 210 for the UE 201. Examples of UE 201 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop computer, a personal digital assistant (PDA), a satellite radio, non-terrestrial base station communications, satellite mobile communications, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a drone, an aircraft, a narrowband Internet of Things device, a machine type communication device, a land vehicle, an automobile, a wearable device, or any other similarly functional device.Those skilled in the art may also refer to UE201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable term. Node 203 is connected to the core network 210 via an S1 / NG interface. The core network 210 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 a control node that processes signaling between UE201 and the core network 210. In general, MME / AMF / SMF211 provides bearer and connection management. All user IP (Internet Protocol) packets are transmitted through S-GW / UPF212, which is itself connected to P-GW / UPF213. P-GW provides UE IP address allocation and other functions. P-GW / UPF213 is connected to Internet Service 230. Internet Service 230 includes operator-corresponding Internet Protocol services, which may specifically include Internet, Intranet, IMS (IP Multimedia Subsystem) and packet-switched streaming services.

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

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

[0261] As an embodiment, the UE 201 is a relay device.

[0262] As an embodiment, the UE201 is a gateway device.

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

[0264] As an embodiment, the node 203 is a base station device.

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

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

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

[0268] Typically, the UE 201 is a user equipment, and the node 203 is a base station device.

[0269] Typically, the UE 201 is a user equipment, and the node 203 is a user equipment.

[0270] Typically, the UE 201 is a base station device, and the node 203 is a base station device.

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

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

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

[0274] As an embodiment, the user equipment supports V2X.

[0275] As an embodiment, the user equipment supports multicast MBS.

[0276] As an embodiment, the user equipment supports multicast MBS and V2X.

[0277] As an embodiment, the user equipment supports RRC_INACTIVE multicast MBS.

[0278] As an embodiment, the user equipment supports RRC_INACTIVE multicast MBS and V2X.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0307] As an embodiment, the base station device includes a gateway device.

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

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

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

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

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

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

[0314] As an embodiment, the relay device includes a relay.

[0315] As an embodiment, the relay device includes an L3 relay.

[0316] As an embodiment, the relay device includes an L2 relay.

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

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

[0319] As an embodiment, the relay device includes a gateway device.

[0320] As an embodiment, the relay device includes user equipment.

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

[0322] Example 3

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

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

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

[0326] As an embodiment, the first MAC PDU in the present application is generated at a higher layer of the PDCP304.

[0327] As an embodiment, the first MAC PDU in the present application is generated in the PDCP304.

[0328] As an embodiment, the first MAC PDU in the present application is generated at a higher layer of the RRC306.

[0329] As an embodiment, the first MAC PDU in the present application is generated in the RRC306.

[0330] As an embodiment, the first MAC PDU in the present application is generated by the MAC302 or MAC352.

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

[0332] Example 4

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

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

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

[0336] In transmission from the second communication device 410 to the first communication device 450, at the second communication device 410, upper layer data packets from the core network are provided to the controller / processor 475. The controller / processor 475 implements the functionality of the L2 layer. In transmission from the second communication device 410 to the first communication device 450, the controller / processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the first communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for retransmission of lost packets and signaling to the first communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., the physical layer). The transmit processor 416 implements coding and interleaving to facilitate forward error correction (FEC) at the second communication device 410, as well as mapping of signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing on the coded and modulated symbols to generate one or more spatial streams. The transmit processor 416 then maps each spatial stream to a subcarrier, multiplexes it with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then uses an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain multi-carrier symbol stream. The multi-antenna transmit processor 471 then performs a transmit analog precoding / beamforming operation on the time-domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multi-carrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream, and then provides it to a different antenna 420.

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

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

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

[0340] As an embodiment, the first communication device 450 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor, and the first communication device 450 at least: receives a first MAC PDU; wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; as a response to the first MAC PDU being received, discards the first MAC subPDU; wherein the discarding of the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or, the first MAC PDU is received via a side link; or, the discarding of the first MAC subPDU depends on the first bearer being associated with an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

[0341] As an embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program, wherein the computer-readable instruction program generates actions when executed by at least one processor, and the actions include: receiving a first MAC PDU; wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; as a response to the first MAC PDU being received, discarding the first MAC subPDU; wherein the discarding of the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or, the first MAC PDU is received via a side link; or, the discarding of the first MAC subPDU depends on the first bearer being associated with an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

[0342] As an embodiment, the second communication device 410 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used with the at least one processor. The second communication device 410 at least: sends a first MAC PDU; wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; as a response to the first MAC PDU being received, the receiver of the first MAC PDU discards the first MAC subPDU; wherein the discarding of the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or, the first MAC PDU is received via a side link; or, the discarding of the first MAC subPDU depends on the first bearer being associated with an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

[0343] As an embodiment, the second communication device 410 includes: a memory storing a computer-readable instruction program, wherein the computer-readable instruction program generates actions when executed by at least one processor, and the actions include: sending a first MAC PDU; wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; as a response to the first MAC PDU being received, the receiver of the first MAC PDU discards the first MAC subPDU; wherein the discarding of the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or, the first MAC PDU is received via a side link; or, the discarding of the first MAC subPDU depends on the first bearer being associated with an RNTI other than the first RNTI, wherein the first MAC PDU is received via the first RNTI.

[0344] As an embodiment, at least one of the antenna 452, the receiver 454, the receiving processor 456, and the controller / processor 459 is used to receive a first MAC PDU.

[0345] As an embodiment, at least one of the antenna 420, the transmitter 418, the transmit processor 416, and the controller / processor 475 is used to send a first MAC PDU.

[0346] As an embodiment, at least one of the antenna 452, the receiver 454, the receiving processor 456, and the controller / processor 459 is used to receive a first RRC message.

[0347] As an embodiment, at least one of the antenna 420, the transmitter 418, the transmit processor 416, and the controller / processor 475 is used to send a first RRC message.

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

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

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

[0351] As an embodiment, the first communication device 450 is a base station device.

[0352] As an embodiment, the first communication device 450 is a relay device.

[0353] As an embodiment, the second communication device 410 is a user equipment.

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

[0355] As an embodiment, the second communication device 410 is a relay device.

[0356] Example 5

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

[0358] for First node U01 In step S5101, a first MAC PDU is received; wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; in step S5102, as a response to the first MAC PDU being received, the first MAC subPDU is discarded.

[0359] for Second node N02, in step S5201, the first MAC PDU is sent.

[0360] for The third node N03 , in step S5301, receive the first MAC PDU.

[0361] In embodiment 5, the discarding of the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast.

[0362] As an embodiment, the first node U01 and the second node N02 are connected via a Uu port.

[0363] As an embodiment, the first node U01 is a user equipment, and the second node N02 is a user equipment.

[0364] As an embodiment, the first node U01 is a user equipment, and the second node N02 is a relay device.

[0365] As an embodiment, the first node U01 is a user equipment, and the second node N02 is a base station device.

[0366] As an embodiment, the user equipment is a UE and the base station device is a gNB.

[0367] As an embodiment, step S5301 is optional.

[0368] As an embodiment, step S5301 does not exist.

[0369] As an embodiment, step S5301 exists.

[0370] As an embodiment, the third node N03 is optional.

[0371] As an embodiment, the third node N03 does not exist.

[0372] As an embodiment, the third node N03 exists.

[0373] As an embodiment, the third node N03 is a node other than the first node U01.

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

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

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

[0377] As an embodiment, the first node U01 receives the first MAC PDU in the RRC_CONNECTED state; the third node N03 receives the first MAC PDU in the RRC_CONNECTED state.

[0378] As an embodiment, the first node U01 receives the first MAC PDU in the RRC_CONNECTED state; the third node N03 receives the first MAC PDU in the RRC_INACTIVE state.

[0379] As an embodiment, the first node U01 receives the first MAC PDU in the RRC_INACTIVE state; the third node N03 receives the first MAC PDU in the RRC_CONNECTED state.

[0380] As an embodiment, the first node U01 receives the first MAC PDU in the RRC_INACTIVE state; the third node N03 receives the first MAC PDU in the RRC_INACTIVE state.

[0381] As an embodiment, optionally, the second node N02 configures the first logical identifier to the first node U01 and the third node N03.

[0382] As an embodiment, optionally, the second node N02 configures the first bearer to the first node U01 and the third node N03.

[0383] As an embodiment, optionally, as a response to the first MAC PDU being received, the first MACsubPDU is not discarded by the third node N03; and the first bearer is not suspended by the third node N03.

[0384] As an embodiment, optionally, as a response to the first MAC PDU being received, the first MACsubPDU is discarded by the third node N03; and the first bearer is suspended by the third node N03.

[0385] As an embodiment, the non-unicast is multicast.

[0386] As an embodiment, the non-unicast is multicast.

[0387] As an embodiment, the first bearer is an MRB (MBS Radio Bearer).

[0388] As an embodiment, the first bearer is a multicast MRB.

[0389] As an embodiment, the first bearer is added by an MRB-ToAddModList field.

[0390] As an embodiment, the first bearer is indicated by an MRB-Identity.

[0391] As an embodiment, the first bearer is indicated by an MRB-Identity.

[0392] As an embodiment, the first logical identifier is configured by an MRB-RLC-ConfigMulticast domain.

[0393] As an embodiment, the first logical identifier is configured by an MBS-SessionInfoListMulticast IE.

[0394] As an embodiment, the first logical identifier is associated to the first bearer by an MRB-InfoMulticast configuration.

[0395] As an embodiment, the first logical identifier is associated to the first bearer by an MRB-InfoMulticast configuration.

[0396] As an embodiment, the first logical identifier is associated with the first bearer configured by an RLC-BearerConfig.

[0397] As an embodiment, the first MAC PDU is received via a configured downlink allocation; the first bearer is associated to the configured downlink allocation.

[0398] As an embodiment, the first MAC PDU is received via a configured downlink allocation; the first bearer is not associated with the configured downlink allocation.

[0399] As an embodiment, the first MAC PDU is received via a first RNTI; and the first bearer is associated with an RNTI other than the first RNTI.

[0400] As an embodiment, the first MAC PDU is received via a first RNTI; and the first bearer is associated with the first RNTI.

[0401] As an embodiment, the first MAC PDU is received through the first RNTI, which means that the first MAC PDU is for the first RNTI.

[0402] As an embodiment, the first MAC PDU is received through the first RNTI, which means that the first MAC PDU is identified by the first RNTI.

[0403] As an embodiment, the first MAC PDU is received through the first RNTI, which means that the first MAC PDU is scheduled by the first RNTI.

[0404] As an embodiment, the first MAC PDU is received through the first RNTI means that the CRC of the DCI scheduling the first MAC PDU is scrambled by the first RNTI.

[0405] As an embodiment, the first bearer being associated with the first RNTI means that: the first RNTI and the first bearer are indicated by the same RRC domain.

[0406] As an embodiment, the first bearer being associated with the first RNTI means that: the first RNTI and the first bearer are indicated by the same MBS-SessionInfo field.

[0407] As an embodiment, the first bearer being associated with the first RNTI means that: the first RNTI and the first bearer are indicated by the same MBS-SessionInfoMulticast field.

[0408] As an embodiment, the first bearer being associated with the first RNTI means that the multicast MBS session corresponding to the first RNTI can be transmitted through the first bearer.

[0409] As an embodiment, the first bearer being associated with the first RNTI means that: at least one bearer is configured for the first RNTI, and the first bearer is one of the at least one bearer.

[0410] As an embodiment, the first RNTI is a G-RNTI.

[0411] As an embodiment, the first RNTI is used to receive a multicast MBS.

[0412] As an embodiment, the first RNTI is used to receive the multicast MBS in the RRC_CONNECTED state.

[0413] As an embodiment, the first RNTI is used to receive the multicast MBS in the RRC_INACTIVE state.

[0414] As an embodiment, the first RNTI is used to receive the multicast MBS in the RRC_IDLE state.

[0415] As an embodiment, the "if at least the first bearer is suspended and the first MAC PDU is received via non-unicast, discard the first MAC subPDU" means: if the first bearer is suspended and the first MAC PDU is received via non-unicast and the non-unicast is multicast, discard the first MAC subPDU.

[0416] As an embodiment, the "if at least the first bearer is suspended and the first MAC PDU is received via non-unicast, discard the first MAC subPDU" means: if at least the first bearer is suspended and the first MAC PDU is received via non-unicast and the non-unicast is multicast, discard the first MAC subPDU.

[0417] Example 6

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

[0419] for First node U01 In step S6101, a first MAC PDU is received; wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; in step S6102, as a response to the first MAC PDU being received, the first MAC subPDU is discarded.

[0420] for Second node N02 , in step S6201, the first MAC PDU is sent.

[0421] In Embodiment 6, the discarding of the first MAC subPDU is dependent on the first bearer being suspended, wherein the first MAC PDU is received via a side link.

[0422] As an embodiment, the first node U01 and the second node N02 are connected via the PC5 port.

[0423] As an embodiment, the first node U01 and the second node N02 are connected via a V2X interface.

[0424] As an embodiment, the first node U01 is a user equipment, and the second node N02 is a user equipment.

[0425] As an embodiment, the first MAC PDU is received through dynamic scheduling.

[0426] As an embodiment, the first MAC PDU is received via a configured downlink assignment.

[0427] As an embodiment, the first MAC PDU is received through the secondary link means that: the first MAC PDU is received on the secondary link.

[0428] As an embodiment, the first MAC PDU is received through the secondary link, which means that the first MAC PDU is received on the SL-SCH.

[0429] As an embodiment, the first bearer is a wireless bearer of SL.

[0430] As an embodiment, the first bearer is a SL-SRB3.

[0431] As an embodiment, the first bearer is SRB1.

[0432] As an embodiment, the first bearer is split SRB1.

[0433] As an embodiment, the first bearer is configured by a SL-RemoteUE-RB-Identity.

[0434] As an embodiment, the first bearer is configured by an SRB-Identity.

[0435] As an embodiment, the first bearer is configured by an sl-SRB-Identity.

[0436] As an embodiment, the first bearer is configured by an SRB-Identity.

[0437] As an embodiment, the first bearer is configured by an SL-RLC-BearerConfig.

[0438] As an embodiment, the first logical identifier is unicast.

[0439] As an embodiment, the first logical identifier is for multicast.

[0440] As an embodiment, the first logical identifier is configured for the secondary link.

[0441] As an embodiment, the first logical identifier is unicast of the secondary link.

[0442] As an embodiment, the first logical identifier is for multicast of the secondary link.

[0443] As an embodiment, the first logical identifier is associated to the first bearer configured by an SL-RLC-BearerConfig.

[0444] As an embodiment, the first logical identifier is associated with the first bearer configured by an SLRB-Config.

[0445] As an embodiment, the first logical identifier is associated to the first bearer by a SL-MappingToAddMod configuration.

[0446] As an embodiment, the first node is configured with multi-path, and the first MAC PDU is received via a non-direct path.

[0447] As an embodiment, the "if at least the first bearer is suspended and the first MAC PDU is received via a side link, discard the first MAC subPDU" means: if the first bearer is suspended and the first MAC PDU is received via a side link and the first logical identifier is unicast, discard the first MAC subPDU.

[0448] As an embodiment, the "if at least the first bearer is suspended and the first MAC PDU is received through a side link, discard the first MAC subPDU" means: if at least the first bearer is suspended and the first MAC PDU is received through a side link and the first logical identifier is unicast, discard the first MAC subPDU.

[0449] Example 7

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

[0451] for First node U01 In step S7101, a first MAC PDU is received; wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; in step S7102, as a response to the first MAC PDU being received, the first MAC subPDU is discarded.

[0452] for Second node N02 , in step S7201, the first MAC PDU is sent.

[0453] for The third node N03 , in step S7301, receive the first MAC PDU.

[0454] In Embodiment 7, the discarding of the first MAC subPDU relies on the first bearer being associated to an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

[0455] As an embodiment, the first node U01 and the second node N02 are connected via a Uu port.

[0456] As an embodiment, the first node U01 and the second node N02 are connected via a NR Uu port.

[0457] As an embodiment, the first node U01 is a user equipment, and the second node N02 is a user equipment.

[0458] As an embodiment, the first node U01 is a user equipment, and the second node N02 is a relay device.

[0459] As an embodiment, the first node U01 is a user equipment, and the second node N02 is a base station device.

[0460] As an embodiment, the user equipment is a UE and the base station device is a gNB.

[0461] As an embodiment, step S5301 is optional.

[0462] As an embodiment, step S5301 does not exist.

[0463] As an embodiment, step S5301 exists.

[0464] As an embodiment, the third node N03 does not exist.

[0465] As an embodiment, the third node N03 exists.

[0466] As an embodiment, the third node N03 is a node other than the first node U01.

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

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

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

[0470] As an embodiment, optionally, the second node N02 configures the first RNTI to the first node U01 and the third node N03.

[0471] As an embodiment, optionally, the second node N02 configures the first logical identifier to the first node U01 and the third node N03.

[0472] As an embodiment, optionally, the second node N02 configures the first bearer to the first node U01 and the third node N03.

[0473] As an embodiment, the first bearer is suspended.

[0474] As an embodiment, the first bearer is not suspended.

[0475] As an embodiment, the first bearer is configured with at least one G-RNTI.

[0476] As an embodiment, the first bearer is configured with at least one G-CS-RNTI.

[0477] As an embodiment, the first bearer is not configured with G-CS-RNTI.

[0478] As an embodiment, the first bearer is an MRB (MBS Radio Bearer).

[0479] As an embodiment, the first bearer is a multicast MRB.

[0480] As an embodiment, the first bearer is added by an MRB-ToAddModList field.

[0481] As an embodiment, the first bearer is indicated by an MRB-Identity.

[0482] As an embodiment, the first logical identifier is configured by an MRB-RLC-ConfigMulticast domain.

[0483] As an embodiment, the first logical identifier is configured by an MBS-SessionInfoListMulticast IE.

[0484] As an embodiment, the first logical identifier is associated to the first bearer by an MRB-InfoMulticast configuration.

[0485] As an embodiment, the first logical identifier is associated to the first bearer by an MRB-InfoMulticast configuration.

[0486] As an embodiment, the first logical identifier is associated with the first bearer configured by an RLC-BearerConfig.

[0487] As an embodiment, the first RNTI is a G-RNTI.

[0488] As an embodiment, the RNTI other than the first RNTI is a G-RNTI.

[0489] As an embodiment, the G-RNTI is for multicast.

[0490] As an embodiment, the first node U01 is not configured with G-CS-RNTI.

[0491] As an embodiment, the first RNTI is a G-CS-RNTI.

[0492] As an embodiment, the first RNTI is any one of G-RNTI and G-CS-RNTI.

[0493] As an embodiment, the RNTI other than the first RNTI is a G-CS-RNTI.

[0494] As an embodiment, the first RNTI is a G-RNTI; and the non-unicast is a multicast.

[0495] As an embodiment, the first RNTI is a G-RNTI; and the non-unicast is a broadcast.

[0496] Typically, the first RNTI is a G-RNTI; the first logical identifier is an LCID; and the first bearer is a multicast MRB.

[0497] Typically, the first RNTI is a G-RNTI; the first logical identifier is an eLCID; and the first bearer is a multicast MRB.

[0498] Typically, the first RNTI is a G-CS-RNTI; the first logical identifier is an LCID; and the first bearer is a multicast MRB.

[0499] Typically, the first RNTI is a G-CS-RNTI; the first logical identifier is an eLCID; and the first bearer is a multicast MRB.

[0500] Typically, the first RNTI is a G-CS-RNTI; the first logical identifier is an LCID or an eLCID; and the first bearer is a multicast MRB.

[0501] As an embodiment, the first bearer is associated with an RNTI other than the first RNTI, which means that the first RNTI and the first bearer are not indicated by the same MBS-SessionInfo field.

[0502] As an embodiment, the first bearer is associated with an RNTI other than the first RNTI, which means that the first RNTI and the first bearer are not indicated by the same MBS-SessionInfoMulticast domain.

[0503] As an embodiment, the first bearer being associated with an RNTI other than the first RNTI means that the multicast MBS session corresponding to the first RNTI is not transmitted through the first bearer.

[0504] As an embodiment, the first bearer being associated with an RNTI other than the first RNTI means that the first bearer is associated with a G-RNTI other than the first RNTI.

[0505] As an embodiment, the first RNTI and the first bearer are associated to an RNTI other than the first RNTI in order to receive a multicast MBS.

[0506] As an embodiment, the first RNTI and the first bearer are associated to an RNTI other than the first RNTI in order to receive multicast MBS in RRC_INACTIVE state.

[0507] As an embodiment, the first RNTI and the first bearer are associated to an RNTI other than the first RNTI in order to receive multicast MBS in RRC_CONNECTED state.

[0508] As an embodiment, the first RNTI and the first bearer are associated with RNTIs other than the first RNTI, both of which are G-RNTIs.

[0509] As an embodiment, the "if at least the first bearer is associated to an RNTI other than the first RNTI and the first MAC PDU is received through the first RNTI, discarding the first MAC subPDU" means: if the first bearer is associated to an RNTI other than the first RNTI and the first MAC PDU is received through the first RNTI and the first RNTI is a G-RNTI and the non-unicast is multicast, discarding the first MAC subPDU.

[0510] As an embodiment, the "if at least the first bearer is associated to an RNTI other than the first RNTI and the first MAC PDU is received through the first RNTI, discard the first MAC subPDU" means: if at least the first bearer is associated to an RNTI other than the first RNTI and the first MAC PDU is received through the first RNTI and the first RNTI is a G-RNTI and the non-unicast is multicast, discard the first MAC subPDU.

[0511] Example 8

[0512] Embodiment 8 illustrates a flowchart of suspending the first bearer according to an embodiment of the present application, as shown in the attached Figure 8 It is particularly noted that the order in this example does not limit the signal transmission order and implementation order in this application.

[0513] for First node U01 In step S8101, a first RRC message is received; as a response to the first RRC message being received, the RRC_INACTIVE state is maintained and the first bearer is suspended.

[0514] for Second node N02 , in step S8201, the first RRC message is sent.

[0515] In Embodiment 8, the first RRC message indicates that data is transmitted through at least one bearer in the RRC_INACTIVE state; and the first bearer is a bearer other than the at least one bearer.

[0516] As an embodiment, the first node U01 receives the first RRC message in the RRC_INACTIVE state.

[0517] As an embodiment, the first node U01 receives the first RRC message in the RRC_CONNECTED state.

[0518] As an embodiment, the first RRC message is transmitted via MCCH.

[0519] As an embodiment, the first RRC message is transmitted via DCCH.

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

[0521] As an embodiment, the first RRC message is an RRCRelease message, and the message includes a suspendConfig.

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

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

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

[0525] As an embodiment, the first RRC message includes MBS-SessionInfoListMulticast IE.

[0526] As an embodiment, the first RRC message includes the MBS-SessionInfoMulticast-r18 field.

[0527] As an embodiment, maintaining the RRC_INACTIVE state refers to: entering (entering) the RRC_INACTIVE state.

[0528] As an embodiment, maintaining the RRC_INACTIVE state means: if the first node U01 is in the RRC_CONNECTED state, entering the RRC_INACTIVE state.

[0529] As an embodiment, maintaining the RRC_INACTIVE state means: if the first node U01 is in the RRC_INACTIVE state, maintaining the RRC_INACTIVE state.

[0530] As an embodiment, the first node U01 first suspends the first bearer and then maintains the RRC_INACTIVE state.

[0531] As an embodiment, the suspending of the first bearer is before the maintaining of the RRC_INACTIVE state.

[0532] As an embodiment, when the first RRC message is received, the first bearer is not suspended.

[0533] As an embodiment, in response to the first RRC message being received, the first bearer is suspended only when the first bearer is not suspended.

[0534] As an embodiment, in response to the first RRC message being received, if the first bearer is not suspended, the first bearer is suspended.

[0535] As an embodiment, optionally, as a response to the first RRC message being received, all multicast MRBs that are not indicated to transmit data in the RRC_INACTIVE state are suspended; the first bearer is one of all multicast MRBs that are not indicated to transmit data in the RRC_INACTIVE state.

[0536] As an embodiment, optionally, as a response to the first RRC message being received, all SRBs and DRBs except SRB0 and broadcast MRB are suspended.

[0537] As an embodiment, the first node U01 receives the first MAC PDU in the RRC_INACTIVE state.

[0538] As an embodiment, before the step S5101 in Embodiment 5, the step S8101 and the step S8102 are executed.

[0539] As an embodiment, within the time interval between the step S8102 and the step S5101, the first bearer is not resumed.

[0540] As an embodiment, the first bearer is suspended during the time interval between the step S8102 and the step S5101.

[0541] As an embodiment, when step S5101 is executed, the first bearer is suspended.

[0542] As an embodiment, before the step S6101 in Embodiment 6, the step S8101 and the step S8102 are executed.

[0543] As an embodiment, within the time interval between the step S8102 and the step S6101, the first bearer is not resumed.

[0544] As an embodiment, the first bearer is suspended during the time interval between the step S8102 and the step S6101.

[0545] As an embodiment, when step S6101 is executed, the first bearer is suspended.

[0546] Example 9

[0547] Embodiment 9 illustrates a flowchart of suspending the first bearer according to another embodiment of the present application, as shown in the attached Fig. 9 It is particularly noted that the order in this example does not limit the signal transmission order and implementation order in this application.

[0548] for First node U01 In step S9101, it is determined that a connection failure occurs; in step S9102, as a response to the determination that a connection failure occurs, the first bearer is suspended.

[0549] As an embodiment, the determining that a connection failure occurs refers to: considering that the connection failure occurs.

[0550] As an embodiment, the determining that a connection failure occurs refers to: considering that the connection failure is detected.

[0551] As an embodiment, determining that a connection failure occurs refers to: detecting the connection failure.

[0552] As an embodiment, the connection failure is a radio link failure (Radio Link Failure, RLF).

[0553] As an embodiment, the connection failure is a switching failure.

[0554] As an embodiment, the SCG failure is a synchronous reconfiguration failure (reconfiguration with sync failure).

[0555] As an embodiment, the first node U01 determines that a connection failure occurs in the RRC_CONNECTED state; as a response to the determination of the connection failure, a connection failure information process is initiated, and in the connection failure information process, the first bearer is suspended.

[0556] As an embodiment, the connection failure is an MCG failure (Failure).

[0557] As an embodiment, the MCG failure is MCG RLF.

[0558] As an embodiment, the MCG failure is an MCG switching failure.

[0559] As an embodiment, the connection failure information process is an MCG failure information process.

[0560] As an embodiment, in the connection failure information process, MCG transmission (MCG transmission) is suspended; the suspending of MCG transmission includes suspending the first bearer.

[0561] As an embodiment, the suspending MCG transmission includes: suspending MCG transmission for all SRBs and DRBs.

[0562] As an embodiment, the connection failure is an SCG failure.

[0563] As an embodiment, the SCG failure is a SCG RLF.

[0564] As an embodiment, the SCG failure is an SCG synchronous reconfiguration failure.

[0565] As an embodiment, the SCG failure is the SCG configuration failure.

[0566] As an embodiment, the SCG failure is receiving an integrity check failure indication from SCG lower layers concerning SRB3.

[0567] As an embodiment, the connection failure information process is an SCG failure information process.

[0568] As an embodiment, in the connection failure information process, SCG transmission (SCG transmission) is suspended; the suspending SCG transmission includes suspending the first bearer.

[0569] As an embodiment, the suspending SCG transmission includes: suspending SCG transmission for all SRBs and DRBs.

[0570] As an embodiment, the connection failure is an indirect path failure.

[0571] As an embodiment, the indirect path failure is a secondary link (SL) indirect path failure.

[0572] As an embodiment, the indirect path failure is an N3C indirect path failure (SL indirect path failure).

[0573] As an embodiment, the connection failure information process is an Indirect path failure information process.

[0574] As an embodiment, in the connection failure information process, indirect path transmission is suspended.

[0575] As an embodiment, the suspending of the non-direct path transmission includes suspending the first bearer.

[0576] As an embodiment, the suspending the non-direct path transmission includes: suspending the non-direct path transmission for all SRBs and DRBs.

[0577] As an embodiment, the first node U01 determines that a connection failure occurs in the RRC_INACTIVE state.

[0578] As an embodiment, optionally, as a response to the first MAC PDU being received, the first MACsubPDU is discarded, and the MAC SDU other than the first MAC subPDU in the first MAC PDU is not affected by the discarding of the first MAC subPDU.

[0579] As an embodiment, optionally, as a response to the first MAC PDU being received, the first MAC PDU is discarded, and the discarding of the first MAC PDU includes discarding the first MAC subPDU.

[0580] The above method avoids the impact of inaccurate MAC PDU received when the link quality is poor.

[0581] As an embodiment, optionally, as a response to the first MAC PDU being received, the first MACsubPDU and all remaining MAC subPDUs in the first MAC PDU are discarded.

[0582] The above method avoids the impact of inaccurate MAC subPDUs received when the link quality is poor.

[0583] As an embodiment, before the step S5101 in Embodiment 5, the step S9101 and the step S9102 are executed.

[0584] As an embodiment, within the time interval between the step S9102 and the step S5101, the first bearer is not resumed.

[0585] As an embodiment, the first bearer is suspended during the time interval between the step S9102 and the step S5101.

[0586] As an embodiment, when step S5101 is executed, the first bearer is suspended.

[0587] As an embodiment, before the step S6101 in Embodiment 6, the step S9101 and the step S9102 are executed.

[0588] As an embodiment, within the time interval between the step S9102 and the step S6101, the first bearer is not resumed.

[0589] As an embodiment, the first bearer is suspended during the time interval between the step S9102 and the step S6101.

[0590] As an embodiment, when step S6101 is executed, the first bearer is suspended.

[0591] Example 10

[0592] Embodiment 10 illustrates a structural block diagram of a processing device used in a first node according to an embodiment of the present application; Fig.10 As shown in the attached Fig.10 In the embodiment, the processing device 1000 in the first node includes a first receiver 1001 and a first transmitter 1002.

[0593] A first receiver 1001 receives a first MAC PDU, wherein the first MAC PDU includes a first MACsubPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer;

[0594] The first transmitter 1002 discards the first MACsubPDU in response to the first MAC PDU being received;

[0595] In embodiment 10, the discarding of the first MAC subPDU is dependent on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or the first MAC PDU is received via a side link;

[0596] or,

[0597] The discarding of the first MAC subPDU is dependent on the first bearer being associated to an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

[0598] As an embodiment, the first RNTI is a G-RNTI; the non-unicast is a multicast; and the first MAC PDU is received via the first RNTI.

[0599] As an embodiment, the first logical identifier is unicast; and the first MAC PDU is received via a secondary link.

[0600] As an embodiment, the first MAC PDU is for MBS; the non-unicast is multicast; and the first MAC PDU is received via non-unicast.

[0601] As an embodiment, the first receiver 1001 receives a first RRC message; as a response to the first RRC message being received, maintains the RRC_INACTIVE state and suspends the first bearer; wherein the first RRC message indicates that data is transmitted through at least one bearer in the RRC_INACTIVE state; and the first bearer is a bearer other than the at least one bearer.

[0602] As an embodiment, the first receiver 1001 determines that a connection failure occurs; and in response to the determination of the connection failure, suspends the first bearer.

[0603] As an embodiment, the first receiver 1001 includes the attached Figure 4 At least one of the antenna 452 or the receiver 454 or the multi-antenna receive processor 458 or the receive processor 456 or the controller / processor 459 or the memory 460 or the data source 467.

[0604] As an embodiment, the first receiver 1001 includes the attached Figure 4 At least an antenna 452 and a receiver 454.

[0605] As an embodiment, the first transmitter 1002 includes the attached Figure 4 At least one of the antenna 452 or the transmitter 454 or the multi-antenna transmit processor 457 or the transmit processor 468 or the controller / processor 459 or the memory 460 or the data source 467.

[0606] As an embodiment, the first transmitter 1002 includes the attached Figure 4 At least antenna 452 and transmitter 454.

[0607] Embodiment 11

[0608] Embodiment 11 illustrates a structural block diagram of a processing device used in a second node according to an embodiment of the present application; Fig.11 As shown in the attached Fig.11 In the embodiment, the processing device 1100 in the second node includes a second transmitter 1101.

[0609] The second transmitter 1101 sends a first MAC PDU; wherein the first MAC PDU includes a first MACsubPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; as a response to the first MAC PDU being received, the receiver of the first MAC PDU discards the first MAC subPDU;

[0610] In embodiment 11, the discarding of the first MAC subPDU is dependent on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or the first MAC PDU is received via a side link;

[0611] or,

[0612] The discarding of the first MAC subPDU is dependent on the first bearer being associated to an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

[0613] As an embodiment, the first RNTI is a G-RNTI; the non-unicast is a multicast; and the first MAC PDU is received via the first RNTI.

[0614] As an embodiment, the first logical identifier is unicast; and the first MAC PDU is received via a secondary link.

[0615] As an embodiment, the first MAC PDU is for MBS; the non-unicast is multicast; and the first MAC PDU is received via non-unicast.

[0616] As an embodiment, the second transmitter 1101 sends a first RRC message; wherein, as a response to the first RRC message being received, the receiver of the first MAC PDU maintains the RRC_INACTIVE state and suspends the first bearer; the first RRC message indicates that data is transmitted through at least one bearer in the RRC_INACTIVE state; and the first bearer is a bearer other than the at least one bearer.

[0617] As an embodiment, the receiver of the first MAC PDU determines that a connection failure occurs; in response to the determination of the connection failure, the receiver of the first MAC PDU suspends the first bearer.

[0618] As an embodiment, the second transmitter 1101 includes the attached Figure 4 At least one of the antenna 420 or the transmitter 418 or the multi-antenna transmit processor 471 or the transmit processor 416 or the controller / processor 475 or the memory 476.

[0619] As an embodiment, the second transmitter 1101 includes the attached Figure 4 At least antenna 420 and transmitter 418.

[0620] A person of ordinary skill in the art can understand that all or part of the steps in the above method can be completed by instructing the relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk or an optical disk. Optionally, all or part of the steps in the above embodiment can also be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiment can be implemented in the form of hardware or in the form of a software function module, and the present application is not limited to any specific form of software and hardware combination. The user equipment, terminal and UE in the present application include but are not limited to drones, communication modules on drones, remote-controlled aircraft, aircraft, small aircraft, mobile phones, tablet computers, notebooks, vehicle-mounted communication equipment, wireless sensors, Internet cards, Internet of Things terminals, RFID terminals, NB-IOT terminals, MTC (Machine Type Communication, Machine Type Communication) terminals, eMTC (enhanced MTC, enhanced MTC) terminals, data cards, Internet cards, vehicle-mounted communication equipment, low-cost mobile phones, low-cost tablet computers and other wireless communication devices. The base stations or system devices in this application include but are not limited to macrocell base stations, microcell base stations, home base stations, relay base stations, gNB (NR Node B) NR Node B, TRP (Transmitter Receiver Point) and other wireless communication devices.

[0621] The above is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A first node used for wireless communication, characterized in that: include: A first receiver receives a first MAC PDU; wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; a first transmitter, in response to receiving the first MAC PDU, discarding the first MAC subPDU; wherein the discarding of the first MAC subPDU is dependent on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or the first MAC PDU is received via a side link; or, The discarding of the first MAC subPDU is dependent on the first bearer being associated to an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

2. The first node according to claim 1, characterized in that: The first RNTI is a G-RNTI; the non-unicast is a multicast; and the first MAC PDU is received via the first RNTI.

3. The first node according to claim 1, characterized in that: The first logical identifier is for unicast; and the first MAC PDU is received via a secondary link.

4. The first node according to claim 1, characterized in that: The first MAC PDU is for MBS; the non-unicast is multicast; and the first MAC PDU is received via non-unicast.

5. The first node according to any one of claims 1 to 4, characterized in that: include: The first receiver receives a first RRC message; In response to receiving the first RRC message, maintaining the RRC_INACTIVE state and suspending the first bearer; The first RRC message indicates that data is transmitted through at least one bearer in the RRC_INACTIVE state; and the first bearer is a bearer other than the at least one bearer.

6. The first node according to any one of claims 1 to 5, characterized in that: include: The first receiver determines that a connection failure occurs; In response to the determination that a connection failure has occurred, the first bearer is suspended.

7. A method in a first node for wireless communication, characterized in that: include: Receive a first MAC PDU; wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; In response to receiving the first MAC PDU, discarding the first MAC subPDU; wherein the discarding of the first MAC subPDU is dependent on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or the first MAC PDU is received via a side link; or, The discarding of the first MAC subPDU is dependent on the first bearer being associated to an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

8. A second node used for wireless communication, characterized in that: include: A second transmitter sends a first MAC PDU; wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; as a response to the first MAC PDU being received, the receiver of the first MAC PDU discards the first MAC subPDU; wherein the discarding of the first MAC subPDU is dependent on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or the first MAC PDU is received via a side link; or, The discarding of the first MAC subPDU is dependent on the first bearer being associated to an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

9. A method in a second node for wireless communication, characterized in that: include: Sending a first MAC PDU; wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; as a response to the first MAC PDU being received, the receiver of the first MAC PDU discards the first MAC subPDU; wherein the discarding of the first MAC subPDU is dependent on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or the first MAC PDU is received via a side link; or, The discarding of the first MAC subPDU is dependent on the first bearer being associated to an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

Images