Communication method, terminal, network device, system, and storage medium
By using CB-MSG3 and CB-MSG4 interactions between terminals and network devices, and utilizing the MAC subheader and response message in the MAC PDU, the problem of unreliable data transmission is solved, faster connection establishment is achieved, signaling overhead is reduced, and data transmission efficiency is improved.
Patent Information
- Application Number
- PCT/CN2025/093575
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-08
- Publication Date
- 2026-11-12
AI Technical Summary
Existing technologies suffer from unreliable data transmission, long connection establishment times, and high signaling overhead during early and small data transmission processes.
By using contention-based message 3 (CB-MSG3) and message 4 (CB-MSG4) interactions between terminals and network devices, and utilizing the MAC subheader and response message in the MAC PDU, contention conflicts are resolved, thereby improving the reliability of data transmission.
It improves the reliability of data transmission, reduces connection establishment time and signaling overhead, and lowers data transmission latency.
Smart Images

Figure CN2025093575_12112026_PF_FP_ABST
Abstract
Description
Communication methods, terminals, network devices, systems, and storage media Technical Field
[0001] This disclosure relates to the field of communications, and in particular to communication methods, terminals, network devices, systems and storage media. Background Technology
[0002] For Early Data Transmission (EDT) and / or Small Data Transmission (SDT), data can be uploaded via Message 3 (MSG3) during random access, allowing the terminal to transmit small amounts of data in the early stages of connection establishment, thereby reducing connection establishment time and signaling overhead, improving data transmission efficiency and reducing power consumption. Summary of the Invention
[0003] To improve the reliability of data transmission, embodiments of this disclosure provide a communication method, a terminal, a network device, a system, and a storage medium.
[0004] According to a first aspect of the present disclosure, a communication method is provided, the method being executed by a terminal, the method comprising:
[0005] Send a contention-based message 3 (CB-MSG3) to the network device; wherein the CB-MSG3 carries data;
[0006] The network device receives a contention-based message 4 (CB-MSG4) Media Access Control Packet Data Unit (MAC PDU); wherein, if the MAC PDU includes a response message from at least one terminal, each response message is used to respond to a CB-MSG3 sent by one of the at least one terminals.
[0007] According to a second aspect of the present disclosure, a communication method is provided, the method being performed by a network device, the method comprising:
[0008] The receiving terminal sends a contention-based message 3 (CB-MSG3); wherein the CB-MSG3 carries data;
[0009] The Media Access Control Packet Data Unit (MAC PDU) based on contention-based message 4 (CB-MSG4) is sent to the terminal; wherein, if the MAC PDU includes a response message from at least one terminal, each response message is used to respond to CB-MSG3 sent by one of the at least one terminals.
[0010] According to a third aspect of the present disclosure, a terminal is provided, comprising:
[0011] The transceiver module is configured to send contention-based message 3 (CB-MSG3) to the network device; wherein the CB-MSG3 carries data;
[0012] The transceiver module is further configured to receive a contention-based message 4 (CB-MSG4) Media Access Control Packet Data Unit (MAC PDU) sent by the network device; wherein, if the MAC PDU includes a response message from at least one terminal, each response message is used to respond to a CB-MSG3 sent by one of the at least one terminals.
[0013] According to a fourth aspect of the present disclosure, a network device is provided, comprising:
[0014] The transceiver module is configured to receive contention-based message 3 (CB-MSG3) sent by the terminal; wherein the CB-MSG3 carries data.
[0015] The transceiver module is further configured to send a contention-based message 4 (CB-MSG4) Media Access Control Packet Data Unit (MAC PDU) to the terminal; wherein, if the MAC PDU includes a response message from at least one terminal, each response message is used to respond to a CB-MSG3 sent by one of the at least one terminals.
[0016] According to a fifth aspect of the present disclosure, a terminal is provided, comprising:
[0017] One or more processors;
[0018] The processor is used to execute the method described in any one of the first aspects.
[0019] According to a sixth aspect of the present disclosure, a network device is provided, comprising:
[0020] One or more processors;
[0021] The processor is used to execute the communication method described in any one of the second aspects.
[0022] According to a seventh aspect of the present disclosure, a communication system is provided, comprising:
[0023] A terminal, the terminal being configured to implement the communication method described in any one of the first aspects;
[0024] A network device configured to implement the communication method described in any one of the second aspects.
[0025] According to an eighth aspect of the present disclosure, a storage medium is provided that stores instructions that, when executed on a communication device, cause the communication device to perform a communication method as described in any one of the first or second aspects.
[0026] According to a ninth aspect of the present disclosure, a computer program product is provided, including a computer program that, when executed by a processor, is used to implement the communication method described in any one of the first or second aspects.
[0027] In this embodiment, the terminal can directly send data to the network device via CB-MSG3 without needing to send messages 1 and 2, and receive MAC PDUs (CB-MSG4) sent by the network device. If the PDU includes a response message for at least one terminal, each response message can be used to respond to a CB-MSG3 sent by one terminal. This disclosure improves the reliability of data transmission, especially small data transmission, reduces connection establishment time and signaling overhead, and helps reduce data transmission latency.
[0028] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description
[0029] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.
[0030] Figure 1 is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.
[0031] Figure 2 is an exemplary interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure.
[0032] Figure 3A is one of the exemplary flowcharts of a communication method provided according to an embodiment of the present disclosure.
[0033] Figure 3B is a second exemplary flowchart of a communication method provided according to an embodiment of the present disclosure.
[0034] Figure 4A is one of the structural schematic diagrams of a MAC subheader for backoff provided according to an embodiment of the present disclosure.
[0035] Figure 4B is one of the structural schematic diagrams of a MAC subheader including only CR-ID according to an embodiment of the present disclosure.
[0036] Figure 4C is one of the structural schematic diagrams of a MAC subheader including CR-ID and RNTI provided according to an embodiment of the present disclosure.
[0037] Figure 4D is one of the structural schematic diagrams of a MAC PDU provided according to an embodiment of the present disclosure.
[0038] Figure 4E is a second schematic diagram of the structure of a MAC subheader for backoff provided according to an embodiment of the present disclosure.
[0039] Figure 4F is a second schematic diagram of the structure of a MAC sub-header including only CR-ID according to an embodiment of the present disclosure.
[0040] Figure 4G is a second schematic diagram of the structure of a MAC sub-header including CR-ID and RNTI provided according to an embodiment of the present disclosure.
[0041] Figure 4H is a second schematic diagram of the structure of a MAC PDU provided according to an embodiment of the present disclosure.
[0042] Figure 5A is an exemplary block diagram of a terminal provided according to an embodiment of the present disclosure.
[0043] Figure 5B is an exemplary block diagram of a network device provided according to an embodiment of the present disclosure.
[0044] Figure 6A is an exemplary schematic diagram of a communication device provided according to an embodiment of the present disclosure.
[0045] Figure 6B is an exemplary schematic diagram of a chip provided according to an embodiment of the present disclosure. Detailed Implementation
[0046] This disclosure provides a communication method, terminal, network device, system, and storage medium.
[0047] In a first aspect, embodiments of this disclosure provide a communication method executed by a terminal, the method comprising: sending a contention-based message 3 (CB-MSG3) to a network device; wherein the CB-MSG3 carries data; receiving a media access control packet data unit (MAC PDU) of a contention-based message 4 (CB-MSG4) sent by the network device; wherein, if the MAC PDU includes a response message from at least one terminal, each response message is used to respond to the CB-MSG3 sent by one of the at least one terminals.
[0048] The above embodiments improve the reliability of data transmission, especially small data transmission, reduce connection establishment time and signaling overhead, and help reduce data transmission latency.
[0049] In conjunction with some embodiments of the first aspect, in some embodiments, the MAC PDU includes at least one of the following: a MAC header; a response message from at least one terminal; and padding items.
[0050] In the above embodiments, the MAC PDU may include at least one of the above-mentioned features, thereby improving the reliability of data transmission, especially small data transmission.
[0051] In conjunction with some embodiments of the first aspect, in some embodiments, the MAC header includes at least one of the following MAC sub-headers: a MAC sub-header for backoff; a MAC sub-header including a contention resolution identifier; and a MAC sub-header including a contention resolution identifier and a Radio Network Temporary Identifier (RNTI).
[0052] In the above embodiments, the MAC header may include at least one MAC sub-header, which improves the reliability of CB-MSG4 MAC PDU transmission and helps to resolve contention conflicts.
[0053] In conjunction with some embodiments of the first aspect, in some embodiments, the first MAC subheader is any one of the MAC subheaders, and the first MAC subheader includes at least one of the following: a first type indication field, which indicates that the first MAC subheader is a MAC subheader for backoff or a MAC subheader including a contention resolution identifier; a second type indication field, which indicates whether the first MAC subheader includes an RNTI; an extension indication field, which indicates whether there is any further extended information field in the MAC subheader; and a reserved field.
[0054] In the above embodiments, any MAC subheader in the MAC header may include at least one of the above-mentioned information fields, thereby improving the reliability of CB-MSG4 MAC PDU transmission.
[0055] In conjunction with some embodiments of the first aspect, in some embodiments, the MAC PDU includes at least one of the following: a contention resolution identifier and an RNTI; a contention resolution identifier and a first type of response message from at least one terminal.
[0056] In the above embodiments, the MAC PDU may include at least one of the above-mentioned features, which improves data transmission efficiency and helps resolve contention conflicts.
[0057] In conjunction with some embodiments of the first aspect, in some embodiments, the number of response messages included in the MAC PDU is equal to the number of MAC subheaders including a contention resolution identifier in the MAC header; and / or the sequence number of the response message corresponding to the terminal is the same as the sequence number of the MAC subheader including a contention resolution identifier corresponding to the terminal in the MAC header.
[0058] In the above embodiments, the number and sequence number of response messages satisfy the above conditions, which helps the terminal determine whether data has been successfully transmitted through CB-MSG3 and improves the reliability of data transmission.
[0059] In conjunction with some embodiments of the first aspect, in some embodiments, the second MAC subheader is any one of the MAC subheaders, and the second MAC subheader includes at least one of the following: a first type indication field, which indicates that the second MAC subheader is a MAC subheader for backoff or a MAC subheader including a contention resolution identifier; a second type indication field, which indicates whether the second MAC subheader includes an RNTI; a third type indication field, which indicates whether the second MAC subheader has an associated response message; an extension indication field, which indicates whether there is any further extended information field in the MAC header; and a reserved field.
[0060] In the above embodiments, any MAC subheader in the MAC header may include at least one of the above-mentioned information fields, thereby improving the reliability of CB-MSG4 MAC PDU transmission.
[0061] In conjunction with some embodiments of the first aspect, in some embodiments, the MAC PDU includes at least one of the following: a contention resolution identifier and an RNTI; a contention resolution identifier and a first type of response message from at least one terminal; and a contention resolution identifier, an RNTI, and a second type of response message from at least one terminal.
[0062] In the above embodiments, the MAC PDU may include at least one of the above-mentioned features, which improves data transmission efficiency and helps resolve contention conflicts.
[0063] In conjunction with some embodiments of the first aspect, in some embodiments, the number of response messages included in the MAC PDU is equal to the number of first-type MAC subheaders included in the MAC header; and / or the sequence number of the response message corresponding to the terminal is the same as the sequence number of the first-type MAC subheader corresponding to the terminal in the MAC header; wherein, the first-type MAC subheader is the MAC subheader of the associated response message indicated by the third type indication field.
[0064] In the above embodiments, the number and sequence number of response messages satisfy the above conditions, which helps the terminal determine whether data has been successfully transmitted through CB-MSG3 and improves the reliability of data transmission.
[0065] In conjunction with some embodiments of the first aspect, in some embodiments, the first type of response message is any one of the following: a data transmission completion message; a Radio Resource Control (RRC) connection release message.
[0066] In the above embodiments, the terminal determines that it does not need to switch to the connected state based on the first type of response message sent by the network device, thus clarifying the terminal behavior and achieving high availability.
[0067] In conjunction with some embodiments of the first aspect, in some embodiments, the second type of response message is any one of the following: an RRC connection establishment message; an RRC connection recovery message.
[0068] In the above embodiments, the terminal can switch to the connected state based on the second type of response message sent by the network device, which clarifies the terminal behavior and ensures high availability.
[0069] Secondly, embodiments of this disclosure provide a communication method executed by a network device, the method comprising: receiving a contention-based message 3 (CB-MSG3) sent by a terminal; wherein the CB-MSG3 carries data; and sending a contention-based message 4 (CB-MSG4) of Media Access Control Packet Data Unit (MAC PDU) to the terminal; wherein, if the MAC PDU includes a response message from at least one terminal, each response message is used to respond to the CB-MSG3 sent by one of the at least one terminals.
[0070] In conjunction with some embodiments of the second aspect, in some embodiments, the MAC PDU includes at least one of the following: a MAC header; a response message from at least one terminal; and padding items.
[0071] In conjunction with some embodiments of the second aspect, in some embodiments, the MAC header includes at least one of the following MAC sub-headers: a MAC sub-header for backoff; a MAC sub-header including a contention resolution identifier; and a MAC sub-header including a contention resolution identifier and a Radio Network Temporary Identifier (RNTI).
[0072] In conjunction with some embodiments of the second aspect, in some embodiments, the first MAC sub-header is any one of the MAC sub-headers, and the first MAC sub-header includes at least one of the following: a first type indication field, which indicates that the first MAC sub-header is a MAC sub-header for backoff or a MAC sub-header including a contention resolution identifier; a second type indication field, which indicates whether the first MAC sub-header includes an RNTI; an extension indication field, which indicates whether there is any further extended information field in the MAC head; and a reserved field.
[0073] In conjunction with some embodiments of the second aspect, in some embodiments, the MAC PDU includes at least one of the following: a contention resolution identifier and an RNTI; a contention resolution identifier and a first type of response message from at least one terminal.
[0074] In conjunction with some embodiments of the second aspect, in some embodiments, the number of response messages included in the MAC PDU is equal to the number of MAC subheaders including a contention resolution identifier in the MAC header; and / or the sequence number of the response message corresponding to the terminal is the same as the sequence number of the MAC subheader including a contention resolution identifier corresponding to the terminal in the MAC header.
[0075] In conjunction with some embodiments of the second aspect, in some embodiments, the second MAC sub-header is any one of the MAC sub-headers, and the second MAC sub-header includes at least one of the following: a first type indication field, which indicates that the second MAC sub-header is a MAC sub-header for backoff or a MAC sub-header including a contention resolution identifier; a second type indication field, which indicates whether the second MAC sub-header includes an RNTI; a third type indication field, which indicates whether the second MAC sub-header has an associated response message; an extension indication field, which indicates whether there is an extended information field in the MAC header; and a reserved field.
[0076] In conjunction with some embodiments of the second aspect, in some embodiments, the MAC PDU includes at least one of the following: a contention resolution identifier and an RNTI; a contention resolution identifier and a first type of response message from at least one terminal; and a contention resolution identifier, an RNTI, and a second type of response message from at least one terminal.
[0077] In conjunction with some embodiments of the second aspect, in some embodiments, the number of response messages included in the MAC PDU is equal to the number of first-type MAC subheaders included in the MAC header; and / or the sequence number of the response message corresponding to the terminal is the same as the sequence number of the first-type MAC subheader corresponding to the terminal in the MAC header; wherein, the first-type MAC subheader is the MAC subheader of the associated response message indicated by the third type indication field.
[0078] In conjunction with some embodiments of the second aspect, in some embodiments, the first type of response message is any one of the following: a data transmission completion message; a Radio Resource Control (RRC) connection release message.
[0079] In conjunction with some embodiments of the second aspect, in some embodiments, the second type of response message is any one of the following: an RRC connection establishment message; an RRC connection recovery message.
[0080] Thirdly, embodiments of this disclosure provide a terminal, including: a transceiver module configured to send a contention-based message 3 (CB-MSG3) to a network device; wherein the CB-MSG3 carries data; the transceiver module is further configured to receive a Media Access Control Packet Data Unit (MAC PDU) of a contention-based message 4 (CB-MSG4) sent by the network device; wherein, when the MAC PDU includes a response message from at least one terminal, each response message is used to respond to the CB-MSG3 sent by one of the at least one terminals.
[0081] Fourthly, embodiments of this disclosure provide a network device, including: a transceiver module configured to receive a contention-based message 3 (CB-MSG3) sent by a terminal; wherein the CB-MSG3 carries data; the transceiver module is further configured to send a media access control packet data unit (MAC PDU) of a contention-based message 4 (CB-MSG4) to the terminal; wherein, when the MAC PDU includes a response message from at least one terminal, each response message is used to respond to the CB-MSG3 sent by one of the at least one terminals.
[0082] Fifthly, embodiments of this disclosure provide a terminal comprising: one or more processors; wherein the processors are configured to execute the communication method described in any one of the first aspects.
[0083] In a sixth aspect, embodiments of this disclosure provide a network device comprising: one or more processors; wherein the processors are configured to perform the communication method described in any one of the second aspects.
[0084] In a seventh aspect, embodiments of this disclosure provide a communication system comprising: a terminal configured to perform the communication method described in any one aspect; and a network device configured to perform the communication method described in any one aspect.
[0085] Eighthly, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the communication method as described in either the first or second aspect.
[0086] In a ninth aspect, embodiments of this disclosure provide a computer program product, including a computer program that, when executed by a processor, is used to implement the communication method described in any one of the first or second aspects.
[0087] It is understood that the aforementioned terminals, network devices, communication systems, and storage media are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.
[0088] This disclosure provides communication methods, terminals, network devices, systems, and storage media. In some embodiments, the terms "communication method" and "information transmission method," "information processing method," etc., can be used interchangeably; the terms "communication device" and "information transmission device," "information processing device," etc., can be used interchangeably; and the terms "information transmission system," "information processing system," "communication system," etc., can be used interchangeably.
[0089] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.
[0090] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.
[0091] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.
[0092] In this disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the aforementioned," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular or a plural expression.
[0093] In the embodiments of this disclosure, "multiple" refers to two or more.
[0094] In some embodiments, the terms “at least one of”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.
[0095] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of B); in some embodiments, B (execute B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, C, etc.
[0096] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execution of A regardless of B); in some embodiments, B (execution of B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, C, etc.
[0097] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.
[0098] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
[0099] In some embodiments, the apparatus and device may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. In some cases, they may also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "entity", "body", etc.
[0100] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.
[0101] In some embodiments, data, information, etc., may be obtained with the user's consent.
[0102] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.
[0103] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.
[0104] As shown in Figure 1, the communication system 100 includes a terminal 101 and a network device 102.
[0105] In some embodiments, terminal 101 includes, for example, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home, but is not limited thereto.
[0106] In one example, terminal 101 may be an LPWA terminal or a high-end terminal, which is not limited in this disclosure.
[0107] In some embodiments, network device 102 may include at least one of access network device 102-1 and core network device 102-2.
[0108] In some embodiments, the access network device 102-1 is, for example, a node or device that connects a terminal to a wireless network. The access network device may include at least one of the following in a 5G communication system: an evolved Node B (eNB), a next-generation eNB (ng-eNB), a next-generation Node B (gNB), a node B (NB), a home node B (HNB), a home evolved node B (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open RAN, a cloud RAN, a base station in other communication systems, and an access node in a Wi-Fi system, but is not limited thereto.
[0109] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.
[0110] In some embodiments, the access network device 102-2 may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. By adopting the CU-DU structure, the protocol layer of the access network device can be separated. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU, which is centrally controlled by the CU. However, this is not the only possibility.
[0111] In some embodiments, the core network device 102-2 may be a single device, including a first network element, a second network element, etc., or it may be multiple devices or a group of devices, each including all or part of the first network element, the second network element, etc. Network elements may be virtual or physical. The core network may include, for example, at least one of the Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).
[0112] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.
[0113] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.
[0114] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).
[0115] In some embodiments, the early data transmission of contention-based message 3 (Contention Based-Msg3 EDT, CB-Msg3 EDT) is described.
[0116] To improve uplink capacity, contention-based MSG3 transmission EDT was introduced in Non-Terrestrial Networks (NTNs). This means that small data transmissions directly utilize the contentionable MSG3 resource instead of using Message 1 (MSG1) and Message 2 (MSG2). Because MSG3 transmission uses contention, conflicts may occur due to multiple terminals using the same resource; these conflicts can be resolved using MSG4.
[0117] To improve the reliability of data transmission and resolve contention, this disclosure provides the following communication methods, terminals, network devices, systems, and storage media.
[0118] Figure 2 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2, the embodiments of the present disclosure relate to a communication method, which includes:
[0119] In step S2101, terminal 101 sends CB-MSG3 to network device 102.
[0120] In some embodiments, network device 102 receives CB-MSG3.
[0121] In some embodiments, the CB-MSG3 carries a small amount of data. The amount of this data may be less than or equal to a data volume threshold, which may be determined based on a predefined method and / or the configuration of network device 102.
[0122] For example, terminal 101 determines the data volume threshold based on the resource size of CB-MSG3 configured in network device 102.
[0123] For example, the protocol stipulates a data volume threshold, and terminal 101 directly determines the data volume threshold based on the protocol.
[0124] For example, the protocol specifies several optional data volume thresholds. Based on the network device configuration, terminal 101 determines a data volume threshold that does not exceed the size of the CB-MSG3 resource from among the multiple optional data volume thresholds.
[0125] In some embodiments, terminal 101 may send CB-MSG3 to network device 102 if EDT and / or SDT are required.
[0126] In some embodiments, terminal 101 may implement itself to send CB-MSG3 to network device 102.
[0127] In some embodiments, terminal 101 may send CB-MSG3 to network device 102 at an event or time agreed upon by the protocol.
[0128] The above is merely an illustrative example, and this disclosure does not limit the timing or event that triggers terminal 101 to send CB-MSG3.
[0129] In step S2102, network device 102 sends a Media Access Control Packet Data Unit (MAC PDU) of CB-MSG4 to terminal 101.
[0130] In some embodiments, terminal 101 receives MAC PDU of CB-MSG4.
[0131] In some embodiments, where the MAC PDU includes response messages from at least one terminal, each response message is used to respond to a CB-MSG3 sent by one of the at least one terminals.
[0132] In some embodiments, the MAC PDU may include, but is not limited to, at least one of the following: a MAC header; a response message from at least one terminal; and padding items.
[0133] In one example, the MAC header may include at least one of the following MAC subheaders: a MAC subheader for backoff; a MAC subheader including a Contention Resolution Identity (CR-ID); or a MAC subheader including both the Contention Resolution Identity and the Radio Network Temporary Identity (RNTI).
[0134] In the event of a contention, network device 102 may include a MAC sub-header for backoff in the MAC header, so that terminal 101 may wait for a period of time before transmitting data again based on the indication of the MAC sub-header.
[0135] In this context, "MAC subheader including CR-ID" refers to a MAC subheader that includes only CR-ID. The name of the MAC subheader including CR-ID is not limited and can be used interchangeably with "MAC subheader including only CR-ID" or "MAC subheader including CR-ID but not RNTI".
[0136] The RNTI can be an RNTI provided by the network device 102 to the terminal 101, such as, but not limited to, at least one of the following: Cell-RNTI (C-RNTI), Configured Scheduling-RNTI (CS-RNTI), and Modulation and Coding Scheme-Cell-RNTI (MCS-C-RNTI).
[0137] Accordingly, taking any MAC subheader in the MAC header as an example, any MAC subheader is called the "first MAC subheader", and the first MAC subheader may include at least one of the following: a first type indicator field; a second type indicator field; an extended indicator field; and a reserved field.
[0138] In one example, the first type indicator field can be used to indicate that the first MAC subheader is a MAC subheader for backoff or a MAC subheader that includes a contention resolution identifier.
[0139] For example, the first type indicator field can be a T field, which can occupy at least one bit of the first MAC subheader. Taking a T field occupying 1 bit as an example, its bit value is set to a first value, which can be used to indicate that the current first MAC subheader is a MAC subheader used for backoff, and its bit value is set to a second value, which can be used to indicate that the current first MAC subheader includes the CR-ID. The first value can be 0 and the second value can be 1, or the first value can be 1 and the second value can be 0. This disclosure does not limit this.
[0140] In one example, the second type indicator field is used to indicate whether the first MAC subheader includes an RNTI.
[0141] For example, the second type of indication field can be called the T1 field. The T1 field can occupy at least one bit of the first MAC subheader. Taking the T1 field occupying 1 bit as an example, its bit value is set to a first value, which can be used to indicate that the current first MAC subheader includes RNTI. The bit value is set to a second value, which can be used to indicate that the current first MAC subheader does not include RNTI. The first value can be 0 and the second value can be 1, or the first value can be 1 and the second value can be 0. This disclosure does not limit this.
[0142] In one example, the extended indicator field can be used to indicate whether there are any extended information fields in the MAC header.
[0143] For example, the extended indicator field may occupy at least one bit in the first MAC subheader. Taking the extended indicator field occupying 1 bit as an example, its bit value is set to a first value, which can be used to indicate that there are extended information fields in the MAC header, such as an extended indicator field (E field), CR-ID field, T field, T1 field, etc., after the first MAC subheader. Its bit value is set to a second value, which can be used to indicate that there are no extended information fields in the MAC header, such as no MAC subheader after the current first MAC subheader, and / or a response message or padding item following the first MAC subheader. The first value can be 0 and the second value can be 1, or the first value can be 1 and the second value can be 0. This disclosure does not limit this.
[0144] For example, the extended (E) indicating field can be called the E field.
[0145] A reserved field is an information field that is temporarily reserved without any settings. A reserved field can also be called an R field.
[0146] In one example, if the first MAC subheader includes at least one of a first type indicator field, a second type indicator field, an extended indicator field, and a reserved field, the structure of the MAC subheader for backoff can be as shown in Figure 4A, including an extended indicator field (E field), a first type indicator field (T field), a reserved field (R field), and a backoff flag field. The backoff flag field is used to indicate the backoff flag (BI). The MAC subheader for backoff can occupy one octet (Oct).
[0147] In one example, if the first MAC subheader includes at least one of the first type indicator field, the second type indicator field, the extended indicator field, and the reserved field, the structure of the MAC subheader that only includes CR-ID can be as shown in Figure 4B, for example, including the extended indicator field (E field), the first type indicator field (T field), the second type indicator field (T1 field), the reserved field (R field), and at least one CR-ID field corresponding to the terminal. The MAC subheader that only includes CR-ID can occupy multiple octets (Oct).
[0148] In one example, when the first MAC subheader includes at least one of the first type indicator field, the second type indicator field, the extended indicator field, and the reserved field, the structure of the MAC subheader including CR-ID and RNTI can be as shown in Figure 4C, including the extended indicator field (E field), the first type indicator field (T field), the second type indicator field (T1 field), the reserved field (R field), the CR-ID field (corresponding to at least one terminal), and the RNTI field (corresponding to at least one terminal). The MAC subheader including CR-ID and RNTI can occupy multiple octets (Oct).
[0149] In one example, if the first MAC subheader includes at least one of the following: a first type indication field, a second type indication field, an extended indication field, and a reserved field, the MAC PDU may include at least one of the following: a contention resolution identifier (CR-ID) and an RNTI; a contention resolution identifier and a first type response message from at least one terminal.
[0150] The first type of response message can be a data transmission completion message or a Radio Resource Control (RRC) connection release message.
[0151] In other words, the MAC PDU can include CR-ID and RNTI at this time. The RNTI can be used by the network device 102 to schedule the terminal 101, and the terminal 101 does not need to switch to the connected state.
[0152] Alternatively, the MAC PDU may include a CR-ID and a response message, with the response message being the first type of response message mentioned above. In this case, terminal 101 does not need to switch to connected mode.
[0153] In one example, the response message from at least one terminal may also be referred to as a MAC Service Data Unit (SDU).
[0154] In one example, the structure of a MAC PDU is shown in Figure 4D, which may include a MAC header, m response messages (i.e., MAC MSG4), and padding items, which are optional.
[0155] It is understandable that m is a non-negative integer, such as 0, 1, 2, ...
[0156] For example, the number of response messages (i.e., MAC MSG4) included in the MAC PDU is equal to the number of MAC subheaders that only include CR-ID in the MAC header. In other words, the number m of response messages is not related to the number of MAC subheaders that include CR-ID and RNTI. For network device 102, if it sends CR-ID and RNTI, it will not send response messages (i.e., MAC MSG4, also known as Radio Resource Control messages) for the same terminal.
[0157] For example, in Figure 4D, there is a MAC subheader for backoff, a MAC subheader that includes only CR-ID, and a MAC subheader that includes both CR-ID and RNTI, wherein the total number of MAC subheaders that include only CR-ID and the total number of MAC subheaders that include both CR-ID and RNTI is n. m is equal to the number of MAC subheaders that include only CR-ID.
[0158] For example, the sequence number of the response message corresponding to terminal 101 is the same as the sequence number of the MAC subheader (which only includes the CR-ID) corresponding to the terminal in the MAC header. For instance, the MAC PDU includes response messages from m terminals, and the sequence number of the response message corresponding to the current terminal 101 is 2, that is, MAC MSG4#2 is the response message of terminal 101, used to respond to CB-MSG3 sent by the terminal. In the MAC header, the sequence number of the MAC subheader (which only includes the CR-ID) corresponding to terminal 101 is also #2.
[0159] In some embodiments, the MAC PDU may include, but is not limited to, at least one of the following: a MAC header; a response message from at least one terminal; and padding items.
[0160] In one example, the MAC header may include at least one of the following MAC subheaders: a MAC subheader for backoff; a MAC subheader including a Contention Resolution Identity (CR-ID); and a MAC subheader including both the Contention Resolution Identity and the RNTI. Specific details have been described in the foregoing embodiments and will not be repeated here.
[0161] In one example, taking any MAC subheader in the MAC header as an example, any MAC subheader is called the "second MAC subheader", which may include at least one of the following: a first type indicator field; a second type indicator field; a third type indicator field; an extended indicator field; and a reserved field.
[0162] In one example, the first type indicator field is used to indicate that the MAC subheader is a MAC subheader for backoff or a MAC subheader that includes a contention resolution identifier.
[0163] For example, the first type of indication field can be called the T field. The T field can occupy at least one bit of the second MAC subheader. Taking the T field occupying 1 bit as an example, its bit value is set to a first value, which can be used to indicate that the current second MAC subheader is a MAC subheader for backoff. The bit value is set to a second value, which can be used to indicate that the current second MAC subheader includes the CR-ID. The first value can be 0 and the second value can be 1, or the first value can be 1 and the second value can be 0. This disclosure does not limit this.
[0164] In one example, the second type indicator field is used to indicate whether the second MAC subheader includes an RNTI.
[0165] For example, the second type of indication field can be called the T1 field. The T1 field can occupy at least one bit of the second MAC subheader. Taking the T1 field occupying 1 bit as an example, its bit value is set to a first value, which can be used to indicate that the current second MAC subheader includes RNTI. The bit value is set to a second value, which can be used to indicate that the current second MAC subheader does not include RNTI. The first value can be 0 and the second value can be 1, or the first value can be 1 and the second value can be 0. This disclosure does not limit this.
[0166] In one example, the third type indicator field is used to indicate whether the second MAC subheader has an associated response message.
[0167] For example, the third type of indication field can be called the T2 field. The T2 field can occupy at least one bit of the second MAC subheader. Taking the T2 field occupying 1 bit as an example, its bit value is set to a first value, which can be used to indicate that the current second MAC subheader has an associated response message. The bit value is set to a second value, which can be used to indicate that the current second MAC subheader does not have an associated response message. The first value can be 0 and the second value can be 1, or the first value can be 1 and the second value can be 0. This disclosure does not limit this.
[0168] In one example, the extended indicator field can be used to indicate whether there are any extended information fields in the MAC header.
[0169] For example, the extended indicator field may occupy at least one bit of the second MAC subheader. Taking the extended indicator field occupying 1 bit as an example, its bit value is set to a first value, which can be used to indicate that there are still extended information fields in the MAC header, such as E field, CR-ID field, T field, T1 field, T2 field, etc. after the second MAC subheader. Its bit value is set to a second value, which can be used to indicate that there are no extended information fields in the MAC header, such as no MAC subheader after the current second MAC subheader, and / or, a response message or padding item follows the second MAC subheader. The first value can be 0, and the second value can be 1, or the first value can be 1 and the second value can be 0. This disclosure does not limit this.
[0170] For example, the extended indicator field can be called the E field.
[0171] Reserved fields are information fields that are temporarily retained without any settings. Reserved fields can be called R fields.
[0172] In one example, if the second MAC subheader includes at least one of the following: a first type indicator field, a second type indicator field, an extended indicator field, and a reserved field, the structure of the MAC subheader for backoff can be as shown in Figure 4E, including an extended indicator field (E field), a first type indicator field (T field), a reserved field (R field), and a backoff flag field. The backoff flag field is used to indicate the backoff flag (BI). It can occupy one octet (Oct).
[0173] In one example, if the second MAC subheader includes at least one of the first type indicator field, the second type indicator field, the third type indicator field, the extended indicator field, and the reserved field, the structure of the MAC subheader that only includes the CR-ID can be as shown in Figure 4F, for example, including the extended indicator field (E field), the first type indicator field (T field), the second type indicator field (T1 field), the third type indicator field (T2 field), the reserved field (R field), and at least one CR-ID field corresponding to the terminal, which can occupy multiple octets (Oct).
[0174] In one example, when the second MAC subheader includes at least one of the following: a first type indicator field, a second type indicator field, a third type indicator field, an extended indicator field, and a reserved field, the structure of the MAC subheader including CR-ID and RNTI can be as shown in Figure 4G, for example, including an extended indicator field (E field), a first type indicator field (T field), a second type indicator field (T1 field), a third type indicator field (T2 field), a reserved field (R field), a CR-ID field (corresponding to at least one terminal), and an RNTI field (corresponding to at least one terminal), which can occupy multiple octets (Oct).
[0175] In one example, the MAC PDU may include at least one of the following: a contention resolution identifier (CR-ID) and an RNTI; a first type of response message containing the contention resolution identifier and at least one terminal; and a second type of response message containing the contention resolution identifier, the RNTI, and at least one terminal.
[0176] The first type of response message can be a data transmission completion message or a Radio Resource Control (RRC) connection release message.
[0177] The second type of response message can be an RRC connection establishment message or an RRC connection recovery message.
[0178] In other words, the MAC PDU can include CR-ID and RNTI at this time. The RNTI can be used by the network device 102 to schedule the terminal 101, and the terminal 101 does not need to switch to the connected state.
[0179] Alternatively, the MAC PDU may include a CR-ID and a response message, with the response message being the first type of response message mentioned above. In this case, terminal 101 does not need to switch to connected mode.
[0180] Alternatively, the MAC PDU may include CR-ID, RNTI, and a response message from at least one terminal. The response message is the second type of response message mentioned above, in which case terminal 101 needs to switch to connected mode.
[0181] In one example, the response message from at least one terminal may also be referred to as a MAC Service Data Unit (SDU).
[0182] The structure of a MAC PDU is shown in Figure 4H, which may include a MAC header, m response messages (i.e., MAC MSG4) and padding items, which are optional.
[0183] It is understandable that m is a non-negative integer, such as 0, 1, 2, ...
[0184] For example, the number of response messages (i.e., MAC MSG4) included in the MAC PDU is the same as the sequence number of the first type MAC subheader corresponding to the terminal in the MAC header. The first type MAC subheader is the MAC subheader that the third type indication field (T2 field) indicates the associated response message.
[0185] For example, Figure 4H includes a MAC subheader for backoff, a MAC subheader containing only the CR-ID, and a MAC subheader containing both the CR-ID and RNTI, wherein the total number of MAC subheaders containing only the CR-ID and MAC subheaders containing both the CR-ID and RNTI is n. m is equal to the number of the first type of MAC subheaders. The first type of MAC subheader is the MAC subheader that indicates the associated response message in the third type indicator field (T2 field).
[0186] For example, the sequence number of the response message corresponding to terminal 101 is the same as the sequence number of the first type MAC subheader corresponding to the terminal in the MAC header. The first type MAC subheader is the MAC subheader that the third type indicator field (T2 field) indicates the associated response message. For example, the MAC PDU includes response messages from m terminals, and the sequence number of the response message corresponding to the current terminal 101 is 2, that is, MAC MSG4#2 is the response message of terminal 101, used to respond to CB-MSG3 sent by the terminal, and the sequence number of the first type MAC subheader corresponding to terminal 101 in the MAC header is also #2.
[0187] The above is merely an illustrative example, and this disclosure does not limit the structure of the MAC PDU.
[0188] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.
[0189] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transmit,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.
[0190] In some embodiments, “get,” “obtain,” “receive,” “transmit,” “bidirectional transmission,” and “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining through self-processing, or autonomous implementation, among other meanings.
[0191] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.
[0192] In some embodiments, the communication method involved in this disclosure may include at least one of steps S2101 to S2102. For example, step S2101 may be implemented as a standalone embodiment, step S2102 may be implemented as a standalone embodiment, and steps S2101 to S2102 may be implemented as standalone embodiments, but are not limited thereto.
[0193] In some embodiments, steps S2101 to S2102 are optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0194] In some embodiments, the execution order of steps S2101 to S2102 is not limited.
[0195] The above embodiments improve the reliability of data transmission, especially small data transmission, reduce connection establishment time and signaling overhead, and help reduce data transmission latency.
[0196] Figure 3A is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3A, the present disclosure relates to a communication method that can be executed by a terminal 101, and the method includes:
[0197] Step S3101: Send CB-MSG3.
[0198] In some embodiments, terminal 101 sends CB-MSG3 to network device 102.
[0199] In some embodiments, network device 102 receives CB-MSG3.
[0200] In some embodiments, the CB-MSG3 carries a small amount of data. The amount of this data may be less than or equal to a data volume threshold, which may be determined based on a predefined method and / or the configuration of network device 102.
[0201] In some embodiments, optional implementations of step S3101 can be found in optional implementations of step S2101 in FIG2 and other related parts in the embodiments involved in FIG2, which will not be repeated here.
[0202] Step S3102: Obtain the MAC PDU of CB-MSG4.
[0203] In some embodiments, the MAC PDU includes response messages from at least one terminal, each response message being used to respond to a CB-MSG3 sent by one of the at least one terminals.
[0204] In some embodiments, optional implementations of step S3102 can be found in optional implementations of step S2102 in FIG2 and other related parts in the embodiments involved in FIG2, which will not be repeated here.
[0205] In some embodiments, terminal 101 receives MAC PDU of CB-MSG4 sent by network device 101, but is not limited thereto. Terminal 101 may also receive MAC PDU of CB-MSG4 sent by other entities, such as relay devices or other devices. In this case, step S3101 can be omitted.
[0206] In some embodiments, terminal 101 obtains the MAC PDU of CB-MSG4 as specified by the protocol, in which step S3102 is omitted.
[0207] In some embodiments, terminal 101 obtains the MAC PDU of CB-MSG4 from the upper layer(s), in which case step S3102 is omitted.
[0208] In some embodiments, the terminal 101 processes the data to obtain the MAC PDU of CB-MSG4, in which step S3102 is omitted.
[0209] In some embodiments, the terminal 101 autonomously implements the function indicated by the MAC PDU of CB-MSG4, or the above function is the default or default, in which case step S3102 is omitted.
[0210] In some embodiments, steps S3101 to S3102 are optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0211] In some embodiments, the execution order of steps S3101 to S3102 is not limited.
[0212] The above embodiments improve the reliability of data transmission, especially small data transmission, reduce connection establishment time and signaling overhead, and help reduce data transmission latency.
[0213] Figure 3B is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3B, the present disclosure relates to a communication method that can be executed by a network device 102, and the method includes:
[0214] Step S3201: Obtain CB-MSG3.
[0215] In some embodiments, the CB-MSG3 carries a small amount of data. The amount of this data may be less than or equal to a data volume threshold, which may be determined based on a predefined method and / or the configuration of network device 102.
[0216] In some embodiments, optional implementations of step S3201 can be found in optional implementations of step S2101 in FIG2 and other related parts in the embodiments involved in FIG2, which will not be repeated here.
[0217] In some embodiments, network device 101 receives CB-MSG3 sent by terminal 101, but is not limited thereto. Network device 101 may also receive CB-MSG3 sent by other entities, such as relay devices or other devices. In this case, step S3201 may be omitted.
[0218] In some embodiments, network device 101 obtains CB-MSG3 as specified by the protocol, in which case step S3201 is omitted.
[0219] In some embodiments, network device 101 obtains CB-MSG3 from upper layer(s), in which case step S3201 is omitted.
[0220] In some embodiments, network device 101 processes data to obtain CB-MSG3, in which step S3201 is omitted.
[0221] In some embodiments, the network device 101 autonomously implements the function indicated by CB-MSG3, or the above function is default or default, in which case step S3201 is omitted.
[0222] Step S3202: Send the MAC PDU of CB-MSG4.
[0223] In some embodiments, network device 102 sends CB-MSG4 MAC PDU to terminal 101.
[0224] In some embodiments, terminal 101 receives MAC PDU of CB-MSG4.
[0225] In some embodiments, the MAC PDU includes response messages from at least one terminal, each response message being used to respond to a CB-MSG3 sent by one of the at least one terminals.
[0226] In some embodiments, optional implementations of step S3202 can be found in optional implementations of step S2102 in FIG2 and other related parts in the embodiments involved in FIG2, which will not be repeated here.
[0227] In some embodiments, steps S3201 to S3202 are optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0228] In some embodiments, the execution order of steps S3201 to S3202 is not limited.
[0229] The above embodiments improve the reliability of data transmission, especially small data transmission, reduce connection establishment time and signaling overhead, and help reduce data transmission latency.
[0230] The above process is further illustrated with examples below.
[0231] In this embodiment of the disclosure, the structure of CB-MSG4 MAC PDU and MAC subheader is designed.
[0232] Example 1, MAC header of CB-MSG4:
[0233] A CB-MSG4 MAC header may contain a MAC subheader for backoff, one or more MAC subheaders that only include the contention resolution ID (CR-ID), and one or more MAC subheaders that include both the CR-ID and RNTI.
[0234] The structure of the MAC subheader used for backoff can be as shown in Figure 4A, for example.
[0235] The structure of the MAC subheader, which includes only the CR-ID, can be as shown in Figure 4B, for example.
[0236] The structure of the MAC subheader, which includes CR-ID and RNTI, can be as shown in Figure 4C, for example.
[0237] The E field is an extension indicator field used to indicate whether there are any more fields in the MAC header. For example, setting it to 1 means that the MAC subheader is followed by at least one E, T, or CR-ID field, while setting it to zero means that the MAC subheader is not followed by another MAC subheader and / or is followed by a MAC MSG4 or padding.
[0238] The T field is a (first) type indicator field, for example, setting it to 0 indicates a MAC subheader used for backoff, and setting it to 1 indicates a MAC subheader containing the CR-ID.
[0239] The T1 field is a (second) type indicator field. For example, setting it to 0 means that RNTI is not included, and setting it to 0 means that RNTI is included in the MAC subheader.
[0240] The R field is a reserved bit field.
[0241] The structure of a MAC PDU, which includes the MAC header and the response message MAC MSG4, is shown in Figure 4D.
[0242] A MAC PDU can contain a MAC header, m MAC MSG4s, and optional padding. The MAC MSG4s contain MAC SDUs (e.g., RRC messages).
[0243] In Figure 4D, the number of MAC MAC4 messages is m, which is equal to the number of MAC subheaders in the MAC header that only include the CR-ID, i.e., it is unrelated to MAC subheaders that include both the CR-ID and RNTI. This is because if a network device sends a MAC subheader that includes both the CR-ID and RNTI to a terminal, it will not send a MAC MSG4 (i.e., an RRC message) to that terminal.
[0244] Example 2, MAC header of CB-MSG4:
[0245] A CB-MSG4 MAC header may contain a MAC subheader for backoff, one or more MAC subheaders that only include the CR-ID, and one or more MAC subheaders that include both the CR-ID and the RNTI.
[0246] The structure of the MAC subheader used for backoff can be as shown in Figure 4E, for example.
[0247] The structure of the MAC subheader that includes only the CR-ID can be as shown in Figure 4F, for example.
[0248] The structure of the MAC subheader, including CR-ID and RNTI, can be as shown in Figure 4G.
[0249] The E field is an extension indicator field used to indicate whether there are more fields in the MAC header. For example, setting it to 1 means that the MAC subheader is followed by at least one E, T, or CR-ID field, while setting it to zero means that there is no more MAC subheader following the MAC subheader, and / or that the MAC subheader is followed by a MAC MSG4 or padding.
[0250] The T field is a (first) type indicator field, for example, setting it to 0 indicates a MAC subheader used for backoff, and setting it to 1 indicates a MAC subheader containing the CR-ID.
[0251] The T1 field is a (second) type indicator field. For example, setting it to 0 means that RNTI is not included, and setting it to 0 means that RNTI is included in the MAC subheader.
[0252] The T2 field is a (third) type indicator field. For example, setting it to 0 means that the MAC subheader has no associated MAC MSG4 (i.e., RRC message), and setting it to 1 means that the MAC header has an associated MAC MSG4 (i.e., RRC message).
[0253] The R field is a reserved bit field.
[0254] The structure of a MAC PDU, which includes the MAC header and MAC MSG4, is shown in Figure 4H.
[0255] A MAC PDU can contain a MAC header, m MAC MSG4s, and optional padding. The MAC MSG4s contain MAC SDUs (e.g., RRC messages).
[0256] In Figure 4H, the number m of MAC MAC4 corresponds to the number of MAC subheaders with T2 field set to 1 in the MAC header, and the order is also sequential.
[0257] The response message sent by a network device to a terminal that has successfully resolved a contention issue may include:
[0258] 1) CR-ID and C-RNTI; or
[0259] 2) CR-ID and MAC MSG4 (i.e., containing RRC messages, such as EDT completion messages or connection release messages); or
[0260] 3) CR-ID, C-RNTI, and MAC MSG4 (i.e., containing RRC messages, such as connection establishment messages or connection recovery messages).
[0261] Among them, MAC MSG4 can be understood as MAC SDU.
[0262] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.
[0263] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.
[0264] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).
[0265] Figure 5A is a schematic diagram of the structure of a terminal according to an embodiment of this disclosure. The terminal 5100 is used to perform any of the above methods. In some embodiments, as shown in Figure 5A, the terminal 5100 may include a transceiver module 5101.
[0266] In some embodiments, the transceiver module 5101 is configured to send a contention-based message 3 (CB-MSG3) to a network device, wherein the CB-MSG3 carries data; and to receive a media access control packet data unit (MAC PDU) of a contention-based message 4 (CB-MSG4) sent by the network device; wherein, if the MAC PDU includes a response message from at least one terminal, each response message is used to respond to the CB-MSG3 sent by one of the at least one terminals.
[0267] Optionally, the transceiver module 5101 is used to perform at least one of the communication steps (such as step S2101, step S2102, but not limited thereto) performed by the terminal 5100 in any of the above methods, which will not be described in detail here.
[0268] Figure 5B is a schematic diagram of the structure of a network device according to an embodiment of this disclosure. The network device 5200 is used to perform any of the above methods. In some embodiments, as shown in Figure 5B, the network device 5200 may include a transceiver module 5201.
[0269] In some embodiments, the transceiver module 5201 is configured to receive a contention-based message 3 (CB-MSG3) sent by a terminal; wherein the CB-MSG3 carries data; and to send a contention-based message 4 (CB-MSG4) of Media Access Control Packet Data Unit (MAC PDU) to the terminal; wherein, if the MAC PDU includes a response message from at least one terminal, each response message is used to respond to the CB-MSG3 sent by one of the at least one terminals.
[0270] Optionally, the transceiver module 5201 is used to perform at least one of the communication steps (such as step S2101, step S2102, but not limited thereto) performed by the network device 5200 in any of the above methods, which will not be described in detail here.
[0271] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.
[0272] Alternatively, the transceiver module can be interchanged with the transceiver.
[0273] Figure 6A is a schematic diagram of the structure of the communication device 6100 proposed in an embodiment of this disclosure. The communication device 6100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 6100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.
[0274] As shown in Figure 6A, the communication device 6100 is used to execute any of the above methods. In some embodiments, the communication device 6100 includes one or more processors 6101. The processor 6101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 6100 is used to execute any of the above methods. Optionally, one or more processors 6101 are used to invoke instructions to cause the communication device 6100 to execute any of the above methods.
[0275] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs at least one of the communication steps (e.g., steps S2101, S2102, but not limited thereto) in the above method, such as sending and / or receiving, and the processor 6101 performs at least one of the other steps. In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, sending unit, transmitter, sending circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.
[0276] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data and / or instructions. Optionally, one or more processors 6101 are used to invoke instructions stored in the memory 6103 to cause the communication device 6100 to perform any of the above methods. Optionally, all or part of the memory 6103 may also be located outside the communication device 6100. In an optional embodiment, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuit 6104 is connected to the memory 6103 and can be used to receive data and / or instructions from the memory 6103 or other devices, and can be used to send data and / or instructions to the memory 6103 or other devices. For example, the interface circuit 6104 can read data and / or instructions stored in the memory 6103 and send the data and / or instructions to the processor 6101.
[0277] The communication device 6100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 6100 described in this disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited by FIG. 6A. The communication device may be a standalone device or a part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.
[0278] Figure 6B is a schematic diagram of the structure of chip 6200 according to an embodiment of this disclosure. For cases where the communication device 6100 can be a chip or a chip system, please refer to the schematic diagram of chip 6200 shown in Figure 6B, but it is not limited thereto.
[0279] Chip 6200 includes one or more processors 6201. Chip 6200 is used to perform any of the methods described above.
[0280] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data and / or instructions. Optionally, all or part of the memories 6203 may be located outside of chip 6200. Optionally, interface circuit 6202 is connected to memory 6203, and interface circuit 6202 can be used to receive data and / or instructions from memory 6203 or other devices, and interface circuit 6202 can be used to send data and / or instructions to memory 6203 or other devices. For example, interface circuit 6202 can read data and / or instructions stored in memory 6203 and send the data and / or instructions to processor 6201.
[0281] In some embodiments, the interface circuit 6202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps S2101, S2102, but not limited thereto). For example, the interface circuit 6202 performing the communication steps such as sending and / or receiving in the above-described method means that the interface circuit 6202 performs data and / or instruction interaction between the processor 6201, the chip 6200, the memory 6203, or the transceiver device. In some embodiments, the processor 6201 performs at least one of the other steps.
[0282] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.
[0283] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.
[0284] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.
[0285] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.
[0286] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.
Claims
1. A communication method, characterized in that, The method is executed by a terminal, and the method includes: Send a contention-based message 3 (CB-MSG3) to the network device; wherein the CB-MSG3 carries data; The network device receives a contention-based message 4 (CB-MSG4) Media Access Control Packet Data Unit (MAC PDU); wherein, if the MAC PDU includes a response message from at least one terminal, each response message is used to respond to a CB-MSG3 sent by one of the at least one terminals.
2. The method according to claim 1, characterized in that, The MAC PDU includes at least one of the following: MAC header; A response message from at least one terminal; Fill in the blanks.
3. The method according to claim 2, characterized in that, The MAC header includes at least one of the following MAC sub-headers: MAC subheader used for backoff; Includes the MAC subheader for contention resolution; This includes the MAC subheader containing the Contention Resolution Identifier and the Radio Network Temporary Identifier (RNTI).
4. The method according to claim 3, characterized in that, The first MAC sub-header is any one of the MAC sub-headers, and the first MAC sub-header includes at least one of the following: A first type of indication field is used to indicate that the first MAC subheader is a MAC subheader for backoff or a MAC subheader that includes a contention resolution identifier; The second type of indication field is used to indicate whether the first MAC subheader includes an RNTI; An extended indication field, which is used to indicate whether there is an extended information field in the MAC header; Reserved fields.
5. The method according to claim 4, characterized in that, The MAC PDU includes at least one of the following: Competition resolution identifier and RNTI; The contention resolution identifier and at least one terminal's first type of response message.
6. The method according to claim 4 or 5, characterized in that, The number of response messages included in the MAC PDU is equal to the number of MAC subheaders including a contention resolution flag in the MAC header; and / or The sequence number of the response message corresponding to the terminal is the same as the sequence number of the MAC sub-header, which includes the contention resolution identifier, corresponding to the terminal in the MAC header.
7. The method according to claim 3, characterized in that, The second MAC subheader is any one of the MAC subheaders, and the second MAC subheader includes at least one of the following: A first type of indication field is used to indicate that the second MAC subheader is a MAC subheader for backoff or a MAC subheader that includes a contention resolution identifier; The second type of indication field is used to indicate whether the second MAC subheader includes RNTI; A third type of indication field is used to indicate whether the second MAC subheader has an associated response message; An extended indication field, which is used to indicate whether there is an extended information field in the MAC header; Reserved fields.
8. The method according to claim 7, characterized in that, The MAC PDU includes at least one of the following: Competition resolution identifier and RNTI; The contention resolution identifier and at least one terminal's first type of response message; The contention resolves the identifier, RNTI, and a second type of response message from at least one terminal.
9. The method according to claim 7 or 8, characterized in that, The number of response messages included in the MAC PDU is equal to the number of first-type MAC sub-headers included in the MAC header; and / or The sequence number of the response message corresponding to the terminal is the same as the sequence number of the first type of MAC sub-header corresponding to the terminal in the MAC header; The first type of MAC subheader is the MAC subheader of the associated response message indicated by the third type of indicator field.
10. The method according to claim 5 or 8, characterized in that, The first type of response message is any one of the following: Data transmission complete message; Radio Resource Control (RRC) connection release message.
11. The method according to any one of claims 8-10, characterized in that, The second type of response message is any one of the following: RRC connection establishment message; RRC connection recovery message.
12. A communication method, characterized in that, The method is performed by a network device, and the method includes: The receiving terminal sends a contention-based message 3 (CB-MSG3); wherein the CB-MSG3 carries data; The Media Access Control Packet Data Unit (MAC PDU) based on contention-based message 4 (CB-MSG4) is sent to the terminal; wherein, if the MAC PDU includes a response message from at least one terminal, each response message is used to respond to CB-MSG3 sent by one of the at least one terminals.
13. The method according to claim 12, characterized in that, The MAC PDU includes at least one of the following: MAC header; A response message from at least one terminal; Fill in the blanks.
14. The method according to claim 13, characterized in that, The MAC header includes at least one of the following MAC sub-headers: MAC subheader used for backoff; Includes the MAC subheader for contention resolution; This includes the MAC subheader containing the Contention Resolution Identifier and the Radio Network Temporary Identifier (RNTI).
15. The method according to claim 14, characterized in that, The first MAC sub-header is any one of the MAC sub-headers, and the first MAC sub-header includes at least one of the following: A first type of indication field is used to indicate that the first MAC subheader is a MAC subheader for backoff or a MAC subheader that includes a contention resolution identifier; The second type of indication field is used to indicate whether the first MAC subheader includes an RNTI; An extended indication field, which is used to indicate whether there is an extended information field in the MAC header; Reserved fields.
16. The method according to claim 15, characterized in that, The MAC PDU includes at least one of the following: Competition resolution identifier and RNTI; The contention resolution identifier and at least one terminal's first type of response message.
17. The method according to claim 15 or 16, characterized in that, The number of response messages included in the MAC PDU is equal to the number of MAC subheaders including a contention resolution flag in the MAC header; and / or The sequence number of the response message corresponding to the terminal is the same as the sequence number of the MAC sub-header, which includes the contention resolution identifier, corresponding to the terminal in the MAC header.
18. The method according to claim 14, characterized in that, The second MAC subheader is any one of the MAC subheaders, and the second MAC subheader includes at least one of the following: A first type of indication field is used to indicate that the second MAC subheader is a MAC subheader for backoff or a MAC subheader that includes a contention resolution identifier; The second type of indication field is used to indicate whether the second MAC subheader includes RNTI; A third type of indication field is used to indicate whether the second MAC subheader has an associated response message; An extended indication field, which is used to indicate whether there is an extended information field in the MAC header; Reserved fields.
19. The method according to claim 18, characterized in that, The MAC PDU includes at least one of the following: Competition resolution identifier and RNTI; The contention resolution identifier and at least one terminal's first type of response message; The contention resolves the identifier, RNTI, and a second type of response message from at least one terminal.
20. The method according to claim 18 or 19, characterized in that, The number of response messages included in the MAC PDU is equal to the number of first-type MAC sub-headers included in the MAC header; and / or The sequence number of the response message corresponding to the terminal is the same as the sequence number of the first type of MAC sub-header corresponding to the terminal in the MAC header; The first type of MAC subheader is the MAC subheader of the associated response message indicated by the third type of indicator field.
21. The method according to claim 16 or 19, characterized in that, The first type of response message is any one of the following: Data transmission complete message; Radio Resource Control (RRC) connection release message.
22. The method according to any one of claims 19-21, characterized in that, The second type of response message is any one of the following: RRC connection establishment message; RRC connection recovery message.
23. A terminal, characterized in that, include: The transceiver module is configured to send contention-based message 3 (CB-MSG3) to the network device; wherein the CB-MSG3 carries data; The transceiver module is further configured to receive a contention-based message 4 (CB-MSG4) Media Access Control Packet Data Unit (MAC PDU) sent by the network device; wherein, if the MAC PDU includes a response message from at least one terminal, each response message is used to respond to a CB-MSG3 sent by one of the at least one terminals.
24. A network device, characterized in that, include: The transceiver module is configured to receive contention-based message 3 (CB-MSG3) sent by the terminal; wherein the CB-MSG3 carries data. The transceiver module is further configured to send a contention-based message 4 (CB-MSG4) Media Access Control Packet Data Unit (MAC PDU) to the terminal; wherein, if the MAC PDU includes a response message from at least one terminal, each response message is used to respond to a CB-MSG3 sent by one of the at least one terminals.
25. A terminal, characterized in that, include: One or more processors; The processor is used to execute the method according to any one of claims 1-11.
26. A network device, characterized in that, include: One or more processors; The processor is used to execute the communication method according to any one of claims 12-22.
27. A communication system, characterized in that, include: A terminal configured to implement the communication method according to any one of claims 1-11; A network device configured to implement the communication method according to any one of claims 12-22.
28. A storage medium storing instructions, characterized in that, When the instruction is executed on the communication device, it causes the communication device to perform the communication method as described in any one of claims 1-11 or 12-22.
29. A computer program product, comprising a computer program, characterized in that, When executed by a processor, the computer program is used to implement the communication method according to any one of claims 1-11 or 12-22.
