WO2021081780A1

WO2021081780A1 - Apparatus and method operable for medium access control packet data unit

Info

Publication number: WO2021081780A1
Application number: PCT/CN2019/114132
Authority: WO
Inventors: Xue LIN; Cong SHI
Original assignee: Guangdong Oppo Mobile Telecommunications Corp.,Ltd.
Priority date: 2019-10-29
Filing date: 2019-10-29
Publication date: 2021-05-06

Abstract

An apparatus and a method operable for medium access control packet data unit (MAC PDU), which can solve issues of the prior art, provide better communication, and/or improve reliability are provided. A method operable for MAC PDU of a user equipment includes receiving a radio resource allocation from a network node and configuring a MAC PDU associated with the radio resource allocation, wherein the MAC PDU includes one or more MAC subPDUs, and each MAC subPDU includes one of the following: a MAC subheader with a backoff indicator only, a MAC subheader with a random access preamble identifier (RAPID) and a MAC fallback random access response (RAR), a MAC subheader without the RAPID and a MAC success RAR, a MAC subheader and a MAC service data unit (SDU) carrying a radio resource control (RRC) message, or a MAC subheader and a padding.

Description

APPARATUS AND METHOD OPERABLE FOR MEDIUM ACCESS CONTROL PACKET DATA UNIT

BACKGROUND OF DISCLOSURE

1. Field of Disclosure

The present disclosure relates to the field of communication systems, and more particularly, to an apparatus and a method operable for medium access control packet data unit (MAC PDU) .

2. Description of Related Art

Data are generally transmitted between a user equipment (UE) and a network node through a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, a medium access control (MAC) layer, and a physical (PHY) layer, each of which processes the data differently. The PDCP layer generally functions to perform security-related operations, and header compression and decompression, etc. The RLC layer generally functions to segment the data, to concatenate the data segments, to deliver the data segments in sequence, to perform automatic repeat-request (ARQ) operations, etc. The MAC layer generally functions to schedule PHY-layer resources in an uplink or a downlink. The PHY layer generally packages a transport block, transmits the packet via an air interface.

Although wireless communication technology has been developed to long term evolution (LTE) based on wideband code division multiple access (WCDMA) , demands and expectations of users and service providers are on the rise. In addition, considering other radio access technologies under development, new technological evolution is required to secure high competitiveness in the future. Decrease in cost per bit, increase in service availability, flexible use of frequency bands, a simplified structure, an open interface, appropriate power consumption of UEs, and the like are required.

There is a need to propose an apparatus and a method operable for medium access control packet data unit (MAC PDU) , which can provide at least one of the following benefits: solving issues of the prior art, providing better communication, or improving reliability.

SUMMARY

An object of the present disclosure is to propose an apparatus and a method operable for medium access control packet data unit (MAC PDU) , which can provide at least one of the following benefits: solving issues of the prior art, providing better communication, or improving reliability.

In a first aspect of the present disclosure, a user equipment operable for medium access control packet data unit (MAC PDU) includes a memory, a transceiver, and a processor coupled to the memory and the transceiver. The processor is configured to control the transceiver to receive a radio resource allocation from a network node and configure a MAC PDU associated with the radio resource allocation, wherein the MAC PDU includes one or more MAC subPDUs, and each MAC subPDU includes one of the following: a MAC subheader with a backoff indicator only, a MAC subheader with a random access preamble identifier (RAPID) and a MAC fallback random access response (RAR) , a MAC subheader without the RAPID and a MAC success RAR, a MAC subheader and a MAC service data unit (SDU) carrying a radio resource control (RRC) message, or a MAC subheader and a padding.

In a second aspect of the present disclosure, a method operable for medium access control packet data unit (MAC PDU) of a user equipment includes receiving a radio resource allocation from a network node and configuring a MAC PDU associated with the radio resource allocation, wherein the MAC PDU includes one or more MAC subPDUs, and each MAC subPDU includes one of the following: a MAC subheader with a backoff indicator only, a MAC subheader with a random access preamble identifier (RAPID) and a MAC fallback random access response (RAR) , a MAC subheader without the RAPID and a MAC success RAR, a MAC subheader and a MAC service data unit (SDU) carrying a radio resource control (RRC) message, or a MAC subheader and a padding.

In a third aspect of the present disclosure, a network node operable for medium access control packet data unit (MAC PDU) includes a memory, a transceiver, and a processor coupled to the memory and the transceiver. The processor is configured to control the transceiver to transmit, to a user equipment, a radio resource allocation and be configured a MAC PDU associated with the radio resource allocation from the user equipment, wherein the MAC PDU includes one or more MAC subPDUs, and each MAC subPDU includes one of the following: a MAC subheader with a backoff indicator only, a MAC subheader with a random access preamble identifier (RAPID) and a MAC fallback random access response (RAR) , a MAC subheader without the RAPID and a MAC success RAR, a MAC subheader and a MAC service data unit (SDU) carrying a radio resource control (RRC) message, or a MAC subheader and a padding.

In a fourth aspect of the present disclosure, a method operable for medium access control packet data unit (MAC PDU) of a network node includes transmitting, to a user equipment, a radio resource allocation and being configured a MAC PDU associated with the radio resource allocation from the user equipment, wherein the MAC PDU includes one or more MAC subPDUs, and each MAC subPDU includes one of the following: a MAC subheader with a backoff indicator only, a MAC subheader with a random access preamble identifier (RAPID) and a MAC fallback random access response (RAR) , a MAC subheader without the RAPID and a MAC success RAR, a MAC subheader and a MAC service data unit (SDU) carrying a radio resource control (RRC) message, or a MAC subheader and a padding.

In a fifth aspect of the present disclosure, a non-transitory machine-readable storage medium has stored thereon instructions that, when executed by a computer, cause the computer to perform the above method.

In a sixth aspect of the present disclosure, a chip includes a processor, configured to call and run a computer program stored in a memory, to cause a device in which the chip is installed to execute the above method.

In a seventh aspect of the present disclosure, a computer readable storage medium, in which a computer program is stored, causes a computer to execute the above method.

In an eighth aspect of the present disclosure, a computer program product includes a computer program, and the computer program causes a computer to execute the above method.

In a ninth aspect of the present disclosure, a computer program causes a computer to execute the above method.

BRIEF DESCRIPTION OF DRAWINGS

In order to more clearly illustrate the embodiments of the present disclosure or related art, the following figures will be described in the embodiments are briefly introduced. It is obvious that the drawings are merely some embodiments of the present disclosure, a person having ordinary skill in this field can obtain other figures according to these figures without paying the premise.

FIG. 1 is a block diagram of a user equipment and a network node operable for medium access control packet data unit (MAC PDU) according to an embodiment of the present disclosure.

FIG. 2 is a flowchart illustrating a method operable for medium access control packet data unit (MAC PDU) of a user equipment according to an embodiment of the present disclosure.

FIG. 3 is a flowchart illustrating a method operable for medium access control packet data unit (MAC PDU) of a network node according to an embodiment of the present disclosure.

FIG. 4 is a schematic diagram of an exemplary illustration of a MAC subheader with a backoff indicator according to an embodiment of the present disclosure.

FIG. 5 is a schematic diagram of an exemplary illustration of a MAC subheader with a random access preamble identifier (RAPID) for a MAC fallback RAR according to an embodiment of the present disclosure.

FIG. 6 is a schematic diagram of an exemplary illustration of a MAC subheader without a RAPID for a MAC success RAR according to an embodiment of the present disclosure.

FIG. 7 is a schematic diagram of an exemplary illustration of a MAC subheader for padding according to an embodiment of the present disclosure.

FIG. 8 is a schematic diagram of an exemplary illustration of a MAC PDU according to an embodiment of the present disclosure.

FIG. 9 is a schematic diagram of an exemplary illustration of a MAC fallback random access response (RAR) according to an embodiment of the present disclosure.

FIG. 10 is a schematic diagram of an exemplary illustration of a MAC success RAR according to an embodiment of the present disclosure.

FIG. 11 is a block diagram of a system for wireless communication according to an embodiment of the present disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Embodiments of the present disclosure are described in detail with the technical matters, structural features, achieved objects, and effects with reference to the accompanying drawings as follows. Specifically, the terminologies in the embodiments of the present disclosure are merely for describing the purpose of the certain embodiment, but not to limit the disclosure.

FIG. 1 illustrates that, in some embodiments, a user equipment (UE) 10 and a network node 20 such as a gNB operable for medium access control packet data unit (MAC PDU) according to an embodiment of the present disclosure are provided. For example, the MAC PDU is for MSGB. The UE 10 may include a processor 11, a memory 12, and a transceiver 13. The network node 20 may include a processor 21, a memory 22, and a transceiver 23. The

processor

11 or 21 may be configured to implement proposed functions, procedures and/or methods described in this description. Layers of radio interface protocol may be implemented in the

processor

11 or 21. The

memory

12 or 22 is operatively coupled with the

processor

11 or 21 and stores a variety of information to operate the

processor

11 or 21. The

transceiver

13 or 23 is operatively coupled with the

processor

11 or 21, and the

transceiver

13 or 23 transmits and/or receives a radio signal.

The

processor

11 or 21 may include an application-specific integrated circuit (ASIC) , other chipsets, logic circuit and/or data processing devices. The

memory

12 or 22 may include a read-only memory (ROM) , a random access memory (RAM) , a flash memory, a memory card, a storage medium and/or other storage devices. The

transceiver

13 or 23 may include baseband circuitry to process radio frequency signals. When the embodiments are implemented in software, the techniques described herein can be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The modules can be stored in the

memory

12 or 22 and executed by the

processor

11 or 21. The

memory

12 or 22 can be implemented within the

processor

11 or 21 or external to the

processor

11 or 21, in which those can be communicatively coupled to the

processor

11 or 21 via various means are known in the art.

In some embodiments, the processor 11 is configured to control the transceiver 13 to receive a radio resource allocation from the network node 20 and configure a MAC PDU associated with the radio resource allocation, wherein the MAC PDU includes one or more MAC subPDUs, and each MAC subPDU includes one of the following: a MAC subheader with a backoff indicator only, a MAC subheader with a random access preamble identifier (RAPID) and a MAC fallback random access response (RAR) , a MAC subheader without the RAPID and a MAC success RAR, a MAC subheader and a MAC service data unit (SDU) carrying a radio resource control (RRC) message, or a MAC subheader and a padding. This can solve issues of the prior art, provide better communication, and/or improve reliability.

In some embodiments, the processor 21 is configured to control the transceiver 23 to transmit, to the user equipment 10, a radio resource allocation and be configured a MAC PDU associated with the radio resource allocation from the user equipment 10, wherein the MAC PDU includes one or more MAC subPDUs, and each MAC subPDU includes one of the following: a MAC subheader with a backoff indicator only, a MAC subheader with a random access preamble identifier (RAPID) and a MAC fallback random access response (RAR) , a MAC subheader without the RAPID and a MAC success RAR, a MAC subheader and a MAC service data unit (SDU) carrying a radio resource control (RRC) message, or a MAC subheader and a padding. This can solve issues of the prior art, provide better communication, and/or improve reliability.

In some embodiments, at least one of the MAC subheader, the MAC fallback RAR, and the MAC success RAR is octet aligned. In some embodiments, at least one of the following is provided: the MAC subPDU with the backoff indicator only are placed at a beginning of the MAC PDU, the MAC subPDU with the MAC fallback RAR are placed together, the MAC subPDU with the MAC success RAR are placed together, the MAC subPDU with the MAC SDU carrying the RRC message are placed together, the MAC subPDU with the fallback RAR are placed after all the MAC subPDUs with the MAC success RARs, the MAC subPDU with the fallback RAR and the MAC subPDU with the success RAR are placed between the MAC subPDU with the backoff indicator only and the padding, all the MAC subPDUs with the MAC SDUs carrying the RRC messages are placed after one of the MAC subPDUs with the MAC success RARs, or the padding is placed at the end of the MAC PDU.

In some embodiments, the MAC subheader with the backoff indicator only consists of four header fields, T, R, R, and BI, where the T field means a type field, the R field means a reserved bit, and the BI field means a backoff indicator field. In some embodiments, the MAC subheader with the RAPID for the MAC fallback RAR consists of two header fields, T and RAPID, where the T field means a type field. In some embodiments, the MAC subheader without the RAPID for the MAC success RAR consists of six header fields, T, R, R, R, R, and E, where the T field means a type field, the R field means a reserved bit, and the E field means an extension field. In some embodiments, presence and a length of the padding are implicit based on a transport block (TB) size and a size of MAC subPDU, a size of the padding is zero, or the MAC subheader for the padding consists of two header fields, T and R, where the T field means a type field and the R field means a reserved bit.

In some embodiments, the MAC subheader consists of the following fields, T, E, R, BI, and RAPID, where the T field means a type field, the E field means an extension field, the R field means a reserved bit, the R field is set to 0, and the BI field means a backoff indicator field. In some embodiments, the T field is a flag indicating four types of the MAC subPDU, and a size of the T field is 2 bits. In some embodiments, when the T field is set to 00, the T field indicates presence of the BI field in the subheader, when the T field is set to 01, the T field indicates presence of the RAPID field in the subheader which follows by the MAC fallback RAR, when the T field is set to 10, the T field indicates presence of the E field in the subheader which follows by the MAC success RAR, and when the T field is set to 11, the T field indicates presence of the padding. In some embodiments, the E field indicates a number of the MAC subPDU carrying the RRC message following the MAC subPDU with the MAC success RAR, and a size of the E field is 2 bits. In some embodiments, the BI field identifies an overload condition in a cell, and a size of the BI field is 4 bits. In some embodiments, the RAPID field identifies a transmitted random access preamble, and a size of the RAPID field is 6 bits.

In some embodiments, the fallback RAR is of a fixed size and consists of the following fields, R, timing advance command, UL grant, and temporary C-RNTI, where the R field means a reserved bit, the R field is set to 0, the UL grant field means an uplink grant field, the temporary C-RNTI field means a temporary cell radio network temporary identifier field. In some embodiments, the timing advance command indicates an index value timing advance (TA) used to control an amount of timing adjustment that is used by a MAC entity, and a size of the timing advance command field is 12 bits. In some embodiments, the UL grant field indicates resources to be used on an uplink, and a size of the UL grant field is 27 bits. In some embodiments, the temporary C-RNTI field indicates a temporary identity that is used by a MAC entity during random access, and a size of the temporary C-RNTI field is 16 bits.

In some embodiments, the success RAR is of a fixed size and consists of the following fields, contention resolution identity, R, TPC, timing advance command, and C-RNTI, where the R field means a reserved bit, and the R field is set to 0. In some embodiments, the contention resolution identity field contains an uplink (UL) common control channel (CCCH) SDU, and a size of the contention resolution identity field is 48 bits. In some embodiments, if the UL CCCH SDU is longer than 48 bits, the contention resolution identity field contains the first 48 bits of the UL CCCH SDU. In some embodiments, the TPC filed indicates a transmit power control (TPC) command of the PUCCH resource containing a hybrid automatic repeat request (HARQ) feedback for MSGB, and a size of the TPC field is 2 bits. In some embodiments, the timing advance command field indicates an index value TA used to control an amount of timing adjustment that is used by a MAC entity, and a size of the timing advance command field is 12 bits. In some embodiments, the C-RNTI field indicates a unique user equipment identification used as an identifier of an RRC connection and for scheduling, and a size of the C-RNTI field is 16 bits.

FIG. 2 illustrates a method 200 operable for medium access control packet data unit (MAC PDU) of a user equipment according to an embodiment of the present disclosure. In some embodiments, the method 200 includes: a block 202, receiving a radio resource allocation from a network node, and a block 204, configuring a MAC PDU associated with the radio resource allocation, wherein the MAC PDU includes one or more MAC subPDUs, and each MAC subPDU includes one of the following: a MAC subheader with a backoff indicator only, a MAC subheader with a random access preamble identifier (RAPID) and a MAC fallback random access response (RAR) , a MAC subheader without the RAPID and a MAC success RAR, a MAC subheader and a MAC service data unit (SDU) carrying a radio resource control (RRC) message, or a MAC subheader and a padding. This can solve issues of the prior art, provide better communication, and/or improve reliability.

FIG. 3 illustrates a method 300 operable for medium access control packet data unit (MAC PDU) of a network node according to an embodiment of the present disclosure. In some embodiments, the method 300 includes: a block 302, transmitting, to a user equipment, a radio resource allocation, and a block 304, being configured a MAC PDU associated with the radio resource allocation from the user equipment, wherein the MAC PDU includes one or more MAC subPDUs, and each MAC subPDU includes one of the following: a MAC subheader with a backoff indicator only, a MAC subheader with a random access preamble identifier (RAPID) and a MAC fallback random access response (RAR) , a MAC subheader without the RAPID and a MAC success RAR, a MAC subheader and a MAC service data unit (SDU) carrying a radio resource control (RRC) message, or a MAC subheader and a padding. This can solve issues of the prior art, provide better communication, and/or improve reliability.

In some embodiments, the success RAR is of a fixed size and consists of the following fields, contention resolution identity, R, TPC, timing advance command, and C-RNTI, where the R field means a reserved bit, and the R field is set to 0. In some embodiments, the contention resolution identity field contains an uplink (UL) common control channel (CCCH) SDU, and a size of the contention resolution identity field is 48 bits. In some embodiments, if the UL CCCH SDU is longer than 48 bits, the contention resolution identity field contains the first 48 bits of the UL CCCH SDU. In some embodiments, the TPC filed indicates the TPC command of the PUCCH resource containing HARQ feedback for MSGB, and a size of the TPC field is 2 bits. In some embodiments, the timing advance command field indicates an index value TA used to control an amount of timing adjustment that is used by a MAC entity, and a size of the timing advance command field is 12 bits. In some embodiments, the C-RNTI field indicates a unique user equipment identification used as an identifier of an RRC connection and for scheduling, and a size of the C-RNTI field is 16 bits.

In summary, in some embodiments, a MAC PDU for MSGB consists of one or more MAC subPDUs and optionally padding. Each MAC subPDU consists one of the following: a MAC subheader with a backoff indicator only, a MAC subheader with a RAPID and a MAC fallback RAR, a MAC subheader without a RAPID and a MAC success RAR, a MAC subheader and a MAC SDU carrying an RRC message, or a MAC subheader and padding.

FIG. 4 is an exemplary illustration of a MAC subheader with a backoff indicator according to an embodiment of the present disclosure. FIG. 4 illustrates that, in some embodiments, a MAC subheader with a backoff indicator consists of four header fields T/R/R/BI. A MAC subPDU with the backoff indicator only is placed at the beginning of the MSGB MAC PDU, if included.

In some embodiments, MAC subPDU (s) with the MAC fallback RAR are placed together. MAC subPDU (s) with the MAC success RAR are placed together. MAC subPDU (s) with the MAC SDU carrying the RRC message are placed together. MAC subPDU (s) with the fallback RAR are placed after all the MAC subPDU (s) with the MAC success RAR. MAC subPDU (s) with the fallback RAR and the MAC subPDU (s) with the success RAR are placed between the MAC subPDU with the backoff indicator only (if any) and padding (if any) . All the MAC subPDU (s) with the MAC SDU carrying the RRC message (if any) can be placed after one of the MAC subPDU (s) with the MAC success RAR.

FIG. 5 is an exemplary illustration of a MAC subheader with a random access preamble identifier (RAPID) for a MAC fallback RAR according to an embodiment of the present disclosure. FIG. 5 illustrates that, in some embodiments, a MAC subheader with a RAPID for a MAC fallback RAR consists of two header fields T/RAPID.

FIG. 6 is an exemplary illustration of a MAC subheader without a RAPID for a MAC success RAR according to an embodiment of the present disclosure. FIG. 6 illustrates that, in some embodiments, a MAC subheader without a RAPID for a MAC success RAR consists of six header fields T/R/R/R/R/E.

FIG. 7 is an exemplary illustration of a MAC subheader for padding according to an embodiment of the present disclosure. FIG. 7 illustrates that, in some embodiments, a MAC subheader for padding consists of two header fields T/R. In some embodiments, padding is placed at the end of the MAC PDU if present. Presence and length of the padding are implicit based on a TB size, a size of the MAC subPDU (s) . A size of padding can be zero.

FIG. 8 is an exemplary illustration of a MAC PDU according to an embodiment of the present disclosure. FIG. 8 illustrates that, in some embodiments, a MAC subheader consists of the following fields:

T: a type field is a flag indicating four types of MAC subPDU. A size of the T field is 2 bits. The T field is set to "00" to indicate presence of a backoff indicator field in the subheader (BI) . The T field is set to "01" to indicate presence of a random access preamble identifier field in the subheader (RAPID) which follows by a MAC fallback RAR. The T field is set to "10" to indicate presence of an E field in the subheader which follows by a MAC success RAR. The T field is set to "11" to indicate presence of padding.

E: an extension field indicates a number of MAC subPDU (s) carrying an RRC message following the MAC subPDU with the MAC success RAR. A size of the E field is 2 bits.

R: reserved bit, set to "0" .

BI: a backoff indicator field identifies an overload condition in a cell. A size of the BI field is 4 bits.

RAPID: a random access preamble identifier field identifies a transmitted random access preamble. A size of the RAPID field is 6 bits.

FIG. 8 illustrates that, in some embodiments, the MAC subheader is octet aligned.

FIG. 9 is an exemplary illustration of a MAC fallback random access response (RAR) according to an embodiment of the present disclosure. FIG. 9 illustrates that, in some embodiments, a fallback RAR is of fixed size consists of the following fields:

R: a reserved bit, set to "0" .

Timing Advance Command: The timing advance command field indicates an index value TA used to control an amount of timing adjustment that a MAC entity can apply in TS 38.213. A size of the timing advance command field is 12 bits.

UL Grant: The uplink grant field indicates resources to be used on an uplink in TS 38.213. A size of the UL grant field is 27 bits.

Temporary C-RNTI: The temporary C-RNTI field indicates a temporary identity that is used by the MAC entity during random access. A size of the temporary C-RNTI field is 16 bits.

FIG. 8 and FIG. 9 illustrate that, in some embodiments, the MAC fallback RAR and the MAC success RAR are octet aligned.

FIG. 10 is an exemplary illustration of a MAC success RAR according to an embodiment of the present disclosure. FIG. 10 illustrates that, in some embodiments, a success RAR is of fixed size and consists of the following fields:

Contention Resolution Identity: The contention resolution identity field contains UL CCCH SDU. A size of the contention resolution identity field is 48 bits. If the UL CCCH SDU is longer than 48 bits, this field contains the first 48 bits of the UL CCCH SDU.

R: Reserved bit, set to "0" .

TPC: the TPC filed indicates a transmit power control (TPC) command of the PUCCH resource containing a hybrid automatic repeat request (HARQ) feedback for MSGB, and a size of the TPC field is 2 bits.

Timing Advance Command: The timing advance command field indicates an index value TA used to control an amount of timing adjustment that a MAC entity can apply in TS 38.213. A size of the timing advance command field is 12 bits；

C-RNTI: The C-RNTI field indicates a unique UE identification used as an identifier of an RRC connection and for scheduling. A size of the C-RNTI field is 16 bits.

Commercial interests for some embodiments are as follows. 1. Solving issues of the prior art, providing better communication, and/or improving reliability. 2. Some embodiments of the present disclosure are used by 5G-NR chipset vendors, communication system development vendors, automakers including cars, trains, trucks, buses, bicycles, moto-bikes, helmets, and etc., drones (unmanned aerial vehicles) , smartphone makers, communication devices for public safety use, AR/VR device maker for example gaming, conference/seminar, education purposes. Some embodiments of the present disclosure are a combination of “techniques/processes” that can be adopted in 3GPP specification to create an end product.

FIG. 11 is a block diagram of an example system 700 for wireless communication according to an embodiment of the present disclosure. Embodiments described herein may be implemented into the system using any suitably configured hardware and/or software. FIG. 11 illustrates the system 700 including a radio frequency (RF) circuitry 710, a baseband circuitry 720, an application circuitry 730, a memory/storage 740, a display 750, a camera 760, a sensor 770, and an input/output (I/O) interface 780, coupled with each other at least as illustrated.

The application circuitry 730 may include a circuitry such as, but not limited to, one or more single-core or multi-core processors. The processors may include any combination of general-purpose processors and dedicated processors, such as graphics processors, application processors. The processors may be coupled with the memory/storage and configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems running on the system.

The baseband circuitry 720 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processors may include a baseband processor. The baseband circuitry may handle various radio control functions that enables communication with one or more radio networks via the RF circuitry. The radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency shifting, etc. In some embodiments, the baseband circuitry may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN) , a wireless local area network (WLAN) , a wireless personal area network (WPAN) . Embodiments in which the baseband circuitry is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

In various embodiments, the baseband circuitry 720 may include circuitry to operate with signals that are not strictly considered as being in a baseband frequency. For example, in some embodiments, baseband circuitry may include circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency.

The RF circuitry 710 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.

In various embodiments, the RF circuitry 710 may include circuitry to operate with signals that are not strictly considered as being in a radio frequency. For example, in some embodiments, RF circuitry may include circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency.

In various embodiments, the transmitter circuitry, control circuitry, or receiver circuitry discussed above with respect to the user equipment, eNB, or gNB may be embodied in whole or in part in one or more of the RF circuitry, the baseband circuitry, and/or the application circuitry. As used herein, “circuitry” may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC) , an electronic circuit, a processor (shared, dedicated, or group) , and/or a memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the electronic device circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules.

In some embodiments, some or all of the constituent components of the baseband circuitry, the application circuitry, and/or the memory/storage may be implemented together on a system on a chip (SOC) .

The memory/storage 740 may be used to load and store data and/or instructions, for example, for system. The memory/storage for one embodiment may include any combination of suitable volatile memory, such as dynamic random access memory (DRAM) ) , and/or non-volatile memory, such as flash memory.

In various embodiments, the I/O interface 780 may include one or more user interfaces designed to enable user interaction with the system and/or peripheral component interfaces designed to enable peripheral component interaction with the system. User interfaces may include, but are not limited to a physical keyboard or keypad, a touchpad, a speaker, a microphone, etc. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, and a power supply interface.

In various embodiments, the sensor 770 may include one or more sensing devices to determine environmental conditions and/or location information related to the system. In some embodiments, the sensors may include, but are not limited to, a gyro sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of, or interact with, the baseband circuitry and/or RF circuitry to communicate with components of a positioning network, e.g., a global positioning system (GPS) satellite.

In various embodiments, the display 750 may include a display, such as a liquid crystal display and a touch screen display. In various embodiments, the system 700 may be a mobile computing device such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, a AR/VR glasses, etc. In various embodiments, system may have more or less components, and/or different architectures. Where appropriate, methods described herein may be implemented as a computer program. The computer program may be stored on a storage medium, such as a non-transitory storage medium.

A person having ordinary skill in the art understands that each of the units, algorithm, and steps described and disclosed in the embodiments of the present disclosure are realized using electronic hardware or combinations of software for computers and electronic hardware. Whether the functions run in hardware or software depends on the condition of application and design requirement for a technical plan.

A person having ordinary skill in the art can use different ways to realize the function for each specific application while such realizations should not go beyond the scope of the present disclosure. It is understood by a person having ordinary skill in the art that he/she can refer to the working processes of the system, device, and unit in the above-mentioned embodiment since the working processes of the above-mentioned system, device, and unit are basically the same. For easy description and simplicity, these working processes will not be detailed.

It is understood that the disclosed system, device, and method in the embodiments of the present disclosure can be realized with other ways. The above-mentioned embodiments are exemplary only. The division of the units is merely based on logical functions while other divisions exist in realization. It is possible that a plurality of units or components are combined or integrated in another system. It is also possible that some characteristics are omitted or skipped. On the other hand, the displayed or discussed mutual coupling, direct coupling, or communicative coupling operate through some ports, devices, or units whether indirectly or communicatively by ways of electrical, mechanical, or other kinds of forms.

The units as separating components for explanation are or are not physically separated. The units for display are or are not physical units, that is, located in one place or distributed on a plurality of network units. Some or all of the units are used according to the purposes of the embodiments. Moreover, each of the functional units in each of the embodiments can be integrated in one processing unit, physically independent, or integrated in one processing unit with two or more than two units.

If the software function unit is realized and used and sold as a product, it can be stored in a readable storage medium in a computer. Based on this understanding, the technical plan proposed by the present disclosure can be essentially or partially realized as the form of a software product. Or, one part of the technical plan beneficial to the conventional technology can be realized as the form of a software product. The software product in the computer is stored in a storage medium, including a plurality of commands for a computational device (such as a personal computer, a server, or a network device) to run all or some of the steps disclosed by the embodiments of the present disclosure. The storage medium includes a USB disk, a mobile hard disk, a read-only memory (ROM) , a random access memory (RAM) , a floppy disk, or other kinds of media capable of storing program codes.

While the present disclosure has been described in connection with what is considered the most practical and preferred embodiments, it is understood that the present disclosure is not limited to the disclosed embodiments but is intended to cover various arrangements made without departing from the scope of the broadest interpretation of the appended claims.

Claims

A user equipment operable for medium access control packet data unit (MAC PDU) , comprising:

a memory；

a transceiver； and

a processor coupled to the memory and the transceiver；

wherein the processor is configured to:

control the transceiver to receive a radio resource allocation from a network node； and

configure a MAC PDU associated with the radio resource allocation, wherein the MAC PDU comprises one or more MAC subPDUs, and each MAC subPDU comprises one of the following: a MAC subheader with a backoff indicator only, a MAC subheader with a random access preamble identifier (RAPID) and a MAC fallback random access response (RAR) , a MAC subheader without the RAPID and a MAC success RAR, a MAC subheader and a MAC service data unit (SDU) carrying a radio resource control (RRC) message, or a MAC subheader and a padding.
The user equipment of claim 1, wherein at least one of the MAC subheader, the MAC fallback RAR, and the MAC success RAR is octet aligned.
The user equipment of claim 1 or 2, wherein at least one of the following is provided: the MAC subPDU with the backoff indicator only are placed at a beginning of the MAC PDU, the MAC subPDU with the MAC fallback RAR are placed together, the MAC subPDU with the MAC success RAR are placed together, the MAC subPDU with the MAC SDU carrying the RRC message are placed together, the MAC subPDU with the fallback RAR are placed after all the MAC subPDUs with the MAC success RARs, the MAC subPDU with the fallback RAR and the MAC subPDU with the success RAR are placed between the MAC subPDU with the backoff indicator only and the padding, all the MAC subPDUs with the MAC SDUs carrying the RRC messages are placed after one of the MAC subPDUs with the MAC success RARs, or the padding is placed at the end of the MAC PDU.
The user equipment of any one of claims 1 to 3, wherein the MAC subheader with the backoff indicator only consists of four header fields, T, R, R, and BI, where the T field means a type field, the R field means a reserved bit, and the BI field means a backoff indicator field.
The user equipment of any one of claims 1 to 3, wherein the MAC subheader with the RAPID for the MAC fallback RAR consists of two header fields, T and RAPID, where the T field means a type field.
The user equipment of any one of claims 1 to 3, wherein the MAC subheader without the RAPID for the MAC success RAR consists of six header fields, T, R, R, R, R, and E, where the T field means a type field, the R field means a reserved bit, and the E field means an extension field.
The user equipment of any one of claims 1 to 3, wherein presence and a length of the padding are implicit based on a transport block (TB) size and a size of MAC subPDU, a size of the padding is zero, or the MAC subheader for the padding consists of two header fields, T and R, where the T field means a type field and the R field means a reserved bit.
The user equipment of any one of claims 1 to 3, wherein the MAC subheader consists of the following fields, T, E, R, BI, and RAPID, where the T field means a type field, the E field means an extension field, the R field means a reserved bit, the R field is set to 0, and the BI field means a backoff indicator field.
The user equipment of claim 8, wherein the T field is a flag indicating four types of the MAC subPDU, and a size of the T field is 2 bits.
The user equipment of claim 8 or 9, wherein when the T field is set to 00, the T field indicates presence of the BI field in the subheader, when the T field is set to 01, the T field indicates presence of the RAPID field in the subheader which follows by the MAC fallback RAR, when the T field is set to 10, the T field indicates presence of the E field in the subheader which follows by the MAC success RAR, and when the T field is set to 11, the T field indicates presence of the padding.
The user equipment of any one of claims 8 to 10, wherein the E field indicates a number of the MAC subPDU carrying the RRC message following the MAC subPDU with the MAC success RAR, and a size of the E field is 2 bits.
The user equipment of any one of claims 8 to 11, wherein the BI field identifies an overload condition in a cell, and a size of the BI field is 4 bits.
The user equipment of any one of claims 8 to 12, wherein the RAPID field identifies a transmitted random access preamble, and a size of the RAPID field is 6 bits.
The user equipment of any one of claims 1 to 3, wherein the fallback RAR is of a fixed size and consists of the following fields, R, timing advance command, UL grant, and temporary C-RNTI, where the R field means a reserved bit, the R field is set to 0, the UL grant field means an uplink grant field, the temporary C-RNTI field means a temporary cell radio network temporary identifier field.
The user equipment of claim 14, wherein the timing advance command indicates an index value timing advance (TA) used to control an amount of timing adjustment that is used by a MAC entity, and a size of the timing advance command field is 12 bits.
The user equipment of claim 14 or 15, wherein the UL grant field indicates resources to be used on an uplink, and a size of the UL grant field is 27 bits.
The user equipment of any one of claims 14 to 16, wherein the temporary C-RNTI field indicates a temporary identity that is used by a MAC entity during random access, and a size of the temporary C-RNTI field is 16 bits.
The user equipment of any one of claims 1 to 3, wherein the success RAR is of a fixed size and consists of the following fields, contention resolution identity, R, TPC, timing advance command, and C-RNTI, where the R field means a reserved bit, and the R field is set to 0.
The user equipment of claim 18, wherein the contention resolution identity field contains an uplink (UL) common control channel (CCCH) SDU, and a size of the contention resolution identity field is 48 bits.
The user equipment of claim 18 or 19, wherein if the UL CCCH SDU is longer than 48 bits, the contention resolution identity field contains the first 48 bits of the UL CCCH SDU.
The user equipment of any one of claims 18 to 20, wherein the timing advance command field indicates an index value TA used to control an amount of timing adjustment that is used by a MAC entity, and a size of the timing advance command field is 12 bits.
The user equipment of any one of claims 18 to 21, wherein the C-RNTI field indicates a unique user equipment identification used as an identifier of an RRC connection and for scheduling, and a size of the C-RNTI field is 16 bits, the TPC filed indicates a TPC command of a PUCCH resource containing a hybrid automatic repeat request (HARQ) feedback, and a size of the TPC field is 2 bits.
A method operable for medium access control packet data unit (MAC PDU) of a user equipment, comprising:

receiving a radio resource allocation from a network node； and

configuring a MAC PDU associated with the radio resource allocation, wherein the MAC PDU comprises one or more MAC subPDUs, and each MAC subPDU comprises one of the following: a MAC subheader with a backoff indicator only, a MAC subheader with a random access preamble identifier (RAPID) and a MAC fallback random access response (RAR) , a MAC subheader without the RAPID and a MAC success RAR, a MAC subheader and a MAC service data unit (SDU) carrying a radio resource control (RRC) message, or a MAC subheader and a padding.
The method of claim 23, wherein at least one of the MAC subheader, the MAC fallback RAR, and the MAC success RAR is octet aligned.
The method of claim 23 or 24, wherein at least one of the following is provided: the MAC subPDU with the backoff indicator only are placed at a beginning of the MAC PDU, the MAC subPDU with the MAC fallback RAR are placed together, the MAC subPDU with the MAC success RAR are placed together, the MAC subPDU with the MAC SDU carrying the RRC message are placed together, the MAC subPDU with the fallback RAR are placed after all the MAC subPDUs with the MAC success RARs, the MAC subPDU with the fallback RAR and the MAC subPDU with the success RAR are placed between the MAC subPDU with the backoff indicator only and the padding, all the MAC subPDUs with the MAC SDUs carrying the RRC messages are placed after one of the MAC subPDUs with the MAC success RARs, or the padding is placed at the end of the MAC PDU.
The method of any one of claims 23 to 25, wherein the MAC subheader with the backoff indicator only consists of four header fields, T, R, R, and BI, where the T field means a type field, the R field means a reserved bit, and the BI field means a backoff indicator field.
The method of any one of claims 23 to 25, wherein the MAC subheader with the RAPID for the MAC fallback RAR consists of two header fields, T and RAPID, where the T field means a type field.
The method of any one of claims 23 to 25, wherein the MAC subheader without the RAPID for the MAC success RAR consists of six header fields, T, R, R, R, R, and E, where the T field means a type field, the R field means a reserved bit, and the E field means an extension field.
The method of any one of claims 23 to 25, wherein presence and a length of the padding are implicit based on a transport block (TB) size and a size of MAC subPDU, a size of the padding is zero, or the MAC subheader for the padding consists of two header fields, T and R, where the T field means a type field and the R field means a reserved bit.
The method of any one of claims 23 to 25, wherein the MAC subheader consists of the following fields, T, E, R, BI, and RAPID, where the T field means a type field, the E field means an extension field, the R field means a reserved bit, the R field is set to 0, and the BI field means a backoff indicator field.
The method of claim 30, wherein the T field is a flag indicating four types of the MAC subPDU, and a size of the T field is 2 bits.
The method of claim 30 or 31, wherein when the T field is set to 00, the T field indicates presence of the BI field in the subheader, when the T field is set to 01, the T field indicates presence of the RAPID field in the subheader which follows by the MAC fallback RAR, when the T field is set to 10, the T field indicates presence of the E field in the subheader which follows by the MAC success RAR, and when the T field is set to 11, the T field indicates presence of the padding.
The method of any one of claims 30 to 32, wherein the E field indicates a number of the MAC subPDU carrying the RRC message following the MAC subPDU with the MAC success RAR, and a size of the E field is 2 bits.
The method of any one of claims 30 to 33, wherein the BI field identifies an overload condition in a cell, and a size of the BI field is 4 bits.
The method of any one of claims 30 to 34, wherein the RAPID field identifies a transmitted random access preamble, and a size of the RAPID field is 6 bits.
The method of any one of claims 23 to 25, wherein the fallback RAR is of a fixed size and consists of the following fields, R, timing advance command, UL grant, and temporary C-RNTI, where the R field means a reserved bit, the R field is set to 0, the UL grant field means an uplink grant field, the temporary C-RNTI field means a temporary cell radio network temporary identifier field.
The method of claim 36, wherein the timing advance command indicates an index value timing advance (TA) used to control an amount of timing adjustment that is used by a MAC entity, and a size of the timing advance command field is 12 bits.
The method of claim 36 or 37, wherein the UL grant field indicates resources to be used on an uplink, and a size of the UL grant field is 27 bits.
The method of any one of claims 36 to 38, wherein the temporary C-RNTI field indicates a temporary identity that is used by a MAC entity during random access, and a size of the temporary C-RNTI field is 16 bits.
The method of any one of claims 23 to 25, wherein the success RAR is of a fixed size and consists of the following fields, contention resolution identity, R, TPC, timing advance command, and C-RNTI, where the R field means a reserved bit, and the R field is set to 0.
The method of claim 40, wherein the contention resolution identity field contains an uplink (UL) common control channel (CCCH) SDU, and a size of the contention resolution identity field is 48 bits.
The method of claim 40 or 41, wherein if the UL CCCH SDU is longer than 48 bits, the contention resolution identity field contains the first 48 bits of the UL CCCH SDU.
The method of any one of claims 40 to 42, wherein the timing advance command field indicates an index value TA used to control an amount of timing adjustment that is used by a MAC entity, and a size of the timing advance command field is 12 bits.
The method of any one of claims 40 to 43, wherein the C-RNTI field indicates a unique user equipment identification used as an identifier of an RRC connection and for scheduling, and a size of the C-RNTI field is 16 bits, the TPC filed indicates a TPC command of a PUCCH resource containing a hybrid automatic repeat request (HARQ) feedback, and a size of the TPC field is 2 bits.
A network node operable for medium access control packet data unit (MAC PDU) , comprising:

a memory；

a transceiver； and

a processor coupled to the memory and the transceiver；

wherein the processor is configured to:

control the transceiver to transmit, to a user equipment, a radio resource allocation； and

be configured a MAC PDU associated with the radio resource allocation from the user equipment, wherein the MAC PDU comprises one or more MAC subPDUs, and each MAC subPDU comprises one of the following: a MAC subheader with a backoff indicator only, a MAC subheader with a random access preamble identifier (RAPID) and a MAC fallback random access response (RAR) , a MAC subheader without the RAPID and a MAC success RAR, a MAC subheader and a MAC service data unit (SDU) carrying a radio resource control (RRC) message, or a MAC subheader and a padding.
The network node of claim 45, wherein at least one of the MAC subheader, the MAC fallback RAR, and the MAC success RAR is octet aligned.
The network node of claim 45 or 46, wherein at least one of the following is provided: the MAC subPDU with the backoff indicator only are placed at a beginning of the MAC PDU, the MAC subPDU with the MAC fallback RAR are placed together, the MAC subPDU with the MAC success RAR are placed together, the MAC subPDU with the MAC SDU carrying the RRC message are placed together, the MAC subPDU with the fallback RAR are placed after all the MAC subPDUs with the MAC success RARs, the MAC subPDU with the fallback RAR and the MAC subPDU with the success RAR are placed between the MAC subPDU with the backoff indicator only and the padding, all the MAC subPDUs with the MAC SDUs carrying the RRC messages are placed after one of the MAC subPDUs with the MAC success RARs, or the padding is placed at the end of the MAC PDU.
The network node of any one of claims 45 to 47, wherein the MAC subheader with the backoff indicator only consists of four header fields, T, R, R, and BI, where the T field means a type field, the R field means a reserved bit, and the BI field means a backoff indicator field.
The network node of any one of claims 45 to 47, wherein the MAC subheader with the RAPID for the MAC fallback RAR consists of two header fields, T and RAPID, where the T field means a type field.
The network node of any one of claims 45 to 47, wherein the MAC subheader without the RAPID for the MAC success RAR consists of six header fields, T, R, R, R, R, and E, where the T field means a type field, the R field means a reserved bit, and the E field means an extension field.
The network node of any one of claims 45 to 47, wherein presence and a length of the padding are implicit based on a transport block (TB) size and a size of MAC subPDU, a size of the padding is zero, or the MAC subheader for the padding consists of two header fields, T and R, where the T field means a type field and the R field means a reserved bit.
The network node of any one of claims 45 to 47, wherein the MAC subheader consists of the following fields, T, E, R, BI, and RAPID, where the T field means a type field, the E field means an extension field, the R field means a reserved bit, the R field is set to 0, and the BI field means a backoff indicator field.
The network node of claim 52, wherein the T field is a flag indicating four types of the MAC subPDU, and a size of the T field is 2 bits.
The network node of claim 52 or 53, wherein when the T field is set to 00, the T field indicates presence of the BI field in the subheader, when the T field is set to 01, the T field indicates presence of the RAPID field in the subheader which follows by the MAC fallback RAR, when the T field is set to 10, the T field indicates presence of the E field in the subheader which follows by the MAC success RAR, and when the T field is set to 11, the T field indicates presence of the padding.
The network node of any one of claims 52 to 54, wherein the E field indicates a number of the MAC subPDU carrying the RRC message following the MAC subPDU with the MAC success RAR, and a size of the E field is 2 bits.
The network node of any one of claims 52 to 55, wherein the BI field identifies an overload condition in a cell, and a size of the BI field is 4 bits.
The network node of any one of claims 52 to 56, wherein the RAPID field identifies a transmitted random access preamble, and a size of the RAPID field is 6 bits.
The network node of any one of claims 45 to 47, wherein the fallback RAR is of a fixed size and consists of the following fields, R, timing advance command, UL grant, and temporary C-RNTI, where the R field means a reserved bit, the R field is set to 0, the UL grant field means an uplink grant field, the temporary C-RNTI field means a temporary cell radio network temporary identifier field.
The network node of claim 58, wherein the timing advance command indicates an index value timing advance (TA) used to control an amount of timing adjustment that is used by a MAC entity, and a size of the timing advance command field is 12 bits.
The network node of claim 58 or 59, wherein the UL grant field indicates resources to be used on an uplink, and a size of the UL grant field is 27 bits.
The network node of any one of claims 58 to 60, wherein the temporary C-RNTI field indicates a temporary identity that is used by a MAC entity during random access, and a size of the temporary C-RNTI field is 16 bits.
The network node of any one of claims 45 to 47, wherein the success RAR is of a fixed size and consists of the following fields, contention resolution identity, R, TPC, timing advance command, and C-RNTI, where the R field means a reserved bit, and the R field is set to 0.
The network node of claim 62, wherein the contention resolution identity field contains an uplink (UL) common control channel (CCCH) SDU, and a size of the contention resolution identity field is 48 bits.
The network node of claim 62 or 63, wherein if the UL CCCH SDU is longer than 48 bits, the contention resolution identity field contains the first 48 bits of the UL CCCH SDU.
The network node of any one of claims 62 to 64, wherein the timing advance command field indicates an index value TA used to control an amount of timing adjustment that is used by a MAC entity, and a size of the timing advance command field is 12 bits.
The network node of any one of claims 62 to 65, wherein wherein the C-RNTI field indicates a unique user equipment identification used as an identifier of an RRC connection and for scheduling, and a size of the C-RNTI field is 16 bits, the TPC filed indicates a TPC command of a PUCCH resource containing a hybrid automatic repeat request (HARQ) feedback, and a size of the TPC field is 2 bits.
A method operable for medium access control packet data unit (MAC PDU) of a network node, comprising:

transmitting, to a user equipment, a radio resource allocation； and

being configured a MAC PDU associated with the radio resource allocation from the user equipment, wherein the MAC PDU comprises one or more MAC subPDUs, and each MAC subPDU comprises one of the following: a MAC subheader with a backoff indicator only, a MAC subheader with a random access preamble identifier (RAPID) and a MAC fallback random access response (RAR) , a MAC subheader without the RAPID and a MAC success RAR, a MAC subheader and a MAC service data unit (SDU) carrying a radio resource control (RRC) message, or a MAC subheader and a padding.
The method of claim 67, wherein at least one of the MAC subheader, the MAC fallback RAR, and the MAC success RAR is octet aligned.
The method of claim 67 or 68, wherein at least one of the following is provided: the MAC subPDU with the backoff indicator only are placed at a beginning of the MAC PDU, the MAC subPDU with the MAC fallback RAR are placed together, the MAC subPDU with the MAC success RAR are placed together, the MAC subPDU with the MAC SDU carrying the RRC message are placed together, the MAC subPDU with the fallback RAR are placed after all the MAC subPDUs with the MAC success RARs, the MAC subPDU with the fallback RAR and the MAC subPDU with the success RAR are placed between the MAC subPDU with the backoff indicator only and the padding, all the MAC subPDUs with the MAC SDUs carrying the RRC messages are placed after one of the MAC subPDUs with the MAC success RARs, or the padding is placed at the end of the MAC PDU.
The method of any one of claims 67 to 69, wherein the MAC subheader with the backoff indicator only consists of four header fields, T, R, R, and BI, where the T field means a type field, the R field means a reserved bit, and the BI field means a backoff indicator field.
The method of any one of claims 67 to 69, wherein the MAC subheader with the RAPID for the MAC fallback RAR consists of two header fields, T and RAPID, where the T field means a type field.
The method of any one of claims 67 to 69, wherein the MAC subheader without the RAPID for the MAC success RAR consists of six header fields, T, R, R, R, R, and E, where the T field means a type field, the R field means a reserved bit, and the E field means an extension field.
The method of any one of claims 67 to 69, wherein presence and a length of the padding are implicit based on a transport block (TB) size and a size of MAC subPDU, a size of the padding is zero, or the MAC subheader for the padding consists of two header fields, T and R, where the T field means a type field and the R field means a reserved bit.
The method of any one of claims 67 to 69, wherein the MAC subheader consists of the following fields, T, E, R, BI, and RAPID, where the T field means a type field, the E field means an extension field, the R field means a reserved bit, the R field is set to 0, and the BI field means a backoff indicator field.
The method of claim 74, wherein the T field is a flag indicating four types of the MAC subPDU, and a size of the T field is 2 bits.
The method of claim 74 or 75, wherein when the T field is set to 00, the T field indicates presence of the BI field in the subheader, when the T field is set to 01, the T field indicates presence of the RAPID field in the subheader which follows by the MAC fallback RAR, when the T field is set to 10, the T field indicates presence of the E field in the subheader which follows by the MAC success RAR, and when the T field is set to 11, the T field indicates presence of the padding.
The method of any one of claims 74 to 76, wherein the E field indicates a number of the MAC subPDU carrying the RRC message following the MAC subPDU with the MAC success RAR, and a size of the E field is 2 bits.
The method of any one of claims 74 to 77, wherein the BI field identifies an overload condition in a cell, and a size of the BI field is 4 bits.
The method of any one of claims 74 to 78, wherein the RAPID field identifies a transmitted random access preamble, and a size of the RAPID field is 6 bits.
The method of any one of claims 67 to 69, wherein the fallback RAR is of a fixed size and consists of the following fields, R, timing advance command, UL grant, and temporary C-RNTI, where the R field means a reserved bit, the R field is set to 0, the UL grant field means an uplink grant field, the temporary C-RNTI field means a temporary cell radio network temporary identifier field.
The method of claim 80, wherein the timing advance command indicates an index value timing advance (TA) used to control an amount of timing adjustment that is used by a MAC entity, and a size of the timing advance command field is 12 bits.
The method of claim 80 or 81, wherein the UL grant field indicates resources to be used on an uplink, and a size of the UL grant field is 27 bits.
The method of any one of claims 80 to 82, wherein the temporary C-RNTI field indicates a temporary identity that is used by a MAC entity during random access, and a size of the temporary C-RNTI field is 16 bits.
The method of any one of claims 67 to 69, wherein the success RAR is of a fixed size and consists of the following fields, contention resolution identity, R, TPC, timing advance command, and C-RNTI, where the R field means a reserved bit, and the R field is set to 0.
The method of claim 84, wherein the contention resolution identity field contains an uplink (UL) common control channel (CCCH) SDU, and a size of the contention resolution identity field is 48 bits.
The method of claim 84 or 85, wherein if the UL CCCH SDU is longer than 48 bits, the contention resolution identity field contains the first 48 bits of the UL CCCH SDU.
The method of any one of claims 84 to 86, wherein the timing advance command field indicates an index value TA used to control an amount of timing adjustment that is used by a MAC entity, and a size of the timing advance command field is 12 bits.
The method of any one of claims 84 to 87, wherein the C-RNTI field indicates a unique user equipment identification used as an identifier of an RRC connection and for scheduling, and a size of the C-RNTI field is 16 bits, the TPC filed indicates a TPC command of a PUCCH resource containing a hybrid automatic repeat request (HARQ) feedback, and a size of the TPC field is 2 bits.
A non-transitory machine-readable storage medium having stored thereon instructions that, when executed by a computer, cause the computer to perform the method of any one of claims 23 to 44 and 67 to 88.
A chip, comprising:

a processor, configured to call and run a computer program stored in a memory, to cause a device in which the chip is installed to execute the method of any one of claims 23 to 44 and 67 to 88.
A computer readable storage medium, in which a computer program is stored, wherein the computer program causes a computer to execute the method of any one of claims 23 to 44 and 67 to 88.
A computer program product, comprising a computer program, wherein the computer program causes a computer to execute the method of any one of claims 23 to 44 and 67 to 88.
A computer program, wherein the computer program causes a computer to execute the method of any one of claims 23 to 44 and 67 to 88.