WO2025261202A1 - Procédé de communication, et appareil - Google Patents

Procédé de communication, et appareil

Info

Publication number
WO2025261202A1
WO2025261202A1 PCT/CN2025/099905 CN2025099905W WO2025261202A1 WO 2025261202 A1 WO2025261202 A1 WO 2025261202A1 CN 2025099905 W CN2025099905 W CN 2025099905W WO 2025261202 A1 WO2025261202 A1 WO 2025261202A1
Authority
WO
WIPO (PCT)
Prior art keywords
mac
data unit
field
terminal device
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2025/099905
Other languages
English (en)
Chinese (zh)
Inventor
李晨琬
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2025261202A1 publication Critical patent/WO2025261202A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/231—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the layers above the physical layer, e.g. RRC or MAC-CE signalling

Definitions

  • This application relates to the field of mobile communication technology, and in particular to a communication method and apparatus.
  • This application provides a communication method and apparatus for reducing the transmission overhead of MAC PDU.
  • the MAC header of the first MAC PDU does not carry a field indicating the length of the first SDU, which can reduce the transmission overhead of the MAC PDU.
  • the first SDU can be the first MAC SDU.
  • the first field can be the L field.
  • the terminal device is an IoT terminal device, such as an AIoT terminal or an IoT terminal. Therefore, this method can reduce the transmission overhead of the IoT terminal device, thereby reducing its power consumption.
  • the first MAC PDU includes an SDU (i.e., the first SDU), or in other words, the terminal device transmits the first MAC PDU using a single-bearer transmission method, or the terminal device uses a single-bearer transmission method.
  • the first aspect and its various possible implementations can be applied to scenarios where the first MAC PDU contains only one SDU, or in other words, the first aspect and its various possible implementations can be applied to scenarios where the terminal device transmits the first MAC PDU using a single-bearer transmission method, or in other words, the first aspect and its various possible implementations can be applied to scenarios where the terminal device uses a single-bearer transmission method.
  • the first MAC PDU includes a second field, which indicates whether the first MAC PDU carries the first field.
  • the terminal device can use the second field to indicate whether the first MAC PDU carries the first field.
  • the network device can determine whether the first MAC PDU carries the first field based on the second field. If the network device determines that the first field is present based on the second field, it can determine the length of the first SDU based on the first field. Conversely, if the network device determines that the first field is absent based on the second field, it can determine that all bits outside the first MAC header are occupied by the first SDU, and thus the first SDU can be parsed to obtain the data carried by the first SDU.
  • the size of the resources occupied by the first MAC PDU can be understood as the size of the resources occupied by the data (or data packet) to be transmitted by the terminal device, and the size of the resources occupied by the data packet to be transmitted can be considered to be the same as the size of the resources occupied by the first MAC PDU.
  • the terminal device may also receive first information used to determine whether to send the first MAC information.
  • the network device can instruct the terminal device to adopt the first aspect and various possible implementations via the first information, i.e., instruct the terminal device to send the aforementioned first MAC PDU via the first information.
  • the first information can be determined by the network device (such as a base station, central unit (CU), distributed unit (DU), or radio unit/radio unit (RU)) based on the terminal device's device type or transmission type.
  • the method can be implemented through the following steps: the network equipment receives a MAC PDU, the first MAC PDU including a first MAC header and a first SDU, wherein the first MAC header does not carry a first field, the first field being used to indicate the length of the first SDU; the network equipment can also acquire the data carried by the first SDU.
  • the network device can treat all bits other than the first MAC header as bits occupied by the first SDU, and can parse the first SDU to obtain the data carried by the first SDU.
  • the terminal device is an Internet of Things (IoT) terminal device.
  • IoT Internet of Things
  • the first MAC protocol data unit includes a service data unit.
  • the terminal device transmits the first MAC protocol data unit using a single-bearer transmission method.
  • the first MAC protocol data unit includes a second field that indicates whether the first MAC protocol data unit carries the first field.
  • the network device may also receive a second MAC protocol data unit, which includes a second MAC header, a second service data unit, and padding bits, wherein the second MAC header carries a third field for indicating the length of the second service data unit.
  • the third field is used to indicate the length information of the second business data unit and/or the length information of the padding bits.
  • the network device is a DU, and the network device can also receive second information from the central unit, which is used to indicate the device type or transmission type of the terminal device; in addition, the network device can determine to send the first information based on the device type or transmission type of the terminal device.
  • the device may include modules corresponding one-to-one with the methods/operations/steps/actions performed in any possible implementation of any of the first to second aspects. These modules may be hardware circuits, software, or a combination of hardware circuits and software.
  • the device includes a processing unit (sometimes also called a processing module) and a communication unit (sometimes also called a transceiver module, communication module, etc.).
  • the transceiver unit is capable of both sending and receiving functions. When the transceiver unit performs the sending function, it may be called a sending unit (sometimes also called a sending module); when the transceiver unit performs the receiving function, it may be called a receiving unit (sometimes also called a receiving module).
  • the sending unit and the receiving unit may be the same functional module, which is called the transceiver unit and can perform both sending and receiving functions; or, the sending unit and the receiving unit may be different functional modules, with the transceiver unit being a collective term for these functional modules.
  • embodiments of this application also provide a communication device, including a processor for executing a computer program (or computer-executable instructions) stored in a memory, such that when the computer program (or computer-executable instructions) is executed, the device performs the method as described in any possible implementation of any of the first to second aspects.
  • processor and memory are integrated together
  • the memory is located outside the communication device.
  • the communication device also includes a communication interface for communicating with other devices, such as sending or receiving data and/or signals.
  • the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.
  • a computer-readable storage medium for storing a computer program or instructions that, when executed, enable the implementation of the method described in any possible implementation of any of the first to second aspects, and the method shown in any possible implementation of the first aspect.
  • the chip system may also include a memory or circuitry, the memory of which can be used to store instructions, and the memory or circuitry can call the instructions stored in the memory to implement corresponding functions.
  • a communication method may include the method implemented by a first communication device as shown in the first aspect and any possible implementation thereof, and the method implemented by a second communication device as shown in the second aspect and any possible implementation thereof.
  • a tenth aspect provides a communication system that may include a first communication device and a second communication device.
  • the first communication device may be used to implement the method shown in the first aspect and any possible implementation thereof
  • the second communication device may be used to implement the method shown in the second aspect and any possible implementation thereof.
  • Figure 1 is a schematic diagram of the architecture of a wireless communication system
  • Figure 3 is a schematic diagram of a MAC PDU structure
  • Figure 4 is a schematic diagram of the header structure in a MAC PDU
  • Figure 5 is a schematic diagram of an open access network system
  • Figure 6 is a structural schematic diagram of an open access network device
  • Figure 7 is a flowchart illustrating a communication method provided in an embodiment of this application.
  • Figure 8 is a schematic diagram of the header structure in a first MAC PDU provided in an embodiment of this application.
  • Figure 9 is a schematic diagram of the transmission process of the first information under a CU-DU structure provided in an embodiment of this application.
  • Figure 10 is a schematic diagram of the header structure in another first MAC PDU provided in an embodiment of this application.
  • FIG 11 is a schematic diagram of a MAC PDU structure provided in an embodiment of this application.
  • Figure 12 is a schematic diagram of the structure of a communication device provided in an embodiment of this application.
  • Figure 13 is a schematic diagram of another communication device provided in an embodiment of this application.
  • This application provides a communication method and apparatus.
  • the method and apparatus are based on the same inventive concept. Since the principles by which the method and apparatus solve problems are similar, their implementations can be mutually referenced, and repeated details will not be repeated.
  • FIG 1 is a schematic diagram of the architecture of the communication system applied in an embodiment of this application.
  • the communication system includes an access network 100 and a core network 200.
  • the communication system may also include an Internet 300.
  • the radio access network (RAN) 100 may include at least one RAN device (110a and 110b in Figure 1) and at least one terminal (120a-120j in Figure 1).
  • the terminal is wirelessly connected to the radio access network device (or simply access network device), and the radio access network device is connected to the core network wirelessly or via a wired connection.
  • the core network device and the radio access network device may be independent physical devices, or the functions of the core network device and the logical functions of the radio access network device may be integrated on the same physical device, or a single physical device may integrate some of the functions of the core network device and some of the functions of the radio access network device. Terminals and radio access network devices can be interconnected via wired or wireless connections.
  • Figure 1 is just a schematic diagram. It can be understood that in addition to the access network equipment, the communication system may also include other network equipment, such as wireless relay equipment and wireless backhaul equipment, which are not shown in Figure 1.
  • the network device is a network-side device with transceiver capabilities.
  • the network device can be a device in a RAN that provides priority and/or wireless communication functions for terminal devices, referred to as RAN equipment.
  • the RAN can be an access network in the 3rd Generation Partnership Project (3GPP), such as 4th generation (4G), 5th generation (5G), or future communication networks.
  • 3GPP 3rd Generation Partnership Project
  • 4G 4th generation
  • 5G 5th generation
  • the RAN can also be an open access network (open RAN, O-RAN or ORAN), a cloud radio access network (CRAN), or a communication network combining two or more of the above.
  • RAN equipment can be a base station, evolved NodeB (eNodeB), or transmission reception point (TRP) in a Long Term Evolution (LTE) or LTE Advanced (LTE-A) communication system; a next-generation nodeB (gNB) in a 5th generation (5G) mobile communication system; a base station in a future mobile communication system; a wireless fidelity (WiFi) system; a long-range radio (LoRa) system; or an access node in a vehicle-to-everything (V2X) system.
  • RAN equipment can also be a module or unit that performs some of the functions of a base station; for example, it can be a CU, a DU, or an RU.
  • a CU is configured to implement the functions of the Packet Data Convergence Protocol (PDCP) layer and above (such as the RRC layer and/or the Service Data Adaptation Protocol (SDAP) layer); a DU is configured to implement the functions of the protocol layers below the PDCP layer (such as the Radio Link Control (RLC) layer, the MAC layer, and/or the Physical (PHY) layer).
  • PDCP Packet Data Convergence Protocol
  • SDAP Service Data Adaptation Protocol
  • a DU is configured to implement the functions of the protocol layers below the PDCP layer (such as the Radio Link Control (RLC) layer, the MAC layer, and/or the Physical (PHY) layer).
  • RLC Radio Link Control
  • PHY Physical
  • CUs and DUs can be configured separately or included in the same network element, such as a baseband unit (BBU).
  • BBU baseband unit
  • the RU can be included in radio frequency equipment or radio frequency units, such as in a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).
  • RRU remote radio unit
  • AAU active antenna unit
  • RRH remote radio head
  • CU, DU, or RU may have different names, but those skilled in the art will understand their meaning.
  • CU can also be called O-CU (open CU)
  • DU can also be called O-DU
  • RU can also be called O-RU.
  • Any of the units among CU (or CU-control plane (CP), CU-user plane (UP)), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.
  • the wireless access network equipment can be a macro base station (as shown in Figure 1, 110a), a micro base station or an indoor station (as shown in Figure 1, 110b), or a relay node or donor node, etc.
  • the embodiments of this application do not limit the specific technology or specific equipment form used in the wireless access network equipment.
  • network equipment can be used as a shorthand for wireless access network equipment, and base station can be used as an example of wireless access network equipment.
  • the control plane protocol layer structure may include the RRC layer, PDCP layer, RLC layer, MAC layer, and PHY layer;
  • the user plane protocol layer structure may include the PDCP layer, RLC layer, MAC layer, and PHY layer.
  • the SDAP layer may also be included above the PDCP layer.
  • the SDAP layer, PDCP layer, RLC layer, MAC layer, and PHY layer can also be collectively referred to as the access layer.
  • Downlink data refers to the data sent from the access network device to the terminal device.
  • downward arrows represent data transmission
  • upward arrows represent data reception.
  • the SDAP layer entity After receiving data from the upper layer, the SDAP layer entity maps the data to the corresponding PDCP layer entity. The PDCP layer entity then delivers the data to at least one RLC layer entity corresponding to that PDCP layer entity. This RLC layer entity then delivers the data to the corresponding MAC layer entity, which generates a transport block (TB). Finally, the data is wirelessly transmitted through the corresponding PHY layer entity. Data is encapsulated at each layer. Data received by a layer from its upper layer is used as its SDU, which is then encapsulated into a PDU before being passed to the next layer.
  • data received by a PDCP layer entity from an upper layer is called a PDCP SDU
  • data sent by a PDCP layer entity to a lower layer is called a PDCP PDU in the PDCP layer
  • data received by an RLC layer entity from an upper layer is called an RLC SDU in the RLC layer
  • data sent by an RLC layer entity to a lower layer is called an RLC PDU
  • data received by a MAC layer entity from an upper layer (such as the RLC layer) (such as an RLC PDU) is called a MAC SDU
  • data sent by a MAC layer entity to a lower layer is called a MAC PDU.
  • RLC layer entities and MAC layer entities can transmit data through a logical channel (LCH)
  • MAC layer entities and physical layer entities can transmit data through a transport channel.
  • a MAC PDU includes a header or multiple sub-headers. Additionally, a MAC PDU may also include at least one of the following: a MAC control element (MAC CE), a MAC SDU, and padding bits (or padding information or padding).
  • MAC CE MAC control element
  • the MAC CE, MAC SDU, and padding bits can also be referred to as the MAC payload.
  • Each sub-header can correspond to one MAC CE, one MAC SDU, or padding bits.
  • the structure of the head (or sub-head) is described below with reference to Figure 4.
  • the head (or sub-head) may contain at least one of the following terminals:
  • the R field indicates reserved bits.
  • the F field represents the length of the length field L.
  • a value of 0 for the F field indicates that the header (or sub-header) contains an 8-bit length L; a value of 1 for the F field indicates that the header (or sub-header) contains a 16-bit length L.
  • the L field indicates the length of the MAC SDU.
  • Logical Channel Identifier This identifier represents the logical channel between the RLC layer entity and the MAC layer entity.
  • the LCID length is, for example, 5 bits.
  • Extended LCID extended logical channel identifier, eLCID
  • eLCID extended logical channel identifier
  • terminal equipment Similar to access network equipment, terminal equipment also has an access layer comprising SDAP, PDCP, RLC, MAC, and physical layers. Terminal equipment also has an application layer and a non-access layer.
  • the application layer provides services to applications installed on the terminal equipment. For example, downlink data received by the terminal equipment can be sequentially transmitted from the physical layer to the application layer, and then provided to the application by the application layer. Alternatively, the application layer can acquire data generated by applications (such as videos recorded by users using applications) and sequentially transmit the data to the physical layer for transmission to other communication devices.
  • the non-access layer forwards user data, such as forwarding uplink data received from the application layer to the SDAP layer or forwarding downlink data received from the SDAP layer to the application layer.
  • Figure 5 is an example diagram of an O-RAN system, which may include other components besides those shown in Figure 5.
  • access network equipment e.g., eNB, gNB, or next-generation base station
  • core network equipment can also communicate with UEs via an air interface.
  • the specific communication process may include the BBU in the access network equipment communicating with the core network via the backhaul link, and the RU in the access network equipment communicating with at least one UE via an air interface.
  • the BBU can communicate with at least one RU via a fronthaul link.
  • the BBU and RU may or may not be co-located.
  • the BBU includes at least one CU and at least one DU, which can communicate via at least one midhaul link.
  • Figure 6 illustrates the network element function division and protocol layer structure of an access network device under an O-RAN architecture.
  • the CU (Core Unit) of the access network device is a logical node that carries the radio resource control (RRC) layer, service data adaptation protocol (SDAP) layer, packet data convergence protocol (PDCP) layer, and other control functions.
  • RRC radio resource control
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • the CU connects to network nodes such as the core network through interfaces, which can be interfaces such as E2 interfaces.
  • the CU can have some of the core network's functions.
  • the CU e.g., the PDCP layer and higher layers
  • connects to the DU e.g., the radio link control (RLC) layer and lower layers
  • interfaces which can be interfaces such as F1 interfaces.
  • these interfaces can provide control plane (C-Plane) and user plane (U-Plane) functions (e.g., interface management, system information management, UE context management, RRC message transmission, etc.).
  • F1AP is the application protocol for the F1 interface, defining the F1 signaling procedures in some examples.
  • the F1 interface supports control plane F1-C and user plane F1-U.
  • the CU can be split into CU-CP and CU-UP.
  • CU-CP is a logical node carrying the RRC layer and the PDCP control plane (PDCP-C) layer, used to implement the CU's control plane functions.
  • CU-CP can interact with network elements in the core network used to implement control plane functions. These network elements can be access and mobility function (AMF) network elements, such as the AMF network elements in a 5G system.
  • CU-UP is a logical node carrying the SDAP layer and the PDCP-U (user plane part of PDCP) layer, used to implement the CU's user plane functions.
  • CU-UP can interact with network elements in the core network used to implement user plane functions.
  • CU and DU configurations are merely examples; the functions of CU and DU can be configured as needed.
  • a CU or DU can be configured to have more protocol layer functions, or it can be configured to have only some protocol layer processing functions.
  • some RLC layer functions and protocol layer functions above the RLC layer can be placed in the CU, while the remaining RLC layer functions and protocol layer functions below the RLC layer can be placed in the DU.
  • the functions of the CU or DU can be divided according to service type or other system requirements. For instance, based on latency, functions that need to meet low latency requirements can be placed in the DU, while functions that do not need to meet this latency requirement can be placed in the CU.
  • a DU can host logical nodes that function as RLC, MAC, higher physical layer (PHY), or other layers.
  • a DU can control at least one RU. The DU connects to the RU through interfaces, which can be fronthaul interfaces.
  • the CU may not have a PDCP layer, for example, it may only include the RRC layer.
  • the CU-CP may not have PDCP-C.
  • the CU-UP may not have PDCP-U, or may not have CU-UP at all.
  • the DU may not have an RLC layer, for example, it may only have MAC and higher physical layers.
  • the O-RAN device may also not have a CU and only include the DU, i.e., without an RRC layer.
  • the higher physical layer includes portions of the PHY layer processing, such as forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation.
  • the RU is a logical node carrying both lower physical layer (lower PHY) and radio frequency (RF) processing.
  • the RU can be a 3GPP TRP or RRH or other similar functional entity.
  • the lower physical layer includes portions of the PHY processing, such as fast Fourier transform (FFT), inverse fast Fourier transform (IFFT), digital beamforming, and filtering.
  • FFT fast Fourier transform
  • IFFT inverse fast Fourier transform
  • the RU communicates with one or more UEs via a radio link.
  • the DU and RU may or may not be co-located.
  • the DU and RU exchange control plane and user plane information via a lower-layer split-control, user, and synchronization (LLS-CUS) interface through a fronthaul link.
  • LLS-CUS may include LLS-C and LLS-U interfaces providing C-Plane and LLS-C and LLS-U interfaces providing U-Plane, respectively.
  • C-Plane refers to real-time control between the DU and RU.
  • the DU and RU exchange management information, such as management plane (M-Plane) management information, through an LLS-M interface on the fronthaul link.
  • M-Plane refers to non-real-time management operations between the DU and RU.
  • the DU and RU can cooperate to implement PHY layer functions.
  • a DU can be connected to one or more RUs.
  • the functions of the DU and RU can be configured in various ways depending on the design.
  • the DU may be configured to implement baseband functions, and the RU may be configured to implement mid-RF functions.
  • DU is configured to implement higher-level functions in the PHY layer
  • RU is configured to implement lower-level functions in the PHY layer, or to implement both lower-level functions and RF functions.
  • Higher-level functions in the physical layer may include a portion of the physical layer's functions that are closer to the MAC layer, while lower-level functions in the physical layer may include another portion of the physical layer's functions that are closer to the mid-RF side.
  • access network equipment can be one or more of the following: CU, DU, or AAU.
  • a CU can be classified as a network device in the access network or as a network device in the core network (CN); this application does not limit this classification.
  • a terminal is a device with wireless transceiver capabilities, capable of sending signals to or receiving signals from a base station.
  • Terminals can also be called terminal devices, user interfaces (UEs), mobile stations, mobile terminals, etc.
  • Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), the Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, and smart homes.
  • Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the specific technologies or device forms used in the terminals.
  • the terminal in this application can be a device with backscatter transmission functionality, such as an AIoT terminal.
  • An AIoT terminal can also be referred to as a tag, an AIoT label, a terminal in an AIoT scenario, or a tag in an AIoT scenario.
  • An AIoT terminal can be a terminal device that supports radio frequency identification (RFID) technology.
  • RFID radio frequency identification
  • AIoT terminals can be categorized based on whether they use backscatter communication. For example, AIoT terminals can be divided into active, passive, and semi-active terminals, while tags can be categorized into active tags, passive tags, and semi-passive tags. Passive and semi-passive tags use backscatter communication; active tags use actively generated carrier waves, meaning they do not communicate based on backscatter. AIoT terminals can also be called AIoT devices, and to distinguish them from 5G terminals, they can also be referred to as devices.
  • AIoT terminals can also be classified based on their ability to store energy or not, or a combination of both.
  • the AIoT terminal in this application can also be called an AIoT device.
  • An AIoT device can be device A, device B, or device C.
  • Device A refers to a device without energy storage and without independent signal generation, such as a backscatter transmission device with this characteristic.
  • Device B can be a device with energy storage but without independent signal generation, such as a backscatter transmission device with this characteristic, where the use of stored energy can include amplification of the reflected signal.
  • Device C can be a device with energy storage and independent signal generation, such as an active wireless radio frequency component for transmission.
  • the functions of the base station can be executed by modules (such as chips) within the base station, or by a control subsystem that includes base station functions.
  • This control subsystem, including base station functions can be a control center in the aforementioned application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities.
  • the functions of the terminal can be executed by modules (such as chips or modems) within the terminal, or by a device that includes terminal functions.
  • the base station sends downlink (DL) signals or downlink information to the terminal, and the downlink information is carried on the downlink channel;
  • the terminal sends uplink (UL) signals or uplink information to the base station, and the uplink information is carried on the uplink channel.
  • the helicopter or drone 120i in Figure 1 can be configured as a mobile base station.
  • terminal 120i For terminals 120j that access the wireless access network 100 through 120i, terminal 120i is a base station; however, for base station 110a, 120i is a terminal, meaning that 110a and 120i communicate via a wireless air interface protocol.
  • 110a and 120i can also communicate via a base station-to-base station interface protocol.
  • base station and terminal can be collectively referred to as communication devices.
  • 110a and 110b in Figure 1 can be called communication devices with base station functions
  • 120a-120j in Figure 1 can be called communication devices with terminal functions.
  • the base station and terminal can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed on aircraft, balloons, and satellites.
  • the embodiments of this application do not limit the application scenarios of the base station and terminal.
  • the network equipment may also include CN equipment.
  • Core network elements may include mobility management network elements, primarily used for mobility management and access management.
  • this access management network element may be an AMF, primarily performing functions such as mobility management, access authentication, or authorization.
  • mobility management network elements can be network components in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform).
  • a platform e.g., a cloud platform
  • the aforementioned network elements or functions can be implemented by one device, multiple devices working together, or a functional module within a single device; this application does not specifically limit these possibilities.
  • AMF will be used as an example of a mobility management network element or a core network element for illustration.
  • NB-IoT Narrowband Internet of Things
  • NB-IoT terminals still require external power supply, such as through batteries or external power sources, and NB-IoT terminals have the ability to generate local high-frequency local oscillator carriers. Therefore, these terminals can only achieve milliwatt-level power consumption, and energy consumption needs further reduction.
  • the AIoT terminal can use a low-precision, low-power mid-to-low frequency ring oscillator or receive downlink signals without a local oscillator.
  • the communication energy and carrier are supplied by a reader, and communication is based on reflected carriers.
  • the reader can be a handheld or fixed device for reading AIoT terminal information.
  • the reader/writer can also be used to write information to AIoT terminals.
  • This application does not limit the form of the reader/writer; it can be a base station, a terminal, a relay node, or an integrated access and backhaul (IAB) node.
  • the reader/writer is a terminal
  • the communication between the reader/writer and the AIoT terminal can be considered as transmission between terminals.
  • the reader/writer is a base station
  • the communication between the reader/writer and the AIoT terminal is through a universal user-to-network interface (Uu) interface, meaning that the reader/writer and the AIoT terminal communicate over the air.
  • the AIoT terminal can be located within the coverage area provided by the reader/writer.
  • the header or sub-header of the MAC PDU sent by the terminal device to the access network device may not carry the indication field (L field as shown in FIG. 4) used to indicate the data length of the MAC PDU, thus reducing the transmission overhead of the MAC PDU.
  • the reduction of the transmission overhead of the MAC PDU can reduce the power consumption of the terminal device.
  • the communication method provided in this application embodiment can be executed by a first communication device and a second communication device.
  • the steps executed by the first communication device can be implemented by a terminal device (specifically, an IoT terminal or an AIoT terminal), or by components in the terminal (such as chips, or other processing units or processors, transceiver units or transceiver modules), or by a device or equipment that performs some functions of the terminal.
  • the steps executed by the second communication device can be implemented by the access network device (such as a base station) itself, or by components in the access network device (such as baseband chips, or other processing units or processor modules), or by a device or equipment that includes some functions of the access network device.
  • the access network device can be a CU, DU, or RU that performs some functions of the second access network device.
  • the first communication device can be a chip
  • the second communication device can be an equipment (such as a base station); or, both the first communication device and the second access network device can be chips or both can be equipment.
  • the following description illustrates the communication method provided in this application, with the first communication device being a terminal device and the second communication device being a base station.
  • the terminal device mentioned below can be replaced by AIoT terminal, IoT terminal, terminal, first communication device, first communication equipment, etc.
  • the base station mentioned below can be replaced by network equipment, second communication device, RAN equipment.
  • the communication method provided in this application embodiment may include the following steps:
  • the S101 can be understood as the MAC layer entity of the terminal device generating the first MAC PDU.
  • the first MAC PDU may include a MAC header and a MAC SDU.
  • the MAC header carried in the first MAC PDU can be called the first MAC header
  • the MAC SDU carried in the first MAC PDU can be called the first MAC SDU.
  • the first MAC header can be either a header or a sub-header, without specific restrictions. Specifically, if the first MAC PDU includes only one MAC SDU (i.e., the first MAC SDU) and does not carry a MAC CE or padding bits, then the first MAC header is a header. If the first MAC PDU includes the first MAC SDU and also includes a MAC CE or padding bits, then the first MAC header can be a sub-header. Multiple sub-headers can be collectively referred to as a header.
  • the first MAC PDU does not carry a field indicating the length of the first MAC SDU.
  • this field may be simply referred to as the first field below.
  • the first field may be an L field.
  • the L field can be seen in the description of Figure 4.
  • FIG. 8 shows an exemplary implementation of the first MAC header, in which the first MAC header may consist of the R field, F field, E field, and LCID.
  • (b) shows another exemplary implementation of the first MAC header, in which the first MAC header may consist of the R field, F field, and LCID.
  • (c) shows yet another exemplary implementation of the first MAC header, in which the first MAC header may consist of the R field, F field, LCID, and eLCID.
  • the F field, LCID, and eLCID can be referred to in the description of Figure 4.
  • the first MAC PDU may carry a second field, which can be used to indicate whether the first MAC header carries the first field. For example, a value of 1 for the second field indicates that the first MAC header carries the first field, and a value of 0 for the second field indicates that the first MAC header does not carry the first field.
  • the second field is carried in the first MAC header.
  • the second field occupies fewer bits than the L field would normally occupy.
  • the second field shares bits with the F field in the first MAC header; as shown in Figure 8(a), (b), or (c), the F field in the first MAC header can be used to indicate whether the first field is carried in the first MAC header.
  • the second field can occupy one or more bits that would normally belong to the L field.
  • the terminal device in this application employs a single-bearer transmission method.
  • the terminal device only supports single-bearer transmission, or the terminal device is configured to employ single-bearer transmission.
  • the first MAC PDU contains only one MAC SDU, or that the first MAC PDU transmits the first MAC SDU using a single-bearer transmission method.
  • single-bearer transmission means that only one radio barrier's data is transmitted in a single MAC PDU.
  • the radio barrier includes a data radio barrier (DRB) and a signaling radio barrier (SRB) (e.g., SRB1).
  • DRB data radio barrier
  • SRB signaling radio barrier
  • the first MAC PDU is only used to carry the data of one DRB, and data for the same DRB typically only needs to be carried by one MAC SDU.
  • the first MAC PDU is only used to carry the data of one SRB, and data for the same SRB typically only needs to be carried by one MAC SDU.
  • the method in this application can be used when the terminal device adopts a single-bearer transmission mode, the first MAC PDU contains only one MAC SDU and/or the first MAC PDU is sent using a single-bearer transmission mode. That is, when the AIoT terminal adopts a single-bearer transmission mode, the first MAC PDU contains only one MAC SDU and/or the first MAC PDU is sent using a single-bearer transmission mode, the scheme in Figure 7 is executed. In other words, in the above case, the first MAC header of the first MAC PDU does not carry the first field, or in other words, the first MAC header does not carry the first field at this time.
  • the terminal device can determine the method to be executed based on the transmission resources of the first MAC PDU configured by the base station. For example, the terminal device can receive first resource configuration information from the base station, which can be used to configure the transmission resources of the first MAC PDU (or the configured transmission resources). For example, the first resource configuration information can indicate the transmission resources allocated by the base station to the terminal device. The terminal device can compare the size of the configured transmission resources with the size of the transmission resources occupied by the first data packet to be transmitted, and determine whether the first MAC PDU carries a first field based on the comparison result.
  • the size of the transmission resources occupied by the first data packet to be transmitted can be understood as being the same as the size of the transmission resources allocated to it, and the first data packet to be transmitted can be understood as at least one RLC PDU, which corresponds to the first MAC SDU.
  • a terminal device can determine to transmit at least one RLC PDU (which may contain segmented SDUs) based on the size of the transmission resources configured by the base station. In this case, it can be determined that the at least one transmitted RLC PDU corresponds to a first MAC SDU. For instance, when it is determined to transmit one RLC PDU, the first MAC SDU can be generated based on that RLC PDU.
  • the first MAC SDU can be generated based on the first (or not the last) RLC PDU.
  • the size of the transmission resources occupied by the first data packet can be understood as the sum of the resource size of at least one RLC PDU and the resource size occupied by the first MAC header. Therefore, comparing the configured transmission resource size with the transmission resource size occupied by the first data packet to be transmitted can also be considered as comparing the configured transmission resource size with the transmission resource size occupied by the first MAC PDU.
  • the size of the configured transmission resources is equal to the size of the transmission resources occupied by the first MAC PDU, it is not necessary to split the first data packet to be transmitted into multiple MAC SDUs for transmission, and it is not necessary to add padding bits to execute the method in Figure 7, that is, to generate a first MAC PDU without carrying the first field.
  • the first MAC header consists of R, F, E, and LCID fields (the specific field names are not limited)
  • the first data packet to be transmitted is the data to be sent by the terminal device, which can be understood as a MAC SDU.
  • the terminal device Before generating the first MAC PDU, the terminal device can determine the resource size occupied by the first MAC header based on the format of the MAC header, and determine the resource size occupied by the first MAC SDU based on the size of the RLC PDU.
  • the first MAC PDU can consist of the first MAC header and the first MAC SDU.
  • the size of the time-frequency resources occupied by the first data packet to be transmitted (or the size of the transmission resources occupied by the first MAC PDU) is equal to the sum of the resource sizes occupied by the first MAC header and the first MAC SDU.
  • the terminal device can then compare the size of the transmission resources configured by the base station with the size of the time-frequency resources occupied by the first data packet to be transmitted (or the size of the transmission resources occupied by the first MAC PDU). If they are equal, the first MAC header can be generated, and the first MAC PDU can be further generated based on the first MAC header and the first MAC SDU.
  • the first MAC PDU needs to carry padding bits.
  • the first MAC header can carry a first field to indicate the length of the MAC PDU, or the first MAC header can carry a field to indicate the length of the padding bits.
  • the first data packet needs to be split into multiple RLC PDUs for transmission. This will be described below with reference to an embodiment of the terminal device sending the first MAC PDU and the second MAC PDU; it will not be elaborated here.
  • the terminal device can report the size of the cached data or the size of the data to be transmitted to the base station via a buffer status report (BSR).
  • BSR buffer status report
  • the BSR can indicate the size of the RLC PDU cached at the first RLC layer.
  • the base station can know the range of data to be transmitted by the terminal device based on the BSR and allocate transmission resources accordingly.
  • the base station can send first resource configuration information to the terminal device based on the BSR.
  • the BSR can be triggered according to different bearers or logical channels.
  • the BSR can carry logical channel information to indicate the logical channel mentioned in the data.
  • multiple BSRs can be carried in one MAC PDU and sent.
  • the multiple BSRs can be carried in one MAC CE of the MAC PDU or multiple MAC CEs of the MAC PDU, without specific limitation.
  • the resources scheduled by the base station can indicate which logical channel the resource is allocated to for the data packet to be transmitted; that is, the base station scheduling resource information includes logical channel information.
  • the terminal device may receive first information from the base station before S101.
  • This first information can be used by the terminal device to determine whether to send the aforementioned first MAC PDU, specifically, whether to send a MAC PDU that does not contain the L field. Therefore, the terminal device can determine whether to execute the process shown in Figure 7 based on the first information, or in other words, the terminal device can determine whether to execute S101 and subsequent steps based on the first information.
  • the first information may be switch information, used to indicate whether to send the aforementioned first MAC PDU or to indicate whether to send it in a single-bearer mode.
  • the terminal device when the first information takes a first value (e.g., 1), it is used by the terminal device to determine whether to send the first MAC PDU; when the first information takes a second value (e.g., 0), it is used by the terminal device to determine whether to send the aforementioned first MAC PDU.
  • a first value e.g. 1
  • a second value e.g. 0
  • the first information can be an indication for a single MAC packet transmission process (including the transmission of at least one RLC PDU). For example, when the first information takes a first value, it indicates single-bearer transmission; when the first information takes a second value, it indicates closing or stopping single-bearer transmission. That is, the first information can be used to indicate whether the terminal device adopts single-bearer transmission mode. If single-bearer transmission mode is adopted, the terminal device can determine to execute the scheme in Figure 7.
  • the indication of single-bearer transmission can be applied to the transmission process of at least one RLC PDU on a certain bearer, and the scheme in Figure 7 can be executed until the terminal device receives an indication to close or stop single-bearer transmission.
  • the MAC layer Upon receiving a resource schedule, the MAC layer interacts with the RLC layer to determine how many RLC PDUs can be transmitted.
  • a first information value can indicate or instruct the terminal device to send a simplified or improved MAC header
  • a second information value can indicate or instruct the terminal device to turn off or stop sending a simplified or improved MAC header.
  • the first information can be an indication of whether to send a simplified or improved MAC header.
  • This simplified or improved MAC header does not include a field indicating the length of the MAC SDU.
  • the first information can also be applied to a transmission process carrying at least one RLC PDU.
  • the terminal device can execute the scheme in Figure 7 until it receives an indication to turn off or stop sending a simplified or improved MAC header.
  • the first information can be an indication for a single MAC packet transmission process. For example, it can be used to indicate or indicate that the first MAC PDU contains only one MAC SDU, or it can be said that the first information can be used to indicate or indicate that the first MAC PDU is sent using a single-bearer transmission method.
  • this indication can be understood as being effective only for the first MAC PDU.
  • the terminal device may use the scheme in Figure 7 in the next transmission of RLC PDU, and subsequent transmission processes may not use this method.
  • this first information can originate from a base station.
  • the base station can send the first information based on the terminal type information of the terminal device. For example, when the terminal type indicates that the terminal device communicating with the base station is an AIoT terminal or an IoT terminal, the base station can send the first information to the terminal.
  • the CU can send second information to the DU.
  • the DU can send first information to the terminal device based on the second information.
  • the second information can be used to indicate the terminal type or transmission type of the terminal device.
  • the DU can determine the MAC PDU transmission method, that is, the DU determines and instructs the terminal device to send a MAC PDU containing the simplified or improved MAC header shown in this application. For example, the DU can determine whether the terminal device communicating with the DU is an AIoT terminal or an IoT terminal based on the terminal type. Therefore, the DU can send the first information to the terminal device to instruct the terminal device to send a simplified or improved MAC header.
  • the CU can obtain the terminal type of the terminal device when the terminal device accesses the system.
  • the terminal type may include information such as the product model or identifier of the terminal device.
  • the CU can determine the transmission method of the MAC PDU.
  • the transmission type can be used to indicate or instruct the terminal device to send a simplified or improved MAC header.
  • the CU can determine whether the terminal is an AIoT terminal or an IoT terminal based on the terminal type.
  • the CU can send a transmission type indication (i.e., the second information) to the DU.
  • the DU sends first information to the terminal device based on the transmission type indication.
  • This transmission type indication can be used to instruct the terminal device to use a single-bearer transmission method, or to instruct the first MAC PDU to send the first MAC SDU using a single-bearer transmission method, or to instruct the first MAC PDU to send the first MAC SDU using a single-bearer transmission method.
  • the transmission type indication can indicate that the terminal device is sending a simplified or improved MAC header.
  • both the first and second information can be transmission type indications.
  • the CU can determine whether the terminal device is an AIoT terminal or an IoT terminal based on the terminal type. Further, the CU can send a transmission type indication to the DU, and the DU can forward the transmission type indication to the terminal device.
  • the terminal device sends the first MAC PDU.
  • S102 can be understood as the terminal device sending a first MAC PDU to the PHY layer.
  • the PHY layer can perform PHY layer processing such as scrambling and modulation on the first MAC PDU to obtain the signal to be transmitted over the air interface.
  • S102 can also be understood as the terminal device sending a signal to the base station through the air interface. This signal can be obtained by the terminal device's PHY layer based on the first MAC PDU.
  • the base station receives the first MAC PDU from the terminal device.
  • S103 can be understood as the base station's PHY layer performing descrambling and demodulation on the air interface transmitted signals, parsing the first MAC PDU carried on the air interface signals.
  • S103 can also be understood as the base station receiving air interface signals, which are obtained by the terminal device's PHY layer based on the first MAC PDU.
  • the base station obtains the data carried by the first MAC PDU.
  • the base station's MAC layer entity processing the first MAC PDU to obtain the first MAC SDU, and then sending the first MAC SDU to the upper layer. It can be understood that the base station's MAC layer can parse the first MAC PDU based on the format of the first MAC header to obtain the first MAC SDU. For example, assuming the first MAC header consists of an R field, an F field, an E field, and an LCID, occupying one byte, after demodulating and decoding the air interface signal, the base station can obtain the bit information.
  • the base station can determine the first bit of the bit information occupied by the first MAC header based on the aforementioned structure of the first MAC header, thereby determining the remaining bits of the bit information as the first MAC SDU, and performing subsequent processing.
  • subsequent processing includes the MAC layer entity sending the remaining bits to the RLC layer for RLC layer processing.
  • the MAC header of the MAC PDU generated by the terminal device may not carry a field indicating the length of the MAC SDU to reduce transmission overhead, thereby reducing the power consumption of the terminal device.
  • the first MAC PDU may include a MAC CE, which may be located before the MAC SDU.
  • the first MAC header may include at least one of the following: an N field, an E field, an F field, an L field, or an LCID.
  • the F field, L field, and LCID can be described with reference to Figure 4.
  • the E field can be used to indicate whether an extension of the L field exists. For example, if the E field takes a first value (e.g., 0) or does not exist, it indicates that no extension of the L field exists, which can be understood as the MAC header carrying only one L field.
  • the first MAC header occupies 1 byte and does not have an extended L field.
  • the number of bits occupied by the LCID can be reduced; for example, the LCID may occupy 3 bits, and correspondingly, a 3-bit L field may be included before the LCID.
  • the L field can be used to indicate that the first MAC PDU contains a 9-byte MAC SDU.
  • the F field may be an optional field, or the F field may be part of the L field.
  • the E field indicates the presence of an extended L field, which can be understood as the MAC header carrying an extended L field.
  • an extended L field which can be understood as the MAC header carrying an extended L field.
  • the first MAC header (b) in Figure 10 contains extended L and E fields.
  • This extended L field can be used to support indicating a longer MAC SDU length, in which case the total length of the first MAC header (b) can be 2 bytes.
  • the first MAC header can also be extended by bytes based on the first MAC header (b) in Figure 10, such as increasing the length to 3 or 4 bytes.
  • the added bytes can include extended L and E fields to support indicating the length of a longer MAC SDU.
  • the terminal device may also send a second MAC PDU.
  • the second MAC PDU may include a second MAC header and a second MAC SDU.
  • the second MAC header may be a header or a sub-header.
  • the second MAC SDU may carry uplink data.
  • the second MAC header may include a third field, which can be used to determine the length of the second MAC SDU, and correspondingly, the base station can determine the location of the second MAC SDU.
  • the third field can indicate the length of the second MAC SDU. Accordingly, the base station can know that the bits occupied by the second MAC SDU in the second MAC PDU are the bits of that length after the second MAC header. Therefore, the base station can use the bits of that length after the second MAC header as the second MAC SDU.
  • the third field can indicate the length of the padding bits. Accordingly, the base station can know that the bit information corresponding to the second MAC PDU contains the second MAC header and padding bits of that length. The remaining bits are the bits corresponding to the second MAC SDU. Therefore, the base station can obtain the remaining bits as the second MAC SDU.
  • the second MAC SDU is related to the first MAC SDU.
  • the first MAC SDU and the second MAC SDU belong to the same PDCP PDU (excluding the possibility that other MAC SDUs may also carry data within the same PDCP PDU) or RLC SDU.
  • the data carried by the first MAC SDU and the data carried by the second MAC SDU belong to the same radio bearer.
  • the base station can configure the transmission resources of the MAC PDU to the terminal device through resource configuration information.
  • the terminal device can send data through multiple MAC PDUs. For example, the terminal device can determine the first MAC PDU based on the size of the transmission resource.
  • the transmission resource size occupied by the first MAC PDU is equal to the size of the transmission resource configured in the first resource configuration information; that is, the remaining data is sent through other MAC PDUs.
  • the base station can also configure the transmission resources of subsequent MAC PDUs through resource configuration information.
  • the RLC SDU needs to be sent through multiple MAC SDUs. That is, the terminal device can send multiple MAC PDUs, and the multiple MAC PDUs are used to carry multiple MAC SDUs respectively.
  • the plurality of MAC PDUs includes a first MAC PDU and a second MAC PDU.
  • other MAC PDUs may be included between the first and second MAC PDUs. That is, when RLC SDUs need to be segmented for transmission, or when the configured transmission resource size is smaller than the size of the terminal device's RLC SDU, the last MAC PDU (i.e., the second MAC PDU) among the multiple MAC PDUs corresponding to the same RLC SDU sent by the terminal device may carry a third field, such as an L field or a field indicating the length of padding bits.
  • the other MAC PDUs among the plurality of MAC PDUs completely contain one or more RLC PDUs and do not require padding bits, they may not carry the field indicating the length of the MAC SDU; otherwise, they may need to carry it. This method can reduce the transmission overhead of MAC PDUs.
  • the third field mentioned above can be the L field in the second MAC header, or it can be any other field, without specific restrictions.
  • the second MAC header may include an F field, which can be used to indicate whether the second MAC header contains a third field.
  • the F field can also indicate the length of the third field. For example, a first value for the F field indicates that the second MAC header does not contain a third field. Conversely, a second value for the F field indicates that the second MAC header contains a third field of a certain length (e.g., 8 bits, 16 bits, or longer).
  • the third field may carry either the length information of the second MAC SDU or the length information of the padding bits.
  • the length information of the second MAC SDU may be, for example, the byte length or bit length occupied by the second MAC SDU, or it may be an index value corresponding to the byte length or bit length occupied by the second MAC SDU.
  • the length information of the padding bits may be, for example, the byte length or bit length occupied by the padding bits, or it may be an index value corresponding to the byte length or bit length occupied by the padding bits.
  • the third field may carry the one with lower transmission overhead, either the length information of the second MAC SDU or the length information of the padding bits, to further reduce transmission overhead.
  • the MAC PDU may contain padding bits.
  • This MAC PDU then serves as the second MAC PDU, meaning it can carry the third field to indicate the size of the MAC SDU or padding bits.
  • the last MAC PDU carrying data from the same PDCP PDU does not contain padding bits, then it does not need to carry the third field, i.e., it does not need to indicate the length of the MAC SDU or the length of the padding bits.
  • This MAC PDU can refer to the first MAC PDU, meaning it does not carry a field indicating the length of the MAC SDU (i.e., the MAC header does not carry the L field).
  • the embodiments provided in this application can also be applied to scenarios with multiple RLC SDUs.
  • the application of the process shown in Figure 7 or Figure 9 in scenarios with multiple RLC SDUs can be determined based on the size of the time-frequency resources configured by the base station. Specifically, taking two consecutive RLC SDUs as an example, if the size of the transmission resources occupied by the MAC PDU corresponding to the previous RLC SDU is the same as the size of the transmission resources configured by the base station, that is, the previous RLC SDU does not need to fill bits, then the MAC PDU corresponding to the previous RLC SDU can be considered as the first MAC PDU described in this application.
  • next RLC SDU needs to fill bits, that is, the transmission resources to be transmitted are greater than the next RLC SDU
  • the last MAC PDU corresponding to the next RLC SDU can be considered as the second MAC PDU. It is also understood that among the MAC PDUs corresponding to the next RLC SDU, those not the last MAC PDU can be used as the third MAC PDU.
  • the RLC PDU corresponding to the first RLC SDU can generate the first MAC PDU described in this application, and the last MAC PDU corresponding to the nth RLC SDU is the second MAC PDU described in this application, and the other MAC PDUs between the first MAC PDU and the second MAC PDU can be used as the third MAC PDU described in this application.
  • this application provides a communication device, which includes modules, units, or means that perform the method steps in the above method embodiments.
  • the functions, units, or means can be implemented by software, hardware, or hardware executing corresponding software.
  • device 1200 may include processing module 1201 and transceiver module 1202.
  • the transceiver module 1202 may include a sending module and/or a receiving module.
  • the sending module is used to perform the sending operation in the above method embodiments.
  • the receiving module is used to perform the receiving operation in the above method embodiments.
  • the communication device 1200 may include a transmitting module but not a receiving module.
  • the communication device 1200 may include a receiving module but not a transmitting module. Specifically, it depends on whether the above-described scheme executed by the communication device 1200 includes both transmitting and receiving actions.
  • the processing module 1201 is used for data processing.
  • the transceiver module 1202 can realize the corresponding communication functions.
  • the communication device 1200 may further include a storage module, which can be used to store instructions and/or data.
  • the processing module 1201 can read the instructions and/or data in the storage module so that the communication device 1200 can implement the aforementioned method embodiments.
  • the communication device 1200 may be a first communication device or a component configurable on the first communication device.
  • the first communication device may be, for example, a terminal device (as shown in FIG7 or FIG9).
  • the processing module 1201 is used to perform processing-related operations of the terminal device in the above method embodiments.
  • the transceiver module 1202 is used to perform sending and/or receiving-related operations of the terminal device in the above method embodiments.
  • the processing module 1201 can be used to execute S101, that is, to obtain the first MAC PDU.
  • the transceiver module 1202 can be used to execute S102, that is, to send the first MAC PDU.
  • the transceiver module 1202 can be used to receive first information and send a first MAC PDU.
  • the processing module 1201 can be used to generate a first MAC PDU based on the first information.
  • the communication device 1200 can be a second communication device or a component configurable within a second communication device.
  • the second communication device is, for example, a network device (such as a base station, CU, DU, or RU as shown in Figure 7 or 9).
  • the processing module 1201 is used to perform processing-related operations of the network device in the above method embodiments.
  • the transceiver module 1202 is used to perform transmission and/or reception-related operations of the network device in the above method embodiments.
  • the transceiver module 1202 can be used to receive the first MAC PDU.
  • the processing module 1201 can be used to determine the data carried by the first MAC PDU.
  • the transceiver module 1202 can be used to receive second information from the CU and send first information to the terminal device.
  • the processing module 1201 can be used to determine the first information based on the second information.
  • the transceiver module 1202 can be used to send second information to the DU.
  • the processing module 1201 can be used to determine the second information based on the terminal type or transmission type of the terminal device.
  • the processing module 1201 in the above embodiments can be implemented by at least one processor or processor-related circuitry.
  • the transceiver module 1202 can be implemented by a transceiver or transceiver-related circuitry.
  • the transceiver module 1202 can also be referred to as a communication module or communication interface.
  • an embodiment of this application also provides a communication device 1300, including:
  • At least one processor 1301 and a communication interface 1303 communicatively connected to the at least one processor 1301; the at least one processor 1301 causes the device to perform the method steps in the above method embodiments through the communication interface 1303 by executing instructions stored in at least one memory 1302.
  • the at least one memory 1302 is located outside the device 1300.
  • the device 1300 includes at least one memory 1302, which is connected to at least one processor 1301, and stores instructions executable by the at least one processor 1301.
  • Figure 13 shows, with dashed lines, that the memory 1302 is optional for the device 1300.
  • the processor 1301 and the memory 1302 can be coupled through an interface circuit or integrated together; no restriction is imposed here.
  • This application embodiment does not limit the specific connection medium between the processor 1301, memory 1302, and communication interface 1303.
  • the processor 1301, memory 1302, and communication interface 1303 are connected via a bus 1304, which is represented by a thick line.
  • the connection methods between other components are for illustrative purposes only and are not intended to be limiting.
  • the bus can be classified as an address bus, data bus, control bus, etc. For ease of illustration, it is represented by a single thick line in Figure 13, but this does not indicate that there is only one bus or one type of bus.
  • the first communication device may include a processor, a memory, and a transceiver.
  • the memory may store computer program code
  • the transceiver includes a transmitter and a receiver.
  • the processor is primarily used for processing communication protocols and data; for example, controlling the first communication device, executing software programs, and processing the data from those programs.
  • the memory is mainly used to store software programs and data.
  • the transmitter is used to send signals to other communication devices or equipment, and the receiver is used to receive signals from other communication devices or equipment.
  • the chip may include a processor, a memory, and a transceiver.
  • the transceiver may be an input/output circuit or a communication interface.
  • the processor may be a processing module integrated on the chip, a microprocessor, or an integrated circuit.
  • the second communication device may include a processor, a memory, and a transceiver.
  • the memory may store computer program code
  • the transceiver includes a transmitter and a receiver.
  • the processor is primarily used for processing communication protocols and data; controlling the secondary communication device; executing software programs; and processing the data from those programs.
  • the memory is mainly used for storing software programs and data.
  • the transmitter is used to send signals to other communication devices or equipment, and the receiver is used to receive signals from other communication devices or equipment.
  • the chip may include a processor, a memory, and a transceiver.
  • the transceiver may be an input/output circuit or a communication interface.
  • the processor may be a processing module integrated on the chip, a microprocessor, or an integrated circuit.
  • the processor mentioned in the embodiments of this application can be implemented in hardware or software.
  • the processor can be a logic circuit, integrated circuit, etc.
  • the processor can be a general-purpose processor, implemented by reading software code stored in memory.
  • the processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • a general-purpose processor can be a microprocessor or any conventional processor.
  • Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory.
  • Volatile memory can be random access memory (RAM), which is used as an external cache.
  • RAM dynamic random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • DDR SDRAM double data rate synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous linked dynamic random access memory
  • DR RAM direct rambus RAM
  • the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component
  • the memory storage module
  • embodiments of this application also provide a computer-readable storage medium, including a program or instructions, which, when run on a computer, cause the methods in the above method embodiments to be executed.
  • This application also provides a chip or chip system, including circuitry (such as analog circuitry and/or logic circuitry; or understood as the chip system including one or more processors, which may include circuitry, etc.), or understood as the chip including a processor.
  • the circuitry or processor is coupled to a memory for executing computer programs or instructions stored in the memory, thereby implementing the methods shown in Figures 3 and 4 or the various embodiments of this application.
  • the chip or chip system may also include input/output interfaces.
  • the chip can receive information from other modules (such as radio frequency or antenna) of the terminal device through the input/output interface; this information may be sent to the terminal device by other communication devices such as base stations.
  • the chip can send information to other modules (such as radio frequency or antenna) in the terminal device through the input/output interface; this information may be sent by the terminal device to other communication devices such as base stations.
  • embodiments of this application also provide a computer program product, including instructions that, when run on a computer, cause the methods in the above method embodiments to be executed.
  • embodiments of this application also provide a communication system, which may include a first communication device and a second communication device.
  • the first communication device can be used to implement the methods implemented by the first communication device in the above method embodiments
  • the second communication device can be used to implement the methods implemented by the second communication device in the above method embodiments.
  • the first communication device is used to execute the actions implemented by the terminal device in the process shown in FIG7 or FIG9
  • the second communication device is used to execute the actions implemented by the base station, CU, or DU in the process shown in FIG7 or FIG9.
  • embodiments of this application also provide a communication system, which may include a first communication device and a second communication device.
  • the first communication device is a terminal device
  • the second communication device is a base station, CU, DU, RU, or reader/writer, etc.
  • this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and/or one or more block diagrams.
  • These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and/or one or more block diagrams.
  • At least one means one or more, and “more than one” means two or more.
  • At least one of the following” or similar expressions refer to any combination of these items, including any combination of single or plural items.
  • at least one of a, b, or c can mean: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.
  • “/” means “or,” for example, a/b means a or b.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Procédé de communication et appareil, qui sont utilisés pour réduire le surdébit de transmission d'une PDU MAC. Le procédé comprend les étapes suivantes : un dispositif terminal acquiert une première PDU MAC, la première PDU MAC comprenant un premier en-tête MAC et une première SDU, le premier en-tête MAC ne transportant pas un premier champ, et le premier champ étant utilisé pour indiquer la longueur de la première SDU ; et le dispositif terminal envoie la première PDU MAC.
PCT/CN2025/099905 2024-06-19 2025-06-09 Procédé de communication, et appareil Pending WO2025261202A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202410798152.4A CN121174290A (zh) 2024-06-19 2024-06-19 一种通信方法及装置
CN202410798152.4 2024-06-19

Publications (1)

Publication Number Publication Date
WO2025261202A1 true WO2025261202A1 (fr) 2025-12-26

Family

ID=98044344

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2025/099905 Pending WO2025261202A1 (fr) 2024-06-19 2025-06-09 Procédé de communication, et appareil

Country Status (2)

Country Link
CN (1) CN121174290A (fr)
WO (1) WO2025261202A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110753076A (zh) * 2018-07-24 2020-02-04 中国移动通信有限公司研究院 一种数据发送及接收方法、装置和存储介质
CN112055999A (zh) * 2018-04-30 2020-12-08 三星电子株式会社 发送和接收消息3协议数据单元的装置和方法
US20230319628A1 (en) * 2022-03-10 2023-10-05 Qualcomm Incorporated Protocol overhead reduction for medium access control
WO2024071760A1 (fr) * 2022-09-27 2024-04-04 Lg Electronics Inc. Procédé et appareil de transmission d'unité de données sans champ de longueur dans un système de communication sans fil

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112055999A (zh) * 2018-04-30 2020-12-08 三星电子株式会社 发送和接收消息3协议数据单元的装置和方法
CN110753076A (zh) * 2018-07-24 2020-02-04 中国移动通信有限公司研究院 一种数据发送及接收方法、装置和存储介质
US20230319628A1 (en) * 2022-03-10 2023-10-05 Qualcomm Incorporated Protocol overhead reduction for medium access control
WO2024071760A1 (fr) * 2022-09-27 2024-04-04 Lg Electronics Inc. Procédé et appareil de transmission d'unité de données sans champ de longueur dans un système de communication sans fil

Also Published As

Publication number Publication date
CN121174290A (zh) 2025-12-19

Similar Documents

Publication Publication Date Title
JP7273057B2 (ja) サービスデータ適応プロトコルレイヤを利用したサービス品質フロー再マッピングの容易化
US12470328B2 (en) Method for sidelink interface duplication transmission, terminal, and network-side device
KR102827523B1 (ko) 무선 베어러 구성 방법, 장치, 및 시스템
US11825474B2 (en) Service transmission method and apparatus
CN115943595B (zh) 辅小区激活方法、终端设备和网络设备
CN113691359B (zh) 用于复制数据传输的方法和设备
US12328741B2 (en) Resource scheduling method, terminal device, and network device
JP2023526459A (ja) バッファ状態報告の強化
US11528640B2 (en) Base station device, and method for transmitting data and signal
KR20210134398A (ko) 통신 방법 및 장치
WO2021081898A1 (fr) Procédé de communication et appareil de communication
US20240365160A1 (en) Communication method, apparatus, and system
WO2023138622A1 (fr) Procédé et appareil de configuration de ressources, dispositif de réseau et dispositif terminal
CN115915407A (zh) 数据传输方法及装置
WO2025261202A1 (fr) Procédé de communication, et appareil
WO2024212059A1 (fr) Dispositifs et procédés de communication
US20250351161A1 (en) Data transmission method and communication apparatus
WO2025194621A1 (fr) Procédé, appareil et système de transmission de données
RU2785091C1 (ru) Система, устройство и способ конфигурации радиоканала-носителя
CN121056977A (zh) 一种通信方法、装置和可读存储介质
WO2025031191A1 (fr) Procédé et appareil de communication
WO2025195262A1 (fr) Procédé et appareil de communication
CN119520635A (zh) 一种数据传输方法和装置
WO2025214389A1 (fr) Procédé d'indication de ressource de domaine fréquentiel et appareil associé
CN120417086A (zh) 一种跨无线接入技术的小区管理方法及通信装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 25829683

Country of ref document: EP

Kind code of ref document: A1