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; as a response that the first MAC PDU is received, the first MAC subPDU is discarded; the discarding of the first MAC subPDU depends only on the first MAC PDU comprising a value of a logical channel identifier associated with the suspended radio bearer. The method facilitates forward compatibility and backward compatibility and facilitates reduction of UE implementation complexity.

Description

Technical Field

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

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

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

[0004] 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 for discarding unknown, unforeseen and erroneous protocol data.

[0005] Among them, in order to reduce the impact of the value of the LCID or eLCID associated with the suspended RB received through the C-RNTI or CS-RNTI of the MAC entity or the configured downlink allocation on the UE, it is stipulated that for the MAC PDU including the value of the LCID or eLCID associated with the suspended RB received through the C-RNTI or CS-RNTI of the MAC entity or the configured downlink allocation, the received subPDU is discarded. The specific definitions are as follows:

[0006] When a MAC entity receives a MAC PDU for the MAC entity's C-RNTI or CS-RNTI, or by the configured downlink assignment, containing an LCID or eLCID value which is not configured, or an LCID or eLCID value associated with asuspended RB as specified in TS 38.331[5], the MAC entity shall at least:

[0007] 1>discard the received subPDU.

[0008] In order to avoid the impact on the UE of the LCID or eLCID value associated with the suspended multicast MRB received for MBS multicast through the G-RNTI or G-CS-RNTI of the MAC entity or the configured downlink allocation, in the 3GPP RAN125bis meeting, the document R2-2403203 proposed to discard the received subPDU for the MAC PDU for MBS multicast including the LCID or eLCID value associated with the suspended multicast MRB received through the G-RNTI or G-CS-RNTI of the MAC entity or the configured downlink allocation. Based on this scheme, the specific implementation method in Section 5.13 of 3GPP TS38.321 is as follows:

[0009] When a MAC entity receives a MAC PDU for MAC entity's G-RNTI or G-CS-RNTI, or by the configured downlink assignment for MBS multicast containing anLCID or eLCID which is not configured, or an LCID or eLCID value associated with a suspended multicast MRB as specified in TS 38.331[5], the MAC entityshall at least:

[0010] 1>discard the received subPDU. Summary of the invention

[0011] The inventors have found through research that with the enhancement of communication scenarios, there are more and more scenarios where radio bearers are suspended. The processing of MAC subPDUs associated with received and suspended radio bearers makes the protocol more and more complicated, and also affects the conditions for discarding MAC subPDUs, which has an impact on UE implementation. Therefore, it is necessary to enhance the processing of unknown, unpredictable and erroneous protocol data.

[0012] In response to the above problems, the present application provides a solution for processing MAC subPDU. In the description of the above problems, the NR system is used as an example. The present application is also applicable to scenarios such as LTE (Long-Term Evolution) or LTE-A (Long-Term Evolution Advanced) or future 5G+ or 6G systems, achieving technical effects similar to those of the NR system; further, adopting a unified design solution for different scenarios can also help reduce hardware complexity and costs. Furthermore, although the original intention of the present application is for terrestrial network (Terrestrial Network, TN) scenarios, the present application is also applicable to non-terrestrial network (Non-Terrestrial Network, NTN) communication scenarios, achieving technical effects similar to those in TN scenarios. In addition, adopting a unified solution for different scenarios can also help reduce hardware complexity and costs.

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

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

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

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

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

[0018] receiving a first MAC PDU; and discarding a first MAC subPDU in response to receiving the first MAC PDU;

[0019] The discarding of the first MAC subPDU depends only on the value of the logical channel identifier associated with the suspended radio bearer included in the first MAC PDU.

[0020] The problem to be solved by the present application includes: how to determine to discard the first MAC subPDU.

[0021] The above method solves the above problem by discarding the first MAC subPDU only depending on the first MAC PDU including the value of the logical channel identifier associated with the suspended radio bearer.

[0022] As an embodiment, the above method prevents the UE from accepting the MAC subPDU indicated by the value of the logical channel identifier associated with the suspended radio bearer.

[0023] As an embodiment, the above method avoids the UE from processing the MAC subPDU indicated by the value of the logical channel identifier associated with the suspended radio bearer.

[0024] As an embodiment, the above method avoids the impact of the MAC subPDU indicated by the value of the logical channel identifier associated with the suspended radio bearer on the UE.

[0025] As an embodiment, compared with the prior art, the above method is helpful in reducing the triggering conditions for discarding a MAC subPDU.

[0026] As an embodiment, the above method is helpful in reducing implementation complexity compared with the prior art.

[0027] As an embodiment, the above method is helpful in simplifying the complexity of protocol implementation compared with the prior art.

[0028] As an embodiment, the above method is more conducive to forward compatibility compared with the prior art.

[0029] As an embodiment, the above method is more conducive to backward compatibility compared with the prior art.

[0030] As an embodiment, the above method is advantageous for forward compatibility and backward compatibility compared with the prior art.

[0031] As an embodiment, the above method is helpful to reduce standardization work compared with the prior art.

[0032] According to one aspect of the present application, it is characterized in that the discarding of the first MAC subPDU only depends on the first MAC PDU including the value of the logical channel identifier associated with the suspended radio bearer, which means: when the first MAC PDU includes the value of the logical channel identifier associated with the suspended radio bearer, the first MAC subPDU is discarded.

[0033] The problem to be solved by the present application includes: how to discard the first MAC subPDU only depends on the first MAC PDU including the value of the logical channel identifier associated with the suspended radio bearer.

[0034] The above method solves the above problem by discarding the first MAC subPD when the first MAC PDU includes the value of the logical channel identifier associated with the suspended radio bearer.

[0035] According to one aspect of the present application, it is characterized in that the discarding of the first MAC subPDU only depends on the value of the logical channel identifier associated with the suspended radio bearer included in the first MAC PDU, including: the discarding of the first MACsubPDU is independent of the type of RNTI used to receive the first MAC PDU.

[0036] According to one aspect of the present application, it is characterized in that discarding the first MAC subPDU is based on protocol regulations.

[0037] As an embodiment, the above method solves the above problem based on protocol regulations.

[0038] As an embodiment, the above method is more conducive to standardization compared with UE-based implementation.

[0039] As an embodiment, compared with UE-based implementation, the above method is helpful in avoiding the impact of different UE behaviors on the UE itself.

[0040] As an embodiment, compared with UE-based implementation, the above method is helpful in avoiding the impact of different UE behaviors on the network.

[0041] According to one aspect of the present application, it is characterized in that the discarding of the first MAC subPDU is implemented based on UE.

[0042] As an embodiment, the above method solves the above problem by being implemented based on UE.

[0043] As an embodiment, the above method is helpful to improve the flexibility of UE implementation compared with the method based on protocol regulations.

[0044] As an embodiment, the above method is helpful to reduce the operation steps of discarding MAC subPDU compared with the method based on protocol provisions.

[0045] According to one aspect of the present application, it is characterized in that the suspended radio bearer is any one of DRB, SRB or MRB.

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

[0047] A first processor receives a first MAC PDU; in response to the first MAC PDU being received, discards a first MAC subPDU;

[0048] The discarding of the first MAC subPDU depends only on the value of the logical channel identifier associated with the suspended radio bearer included in the first MAC PDU. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

[0055] Figure 6 A schematic diagram in a 3GPP protocol according to an embodiment of the present application is shown;

[0056] Figure 7 A schematic diagram in a 3GPP protocol according to another embodiment of the present application is shown;

[0057] Figure 8 A structural block diagram of a processing device used in a first node according to an embodiment of the present application is shown. DETAILED DESCRIPTION

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

[0059] Example 1

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

[0061] In Example 1, the first node in the present application receives a first MAC PDU in step 101; in step 102, as a response to the reception of the first MAC PDU, the first MAC subPDU is discarded; wherein the discarding of the first MACsubPDU depends only on the value of the logical channel identifier associated with the suspended radio bearer included in the first MAC PDU.

[0062] As an embodiment, the discarding of the first MAC subPDU depends only on the value of the logical channel identifier associated with the suspended radio bearer included in the first MAC PDU, including: the discarding of the first MAC subPDU is independent of the type of RNTI used to receive the first MAC PDU.

[0063] As an embodiment, the discarding of the first MAC subPDU is independent of the type of RNTI used for receiving the first MAC PDU, which means that the discarding of the first MAC subPDU is independent of whether the type of RNTI used for receiving the first MAC PDU is unicast or multicast.

[0064] As an embodiment, the above method does not need to determine the type of RNTI used to receive the first MAC PDU, and is simple to implement.

[0065] As an embodiment, the discarding of the first MAC subPDU depends only on the value of the logical channel identifier associated with the suspended radio bearer included in the first MAC PDU, including: the discarding of the first MAC subPDU is independent of whether the first MAC PDU is received via unicast or multicast.

[0066] As an embodiment, the above method does not need to determine whether the first MAC PDU is received via unicast or multicast, and is simple to implement.

[0067] As an embodiment, the discarding of the first MAC subPDU depends only on the value of the logical channel identifier associated with the suspended radio bearer included in the first MAC PDU, including: the discarding of the first MAC subPDU is independent of the state of the first node when receiving the first MAC PDU.

[0068] As an embodiment, the above method does not need to determine the state of the first node when receiving the first MAC PDU, and is simple to implement.

[0069] As an embodiment, the discarding of the first MAC subPDU is independent of the state of the first node when the first MAC PDU is received, which means that regardless of the state of the first node when the first MAC PDU is received, the discarding of the first MAC subPDU only depends on the value of the logical channel identifier associated with the suspended radio bearer included in the first MAC PDU.

[0070] As an embodiment, the discarding of the first MAC subPDU depends only on the value of the logical channel identifier associated with the suspended radio bearer included in the first MAC PDU, including: the discarding of the first MAC subPDU is independent of the radio resources for receiving the first MAC PDU.

[0071] As an embodiment, the discarding of the first MAC subPDU is independent of the wireless resources for receiving the first MAC PDU, which means that the discarding of the first MAC subPDU is independent of whether the wireless resources for receiving the first MAC PDU are at the Uu port or at a sub-link.

[0072] As an embodiment, the above method does not need to determine the wireless resources for receiving the first MAC PDU, and is simple to implement.

[0073] As an embodiment, the discarding of the first MAC subPDU depends only on the value of the logical channel identifier associated with the suspended radio bearer included in the first MAC PDU, including: the discarding of the first MAC subPDU is independent of the type of the suspended radio bearer.

[0074] As an embodiment, the above method does not need to determine the type of the suspended radio bearer, and is simple to implement.

[0075] As an embodiment, the discarding of the first MAC subPDU depends only on the value of the logical channel identifier associated with the suspended radio bearer included in the first MAC PDU, including: the discarding of the first MAC subPDU is irrelevant to the reason why the radio bearer is suspended.

[0076] As an embodiment, the above method does not need to determine the reason why the radio bearer is suspended, and is simple to implement.

[0077] As an embodiment, the discarding of the first MAC subPDU is based on UE implementation, which means that the execution time of discarding the first MAC subPDU is based on UE implementation.

[0078] As an embodiment, the discarding of the first MAC subPDU is based on UE implementation, which means that the discarding of the first MAC subPDU is performed by the first node based on UE implementation.

[0079] As an embodiment, the discarding of the first MAC subPDU is based on UE implementation, which means that: the discarding of the first MAC subPDU is not mandatory.

[0080] As an embodiment, the discarding of the first MAC subPDU is based on UE implementation, which means that: the discarding of the first MAC subPDU is not specified by the protocol.

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

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

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

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

[0085] As an embodiment, the first MAC PDU is received via an RNTI for the first MAC entity.

[0086] As an embodiment, the first MAC PDU is received via any RNTI for the first MAC entity.

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

[0088] As an embodiment, the first MAC PDU is received via an RNTI for the first MAC entity or via a configured downlink allocation.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0110] As an embodiment, the first MAC subPDU consists of one MAC SDU, and the one MAC SDU indicates the value of the logical channel identifier associated with the suspended radio bearer.

[0111] As an embodiment, the first MAC subPDU consists of a MAC SDU and a MAC subheader, and the MAC subheader in the first MAC subPDU indicates the value of the logical channel identifier associated with the suspended radio bearer.

[0112] As an embodiment, a field in the MAC subheader in the first MAC subPDU indicates the value of the logical channel identifier associated with the suspended radio bearer.

[0113] As an embodiment, the MAC subheader in the first MAC subPDU includes an LCID field, and the LCID field indicates the value of the logical channel identifier associated with the suspended radio bearer.

[0114] As an embodiment, the MAC subheader in the first MAC subPDU includes an eLCID field, and the eLCID field indicates the value of the logical channel identifier associated with the suspended radio bearer.

[0115] As an embodiment, the MAC subheader in the first MAC subPDU includes an LCID field and an eLCID field, and the LCID field and the eLCID field indicate the value of the logical channel identifier associated with the suspended radio bearer.

[0116] As an embodiment, the value of the logical channel identifier associated with the suspended radio bearer is an identifier of a logical channel.

[0117] As an embodiment, the value of the logical channel identifier associated with the suspended radio bearer indicates a logical channel.

[0118] As an embodiment, the value of the logical channel identifier associated with the suspended radio bearer is a LogicalChannelIdentity.

[0119] As an embodiment, the value of the logical channel identifier associated with the suspended radio bearer corresponds to an LCID.

[0120] As an embodiment, the value of the logical channel identifier associated with the suspended radio bearer corresponds to an eLCID.

[0121] As an embodiment, the value of the logical channel identifier associated with the suspended radio bearer corresponds to any one of an LCID or an eLCID.

[0122] As an embodiment, the value of the logical channel identifier associated with the suspended radio bearer is configured by an RRC signaling.

[0123] As an embodiment, the value of the logical channel identifier associated with the suspended radio bearer is configured by a domain whose name includes LogicalChannelIdentity.

[0124] As an embodiment, the value of the logical channel identifier associated with the suspended radio bearer is configured by a LogicalChannelIdentity.

[0125] As an embodiment, the value of the logical channel identifier associated with the suspended radio bearer is configured by a LogicalChannelIdentityExt.

[0126] As an embodiment, the suspended wireless bearer corresponds to a PDCP entity.

[0127] As an embodiment, the suspended wireless bearer corresponds to multiple PDCP entities.

[0128] As an embodiment, the suspended radio bearer corresponds to an RLC entity.

[0129] As an embodiment, the suspended radio bearer corresponds to multiple RLC entities.

[0130] As an embodiment, the suspended wireless bearer is used to carry service data.

[0131] As an embodiment, the suspended radio bearer is used to carry control signaling.

[0132] As an embodiment, the suspended radio bearer is a radio bearer (Radio Bearer, RB).

[0133] As an embodiment, the suspended radio bearer is a radio bearer of IAB.

[0134] As an embodiment, the suspended radio bearer is a radio bearer of a secondary link.

[0135] As an embodiment, the suspended radio bearer is a Uu radio bearer.

[0136] As an embodiment, the suspended radio bearer is a radio bearer of NR Uu.

[0137] As an embodiment, the suspended radio bearer is an SRB (Signalling Radio Bearer).

[0138] As an embodiment, the suspended radio bearer is a DRB ((user) Data Radio Bearer).

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

[0140] As an embodiment, the suspended radio bearer is configured by a pdcp-Config.

[0141] As an embodiment, the suspended radio bearer is configured by a RadioBearerConfig field.

[0142] As an embodiment, the suspended radio bearer is configured by a DRB-Identity.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0160] As an embodiment, in response to the first MAC PDU being received, the first MAC subPDU is discarded when a value of a logical channel identifier associated with the suspended radio bearer is determined.

[0161] As an embodiment, in response to the first MAC PDU being received, when it is determined that the radio bearer is suspended, the first MAC subPDU is discarded.

[0162] As an embodiment, in response to the first MAC PDU being received, when it is determined that the first MAC PDU includes a value of a logical channel identifier associated with a suspended radio bearer, the first MAC subPDU is discarded.

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

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

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

[0166] As an embodiment, in response to the first MAC PDU being received, any MAC subPDU in the first MAC PDU including the value of the logical channel identifier associated with the suspended radio bearer is discarded.

[0167] As an embodiment, the suspended radio bearer refers to: a suspended radio bearer.

[0168] As an embodiment, the suspended radio bearer refers to: a stopped radio bearer.

[0169] As an embodiment, the suspended radio bearer refers to a radio bearer that is not allowed to send or receive at least one of the radio bearers.

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

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

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

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

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

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

[0176] As an embodiment, the first MAC subPDU is a MAC subPDU indicated by a value of a logical channel identifier associated with the suspended radio bearer in the first MAC PDU.

[0177] As an embodiment, the first MAC subPDU is indicated by the value of the logical channel identifier associated with the suspended radio bearer in the first MAC PDU.

[0178] Example 2

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0195] As an embodiment, the user equipment supports SDT.

[0196] As an embodiment, the user equipment supports suspending a radio bearer.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0245] Example 3

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

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

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

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

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

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

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

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

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

[0255] Example 4

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

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

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

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

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

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

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

[0263] 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; discards a first MAC subPDU in response to the first MAC PDU being received; wherein the discarding of the first MAC subPDU depends only on the first MAC PDU including the value of the logical channel identifier associated with the suspended radio bearer.

[0264] 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, the actions including: receiving a first MAC PDU; discarding a first MAC subPDU in response to the first MAC PDU being received; wherein the discarding of the first MAC subPDU depends only on the first MAC PDU including a value of a logical channel identifier associated with the suspended radio bearer.

[0265] 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 together with the at least one processor. The second communication device 410 at least: sends a first MAC PDU; as a response to the first MAC PDU being received, the receiver of the first MAC PDU discards a first MAC subPDU; wherein the receiver of the first MAC PDU discards the first MAC subPDU only depending on the first MAC PDU including a value of a logical channel identifier associated with a suspended radio bearer.

[0266] 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; in response to the first MAC PDU being received, the receiver of the first MAC PDU discards the first MAC subPDU; wherein the receiver of the first MAC PDU discards the first MAC subPDU only depends on the first MAC PDU including the value of the logical channel identifier associated with the suspended radio bearer.

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

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

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

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

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

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

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

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

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

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

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

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

[0279] Example 5

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

[0281] for First node U01In step S5101, the radio bearer is suspended; in step S5102, a first MAC PDU is received; in step S5103, as a response to the first MAC PDU being received, the first MAC subPDU is discarded.

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

[0283] In embodiment 5, the discarding of the first MAC subPDU depends only on the first MAC PDU including a value of a logical channel identifier associated with the suspended radio bearer.

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

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

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

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

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

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

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

[0291] As an embodiment, the state of the first node when receiving the first MAC PDU is the RRC_CONNECTED state.

[0292] As an embodiment, the state of the first node when receiving the first MAC PDU is RRC_INACTIVE state.

[0293] As an embodiment, the state of the first node when receiving the first MAC PDU is the RRC_IDLE state.

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

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

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

[0297] As an embodiment, in response to an RRC signaling being received, the radio bearer is suspended.

[0298] As an embodiment, in response to the RRC signaling being received, the radio bearer is suspended and enters the RRC_INACTIVE state.

[0299] As an embodiment, the RRC signaling is an RRCRelease message.

[0300] As an embodiment, the RRC signaling is a suspendConfig field in a RRCRelease message.

[0301] As an embodiment, the RRC signaling is a Paging message.

[0302] As an embodiment, the RRC signaling is an MBSMulticastConfiguration message.

[0303] As an embodiment, the RRC signaling is an MBS-SessionInfoListMulticast IE.

[0304] As an embodiment, the RRC signaling is an MBS-SessionInfoMulticast-r18 domain.

[0305] As an embodiment, in response to determining that a connection failure has occurred, the radio bearer is suspended.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0323] As an embodiment, in response to initiating a connection failure information process, the radio bearer is suspended.

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

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

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

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

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

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

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

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

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

[0333] As an embodiment, the suspending the non-direct path transmission includes suspending the radio bearer.

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

[0335] Example 6

[0336] Embodiment 6 illustrates a schematic diagram in a 3GPP protocol according to an embodiment of the present application, as shown in the attached Figure 6 shown.

[0337] In embodiment 6, when the first MAC PDU received by the first MAC entity through the RNTI for the first MAC entity includes the value of the logical channel identifier associated with the suspended radio bearer, the first MAC subPDU is discarded.

[0338] A specific implementation of the above method in Section 5.13 of 3GPP TS38.321 is as follows:

[0339] 当一个MAC实体接收到针对该MAC实体的C-RNTI、CS-RNTI、G-RNTI、G-CS-RNTI的MAC PDU,或者通过配置的下行链路分配接收到的MAC PDU,且该MAC PDU包含保留的LCID或eLCID值,或者包含该MAC实体不支持的LCID或eLCID值时,该MAC实体应至少:

[0340] 1>丢弃接收到的子PDU以及MAC PDU中任何剩余的子PDU。

[0341] 当一个MAC实体接收到针对该MAC实体的C-RNTI或CS-RNTI的MAC PDU,或者通过配置的下行链路分配接收到的MAC PDU,且该MAC PDU包含未配置的LCID或eLCID值时,该MAC实体应至少:

[0342] 1>丢弃接收到的子PDU。

[0343] 当一个MAC实体接收到一个包含与TS 38.331[5]中规定的挂起RB相关联的LCID或eLCID值的MAC PDU时,该MAC实体应至少:

[0344] 1>丢弃接收到的子PDU。

[0345] When a MAC entity receives a MAC PDU on SL-SCH containing a ReservedLCID value for broadcast or groupcast,or an LCID value which is notconfigured,the MAC entity shall:

[0346] 1>discard the received subPDU.

[0347] When a MAC entity receives a MAC PDU on SL-SCH containing a ReservedLCID value for unicast, the MAC entity shall:

[0348] 1>discard the received subPDU and any remaining subPDUs in the MACPDU.

[0349] As an embodiment, compared with the prior art, the above method is helpful in reducing the triggering conditions for discarding a MAC subPDU.

[0350] As an embodiment, the above method is helpful to reduce the complexity of UE implementation compared with the prior art.

[0351] As an embodiment, the above method is helpful in simplifying the complexity of protocol implementation compared with the prior art.

[0352] As an embodiment, the above method is more conducive to forward compatibility compared with the prior art.

[0353] As an embodiment, the above method is more conducive to backward compatibility compared with the prior art.

[0354] As an embodiment, the above method is advantageous for forward compatibility and backward compatibility compared with the prior art.

[0355] As an embodiment, the above method is helpful to reduce standardization work compared with the prior art.

[0356] As an embodiment, the above method is advantageous in supporting a wider range of scenarios compared with the prior art.

[0357] Example 7

[0358] Embodiment 7 illustrates a schematic diagram in a 3GPP protocol according to another embodiment of the present application, as shown in the attached Figure 7 shown.

[0359] In embodiment 7, when the first MAC PDU received by the first MAC entity through the RNTI or configured downlink allocation for the first MAC entity includes the value of the logical channel identifier associated with the suspended radio bearer, the first MAC subPDU is discarded.

[0360] Another specific implementation of the above method in Section 5.13 of 3GPP TS38.321 is as follows:

[0361] When a MAC entity receives a MAC PDU for the MAC entity's C-RNTI,CS-RNTI,G-RNTI,G-CS-RNTI or by the configured downlink assignment,containing aReserved LCID or eLCID value,or an LCID or eLCID value the MAC Entity does not support,the MAC entity shall at least:

[0362] 1>discard the received subPDU and any remaining subPDUs in the MACPDU.

[0363] When a MAC entity receives a MAC PDU for the MAC entity's C-RNTI orCS-RNTI,or by the configured downlink assignment,containing an LCID or eLCIDvalue which is not configured,the MAC entity shall at least:

[0364] 1>discard the received subPDU.

[0365] When a MAC entity receives a MAC PDU for the MAC entity's RNTI, or by the configured downlink assignment, containing an LCID or eLCID value associated with a suspended RB as specified in TS 38.331[5], the MAC entityshall at least:

[0366] 1>discard the received subPDU.

[0367] When a MAC entity receives a MAC PDU on SL-SCH containing a ReservedLCID value for broadcast or groupcast,or an LCID value which is notconfigured,the MAC entity shall:

[0368] 1>discard the received subPDU.

[0369] When a MAC entity receives a MAC PDU on SL-SCH containing a ReservedLCID value for unicast, the MAC entity shall:

[0370] 1>discard the received subPDU and any remaining subPDUs in the MACPDU.

[0371] As an embodiment, compared with the prior art, the above method is helpful in reducing the triggering conditions for discarding a MAC subPDU.

[0372] As an embodiment, the above method is helpful to reduce the complexity of UE implementation compared with the prior art.

[0373] As an embodiment, the above method is helpful in simplifying the complexity of protocol implementation compared with the prior art.

[0374] As an embodiment, the above method is more conducive to forward compatibility compared with the prior art.

[0375] As an embodiment, the above method is more conducive to backward compatibility compared with the prior art.

[0376] As an embodiment, the above method is advantageous for forward compatibility and backward compatibility compared with the prior art.

[0377] As an embodiment, the above method is helpful to reduce standardization work compared with the prior art.

[0378] As an embodiment, the above method is advantageous in supporting a wider range of scenarios compared with the prior art.

[0379] Example 8

[0380] Embodiment 8 illustrates a structural block diagram of a processing device used in a first node according to an embodiment of the present application; Figure 8 As shown in the attached Figure 8 In the example, the processing device 800 in the first node includes a first processor 801 .

[0381] The first processor 1001 receives a first MAC PDU; in response to the first MAC PDU being received, discards a first MAC subPDU;

[0382] The discarding of the first MAC subPDU depends only on the value of the logical channel identifier associated with the suspended radio bearer included in the first MAC PDU.

[0383] As an embodiment, the discarding of the first MAC subPDU depends only on the first MAC PDU including the value of the logical channel identifier associated with the suspended radio bearer, which means: when the first MAC PDU includes the value of the logical channel identifier associated with the suspended radio bearer, the first MAC subPDU is discarded.

[0384] As an embodiment, the discarding of the first MAC subPDU depends only on the value of the logical channel identifier associated with the suspended radio bearer included in the first MAC PDU, including: the discarding of the first MAC subPDU is independent of the type of RNTI used to receive the first MAC PDU.

[0385] As an embodiment, discarding the first MAC subPDU is based on protocol provisions.

[0386] As an embodiment, the discarding of the first MAC subPDU is implemented based on UE.

[0387] As an embodiment, the suspended radio bearer is any one of DRB, SRB or MRB.

[0388] As an embodiment, the first processor 1001 includes the first MAC entity.

[0389] As an embodiment, the first processor 1001 is the first MAC entity.

[0390] As an embodiment, the first processor 1001 includes a first receiver.

[0391] As an embodiment, the first receiver 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.

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

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

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

Claims

1. A first node used for wireless communication, characterized in that: include: A first processor receives a first MAC PDU; In response to receiving the first MAC PDU, discarding the first MACsubPDU; The discarding of the first MAC subPDU depends only on the value of the logical channel identifier associated with the suspended radio bearer included in the first MAC PDU.

2. The first node according to claim 1, characterized in that: The discarding of the first MAC subPDU depends only on the first MAC PDU including the value of the logical channel identifier associated with the suspended radio bearer, which means that when the first MAC PDU includes the value of the logical channel identifier associated with the suspended radio bearer, the first MAC subPDU is discarded.

3. The first node according to claim 1 or 2, characterized in that: The discarding of the first MAC subPDU depends only on the value of the logical channel identifier associated with the suspended radio bearer included in the first MAC PDU, including: the discarding of the first MAC subPDU is independent of the type of RNTI used to receive the first MAC PDU.

4. The first node according to any one of claims 1 to 3, characterized in that: The discarding of the first MACsubPDU depends only on the value of the logical channel identifier associated with the suspended radio bearer included in the first MAC PDU, including: the discarding of the first MAC subPDU is irrelevant to whether the first MAC PDU is received via unicast or multicast.

5. The first node according to any one of claims 1 to 4, characterized in that: The suspended radio bearer is any one of DRB, SRB or MRB.

6. A method in a first node for wireless communication, characterized in that: include: receiving a first MAC PDU; In response to receiving the first MAC PDU, discarding the first MAC subPDU; The discarding of the first MAC subPDU depends only on the value of the logical channel identifier associated with the suspended radio bearer included in the first MAC PDU.

Images