CN118301764A

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

Info

Publication number: CN118301764A
Application number: CN202310008106.5A
Authority: CN
Inventors: 于巧玲; 张晓博
Original assignee: Shanghai Langbo Communication Technology Co Ltd
Current assignee: Shanghai Langbo Communication Technology Co Ltd
Priority date: 2023-01-04
Filing date: 2023-01-04
Publication date: 2024-07-05

Abstract

A method and apparatus in a communication node for wireless communication is disclosed. The communication node transmitting a first uplink grant; receiving a first MAC pdu on the first uplink grant, the first MAC pdu comprising first MAC signaling; the first MAC pdu comprising a size of padding bits in the first MAC signaling dependent on the first uplink grant of less than X1 bytes, the X1 being a positive integer; the first MAC signaling is composed of at least one of a first MAC sub-header or a first MAC ce; the first MAC signaling is used to indicate uplink data to be processed. The scheme provided by the application can timely indicate the uplink data to be processed to request the resource for sending, thereby shortening the scheduling time delay.

Description

Method and apparatus in a communication node for wireless communication

Technical Field

The present application relates to a transmission method and apparatus in a wireless communication system, and to a method and apparatus for reporting a buffer status.

Background

Future wireless communication systems have more and more diversified application scenes, and different application scenes have different performance requirements on the system. In order to meet different performance requirements of various application scenarios, WI (WorkItem ) of "XR (ExtendedReality) enhancements (XREnhancementsforNR) for NR (NewRadio, new air interface)" is passed through in 3GPP (3 rdGenerationPartnerProject, third generation partnership project) RAN (radio access network) #98, where enhancement of data buffer reporting (BufferStatusReporting, BSR) is an important research direction.

Disclosure of Invention

XR services include VR (Virtualreality ) services, AR (Augmentedreality, augmented reality) and MR (Mixed reality) services, and the like, and have the characteristics of high speed and low time delay, and are interactive services, and strict requirements are set on response time of the services, for example, gesture information of a user is transmitted to a server, and pictures fed back by the server need to be presented on a terminal of the user in a short time, otherwise, the user can feel obvious time delay, and experience of the user is affected. XR services include various data, such as video, audio, data for controlling various sensors, etc., which have certain dependencies, and one packet with a dependency may be discarded from another packet. In the prior art, when an uplink grant is allocated, if the size of the padding bit (paddingbits) is equal to or greater than BufferStatusReportMACCE plus the size of its MAC sub-header (subheader), one PaddingBSR is triggered, and when more than 1 LCG (LogicalChannelGroup ) has data available for transmission, if the size of the padding bit (paddingbits) is equal to BufferStatusReportMACCE plus the size of its MAC sub-header (subheader), the LCG to which the highest priority logical channel of the data available for transmission belongs is reported in ShortTruncatedBSR MACCE. The inventors found how to guarantee that the reporting of the buffer status for XR needs to be enhanced due to the larger size of the data packet of XR and the greater sensitivity to delay.

Aiming at the problems, the application provides a solution for reporting the buffer status. In the description of the above problems, XR service is taken as an example; the application is equally applicable to scenarios such as other high data rate services; further, although the present application provides a specific embodiment for NR, the present application can also be used in, for example, LTE (Long-term evolution) scenarios, to achieve technical effects similar to NR. Further, while the present application is initially directed to Uu air interfaces, the present application can also be used for PC5 interfaces. Further, although the present application is initially directed to a terminal and base station scenario, the present application is also applicable to a V2X (Vehicle-to-internet) scenario, a communication scenario between a terminal and a relay, and a communication scenario between a relay and a base station, and similar technical effects in the terminal and base station scenario are obtained. Further, although the present application is initially directed to a terminal and base station scenario, the present application is also applicable to an IAB (INTEGRATEDACCESSAND BACKHAUL ) communication scenario, and achieves similar technical effects in a terminal and base station scenario. Further, although the present application is initially directed to a terrestrial network (TerrestrialNetwork ) scenario, the present application is equally applicable to a Non-terrestrial network (Non-TerrestrialNetwork, NTN) communication scenario, achieving similar technical effects in a TN scenario. Furthermore, the adoption of a unified solution for different scenarios also helps to reduce hardware complexity and cost.

As an embodiment, the term (Terminology) in the present application is explained with reference to the definition of the 3GPP specification protocol TS36 series.

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

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

As one example, the explanation of terms in the present application refers to the definition of the specification protocol of IEEE (InstituteofElectricalandElectronics Engineers ).

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

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

receiving a first uplink grant (afirstuplinkgrant);

transmitting a first MAC (MediumAccessControl ) PDU (Protocol DataUnit, protocol data unit) on the first uplink grant, the first MAC PDU comprising first MAC signaling;

Wherein the first MAC pdu comprises a size of padding bits (padding bits) in the first MAC signaling dependent on the first uplink grant of less than X1 bytes, the X1 being a positive integer; the first MAC signaling is comprised of at least one of a first MAC subheader (subheader) or a first MAC ce (ControlElement ); the first MAC signaling is used to indicate uplink data to be processed.

As one embodiment, the problems to be solved by the present application include: how to send the buffer status report.

As one embodiment, the problems to be solved by the present application include: how to shorten the scheduling delay.

As one embodiment, the features of the above method include: the first MAC signaling is comprised of a first MAC subheader.

As one embodiment, the features of the above method include: the first MAC signaling is comprised of a first MACCE.

As one embodiment, the features of the above method include: the first MAC signaling is composed of a first MAC subheader and a first MAC ce.

As one example, the benefits of the above method include: the filler bits are fully utilized.

As one example, the benefits of the above method include: uplink data to be processed is indicated as much as possible to request resources for transmission.

As one example, the benefits of the above method include: and the scheduling time delay is shortened.

According to an aspect of the present application, the first MAC signaling is composed of the first MAC sub-header, which includes a first LCID (LogicalChannelID, logical channel identification) field, which is used to indicate uplink data to be processed.

According to an aspect of the application, the first MAC sub-header comprises a first field, which is used to indicate the amount of uplink data to be processed.

According to an aspect of the present application, the first MAC signaling consists of the first MAC ce; the first MACCE includes a first buffer size field that is used to indicate a data amount of uplink data to be processed.

According to an aspect of the application, it is characterized in that the most significant bit in the first MAC signaling is set to 1.

According to one aspect of the application, the first MACCE is comprised of a first LCGID field and a first buffer size field, the first buffer size field being used to indicate a data amount of uplink data to be processed for at least a first logical channel (LogicalChannel).

According to one aspect of the application, the first logical channel belongs to a first LCG; the first LCGID domain indicates a second LCG; the LCGID of the first LCG and the LCGID of the second LCG are different.

As one embodiment, the features of the above method include: the first MACCE includes a first buffer size field that is used to indicate a data amount of uplink data to be processed and the first LCGID field that indicates a second LCG.

As one example, the benefits of the above method include: the priority of the resource request is increased, so that the first node is allocated with the resources as preferentially as possible.

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

Receiving a second uplink grant;

Transmitting a second MAC pdu on the second uplink grant, the second MAC pdu comprising second MAC signaling;

Wherein the second MAC pdu comprises a size of padding bits in the second MAC signaling dependent on the first uplink grant greater than X2 bytes, the X2 being an integer greater than the X1; the second MAC signaling is composed of a second MAC subheader and a second MACCE; the second MAC signaling is used to indicate uplink data to be processed.

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

Transmitting a first uplink grant;

receiving a first MAC pdu on the first uplink grant, the first MAC pdu comprising first MAC signaling;

wherein the first MAC pdu comprises a size of the first MAC signaling dependent on padding bits in the first uplink grant of less than X1 bytes, the X1 being a positive integer; the first MAC signaling is composed of at least one of a first MAC sub-header or a first MAC ce; the first MAC signaling is used to indicate uplink data to be processed.

According to an aspect of the application, the first MAC signaling consists of the first MAC sub-header comprising a first LCID field, which is used to indicate uplink data to be processed.

According to an aspect of the application, the first MACCE is comprised of a first LCGID field and a first buffer size field, the first buffer size field being used to indicate a data amount of uplink data to be processed for at least a first logical channel.

Transmitting a second uplink grant;

receiving a second MAC pdu on the second uplink grant, the second MAC pdu comprising second MAC signaling;

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

a first receiver that receives a first uplink grant;

A first transmitter to transmit a first MAC pdu on the first uplink grant, the first MAC pdu comprising a first MAC signaling;

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

a second transmitter transmitting a first uplink grant;

A second receiver that receives a first MAC pdu on the first uplink grant, the first MAC pdu comprising a first MAC signaling;

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

fully utilizing the filling bits;

indicating as much as possible uplink data to be processed to request resources for transmission;

shorten the scheduling delay.

Drawings

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

Fig. 1 shows a flow chart of a first uplink grant and transmission of a first mac pdu in accordance with one embodiment of the present application;

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

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

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

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

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

fig. 7 shows a schematic diagram of a first MAC signaling consisting of the first MAC subheader according to an embodiment of the application;

Fig. 8 shows a schematic diagram of a first field included in a first MAC sub-header being used to indicate a data amount of uplink data to be processed according to an embodiment of the present application;

Fig. 9 shows a schematic diagram of a first MAC signaling consisting of the first MAC ce according to an embodiment of the present application;

fig. 10 shows a schematic diagram in which the most significant bit in the first MAC signaling is set to 1 according to an embodiment of the present application;

FIG. 11 is a schematic diagram showing a first MACCE consisting of a first LCGID field and a first cache size field, according to one embodiment of the application;

fig. 12 shows a schematic diagram of a first logical channel belonging to a first LCG and a first LCGID domain indicating a second LCG according to one embodiment of the application;

Fig. 13 shows a schematic diagram of a location of a first MAC signaling in a first MAC pdu according to an embodiment of the application;

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

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

Fig. 16 shows a schematic diagram of a first MACCE consisting of at least the former in a first bit map or cache size field, according to one embodiment of the application.

Detailed Description

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

Example 1

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

In embodiment 1, a first node in the present application receives a first uplink grant in step 101; in step 102, a first MAC pdu is sent on the first uplink grant, the first MAC pdu comprising first MAC signaling; wherein the first MAC pdu comprises a size of the first MAC signaling dependent on padding bits in the first uplink grant of less than X1 bytes, the X1 being a positive integer; the first MAC signaling is composed of at least one of a first MAC sub-header or a first MAC ce; the first MAC signaling is used to indicate uplink data to be processed.

As an embodiment, the first uplink grant is an Uplink (UL) grant.

As one embodiment, the first uplink grant is ULgrant received dynamically on a PDCCH (Physicaldownlinkcontrolchannel ).

As an embodiment, the first uplink grant is received ULgrant in a random access response of a random access procedure.

As an embodiment, the first uplink grant is ULgrant configured by RRC (RadioResourceControl ) semi-persistent (configuredsemi-PERSISTENTLY).

As an embodiment, the first uplink grant is ULgrant determined by MSGA (MessageA ) associated PUSCH (Physical UplinkSharedChannel ) resources.

As an embodiment, the first uplink grant includes time domain resources and frequency domain resources.

As an embodiment, the first uplink grant is a PUSCH resource.

As an embodiment, the first uplink grant is an UL-SCH (UplinkSharedChannel ) resource.

As an embodiment, the first uplink grant is a PSSCH (PHYSICALSIDELINKSHAREDCHANNEL ) resource.

As an embodiment, the first uplink grant is a SL-SCH (SIDELINKSHAREDCHANNEL ) resource.

As an embodiment, the first uplink grant is an UL-SCH resource available for a new transmission.

As an embodiment, the first uplink grant is a SL-SCH resource that is available for a new transmission.

As one embodiment, the act of transmitting the first mac pdu on the first uplink grant comprises: the physical layer is instructed to generate a transmission (instructthephysicallayertogenerateatransmissionaccording tothefirstuplinkgrant) based on the first uplink grant.

As one embodiment, the act of transmitting the first mac pdu on the first uplink grant comprises: and sending the first MAPDU according to the first uplink grant.

As one embodiment, the act of transmitting the first mac pdu on the first uplink grant comprises: and transmitting the first MAPDU on the time-frequency resource granted by the first uplink.

As an embodiment, the first mac pdu is a mac pdu.

As an embodiment, only one MACsubPDU (sub-PDU) is included in the first mac PDU.

As an embodiment, the first MAC pdu includes only the first MAC signaling, and the only one MACsubPDU is the first MAC signaling.

As an embodiment, the first MAC pdu includes a plurality MACsubPDU therein, and the first MAC signaling is one MACsubPDU of the plurality MACsubPDU.

As an embodiment, padding (Padding) bits are not included in the first mac pdu.

As an embodiment, the first mac pdu includes padding bits.

As an embodiment, the first MAC pdu includes one MAC subheader with LCID set to 63.

As an embodiment, the MAC subheader with LCID set to 63 is not included in the first MAC pdu.

As an embodiment, the first MAC signaling in the first MAC pdu does not include a MAC subheader after the first MAC signaling with LCID set to any value other than 63.

As an embodiment, the first MAC signaling is one MACsubPDU.

As an embodiment, the first MAC signaling is one MACsubPDU of the first MAC pdus.

As an embodiment, the first MAC signaling is the first MAC pdu.

As an embodiment, the first MAC signaling is the last MACsubPDU of the first MAC pdu.

As an embodiment, the first MAC signaling is the next to last MACsubPDU in the first MAC pdu.

As an embodiment, the first MAC signaling occupies the lowest bit of the first MAC pdu.

As an embodiment, the padding bits of the first uplink grant refer to: the first uplink grant is allocated with padding bits.

As an embodiment, the padding bits of the first uplink grant refer to: for the first uplink grant, the remaining bits after the LCP (LogicalChannelPrioritization ) procedure.

As an embodiment, the padding bits of the first uplink grant refer to: for the first uplink grant, the remaining bits after the LCP procedure.

As an embodiment, the phrase that the first MAC pdu includes that the first MAC signaling depends on the first uplink grant has a size of less than X1 bytes includes: the first MAC pdu includes a size of the first MAC signaling padding bits equal to (X1-1) bytes depending on the first uplink grant.

As an embodiment, the phrase that the first MAC pdu includes that the first MAC signaling depends on the first uplink grant has a size of less than X1 bytes includes: at least the size of the padding bits of the first uplink grant is less than the X1 bytes used to determine that the first MAC pdu includes the first MAC signaling.

As an embodiment, the phrase that the first MAC pdu includes that the first MAC signaling depends on the first uplink grant has a size of less than X1 bytes includes: the first MAC pdu includes that the first MAC signaling relates to a size of the first uplink grant padding bits of less than X1 bytes.

As an embodiment, the phrase that the first MAC pdu includes that the first MAC signaling depends on the first uplink grant has a size of less than X1 bytes includes: the first MAC pdu includes the first MAC signaling when a size of the padding bits of the first uplink grant is less than the X1 bytes.

As an embodiment, said X1 is equal to 2.

As a sub-embodiment of this embodiment, the phrase that the first MAC pdu includes that the first MAC signaling depends on the size of the padding bits of the first uplink grant being less than X1 bytes means that: the first MAC pdu includes the first MAC signaling being less than 2 bytes depending on the size of the padding bits in the first uplink grant.

As a sub-embodiment of this embodiment, the phrase that the first MAC pdu includes that the first MAC signaling depends on the size of the padding bits of the first uplink grant being less than X1 bytes means that: the first MAC pdu includes that the first MAC signaling depends on a size of a padding bit in the first uplink grant equal to 1 byte.

As a sub-embodiment of this embodiment, the X1 is ShortBSR plus the size (thesize oftheShortBSRplusitssubheader) of its MAC subheader (subheader).

As a sub-embodiment of this embodiment, X1 is ShortBSR for XR plus the size of its MAC sub-header.

As a sub-embodiment of this embodiment, the X1 is the first byte of ShortBSR for XR plus the size of its MAC sub-header.

As a sub-embodiment of this embodiment, the dimensions of X1 and ShortBSR plus their MAC sub-heads are equal.

As a sub-embodiment of this embodiment, the X1 and ShortBSR for XR plus their MAC sub-header are equal in size.

As a sub-embodiment of this embodiment, the size of X1 and ShortBSR bytes for XR plus its MAC sub-header is equal.

As a sub-embodiment of this embodiment, the phrase that the first MAC pdu includes that the first MAC signaling depends on the size of the padding bits of the first uplink grant being less than X1 bytes means that: the first MAC pdu includes that the first MAC signaling depends on the size of the first uplink grant filler bits being less than ShortBSR plus the size of its MAC subheader.

As a sub-embodiment of this embodiment, the phrase that the first MAC pdu includes that the first MAC signaling depends on the size of the padding bits of the first uplink grant being less than X1 bytes means that: the first MAC pdu includes that the first MAC signaling depends on the size of the first uplink grant filler bits being smaller than ShortBSR for XR plus the size of its MAC subheader.

As a sub-embodiment of this embodiment, the phrase that the first MAC pdu includes that the first MAC signaling depends on the size of the padding bits of the first uplink grant being less than X1 bytes means that: the first MAC pdu includes a MAC subheader size equal to ShortBSR depending on the size of the first uplink grant filler bits.

As a sub-embodiment of this embodiment, the phrase that the first MAC pdu includes that the first MAC signaling depends on the size of the padding bits of the first uplink grant being less than X1 bytes means that: the first MAC pdu includes that the first MAC signaling relies on the size of the first uplink grant padding bits to be equal to the size of the MAC subheader ShortBSR for XR.

As a sub-embodiment of this embodiment, the phrase that the first MAC pdu includes that the first MAC signaling depends on the size of the padding bits of the first uplink grant being less than X1 bytes means that: the first MAC pdu includes a size of the first MAC signaling padding bits that is equal to ShortBSR depending on the first uplink grant.

As a sub-embodiment of this embodiment, the phrase that the first MAC pdu includes that the first MAC signaling depends on the size of the padding bits of the first uplink grant being less than X1 bytes means that: the first MAC pdu includes that the first MAC signaling depends on the size of the first uplink grant padding bits being equal to the size ShortBSR for XR.

As an embodiment, the X1 is greater than 2.

As an embodiment, said X1 is equal to 3.

As a sub-embodiment of this embodiment, the phrase that the first MAC pdu includes that the first MAC signaling depends on the size of the padding bits of the first uplink grant being less than X1 bytes means that: the first MAC pdu includes the first MAC signaling being less than 3 bytes depending on the size of the padding bits in the first uplink grant.

As a sub-embodiment of this embodiment, the phrase that the first MAC pdu includes that the first MAC signaling depends on the size of the padding bits of the first uplink grant being less than X1 bytes means that: the first MAC pdu includes that the first MAC signaling depends on a size of a padding bit in the first uplink grant equal to 2 bytes.

As a sub-embodiment of this embodiment, the minimum dimensions (the sizeoftheLongBSRplusitssubheader) of the X1 and LongBSR plus their MAC subheads (subheader) are equal.

As a sub-embodiment of this embodiment, the X1 is LongBSR plus the minimum size of its MAC subheader.

As a sub-embodiment of this embodiment, the minimum size of X1 and LongBSR for XR or LongTruncatedBSR for XR plus its MAC subheader is equal.

As a sub-embodiment of this embodiment, the X1 is LongBSR for XR or LongTruncatedBSR for XR plus the minimum size of its MAC subheader.

As a sub-embodiment of this embodiment, the size of the first uplink grant filler bits is not less than ShortBSR plus the size of its MAC subheader.

As a sub-embodiment of this embodiment, the first MAC pdu comprises a size of the first MAC signaling dependent padding bits of the first uplink grant equal to ShortBSR plus a size of its MAC sub-header.

As a sub-embodiment of this embodiment, the first MAC pdu comprises that the size of the padding bits the first MAC signaling relies on for the first uplink grant is equal to ShortBSR for XR or ShortTruncatedBSR for XR plus the size of its MAC sub-header.

As a sub-embodiment of this embodiment, the first MAC pdu comprises that the size of the padding bits in the first MAC signaling dependent on the first uplink grant is less than the X1 bytes, and the size of the padding bits of the first uplink grant is not less than ShortBSR plus the size of its MAC subheader.

As a sub-embodiment of this embodiment, the first MAC pdu comprises that the size of the padding bits in the first MAC signaling dependent on the first uplink grant is less than the X1 bytes and the size of the padding bits of the first uplink grant is not less than ShortBSR plus the size of its MAC subheader for XR.

As a sub-embodiment of this embodiment, the first MAC pdu comprises a size of the first MAC signaling padding bits dependent on the first uplink grant equal to the first byte of ShortBSR for XR plus the size of its MAC sub-header.

As an embodiment, said X1 is equal to 4.

As a sub-embodiment of this embodiment, the phrase that the first MAC pdu includes that the first MAC signaling depends on the size of the padding bits of the first uplink grant being less than X1 bytes means that: the first MAC pdu includes the first MAC signaling being less than 4 bytes depending on the size of the padding bits in the first uplink grant.

As a sub-embodiment of this embodiment, the phrase that the first MAC pdu includes that the first MAC signaling depends on the size of the padding bits of the first uplink grant being less than X1 bytes means that: the first MAC pdu includes that the first MAC signaling depends on a size of a padding bit in the first uplink grant equal to 3 bytes.

As a sub-embodiment of this embodiment, the X1 is equal to LongBSR for XR or LongTruncatedBSR for XR plus the minimum size (thesizeoftheLongBSRplusitssubheader) of its MAC subheader (subheader).

As a sub-embodiment of this embodiment, X1 is LongBSR for XR plus the minimum size of its MAC subheader.

As a sub-embodiment of this embodiment, X1 is LongTruncatedBSR for XR plus the minimum size of its MAC subheader.

As a sub-embodiment of this embodiment, the size of the first uplink grant filler bits is not less than LongBSR plus the minimum size of its MAC subheader.

As a sub-embodiment of this embodiment, the size of the first uplink grant filler bits is not less than LongTruncatedBSR plus the minimum size of its MAC subheader.

As a sub-embodiment of this embodiment, the first MAC pdu comprises a size of the first MAC signaling dependent on the padding bits of the first uplink grant not less than LongBSR plus a minimum size of its MAC subheader.

As a sub-embodiment of this embodiment, the first MAC pdu comprises a size of padding bits that the first MAC signaling relies on the first uplink grant equal to LongBSR plus a minimum size of its MAC subheader.

As a sub-embodiment of this embodiment, the first MAC pdu comprises that the size of the padding bits the first MAC signaling relies on for the first uplink grant is equal to ShortBSR for XR or LongTruncatedBSR for XR plus the size of its MAC sub-header.

As a sub-embodiment of this embodiment, the first MAC pdu comprises that the size of the padding bits in the first MAC signaling dependent on the first uplink grant is less than the X1 bytes, and the size of the padding bits of the first uplink grant is not less than LongBSR plus the minimum size of its MAC subheader.

For purposes of XR, as one example, means: enhanced for XR.

For purposes of XR, as one example, means: is used for XR.

For purposes of XR, as one example, means: XR is specific.

As an embodiment, longBSR plus the minimum size of its MAC subheader refers to: longBSR, which includes 0 BufferSize fields, plus the minimum size of its MAC subheader.

As an embodiment, longTruncatedBSR plus the minimum size of its MAC subheader refers to: longTruncatedBSR, which includes 0 BufferSize fields, plus the minimum size of its MAC subheader.

For one embodiment, longBSR for XR plus the minimum size of its MAC subheader refers to: longBSR for XR, which includes 0 BufferSize fields, plus the minimum size of its MAC subheader.

For one embodiment, longTruncatedBSR for XR plus the minimum size of its MAC subheader refers to: longTruncatedBSR for XR, including 0 Buffer Size fields, plus the minimum Size of its MAC subheader.

As an example, the length of the MAC subheader for ShortBSR of XR is 1 byte, the length of the MAC subheader for ShortTruncatedBSR of XR is 1 byte, the length of the MAC subheader for LongBSR of XR is 2 bytes, and the length of the MAC subheader for LongTruncated BSR of XR is 2 bytes.

As an example, the length of the MAC subheader for ShortBSR of XR is 1 byte, the length of the MAC subheader for ShortTruncatedBSR of XR is 1 byte, the length of the MAC subheader for LongBSR of XR is 3 bytes, and the length of the MAC subheader for LongTruncated BSR of XR is 3 bytes.

As an example, the length of the MAC subheader for ShortBSR of XR is 2 bytes, the length of the MAC subheader for ShortTruncatedBSR of XR is 1 byte, the length of the MAC subheader for LongBSR of XR is 3 bytes, and the length of the MAC subheader for LongTruncated BSR of XR is 3 bytes.

As an example, the length of the MAC subheader for ShortBSR of XR is 2 bytes, the length of the MAC subheader for ShortTruncatedBSR of XR is 2 bytes, the length of the MAC subheader for LongBSR of XR is 3 bytes, and the length of the MAC subheader for LongTruncated BSR of XR is 3 bytes.

As an example, shortBSR for XR corresponds to LCID 37 or 38 or 39 or 40 or 41 or 42; the length of the MAC subheader for ShortBSR of XR is 1 byte.

As a sub-embodiment of this embodiment, the MAC sub-header of ShortBSR for XR consists of 2R fields and 1 LCID field.

As a sub-embodiment of this embodiment, reference is made to fig. 6.1.2-3 of 3GPPTS38.321 for the structure of the MAC subheader of ShortBSR of XR.

As one example, shortBSR for XR corresponds to LCID 61; the length of the MAC subheader for ShortBSR of XR is 1 byte.

As one embodiment, eLCID (extendedLCID ) corresponding to ShortBSR for XR is an integer no less than 0 and no greater than 228; the length of the MAC subheader for ShortBSR of XR is 2 bytes.

As a sub-embodiment of this embodiment, the MAC sub-header of ShortBSR for XR consists of 2R fields, 1 LCID field and 1 eLCID field.

As an example, shortTruncatedBSR for XR corresponds to LCID 37 or 38 or 39 or 40 or 41 or 42; the length of the MAC subheader for ShortTruncatedBSR of XR is 1 byte.

As a sub-embodiment of this embodiment, the MAC sub-header of ShortTruncatedBSR for XR consists of 2R fields and 1 LCID field.

As a sub-embodiment of this embodiment, reference is made to fig. 6.1.2-3 of 3GPPTS38.321 for the structure of the MAC subheader of ShortTruncatedBSR of XR.

As one example, shortTruncatedBSR for XR corresponds to LCID 59; the length of the MAC subheader for ShortTruncatedBSR of XR is 1 byte.

As one embodiment, shortTruncatedBSR for XR corresponds to eLCID being an integer no less than 0 and no greater than 228; the length of the MAC subheader for ShortTruncatedBSR of XR is 2 bytes.

As a sub-embodiment of this embodiment, the MAC sub-header of ShortTruncatedBSR for XR consists of 2R fields, 1 LCID field and 1 eLCID field.

As an example, longBSR for XR corresponds to LCID 37 or 38 or 39 or 40 or 41 or 42; the length of the MAC subheader for LongBSR of XR is 2 bytes.

As a sub-embodiment of this embodiment, the MAC sub-header of LongBSR for XR consists of 1R field, 1F field, 1 LCID field, and 1L field.

As a sub-embodiment of this embodiment, reference is made to fig. 6.1.2-1 of 3GPPTS38.321 for the structure of the MAC sub-header of LongBSR of XR.

As one embodiment, longBSR for XR corresponds to eLCID being an integer no less than 0 and no greater than 228; the length of the MAC subheader for LongBSR of XR is 3 bytes.

As a sub-embodiment of this embodiment, the MAC sub-header of LongBSR for XR consists of 1R field, 1F field, 1 LCID field, 1 eLCID field, and 1L field.

As an example, longTruncatedBSR for XR corresponds to LCID 37 or 38 or 39 or 40 or 41 or 42; the length of the MAC subheader for LongTruncatedBSR of XR is 2 bytes.

As a sub-embodiment of this embodiment, the MAC sub-header of LongTruncatedBSR for XR consists of 1R field, 1F field, 1 LCID field, and 1L field.

As a sub-embodiment of this embodiment, reference is made to fig. 6.1.2-1 of 3GPPTS38.321 for the structure of the MAC sub-header of LongTruncatedBSR of XR.

As one embodiment, longTruncatedBSR for XR corresponds to eLCID being an integer no less than 0 and no greater than 228; the length of the MAC subheader for LongTruncatedBSR of XR is 3 bytes.

As a sub-embodiment of this embodiment, the MAC sub-header of LongTruncatedBSR for XR consists of 1R field, 1F field, 1 LCID field, 1 eLCID field, and 1L field.

As an embodiment, the LCID corresponding to one BSR refers to: the value of the LCID field in the MAC subheader of the one BSR.

As an embodiment, the LCID corresponding to one BSR refers to: the code point (codepoint) of the LCID corresponding to the one BSR.

As an embodiment, the LCID corresponding to one BSR refers to: an index (index) of the LCID corresponding to the one BSR.

As an embodiment, eLCID corresponding to one BSR refers to: the value of eLCID fields in the MAC subheader of the one BSR.

As an embodiment, eLCID corresponding to one BSR refers to: the code point of eLCID corresponding to the one BSR (codepoint).

As an embodiment, the first MAC signaling consists of both the first MAC subheader and the first MAC ce.

As a sub-embodiment of this embodiment, said X1 is greater than 2.

As a sub-embodiment of this embodiment, said X1 is equal to 3.

As a sub-embodiment of this embodiment, said X1 is equal to 4.

As a sub-embodiment of this embodiment, said X1 is equal to 5.

As a sub-embodiment of this embodiment, the first MAC signaling is one MACsubPDU.

As a sub-embodiment of this embodiment, the first MAC sub-header and the first MAC ce belong to the same MACsubPDU.

As a sub-embodiment of this embodiment, the first MAC sub-header indicates the first MAC ce.

As a sub-embodiment of this embodiment, the first MAC sub-header is a MAC sub-header of the first MAC ce.

As a sub-embodiment of this embodiment, the first MAC sub-header is located immediately before the first MAC ce.

As a sub-embodiment of this embodiment, the first MAC ce is ShortBSR and the first MAC sub-header is a MAC sub-header of ShortBSR.

As a sub-embodiment of this embodiment, the first MAC ce is ShortBSR for XR and the first MAC subheader is a ShortBSR MAC subheader for XR.

As a sub-embodiment of this embodiment, the first MAC ce is ShortTruncatedBSR for XR and the first MAC subheader is a ShortTruncatedBSR MAC subheader for XR.

As a sub-embodiment of this embodiment, the first MAC ce is LongBSR for XR and the first MAC subheader is a LongBSR MAC subheader for XR.

As a sub-embodiment of this embodiment, the first MAC ce is LongTruncatedBSR for XR and the first MAC subheader is a LongTruncatedBSR MAC subheader for XR.

As a sub-embodiment of this embodiment, a first padding BSR is triggered when the first uplink grant is allocated and the size of the padding bits of the first uplink grant is not less than 2 bytes.

As a sub-embodiment of this embodiment, a first padding BSR is triggered when the first uplink grant is allocated and the size of the padding bits of the first uplink grant is equal to or greater than BSRMACCE plus the size of its MAC subheader.

As a sub-embodiment of this embodiment, the first padding BSR is one PaddingBSR.

As a sub-embodiment of this embodiment, the first padding BSR is an enhancement PaddingBSR.

As a sub-embodiment of this embodiment, the first padding BSR is one PaddingBSR for XR.

As one embodiment, the first MAC signaling consists of one of the first MAC subheader or the first MAC ce.

As a sub-embodiment of this embodiment, said X1 is equal to 2.

As a sub-embodiment of this embodiment, the first MAC signaling is comprised of the first MAC sub-header.

As a sub-embodiment of this embodiment, the first MAC signaling consists of the first MAC ce.

As a sub-embodiment of this embodiment, the size of the first MAC signaling is equal to 1 byte.

As a sub-embodiment of this embodiment, the first MAC signaling is not MACsubPDU.

As a sub-embodiment of this embodiment, the first MAC signaling does not belong to any MACsubPDU.

As a sub-embodiment of this embodiment, the first MAC signaling is a MAC ce.

As a sub-embodiment of this embodiment, the first MAC signaling is a MAC sub-header.

As a sub-embodiment of this embodiment, the first MAC signaling is one MAC ce and the one MAC ce does not include a MAC sub-header.

As a sub-embodiment of this embodiment, the first MAC signaling is one MAC sub-header, and the one MAC sub-header does not indicate any MAC ce.

As a sub-embodiment of this embodiment, the first MAC signaling is one MAC sub-header, and the one MAC sub-header indicates one MACCE of which size is equal to 0 bytes.

As a sub-embodiment of this embodiment, either BSR is not triggered when the first uplink grant is allocated and the size of the padding bits of the first uplink grant is less than 2 bytes.

As a sub-embodiment of this embodiment, a first padding BSR is triggered when the first uplink grant is allocated and the size of the padding bits of the first uplink grant is equal to 1 byte.

As a sub-embodiment of this embodiment, the first uplink grant is allocated and a size of padding bits of the first uplink grant equal to 1 byte is used to trigger the first padding BSR.

As a sub-embodiment of this embodiment, the first uplink grant is allocated and a size of padding bits of the first uplink grant equal to or greater than 1 byte is used to trigger the first padding BSR.

As a sub-embodiment of this embodiment, the first padding BSR is one PaddingBSR triggered by the logical channel used for XR.

As an embodiment, the first MAC signaling is a BSRMACCE used to indicate uplink data to be processed.

As an embodiment, the type of the first MAC signaling is used to indicate uplink data to be processed.

As an embodiment, the LCID field of the first MAC signaling is used to indicate uplink data to be processed.

As an embodiment, eLCID fields of the first MAC signaling are used to indicate uplink data to be processed.

As an embodiment, the MAC subheader in the first MAC signaling is used to indicate uplink data to be processed.

As an embodiment, the BufferSize field in the first MAC signaling is used to indicate uplink data to be processed.

As an embodiment, the LCGID field in the first MAC signaling is used to indicate uplink data to be processed.

As an embodiment, the LCG _i field in the first MAC signaling is used to indicate uplink data to be processed.

As an embodiment, the uplink data to be processed means: data (dataavailablefor transmission) available for transmission.

As an embodiment, the uplink data to be processed means: available data (availabledata).

As an embodiment, the uplink data to be processed means: expected data.

As an embodiment, the uplink data to be processed means: cached data.

As an embodiment, the uplink data to be processed includes a packet of a PDCP sublayer.

As an embodiment, the uplink data to be processed includes a data packet of an RLC sublayer.

As an embodiment, uplink data to be processed by one LCG means: at least one logical channel in the one LCG has uplink data to be processed.

As one embodiment, an LCG includes one or more logical channels.

As an embodiment, the logical channels included in one LCG are configured through an RRC (RadioResourceControl ) message.

Example 2

Embodiment 2 illustrates a schematic diagram of a network architecture according to one embodiment of the application, as shown in fig. 2. Fig. 2 illustrates a network architecture 200 of a 5GNR (NewRadio, new air interface)/LTE (Long-term evolution)/LTE-a (Long-TermEvolutionAdvanced, enhanced Long-term evolution) system. The 5 GNR/LTE-a network architecture 200 may be referred to as 5GS (5 GSystem)/EPS (Evolved PacketSystem ) 200, or some other suitable terminology. The 5GS/EPS200 includes at least one of a UE (user equipment) 201, a ran (radio access network) 202,5GC (5 g core network)/EPC (EvolvedPacketCore ) 210, an hss (HomeSubscriberServer, home subscriber server)/UDM (UnifiedDataManagement ) 220, and an internet service 230. The 5GS/EPS may interconnect with other access networks, but these entities/interfaces are not shown for simplicity. As shown, 5GS/EPS provides packet switched services, however, those skilled in the art will readily appreciate that the various concepts presented throughout this disclosure may be extended to networks providing circuit switched services or other cellular networks. The RAN includes node 203 and other nodes 204. Node 203 provides user and control plane protocol termination towards UE 201. Node 203 may be connected to other nodes 204 via an Xn interface (e.g., backhaul)/X2 interface. Node 203 may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a Basic Service Set (BSS), an Extended Service Set (ESS), a TRP (transmit receive node), or some other suitable terminology. The node 203 provides the UE201 with an access point to the 5GC/EPC 210. Examples of UE201 include a cellular telephone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a Personal Digital Assistant (PDA), a satellite radio, a non-terrestrial base station communication, a satellite mobile communication, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, an drone, an aircraft, a narrowband internet of things device, a machine-type communication device, a land-based vehicle, an automobile, a wearable device, or any other similar functional device. Those of skill in the art may also refer to the UE201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. The node 203 is connected to the 5GC/EPC210 through an S1/NG interface. The 5GC/EPC210 includes MME (MobilityManagementEntity )/AMF (AuthenticationManagement Field, authentication management domain)/SMF (SessionManagementFunction ) 211, other MME/AMF/SMF214, S-GW (SERVICEGATEWAY, serving gateway)/UPF (UserPlaneFunction ) 212 and P-GW (Packet DateNetworkGateway, Packet data network gateway)/UPF 213. The MME/AMF/SMF211 is a control node that handles signaling between the UE201 and the 5GC/EPC 210. In general, the MME/AMF/SMF211 provides bearer and connection management. All user IP (InternetProtocal, internet protocol) packets are transported through the S-GW/UPF212, which S-GW/UPF212 itself is connected to the P-GW/UPF213. The P-GW provides UEIP address allocation as well as other functions. The P-GW/UPF213 is connected to the internet service 230. Internet services 230 include operator-corresponding internet protocol services, which may include, in particular, the internet, intranets, IMS (IPMultimediaSubsystem ) and packet-switched streaming services.

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

As an embodiment, the UE201 is a user equipment (UserEquipment, UE).

As an embodiment, the UE201 is a Base Station (BS).

As an embodiment, the UE201 is a relay device.

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

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

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

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

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

As one embodiment, the user equipment supports transmission of a terrestrial network (Non-TerrestrialNetwork, NTN).

As one embodiment, the user equipment supports transmission of a non-terrestrial network (TerrestrialNetwork ).

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

As one embodiment, the user equipment supports dual connectivity (DualConnection, DC) transmissions.

As an embodiment, the user equipment comprises a handheld terminal.

As an embodiment, the user device comprises a wearable device.

As an embodiment, the user device comprises an aircraft.

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

As an embodiment, the user equipment comprises a watercraft.

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

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

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

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

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

As an embodiment, the base station apparatus comprises a base transceiver station (BaseTransceiverStation, BTS).

As an embodiment, the base station device comprises a node B (NodeB, NB).

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

As an embodiment, the base station device comprises an eNB.

As an embodiment, the base station device comprises a ng-eNB.

As an embodiment, the base station device comprises an en-gNB.

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

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

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

As an embodiment, the base station device comprises a macro cell (MarcoCellular) base station.

As an embodiment, the base station device comprises a micro cell (MicroCell) base station.

As one embodiment, the base station apparatus includes a pico cell (PicoCell) base station.

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

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

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

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

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

As an embodiment, the base station device comprises a CU (CentralizedUnit, concentration unit).

As an embodiment, the base station device comprises a DU (DistributedUnit, distribution unit).

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

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

As an embodiment, the base station device comprises a IAB (IntegratedAccessandBackhaul) -node.

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

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

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

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

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

As an embodiment, the relay device comprises a relay.

As an embodiment, the relay device comprises an L3relay.

As an embodiment, the relay device comprises an L2relay.

As an embodiment, the relay device comprises a router.

As an embodiment, the relay device comprises a switch.

As an embodiment, the relay device comprises a user equipment.

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

Example 3

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

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

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

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

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

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

As an embodiment, the first MAC pdu of the present application is generated in the MAC302 or the MAC352.

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

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

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

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

As an embodiment, the second MAC pdu of the present application is generated in the MAC302 or the MAC352.

Example 4

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

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

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

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

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

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

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

As an embodiment, the first communication device 450 includes: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code are configured to, with the at least one processor, the first communication device 450 at least: receiving a first uplink grant; transmitting a first MAC PDU on the first uplink grant, the first MAC PDU comprising first MAC signaling; wherein the first MAC pdu comprises a size of the first MAC signaling dependent on padding bits in the first uplink grant of less than X1 bytes, the X1 being a positive integer; the first MAC signaling is composed of at least one of a first MAC sub-header or a first MAC ce; the first MAC signaling is used to indicate uplink data to be processed.

As an embodiment, the first communication device 450 includes: a memory storing a program of computer-readable instructions that, when executed by at least one processor, produce acts comprising: receiving a first uplink grant; transmitting a first MAC pdu on the first uplink grant, the first MAC pdu comprising first MAC signaling; wherein the first MAC pdu comprises a size of the first MAC signaling dependent on padding bits in the first uplink grant of less than X1 bytes, the X1 being a positive integer; the first MAC signaling is composed of at least one of a first MAC sub-header or a first MAC ce; the first MAC signaling is used to indicate uplink data to be processed.

As one embodiment, the second communication device 410 includes: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code are configured for use with the at least one processor. The second communication device 410 at least: transmitting a first uplink grant; receiving a first MAC PDU on the first uplink grant, the first MAC PDU comprising first MAC signaling; wherein the first MAC pdu comprises a size of the first MAC signaling dependent on padding bits in the first uplink grant of less than X1 bytes, the X1 being a positive integer; the first MAC signaling is composed of at least one of a first MAC sub-header or a first MAC ce; the first MAC signaling is used to indicate uplink data to be processed.

As one embodiment, the second communication device 410 includes: a memory storing a program of computer-readable instructions that, when executed by at least one processor, produce acts comprising: transmitting a first uplink grant; receiving a first MAC pdu on the first uplink grant, the first MAC pdu comprising first MAC signaling; wherein the first MAC pdu comprises a size of the first MAC signaling dependent on padding bits in the first uplink grant of less than X1 bytes, the X1 being a positive integer; the first MAC signaling is composed of at least one of a first MAC sub-header or a first MAC ce; the first MAC signaling is used to indicate uplink data to be processed.

As an embodiment, at least one of the antenna 452, the receiver 454, the receive processor 456, and the controller/processor 459 is configured to receive a first uplink grant.

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

As an embodiment, at least one of the antenna 452, the receiver 454, the receive processor 456, and the controller/processor 459 is configured to receive a second uplink grant.

As one embodiment, the antenna 420, the transmitter 418, the transmit processor 416, and at least one of the controller/processors 475 are used to transmit a second uplink grant.

As one example, the antenna 452, the transmitter 454, the transmit processor 468, and at least one of the controller/processor 459 is used to transmit a first mac pdu.

As an example, at least one of the antenna 420, the receiver 418, the receive processor 470, and the controller/processor 475 is configured to receive a first mac pdu.

As one example, the antenna 452, the transmitter 454, the transmit processor 468, and at least one of the controller/processor 459 is used to transmit a second mac pdu.

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

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

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

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

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

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

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

Example 5

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

For the first node U01, in step S5101, a first uplink grant is received; in step S5102, a first MAC pdu is transmitted on the first uplink grant, the first MAC pdu including first MAC signaling.

For the second node N02, in step S5201, the first uplink grant is sent; in step S5202, the first mac pdu is received.

In embodiment 5, the first MAC pdu comprises the first MAC signaling relying on the size of the padding bits in the first uplink grant being less than X1 bytes, the X1 being a positive integer; the first MAC signaling is composed of at least one of a first MAC sub-header or a first MAC ce; the first MAC signaling is used to indicate uplink data to be processed.

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

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

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

As an embodiment, the first node U01 supports at least 3GPPRELEASE s 18.

As an embodiment, any logical channel in the first node U01 is not used for XR.

As an embodiment, at least one logical channel in the first node U01 is used for XR.

As one embodiment, a logical channel is used for XR comprising: the one logical channel is allocated to XR.

As one embodiment, a logical channel is used for XR comprising: the one logical channel can be used for XR.

As one embodiment, a logical channel is used for XR comprising: the one logical channel is indicated XR.

As one embodiment, a logical channel is used for XR comprising: the DRB associated with the one logical channel is used for XR.

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

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

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

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

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

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

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

As an embodiment, the first node U01 is a relay device, and the second node N02 is a base station device.

Example 6

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

For the first node U01, in step S6101, a second uplink grant is received; in step S6102, a second MAC pdu is transmitted on the second uplink grant, the second MAC pdu comprising second MAC signaling.

For the second node N02, in step S6201, transmitting the second uplink grant; in step S6202, the second mac pdu is received.

In embodiment 6, the second MAC pdu comprises the second MAC signaling relying on the size of the padding bits in the first uplink grant being greater than X2 bytes, the X2 being an integer greater than the X1; the second MAC signaling is composed of a second MAC subheader and a second MACCE; the second MAC signaling is used to indicate uplink data to be processed.

As an embodiment, said X2 is equal to 3.

As an embodiment, said X2 is equal to 4.

As an embodiment, said X2 is equal to 5.

As an embodiment, said X2 is equal to 6.

As an embodiment, the phrase that the size of the padding bits in the first uplink grant is greater than X2 bytes means: the size of the padding bits in the first uplink grant is greater than the minimum size of the second MAC ce plus the second MAC subheader.

As an embodiment, the phrase that the size of the padding bits in the first uplink grant is greater than X2 bytes means: the size of the padding bits in the first uplink grant is equal to the minimum size of the second MAC ce plus the second MAC subheader.

As an embodiment, the phrase that the size of the padding bits in the first uplink grant is greater than X2 bytes means: the size of the padding bits in the first uplink grant is equal to or greater than the minimum size of the second MAC ce plus the second MAC subheader.

As an embodiment, the second uplink grant is one ULgrant.

As an embodiment, the second uplink grant is dynamically received ULgrant on the PDCCH.

As an embodiment, the second uplink grant is received ULgrant in a random access response of a random access procedure.

As an embodiment, the second uplink grant is configured by RRC semi-persistent ULgrant.

As an embodiment, the second uplink grant is ULgrant determined by MSGA associated PUSCH resources.

As an embodiment, the second uplink grant includes time domain resources and frequency domain resources.

As an embodiment, the second uplink grant includes PUSCH resources.

As an embodiment, the second mac pdu is sent according to the second uplink grant.

As an embodiment, the second mac pdu is sent on the time-frequency resource granted by the second uplink.

As an embodiment, the first uplink grant has a reception time earlier than the second uplink grant.

As an embodiment, the reception instant of the first uplink grant is later than the reception instant of the second uplink grant.

As one embodiment, the first uplink grant and the second uplink grant are received simultaneously.

As one embodiment, the second mac pdu is transmitted before the first mac pdu is transmitted.

As one embodiment, the second mac pdu is transmitted after the first mac pdu is transmitted.

As an embodiment, the second MAC signaling is one MACsubPDU.

As an embodiment, the second MAC subheader immediately precedes the second MAC ce.

As an embodiment, the second MAC sub-header is a MAC sub-header of the second MAC ce.

As an embodiment, the second MAC ce is ShortBSR for XR and the first MAC subheader is a ShortBSR MAC subheader for XR.

As an embodiment, the second MAC ce is ShortTruncatedBSR for XR and the first MAC subheader is a ShortTruncatedBSR MAC subheader for XR.

As an embodiment, the second MAC ce is LongBSR for XR and the first MAC subheader is a LongBSR MAC subheader for XR.

As an embodiment, the second MAC ce is LongTruncatedBSR for XR and the first MAC subheader is a LongTruncatedBSR MAC subheader for XR.

Example 7

Embodiment 7 illustrates a schematic diagram of first MAC signaling consisting of the first MAC subheader according to an embodiment of the present application, as shown in fig. 7.

In embodiment 7, the first MAC signaling is comprised of the first MAC sub-header including a first LCID field, the first LCID field being used to indicate uplink data to be processed; the X1 is equal to 2.

As an embodiment, the first MAC signaling includes a 0 byte MAC ce.

As an embodiment, the first MAC subheader indicates a MACCE of 0 bytes.

As an embodiment, the first MAC subheader indicates ShortTruncatedBSRMACCE.

As an embodiment, the first MAC subheader indicates ShortBSRMACCE.

As an embodiment, the structure of the first MAC subheader refers to fig. 6.1.2-3 of 3GPPTS38.321.

As an embodiment, the first MAC sub-header is composed of the first LCID field and 2R (Reserved) fields.

As an embodiment, the first LCID field occupies 6 bits.

As an embodiment, the first LCID field is set to 59.

As an embodiment, the first LCID field is set to 61.

As one embodiment, the first LCID field is set to an integer not less than 37 and not greater than 42.

As an embodiment, the first LCID field is set to LCID ShortTruncatedBSRMACCE.

As an embodiment, the first LCID field is set to LCID ShortBSRMACCE.

As an embodiment, the first LCID field is set to LCID ShortTruncatedBSRMACCE for XR.

As an embodiment, the first LCID field is set to LCID ShortBSRMACCE for XR.

As an embodiment, the first LCID field is set to a LCID indicating a MACCE of 0 bytes.

As an embodiment, the phrase that the first LCID field is used to indicate uplink data to be processed means that: the first LCID field indicates that one BSRMACCE is used to indicate uplink data to be processed.

As an embodiment, the phrase that the first LCID field is used to indicate uplink data to be processed means that: the value of the first LCID field is used to indicate uplink data to be processed.

As an embodiment, the phrase that the first LCID field is used to indicate uplink data to be processed means that: the first LCID field is used to indicate uplink data to be processed by at least one LCG.

As an embodiment, the phrase that the first LCID field is used to indicate uplink data to be processed means that: the first LCID field is used to indicate uplink data to be processed for at least one logical channel.

As an embodiment, the phrase that the first LCID field is used to indicate uplink data to be processed means that: the first LCID field is used to indicate at least one logical channel used for XR to be pending uplink data.

As an embodiment, the first MAC signaling is one MACsubPDU, the one MACsubPDU does not include MACCE, and the one MACsubPDU belongs to Paddingbits.

As an embodiment, the first MAC signaling is the first MAC sub-header, the first MAC sub-header belongs to Paddingbits, and the Paddingbits does not include MACCE indicated by the one MAC sub-header.

Example 8

Embodiment 8 illustrates a schematic diagram in which a first field included in a first MAC sub-header is used to indicate a data amount of uplink data to be processed according to an embodiment of the present application, as shown in fig. 8.

In embodiment 8, the first MAC sub-header includes a first field that is used to indicate the data amount of uplink data to be processed.

As an embodiment, the first MAC sub-header includes a first field that is used to indicate a data amount of uplink data to be processed; the first MAC signaling is composed of the first MAC subheader, which includes a first LCID field, which is used to indicate uplink data to be processed; the X1 is equal to 2.

As an embodiment, the first domain is an R domain.

As an embodiment, the first field occupies 1 bit.

As an embodiment, the first domain is 1R domain.

As an embodiment, the first field is the most significant bit in the first MAC subheader.

As an embodiment, the first field being set to 0 indicates that the data amount of the uplink data to be processed is not greater than the first threshold, and the first field being set to 1 indicates that the data amount of the uplink data to be processed is greater than the first threshold.

As an embodiment, the first field occupies 2 bits.

As an embodiment, the first domain is 2R domains.

As an embodiment, the first field is the most significant bit and the next most significant bit in the first MAC subheader.

As one embodiment, the first field is set to 00 indicating that the data amount of the uplink data to be processed is not greater than a first threshold, the first field is set to 01 indicating that the data amount of the uplink data to be processed is not greater than a second threshold, the first field is set to 10 indicating that the data amount of the uplink data to be processed is not greater than a third threshold, and the first field is set to 11 indicating that the data amount of the uplink data to be processed is greater than the third threshold; the first threshold is less than the second threshold, and the second threshold is less than the third threshold.

Example 9

Embodiment 9 illustrates a schematic diagram of first MAC signaling consisting of the first MAC ce according to an embodiment of the present application, as shown in fig. 9.

In embodiment 9, the first MAC signaling consists of the first MAC ce; the first MACCE includes a first buffer size field that is used to indicate a data amount of uplink data to be processed; the X1 is equal to 2.

As an embodiment, the first MACCE does not include an LCGID domain.

As an embodiment, the first MACCE comprises an LCGID domain.

As an embodiment, the first MACCE is comprised of one LCGID field and the first cache size field.

As an embodiment, the first MACCE is composed of the first LCGID field and the first buffer size field in the present application, and the first buffer size field is used to indicate a data amount of uplink data to be processed of at least a first logical channel.

As an embodiment, the one LCGID field occupies 3 bits.

As an embodiment, the one LCGID field immediately precedes the first cache size field.

As an embodiment, the first buffer size field occupies 5 bits.

As an embodiment, the first buffer size field occupies 6 bits.

As an embodiment, the first buffer size field occupies 7 bits.

As an embodiment, the first buffer size field occupies 8 bits.

As an embodiment, the first MAC signaling occupies one octet.

As an embodiment, the first MAC signaling is the first MAC ce.

As an embodiment, the first MAC signaling is MACsubPDU including only the first MAC ce.

As an embodiment, the first MAC signaling is one MACsubPDU, the one MACsubPDU does not include a MAC subheader, and the one MACsubPDU belongs to Paddingbits.

As an embodiment, the first MAC signaling is the first MAC ce, the first MAC ce belongs to Paddingbits, and the Paddingbits does not include a MAC subheader indicating the one MAC ce.

Example 10

Embodiment 10 illustrates a schematic diagram in which the most significant bit in the first MAC signaling is set to 1, as shown in fig. 10, according to an embodiment of the present application.

In embodiment 10, the first MAC signaling consists of the first MAC ce; the first MACCE includes a first buffer size field that is used to indicate a data amount of uplink data to be processed; the most significant bit in the first MAC signaling is set to 1; the X1 is equal to 2.

As an embodiment, the most significant bits in the first MAC signaling refer to most significant bits in the first MAC ce.

As an embodiment, the most significant bits in the first MAC signaling refer to most significant bits in octets occupied by the first MAC signaling.

As an embodiment, the most significant bit refers to the leftmost one bit.

As an embodiment, the most significant bit in the first MAC signaling being set to 1 is used to indicate that the first MAC signaling does not include a MAC subheader.

As an embodiment, the most significant bit in the first MAC signaling being set to 1 is used to indicate that the first MAC signaling includes the first buffer size field.

As an embodiment, the most significant bit in the first MAC signaling being set to 1 is used to indicate that the first MAC signaling is used to indicate uplink data to be processed.

As an embodiment, if the most significant bit in one MACsubPDU is set to 0, the most significant bit is reserved.

As an embodiment, if one MACsubPDU does not belong to Paddingbits, the most significant bit in said one MACsubPDU is reserved and the most significant bit in said one MACsubPDU is set to 0.

As an embodiment, if one MACsubPDU belongs to Paddingbits and the most significant bit in the one MACsubPDU is set to 0, the most significant bit in the one MACsubPDU is reserved.

As an embodiment, if one MACsubPDU belongs to Paddingbits and the most significant bit in the one MACsubPDU is set to 0, the one MACsubPDU includes one MAC subheader, the LCID field in the one MAC subheader indicating Padding.

As an embodiment, if one MACsubPDU belongs to Paddingbits and the most significant bit in the one MACsubPDU is set to 1, the one MACsubPDU does not include a MAC subheader.

As an embodiment, if one MACsubPDU belongs to Paddingbits and the most significant bit in the one MACsubPDU is set to 1, the one MACsubPDU is used to indicate uplink data to be processed.

As an example, if one MACsubPDU belongs to Paddingbits and the most significant bit in the one MACsubPDU is set to 1, the one MACsubPDU includes a cache size field.

Example 11

Embodiment 11 illustrates a schematic diagram of a first MACCE consisting of a first LCGID field and a first cache size field, as shown in fig. 11, according to one embodiment of the application.

In embodiment 11, the first MACCE consists of a first LCGID field and a first buffer size field, the first buffer size field being used to indicate a data amount of uplink data to be processed of at least a first logical channel; the first MAC signaling is composed of the first MAC subheader and the first MAC ce; the X1 is more than 2.

As an embodiment, said X1 is equal to 3.

As an embodiment, said X1 is equal to 4.

As an embodiment, the first MACCE is ShortTruncatedBSR.

As an example, the first MACCE is ShortTruncatedBSR for XR.

As an embodiment, the first MAC subheader is a MAC subheader of the first MAC ce.

As an embodiment, the first MAC subheader indicates the first MAC ce.

As an embodiment, the first LCGID field occupies 3 bits.

As an embodiment, the first LCGID domain is an LCGID domain.

As an embodiment, the first LCGID field is used to indicate an LCG.

As an embodiment, the first LCGID field indicates an LCG to which the first logical channel belongs.

As an embodiment, the first LCGID field is set as an LCGID of an LCG to which the first logical channel belongs.

As an embodiment, the first buffer size field occupies 5 bits.

As an embodiment, the first buffer size field occupies 6 bits.

As an embodiment, the first buffer size field occupies 7 bits.

As an embodiment, the first buffer size field occupies 8 bits.

As an embodiment, the first cache size domain is a BufferSize domain.

As an embodiment, the first buffer size field indicates a data amount of uplink data to be processed of at least the first logical channel.

As an embodiment, the first buffer size field indicates a data amount of uplink data to be processed of only the first logical channel.

As an embodiment, the first buffer size field indicates a data amount of uplink data to be processed of all logical channels in the LCG to which the first logical channel belongs.

As an embodiment, the first buffer size field indicates a data amount of uplink data to be processed of a part of logical channels in the LCG to which the first logical channel belongs.

As an embodiment, the first buffer size field indicates a data amount of uplink data to be processed of all logical channels associated with DRBs (data radio bearers, dataRadio Bearer) associated with the first logical channel.

As an embodiment, at least one LCG has uplink data to process.

As an embodiment, only one LCG of the at least one LCG of uplink data to be processed is reported.

As an embodiment, one or more of the at least one LCG of uplink data to be processed is not reported.

As one embodiment, at least one LCG has uplink data to process; the first logical channel is the highest priority logical channel of the at least one LCG.

As a sub-embodiment of this embodiment, the first logical channel is the one of the at least one LCG for which the configured Priority is the smallest is used to determine that the first logical channel is the highest Priority logical channel of the at least one LCG.

As a sub-embodiment of this embodiment, the first logical channel is considered to be the highest priority logical channel of the at least one LCG, and is used to determine that the first logical channel is the highest priority logical channel of the at least one LCG.

As a sub-embodiment of this embodiment, the first logical channel is used for XR and is used to determine that the first logical channel is the highest priority logical channel of the at least one LCG.

As a sub-embodiment of this embodiment, PDB (PDUDelayBudget) or PSDB (PDU-Set DelayBudget) with which the first logical channel is associated is least used to determine that the first logical channel is the highest priority logical channel of the at least one LCG.

As one embodiment, at least one LCG has uplink data to process; the first logical channel is one of the at least one LCG configured for XR.

As one embodiment, at least one LCG has uplink data to process; the first logical channel is the smallest one of the associated PDBs or PSDBs in the at least one LCG.

As one embodiment, at least one LCG has uplink data to process; the LCG to which the first logic channel belongs comprises one logic channel with highest priority in the at least one LCG; the one logical channel with the highest priority in the at least one LCG has or has not uplink data to be processed.

Example 12

Embodiment 12 illustrates a schematic diagram in which a first logical channel belongs to a first LCG and a first LCGID field indicates a second LCG, as shown in fig. 12, according to one embodiment of the application.

In embodiment 12, the first MACCE consists of a first LCGID field and a first buffer size field, the first buffer size field being used to indicate a data amount of uplink data to be processed of at least a first logical channel; the first logical channel belongs to a first LCG; the first LCGID domain indicates a second LCG; the LCGID of the first LCG and the LCGID of the second LCG are different; the X1 is equal to 2.

As an embodiment, the logical channel to which the first logical channel belongs is the first LCG.

As an embodiment, at least one LCG has uplink data to process.

As an embodiment, only the first LCG has uplink data to be processed.

As one embodiment, multiple LCGs have uplink data to process.

As one embodiment, at least one LCG has uplink data to process; the second LCG includes one logical channel with the highest priority in the at least one LCG.

As an embodiment, the first LCGID field is set to the LCGID of the second LCG.

As an embodiment, any logical channel in the second LCG has no uplink data to be processed.

As an embodiment, the highest priority of the logical channels in the second LCG is higher than the highest priority of the logical channels in the first LCG.

As an embodiment, the second LCG is an LCG to which a logical channel with highest priority among the at least one LCG of uplink data to be processed belongs; at least one LCG has uplink data to process.

As an embodiment, the second LCG is an LCG to which a logical channel having a largest data amount among the at least one LCG of uplink data to be processed belongs; at least one LCG has uplink data to process.

As an embodiment, the second LCG is an LCG to which a logical channel, of the at least one LCG of uplink data to be processed, to which an LCGID is smallest belongs; at least one LCG has uplink data to process.

As an embodiment, the second LCG is an LCG to which a logical channel with the highest priority belongs among all LCGs configured to the first node.

As an embodiment, the second LCG is an LCG to which a logical channel with the smallest Priority among all LCGs configured to the first node belongs.

As an embodiment, the second LCG is an LCG to which a logical channel with a smallest LCGID among all LCGs configured to the first node belongs.

Example 13

Embodiment 13 illustrates a schematic diagram of the location of the first MAC signaling in the first MAC pdu, as shown in fig. 13, according to one embodiment of the present application. Dashed box 1301 represents MACsubPDU #1, dashed box 1302 represents MACsubPDU #2=k, dashed box 1303 represents MACsubPDU #k1, respectively, solid box 1304 represents first MAC signaling, dashed box 1305 represents MACsubPDU including Padding; the ellipses represent other MACsubPDU.

In embodiment 13, the first MAC pdu consists of at least the first MAC signaling or at least the former of the at least one MACsubPDU.

As an embodiment, before the first MAC signaling, a MAC subheader of the first MAC signaling is not included.

As an embodiment, any bit of the first MAC pdu is not included prior to the first MAC signaling.

As an embodiment, following the first MAC signaling, a MAC subheader with LCID field set to 63 follows.

As an embodiment, after the first MAC signaling, no bits of the first MAC pdu are included.

As one embodiment, at least one of dashed box 1301, dashed box 1302, and dashed box 1303 is absent.

As an embodiment, dashed box 1301, dashed box 1302, and dashed box 1303 are all absent.

The dashed box 1305 exists, as one embodiment.

As an example, the dashed box 1305 is not present.

As an example, the ellipses in fig. 13 are present.

As one example, the ellipses in FIG. 13 are not present.

Example 14

Embodiment 14 illustrates a block diagram of a processing apparatus for use in a first node according to one embodiment of the application; as shown in fig. 14. In fig. 14, the processing means 1400 in the first node comprises a first receiver 1401 and a first transmitter 1402.

A first receiver 1401 that receives a first uplink grant;

a first transmitter 1402 that transmits a first MAC pdu on the first uplink grant, the first MAC pdu comprising a first MAC signaling;

In embodiment 14, the first MAC pdu includes that the first MAC signaling depends on the size of the padding bits in the first uplink grant being less than X1 bytes, the X1 being a positive integer; the first MAC signaling is composed of at least one of a first MAC sub-header or a first MAC ce; the first MAC signaling is used to indicate uplink data to be processed.

As an embodiment, the first MAC signaling is composed of the first MAC sub-header, which includes a first LCID field, which is used to indicate uplink data to be processed.

As an embodiment, the first MAC sub-header includes a first field that is used to indicate the amount of uplink data to be processed.

As an embodiment, the first MAC signaling consists of the first MAC ce; the first MACCE includes a first buffer size field that is used to indicate a data amount of uplink data to be processed.

As an embodiment, the most significant bit in the first MAC signaling is set to 1.

As an embodiment, the first MACCE is composed of a first LCGID field and a first buffer size field, the first buffer size field being used to indicate a data amount of uplink data to be processed of at least a first logical channel.

As an embodiment, the first logical channel belongs to a first LCG; the first LCGID domain indicates a second LCG; the LCGID of the first LCG and the LCGID of the second LCG are different.

As one embodiment, the first receiver 1401 receives a second uplink grant; the first transmitter 1402 transmitting a second MAC pdu on the second uplink grant, the second MAC pdu comprising second MAC signaling; wherein the second MAC pdu comprises a size of padding bits in the second MAC signaling dependent on the first uplink grant greater than X2 bytes, the X2 being an integer greater than the X1; the second MAC signaling is composed of a second MAC subheader and a second MACCE; the second MAC signaling is used to indicate uplink data to be processed.

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

As an example, the first receiver 1401 includes the antenna 452, the receiver 454, the multi-antenna receiving processor 458, and the receiving processor 456 of fig. 4 according to the present application.

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

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

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

As an example, the first transmitter 1402 includes the antenna 452, the transmitter 454, and the transmission processor 468 of fig. 4 of the present application.

Example 15

Embodiment 15 illustrates a block diagram of a processing apparatus for use in a second node according to one embodiment of the application; as shown in fig. 15. In fig. 15, the processing means 1500 in the second node comprises a second transmitter 1501 and a second receiver 1502.

A second transmitter 1501 transmitting a first uplink grant;

a second receiver 1502 that receives a first MAC pdu on the first uplink grant, the first MAC pdu comprising a first MAC signaling;

In embodiment 15, the first MAC pdu includes that the first MAC signaling depends on the size of the padding bits in the first uplink grant being less than X1 bytes, the X1 being a positive integer; the first MAC signaling is composed of at least one of a first MAC sub-header or a first MAC ce; the first MAC signaling is used to indicate uplink data to be processed.

As an embodiment, the second transmitter 1501 sends a second uplink grant; the second receiver 1502 receives a second MAC pdu on the second uplink grant, the second MAC pdu comprising second MAC signaling; wherein the second MAC pdu comprises a size of padding bits in the second MAC signaling dependent on the first uplink grant greater than X2 bytes, the X2 being an integer greater than the X1; the second MAC signaling is composed of a second MAC subheader and a second MACCE; the second MAC signaling is used to indicate uplink data to be processed.

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

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

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

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

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

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

Example 16

Embodiment 16 illustrates a schematic diagram of a first MACCE consisting of at least the former of a first bit map or a buffer size field, as shown in fig. 16, according to one embodiment of the present application.

In embodiment 16, the first MACCE consists of at least the former in a first bit bitmap or buffer size field, the first bit bitmap being used to indicate uplink data to be processed for at least a first logical channel; the first MAC signaling is composed of the first MAC subheader and the first MAC ce; the X1 is more than 3.

As an embodiment, said X1 is equal to 4.

As an embodiment, said X1 is equal to 5.

As an embodiment, the first bit map is 8 LCG _i fields, the i=0, 1,2,3,4,5,6,7.

As an embodiment, the first bit map occupies 1 octet.

As an embodiment, one bit in the first bit map is an LCG _i field.

As an embodiment, one bit in the first bit map indicates one LCG.

As an embodiment, one bit of the first bit map corresponding to the LCG to which the first logical channel belongs is set to 1.

As an embodiment, setting one bit of the first bit map corresponding to the LCG to which the first logical channel belongs to 1 indicates that the LCG to which the first logical channel belongs has uplink data to be processed.

As one embodiment, one bit of a corresponding one of the LCGs in the first bit bitmap is set to 1 to indicate uplink data to be processed by the one LCG; one bit of a corresponding one of the LCGs in the first bit bitmap is set to 0 indicating that the one LCG has no uplink data to be processed.

As an embodiment, the first MACCE consists of the first bit map.

As an embodiment, the first MACCE consists of the first bit map and at least one buffer size field.

As a sub-embodiment of this embodiment, the first bit map is followed for the buffer size field of the LCG to which the first logical channel belongs.

As a sub-embodiment of this embodiment, the location of the cache size field of the LCG to which the first logical channel belongs is related to the LCGID.

As a sub-embodiment of this embodiment, the second octet in the first MACCE is occupied for the cache size field of the LCG to which the first logical channel belongs.

As an embodiment, the padding bits in the first uplink grant can only accommodate one buffer size field, and one bit in the first bit map corresponding to only the LCG to which the first logical channel belongs is set to 1, and the buffer size field in the first mac ce indicates the data amount of the uplink data to be processed of the LCG to which the first logical channel belongs.

As an embodiment, the padding bits in the first uplink grant can only accommodate a plurality of buffer size domains, and at least one bit corresponding to the LCG to which the first logical channel belongs in the first bit map is set to 1.

As an embodiment, the first MACCE is LongTruncatedBSR.

As an example, the first MACCE is ShortTruncatedBSR for XR.

As an example, the first MACCE is LongTruncatedBSR for XR.

As an embodiment, the first MAC subheader indicates the first MAC ce.

As one example, each cache size field is a BufferSize field.

As an embodiment, at least one LCG has uplink data to process.

As an embodiment, a part of the LCGs of the at least one LCG of uplink data to be processed is reported.

As an embodiment, one or more of the at least one LCG of uplink data to be processed is reported.

As an embodiment, the reporting is ordered in ascending order of PDBs or PSDBs associated with logical channels in each of the at least one LCG.

As an embodiment, the reporting is ordered in descending order of highest priority of logical channels in each of the at least one LCG.

As an embodiment, the reporting is performed in descending order of the highest priority of the logical channels in each of the at least one LCG, and in case of the same priority, the reporting is performed in ascending order of the LCGID.

As an embodiment, the sorting and reporting are performed in descending order of the highest priority of the logical channels in each of the at least one LCG, and in case of the same priority, the sorting and reporting are performed in ascending order of the PDBs or PSDBs associated with the logical channels in each of the at least one LCG.

As one embodiment, at least one LCG has uplink data to process; the first logical channel is a smallest logical channel of the at least 2 logical channels having the highest priority among the at least one LCG.

As one embodiment, at least one LCG has uplink data to process; the first logical channel is the only one of the at least one LCG having the highest priority.

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

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

Claims

1. A first node for wireless communication, comprising:

a first receiver that receives a first uplink grant;

2. The first node of claim 1, wherein the first MAC signaling consists of the first MAC subheader including a first LCID field that is used to indicate uplink data to be processed.

3. The first node of claim 2, wherein the first MAC subheader comprises a first field that is used to indicate a data amount of uplink data to be processed.

4. The first node of claim 1, wherein the first MAC signaling consists of the first MACCE; the first MACCE includes a first buffer size field that is used to indicate a data amount of uplink data to be processed.

5. The first node of claim 4, wherein a most significant bit in the first MAC signaling is set to 1.

6. The first node of claim 1, wherein the first MACCE consists of a first LCGID field and a first buffer size field, the first buffer size field being used to indicate a data amount of uplink data to be processed for at least a first logical channel.

7. The first node of claim 6, wherein the first logical channel belongs to a first LCG; the first LCGID domain indicates a second LCG; the LCGID of the first LCG and the LCGID of the second LCG are different.

8. The first node according to any of claims 1 to 7, comprising:

the first receiver receiving a second uplink grant;

the first transmitter transmitting a second MAC pdu on the second uplink grant, the second MAC pdu comprising second MAC signaling;

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

receiving a first uplink grant;

Transmitting a first MAC pdu on the first uplink grant, the first MAC pdu comprising first MAC signaling;

10. A second node for wireless communication, comprising:

a second transmitter transmitting a first uplink grant;

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

Transmitting a first uplink grant;