Communication method and apparatus, computer readable storage medium

CN120659165BActive Publication Date: 2026-10-09SPREADTRUM COMMUNICATION (SHANGHAI) CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202410264572.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-03-07
Publication Date
2026-10-09
Estimated Expiration
2044-03-07

AI Technical Summary

Technical Problem

[0004]但是,在一种可能的EDT场景中,有多个终端设备同时在同一块资源上发送随机接入过程的Msg3,基站分别向这些终端设备反馈RRCEarlyDataComplete消息,会造成资源浪费

Benefits of technology

[0028] In this application's technical solution, a terminal device sends a first message requesting data transmission; and receives a second message including multiple sub-protocol data units, comprising M sub-protocol data units. Each of the M sub-protocol data units has a header including first information indicating whether a Media Access Control Service Data Unit (MAC SDU) is applicable to a first terminal device matching at least one contention resolution identifier. This technical solution, by including first information in the headers of the M sub-protocol data units in the second message to indicate whether a MAC SDU is applicable to a terminal device matching at least one contention resolution identifier, enables downlink message multiplexing by sending the same MAC SDU to at least one terminal device, saving downlink transmission resources and improving communication efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120659165B_ABST
    Figure CN120659165B_ABST
Patent Text Reader

Abstract

The application provides a communication method and device and a computer readable storage medium. The communication method comprises the following steps: a first message is sent, the first message being used for requesting data transmission; a second message is received, the second message being used for responding to the first message, the second message comprising a plurality of sub-protocol data units, the plurality of sub-protocol data units comprising M sub-protocol data units, and the sub-header of each sub-protocol data unit in the M sub-protocol data units comprising first information, the first information indicating whether a medium access control service data unit (MAC SDU) is applicable to at least one first terminal device, the first terminal device being a terminal device matched with a contention resolution identifier. The application provides a scheme for saving transmission resources.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and apparatus, and a computer-readable storage medium. Background Technology

[0002] The 3rd Generation Partnership Project (3GPP) protocol release 15 (R15) introduced Early Data Transmission (EDT), which allows data to be transmitted during random access. This feature aims to reduce latency and power consumption of end devices.

[0003] In the control plane EDT scheme, the terminal device sends data to the base station in Msg3. In the Msg4 returned by the base station, in addition to carrying the contention resolution identifier, it may also carry the RRC Early Data Complete message, indicating that the terminal device has completed the transmission and returns to the idle state.

[0004] However, in a possible EDT scenario, multiple terminal devices simultaneously send Msg3 for the random access procedure on the same resource. The base station sends RRCEarlyDataComplete messages back to these terminal devices, which will result in resource waste. Summary of the Invention

[0005] This application provides a communication method and apparatus, and provides a solution for saving transmission resources.

[0006] To achieve the above objectives, this application provides the following technical solution:

[0007] In a first aspect, a communication method is provided, comprising: sending a first message, the first message being used to request data transmission; receiving a second message, the second message being used to respond to the first message, the second message including a plurality of sub-protocol data units, the plurality of sub-protocol data units including M sub-protocol data units, each of the M sub-protocol data units having a header including first information, the first information indicating whether a Media Access Control Service Data Unit (MAC SDU) is applicable to at least one first terminal device, the first terminal device being a terminal device matching a contention resolution identifier, and M being a positive integer greater than or equal to 1; the plurality of sub-protocol data units including the MAC SDU; the plurality of sub-protocol data units including the contention resolution identifier.

[0008] Optionally, the MAC SDU is carried in the last or first N sub-protocol data units of the plurality of sub-protocol data units, where N is a positive integer greater than or equal to 1.

[0009] Optionally, the first information in the subheader of each sub-protocol data unit indicates whether the MAC SDU is applicable to a terminal device that matches the contention resolution identifier carried by that sub-protocol data unit.

[0010] Optionally, the first information occupies one bit, wherein the bit is a first value indicating that the MAC SDU is applicable to a first terminal device that matches the contention resolution identifier carried by the sub-protocol data unit, and the first information is a second value indicating that the MAC SDU is not applicable to a first terminal device that matches the contention resolution identifier carried by the sub-protocol data unit.

[0011] Optionally, the first message carries a Common Control Channel (CCCH) SDU, and the communication method further includes: receiving the MAC SDU in response to the CCCH SDU being consistent with the contention resolution identifier carried by the M sub-protocol data units.

[0012] Optionally, the M sub-protocol data units include a first sub-protocol data unit and a second sub-protocol data unit, wherein the first information indicated by the first sub-protocol data unit is applicable to a first terminal device that matches the contention resolution identifier carried by the second sub-protocol data unit.

[0013] Optionally, the second sub-protocol data unit is located after the first sub-protocol data unit, the first information occupies one bit, the bit being a first value indicates that the sub-protocol data unit containing the first information is the first sub-protocol data unit and the MAC SDU is applicable to a first terminal device that matches the contention resolution identifier carried by the second sub-protocol data unit; the bit being a second value indicates that the sub-protocol data unit containing the first information is the second sub-protocol data unit; or, the first information carried in the second sub-protocol data unit indicates that the current sub-protocol data unit is the second sub-protocol data unit.

[0014] Optionally, the first message carries a CCCH SDU, and the communication method further includes: receiving the MAC SDU in response to the CCCH SDU being consistent with the contention resolution identifier carried by the second sub-protocol data unit.

[0015] Secondly, this application also discloses a communication method, the communication method comprising: receiving a first message, the first message being used to request data transmission; sending a second message, the second message being used to respond to the first message, the second message including a plurality of sub-protocol data units, the plurality of sub-protocol data units including M sub-protocol data units, wherein the subheader of each of the M sub-protocol data units includes first information, the first information indicating whether a Media Access Control Service Data Unit (MAC SDU) is applicable to at least one first terminal device, the first terminal device being a terminal device matching a contention resolution identifier, and M being a positive integer greater than or equal to 1; the plurality of sub-protocol data units including the MAC SDU; the plurality of sub-protocol data units including the contention resolution identifier.

[0016] Optionally, the first information in the subheader of each sub-protocol data unit indicates whether the MAC SDU is applicable to a first terminal device that matches the contention resolution identifier carried by that sub-protocol data unit.

[0017] Optionally, the M sub-protocol data units include a first sub-protocol data unit and a second sub-protocol data unit, wherein the first information indicated by the first sub-protocol data unit is applicable to a first terminal device that matches the contention resolution identifier carried by the second sub-protocol data unit.

[0018] Thirdly, this application also discloses a communication device, comprising: a communication module for sending a first message, the first message being used to request data transmission; the communication module further for receiving a second message, the second message being used to respond to the first message, the second message including a plurality of sub-protocol data units, the plurality of sub-protocol data units including M sub-protocol data units, each of the M sub-protocol data units having a header including first information, the first information indicating whether a Media Access Control Service Data Unit (MAC SDU) is applicable to at least one first terminal device, the first terminal device being a terminal device matching a contention resolution identifier, M being a positive integer greater than or equal to 1; the plurality of sub-protocol data units including the MAC SDU; the plurality of sub-protocol data units including the contention resolution identifier.

[0019] Fourthly, this application also discloses a communication device, comprising: a communication module for receiving a first message, the first message being for requesting data transmission; the communication module further for sending a second message, the second message being for responding to the first message, the second message including a plurality of sub-protocol data units, the plurality of sub-protocol data units including M sub-protocol data units, each of the M sub-protocol data units having a header including first information, the first information indicating whether a Media Access Control Service Data Unit (MAC SDU) is applicable to at least one first terminal device, the first terminal device being a terminal device matching a contention resolution identifier, M being a positive integer greater than or equal to 1; the plurality of sub-protocol data units including the MAC SDU; the plurality of sub-protocol data units including the contention resolution identifier.

[0020] Fifthly, a computer-readable storage medium is provided having a computer program stored thereon, the computer program being executed by a processor to perform any one of the methods provided in the first or second aspect.

[0021] In a sixth aspect, a communication device is provided, including a memory and a processor, wherein the memory stores a computer program executable on the processor, and the processor executes the computer program to perform any of the methods provided in the first aspect.

[0022] In a seventh aspect, a communication device is provided, including a memory and a processor, wherein the memory stores a computer program executable on the processor, and the processor executes the computer program to perform any of the methods provided in the second aspect.

[0023] Eighthly, a computer program product is provided, on which a computer program is stored, the computer program being executed by a processor to perform any one of the methods provided in the first or second aspect.

[0024] Ninthly, a communication system is provided, including the aforementioned terminal equipment and the aforementioned network equipment.

[0025] In a tenth aspect, embodiments of this application also provide a chip (or data transmission device) on which a computer program is stored, and when the computer program is executed by the chip, the steps of the above method are implemented.

[0026] Eleventhly, embodiments of this application also provide a system chip for use in a terminal. The chip system includes at least one processor and an interface circuit. The interface circuit and the at least one processor are interconnected via a line. The at least one processor is used to execute instructions to perform any one of the methods provided in the first or second aspect.

[0027] Compared with the prior art, the technical solution of this application has the following beneficial effects:

[0028] In this application's technical solution, a terminal device sends a first message requesting data transmission; and receives a second message including multiple sub-protocol data units, comprising M sub-protocol data units. Each of the M sub-protocol data units has a header including first information indicating whether a Media Access Control Service Data Unit (MAC SDU) is applicable to a first terminal device matching at least one contention resolution identifier. This technical solution, by including first information in the headers of the M sub-protocol data units in the second message to indicate whether a MAC SDU is applicable to a terminal device matching at least one contention resolution identifier, enables downlink message multiplexing by sending the same MAC SDU to at least one terminal device, saving downlink transmission resources and improving communication efficiency.

[0029] Furthermore, the first information in the subheader of each sub-protocol data unit indicates whether the MAC SDU is applicable to a first terminal device that matches the contention resolution identifier carried by that sub-protocol data unit, or the first information carried by the first sub-protocol data unit indicates whether the MAC SDU is applicable to a first terminal device that matches the contention resolution identifier carried by a second sub-protocol data unit among multiple sub-protocol data units. The technical solution of this application designs the information indicated by the first information so that the second message has different formats, which can meet the needs of small data transmission under different requirements. Attached Figure Description

[0030] Figure 1 This is a schematic diagram of a random access procedure in the prior art;

[0031] Figure 2 This is a schematic diagram of another random access procedure in the prior art;

[0032] Figure 3 This is an interactive flowchart of a communication method provided in an embodiment of this application;

[0033] Figure 4 This is a schematic diagram of a second message provided in an embodiment of this application;

[0034] Figure 5 This is a schematic diagram of a sub-protocol data unit provided in an embodiment of this application;

[0035] Figure 6 This is a schematic diagram of a subheader of a sub-protocol data unit provided in an embodiment of this application;

[0036] Figure 7 This is an interactive flowchart of another communication method provided in an embodiment of this application;

[0037] Figure 8 This is a schematic diagram of another second message provided in an embodiment of this application;

[0038] Figure 9 This is a schematic diagram of the subheader of the first sub-protocol data unit provided in the embodiments of this application;

[0039] Figure 10 This is a schematic diagram of the subheader of the second sub-protocol data unit provided in the embodiments of this application;

[0040] Figure 11 This is an interactive flowchart of another communication method provided in the embodiments of this application;

[0041] Figure 12 This is a schematic diagram of yet another type of second message provided in an embodiment of this application;

[0042] Figure 13 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0043] Figure 14 This is a schematic diagram of the hardware structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0044] The communication systems applicable to the embodiments of this application include, but are not limited to, Long Term Evolution (LTE) systems, 5th-generation (5G) systems, New Radio (NR) systems, and future evolution systems or multiple converged communication systems. The 5G system can be a non-standalone (NSA) 5G system or a standalone (SA) 5G system. The technical solutions of this application are also applicable to different network architectures, including but not limited to relay network architectures, dual-connectivity architectures, and vehicle-to-everything (V2X) communication architectures.

[0045] This application primarily relates to communication between terminal devices and network devices. Specifically:

[0046] The network device in this application embodiment can also be called an access network device, for example, it can be a base station (BS) (also called a base station device). A network device is a device deployed in a radio access network (RAN) to provide wireless communication functions. For example, in second-generation (2G) networks, the equipment providing base station functionality includes base transceiver stations (BTS); in third-generation (3G) networks, the equipment providing base station functionality includes nodes (NodeB); in fourth-generation (4G) networks, the equipment providing base station functionality includes evolved nodes (eNB); in wireless local area networks (WLANs), the equipment providing base station functionality is the access point (AP); in NR, the equipment providing base station functionality includes next-generation node base stations (gNBs) and further evolved nodes (ng-eNBs). gNBs and terminal devices communicate using NR technology, while ng-eNBs and terminal devices communicate using evolved universal terrestrial radio access (E-UTRA) technology. Both gNBs and ng-eNBs can connect to the 5G core network. The network devices in this application embodiment also include devices that provide base station functions in future new communication systems.

[0047] In this application, "terminal equipment" can refer to various forms of access terminals, user units, user stations, mobile stations, mobile stations (MS), remote stations, remote terminals, mobile devices, user terminals, wireless communication equipment, user agents, or user devices. Terminal equipment can also be cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), handheld devices with wireless communication capabilities, computing devices, or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal equipment in future 5G networks, or terminal equipment in future evolved Public Land Mobile Networks (PLMNs), etc. This application does not limit the scope of these terms. Terminal equipment can also be referred to as User Equipment (UE), terminal, etc.

[0048] As described in the background section, when multiple terminal devices simultaneously send Msg3 for the random access procedure on the same resource, and the base station sends RRCEarlyDataComplete messages back to these terminal devices respectively, it will result in resource waste.

[0049] In EDT scenarios, for these RRCEarlyDataComplete messages that may carry the exact same content (usually the configuration information related to cell reselection priority is the same), if it is possible to send only one RRCEarlyDataComplete message to instruct multiple specific terminal devices to receive it, then it is obviously an efficient way to multiplex downlink transmissions.

[0050] However, the current Msg4 format cannot achieve this function.

[0051] The existing random access procedure is described below. Figure 1As shown, during the contention-based random access process, the terminal device and the network device exchange two messages, one upstream and one downstream. Message 1 (Msg1) is sent by the terminal device as an uplink random access preamble. Its main purpose is to inform the network device of a random access request and enable the network device to estimate the transmission delay between itself and the terminal device, and to calibrate the uplink transmission timing, i.e., timing advance (TA) adjustment. The terminal device then waits for message 2 (Msg2), which carries the preamble index of Msg1, the TA, message 3 (Msg3) regarding uplink resource allocation, the Cell-Radio Network Temporary Identity (C-RNTII), and backoff parameters.

[0052] When the timing advance of the terminal device is valid, a random access procedure without Msg1 and Msg2 can be considered, meaning the terminal device only sends Msg3 and receives a message (Msg4) to complete the random access. Figure 2 In the random access process shown, multiple terminal devices send Msg3 on shared resources, where Msg3 includes the content and Figure 1 Similar to the random access process, such as the Radio Resource Control (RRC) connection establishment request message, the network device responds and confirms in Msg4, and the messages it carries can also be... Figure 1 The Msg4 in the middle carries the same content, such as contention resolution identification information for each terminal device.

[0053] In the technical solution of this application, by including first information in the subheader of the M sub-protocol data units in the second message to indicate whether the MAC SDU is applicable to the first terminal device that matches at least one contention resolution identifier, it is possible to realize the multiplexing of downlink messages by sending the same MAC SDU to at least one terminal device, thereby saving downlink transmission resources and improving communication efficiency.

[0054] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, specific embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0055] See Figure 1 The method provided in this application specifically includes the following steps:

[0056] Step 301: The terminal device sends a first message to the network device, and the network device receives the first message accordingly.

[0057] Step 302: The network device sends a second message to the terminal device, and the terminal device receives the second message accordingly.

[0058] It should be noted that the sequence number of each step in this embodiment does not represent a limitation on the execution order of each step.

[0059] It is understood that, in specific implementations, the communication method can be implemented using a software program, which runs in a processor integrated within the chip or chip module. The method can also be implemented using a combination of software and hardware; this application does not impose any restrictions.

[0060] In this embodiment, the first message is used to request data transmission. More specifically, the first message can be used to request the transmission of small data.

[0061] In this embodiment, the second message includes multiple sub-protocol data units (subPDUs). The headers of M sub-protocol data units include first information indicating whether a Medium Access Control Service Data Unit (MAC SDU) is applicable to the first terminal device. The first terminal device is a terminal device that matches the contention resolution identifier carried in the sub-protocol data units. The MAC SDU is included in the multiple sub-protocol data units.

[0062] Furthermore, if the first indication information indicates that the MAC SDU is applicable to the first terminal device, then the first terminal device receives the MAC SDU; otherwise, the first terminal device does not receive the MAC SDU.

[0063] like Figure 4 As shown, each second message includes multiple subprotocol data units (subPDUs). The MAC SDU is carried in the last or first N subprotocol data units, where N is a positive integer greater than or equal to 1. A MAC SDU is typically a single RRC message.

[0064] In one specific embodiment, the MAC SDU is carried in the last sub-protocol data unit among multiple sub-protocol data units. The MAC SDU carries the RRCEarlyDataComplete message.

[0065] In another specific embodiment, the MAC SDU is carried in the first sub-protocol data unit of a plurality of sub-protocol data units. The MAC SDU carries the RRCEarlyDataComplete message.

[0066] In this embodiment, when terminal devices simultaneously send a first message on the same resource and all messages are successfully decoded by the network device, and the network device determines that some terminal devices do not have subsequent data to transmit, a MAC SDU (e.g., an RRCEarlyDataComplete message) can be carried in the second message for multiple terminal devices to receive. This avoids the resource waste caused by the network device sending RRCEarlyDataComplete messages back to these terminal devices separately, realizes downlink message reuse, saves downlink transmission resources, and improves communication efficiency.

[0067] In a specific embodiment, the first message can be message 3 (Msg3), and the second message can be message 4 (Msg4). That is, message 3 is used to request small data transmission, and the subheader of message 4, consisting of M sub-protocol data units, includes the first information.

[0068] In a non-limiting embodiment, the first information in the subheader of each subprotocol data unit indicates whether the MAC SDU is applicable to a first terminal device that matches the contention resolution identifier carried by the subprotocol data unit.

[0069] In this embodiment, the structure of each sub-protocol data unit is as follows: Figure 5 As shown, each sub-protocol data unit may include a subheader and a payload. The subheader of each sub-protocol data unit carries first information. The payload of each sub-protocol data unit carries a terminal device contention resolution identifier. If the contention resolution identifier stored by the terminal device matches the terminal device contention resolution identifier carried in the payload, then the sub-protocol data unit is considered to belong to itself.

[0070] Specifically, the first information occupies one bit, and the first bit value indicates that the MAC SDU is applicable to the first terminal device that matches the contention resolution identifier carried by the sub-protocol data unit, and the first information value indicates that the MAC SDU is not applicable to the first terminal device that matches the contention resolution identifier carried by the sub-protocol data unit.

[0071] Please refer to the details. Figure 6 Each sub-protocol data unit occupies an octet Oct1. The sub-header of the sub-protocol data unit has an S1 field, which represents the first information, namely whether the MAC SDU is applicable to the first terminal device that matches the contention resolution identifier carried by the sub-protocol data unit.

[0072] For example, S1 = 1 indicates that it applies, and S1 = 0 indicates that it does not apply.

[0073] For example, S1 = 0 means applicable, and S1 = 1 means not applicable.

[0074] Continue to refer to Figure 6 Each sub-protocol data unit's header also contains E, S, and R fields. The E field indicates whether this sub-protocol data unit is the last one; for example, E=1 indicates that there are more sub-protocol data units following it, and E=0 indicates that there are no more. The S field indicates whether a sub-protocol data unit containing a MAC SDU immediately follows this sub-protocol data unit; for example, S=1 indicates that a sub-protocol data unit containing a MAC SDU immediately follows this sub-protocol data unit, and S=0 indicates that there is no sub-protocol data unit containing a MAC SDU immediately following it. The R field is a reserved bit.

[0075] It is understandable that the S1 field may occupy a reserved bit in the sub-protocol data unit.

[0076] In a non-limiting embodiment, please refer to Figure 7 The communication method may include steps 701-703.

[0077] In step 701, the terminal device sends a first message to the network device. The first message carries the Common Control Channel (CCCH) SDU.

[0078] In step 702, the network device sends a second message to the terminal device. The second message includes multiple sub-protocol data units, with the MAC SDU carried in the last or first N sub-protocol data units.

[0079] In step 703, in response to the CCCH SDU being consistent with the contention resolution identifier carried by the M sub-protocol data units, the terminal device receives the MAC SDU.

[0080] Specifically, the terminal device can use the lower 48 bits of the CCCH SDU as the contention resolution identifier. In other words, the CCCH SDU being consistent with the contention resolution identifier carried by the M sub-protocol data units means that the lower 48 bits of the CCCH SDU are consistent with the contention resolution identifier carried by the M sub-protocol data units.

[0081] In a specific application scenario, three terminal devices, namely UE1, UE2, and UE3, send a first message on the same resource. The network device successfully receives the first message from all three terminal devices and decides to instruct UE1 and UE2 to terminate transmission. The format of the second message would be as follows: Figure 8 As shown.

[0082] Please refer to Figure 8The second message includes four sub-protocol data units, namely the sub-protocol data units corresponding to UE1, UE2 and UE3 respectively, and a sub-protocol data unit including MAC SDU.

[0083] The first sub-protocol data unit occupies two octets (Oct1 and Oct2). In the subheader of this sub-protocol data unit, the E field has a value of 1, indicating that there is another sub-protocol data unit following it; the S field has a value of 0, indicating that there is no subsequent sub-protocol data unit including a MAC SDU; and the S1 field has a value of 1, indicating that the MAC SDU is applicable to the first terminal device matching the contention resolution identifier carried by this sub-protocol data unit. The payload of this sub-protocol data unit carries the contention resolution identifier of UE1.

[0084] The second sub-protocol data unit occupies two octets (Oct3 and Oct4). In the subheader of this sub-protocol data unit, the E field has a value of 1, indicating that there is another sub-protocol data unit following it; the S field has a value of 0, indicating that there is no subsequent sub-protocol data unit containing a MAC SDU; and the S1 field has a value of 1, indicating that the MAC SDU is applicable to the first terminal device matching the contention resolution identifier carried by this sub-protocol data unit. The payload of this sub-protocol data unit carries the contention resolution identifier of UE2.

[0085] The third sub-protocol data unit occupies two octets (Oct5 and Oct6). In the subheader of this sub-protocol data unit, the E field has a value of 0, indicating that this is the last sub-protocol data unit; the S field has a value of 1, indicating that it is followed by a sub-protocol data unit that includes a MAC SDU; and the S1 field has a value of 0, indicating that the MAC SDU is not applicable to the first terminal device that matches the contention resolution identifier carried by this sub-protocol data unit. The payload of this sub-protocol data unit carries the contention resolution identifier of UE3.

[0086] The fourth sub-protocol data unit occupies two octets (Oct7 and Oct8), and includes the Logical Channel Identification (LCID) and the MAC SDU.

[0087] In this embodiment, UE1, UE2, and UE3 all receive the aforementioned second message and determine whether to receive the MAC SDU based on the first information in the second message (i.e., the value of the S1 field). UE1 and UE2 receive the MAC SDU, while UE3 does not.

[0088] In another embodiment of this application, the plurality of sub-protocol data units in the second message are divided into ordinary sub-protocol data units, first sub-protocol data units, and second sub-protocol data units. The first information carried by the first sub-protocol data unit indicates that the MAC SDU is applicable to a first terminal device that matches the contention resolution identifier carried by the second sub-protocol data unit among the plurality of sub-protocol data units. The value of the first information carried in the second sub-protocol data unit is different from the value of the first information carried in the first sub-protocol data unit. The ordinary sub-protocol data unit does not carry first information.

[0089] Furthermore, the second sub-protocol data unit is located after the first sub-protocol data unit, and the first information carried in the second sub-protocol data unit indicates that the current sub-protocol data unit is the second sub-protocol data unit.

[0090] Specifically, the first information occupies one bit, and the first value of the bit indicates that the MAC SDU is applicable to a first terminal device that matches the contention resolution identifier carried by the second sub-protocol data unit among multiple sub-protocol data units. The first information is a second value indicating that the sub-protocol data unit is the second sub-protocol data unit. The terminal device corresponding to the sub-protocol data unit receives the MAC SDU.

[0091] Please refer to Figure 9 , Figure 9 A schematic diagram of the subheader of the first sub-protocol data unit is shown.

[0092] The first sub-protocol data unit has a T field in its subheader, and the value of the T field is a first value, indicating that the MAC SDU is applicable to a first terminal device that matches the contention resolution identifier carried by the second sub-protocol data unit.

[0093] In addition, the header of the first sub-protocol data unit also contains E and R fields. The E field indicates whether the sub-protocol data unit is the last sub-protocol data unit. For example, E=1 indicates that there are more sub-protocol data units to follow, and E=0 indicates that there are no more sub-protocol data units to follow. The R field represents reserved bits.

[0094] In one specific embodiment, the first sub-protocol data unit may include only a sub-header.

[0095] In another specific embodiment, the first sub-protocol data unit may also include a sub-header and a payload.

[0096] Please refer to Figure 10 , Figure 10 A schematic diagram of the subheader of the second sub-protocol data unit is shown.

[0097] The header of the second sub-protocol data unit contains a T field, and the value of the T field is the second value, indicating that this sub-protocol data unit is a second sub-protocol data unit. In other words, the terminal device corresponding to this sub-protocol data unit needs to receive MACSDU.

[0098] In addition, the header of the second sub-protocol data unit also contains E, S, and R fields. The E field indicates whether this sub-protocol data unit is the last one; for example, E=1 indicates that there are more sub-protocol data units following it, and E=0 indicates that there are no more sub-protocol data units following it. The S field indicates whether there is a sub-protocol data unit containing a MAC SDU immediately following this sub-protocol data unit; for example, S=1 indicates that there is a sub-protocol data unit containing a MAC SDU immediately following it, and S=0 indicates that there is no sub-protocol data unit containing a MAC SDU immediately following it. The R field is a reserved bit.

[0099] In a non-limiting embodiment, please refer to Figure 11 The communication method may include steps 1101-1103.

[0100] In step 1101, the terminal device sends a first message to the network device. The first message carries a CCCH SDU.

[0101] In step 1102, the network device sends a second message to the terminal device. The second message includes multiple sub-protocol data units, and the MAC SDU is carried in the last or first N sub-protocol data units of the multiple sub-protocol data units.

[0102] In step 1103, in response to the CCCH SDU being identical to the contention resolution identifier carried by the second sub-protocol data unit, the terminal device receives the MAC SDU.

[0103] Specifically, the terminal device can use the lower 48 bits of the CCCH SDU as the contention resolution identifier. In other words, the consistency between the contention resolution identifier carried by the CCCH SDU and the second sub-protocol data unit means that the lower 48 bits of the CCCH SDU are consistent with the contention resolution identifiers carried by the M sub-protocol data units.

[0104] In a specific application scenario, three terminal devices, namely UE1, UE2, and UE3, send a first message on the same resource. The network device successfully receives the first message from all three terminal devices and decides to instruct UE1 and UE2 to terminate transmission. The format of the second message would be as follows: Figure 12 As shown.

[0105] Please refer to Figure 12 The second message includes five sub-protocol data units.

[0106] The first sub-protocol data unit is a normal sub-protocol data unit, occupying two octets (Oct1 and Oct2). In the sub-header of this sub-protocol data unit, the E field has a value of 1, indicating that there is another sub-protocol data unit following it; the S field has a value of 0, indicating that there is no sub-protocol data unit that includes a MAC SDU immediately following it. The payload of this sub-protocol data unit carries the UE3 contention resolution identifier.

[0107] The second sub-protocol data unit occupies one octet (Oct3). In the subheader of this sub-protocol data unit, the E field has a value of 1, indicating that there is another sub-protocol data unit following; the T field has a value of 1, indicating that the MAC SDU is applicable to the first terminal device that matches the contention resolution identifier carried by the second sub-protocol data unit. The subheader of the second sub-protocol data unit is a segmentation indicator.

[0108] The third sub-protocol data unit occupies two octets (Oct4 and Oct5). In the sub-header of this sub-protocol data unit, the E field has a value of 1, indicating that there is another sub-protocol data unit following; the T field has a value of 0, indicating that this sub-protocol data unit is the second sub-protocol data unit. The payload of this sub-protocol data unit carries the contention resolution identifier of UE1.

[0109] The fourth sub-protocol data unit occupies two octets (Oct6 and Oct7). In the sub-header of this sub-protocol data unit, the E field has a value of 1, indicating that there is another sub-protocol data unit following; the T field has a value of 0, indicating that this sub-protocol data unit is the second sub-protocol data unit. The payload of this sub-protocol data unit carries the contention resolution identifier of UE2.

[0110] The fifth sub-protocol data unit occupies two octets (Oct8 and Oct9) and includes the LCID and MAC SDU.

[0111] In this embodiment, UE1, UE2, and UE3 all receive the aforementioned second message and determine whether to receive the MAC SDU based on the first sub-protocol data unit and the first information (i.e., the value of the T field) in the second sub-protocol data unit. Specifically, UE1 and UE2 read the MAC SDUs of Oct8 and Oct9, while UE3 does not read the MAC SDUs of Oct8 and Oct9.

[0112] For more specific implementations of the embodiments of this application, please refer to the foregoing embodiments, which will not be repeated here.

[0113] Please refer to Figure 13 , Figure 13 A communication device 130 is shown, which may include:

[0114] The communication module 1301 is used to send a first message, which is used to request data transmission.

[0115] Communication module 1301 is also used to receive a second message, the second message including a plurality of sub-protocol data units, wherein the headers of M of the plurality of sub-protocol data units include first information, the first information indicating whether a Media Access Control Service Data Unit (MAC SDU) is applicable to a first terminal device that matches at least one contention resolution identifier.

[0116] Furthermore, the first message carries the Common Control Channel (CCCH) SDU, and the communication module 1301 receives the MAC SDU in response to the CCCH SDU being consistent with the contention resolution identifier carried by the M sub-protocol data units.

[0117] Furthermore, the communication module 1301 receives the MAC SDU in response to the CCCH SDU being identical to the contention resolution identifier carried by the second sub-protocol data unit.

[0118] In specific implementations, the aforementioned communication device 130 may correspond to a chip with communication function in a terminal device, such as a system-on-a-chip (SOC), a baseband chip, etc.; or to a chip module in a terminal device that includes a chip with communication function; or to a chip module with a chip with data processing function; or to a terminal device.

[0119] In another non-limiting embodiment, the communication module 1301 is configured to receive a first message, the first message being a request for data transmission;

[0120] Communication module 1301 is also used to send a second message, the second message including a plurality of sub-protocol data units, wherein the headers of M of the plurality of sub-protocol data units include first information, the first information indicating whether a Media Access Control Service Data Unit (MAC SDU) is applicable to a first terminal device that matches at least one contention resolution identifier.

[0121] Furthermore, the first information in the subheader of each sub-protocol data unit indicates whether the MAC SDU is applicable to a first terminal device that matches the contention resolution identifier carried by that sub-protocol data unit.

[0122] Furthermore, the first information indication MAC SDU carried by the first sub-protocol data unit is applicable to a first terminal device that matches the contention resolution identifier carried by the second sub-protocol data unit among the plurality of sub-protocol data units.

[0123] In specific implementations, the aforementioned communication device 130 may correspond to a chip with communication function in a network device, such as a SOC, baseband chip, etc.; or correspond to a chip module in a network device that includes a chip with communication function; or correspond to a chip module with a chip with data processing function; or correspond to a network device.

[0124] Other relevant descriptions of the communication device 130 can be found in the descriptions in the foregoing embodiments, and will not be repeated here.

[0125] Regarding the modules / units included in the various devices and products described in the above embodiments, they can be software modules / units, hardware modules / units, or a combination of both. For example, for devices and products applied to or integrated into a chip, all modules / units can be implemented using hardware methods such as circuits, or at least some modules / units can be implemented using software programs running on a processor integrated within the chip, while the remaining (if any) modules / units can be implemented using hardware methods such as circuits. For devices and products applied to or integrated into a chip module, all modules / units can be implemented using hardware methods such as circuits. Different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or different components of the chip module, or at least some modules / units can be implemented using hardware methods such as circuits. The implementation is achieved through a software program that runs on a processor integrated within the chip module. The remaining modules / units (if any) can be implemented using hardware methods such as circuits. For various devices and products applied to or integrated into terminal equipment, each of their modules / units can be implemented using hardware methods such as circuits. Different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or different components within the terminal equipment. Alternatively, at least some modules / units can be implemented using a software program that runs on a processor integrated within the terminal equipment, while the remaining modules / units (if any) can be implemented using hardware methods such as circuits.

[0126] This application also discloses a storage medium, which is a computer-readable storage medium storing a computer program thereon. When the computer program is executed, it can perform the steps of the method shown in the foregoing embodiments. The storage medium may include read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk, etc. The storage medium may also include non-volatile memory or non-transitory memory, etc.

[0127] Please refer to Figure 14 This application also provides a schematic diagram of the hardware structure of a communication device. The device includes a processor 1401, a memory 1402, and a transceiver 1403.

[0128] Processor 1401 can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program according to the present application. Processor 1401 may also include multiple CPUs, and processor 1401 can be a single-core processor or a multi-core processor. Here, processor can refer to one or more devices, circuits, or processing cores used to process data (e.g., computer program instructions).

[0129] The memory 1402 may be a ROM or other type of static storage device capable of storing static information and instructions, RAM or other type of dynamic storage device capable of storing information and instructions, or it may be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer. This application embodiment does not impose any limitations on this. The memory 1402 may exist independently (in this case, the memory 1402 may be located outside or inside the device) or it may be integrated with the processor 1401. The memory 1402 may contain computer program code. The processor 1401 is used to execute the computer program code stored in the memory 1402 to implement the method provided in this application embodiment.

[0130] The processor 1401, memory 1402, and transceiver 1403 are connected via a bus. The transceiver 1403 is used to communicate with other devices or communication networks. Optionally, the transceiver 1403 may include a transmitter and a receiver. The device in the transceiver 1403 that implements the receiving function can be considered as a receiver, and the receiver is used to perform the receiving steps in the embodiments of this application. The device in the transceiver 1403 that implements the transmitting function can be considered as a transmitter, and the transmitter is used to perform the transmitting steps in the embodiments of this application.

[0131] when Figure 14 The schematic diagram shown illustrates the structure of the terminal device involved in the above embodiments. The processor 1401 is used to control and manage the actions of the terminal device. For example, the processor 1401 is used to support the terminal device in performing... Figure 3 Steps 301 and 302 in the text, or Figure 7 Steps 701, 702, and 703 in the text, or Figure 11 The actions performed by the terminal device in steps 1101, 1102, and 1103, and / or other processes described in the embodiments of this application. The processor 1401 can communicate with other network entities via the transceiver 1403, for example, with the aforementioned network device. The memory 1402 is used to store the program code and data of the terminal device. When the processor runs the computer program, it can control the transceiver 1403 to send a first message, receive a second message, RRC signaling, etc.

[0132] when Figure 14 The schematic diagram shown illustrates the structure of the network device involved in the above embodiments. The processor 1401 is used to control and manage the actions of the network device. For example, the processor 1401 is used to support the network device in performing... Figure 3 Steps 301 and 302 in the text, or Figure 7 Steps 701 and 702 in the text, or Figure 11 The processor 1401 performs actions in steps 1101 and 1102, and / or other processes described in the embodiments of this application. The processor 1401 can communicate with other network entities via the transceiver 1403, for example, with the aforementioned terminal device. The memory 1402 stores the program code and data of the network device. When the processor runs the computer program, it can control the transceiver 1403 to receive a first message, send a second message, RRC signaling, etc.

[0133] In this application embodiment, a one-way communication link from the access network to the terminal device is defined as a downlink, and the data transmitted on the downlink is called downlink data. The transmission direction of the downlink data is called the downlink direction. On the other hand, a one-way communication link from the terminal device to the access network is defined as an uplink, and the data transmitted on the uplink is called uplink data. The transmission direction of the uplink data is called the uplink direction.

[0134] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this article indicates that the preceding and following related objects have an "or" relationship.

[0135] In the embodiments of this application, "multiple" refers to two or more.

[0136] The descriptions of "first," "second," etc., appearing in the embodiments of this application are for illustrative purposes and to distinguish the objects being described. They have no order and do not indicate any special limitation on the number of devices in the embodiments of this application, nor do they constitute any limitation on the embodiments of this application.

[0137] In this application, the term "connection" refers to various connection methods, such as direct connection or indirect connection, to achieve communication between devices. This application does not impose any limitations on this.

[0138] The above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer program are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means.

[0139] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0140] In the several embodiments provided in this application, it should be understood that the disclosed methods, apparatuses, and systems can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for example, the division of units is merely a logical functional division, and other division methods may exist in actual implementation; for example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0141] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0142] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can be physically included separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or in the form of hardware plus software functional units.

[0143] The integrated unit implemented as a software functional unit described above can be stored in a computer-readable storage medium. This software functional unit, stored in a storage medium, includes several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute some steps of the methods described in the various embodiments of this application.

[0144] While this application discloses the above information, it is not limited thereto. Any person skilled in the art can make various modifications and alterations without departing from the spirit and scope of this application; therefore, the scope of protection of this application shall be determined by the scope defined in the claims.

Claims

1. A communication method, characterized in that, include: Send a first message, which is used to request data transmission; Receive a second message, which is used to respond to the first message, and the second message includes multiple sub-protocol data units; The plurality of sub-protocol data units include M sub-protocol data units. The subheader of each of the M sub-protocol data units includes first information. The first information indicates whether the Media Access Control Service Data Unit (MACSDU) is applicable to at least one first terminal device. The first terminal device is a terminal device that matches the contention resolution identifier, and M is a positive integer greater than or equal to 1. The plurality of sub-protocol data units include the MAC SDU; The plurality of sub-protocol data units include the contention resolution identifier.

2. The communication method according to claim 1, characterized in that, The MAC SDU is carried in the last or first N sub-protocol data units of the plurality of sub-protocol data units, where N is a positive integer greater than or equal to 1.

3. The communication method according to claim 1, characterized in that, The first information in the subheader of each sub-protocol data unit indicates whether the MAC SDU is applicable to a first terminal device that matches the contention resolution identifier carried by that sub-protocol data unit.

4. The communication method according to claim 3, characterized in that, The first information occupies one bit. The first bit value indicates that the MAC SDU is applicable to the first terminal device that matches the contention resolution identifier carried by the sub-protocol data unit. The second bit value indicates that the MAC SDU is not applicable to the first terminal device that matches the contention resolution identifier carried by the sub-protocol data unit.

5. The communication method according to claim 3, characterized in that, The first message carries the Common Control Channel (CCCHSDU), and the communication method further includes: In response to the CCCH SDU being identical to the contention resolution identifier carried by the M sub-protocol data units, the MAC SDU is received.

6. The communication method according to claim 1, characterized in that, The M sub-protocol data units include a first sub-protocol data unit and a second sub-protocol data unit. The first information indicated by the first sub-protocol data unit is applicable to a first terminal device that matches the contention resolution identifier carried by the second sub-protocol data unit.

7. The communication method according to claim 6, characterized in that, The second sub-protocol data unit is located after the first sub-protocol data unit. The first information occupies one bit. The first bit value indicates that the sub-protocol data unit where the first information is located is the first sub-protocol data unit and the MAC SDU is applicable to a first terminal device that matches the contention resolution identifier carried by the second sub-protocol data unit. The second bit value indicates that the sub-protocol data unit where the first information is located is the second sub-protocol data unit.

8. The communication method according to claim 6, characterized in that, The first message carries CCCHSDU, and the communication method further includes: In response to the CCCH SDU matching the contention resolution identifier carried by the second sub-protocol data unit, the MAC SDU is received.

9. A communication method, characterized in that, include: Receive a first message, which is used to request data transmission; Send a second message in response to the first message. The second message includes a plurality of sub-protocol data units, which include M sub-protocol data units. The subheader of each of the M sub-protocol data units includes first information. The first information indicates whether the Media Access Control Service Data Unit (MAC SDU) is applicable to at least one first terminal device. The first terminal device is a terminal device that matches the contention resolution identifier, and M is a positive integer greater than or equal to 1. The plurality of sub-protocol data units include the MAC SDU; The plurality of sub-protocol data units include the contention resolution identifier.

10. The communication method according to claim 9, characterized in that, The first information in the subheader of each subprotocol data unit indicates whether the MAC SDU is applicable to a first terminal device that matches the contention resolution identifier carried by that subprotocol data unit.

11. The communication method according to claim 9, characterized in that, The M sub-protocol data units include a first sub-protocol data unit and a second sub-protocol data unit. The first information indicated by the first sub-protocol data unit is applicable to a first terminal device that matches the contention resolution identifier carried by the second sub-protocol data unit.

12. A communication device, characterized in that, include: The communication module is used to send a first message, which is used to request data transmission. The communication module is also used to receive a second message. The second message is used in response to the first message, and the second message includes multiple sub-protocol data units; The plurality of sub-protocol data units include M sub-protocol data units. The subheader of each of the M sub-protocol data units includes first information. The first information indicates whether the Media Access Control Service Data Unit (MACSDU) is applicable to at least one first terminal device. The first terminal device is a terminal device that matches the contention resolution identifier, and M is a positive integer greater than or equal to 1. The plurality of sub-protocol data units include the MAC SDU; The plurality of sub-protocol data units include the contention resolution identifier.

13. A communication device, characterized in that, include: The communication module is used to receive a first message, which is used to request data transmission. The communication module is also used to send a second message. The second message is used to respond to the first message. The second message includes a plurality of sub-protocol data units, the plurality of sub-protocol data units including M sub-protocol data units, and the sub-header of each of the M sub-protocol data units includes first information. The first information indicates whether the Media Access Control Service Data Unit (MAC SDU) is applicable to at least one first terminal device, the first terminal device being a terminal device that matches the contention resolution identifier, and M being a positive integer greater than or equal to 1. The plurality of sub-protocol data units include the MAC SDU; The plurality of sub-protocol data units include the contention resolution identifier.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that, The computer program, when executed by a processor, performs the steps of the communication method according to any one of claims 1 to 11.

15. A communication device comprising a memory and a processor, wherein the memory stores a computer program executable on the processor, characterized in that, When the processor runs the computer program, it performs the steps of the communication method according to any one of claims 1 to 8.

16. A communication device comprising a memory and a processor, wherein the memory stores a computer program executable on the processor, characterized in that, When the processor runs the computer program, it performs the steps of the communication method according to any one of claims 9 to 11.

Citation Information

Patent Citations

  • Information transmission method, base station and terminal

    CN113260075A

  • Random access method and device, and communication system

    WO2021062639A1