Communication method and apparatus

Abstract

Embodiments of the present application relate to the field of communications, and provide a communication method and apparatus, capable of ensuring that a device (e.g., a first device) performs failure processing in time, thereby improving a random access success rate or a data transmission success rate. The method comprises: a first device transmitting a first D2R message to a reader; and receiving a first R2D message from the reader, the first R2D message being used for instructing the first device to perform random access again, and / or the first R2D message being used for instructing the first device to transmit a second D2R message, the message type of the second D2R message being the same as that of the first D2R message.

Description

A communication method and apparatus

[0001] This application claims priority to Chinese Patent Application No. 202510390832.7, filed with the State Intellectual Property Office of China on March 28, 2025, entitled "A Method, Terminal and System for Failure Indication", and Chinese Patent Application No. 202510600526.1, filed with the State Intellectual Property Office of China on May 9, 2025, entitled "A Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more particularly to a communication method and apparatus. Background Technology

[0003] In an ambient internet of things (A-IoT) system, a device (e.g., a device) can attempt to establish a connection with a reader through random access.

[0004] Random access methods can include contention-based random access (CBRA) and contention-free random access (CFRA). CBRA typically includes three key access steps, while CFRA includes one. However, both CBRA and CFRA can experience access step failures; how to handle these failures requires further discussion. Summary of the Invention

[0005] This application provides a communication method and apparatus that can ensure that devices (e.g., a first device) can handle failures in a timely manner, thereby improving the success rate of random access or data transmission.

[0006] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0007] In a first aspect, a communication method is provided, applied to a first device, the method comprising: sending a first D2R message to a reader; receiving a first R2D message from the reader, the first R2D message being used to instruct the first device to re-perform random access, and / or, the first R2D message being used to instruct the first device to send a second D2R message, the second D2R message having the same message type as the first D2R message.

[0008] Based on the method provided in the embodiments of this application, the first device (e.g., Device) can re-enter random access based on the reader's instruction (indicated by the first R2D message), or send a second D2R message (i.e., retransmit the first D2R message), which can ensure that the first device performs failure processing in a timely manner (e.g., failure to send the first D2R message), thereby improving the success rate of random access or data transmission.

[0009] In one possible implementation, the message type of the first R2D message is a NACK message; or, the message type of the first R2D message is an R2D data message, and the first R2D message includes first information indicating that the first R2D message is a NACK message. This eliminates the need to design different message types for different exceptions, reducing message design complexity.

[0010] In one possible implementation, the first R2D message further includes second information, which is used to instruct at least one device, including the first device. That is, the second information can be used to instruct at least one device to re-enter random access, or to send a second D2R message (i.e., retransmit the failed D2R message), thus saving signaling overhead.

[0011] In one possible implementation, the second information includes at least one first index, which is an access layer index AS ID or a random number.

[0012] In one possible implementation, the first R2D message includes third information, which indicates first time-domain resources and / or first frequency-domain resources. The first time-domain resources include time-domain resources for at least one device to transmit D2R messages, and the first frequency-domain resources include frequency-domain resources for at least one device to transmit D2R messages. The at least one device includes the first device. That is, the first time-domain resources and / or the first frequency-domain resources can be used to instruct at least one device to re-enter random access, or to send a second D2R message (i.e., retransmit the failed D2R message), thus saving signaling overhead.

[0013] In one possible implementation, the method further includes: if the first R2D message instructs the first device to re-enter random access, the first device stops the first process; wherein stopping the first process includes at least one of the following: stopping listening to R2D messages, stopping listening to subsequent paging messages, and releasing first information, the first information including a first random number or access layer index (AS ID). This avoids resource waste and saves device power consumption.

[0014] In one possible implementation, the first R2D message also includes fourth information, which instructs the first device to re-establish random access, or instructs the first device to send a second D2R message. In this way, the fourth information can instruct the device to re-establish random access or send a second D2R message, eliminating the need for designing too many message types and minimizing the amount of MT required, thus reducing message design complexity.

[0015] In one possible implementation, the fourth information is also used to indicate whether the first R2D message includes a fifth information, which indicates the number of bytes / bits the reader has successfully received. In this way, the first device can begin transmission based on the fifth information after the number of bytes / bits successfully received by the reader, saving communication bandwidth and transmission time, and improving the efficiency and flexibility of data transmission.

[0016] In one possible implementation, the first R2D message also includes a sixth piece of information, which indicates whether segmented retransmission is necessary. This allows the first device to determine whether segmented retransmission is required based on the sixth piece of information, improving data transmission efficiency and flexibility.

[0017] In one possible implementation, the sixth information is also used to indicate whether the first R2D message includes the fifth information, which indicates the number of bytes / bits successfully received by the reader / writer. In this way, the first device can begin transmission based on the fifth information after the number of bytes / bits successfully received by the reader / writer, saving communication bandwidth and transmission time, and improving the efficiency and flexibility of data transmission.

[0018] In one possible implementation, the first D2R message includes MSG1, MSG3, or a higher-level data transmission message.

[0019] In one possible implementation, when the first D2D message is an MSG3 or a higher-layer data transmission message, the first R2D message includes fifth information, which indicates the number of bytes / bits successfully received by the reader. It is understood that since MSG3 or higher-layer data transmission messages typically carry service data, adding fifth information to the first R2D message to indicate the number of bytes successfully received by the reader (the number of bytes corresponding to the service data) can avoid duplicate data transmission.

[0020] In one possible implementation, whether the content of the second D2R message is the same as that of the first D2R message is based on protocol specifications (protocol predefined) or network instructions.

[0021] In one possible implementation, the first R2D message further includes resource scheduling information, which indicates the time-domain and / or frequency-domain resources used to send the second D2R message. In this way, the first device can send the second D2R message based on the time-domain and / or frequency-domain resources indicated by the resource scheduling information, thereby improving resource utilization and ensuring communication quality.

[0022] Secondly, a communication method is provided for use in a reader / writer, the method comprising: receiving a first D2R message from a first device; sending a first R2D message to the first device, the first R2D message being used to instruct the first device to re-perform random access; and / or, the first R2D message being used to instruct the first device to send a second D2R message, the second D2R message having the same message type as the first D2R message.

[0023] In one possible implementation, the message type of the first R2D message is a NACK message; or, the message type of the first R2D message is an R2D data message, and the first R2D message includes first information, which is used to indicate that the first R2D message is a NACK message.

[0024] In one possible implementation, the first R2D message further includes second information for indicating at least one device, which includes the first device.

[0025] In one possible implementation, the second information includes at least one first index, which is an access layer index AS ID or a random number.

[0026] In one possible implementation, the first R2D message includes third information for indicating first time-domain resources and / or first frequency-domain resources. The first time-domain resources include time-domain resources for at least one device to transmit D2D messages, and the first frequency-domain resources include frequency-domain resources for at least one device to transmit D2D messages. The at least one device includes the first device.

[0027] In one possible implementation, the first R2D message may also include fourth information, which instructs the first device to re-enter random access, or the fourth information instructs the first device to send a second D2R message.

[0028] In one possible implementation, the fourth information is also used to indicate whether the first R2D message includes a fifth information, which indicates the number of bytes / bits that the reader has successfully received.

[0029] In one possible implementation, the first R2D message also includes a sixth message, which indicates whether segmented retransmission is required.

[0030] In one possible implementation, the sixth information is also used to indicate whether the first R2D message includes the fifth information, which is used to indicate the number of bytes / bits that the reader has successfully received.

[0031] In one possible implementation, the first D2R message includes MSG1, MSG3, or a higher-level data transmission message.

[0032] In one possible implementation, if the first D2R message is an MSG3 or a higher-layer data transmission message, the first R2D message includes a fifth message indicating the number of bytes / bits that the reader has successfully received.

[0033] In one possible implementation, whether the content of the second D2R message is the same as that of the first D2R message is based on protocol specifications or network instructions.

[0034] In one possible implementation, the first R2D message also includes resource scheduling information, which indicates the time-domain and / or frequency-domain resources used to send the second D2R message.

[0035] Thirdly, a communication device is provided, comprising a transceiver module. The transceiver module is configured to: send a first D2R message to a reader / writer; receive a first R2D message from the reader / writer, the first R2D message being used to instruct a first device to re-enter random access; and / or, the first R2D message being used to instruct the first device to send a second D2R message, the second D2R message having the same message type as the first D2R message.

[0036] Fourthly, a communication device is provided, comprising a transceiver module. The transceiver module is configured to: receive a first D2R message from a first device; send a first R2D message to the first device, the first R2D message instructing the first device to re-enter random access; and / or, the first R2D message instructing the first device to send a second D2R message, the second D2R message having the same message type as the first D2R message.

[0037] The third and fourth aspects are the implementation on the device side, which correspond to the first and second aspects. The explanations, supplements, and descriptions of the beneficial effects of the first and second aspects also apply to the third and fourth aspects, and will not be repeated here.

[0038] Fifthly, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the method in any possible implementation of the first aspect described above. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0039] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0040] In another implementation, the communication device is a chip configured in the first device. When the communication device is a chip configured in the first device, the communication interface can be an input / output interface.

[0041] In a sixth aspect, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the method in any possible implementation of the second aspect described above. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0042] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0043] In a seventh aspect, a processor is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute a method in any possible implementation of any aspect.

[0044] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0045] Eighthly, a communication device is provided, including a processor and a memory. The processor is used to read instructions stored in the memory, receive signals via a receiver, and transmit signals via a transmitter to execute the method in any possible implementation of any of the preceding aspects.

[0046] Optionally, the processor may be one or more, and the memory may be one or more.

[0047] Ninthly, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code or instructions), which, when the computer program is run, causes a computer to perform a method in any possible implementation of any of the above aspects.

[0048] In a tenth aspect, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform the method in any possible implementation of any of the above aspects.

[0049] Eleventhly, embodiments of this application provide a chip system including one or more processors for calling and executing instructions stored in memory, causing the methods in any of the above aspects or possible implementations to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0050] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0051] In a twelfth aspect, a communication system is provided, including the aforementioned first device (e.g., Device) and a reader. Optionally, the communication system may further include other devices that communicate with the first device and / or the reader. Attached Figure Description

[0052] Figure 1 is a schematic diagram of a communication system provided in an embodiment of this application;

[0053] Figure 2A is a schematic diagram of an external carrier source providing a carrier signal according to an embodiment of this application;

[0054] Figure 2B is a schematic diagram of another type of external carrier source providing a carrier signal according to an embodiment of this application;

[0055] Figure 3 is a schematic diagram of a CBRA provided in an embodiment of this application;

[0056] Figure 4 is a schematic diagram of signal interaction provided in an embodiment of this application;

[0057] Figure 5A is a schematic diagram of the format of a first R2D message provided in an embodiment of this application;

[0058] Figure 5B is a schematic diagram of the format of a first R2D message provided in an embodiment of this application;

[0059] Figure 5C is a schematic diagram of the format of a first R2D message provided in an embodiment of this application;

[0060] Figure 5D is a schematic diagram of the format of a first R2D message provided in an embodiment of this application;

[0061] Figure 5E is a schematic diagram of the format of a first R2D message provided in an embodiment of this application;

[0062] Figure 5F is a schematic diagram of the format of a first R2D message provided in an embodiment of this application;

[0063] Figure 5G is a schematic diagram of a paging cycle provided in an embodiment of this application;

[0064] Figure 6 is a schematic diagram of another signal interaction provided in an embodiment of this application;

[0065] Figure 7 is a schematic diagram of another signal interaction provided in an embodiment of this application;

[0066] Figure 8 is a schematic diagram of another signal interaction provided in an embodiment of this application;

[0067] Figure 9 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0068] Figure 10 is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0069] The technical solutions provided in this application can be applied to various communication systems, such as: A-IoT systems, Global System for Mobile Communications (GSM) systems, General Packet Radio Service (GPRS), Wireless Local Area Network (WLAN), Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, sidelink communication systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication systems, non-terrestrial network (NTN) communication systems, 5th generation (5G) mobile communication systems, or new radio access technology (NR). Among these, 5G mobile communication systems can include non-standalone (NSA) and / or standalone (SA) networking. The technical solutions provided in this application can also be applied to future communication systems. This application does not limit the scope of these applications.

[0070] Figure 1 is a schematic diagram of a communication system 100 according to an embodiment of this application. The communication system 100 may include a reader 110 and a device 120. The reader 110 and the device 120 can communicate via a wireless channel. Figure 1 illustrates a device exemplarily. Optionally, the communication system 100 may also include more devices.

[0071] In the embodiments of this application, the channel through which the Reader sends data to the Device is called the R2D channel (similar to the downlink channel in a cellular communication system), and the channel through which the Device sends data to the Reader is called the D2R channel (similar to the uplink channel in a cellular communication system).

[0072] For example, the channel between Reader 110 and Device 120 can be a Physical Reader-to-Device channel (PRDCH). The channel between Reader 110 and Device 120 can be a Physical Device-to-Reader channel (PDRCH).

[0073] The Reader in this application includes, but is not limited to, base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs), next-generation NodeBs (gNBs) in 5G mobile communication systems, access network equipment or modules of access network equipment in open RAN (ORAN) systems, satellites in NTN communication systems, base stations in future mobile communication systems, or access nodes in WiFi systems. A Reader can also be a module or unit capable of implementing some functions of a base station. A Reader can be a macro base station, micro base station, indoor station, relay node, donor node, or a radio controller in a cloud radio access network (CRAN) scenario. Optionally, a Reader can also be a server, wearable device, or vehicle-mounted equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). Multiple Readers in a communication system can be the same type of base station or different types of base stations. Base stations can communicate with devices directly or through relay stations. The device can communicate with multiple base stations using different access technologies. The embodiments of this application do not limit the specific technology or device form employed by the access network device. In this application, the access network device is referred to as a network device.

[0074] The device in this application can be a wireless device capable of receiving network device scheduling and instruction information. The wireless device can be a device providing voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. For example, the device can communicate with one or more core networks or the Internet via a radio access network (RAN). The device can also be referred to as a Device, terminal, user equipment (UE), mobile station, mobile terminal, etc. The device can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), ambient IoT (A-IoT), ultra-reliable low-latency communication (URLLC), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, or satellite communication, etc. The device can be an IoT device. IoT devices can include A-IoT devices. Devices can also be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, aircraft (such as drones, helicopters, and airplanes), hot air balloons, ships, robots, robotic arms, or smart home devices, etc. The embodiments of this application do not limit the form of the device.

[0075] The reader and / or device can be fixed or mobile. The reader and / or device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed in the air on airplanes, balloons, and satellites. This application does not limit the application scenarios of the reader and device. The reader and device can be deployed in the same or different scenarios; for example, the reader and device can be deployed simultaneously on land; or the reader can be deployed on land and the device on water, etc., and so on.

[0076] In the embodiments of this application, the functions of the Reader can be executed by a module (such as a chip) within the Reader, or by a control subsystem that includes Reader functions. This control subsystem, including Reader functions, can be a control center in the aforementioned application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities. Similarly, the functions of the Device can be executed by a module (such as a chip or modem) within the Device, or by a device that includes Device functions.

[0077] It should be noted that the solutions in the embodiments of this application can also be applied to other communication systems, and the corresponding names can be replaced by the names of the corresponding functions in other communication systems.

[0078] To facilitate understanding of the embodiments of this application, the terminology used in this application will be briefly explained first. Optionally, the explanation of some terms can also be found in the 3GPP standard protocol.

[0079] 1. IoT: This refers to the Internet of Things, which connects all things. It extends the internet user interface to any object, enabling information exchange and communication between any two objects. This type of communication is also known as MTC (Mechanical, Communication, and Telecommunications).

[0080] More and more IoT devices are being deployed in people's lives. Examples include smart water meters, shared bicycles, and devices for smart cities, environmental monitoring, smart homes, and forest fire prevention—all designed for sensing and data collection. In the future, IoT devices will be ubiquitous, potentially embedded in every piece of clothing, every package, every key, and virtually every offline item will become online thanks to IoT technology.

[0081] However, due to the wide distribution and large number of IoT devices, the process of realizing the Internet of Things has brought considerable challenges to the industry, the most prominent being the power supply issue. Currently, IoT technology is still mainly driven by operators, and IoT modules (the models in IoT devices) use standard cellular protocols to communicate with network devices (such as base stations). Because network devices (such as base stations) need to cover as large an area as possible, IoT modules need to be able to communicate even at a great distance from network devices (such as base stations). This means that IoT modules still consume up to 30mA of current during wireless communication, so current IoT modules still require high-capacity batteries to operate. This also makes it difficult to miniaturize IoT modules, increasing the cost of IoT devices.

[0082] Furthermore, some low-power devices play a crucial role in IoT applications such as medical devices, smart homes, industrial sensors, and wearable devices. However, due to the limited size of these devices, extending their operating time is difficult to achieve simply by increasing battery capacity. Therefore, extending device battery life requires reducing the power consumption of wireless communication. Among these components, the radio transceiver is one of the most power-consuming.

[0083] Therefore, in order to further popularize IoT technology and implant IoT modules into the human body or smaller objects, it is no longer possible to use high-capacity batteries. Instead, smaller batteries or even completely eliminating battery limitations should be used, or a method to reduce the power consumption of radio transceivers should be designed to solve the limitations of IoT devices in terms of cost, size, and power consumption.

[0084] 2. A-IoT Devices: During the discussion of the 3GPP Release-18 standard, a study on low-power wake-up signal and receiver for NR was approved. Furthermore, A-IoT devices were also discussed at the 3GPP plenary meeting.

[0085] Unlike traditional cellular communication systems, A-IoT devices consume extremely low power (approximately 1μW to several hundred μW) and are prohibited from using battery power. Instead, they support normal operation by harvesting and storing ambient energy (such as radio waves, light energy, kinetic energy, and heat energy). To meet the extremely low power consumption requirements of A-IoT devices, the following communication methods can be used:

[0086] (1) On the R2D channel, the Reader uses OOK modulation to transmit data, and the A-IOT device uses an envelope detector receiver with extremely low power consumption to receive data.

[0087] (2) On the D2R channel, A-IoT devices can employ reflection communication technology. For example, an A-IoT device can use a carrier signal provided by an external carrier source and directly modulate the data to be transmitted onto that external carrier signal before sending it to the Reader. Since A-IoT devices do not need to generate their own carrier, power consumption can be greatly reduced.

[0088] A-IoT devices can be divided into active and passive types.

[0089] An active A-IoT device is an active tag or active device that uses energy stored in its own energy storage module to transmit wireless signals. Additionally, active A-IoT devices may also be described in other ways, such as active A-IoT, active A-IoT terminal, active A-IoT terminal device, active IoT, active IoT device, active IoT terminal, active IoT terminal device, active tag, active terminal, active terminal device, etc. These terms are used uniformly here and will not be elaborated upon further.

[0090] Passive A-IoT devices primarily rely on obtaining energy from external radio frequency signals and communicate through backscattered radio frequency signals, ultimately achieving ultra-low power consumption or even zero power consumption. Additionally, passive A-IoT devices may also be described in other ways, such as passive A-IoT, passive A-IoT terminal, passive A-IoT terminal device, passive IoT device, passive IoT terminal, passive IoT terminal equipment, passive source tag, battery-free terminal, battery-free device, no-battery terminal, no-battery device, backscatter terminal, backscatter device, etc. These terms are used uniformly here and will not be elaborated upon further.

[0091] Passive A-IoT devices can use carrier signals provided by an external carrier source and directly modulate the data to be transmitted onto that external carrier signal before sending it to the Reader. The external carrier source can be provided by a network device (e.g., the Reader) or by a third-party device other than the Reader and the A-IoT device. For example, as shown in Figure 2A, the Reader 110 can provide a carrier signal to the A-IoT device 120, which can modulate the carrier signal to obtain a D2R signal and send it to the Reader 110. As another example, as shown in Figure 2B, a third-party device (e.g., the UE 130) can provide a carrier signal to the A-IoT device 120, which can modulate the carrier signal to obtain a D2R signal and send it to the Reader 110.

[0092] 3. R2D and D2R messages: Messages sent from a Reader to an IoT device can be called R2D messages, and messages sent from an IoT device to a Reader can be called D2R messages.

[0093] As shown in Table 1, R2D messages and D2R messages can each include the following message types:

[0094] Table 1

[0095] The message types listed in the table above are illustrative; the message types for R2D and D2R messages can be developed according to functional protocols.

[0096] 4. Random Access Mechanism for A-IoT Devices: Currently, there are two random access mechanisms for A-IoT devices: CBRA and CFRA. As shown in Figure 3, in CBRA, the Reader can send a paging message, which includes relevant information about the IoT device to be paging. Next, the Reader can send an R2D trigger message (or R2D message, slot trigger message, or Qurey rep), which indicates the start of a set of MSG1 resources (i.e., access slots). For example, a set of MSG1 resources may include 6 access slots. CBRA mainly includes the following three key access steps:

[0097] 1. IoT devices transmit Msg1 on a set of Msg1 resources indicated by Qurey rep. Msg1 may include RN16. Each time-frequency resource can be used to transmit Msg1 from one or more IoT devices.

[0098] 2. After receiving Msg1 from the IoT device, the Reader can send Msg2 to the IoT device. Msg2 may include RN16, and the RN16 carried in Msg2 is the same as the RN16 carried in Msg1.

[0099] 3. After receiving Msg2, the IoT device can send Msg3 to the Reader. Msg3 may include the IoT device's identifier or index.

[0100] Subsequently, after receiving Msg3 from the IoT device, the Reader can send a response message (also called Msg4) to the IoT device to indicate whether the random access was successfully resolved. If Msg4 indicates successful random access, the IoT device can send a D2R message (also called Msg5) carrying data to the Reader. The Reader can then issue another Query reply, indicating a new set of Msg1 resources. Further processing can be found in the description above and will not be repeated here.

[0101] The CFRA mainly includes the following key access step:

[0102] IoT devices can send Msg1 on the Msg1 resource indicated by Qurey rep.

[0103] Msg1 can include the RN16 and the identifier or index of the IoT device. Subsequently, after receiving Msg1 from the IoT device, the Reader can send a response to Msg1 to the IoT device to indicate whether the IoT device has successfully resolved the randomization issue.

[0104] Currently, in the random access process of AIoT, for CBRA, there is an issue where Msg1, Msg3, and subsequent messages of Msg3 (e.g., higher-layer data transmission messages) fail to be successfully received by the Reader; for CFRA, there is also an issue where Msg1 and subsequent messages of Msg1 (e.g., higher-layer data transmission messages) fail to be successfully received by the Reader. However, how to handle failures in different scenarios requires further discussion.

[0105] In view of this, this application provides a communication method that ensures timely failure handling by the device, such as re-attempting random access or retransmitting the corresponding message type (e.g., retransmitting Msg1, Msg3, or higher-layer data transmission messages). This can improve the success rate of random access or data transmission, avoid resource waste, and reduce communication latency. The method provided in this application also designs different messages or formats, which can reduce signaling overhead, reduce signaling format complexity, and provide more efficient failure indication.

[0106] The solution provided in this application will be described in detail below with reference to the corresponding flowcharts. It is understood that the illustrative flowcharts provided in this application primarily use different devices (e.g., Device, Reader) as examples of the execution entities for this interactive illustration to illustrate the method, but this application does not limit the execution entities of the interactive illustrations. For example, the devices (e.g., Device, Reader) in the illustrative flowcharts can also be chips, chip systems, or processors that support the implementation of this method on the device, or logic modules or software capable of implementing all or part of the device's functions.

[0107] As a general statement, the message or signaling interactions involved in the interaction process of this application embodiment can be standard messages or signaling or newly introduced messages or signaling. This application embodiment does not make specific limitations on this.

[0108] It should be understood that the technical terms used in this application are for illustrative purposes only and not as limiting. For example, as technology evolves, technical terms may also change, and other technical terms that have the same technical meaning should also apply to this application.

[0109] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of this application, unless otherwise stated, "at least one" means one or more, and "multiple" means two or more. "Greater than or equal to" means greater than or equal to, and "less than or equal to" means less than or equal to. Furthermore, to facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first," "second," etc., are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first," "second," etc., do not limit the quantity or execution order, and that "first," "second," etc., do not necessarily imply differences.

[0110] Figure 4 is a schematic diagram of a communication method according to an embodiment of this application, using a device as an example for illustration. It can be understood that the device in Figure 4 can be Device 120 in Figure 1, or it can refer to a device within the device (e.g., a processor, chip, or chip system). The reader in Figure 4 can be Reader 110 in Figure 1, or it can refer to a device within the reader (e.g., a processor, chip, or chip system).

[0111] As shown in Figure 4, the method includes the following steps:

[0112] 401. The Device sends the first D2R message to the Reader, and the Reader receives the first D2R message from the Device accordingly.

[0113] In this embodiment of the application, the first D2R message may include MSG1, MSG3 or a higher-layer data transmission message.

[0114] MSG1 can include a first random number and / or a device identifier. MSG1 can be used to request random access. In the CBRA procedure, MSG1 can include a first random number, such as RN16. RN16 is a 16-bit random number. In the CFRA procedure, MSG1 can include a first random number and a device identifier.

[0115] MSG3 includes the device's identifier. Optionally, MSG3 may also carry the reason for initiating CBRA. MSG3 is used to establish a connection with the Reader so that the device can access the network. After receiving the MSG3 sent by the device, the Reader can identify the device based on the device identifier carried in the MSG3 and allocate resources for it to perform subsequent data transmission. Optionally, MSG3 may also include first data. The first data is upper-layer data. The upper-layer data can carry the device's service information, such as measurement data (temperature, humidity, etc.).

[0116] Upper-layer data transmission messages can include primary data. This primary data can be upper-layer data. In IoT scenarios, such as smart metering and environmental monitoring, devices typically only need to send a small amount of data (i.e., primary data, such as temperature and humidity). Upper-layer data transmission messages can be used to carry this primary data, eliminating the need for complex Data Radio Bearers (DRBs) and effectively saving network resources and device power consumption. Upper-layer data transmission messages can also be called Data-to-Relation (D2R) data transmission messages, or Non-Access Stratum (NAS) messages.

[0117] 402. The Reader sends the first R2D message to the Device, and the Device receives the first R2D message from the Reader accordingly.

[0118] If the Reader determines that the first D2R message sent by the Device is abnormal, it can send a first R2D message to the Device. An abnormal first D2R message means that the first D2R message transmission failed, the first D2R message was not received, or the first D2R message conflicted with a D2R message sent by another Device.

[0119] The first R2D message is used to instruct the Device to re-enter random access, and / or, the first R2D message is used to instruct the Device to send a second D2R message. The second D2R message has the same message type as the first D2R message.

[0120] It should be understood that the first R2D message is used to instruct the Device to send a second D2R message; that is, the first R2D message can be used to instruct the Device to retransmit MSG1, MSG3, or higher-layer data transmission messages. For example, if the first D2D message is MSG1, the first R2D message instructs the Device to re-initiate random access, or the first R2D message instructs the Device to retransmit MSG1. If the first D2D message is MSG3, the first R2D message instructs the Device to re-initiate random access, or the first R2D message instructs the Device to retransmit MSG3. If the first D2D message is a higher-layer data transmission message, the first R2D message instructs the Device to re-initiate random access, or the first R2D message instructs the Device to retransmit the higher-layer data transmission message. The Device can resend MSG1 to the network device to re-initiate random access after receiving a subsequent paging message.

[0121] Optionally, the first R2D message can be used to indicate an anomaly in the first D2R message.

[0122] In one possible design, the message type of the first R2D message is a NACK message. For example, the message type field (e.g., the MT field) in the message header of the first R2D message can indicate that the first R2D message is a NACK message. For example, as shown in Figure 5A, the MT field in the MAC header of the first R2D message indicates that the message type is a NACK message.

[0123] It should be understood that, in the embodiments of this application, a NACK message refers to a message used to trigger the device to re-enter random access or retransmit (e.g., retransmit MSG1, MSG3, or higher-layer data transmission messages). The embodiments of this application do not limit the name of the NACK message; other technical terms may also apply where the technical meaning is the same.

[0124] In this embodiment, under different abnormal conditions such as MSG1 failure, MSG3 failure, or higher-layer data transmission message failure, the Reader can send an R2D message (i.e., the first R2D message) of type NACK to the Device to instruct the Device to re-enter random access or retransmit the corresponding message (MSG1, MSG3, or higher-layer data transmission message). This eliminates the need to design different message types for different abnormal conditions, avoids excessive MT usage, and reduces message design complexity.

[0125] In another possible design, the message type of the first R2D message is an R2D data message. Furthermore, the first R2D message includes first information indicating that the first R2D message is a NACK message. This first information can be carried in one or more fields / bits. For example, the first information can be carried in a first field. As shown in Figure 5B, the MT field of the MAC header of the first R2D message indicates that the message type is an R2D data message. The MAC header may also include a length field to indicate the data length. The first R2D message may also include a first field (e.g., a NACK indication field) to indicate that the first R2D message is a NACK message.

[0126] The first R2D message can reuse the message type of R2D data, eliminating the need to design a new message type for the first R2D message and reducing the amount of MT required, thus reducing message design complexity.

[0127] In one possible design, the first R2D message also includes second information, which is used to indicate at least one Device.

[0128] For example, the second information may include at least one first index (device-related index). Each device-related index is used to indicate (or identify) a device. The device-related index may be an access layer identity (AS ID) or RN16. The second information may be carried in one or more fields / bits. For example, the second information may be carried in a second field. As shown in Figure 5C(a) or (b), the second field may be an Index 1 field, which may carry an AS ID or RN16.

[0129] In some embodiments, if the Device sends MSG1 but does not receive MSG2, the device-related index can be RN 16. If the Device receives MSG2, and MSG2 carries a network-assigned AS ID, the device-related index can be the AS ID.

[0130] In some possible implementations, RN16 can be used as the AS ID, or the value of the AS ID can be RN16.

[0131] When the first R2D message includes the second information, the first R2D message is used to instruct at least one device to re-enter random access, or to instruct at least one device to retransmit the D2R message (e.g., MSG1, MSG3, or higher-layer data transmission message).

[0132] Optionally, the second information may also include paging ID, temporary ID, and device ID, etc., which are not specifically limited in this application.

[0133] In one possible design, MSG2 could include a single bit indicating whether RN16 from MSG1 is reused as the AS ID. If this bit indicates reuse of RN16 from MSG1 as the AS ID, the device can store RN16 as the AS ID for subsequent network scheduling. If this bit indicates not to reuse RN16 from MSG1 as the AS ID, the device can release RN16 (i.e., there's no need to store RN16), saving storage space. Thus, instead of carrying the complete AS ID in MSG2, a single bit simplifies the MSG2 design.

[0134] In one possible design, the first R2D message further includes third information indicating first time-domain resources and / or first frequency-domain resources. The first time-domain resources are the time-domain resources used by at least one device (including the first device) to transmit D2R messages (including the first D2R message), and the first frequency-domain resources are the frequency-domain resources used by at least one device to transmit D2R messages (including the first D2R message). It should be understood that the first time-domain resources and / or the first frequency-domain resources are resources previously used by at least one device (including the first device) to transmit D2R messages, and not resources subsequently used to transmit new D2R messages.

[0135] When the first R2D message includes third information, at least one device that has transmitted D2R messages on the first time domain resource and / or the first frequency domain resource can re-enter random access, or re-transmit D2R messages (e.g., MSG1, MSG3, or higher-layer data transmission messages). That is, the third information can be used to instruct at least one device to re-enter random access, or to re-transmit D2R messages.

[0136] The third information can be carried in one or more fields / bits. For example, the third information can be carried in a third field. The third field can be an Index 2 field. For example, the Index 2 field can include an index of a first time-domain resource and / or a first frequency-domain resource. As shown in Figure 5D(a) or (b), the Index 2 field can include an index TRI (e.g., 1-2) of the time-domain resource and an index FRI (e.g., 1-8) of the frequency-domain resource; or, Index 2 can include a resource index RI (e.g., an integer in time-division 2 * frequency-division 8). For another example, the Index 2 can be indicated using a bitmap. For example, if there are 6 access occupancy (AO) events, Index 2 can include 6 bits, each indicating one of the 6 AOs. For example, Index 2 can be 111000, indicating the first, second, and third AOs among the aforementioned 6 AOs. That is, the network can instruct at least one device that has performed random access in the first AO, second AO, and third AO to re-perform random access, or to retransmit D2R messages.

[0137] In some embodiments, the first R2D message further includes eighth information, which indicates whether the first R2D message includes a second field or a third field. For example, if the eighth information is a fifth value (e.g., 0), it may indicate that the first R2D message includes the second field but does not include the third field. If the eighth information is a sixth value (e.g., 1), it may indicate that the first R2D message includes the third field but does not include the second field.

[0138] In some embodiments, if the Device sends MSG1 but does not receive MSG2, the first R2D message may include a third field but not the second field. If the Device sends MSG3, the first R2D message may include the second field but not the third field.

[0139] Optionally, the first R2D message also includes resource scheduling information, which indicates the time-domain and / or frequency-domain resources used by at least one Device to send the second D2R message. Each of the at least one Device's resources (time-domain and / or frequency-domain resources) corresponds one-to-one with the Device's identifier (e.g., AS ID). Alternatively, the resources (time-domain and / or frequency-domain resources) for each of the at least one Device can be determined based on preset rules. For example, the Device resources can be arranged in descending order of Device priority, with higher-priority Devices having their resources listed earlier and lower-priority Devices having their resources listed later.

[0140] In some embodiments, the first R2D message may include fourth information. The fourth information instructs the first device to re-enter random access, or the fourth information instructs the first device to send a second D2R message.

[0141] The fourth information can be carried in one or more fields / bits. For example, the fourth information can be carried in the first bit of the first field. When the first bit has a first value, the first R2D message instructs the Device to re-enter random access; when the first bit has a second value, the first R2D message instructs the Device to send a second D2R message. The first value and the second value are different.

[0142] The first bit can include one or more bits. For example, taking NI as the first bit, if NI is a first value (e.g., NI = 0), the first R2D message is used to instruct the Device to re-perform random access. If NI is a second value (e.g., NI = 1), the first R2D message is used to instruct the Device to send a second D2R message, that is, to retransmit the corresponding message (e.g., MSG1, MSG3, or higher-layer data transmission message).

[0143] In this way, the fourth information can instruct the device to re-access or re-transmit the corresponding message (e.g., MSG1, MSG3, or higher-layer data transmission message), without having to design too many message types or occupy too much MT, thus reducing the complexity of message design.

[0144] In some embodiments, the fourth information is further used to indicate whether the first R2D message includes a fifth information. The fifth information indicates the number of bytes / bits that the Reader has successfully received.

[0145] Taking the fourth information carried in the first bit of the first field as an example, if the first bit has a first value, the first R2D message does not include the fifth information; if the first bit has a second value, the first R2D message includes the fifth information. The fifth information can be carried in one or more fields / bits. For example, the fifth information can be carried in the fourth field.

[0146] For example, the fourth field can be an SRB (success received bits) field (also called the SRB field), which indicates the number of bytes (or bits) the Reader has successfully received. The SRB field can implicitly indicate the starting position for the Device to retransmit the MSG3 or higher-layer data transmission message. That is, based on the starting position of the original MSG1, MSG3, or higher-layer data transmission message, counting the number of bytes (or bits) indicated by the SRB field, the next byte (or bit) after the indicated number of bytes / bits is used as the starting position for retransmission. For example, assuming the original MSG3 or higher-layer data transmission message includes 10 bytes and the SRB field indicates 5 bytes, the IoT device can start retransmitting from the 6th byte of the original MSG3 or higher-layer data transmission message. This implicit indication method can save communication bandwidth and transmission time, improving the efficiency and flexibility of data transmission.

[0147] In some embodiments, when the first bit has a first value, the first R2D message is used to instruct the Device to re-perform random access, and the first R2D message is in a first format (i.e., excluding the fifth information). When the first bit has a second value, the first R2D message is used to instruct the Device to retransmit the corresponding message (e.g., MSG1, MSG3, or a higher-layer data transmission message). The first R2D message is in a second format (i.e., including the fifth information).

[0148] For example, taking the first bit as NI and the fourth field as SRB, as shown in Figure 5E(a), when NI=0, the first R2D message does not include the SRB field. As shown in Figure 5E(b), when NI=1, the first R2D message includes the SRB field.

[0149] Understandably, if the Device re-establishes random access, it can resend MSG1 in subsequent paging cycles. Since MSG1 does not carry service data, there is no need to add a fifth piece of information in the first R2D message to indicate the number of bytes successfully received by the Reader, thus saving signaling overhead.

[0150] If the first bit has the second value, the Device can send a second D2R message, i.e., retransmit the corresponding message (e.g., MSG3 or higher-layer data transmission message). Since MSG3 or higher-layer data transmission messages can usually carry service data, a fourth field can be added to the first R2D message to indicate the number of bytes the Reader has successfully received (the number of bytes corresponding to the service data). This allows the Device to start transmitting from the bytes after the number of bytes successfully received by the Reader, avoiding duplicate data transmission.

[0151] In some embodiments, the first R2D message may further include sixth information, which indicates whether segmentation retransmission is required. The sixth information may be carried in one or more fields / bits. For example, the sixth information may be carried in the second bit of the first field. The second bit may include one or more bits.

[0152] Furthermore, the sixth information can also be used to indicate whether the first R2D message includes the fifth information, which is used to indicate the number of bytes / bits that the reader has successfully received.

[0153] In some embodiments, if the fourth information instructs the first device to send a second D2R message, the first R2D message may include a sixth information. If the fourth information instructs the first device to re-enter random access, the first R2D message may not include the sixth information.

[0154] For example, suppose the fourth information is carried in the first bit of the first field, and the sixth information is carried in the second bit of the first field. If the first bit has a second value, the first field may also include a second bit, which indicates whether segmented retransmission is required. If the second bit has a third value, the device does not perform segmented retransmission, and the first R2D message is in the first format (i.e., excluding the SRB field). If the second bit has a fourth value, the device performs segmented retransmission, and the first R2D message is in the second format (i.e., including the SRB field).

[0155] For example, taking NI as the first bit and RSI as the second bit, when NI = 1, the first field can include RSI. As shown in Figure 5F(a), if RSI is a third value (e.g., RSI = 0), the device does not perform segmented retransmission (i.e., it can transmit the entire segment), and the first R2D message is in the first format (i.e., it does not include the SRB field). As shown in Figure 5F(b), if RSI is a fourth value (e.g., RSI = 1), the device performs segmented retransmission, and the first R2D message is in the second format (i.e., it includes the SRB field). In this case, the device can read the SRB field to determine the starting position of the segmented retransmission.

[0156] In this way, the sixth information can indicate whether segmented retransmission is required. When the device needs to retransmit a corresponding message (e.g., MSG3 or higher-layer data transmission message), if segmented retransmission is not required (i.e., full segment retransmission is required), the first R2D message can be set to the first format (i.e., the first R2D message does not include the SRB field), eliminating the need to include the SRB field indicating the number of bytes successfully received by the Reader, thus saving signaling overhead. If segmented retransmission is required, the first R2D message can be set to the second format (i.e., the first R2D message includes the SRB field), using the SRB field to indicate the number of bytes successfully received by the Reader (the number of bytes corresponding to the service data). This allows the device to start transmitting from the bytes successfully received by the Reader, avoiding duplicate data transmission.

[0157] In one possible implementation, when the first D2R message carries a first random number (i.e., when the first D2R message is MSG1), the first R2D message can be in a first format, meaning the first R2D message does not include the fifth information. In other words, if the first R2D message is received after the Device sends MSG1 and before it sends MSG3, the first R2D message does not include the fifth information.

[0158] Understandably, if the first D2R message carries the first random number (i.e., the first D2R message is MSG1), and the Reader determines that the first D2R message is abnormal, it can usually instruct the Device to re-access randomly through the first R2D message, or resend the complete MSG1. Since MSG1 does not carry service data, there is no need to add the fifth information to the first R2D message to indicate the number of bytes that the Reader has successfully received, which can save signaling overhead.

[0159] In one possible implementation, if the first D2R message carries the Device's identifier and / or first data (i.e., if the first D2R message is an MSG3 or a higher-level data transmission message), the first R2D message is in a second format, namely, it includes fifth information indicating the number of bytes successfully received by the Reader. In other words, if the first R2D message is received after the Device has sent an MSG3 or a higher-level data transmission message, the first R2D message includes the fifth information.

[0160] Understandably, if the first D2R message carries the Device identifier and / or the first data (i.e., the first D2R message is an MSG3 or higher-layer data transmission message), and the Reader determines that the first D2R message is abnormal, it can instruct the Device to re-enter random access through the first R2D message, or resend the MSG3 or higher-layer data transmission message. Since the MSG3 or higher-layer data transmission message can usually carry service data, a fifth piece of information can be added to the first R2D message to indicate the number of bytes that the Reader has successfully received (the number of bytes corresponding to the service data), which can avoid duplicate data transmission.

[0161] It should be understood that various information (e.g., first information, second information, etc.) in the embodiments of this application can be indicated by different fields / bits, or multiple information can be jointly indicated by the same field / bit, and this application does not limit this.

[0162] 403. The Device re-establishes random access, or the Device sends a second D2R message.

[0163] If the first R2D message instructs the Device to re-establish random access, the Device may re-establish random access. If the first R2D message instructs the Device to send a second D2R message, the Device may send a second D2R message.

[0164] In some embodiments, the first R2D message includes fourth information. The fourth information instructs the Device to re-enter random access, or instructs the Device to send a second D2R message. The first R2D message may also include second or third information, where the second information indicates at least one Device, and the third information indicates a first time-domain resource and / or a first frequency-domain resource. For example, if the fourth information is carried in the first bit of the first field, and the second or third information is carried in the second or third field respectively, and the first bit of the first field of the first R2D message is a first value, and the at least one Device indicated by the second field of the first R2D message contains resources (time-domain resources and / or frequency-domain resources) that are used by the Device to transmit the first D2R message, then the Device can re-enter random access. If the first bit of the first field of the first R2D message is the second value, and at least one Device indicated by the second field of the first R2D message contains resources (time domain resources and / or frequency domain resources) that are used by the Device to transmit the first D2R message, the Device may send a second D2R message, i.e., retransmit the corresponding message (MSG1, MSG3 or higher layer data transmission message).

[0165] Device re-random access refers to the process where the Device retransmits MSG1 after receiving a subsequent paging message. A subsequent paging message refers to one or more subsequent paging messages that share the same transaction ID and / or paging ID as the preceding paging message (received before the Device sends the first D2R message). Subsequent paging can be subsequent A-IOT paging.

[0166] For example, as shown in Figure 5G, before the Device sends the first D2R message to the Reader, the Device can receive a first paging message from the Reader. The first paging message may include a first identifier, which can be a transaction ID. The first identifier is used to indicate the service / business corresponding to the first paging message (e.g., smart metering, intelligent transportation, smart home, etc.). It is understood that the same service / business can initiate multiple paging (e.g., periodically sending multiple paging messages). That is, the same service / business can correspond to multiple paging cycles (e.g., the first paging cycle and subsequent paging cycles), and each paging cycle can send one or more R2D trigger messages. Suppose that the Device fails to initiate random access after receiving the first paging message (e.g., the first D2R message (e.g., MSG1 or MSG3) sent by the Device after receiving the first paging message is abnormal), then the Device can re-initiate random access. That is, after receiving subsequent paging messages (including the first identifier) ​​following the first paging message, the Device can send a third D2R message to the Reader (i.e., resend MSG1). The third D2R message includes a second random number, or it includes the second random number and the Device's identifier. In other words, after receiving subsequent paging messages following the first paging message, the Device can resend MSG1 to the network device to re-initiate random access.

[0167] In some embodiments, when the first R2D message is used to instruct the Device to re-initiate random access, the Device can stop the currently ongoing first process (e.g., random access process or data transmission process). For example, it can stop listening for R2D messages (e.g., R2D trigger messages), stop listening for subsequent paging messages, and release the first information (the first information includes a first random number or AS ID, where the AS ID takes precedence over the first random number, i.e., the AS ID can be released first). This avoids resource waste and saves device power consumption. In some embodiments, the content of the second D2R message may be the same as the first D2R message. In other embodiments, the content of the second D2R message may be different from the first D2R message. Whether the content of the second D2R message is the same as the first D2R message is based on protocol specifications or network instructions.

[0168] For example, in the case that the first D2R message is MSG1, after the device receives the first R2D message (e.g., the first bit of the first field is the second value, and at least one device indicated by the second or third field contains itself), it can retransmit MSG1. This MSG1 may include RN16. The RN16 in the retransmitted MSG1 may be the same as or different from the RN16 in the first D2R message (the previously sent MSG1).

[0169] In some embodiments, the first R2D message further includes seventh information, which indicates whether to regenerate a random number (e.g., RN16). When the seventh information indicates that a random number should be regenerated, the RN16 (second random number) in the second D2R message (retransmitted MSG1) is different from the RN16 (first random number) in the first D2R message (previously sent MSG1); when the seventh information indicates that a random number should not be regenerated, the second random number is the same as the first random number, meaning that the RN16 in the retransmitted MSG1 can be the same as the RN16 in the first D2R message (previously sent MSG1).

[0170] When the first D2R message is MSG3, the second D2R message is also MSG3. That is, when the first D2R message is MSG3, after the device receives the first R2D message (e.g., the first bit of the first field is the second value, and at least one device indicated by the second field contains resources (time-domain resources and / or frequency-domain resources) that it uses to transmit the first D2R message), it can retransmit MSG3. The first D2R message includes the identifier of the first device, or includes the identifier of the first device and first data; the second D2R message includes the identifier of the first device, or includes the identifier of the first device and second data, where the second data includes part or all of the first data. In other words, the data carried in the retransmitted MSG3 (the second data) can be the same as (the second data includes all of the first data) or different from (the second data includes part of the first data) the data carried in the first D2R message (the previously transmitted MSG3).

[0171] When the first D2R message is a higher-layer data transmission message, after the device receives the first R2D message (e.g., the first bit of the first field is the second value, and at least one device indicated by the second field contains itself or the resources (time-domain resources and / or frequency-domain resources) indicated by the third field are its own resources used to transmit the first D2R message), it can retransmit the higher-layer data transmission message. The data carried in the retransmitted higher-layer data transmission message (second data) may be the same as (the second data includes all of the first data) or different from (the second data includes part of the first data) carried in the first D2R message (the previously sent higher-layer data transmission message).

[0172] Furthermore, the Device can determine whether the first R2D message includes the fifth information based on the fourth or sixth information of the first R2D message. If the first R2D message includes the fifth information, the Device can transmit the MSG3 or higher-layer data transmission message after the number of bytes (or bits) successfully received by the Reader. If the first R2D message does not include the fifth information, the Device can retransmit the MSG3 or higher-layer data transmission message (i.e., retransmit the entire MSG3 or higher-layer data transmission message), as described in step 402.

[0173] In some embodiments, where the first R2D message is used to instruct the Device to send a second D2R message, the Device can release first information, which includes a first random number (e.g., RN16) or an AS ID, thus saving storage space on the Device. The AS ID takes precedence over the first random number, meaning the AS ID can be released first. Furthermore, the Reader can reclaim the released first information (RN16 or AS ID) for use by other Devices (allocating the reclaimed RN16 or AS ID to other Devices), thus saving AS ID resources.

[0174] Based on the method provided in this application, if the Reader determines that the first D2R message (e.g., MSG1, MSG3, or higher-layer data transmission message) sent by the Device is abnormal, it can send a first R2D message to the Device, instructing the Device to re-enter random access or to retransmit the corresponding message (e.g., MSG1, MSG3, or higher-layer data transmission message). This allows for different processing methods to be instructed to the Device under different circumstances, improving the success rate of random access or data transmission, avoiding resource waste, and reducing communication latency.

[0175] For example, in a slot, if multiple devices attempt random access simultaneously, and some devices fail to access the slot later (i.e., near the end of the slot), the Reader can instruct these devices to re-access, preventing them from affecting communication in the next slot. If these devices are not instructed to re-access, they might continue to cause interference or consume resources in subsequent slots, affecting the normal access and communication of other devices. As another example, in a slot, if multiple devices attempt random access simultaneously, and some devices fail to access the slot (e.g., MSG1 error), the Reader can instruct these devices to retransmit the corresponding messages (e.g., MSG1, MSG3, or higher-layer data transmission messages) during the early or middle stages of the slot. This avoids wasting allocated resources and eliminates the need to wait for the next access opportunity to re-access, reducing communication latency.

[0176] As shown in Figure 6, this application provides a communication method, which is illustrated using MSG1 as an example of a first D2R message, including:

[0177] 601. The Device sends MSG1 to the Reader, and the Reader receives MSG1 from the Device accordingly.

[0178] MSG1 includes the first random number and / or the identifier of the Device, which can be referred to in the relevant description of step 401, and will not be repeated here.

[0179] 602. The Reader sends the first R2D message to the Device, and the Device receives the first R2D message from the Reader accordingly.

[0180] The first R2D message is used to instruct the Device to re-perform random access, and / or the first R2D message is used to instruct the Device to send the second D2R message, i.e., to retransmit (resend) MSG1.

[0181] The first R2D message can be found in the relevant description of step 402, which will not be repeated here.

[0182] 603. The Device will re-enter the random access mechanism, or the Device will retransmit MSG1.

[0183] The device can re-access randomly, or the device can retransmit MSG1. Please refer to the relevant instructions in step 403, which will not be elaborated here.

[0184] Based on the method provided in this application, if the Reader determines that the first D2R message (e.g., MSG1) sent by the Device is abnormal, it can send a first R2D message to the Device, instructing the Device to re-enter random access or instructing the Device to retransmit the corresponding message (e.g., MSG1). In this way, if MSG1 is abnormal, the Device can re-enter random access or retransmit MSG1, which can improve the success rate of random access or data transmission.

[0185] As shown in Figure 7, this application provides a communication method, which is illustrated using MSG3 as an example of a first D2R message, including:

[0186] 701. The Device sends MSG3 to the Reader, and the Reader receives MSG3 from the Device accordingly.

[0187] MSG3 includes the Device identifier, or MSG3 includes the Device identifier and the first data. For details, please refer to the description in step 401, which will not be repeated here.

[0188] 702. The Reader sends the first R2D message to the Device, and the Device receives the first R2D message from the Reader accordingly.

[0189] The first R2D message is used to instruct the Device to re-enter random access, and / or, the first R2D message is used to instruct the Device to send a second D2R message, i.e., to retransmit MSG3. The first R2D message can be found in the relevant description of step 402, and will not be repeated here.

[0190] 703. Device re-accesses via random access, or Device retransmits MSG3.

[0191] The device can re-access randomly, or the device can retransmit MSG3. Please refer to the relevant instructions in step 403, which will not be elaborated here.

[0192] Based on the method provided in this application embodiment, if the Reader determines that the first D2R message (e.g., MSG3) sent by the Device is abnormal, it can send a first R2D message to the Device, instructing the Device to re-enter random access or instructing the Device to retransmit the corresponding message (e.g., MSG3). In this way, if MSG3 is abnormal, the Device can re-enter random access or retransmit MSG3, which can improve the success rate of random access or data transmission.

[0193] As shown in Figure 8, this application embodiment provides a communication method, which is illustrated using the first D2R message as an example of a high-layer data transmission message, including:

[0194] 801. The Device sends a higher-level data transfer message to the Reader, and the Reader receives the higher-level data transfer message from the Device accordingly.

[0195] For instructions on high-level data transmission, please refer to step 401. These instructions will not be repeated here.

[0196] 802. The Reader sends the first R2D message to the Device, and the Device receives the first R2D message from the Reader accordingly.

[0197] Specifically, the first R2D message is used to instruct the Device to re-enter random access, and / or, the first R2D message is used to instruct the Device to send a second D2R message, i.e., to retransmit (resend) the higher-layer data transmission message. For details, please refer to the relevant explanation of step 402, which will not be elaborated upon here.

[0198] 803. The Device re-establishes random access, or the Device retransmits the higher-level data transmission message.

[0199] If the device re-enters the random connection, or if the device retransmits the higher-layer data transmission message, please refer to the relevant instructions in step 403, which will not be elaborated here.

[0200] Based on the method provided in this application, if the Reader determines that the first D2R message (e.g., a higher-layer data transmission message) sent by the Device is abnormal, it can send a first R2D message to the Device, instructing the Device to re-establish random access or to retransmit the corresponding message (e.g., the higher-layer data transmission message). In this way, if MSG1 is abnormal, the Device can re-establish random access or retransmit the higher-layer data transmission message, thereby improving the data transmission success rate.

[0201] It should be understood that the flowcharts or scenario diagrams shown in Figures 1 to 8 are for ease of understanding only and are not intended to limit the embodiments of this application to the examples shown. In fact, those skilled in the art can make equivalent transformations based on the examples in Figures 1 to 8 to obtain more implementation methods.

[0202] The communication methods provided by the embodiments of this application have been described in detail above with reference to Figures 1 to 8. The apparatus embodiments of this application will now be described in detail with reference to Figures 9 and 10. It should be understood that the communication apparatus of the embodiments of this application can execute the various communication methods described in the foregoing embodiments of this application; that is, the specific working processes of the various products described below can be referred to the corresponding processes in the foregoing method embodiments.

[0203] In the embodiments described above, the first device can perform some or all of the steps in each embodiment; the network device can perform some or all of the steps in each embodiment. These steps or operations are merely examples, and the embodiments of this application can also perform other operations or variations of various operations. Furthermore, the steps can be performed in different orders as presented in the embodiments, and it is not necessary to perform all the operations in the embodiments of this application. Moreover, the sequence number of each step does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0204] Figure 9 is a schematic block diagram of a communication device provided in an embodiment of this application. As shown in Figure 9, the communication device 900 may include a communication module 910. The communication module 910 can implement corresponding communication functions, which can be internal communication functions of the communication device 900 or communication functions between the communication device 900 and other devices. Optionally, the communication module 910 may also be referred to as a communication interface or a transceiver module. Optionally, the communication device 900 further includes a processing module 920. The processing module 920 can implement corresponding processing functions.

[0205] Optionally, the communication device 900 further includes a storage module, which can be used to store instructions and / or data; the processing module 920 can read the instructions and / or data in the storage module so that the communication device 900 can implement the aforementioned method embodiments.

[0206] In one possible design, the communication device 900 may correspond to the first device (e.g., a device) in the above method embodiments, or a component (such as a circuit, chip, or chip system) configured in the first device. The communication device 900 can be used to perform the steps or processes performed by the first device in any of the above method embodiments.

[0207] For example, the communication module 910 is used to send a first D2R message to the reader; receive a first R2D message from the reader, the first R2D message being used to instruct the first device to re-enter random access, and / or, the first R2D message being used to instruct the first device to send a second D2R message, the second D2R message having the same message type as the first D2R message.

[0208] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0209] In one possible design, the communication device 900 may correspond to a network device (e.g., a reader) in the above method embodiments, or a component (e.g., a circuit, chip, or chip system) configured in a network device. The communication device 900 can be used to perform the steps or processes performed by the network device in any of the above method embodiments.

[0210] For example, the communication module 910 is used to receive a first D2R message from the first device; send a first R2D message to the first device, the first R2D message being used to instruct the first device to re-perform random access; and / or, the first R2D message being used to instruct the first device to send a second D2R message, the second D2R message having the same message type as the first D2R message.

[0211] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0212] Figure 10 is another schematic block diagram of the communication device 1000 provided in an embodiment of this application. The communication device 1000 may be a first device or a reader, a chip, chip system, or processor, etc., that implements the above-described methods. The communication device 1000 can be used to implement the methods described in the above-described method embodiments; for details, please refer to the descriptions in the above-described method embodiments.

[0213] As shown in Figure 10, the communication device 1000 may include one or more processors 1010, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 1010 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device 1000 (e.g., a base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.

[0214] In an alternative design, the processor 1010 may also store instructions and / or data that can be executed by the processor 1010 to cause the communication device 1000 to perform the methods described in the above method embodiments.

[0215] In another alternative design, the communication device 1000 may include a communication interface 1020 for implementing receiving and transmitting functions. For example, the communication interface 1020 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0216] Optionally, the communication device 1000 may include one or more memories 1030, which may store instructions that can be executed on the processor 1010, causing the communication device 1000 to perform the methods described in the above method embodiments. Optionally, the memories 1030 may also store data. Optionally, the processor 1010 may also store instructions and / or data. The processor 1010 and the memories 1030 may be provided separately or integrated together.

[0217] It should be understood that, in one possible design, the steps in the method embodiments provided in this application can be implemented by integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the methods disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.

[0218] In one implementation, the communication device 1000 may correspond to the first device in the above method embodiments and may be used to execute the various steps and / or processes executed by the first device in the above method embodiments. The processor 1010 may be used to execute instructions stored in the memory 1030, and when the processor 1010 executes the instructions stored in the memory, the processor 1010 is used to execute the various steps and / or processes of the above method embodiments corresponding to the first device.

[0219] In another implementation, the communication device 1000 may correspond to the reader in the above method embodiments and may be used to execute the various steps and / or processes executed by the network device in the above method embodiments. The processor 1010 may be used to execute instructions stored in the memory 1030, and when the processor 1010 executes the instructions stored in the memory, the processor 1010 is used to execute the various steps and / or processes of the above method embodiments corresponding to the reader.

[0220] It should be understood that the aforementioned processing device can be one or more chips. For example, the processing device can be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0221] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0222] According to the method provided in the embodiments of this application, this application also provides a chip system, which includes one or more processors for calling and executing instructions stored in memory, thereby causing the method described in the embodiments of this application to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0223] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0224] According to the method provided in the embodiments of this application, this application also provides a communication system, which includes the aforementioned first device and reader.

[0225] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: computer program code, which, when run on a computer, causes the computer to execute the various steps or processes performed by the first device and reader in any of the foregoing method embodiments.

[0226] According to the method provided in the embodiments of this application, this application also provides a computer-readable storage medium storing program code that, when run on a computer, causes the computer to execute the various steps or processes performed by the first device and reader in any of the foregoing method embodiments.

[0227] The computer-readable storage medium may be the aforementioned volatile memory or non-volatile memory, or it may include both volatile memory and non-volatile memory.

[0228] In the embodiments of this application, the terms and English abbreviations are exemplary examples given for ease of description and should not be construed as limiting the application in any way. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0229] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When these computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated.

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

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

[0232] In summary, the above description is merely a preferred embodiment of the technical solution of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A communication method, characterized in that, Applied to a first device, the method includes: Send the first D2R message to the reader; The first R2D message is received from the reader / writer. The first R2D message is used to instruct the first device to re-enter random access, and / or the first R2D message is used to instruct the first device to send a second D2R message. The second D2R message has the same message type as the first D2R message.

2. The method according to claim 1, characterized in that, The message type of the first R2D message is a NACK message; or, The message type of the first R2D message is an R2D data message. The first R2D message includes first information, which is used to indicate that the first R2D message is a NACK message.

3. The method according to claim 1 or 2, characterized in that, The first R2D message also includes second information, which indicates at least one device, including the first device.

4. The method according to claim 3, characterized in that, The second information includes at least one first index, which is an access layer index ASID or a random number.

5. The method according to any one of claims 1-4, characterized in that, The first R2D message includes third information, which is used to indicate a first time-domain resource and / or a first frequency-domain resource. The first time-domain resource includes time-domain resources for at least one device to transmit D2D messages, and the first frequency-domain resource includes frequency-domain resources for the at least one device to transmit D2D messages. The at least one device includes the first device.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: When the first R2D message instructs the first device to re-enter random access, the first device stops the first process; wherein stopping the first process includes at least one of the following: Stop listening to R2D trigger messages, stop listening to subsequent paging messages, and release the first information, which includes a first random number or access layer index AS ID.

7. The method according to any one of claims 1-6, characterized in that, The first R2D message also includes fourth information, which instructs the first device to re-enter random access, or the fourth information instructs the first device to send a second D2R message.

8. The method according to claim 7, characterized in that, The fourth information is also used to indicate whether the first R2D message includes a fifth information, which is used to indicate the number of bytes / bits that the reader has successfully received.

9. The method according to any one of claims 1-8, characterized in that, The first R2D message also includes a sixth message, which indicates whether segmented retransmission is required.

10. The method according to claim 9, characterized in that, The sixth information is also used to indicate whether the first R2D message includes the fifth information, which is used to indicate the number of bytes / bits that the reader has successfully received.

11. The method according to any one of claims 1-10, characterized in that, The first D2R message includes MSG1, MSG3, or a higher-level data transmission message.

12. The method according to claim 11, characterized in that, When the first D2R message is an MSG3 or a higher-layer data transmission message, the first R2D message includes fifth information, which is used to indicate the number of bytes / bits that the reader has successfully received.

13. The method according to any one of claims 1-12, characterized in that, Whether the content of the second D2R message is the same as that of the first D2R message is based on protocol specifications or network instructions.

14. The method according to any one of claims 1-13, characterized in that, The first R2D message also includes resource scheduling information, which indicates the time-domain resources and / or frequency-domain resources used to send the second D2R message.

15. A communication method, characterized in that, Applied to a reader / writer, the method includes: Receive the first D2R message from the first device; Send a first R2D message to the first device, the first R2D message being used to instruct the first device to re-enter random access, and / or, the first R2D message being used to instruct the first device to send a second D2R message, the second D2R message having the same message type as the first D2R message.

16. The method according to claim 15, characterized in that, The message type of the first R2D message is a NACK message; or, The message type of the first R2D message is an R2D data message. The first R2D message includes first information, which is used to indicate that the first R2D message is a NACK message.

17. The method according to claim 15 or 16, characterized in that, The first R2D message also includes second information, which indicates at least one device, including the first device.

18. The method according to claim 17, characterized in that, The second information includes at least one first index, which is an access layer index ASID or a random number.

19. The method according to any one of claims 15-18, characterized in that, The first R2D message includes third information, which is used to indicate a first time-domain resource and / or a first frequency-domain resource. The first time-domain resource includes time-domain resources for at least one device to transmit D2D messages, and the first frequency-domain resource includes frequency-domain resources for the at least one device to transmit D2D messages. The at least one device includes the first device.

20. The method according to any one of claims 15-19, characterized in that, The first R2D message also includes fourth information, which instructs the first device to re-enter random access, or the fourth information instructs the first device to send a second D2R message.

21. The method according to claim 20, characterized in that, The fourth information is also used to indicate whether the first R2D message includes a fifth information, which is used to indicate the number of bytes / bits that the reader has successfully received.

22. The method according to any one of claims 15-21, characterized in that, The first R2D message also includes a sixth message, which indicates whether segmented retransmission is required.

23. The method according to claim 22, characterized in that, The sixth information is also used to indicate whether the first R2D message includes the fifth information, which is used to indicate the number of bytes / bits that the reader has successfully received.

24. The method according to any one of claims 15-23, characterized in that, The first D2R message includes MSG1, MSG3, or a higher-level data transmission message.

25. The method according to claim 24, characterized in that, When the first D2R message is an MSG3 or a higher-layer data transmission message, the first R2D message includes fifth information, which is used to indicate the number of bytes / bits that the reader has successfully received.

26. The method according to any one of claims 15-25, characterized in that, Whether the content of the second D2R message is the same as that of the first D2R message is based on protocol specifications or network instructions.

27. The method according to any one of claims 15-26, characterized in that, The first R2D message also includes resource scheduling information, which indicates the time-domain resources and / or frequency-domain resources used to send the second D2R message.

28. A communication device, characterized in that, The communication device is a first device or a reader / writer, and the communication device includes: a wireless communication module, a memory, and one or more processors; the wireless communication module, the memory, and the processor are coupled together. The memory is used to store computer program code, which includes computer instructions; when the computer instructions are executed by the processor, the communication device performs the method as described in any one of claims 1-14, or the method as described in any one of claims 15-27.

29. A computer-readable storage medium, characterized in that, Includes computer instructions; When the computer instructions are executed on the first device, the first device causes the first device to perform the method as described in any one of claims 1-14; Alternatively, when the computer instructions are executed on the reader, the reader causes the reader to perform the method as described in any one of claims 15-27.

30. A communication system, characterized in that, It includes a first device and a reader / writer, the first device performing the method as described in any one of claims 1-14, and the reader / writer performing the method as described in any one of claims 15-27.

Images