Communication method and communication device

Abstract

Disclosed are a communication method and a communication device, which relate to the field of communications, and a terminal device can successfully decode an MAC sub PDU of an OD-SIB1 on the basis of identification information of a preset length in a case where a UL-WUS configuration message does not include a total NumberOfRA-Preambles parameter, thereby improving communication efficiency and saving overhead. The communication method is applied to terminal equipment, and comprises the following steps: sending a WUS used for requesting network equipment to send OD-SIB1 to the network equipment; receiving the MAC PDU from the network equipment; the MAC PDU comprises a first MAC sub-PDU and identification information with a preset length; the first MAC sub-PDU is the MAC sub-PDU of the OD-SIB1, and the identification information of the preset length is used for indicating that the adjacent MAC sub-PDU after the identification information of the preset length is the first MAC sub-PDU.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular to a communication method and a communication device. Background Art

[0002] In an on-demand request scenario, an R19 UE, which complies with the R19 technical specification developed by the 3rd Generation Partnership Project (3GPP) standardization organization, sends an uplink wake-up signal (UL-WUS) requesting the on-demand first system information block (OD-SIB1) to a network device. The UE then receives a random access response (RAR) message from the network device. The RAR message is encapsulated in a medium access control protocol data unit (MAC PDU) on the network device, which includes the MAC sub-PDU for the OD-SIB1.

[0003] Currently, R19 UEs decode the MAC sub-PDU of OD-SIB1 by obtaining the total number of random access preambles (physical random access channel preambles, PRACH preambles) parameter. Since the first system information block SIB1 has not yet been received from the network device when the R19 UE receives the RAR message, it is unable to obtain the total number of RA-Preambles parameter broadcast by SIB1. Therefore, the R19 UE can only obtain the total number of RA-Preambles parameter from the UL-WUS configuration message that has been pre-configured with the parameter. However, this increases the overhead of the UL-WUS configuration. Summary of the Invention

[0004] An embodiment of the present application provides a communication method and a communication device, in which a terminal device can successfully decode the MAC sub-PDU of OD-SIB1 based on identification information of a preset length when the totalNumberOfRA-Preambles parameter is not included in the UL-WUS configuration message, thereby improving communication efficiency and saving overhead.

[0005] To achieve the purpose, the embodiments of the present application adopt the following technical solutions: In a first aspect, a communication method is provided, which is applied to a terminal device, and the method includes: sending a wake-up signal WUS to a network device; the WUS is used to request the network device to send an on-demand first system information block OD-SIB1; receiving a media access control protocol data unit MAC PDU from the network device; the MAC PDU includes a first MAC sub-PDU and identification information of a preset length; the first MAC sub-PDU is a MAC sub-PDU of OD-SIB1, and the identification information of the preset length is used to indicate that the MAC sub-PDU that follows and is adjacent to the identification information of the preset length is the first MAC sub-PDU.

[0006] The above communication method is applied to a terminal device. First, the terminal device sends a WUS to the network device to request the sending of OD-SIB1. Secondly, it receives a MAC PDU from the network device. Finally, the terminal device locates the position of the first MAC sub-PDU (i.e., the MAC sub-PDU of OD-SIB1) in the MAC PDU by decoding the identification information of the preset length that is before and adjacent to the MAC sub-PDU of OD-SIB1, thereby successfully decoding the first MAC sub-PDU. With this communication method, the terminal device can successfully decode the MAC sub-PDU of OD-SIB1 based on the identification information of the preset length when the totalNumberOfRA-Preambles parameter is not included in the UL-WUS configuration message, thereby improving communication efficiency and saving overhead.

[0007] In an implementation manner of the first aspect, the MAC PDU also includes at least one second MAC sub-PDU, and the second MAC sub-PDU is a MAC sub-PDU before the identification information of a preset length; the first byte of the second MAC sub-PDU includes a first field, the value of the first field is a first value or a second value, and the value of the first field is the first value used to characterize that the first byte of the second MAC sub-PDU also includes a second field, and the value of the first field is the second value used to characterize that the first byte of the second MAC sub-PDU does not include the second field; the value of the second field is a third value or a fourth value, and the value of the second field is the third value used to characterize that the MAC PDU includes the first MAC sub-PDU, and the value of the second field is the fourth value used to characterize that the MAC PDU does not include the first MAC sub-PDU; the method also includes: decoding the first byte of the MAC PDU; and continuing to decode the MAC PDU when the value of the first field is the first value and the value of the second field is the third value.

[0008] In this implementation, since the second MAC sub-PDU precedes the identification information of the preset length, and the value of the first field of the first byte of the second MAC sub-PDU is used to indicate whether the first byte of the second MAC sub-PDU includes the second field, and the value of the second field of the first byte of the second MAC sub-PDU is used to indicate whether the MAC PDU includes the first MAC sub-PDU. When the value of the first field of the first byte of the second MAC sub-PDU indicates that the first byte of the second MAC sub-PDU includes the second field, the second MAC sub-PDU is the first MAC sub-PDU in the MAC PDU, and the first byte of the second MAC sub-PDU is also the first byte of the MAC PDU. In this way, when decoding the MAC PDU, the terminal device can first try to decode the first byte of the MAC PDU to determine whether the MAC PDU includes the first MAC sub-PDU, and thus determine whether to end or continue decoding the MAC PDU. When the value of the first field is the first value and the value of the second field is the third value, the terminal device continues to decode the MAC PDU, indicating that the first byte of the MAC PDU not only includes the second field, but also includes the first MAC sub-PDU. Therefore, the terminal device continues to decode the MAC PDU. With this communication method, the terminal device can successfully decode the MAC sub-PDU of OD-SIB1 based on identification information of a preset length when the UL-WUS configuration message does not include the totalNumberOfRA-Preambles parameter, thereby improving communication efficiency and saving overhead.

[0009] In an implementation manner of the first aspect, the method further includes: when the value of the first field is the first value and the value of the second field is the fourth value, ending decoding the MAC PDU.

[0010] In this implementation, when the value of the first field is the first value and the value of the second field is the fourth value, the terminal device ends decoding the MAC PDU, indicating that the first byte of the MAC PDU includes the second field but the MAC PDU does not include the first MAC sub-PDU. At this time, if the terminal device continues to decode the MAC PDU, additional time and power consumption will be generated. Therefore, the terminal device ends decoding the MAC PDU, thereby saving decoding time and reducing power consumption.

[0011] In an implementation manner of the first aspect, the method further includes: when the value of the first field is the second value, continuing to decode the MAC PDU.

[0012] In this implementation, when the value of the first field is the second value, the MAC PDU is assumed to include the first MAC sub-PDU, and therefore the terminal device continues to decode the MAC PDU. With this communication method, the terminal device can successfully decode the MAC sub-PDU of OD-SIB1 based on identification information of a preset length when the UL-WUS configuration message does not include the totalNumberOfRA-Preambles parameter, thereby improving communication efficiency and reducing overhead.

[0013] In an implementation manner of the first aspect, a value of the third field of the first byte of the second MAC sub-PDU adjacent to the identification information of the preset length is a target value.

[0014] In this implementation, the value of the third field of the first byte of the second MAC sub-PDU adjacent to the identification information of the preset length is set to the target value in order to indicate that the second MAC sub-PDU is the last second MAC sub-PDU.

[0015] In an implementation manner of the first aspect, the identification information of the preset length is at least 6 consecutive bytes of all 1s or at least 7 consecutive bytes of all 0s.

[0016] In this implementation, the identification information of the preset length is set to at least 6 consecutive bytes of all 1s or at least 7 consecutive bytes of all 0s in order to distinguish the value ranges of other fields in the MAC PDU and make the identification information of the preset length unique, that is, uniquely determined, so that the position of the first MAC sub-PDU in the MAC PDU can be uniquely determined.

[0017] In an implementation manner of the first aspect, the second field is a reserved R field.

[0018] In this implementation, according to the three types of the second MAC sub-PDU, in the first byte of the second MAC sub-PDU, since other fields have specific functions and only the R field is a reserved field, the R field can be used for customized functions, that is, the value of the R field is used to indicate whether the MAC PDU includes the first MAC sub-PDU.

[0019] In a second aspect, a communication method is provided, which is applied to a network device, and the method includes: receiving a wake-up signal WUS from a terminal device; the WUS is used to request the sending of an on-demand first system information block OD-SIB1; sending a media access control protocol data unit MAC PDU to the terminal device to trigger the terminal device to decode the MAC PDU; the MAC PDU includes a first MAC sub-PDU and identification information of a preset length; the first MAC sub-PDU is a MAC sub-PDU of OD-SIB1, and the identification information of the preset length is used to indicate that the MAC sub-PDU that follows and is adjacent to the identification information of the preset length is the first MAC sub-PDU.

[0020] The above-mentioned communication method is applied to a network device. First, the network device receives a WUS from a terminal device for requesting the sending of OD-SIB1. Secondly, a MAC PDU is sent to the terminal device to trigger the terminal device to decode the MAC PDU. The network device identifies the position of the first MAC sub-PDU (i.e., the MAC sub-PDU of OD-SIB1) in the MAC PDU by using identification information of a preset length that is before and adjacent to the MAC sub-PDU of OD-SIB1, so that the terminal device can successfully decode the first MAC sub-PDU. With this communication method, the terminal device can successfully decode the MAC sub-PDU of OD-SIB1 based on the identification information of the preset length when the totalNumberOfRA-Preambles parameter is not included in the UL-WUS configuration message, thereby improving communication efficiency and saving overhead.

[0021] In an implementation manner of the second aspect, the MAC PDU also includes at least one second MAC sub-PDU, and the second MAC sub-PDU is a MAC sub-PDU before the identification information of a preset length; the first byte of the second MAC sub-PDU includes a first field; the first field is a first value or a second value; the value of the first field is a first value used to characterize that the first byte of the second MAC sub-PDU also includes a second field, and the value of the first field is a second value used to characterize that the first byte of the second MAC sub-PDU does not include the second field; the value of the second field is a third value or a fourth value, the value of the second field is a third value used to characterize that the MAC PDU includes the first MAC sub-PDU, and the value of the second field is a fourth value used to characterize that the MAC PDU does not include the first MAC sub-PDU.

[0022] In an implementation manner of the second aspect, a value of the third field of the first byte of the second MAC sub-PDU adjacent to the identification information of the preset length is a target value.

[0023] In an implementation manner of the second aspect, the identification information of the preset length is at least 6 consecutive bytes of all 1s or at least 7 consecutive bytes of all 0s.

[0024] In an implementation manner of the second aspect, the second field is a reserved R field.

[0025] In a third aspect, a communication device is provided, comprising a processor and a memory, wherein instructions are stored in the memory. When the processor executes the instructions, the communication device executes the communication method of the first aspect and any embodiment thereof, or executes the communication method of the second aspect and any embodiment thereof.

[0026] In a fourth aspect, a computer-readable storage medium is provided, on which a computer program or instruction is stored. When the computer program or instruction is executed, the computer executes the communication method of the first aspect and any embodiment thereof, or executes the communication method of the second aspect and any embodiment thereof.

[0027] Among them, the technical effects brought about by the design methods of the third and fourth aspects can refer to the technical effects brought about by different design methods in the first or second aspects, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 A schematic diagram of the architecture of a wireless communication system provided in an embodiment of the present application; Figure 2 A schematic diagram of the structure of a terminal device and a network device provided for related technologies; Figure 3 A flow chart of a communication method provided for related technologies; Figure 4 A flow chart of a communication method provided in an embodiment of the present application; Figure 5 A schematic diagram of the structure of a MAC PDU provided in an embodiment of the present application; Figure 6 A schematic diagram of the structure of a MAC sub-PDU type provided in an embodiment of the present application; Figure 7 A schematic diagram of a second terminal device determining whether the value of the fourth field of the first byte of the second MAC sub-PDU is the same as the sent target identification code index provided by an embodiment of the present application; Figure 8 A schematic diagram of a second terminal device provided in an embodiment of the present application for determining whether the value of the third field of the first byte of the second MAC sub-PDU is a target value. DETAILED DESCRIPTION

[0029] The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

[0030] First, some concepts involved in this application are described.

[0031] The terms "first", "second", etc. involved in the embodiments of the present application are only used to distinguish features of the same type and cannot be understood as indicating relative importance, quantity, order, etc.

[0032] The terms "exemplary" or "for example" in the embodiments of this application are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0033] The technical solutions provided in this application can be applied to various communication systems, such as: long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, sidelink communication system, universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication system, non-terrestrial network (NTN) communication system, fifth generation (5G) mobile communication system, new radio access technology (NR), future communication systems, and 5G Advanced communication system. Among them, 5G mobile communication system can include non-standalone (NSA) and / or standalone (SA) networking. The technical solutions provided in this application can also be applied to future communication systems. This application does not limit this. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above as well as other systems and radio technologies.

[0034] Attachment Figure 1 The wireless communication system 100 may include network devices, such as Figure 1 The wireless communication system 100 may also include a terminal device, such as an attached Figure 1 The terminal device 120 is shown. The network device 110 and the terminal device 120 can communicate with each other via a wireless link.

[0035] Attachment Figure 1 The example shows one network device 110 and one terminal device 120. Optionally, the wireless communication system 100 may further include multiple network devices 110 and multiple terminal devices 120.

[0036] The network devices in this application may be network-side devices such as access network devices and core network devices. Access network devices are sometimes also referred to as access nodes. Access network devices have wireless transceiver functions and are used to communicate with terminals. Access network devices include but are not limited to base stations (base stations) in the above-mentioned communication systems, evolved NodeBs (eNodeBs), transmission reception points (TRPs), next-generation NodeBs (gNBs) in 5G mobile communication systems, access network devices or modules of access network devices in open access networks (ORAN) systems, satellites in NTN communication systems, base stations in future mobile communication systems, or access nodes in WiFi systems. Access network devices may also be modules or units that can implement some of the functions of a base station. Access network devices may be macro base stations, micro base stations or indoor stations, relay nodes or donor nodes, or wireless controllers in cloud radio access network (CRAN) scenarios. Optionally, access network devices may also be servers, wearable devices, or vehicle-mounted devices. For example, the access network device in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). Multiple access network devices in a communication system can be base stations of the same type or different types. A base station can communicate with a terminal or through a relay station. A terminal can communicate with multiple base stations using different access technologies. The embodiments of this application do not limit the specific technology or device form used by the access network device. In this application, the access network device is referred to as a network device.

[0037] In this application, the device for implementing the function of a network device can be a network device, or a device that can support the network device to implement the function, such as a processor, circuit, chip, or chip system, etc. The device can be installed in the network device or connected to the network device for use. In the technical solution provided in this application, the technical solution provided in this application is described by taking the device for implementing the function of a network device as an example.

[0038] The terminal device in this application may be a wireless terminal device capable of receiving network device scheduling and instruction information. A wireless terminal device may be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing device connected to a wireless modem. For example, a terminal device may communicate with one or more core networks or the Internet via a radio access network (RAN). A terminal device may also be referred to as a terminal, user equipment (UE), mobile station, or mobile terminal. The terminal device 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), ultra-reliable low-latency communication (URLLC), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearables, smart transportation, smart cities, or satellite communications. The terminal may be a mobile phone, tablet computer, computer with wireless transceiver function, wearable device, vehicle, aircraft (such as drone, helicopter, airplane), hot air balloon, ship, robot, robotic arm, or smart home device, etc. The embodiments of the present application do not limit the form of the terminal device.

[0039] In this application, the device for implementing the function of a terminal device can be a terminal device, or a device that can support the terminal device to implement the function, such as a processor, circuit, chip, chip system, etc. The device can be installed in the terminal device or connected to the terminal device for use. In the technical solution provided in this application, the technical solution provided in this application is described by taking the terminal device as an example in which the device for implementing the function of the terminal device is a terminal device.

[0040] The access network equipment and terminal equipment can be fixed or movable. The access network equipment and terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on the water surface; they can also be deployed on airplanes, balloons and artificial satellites in the air. The embodiments of the present application do not limit the application scenarios of the access network equipment and terminal equipment. The access network equipment and terminal equipment can be deployed in the same scenario or different scenarios. For example, the access network equipment and terminal equipment are deployed on land at the same time; or, the access network equipment is deployed on land and the terminal equipment is deployed on the water surface, etc., and no further examples are given.

[0041] In practical applications, multiple network devices can collaborate to assist terminal devices in achieving wireless access, with different network devices each implementing portions of a base station's functionality. For example, a network device can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be separate or included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or radio unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0042] In different systems, the CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meanings. For example, in the ORAN system, the CU may also be called an O-CU (Open CU), the DU may also be called an O-DU, the CU-CP may also be called an O-CU-CP, the CU-UP may also be called an O-CU-UP, and the RU may also be called an O-RU. Any of the CU (or CU-CP, CU-UP), DU, and RU in this application may be implemented as a software module, a hardware module, or a combination of software and hardware modules. The CU (or CU-CP and CU-UP), DU, and RU can implement different protocol layer functions.

[0043] Figure 2 The terminal device 120 includes a first processor 121 , a first memory 122 , and a first transceiver 123 .

[0044] The first processor 121 may include one or more processing units, for example, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a microcontroller unit (MCU), a programmable logic device (PLD), an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU). Different processing units may be independent devices or integrated into one or more processors.

[0045] The first memory 122 may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DRRAM).

[0046] The first memory 122 can be independent and connected to the first processor 121 via a bus. The first memory 122 can also be integrated with the first processor 121. The first memory 122 is used to store application code for executing the solution of the present application, and the execution is controlled by the first processor 121. The first processor 121 is used to execute the computer program instructions stored in the first memory 122, thereby performing various functional applications and data processing of the terminal device, such as implementing the perception method described in the embodiments of the present application.

[0047] The first processor 121 and the first transceiver 123 are connected via a bus. The first transceiver 123 can be any transceiver-like device for communicating with other devices or communication networks, such as Ethernet, radio access networks (RAN), and wireless local area networks (WLAN). The first transceiver 123 includes a transmitter Tx and a receiver Rx.

[0048] The network device 110 includes a second processor 111, a second memory 112, and a second transceiver 113. The second processor 111 is configured to execute computer program instructions stored in the second memory 112, thereby performing various functional applications and data processing of the network device 110, such as implementing the communication method described in the embodiments of the present application. The functions of the second processor 111 refer to the description of the first processor 121, the functions of the second memory 112 refer to the description of the first memory 122, and the functions of the second transceiver 113 refer to the description of the first transceiver 123, and are not further described here.

[0049] To facilitate understanding of the embodiments of this application, a brief description of the terms used in this application is first provided. Alternatively, reference may be made to the explanations in the 3rd Generation Partnership Project (3GPP) standard protocols for the interpretation of some of these terms. It should be understood that the technical terms used in this application are intended only as examples and not as limitations. For example, as technology evolves, technical terms may also change. In cases where the technical meanings remain the same, other technical terms should also apply to this application.

[0050] User equipment (UE): UE refers to the user's terminal equipment, such as mobile phones and IoT modules.

[0051] Release 19 (R19) is a technical specification developed by the 3GPP standards organization, defining new features that must be supported by UEs and network equipment. It is the second release of 3GPP 5G-Advanced (5G-A) (R18 being the first) and is expected to be frozen (standardization completed) by the end of 2025.

[0052] Next generation nodeB (gNB) in 5G mobile communication systems: gNB is the core network element of a 5G base station, responsible for sending and receiving wireless signals, resource scheduling, and interaction with terminal equipment (UE) and the core network (5GC).

[0053] Network Energy Saving (NES) cells: NES cells dynamically adjust their operating status (e.g., active / dormant), resource allocation, or coverage to reduce base station energy consumption while ensuring quality of service (QoS). Their core goal is to improve network energy efficiency.

[0054] Wake-up signal (WUS): Wakes up dormant devices through a dedicated low-power signal, avoiding continuous network monitoring and significantly extending battery life (such as sensors and wearable devices).

[0055] Uplink wake-up signal (UL-WUS): A signal sent by the UE to the base station (gNB / eNodeB) to request network resources or trigger downlink data transmission. This prevents the UE from continuously monitoring downlink control channels (such as the PDCCH), thereby saving power.

[0056] Uplink wake-up signal configuration (UL-WUS-Config): used to carry time offset information and index configuration information.

[0057] Random Access Response (RAR) message: The RAR message is sent by the gNB to the UE in response to a random access request initiated by the UE. The RAR message is sent at the MAC layer as a Media Access Control Protocol Data Unit (MAC PDU).

[0058] Medium access control protocol data unit (MAC PDU): MAC PDU is the core data encapsulation format of the MAC layer in wireless communication systems such as 5G / LTE. It is used to transmit control information and user data between the UE (terminal equipment) and the base station (gNB / eNodeB).

[0059] MAC sub-PDU: It is the basic unit of MAC layer data encapsulation in wireless communication systems such as 5G / LTE. It is used to carry different types of control information or user data in the MAC PDU. The MAC PDU includes multiple MAC sub-PDUs.

[0060] Total number of physical random access channel preambles (PRACHPreambles): In the 5G NR random access (RACH) process, total number of RA-Preambles is a key RRC layer parameter used to define the total number of available random access preambles (PRACH Preambles) in the cell, which directly affects the success rate of contention access and resource allocation efficiency.

[0061] System information (SI): It is the key configuration parameters broadcast by network equipment to terminal equipment (UE) and is used in processes such as cell access, reselection, and connection establishment.

[0062] System Information Block (SIB): A system information block (SIB) is a set of key system parameters broadcast by base stations to terminals in a mobile communication network. It is used to implement network access, resource configuration, and service control. SIBs include MIB, SIB1, SIB2, SIB3, SIB4, SIB5, SIB6, SIB7, SIB8, and SIB9.

[0063] System Information Block 1 (SIB1): SIB1 is a type of SIB. It contains key parameters for terminal devices accessing and residing in a cell, such as the cell's public land mobile network (PLMN) identifier, tracking area code (TAC), cell reselection priority, minimum receive level, scheduling information for other SIBs (such as SIB2-SIB9), supported operating frequency bands, and carrier bandwidth. Traditional SIB1 is transmitted periodically, resulting in high power consumption for network equipment.

[0064] On-demand SIB1 (OD-SIB1): When a terminal device needs to reconnect to the network (e.g., due to cell reselection or cell camping failure), the UL WUS triggers the network device to send a PDCCH. The downlink control information (DCI) in the PDCCH is used to schedule SIB1, allowing the terminal device to reconnect to the network based on SIB1. OD-SIB1 can reduce ineffective SIB1 broadcasts and reduce power consumption of network devices.

[0065] In the related art, in the on-demand request scenario, the R19 UE decodes the MAC sub-PDU of OD-SIB1 by obtaining the totalNumberOfRA-Preambles parameter. Figure 3 As shown, the communication method 300 includes the following steps S301-S304: S301. The second network device sends a UL-WUS configuration message to the terminal device.

[0066] The terminal device is an R19 UE. A second network device (or a base station of the network device) sends a UL-WUS configuration message to the terminal device to deliver configuration parameters to the terminal device. The totalNumberOfRA-Preambles parameter can be carried in the UL WUS configuration message, that is, the UL-WUS configuration message can include a pre-configured totalNumberOfRA-Preambles parameter. The UL WUS configuration message can also include time offset information and index configuration information. Accordingly, the R19 UE receives the UL-WUS configuration message from the second network device.

[0067] S302. The terminal device sends a UL-WUS to the first network device to request the first network device to send OD-SIB1.

[0068] First, the R19 UE sends a UL-WUS to the first network device (or the network energy saving (NES) cell of the network device) requesting the first network device to send OD-SIB1. When the R19 UE is in idle state (RRC_IDLE) or inactive state (RRC_INACTIVE) and re-accesses the network (e.g., due to cell reselection or cell camp failure), it sends a UL-WUS to the first network device, triggering the first network device to send a PDCCH. The DCI in the PDCCH is used to schedule SIB1, allowing the R19 UE to re-access the network based on SIB1. In response, the first network device receives the UL-WUS from the R19 UE.

[0069] S303: The first network device sends a RAR message to the terminal device.

[0070] The RAR message is sent in the form of a Media Access Control Protocol Data Unit (MAC PDU). The MAC PDU includes multiple MAC sub-PDUs. In an on-demand request scenario, the MAC PDU includes a MAC sub-PDU for OD-SIB1. After receiving a UL-WUS requesting OD-SIB1 from an R19 UE, the first network device sends a RAR message to the R19 UE. In response, the R19 UE receives the RAR message from the first network device.

[0071] S304. The first network device sends SIB1 to the terminal device.

[0072] The first network device broadcasts the totalNumberOfRA-Preambles parameter to the R19 UE via the SIB1. Correspondingly, the R19 UE receives the SIB1 from the first network device.

[0073] As can be seen from the communication method 300 described in steps S301-S304 above, the R19 UE has not yet received step S304 when it receives the RAR message. In other words, it has not yet received the SIB1 from the first network device. Furthermore, it cannot obtain the totalNumberOfRA-Preambles parameter broadcast by SIB1, resulting in the R19 UE being unable to successfully decode the RAR message. Therefore, the R19 UE can only obtain the totalNumberOfRA-Preambles parameter from the UL-WUS configuration message in which the totalNumberOfRA-Preambles parameter is pre-configured. That is, the second network device needs to configure the totalNumberOfRA-Preambles parameter in the UL-WUS configuration message in advance and send it to the R19 UE. Then, after receiving the UL-WUS configuration message from the second network device, the R19 UE sends a UL-WUS requesting OD-SIB1 to the first network device, and then receives the RAR message from the first network device. Since the totalNumberOfRA-Preambles parameter is configured in the UL-WUS configuration message in advance, the UL-WUS configuration message includes the totalNumberOfRA-Preambles parameter, so the MAC sub-PDU of OD-SIB1 can be successfully decoded. However, this will increase the overhead of the UL-WUS configuration.

[0074] In view of this, the present application provides a communication method, first, the terminal device sends a WUS to the network device for requesting the sending of OD-SIB1. Secondly, the terminal device receives a MAC PDU from the network device. Finally, the terminal device locates the position of the MAC sub-PDU of OD-SIB1 in the MAC PDU by decoding the identification information of a preset length that is before and adjacent to the MAC sub-PDU of OD-SIB1, thereby successfully decoding the MAC sub-PDU of OD-SIB1. With this communication method, the terminal device can successfully decode the MAC sub-PDU of OD-SIB1 based on the identification information of the preset length when the totalNumberOfRA-Preambles parameter is not included in the UL-WUS configuration message, thereby improving communication efficiency and saving overhead.

[0075] The following describes the solution provided by this application in detail in conjunction with the corresponding flowcharts. It will be understood that the schematic flowcharts provided in this application primarily use different devices (e.g., terminal devices, network devices) as examples of the execution entities of the interaction diagrams to illustrate the method, but this application does not limit the execution entities of the interaction diagrams. For example, the device (e.g., terminal device, network device) in the schematic flowcharts may also be a chip, chip system, or processor that supports the device to implement the method, or may be a logic module or software that can implement all or part of the functions of the device.

[0076] For a unified explanation here, in the interaction process of the embodiment of the present application, the message or signaling interaction involved can adopt the message or signaling in the standard, or it can be a newly introduced message or signaling, and the embodiment of the present application does not make specific limitations on this.

[0077] Attachment Figure 4 A flow chart of a communication method provided in an embodiment of the present application. It can be understood that the terminal device involved in the communication method can be an attached Figure 1 The terminal device in the communication method may also refer to a device in the terminal device (such as a processor, chip, or chip system). Figure 1 The network device in the network device may also refer to a device in the network device (such as a processor, chip, or chip system, etc.). Figure 4 As shown, the communication method 400 includes the following steps S401-S416: S401. The first terminal device sends a WUS to the network device.

[0078] The first terminal device is a terminal device that complies with the technical specifications developed by the 3GPP standardization organization after 2025, that is, the first terminal device is a terminal device that can be applied to the technical specifications of 5G and future 6G and above, for example, an R19 terminal device.

[0079] In a possible implementation, the network device may be a service cell of the network device (eg, an NES cell) or a base station. The embodiment of the present application does not limit the type of the network device.

[0080] In a possible implementation, the first terminal device may be an R19 UE or an R20 UE. The embodiment of the present application does not limit the protocol version of the first terminal device.

[0081] In an embodiment of the present application, WUS is used to request a network device to send OD-SIB1. In this case, WUS may be UL-WUS.

[0082] In a possible implementation, the first terminal device may send one WUS to the network device, or may send multiple WUS to the network device. The embodiment of the present application does not limit the number of WUS.

[0083] When the first terminal device is in the idle state (RRC_IDLE) or inactive state (RRC_INACTIVE), if it re-accesses the network (e.g., cell reselection, cell camp failure), it sends a UL WUS to the network device to trigger the network device to send a PDCCH. The DCI in the PDCCH is used to schedule SIB1 so that the terminal device can re-access the network according to SIB1. In response, the network device receives the UL WUS from the first terminal device.

[0084] S402: The second terminal device sends a target identification code to the network device.

[0085] The target identification code may be a preamble code. The second terminal device is a terminal device of a technical specification version formulated by the 3GPP standardization organization before 2025, that is, a version before R19. For example, an R18 terminal device.

[0086] In a possible implementation, the second terminal device may be an R18 UE, or a UE of any version among R99, R4-R18. The embodiment of the present application does not limit the protocol version of the second terminal device.

[0087] In an embodiment of the present application, the target identification code may be used to request a network device to send system information SI.

[0088] In a possible implementation, the second terminal device may send one target identification code to the network device, or may send multiple target identification codes to the network device. The embodiment of the present application does not limit the number of target identification codes.

[0089] When the second terminal device is in the idle state (RRC_IDLE) or the inactive state (RRC_INACTIVE), if it is connected to the network for the first time or re-connects to the network (for example, cell reselection or cell camping failure), it will send a target identification code to the network device during a random access channel (RACH occasion, RO) to trigger the initial connection or resynchronization between the second terminal device and the network device. In response, the network device receives the target identification code from the second terminal device.

[0090] S403: The network device encapsulates the RAR corresponding to each of the above requests into a MAC sub-PDU to form a RAR MAC PDU.

[0091] After receiving the WUS from the first terminal device and the preamble from the second terminal device, the network device encapsulates the RAR corresponding to each request in a MAC sub-PDU at the MAC layer, forming a RAR MAC PDU (referred to as MAC PDU). Since the RAR MAC PDU is the encapsulation format of the RAR message at the MAC layer, it forms a RAR message. The MAC PDU includes multiple MAC sub-PDUs, which are concatenated according to priority, and each MAC sub-PDU corresponds to a request.

[0092] In the embodiments of the present application, for example, as shown in the attached Figure 5 As shown, the structure of the RAR message includes the following: (1) A MAC PDU includes a first MAC sub-PDU and (n-1) second MAC sub-PDUs, wherein the nth MAC sub-PDU is the first MAC sub-PDU and the (n-1) second MAC sub-PDUs precede the first MAC sub-PDU.

[0093] The first MAC sub-PDU is the MAC sub-PDU of OD-SIB1, and the second MAC sub-PDU is another type of MAC sub-PDU, corresponding to other types of random access requests, such as SI requests and radio resource control (RRC) connection establishment requests. In other words, the second MAC sub-PDU is the MAC sub-PDU of SI or RRC. The MAC PDU includes n MAC sub-PDUs, where n is a positive integer and n>=2. The nth MAC sub-PDU is the first MAC sub-PDU and the (n-1)th MAC sub-PDU is the second MAC sub-PDU. In other words, the MAC sub-PDU of OD-SIB1 is at the end, and the MAC sub-PDU of SI or RRC is before the MAC sub-PDU of OD-SIB1.

[0094] In one possible implementation, among the n-1 second MAC sub-PDUs, the order of the MAC sub-PDU of SI and the MAC sub-PDU of RRC can be random or set according to the order of reception. The embodiment of the present application does not limit the order of the MAC sub-PDU of RRC and the MAC sub-PDU of SI.

[0095] In a possible implementation, the MAC PDU may include padding information or may not include padding information. The embodiment of the present application does not limit the specific structure of the MAC PDU. Figure 5 As shown in (a) of FIG, MAC PDU does not include padding information. Figure 5 As shown in (b), the MAC PDU includes padding information.

[0096] In a possible implementation, the MAC PDU may further include padding information, which is added after the first MAC sub-PDU. The padding information is added to align the size of the transport block (TB). Figure 5 As shown in (b), the MAC PDU includes padding information, and the padding information is behind the first MAC sub-PDU.

[0097] (2) The value of the third field of the first byte of the (n-1)th second MAC sub-PDU is the target value.

[0098] Among them, the target value of the third field is used to indicate that the second MAC sub-PDU is the n-1th second MAC sub-PDU, that is, the last second MAC sub-PDU. The value of the third field is the fifth value or the sixth value. The value of the third field is the fifth value used to characterize that the second MAC sub-PDU is the n-1th second MAC sub-PDU. The value of the third field is the sixth value used to characterize that the second MAC sub-PDU is not the n-1th second MAC sub-PDU. The fifth value corresponds to the sixth value one-to-one. The fifth value can be 0 or 1. For example, when the fifth value is 0, the sixth value is 1. When the fifth value is 1, the sixth value is 0.

[0099] Since the second MAC sub-PDU is an S1 or RRC MAC sub-PDU, the second MAC sub-PDU includes the following three types: A1 type, A2 type, and A3 type.

[0100] For example, as shown in the attached Figure 6As shown in (a), the second MAC sub-PDU of type A1 includes an E field, a T field, an R field, an R field, and a BI field. The E field is a flag indicating whether the second MAC sub-PDU is the last second MAC sub-PDU in the MAC PDU. The E field takes a value of 1 to indicate that the second MAC sub-PDU is not the n-1th second MAC sub-PDU, that is, it is not the last second MAC sub-PDU in the MAC PDU. The E field takes a value of 0 to indicate that the second MAC sub-PDU is the n-1th second MAC sub-PDU, that is, it is the last second MAC sub-PDU in the MAC PDU. The T field is a flag indicating whether the second MAC sub-PDU includes a random access preamble identifier (RAPID) field or a backoff indicator (BI) field. The T field takes a value of 1 to indicate that the second MAC sub-PDU includes a RAPID field. The T field takes a value of 0 to indicate that the second MAC sub-PDU includes a BI field. The R field is a reserved bit field. The BI field is used to indicate the overload status of the network device and is 4 bits long. In the second MAC sub-PDU of type A1, the second MAC sub-PDU includes the BI field, so the T field has a value of 0. The length of the second MAC sub-PDU of type A1 is 1 byte, and includes, in sequence, a 1-bit E field, a 1-bit T field, a 1-bit R field, a 1-bit R field, and a 4-bit BI field.

[0101] For example, as shown in the attached Figure 6 As shown in (b), the second MAC sub-PDU of type A2 includes an E field, a T field, and a RAPID field. Among them, the E field and the T field have been described in detail in the above-mentioned second MAC sub-PDU of type A1 and will not be repeated here. The RAPID field is used to indicate the index information of the random access preamble detected / received by the network device, that is, the preamble index, and has a length of 6 bits. In the second MAC sub-PDU of type A2, the second MAC sub-PDU includes a RAPID field, so the T field takes a value of 1. The length of the second MAC sub-PDU of type A2 is 1 byte, which includes a 1-bit E field, a 1-bit T field, and a 6-bit RAPID field in sequence.

[0102] For example, as shown in the attached Figure 6As shown in (c) of the figure, the first byte of the A3 type second MAC sub-PDU is identical to that of the A2 type second MAC sub-PDU, which has been described in detail in the A2 type second MAC sub-PDU above and will not be repeated here. In addition to the first byte, the A3 type second MAC sub-PDU also includes a 7-byte MAC RAR. The MAC RAR includes fields such as the transmission identity (TI) or R, timing advance command (TAC), uplink grant (UL Grant), and temporary cell radio network temporary identifier (TC-RNTI). The TI field is used to uniquely identify the data transmission status, for example, to distinguish between initial transmissions and retransmissions, ensure that the receiver correctly combines retransmitted data, or identify new data. The TAC field represents an adjustment amount, which adjusts the UE's transmission timing to ensure that all UE's uplink data arrives within the base station's expected receive window to avoid inter-symbol interference (ISI). A UL Grant is an uplink resource grant allocated by the base station (gNB / eNB) to the UE via downlink control signaling (such as DCI or RAR). It specifies the time, frequency band, and method by which the UE may transmit uplink data (such as Msg3, PUSCH data). The TC-RNTI field is a temporary UE identifier used in the random access procedure (RACH) in 5G (NR) and 4G (LTE), primarily during the contention resolution phase. It is assigned to the UE by the gNB (5G) or eNB (4G) via the random access response (RAR, Msg2) and is used for scheduling and contention resolution in subsequent Msg3 / Msg4 exchanges. Since the first byte of the second MAC sub-PDU of type A3 is the same as that of the second MAC sub-PDU of type A2, and includes the RAPID field, the T field is set to 1. The length of the second MAC sub-PDU of type A3 is 8 bytes. In addition to the 1-bit E field, the 1-bit T field, and the 6-bit RAPID field (1 byte), it also includes the 7-byte MAC RAR. The MAC RAR includes a 1-byte TI (or R) and TAC, a 1-byte TAC and UL Grant, a 3-byte UL Grant, and a 2-byte TC-RNTI.

[0103] In a possible implementation, each second MAC sub-PDU may be of type A1, type A2, or type A3. The embodiment of the present application does not limit the type of each second MAC sub-PDU.

[0104] Based on the type of the second MAC sub-PDU described above, in an embodiment of the present application, the third field is the E field, the fifth value is 0, the sixth value is 1, and the target value is the fifth value.

[0105] The value of the third field of the first byte of the (n-1)th second MAC sub-PDU is the target value, in order to indicate that the second MAC sub-PDU is the (n-1)th second MAC sub-PDU.

[0106] (3) The identification information of the preset length is between the first MAC sub-PDU and the (n-1)th second MAC sub-PDU.

[0107] Since the UL-WUS configuration message does not include the totalNumberOfRA-Preambles parameter, identification information is required to identify the position of the first MAC sub-PDU in the MAC PDU, so that the first terminal device can successfully decode the received RAR message.

[0108] As can be seen from the aforementioned description of the second MAC sub-PDUs of types A1, A2, and A3, the MAC RAR includes two fields with value ranges: the TAC and TC-RNTI fields. The TAC field has a value range of 0 to 3846 (0 to 1111 00000110 0000). The TC-RNTI field has a value range of 0001 to FFF2 (0000 0000 0000 0001 to 1111 11111111 0010). In the TAC and TC-RNTI fields of the MAC RAR, bytes 1 through 7 cannot be all 1s, and bytes 6 and 7 cannot be all 0s at the same time. This means that a MAC PDU can contain a maximum of six consecutive bytes of all 0s (bytes 1 through 6 of the MAC RAR) or five consecutive bytes of all 1s (bytes 2 through 6 of the MAC RAR).

[0109] To distinguish the two fields above, the TAC field and the TC-RNTI field, the identification information of the preset length is unique, i.e., uniquely determined, so that the position of the first MAC sub-PDU in the MAC PDU can be uniquely determined. In one possible implementation, the identification information of the preset length can be at least 6 consecutive bytes of all 1s or at least 7 consecutive bytes of all 0s.

[0110] For example, as shown in the attached Figure 5As shown, the identification information of the preset length is located between the first MAC sub-PDU (i.e., the nth MAC sub-PDU) and the n-1th second MAC sub-PDU (i.e., the n-1th MAC sub-PDU). The identification information of the preset length is located between the first MAC sub-PDU and the n-1th second MAC sub-PDU to locate the position of the first MAC sub-PDU in the MAC PDU. After decoding the identification information of the preset length, the first MAC sub-PDU can be decoded.

[0111] (4) The value of the first field of the first byte of the MAC PDU is the first value or the second value; the value of the first field is the first value used to indicate that the first byte of the MAC PDU includes the second field, and the value of the first field is the second value used to indicate that the first byte of the MAC PDU does not include the second field.

[0112] Among them, the first byte of the MAC PDU is the first byte of the first second MAC sub-PDU. The first field is used to indicate whether the first byte of the second MAC sub-PDU includes the second field. The value of the first field is the first value or the second value. The value of the first field is the first value used to characterize that the first byte of the second MAC sub-PDU includes the second field. The value of the first field is the second value used to characterize that the first byte of the second MAC sub-PDU does not include the second field. The first value corresponds to the second value one-to-one. The first value can be 0 or 1. For example, when the first value is 0, the second value is 1. When the first value is 1, the second value is 0.

[0113] From the above description of the A1, A2, and A3 types of second MAC sub-PDUs, it can be seen that: 1) Only the second MAC sub-PDU whose first byte includes the BI field includes the R field in its first byte. 2) In the first byte of the second MAC sub-PDU, since all other fields have specific functions and only the R field is reserved, it can be used to customize functions.

[0114] In addition, in the communication method 400 described above, when the network device fails to successfully receive the WUS from the first terminal device, or although the network device successfully receives the WUS from the first terminal device but does not send the first MAC sub-PDU to the first terminal device, the first terminal device still needs to decode the MAC PDU that does not include the first MAC sub-PDU. This will result in additional time and power consumption, and in this case, the identification information of the preset length is also unnecessary. Therefore, in order to avoid the above situation, save decoding time and reduce power consumption, the value of the R field of the first byte of the decoded MAC PDU can be used to indicate whether the MAC PDU includes the first MAC sub-PDU. In order to indicate whether the MAC PDU includes the first MAC sub-PDU by the R field of the first byte of the MAC PDU, it is necessary to first determine whether the first byte of the MAC PDU includes the R field, that is, the type of the first second MAC sub-PDU.

[0115] Since the T field is used to indicate whether the second MAC sub-PDU includes the RAPID field or the BI field. And only the second MAC sub-PDU whose first byte includes the BI field, the first byte includes the R field. Therefore, it is possible to determine whether the first byte of the MAC PDU includes the R field by the value of the T field of the first byte of the MAC PDU. To determine whether the first byte of the MAC PDU includes the second field, it is possible to determine whether the value of the first field of the first byte of the MAC PDU is the first value or the second value. The value of the first field of the first byte of the MAC PDU is determined in order to determine whether the first byte of the MAC PDU includes the BI field, thereby determining whether the first byte of the MAC PDU includes the R field, and finally determining whether the MAC PDU includes the first MAC sub-PDU. In the embodiment of the present application, the first field is the T field, the first value is 0, and the second value is 1.

[0116] When the value of the first field is the first value, the first byte of the second MAC sub-PDU includes the second field, and it can be further determined whether the value of the second field is the third value or the fourth value. When the value of the first field is the second value, it can be assumed that the MAC PDU includes the first MAC sub-PDU.

[0117] (5) When the first byte of the MAC PDU includes the second field, the value of the second field of the first byte of the MAC PDU is the third value or the fourth value; the value of the second field being the third value is used to indicate that the MAC PDU includes the first MAC sub-PDU. The value of the second field being the fourth value is used to indicate that the MAC PDU does not include the first MAC sub-PDU.

[0118] Similarly, the first byte of the MAC PDU is the first byte of the first second MAC sub-PDU. The second field is used to indicate whether the MAC PDU includes the first MAC sub-PDU. The value of the second field is the third value or the fourth value. The value of the second field is the third value used to characterize that the MAC PDU includes the first MAC sub-PDU. The value of the second field is the fourth value used to characterize that the MAC PDU does not include the first MAC sub-PDU. The third value corresponds to the fourth value one-to-one. The third value can be 0 or 1. For example, when the third value is 0, the fourth value is 1. When the third value is 1, the fourth value is 0.

[0119] Since the R field can be customized, the R field can be used to indicate whether the MAC PDU includes the first MAC sub-PDU. Therefore, in the embodiment of the present application, the second field is the R field, the third value is 0, and the fourth value is 1.

[0120] In one possible implementation, the first R field can be used to indicate whether the MAC PDU includes the first MAC sub-PDU, the second R field can be used to indicate whether the MAC PDU includes the first MAC sub-PDU, or two R fields can be used to indicate whether the MAC PDU includes the first MAC sub-PDU. The embodiment of the present application does not limit the type and number of R fields.

[0121] In the case where the first byte of the MAC PDU includes the second field, the value of the second field of the first byte of the MAC PDU is the third value or the fourth value in order to determine whether the MAC PDU includes the first MAC sub-PDU, so that the first terminal device can end decoding the MAC PDU when the MAC PDU does not include the first MAC sub-PDU, thereby saving decoding time and reducing power consumption.

[0122] (6) The value of the fourth field of the first byte of the MAC PDU is the target identification code index.

[0123] Among them, the fourth field is the RAPID field. Based on the type of the second MAC sub-PDU described above, it can be known that the RAPID field is used to indicate the index information of the random access preamble detected / received by the network device, that is, the preamble code index. Therefore, in this embodiment of the application, the fourth field is the RAPID field.

[0124] The value of the fourth field is the target identification code index, which is used to locate the position of the second MAC sub-PDU corresponding to the request sent by the second terminal device in the MAC PDU. That is, after the network device receives the target identification code from the second terminal device, the value of the fourth field of one of the second MAC sub-PDUs is the received target identification code index, so that the second terminal device can subsequently locate the position of the second MAC sub-PDU in the MAC PDU, thereby completing the decoding of the MAC PDU.

[0125] The structure of the RAR message described above includes a first MAC sub-PDU and n-1 second MAC sub-PDUs, and the n-th MAC sub-PDU is the first MAC sub-PDU and the n-1 second MAC sub-PDU is before the first MAC sub-PDU. The value of the third field of the first byte of the n-1 second MAC sub-PDU is the target value. The identification information of the preset length is located between the first MAC sub-PDU and the n-1 second MAC sub-PDU. The value of the first field of the first byte of the MAC PDU is the first value or the second value, which is used to indicate whether the first byte of the MAC PDU includes the second field. And in the case where the first byte of the MAC PDU includes the second field, the value of the second field of the first byte of the MAC PDU is the third value or the fourth value, which is used to indicate whether the MAC PDU includes the first MAC sub-PDU. The value of the fourth field is the target identification code index. Finally, the MAC PDU is encapsulated to form a RAR message. In this way, not only can the first terminal device successfully decode the MAC sub-PDU of OD-SIB1 based on the identification information of the preset length when the UL-WUS configuration message does not include the totalNumberOfRA-Preambles parameter, thereby improving communication efficiency and saving overhead. It can also enable the first terminal device to end decoding the MAC PDU based on the value of the R field when the network device does not successfully receive the WUS from the first terminal device, or when the network device successfully receives the WUS from the first terminal device but does not send the first MAC sub-PDU to the first terminal device, thereby saving decoding time and reducing power consumption. It can also enable the second terminal device to successfully decode the second MAC sub-PDU corresponding to the sent request, so that the terminal device can be compatible with decoding the MAC sub-PDU of OD-SIB1 and the MAC sub-PDU of SI (or RRC).

[0126] S404. The network device sends a RAR message to the first terminal device.

[0127] After encapsulating the MAC PDU, the network device sends the RAR message to the first terminal device in the form of the MAC PDU. Correspondingly, the first terminal device receives the RAR message from the network device.

[0128] S405. The network device sends a RAR message to the second terminal device.

[0129] Similarly, after encapsulating the MAC PDU, the network device sends the RAR message to the second terminal device in the form of the MAC PDU. Correspondingly, the second terminal device receives the RAR message from the network device.

[0130] S406. The first terminal device decodes the first byte of the MAC PDU.

[0131] According to the structure of the RAR message described above, the first byte of the MAC PDU is the first byte of the first second MAC sub-PDU.

[0132] Since the first terminal device sends a WUS to the network device for requesting the network device to send OD-SIB1, the first terminal device only needs to be able to decode the first MAC sub-PDU in the MAC PDU. After the first terminal device sends the WUS to the network device, the network device may successfully receive the WUS from the first terminal device, or it may not successfully receive the WUS from the first terminal device. The network device may also send the first MAC sub-PDU to the first terminal device, or it may not send the first MAC sub-PDU. When the network device successfully receives the WUS from the first terminal device and the network device sends the first MAC sub-PDU to the first terminal device, the first terminal device receives the first MAC sub-PDU in the RAR message from the network device. In this case, the first terminal device can successfully decode the first MAC sub-PDU. When the network device fails to successfully receive the WUS from the first terminal device, or although the network device successfully receives the WUS from the first terminal device but does not send the first MAC sub-PDU to the first terminal device, the RAR message received by the first terminal device from the network device does not include the first MAC sub-PDU. In this case, the first terminal device cannot successfully decode the first MAC sub-PDU. At this time, if the first terminal device still completely decodes the MAC PDU, it will generate additional time and power consumption. Therefore, the first terminal device must first determine whether the MAC PDU in the RAR message received from the network device includes the first MAC sub-PDU. According to the structure of the RAR message described above, it can be seen that the value of the second field of the first byte of the MAC PDU can be used to determine whether the MAC PDU includes the first MAC sub-PDU. Therefore, after receiving the RAR message from the network device, the first terminal device can first try to decode the first byte of the MAC PDU and determine whether the MAC PDU includes the first MAC sub-PDU based on the first byte of the MAC PDU.

[0133] S407. The first terminal device determines whether the value of the first field is the first value.

[0134] To determine whether a MAC PDU includes the first MAC sub-PDU by the value of the second field of the first byte of the MAC PDU, it is first necessary to determine whether the first byte of the MAC PDU includes the second field. Therefore, after the first terminal device decodes the first byte of the MAC PDU, it can determine whether the MAC PDU includes the first MAC sub-PDU by determining whether the value of the first field is the first value.

[0135] The first field is a T field, and the first value of the first field is 0, and the second value is 1. The first field's value of the first value is used to indicate that the first byte of the second MAC sub-PDU includes the second field. The first field's value of the second value is used to indicate that the first byte of the second MAC sub-PDU does not include the second field. The content of the first field has been described in detail in the structure of the above-mentioned RAR message and will not be repeated here. When the first field's value is the first value, it indicates that the first byte of the MAC PDU includes the second field, and step S408 is executed. When the first field's value is the second value, it indicates that the first byte of the MAC PDU does not include the second field, and step S409 is executed.

[0136] S408. The first terminal device determines whether the value of the second field is the third value.

[0137] When the value of the first field is the first value, it indicates that the first byte of the MAC PDU includes the second field. At this time, the value of the second field of the first byte of the MAC PDU is used to determine whether the MAC PDU includes the first MAC sub-PDU.

[0138] The second field is an R field. The third value of the second field is 0, and the fourth value is 1. The third value of the second field is used to indicate that the MAC PDU includes the first MAC sub-PDU. The fourth value of the second field is used to indicate that the MAC PDU does not include the first MAC sub-PDU. The content of the second field has been described in detail in the above-mentioned RAR message structure and will not be repeated here. When the value of the second field is the third value, it indicates that the MAC PDU includes the first MAC sub-PDU, and step S409 is executed. When the value of the second field is the fourth value, it indicates that the MAC PDU does not include the first MAC sub-PDU, and step S412 is executed.

[0139] S409. The first terminal device continues to decode the MAC PDU.

[0140] Since the value of the first field is the second value, it is assumed that the MAC PDU includes the first MAC sub-PDU. The value of the first field is the first value and the value of the third field is the third value, which means that the first byte of the MAC PDU includes an R field, and the value of the R field indicates that the MAC PDU includes the first MAC sub-PDU.

[0141] If the value of the first field is the second value, or if the value of the first field is the first value and the value of the third field is the third value, this indicates that the MAC PDU includes the first MAC sub-PDU. In other words, the MAC PDU includes the first MAC sub-PDU sent by the network device to the first terminal device, that is, the MAC sub-PDU of OD-SIB1. At this point, the MAC PDU can continue to be decoded and step S410 can be executed.

[0142] S410: The first terminal device determines whether identification information of a preset length is decoded.

[0143] According to the structure of the RAR message described above, the MAC PDU includes identification information of a preset length for locating the first MAC sub-PDU. This identification information of the preset length is adjacent to and precedes the first MAC sub-PDU. Therefore, after the first terminal device determines that the MAC PDU includes the first MAC sub-PDU, it can determine the location of the first MAC sub-PDU by determining whether the identification information of the preset length is decoded during the MAC PDU decoding process.

[0144] The content of the preset-length identification information has been described in detail in the structure of the aforementioned RAR message and will not be repeated here. If the first terminal device decodes the preset-length identification information, it indicates that the next MAC sub-PDU is the first MAC sub-PDU, and step S411 is executed. If the first terminal device has not yet decoded the preset-length identification information, it indicates that the next MAC sub-PDU is not the first MAC sub-PDU, and further decoding of the MAC PDU is required, returning to step S409 until the preset-length identification information is decoded.

[0145] S411. The first terminal device decodes the first MAC sub-PDU.

[0146] When the first terminal device decodes the identification information of the preset length, it indicates that the next MAC sub-PDU is the first MAC sub-PDU. At this time, the first terminal device decodes the first MAC sub-PDU, which is the first MAC sub-PDU sent by the network device to the first terminal device, that is, the MAC sub-PDU of OD-SIB1.

[0147] S412. The first terminal device finishes decoding the MAC PDU.

[0148] If the value of the first field is the first value and the value of the third field is the fourth value, this indicates that the MAC PDU does not include the first MAC sub-PDU. In other words, the MAC PDU does not include the first MAC sub-PDU sent by the network device to the first terminal device, namely, the MAC sub-PDU of OD-SIB1. In this case, continuing to decode the MAC PDU will incur additional time and power consumption. In this case, identification information of the preset length is also unnecessary. Therefore, the first terminal device can terminate decoding of the MAC PDU, thereby saving decoding time and reducing power consumption.

[0149] When the first terminal device decodes the first MAC sub-PDU, it indicates that the first terminal device has decoded the first MAC sub-PDU corresponding to the request sent to the network device, that is, the MAC sub-PDU of OD-SIB1. At this point, the first terminal device can end decoding the MAC PDU.

[0150] In the communication method 400 described in steps S401-S412 above, the first terminal device and the second terminal device first send a WUS to the network device, requesting the network device to send a MAC sub-PDU for OD-SIB1, and a preamble to request the network device to send a MAC sub-PDU for SI (or RRC). Based on the above requests, the network device encapsulates the RAR corresponding to each request in a MAC sub-PDU to form a RAR MAC PDU, and then sends the RAR message to the first terminal device and the second terminal device, respectively. After receiving the RAR message, the first terminal device first decodes the first byte of the MAC PDU and determines the value of the first field of the first byte of the MAC PDU to determine whether the first byte of the MAC PDU includes the second field. If the first byte of the first byte of the MAC PDU is the second value, that is, the first byte of the MAC PDU does not include the second field, it is assumed that the MAC PDU includes the first MAC sub-PDU, and the first terminal device continues to decode the MAC PDU. When the first byte of the first byte of the MAC PDU is the first value, that is, the first byte of the MAC PDU includes the second field, the first terminal device continues to determine the value of the second field of the first byte of the MAC PDU, thereby determining whether the MAC PDU includes the first MAC sub-PDU. When the second byte of the first byte of the MAC PDU is the third value, that is, the MAC PDU includes the first MAC sub-PDU, the first terminal device continues to decode the MAC PDU. When the second byte of the first byte of the MAC PDU is the fourth value, that is, the MAC PDU does not include the first MAC sub-PDU, the first terminal device ends decoding the MAC PDU. While the first terminal device continues to decode the MAC PDU, it determines whether identification information of a preset length is decoded. When the first terminal device decodes the identification information of the preset length, the first terminal device ends decoding the MAC PDU after decoding the first MAC sub-PDU. When the first terminal device does not decode the identification information of the preset length, the first terminal device continues decoding the MAC PDU until the first MAC sub-PDU is decoded. This communication method 400 not only enables the first terminal device to successfully decode the OD-SIB1 MAC sub-PDU based on identification information of a preset length when the UL-WUS configuration message does not include the totalNumberOfRA-Preambles parameter, thereby improving communication efficiency and reducing overhead, but also enables the first terminal device to terminate decoding of the MAC PDU based on the value of the R field when the network device fails to successfully receive the WUS from the first terminal device, or when the network device successfully receives the WUS from the first terminal device but does not send the first MAC sub-PDU to the first terminal device, thereby saving decoding time and reducing power consumption.

[0151] S413. The second terminal device decodes the second MAC PDU.

[0152] Since the second terminal device sends to the network device a target identification code (for example, a preamble) for requesting the network device to send SI or RRC, the second terminal device cannot identify the identification information of the preset length following the second MAC PDU in the MAC PDU and the first MAC PDU, that is, the identification information of the preset length following the second MAC PDU and the first MAC PDU will be shielded. Therefore, the second terminal device only needs to decode the preceding second MAC PDU. After receiving the RAR message from the network device, the second terminal device can start decoding the MAC PDU, that is, start decoding the second MAC PDU. In an embodiment of the present application, the second terminal device decodes the MAC PDU in the order of the second MAC sub-PDUs.

[0153] S414. The second terminal device determines whether the value of the fourth field of the first byte of the second MAC sub-PDU is the same as the sent target identification code index.

[0154] Since the second terminal device sends to the network device a target identification code (for example, a preamble) for requesting the network device to send SI or RRC, the value of the fourth field (i.e., the RAPID field) of the first byte of the second MAC sub-PDU corresponds to the target identification code index sent by the second terminal device to the network device. Therefore, as long as the second terminal device can decode the second MAC sub-PDU in the MAC PDU with the same value of the fourth field as the target identification code index sent, it will be sufficient. Therefore, in the process of decoding the MAC PDU, the second terminal device can determine whether the second MAC sub-PDU is the second MAC sub-PDU corresponding to the request sent by the second terminal device by the value of the fourth field of the first byte of the second MAC sub-PDU, thereby ending the decoding of the MAC PDU.

[0155] The content of the fourth field has been described in detail in the above-mentioned RAR message structure and will not be repeated here. In the case where the value of the fourth field of the first byte of the second MAC sub-PDU is the same as the target identification code index sent, it indicates that the second MAC sub-PDU is the second MAC sub-PDU corresponding to the request sent by the second terminal device, and step S416 is executed. In the case where the value of the fourth field of the first byte of the second MAC sub-PDU is different from the target identification code index sent, it indicates that the second MAC sub-PDU is not the second MAC sub-PDU corresponding to the request sent by the second terminal device, and step S415 is executed.

[0156] S415. The second terminal device determines whether the value of the third field of the first byte of the second MAC sub-PDU is the target value.

[0157] The content of the third field has been described in detail in the above RAR message structure and will not be repeated here. In the case where the value of the fourth field of the first byte of the second MAC sub-PDU is different from the target identification code index sent, it is necessary to further determine whether the second MAC sub-PDU is the n-1th second MAC sub-PDU, that is, whether it is the last second MAC sub-PDU. The second terminal device determines whether the value of the third field of the first byte of the second MAC sub-PDU is the target value in order to determine whether the second MAC sub-PDU is the n-1th second MAC sub-PDU.

[0158] If the value of the third field of the first byte of the second MAC sub-PDU is the target value, it indicates that the second MAC sub-PDU is the n-1th second MAC sub-PDU, and step S416 is executed. If the value of the third field of the first byte of the second MAC sub-PDU is not the target value, it indicates that the second MAC sub-PDU is not the n-1th second MAC sub-PDU and there is at least another second MAC sub-PDU behind it, and the process returns to step S413 to continue decoding the second MAC PDU.

[0159] S416. The second terminal device finishes decoding the MAC PDU.

[0160] If the value of the fourth field of the first byte of the second MAC sub-PDU is the same as the sent target identification code index, the second terminal device has decoded the second MAC sub-PDU corresponding to the sent request. At this time, the second terminal device does not need to decode the next second MAC sub-PDU, and thus, the decoding of the MAC PDU can be completed. Figure 7 As shown, the second terminal device sends a preamble with a preamble index of 32 to the network setting. When the second terminal device decodes the second MAC sub-PDU, the first byte of the first second MAC sub-PDU is a MAC sub-PDU including the BI field, but does not include the RAPID field, and the second terminal device continues to decode the next second MAC sub-PDU. The value of the RAPID field of the first byte of the second second MAC sub-PDU is 50, which is different from the preamble index 32, and the second terminal device continues to decode the next second MAC sub-PDU. The value of the RAPID field of the first byte of the third second MAC sub-PDU is 32, which is the same as the preamble index 32, and the second terminal device continues to end decoding the MAC PDU.

[0161] Similarly, the network device may successfully receive the target identification code from the second terminal device and send a RAR message. In this case, the second terminal device can decode the second MAC sub-PDU corresponding to the request sent by the second terminal device by determining whether the value of the fourth field of the first byte of the second MAC sub-PDU is the same as the target identification code index sent, that is, the steps S414-S415 described above, and end decoding the MAC PDU after decoding the second MAC sub-PDU. In addition, the network device may not successfully receive the target identification code from the second terminal device, or although the network device successfully receives the target identification code from the second terminal device, it does not send the second MAC sub-PDU corresponding to the request to the second terminal device. In this case, the second terminal device will continue decoding to the n-1th second MAC sub-PDU, and according to the content described in the above step S413, it can be seen that the second terminal device cannot recognize the preset length of identification information and the first MAC PDU after the second MAC PDU in the MAC PDU, that is, it will block the preset length of identification information and the first MAC PDU (as shown in the attached figure) after the second MAC PDU. Figure 7 -Attached Figure 8 (see the dashed box in the figure). In this case, if decoding cannot be completed, the second terminal device will report an error, which may cause a malfunction. Therefore, to avoid the above situation, the second terminal device can terminate the decoding of the MAC PDU by determining whether the value of the third field is the target value.

[0162] When the value of the third field is the target value, the second MAC sub-PDU is the n-1th second MAC sub-PDU. At this time, regardless of whether the value of the fourth field of the first byte of the second MAC sub-PDU is the same as the sent target identification code index, that is, whether the second MAC sub-PDU corresponding to the request sent by the second terminal device is decoded, the second terminal device does not need to decode the MAC PDU again, and therefore, the decoding of the MAC PDU can be ended. For example, as shown in the attached Figure 8As shown, when the second terminal device is decoding the second MAC sub-PDU, the E field value of the first byte of the first second MAC sub-PDU is 1, and the second terminal device continues to decode the next second MAC sub-PDU. The E field value of the first byte of the second second MAC sub-PDU is 1, and the second terminal device continues to decode the next second MAC sub-PDU. The E field value of the first byte of the third second MAC sub-PDU is 1, and the second terminal device continues to decode the next second MAC sub-PDU. Similarly, if the E field value of the first byte of the n-2 second MAC sub-PDU is 1, the second terminal device continues to decode the next second MAC sub-PDU. Until the n-1 second MAC sub-PDU is decoded, the E field value of the first byte of the n-1 second MAC sub-PDU is 0, which is the last MAC sub-PDU, and the second terminal device continues to end decoding the MAC PDU.

[0163] In the communication method 400 described in the above steps S401-S405 and S413-S416, the first terminal device and the second terminal device first send a WUS for requesting the network device to send a MAC sub-PDU of OD-SIB1 and a preamble for requesting the network device to send an SI (or RRC) MAC sub-PDU to the network device, respectively. Based on the above request, the network device encapsulates the RAR corresponding to each request in the MAC sub-PDU to form a RAR MAC PDU, and then sends the RAR message to the first terminal device and the second terminal device, respectively. After receiving the above RAR message, the second terminal device starts decoding the MAC PDU (i.e., the second MAC sub-PDU), and first determines whether the value of the fourth field of the first byte of the second MAC sub-PDU is the same as the sent target identification code index. If the value of the fourth field of the first byte of the second MAC sub-PDU is the same as the sent target identification code index, the second terminal device ends decoding the MAC PDU. In the case that the value of the fourth field of the first byte of the second MAC sub-PDU is different from the target identification code index sent, continue to determine whether the value of the third field of the first byte of the second MAC sub-PDU is the target value, thereby determining whether the second MAC sub-PDU is the last second MAC sub-PDU. In the case that the value of the third field of the first byte of the second MAC sub-PDU is the target value, the second terminal device ends decoding the MAC PDU. In the case that the value of the third field of the first byte of the second MAC sub-PDU is not the target value, the second terminal device continues to decode the next second MAC PDU until the value of the third field of the first byte of the second MAC sub-PDU is the target value. The communication method 400 can also enable the second terminal device to successfully decode the second MAC sub-PDU corresponding to the sent request, so that the terminal device can be compatible with decoding the MAC sub-PDU of OD-SIB1 and the MAC sub-PDU of SI (or RRC).

[0164] In the communication method 400 described in steps S401-S416 above, the first terminal device and the second terminal device first send a WUS and a preamble of an SI (or RRC) MAC sub-PDU to the network device, respectively, requesting the network device to send an OD-SIB1 MAC sub-PDU. Based on the above request, the network device encapsulates the RAR corresponding to each request in a MAC sub-PDU to form a RAR MACPDU, and then sends the RAR message to the first terminal device and the second terminal device, respectively. The first terminal device and the second terminal device decode the MAC PDU, respectively. Because the MAC PDU includes the value of the first field, the value of the second field, the value of the third field, and the value of the fourth field, it also includes identification information of a preset length between the first MAC sub-PDU and the (n-1)th second MAC sub-PDU. Therefore, the communication method 400 can ensure that when the totalNumberOfRA-Preambles parameter is not included in the UL-WUS configuration message, when the network device successfully receives the WUS from the first terminal device, the first terminal device successfully decodes the MAC sub-PDU of OD-SIB1 based on the value of the first field, the value of the second field and the identification information of the preset length, thereby improving communication efficiency and saving overhead. It can also ensure that when the totalNumberOfRA-Preambles parameter is not included in the UL-WUS configuration message, the first terminal device, based on the value of the second field, ends decoding the MAC PDU when the network device fails to successfully receive the WUS from the first terminal device, or when the network device successfully receives the WUS from the first terminal device but fails to send the first MAC sub-PDU to the first terminal device, thereby saving decoding time and reducing power consumption. It can also enable the second terminal device to successfully decode the second MAC sub-PDU corresponding to the request sent based on the value of the fourth field when the network device successfully receives the WUS from the first terminal device and the network device sends the second MAC sub-PDU corresponding to the request to the second terminal device, so that the terminal device can be compatible with decoding the MAC sub-PDU of OD-SIB1 and the MAC sub-PDU of SI (or RRC). When the network device does not successfully receive the WUS from the first terminal device, or although the network device successfully receives the target identification code from the second terminal device but does not send the second MAC sub-PDU corresponding to the request to the second terminal device, the second terminal device ends decoding the MAC PDU based on the value of the third field, thereby avoiding malfunction of the second terminal device.

[0165] In one possible implementation, the first terminal device may also send a preamble code to the network device for requesting to send SI or RRC. In this case, another network device is required to send a totalNumberOfRA-Preambles parameter to the first terminal device in advance to indicate the purpose of the preamble code. The first terminal device decodes the MAC sub-PDU corresponding to the sent request based on the totalNumberOfRA-Preambles parameter and the preamble code. At this time, the RAR message in the embodiment of the present application can also successfully decode the MAC sub-PDU. Its communication method is the same as the principle of the communication method 400 described in steps S413-S416, and will not be repeated here.

[0166] The communication method and communication apparatus provided in the embodiments of the present application are as follows: the first terminal device and the second terminal device first send to the network device a WUS for requesting the network device to send a MAC sub-PDU of OD-SIB1 and a preamble of a MAC sub-PDU of SI (or RRC), and based on the above request, the network device encapsulates the RAR corresponding to each request in a MAC sub-PDU to form a RAR MAC PDU, and then sends the RAR message to the first terminal device and the second terminal device respectively. The first terminal device and the second terminal device decode the MAC PDU respectively. Since the MAC PDU includes the value of the first field, the value of the second field, the value of the third field, and the value of the fourth field, it also includes identification information of a preset length between the first MAC sub-PDU and the n-1th second MAC sub-PDU. Therefore, the communication method 400 can ensure that when the totalNumberOfRA-Preambles parameter is not included in the UL-WUS configuration message, when the network device successfully receives the WUS from the first terminal device, the first terminal device successfully decodes the MAC sub-PDU of OD-SIB1 based on the value of the first field, the value of the second field and the identification information of the preset length, thereby improving communication efficiency and saving overhead. It can also ensure that when the totalNumberOfRA-Preambles parameter is not included in the UL-WUS configuration message, the first terminal device, based on the value of the second field, ends decoding the MAC PDU when the network device fails to successfully receive the WUS from the first terminal device, or when the network device successfully receives the WUS from the first terminal device but fails to send the first MAC sub-PDU to the first terminal device, thereby saving decoding time and reducing power consumption. It can also enable the second terminal device to successfully decode the second MAC sub-PDU corresponding to the request sent based on the value of the fourth field when the network device successfully receives the WUS from the first terminal device and the network device sends the second MAC sub-PDU corresponding to the request to the second terminal device, so that the terminal device can be compatible with decoding the MAC sub-PDU of OD-SIB1 and the MAC sub-PDU of SI (or RRC). When the network device does not successfully receive the WUS from the first terminal device, or although the network device successfully receives the target identification code from the second terminal device but does not send the second MAC sub-PDU corresponding to the request to the second terminal device, the second terminal device ends decoding the MAC PDU based on the value of the third field, thereby avoiding malfunction of the second terminal device.

[0167] It is understandable that in order to implement the above functions, the electronic device includes hardware and / or software modules corresponding to the execution of each function. In combination with the algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in combination with the embodiments, but such implementation should not be considered to be beyond the scope of this application.

[0168] In this embodiment, the electronic device can be divided into functional modules according to the above-mentioned method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into a single processing module. The above-mentioned integrated modules can be implemented in the form of hardware. It should be noted that the module division in this embodiment is illustrative and is only a logical functional division. In actual implementation, other division methods may be used.

[0169] An embodiment of the present application further provides a computer-readable storage medium, in which computer program code is stored. When the processor executes the computer program code, the electronic device executes the relevant method steps in the above method embodiment.

[0170] An embodiment of the present application further provides a computer program product, which, when executed on a computer, enables the computer to execute the relevant method steps in the above method embodiment.

[0171] Among them, the electronic device, computer storage medium or computer program product provided in this application is used to execute the corresponding method provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method provided above, and will not be repeated here.

[0172] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0173] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the above modules or units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0174] The units described above as separate components may or may not be physically separate, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0175] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The functions of the aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0176] If the above-mentioned integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application, or the part that makes the contribution, or all or part of the technical solution can be embodied in the form of a software product. The software product is stored in a storage medium and includes several instructions for enabling a device (which can be a single-chip microcomputer, chip, etc.) or a processor to execute all or part of the steps of the above-mentioned method of each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, etc., various media that can store program code.

[0177] The above content is only a specific embodiment of this application, but the scope of protection of this application is not limited to this. Any changes or replacements within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A communication method, characterized in that: Applied to a terminal device, the method includes: Sending a wake-up signal WUS to a network device; the WUS is used to request the network device to send an on-demand first system information block OD-SIB1; Receive a media access control protocol data unit MAC PDU from the network device; the MAC PDU includes a first MAC sub-PDU and identification information of a preset length; the first MAC sub-PDU is the MAC sub-PDU of the OD-SIB1, and the identification information of the preset length is used to indicate that the MAC sub-PDU that is adjacent to and after the identification information of the preset length is the first MAC sub-PDU.

2. The communication method according to claim 1, wherein: The MAC PDU further includes at least one second MAC sub-PDU, where the second MAC sub-PDU is the MAC sub-PDU preceding the identification information of the preset length; the first byte of the second MAC sub-PDU includes a first field, the value of the first field is a first value or a second value, the value of the first field is the first value used to indicate that the first byte of the second MAC sub-PDU also includes a second field, the value of the first field is the second value used to indicate that the first byte of the second MAC sub-PDU does not include the second field; the value of the second field is a third value or a fourth value, the value of the second field is the third value used to indicate that the MAC PDU includes the first MAC sub-PDU, and the value of the second field is the fourth value used to indicate that the MAC PDU does not include the first MAC sub-PDU; The method further comprises: Decoding the first byte of the MAC PDU; When the value of the first field is the first value and the value of the second field is the third value, continue decoding the MAC PDU.

3. The communication method according to claim 2, wherein: The method further comprises: When the value of the first field is the first value and the value of the second field is the fourth value, decoding of the MAC PDU ends.

4. The communication method according to claim 2 or 3, characterized in that: The method further comprises: When the value of the first field is the second value, continue decoding the MAC PDU.

5. The communication method according to claim 4, wherein: The value of the third field of the first byte of the second MAC sub-PDU adjacent to the identification information of the preset length is the target value.

6. The communication method according to any one of claims 1 to 3 and 5, characterized in that: The identification information of the preset length is at least 6 consecutive bytes of all 1s or at least 7 consecutive bytes of all 0s.

7. The communication method according to any one of claims 2 to 3 or 5, characterized in that: The second field is a reserved R field.

8. A communication method, characterized in that: Applied to a network device, the method includes: Receiving a wake-up signal WUS from a terminal device; the WUS is used to request sending an on-demand first system information block OD-SIB1; A media access control protocol data unit MAC PDU is sent to the terminal device to trigger the terminal device to decode the MAC PDU; the MAC PDU includes a first MAC sub-PDU and identification information of a preset length; the first MAC sub-PDU is the MAC sub-PDU of the OD-SIB1, and the identification information of the preset length is used to indicate that the MAC sub-PDU that is adjacent to and follows the identification information of the preset length is the first MAC sub-PDU.

9. The communication method according to claim 8, wherein: The MAC PDU also includes at least one second MAC sub-PDU, and the second MAC sub-PDU is the MAC sub-PDU before the identification information of the preset length; the first byte of the second MAC sub-PDU includes a first field; the first field is a first value or a second value; the value of the first field is the first value used to characterize that the first byte of the second MAC sub-PDU also includes a second field, and the value of the first field is the second value used to characterize that the first byte of the second MAC sub-PDU does not include the second field; the value of the second field is a third value or a fourth value, the value of the second field is the third value used to characterize that the MAC PDU includes the first MAC sub-PDU, and the value of the second field is the fourth value used to characterize that the MAC PDU does not include the first MAC sub-PDU.

10. The communication method according to claim 9, wherein: The value of the third field of the first byte of the second MAC sub-PDU adjacent to the identification information of the preset length is the target value.

11. The communication method according to any one of claims 8 to 10, characterized in that: The identification information of the preset length is at least 6 consecutive bytes of all 1s or at least 7 consecutive bytes of all 0s.

12. The communication method according to claim 9 or 10, characterized in that: The second field is a reserved R field.

13. A communication device, characterized in that: The communication device comprises a processor and a memory, wherein the memory stores instructions. When the processor executes the instructions, the communication device executes the communication method according to any one of claims 1 to 7, or executes the communication method according to any one of claims 8 to 12.

14. A computer-readable storage medium having a computer program or instruction stored thereon, characterized in that: When the computer program or instruction is executed, the computer executes the communication method according to any one of claims 1 to 7, or the communication method according to any one of claims 8 to 12.

Images