A communication method, a communication device, a system and a computer readable storage medium

Abstract

This application provides a communication method, communication device, system, and computer-readable storage medium. The method, applied in the field of communication, allows a reader to accumulate and statistically analyze the number of valid terminals within the current access period based on received and parsed Msg1 messages from multiple terminals. Then, it matches different AS ID compression strategies according to the range of terminal counts to determine the target number of bits for the AS ID of each accessing terminal, thereby assigning an AS ID with a different number of bits to each terminal. Furthermore, this application's embodiments overcome the limitation of using a traditional fixed 16-bit AS ID for each terminal in NACK messages. It allows for flexible selection of access identifiers based on the number of accessing terminals. This method can adapt to more scenarios, significantly reducing NACK message length and air interface transmission load, improving transmission efficiency and compatibility. It also eliminates the need for significant hardware or protocol stack modifications for terminals, reducing standard upgrade and terminal adaptation costs.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a communication method, communication device, system, and computer-readable storage medium. Background Technology

[0002] The Ambient Internet of Things (A-IoT) of the 3rd generation partnership project (3GPP) is an IoT communication technology for ultra-low power consumption and wide coverage. Its wireless access network architecture consists of readers and devices.

[0003] In a contention-based random access process, the Reader first sends a paging message to trigger one or more Devices to initiate a contention for random access. Upon receiving the paging message, the Device sends a Msg1 request for random access to the Reader. The Reader then sends a random access response message (Msg2) to the Device, which uses this response to determine if the random access was successful. If the random access is successful, the Device can send its device identifier (ID) and service-related upper-layer data to the Reader. If multiple Devices fail to transmit upper-layer data to the Reader, the Reader can use a negative acknowledgment (NACK) message to indicate the IDs of the devices that failed to transmit upper-layer data.

[0004] In current A-IoT networks, NACK messages need to carry multiple device access stratum identifiers (AS IDs) to identify devices that have failed to transmit. Traditional AS IDs use a fixed 16-bit length. As the number of access devices in multicast scenarios continues to increase, the length of NACK messages will increase proportionally with the number of devices. For example, for each additional device that fails to transmit, the NACK message needs to carry an additional 16 bits of AS ID information. Excessive redundant bits occupy a large amount of air interface transmission resources, reduce spectrum utilization, and lead to a waste of transmission resources. A large number of NACK messages can also cause air interface transmission congestion, affecting the overall network transmission efficiency. Summary of the Invention

[0005] This application provides a communication method, communication device, system, and computer-readable storage medium. The method can overcome the limitation that each terminal uses a traditional fixed 16-bit AS ID in the NACK message, and can flexibly select the access identifier of the terminal with different bit numbers, thus adapting to more scenarios.

[0006] Firstly, a communication method is provided. This method can be executed by a network device, such as the network device (Reader) described in the embodiments of this application, or by a component (such as a circuit, chip, or chip system) configured in the network device, or by a logic module or software capable of implementing all or part of the functions of the network device. This application does not limit this. The following description uses a reader as an example. The method includes:

[0007] The reader receives a first message from a first terminal, which includes the random identity identifier of the first terminal. The reader sends a second message to the first terminal, which is a response to the first message. The second message includes a first access layer identifier, which is determined based on the number of terminals that initiate random access to the reader and the random identity identifier of the first terminal, and the first access layer identifier is associated with the random identity identifier of the first terminal. If the reader does not receive upper-layer service data from the first terminal within a preset period, it sends a negative acknowledgment message to the first terminal, which includes the first access layer identifier.

[0008] It should be understood that "first message" can be interpreted as "Msg1," or also as "random access request" or "random access message," etc. This Msg1 contains the first terminal's random identifier (random ID). This random identifier (random ID) is used to identify the first terminal during random access. Before the network side completes authentication of the first terminal, the random ID is a unique temporary identifier between the first terminal and the reader / writer. Typically, the random ID can be a 16-bit or 32-bit random number.

[0009] It should also be understood that the process may also include the Reader sending a paging message, which can trigger one or more Devices to initiate random access. The first terminal can then randomly select one random access resource from the multiple random access resources indicated by the paging message and send a random ID through that random access resource.

[0010] It should also be understood that "second message" can be understood as "Msg2", or it can be called "response message for random access request" or "random access response message", etc.

[0011] In this embodiment, the second message includes a first access layer identifier. Optionally, the first access layer identifier is determined based on the number of terminals initiating random access to the reader and the random identity identifier of the first terminal, and the first access layer identifier is associated with the random identity identifier of the first terminal. Specifically, after receiving and parsing Msg1 sent by one or more devices, the Reader can accumulate and count the number of valid devices in the current access period, for example, the number of valid devices is denoted as D, and further determine the target number of bits of the first access layer identifier based on the value range of D.

[0012] In conjunction with the first aspect, in one possible implementation, the first access layer identifier is determined based on the number of terminals initiating random access to the reader and the random identity identifier of the first terminal, including: when the number of terminals initiating random access to the reader is less than or equal to a first threshold, the first access layer identifier has a first number of bits; when the number of terminals initiating random access to the reader is greater than the first threshold and less than or equal to a second threshold, the first access layer identifier has a second number of bits; when the number of terminals initiating random access to the reader is greater than the second threshold, the first access layer identifier is the random identity identifier of the first terminal; wherein, the first threshold is less than the second threshold, and the first number of bits is less than or equal to the second number of bits.

[0013] For example, when the number of valid Devices D is less than or equal to 16, the first access layer identifier (AS ID) of the first to sixteenth terminals is a 4-bit AS ID. Specifically, this 4-bit AS ID can be in the following format: the first access layer identifier of the first terminal is 0000; the first access layer identifier of the second terminal is 0001; ...; the first access layer identifier of the sixteenth terminal is 1111. Accordingly, the reader returns a second message including the first access layer identifier to each Device. This second message can include at least "4-bit AS ID + 4 bits of all zeros + 8-bit random ID".

[0014] Optionally, the 8-bit random ID can be obtained by compressing the random ID of each terminal, such as taking the last eight bits or the first eight bits of the random ID of each terminal device. This application embodiment does not limit this.

[0015] Alternatively, for example, when the number of valid Devices D is greater than 16 and less than or equal to 256, the first access layer identifier of the 17th to the 256th terminals is an 8-bit AS ID. Specifically, this 8-bit AS ID can be in the following format: the first access layer identifier of the 17th terminal is 0000 0001; the first access layer identifier of the 18th terminal is 00000010; ...; the first access layer identifier of the 256th terminal is 1111 1111. Accordingly, the reader returns a second message including the first access layer identifier to each Device, and this second message can include at least the content of "8-bit AS ID + 8-bit random ID".

[0016] Alternatively, for example, when the number of valid devices D is greater than 256, the first access layer identifier of the 257th terminal is a 16-bit AS ID. When the number of valid devices D in the current access period is greater than 256, choosing to use a 16-bit random ID as the identity identifier for each terminal can avoid effectively distinguishing the identity of each terminal and avoid duplicate identifiers for multiple terminals.

[0017] Using the above method, the Reader can accumulate the number of valid Devices within the current access period based on the Msg1 messages received and parsed from multiple terminals. Then, based on the range of values ​​for D, it determines the target number of first access layer identifier bits for each terminal. This allows for the allocation of different bit counts of AS IDs to each terminal based on different scenarios and the number of valid terminals. The resulting AS IDs, with their varying bit counts, can save communication resources when subsequently sent to each terminal via a second message.

[0018] After receiving the second message, the first terminal can parse it to obtain the newly assigned first access layer identifier and 8-bit random ID from the reader. This allows it to establish a one-to-one correspondence between the newly assigned first access layer identifier and the original random ID. Thus, after receiving the second message, the device can determine whether it is its own random access response message based on the 8-bit random ID, and also obtain the first access layer identifier assigned to it by the reader. This provides a foundation for simplifying the NACK message content in the future.

[0019] In combination with the first aspect and the above implementation, in one possible implementation, the negative confirmation message further includes first indication information, which is used to indicate whether the first access layer identifier is obtained through compression processing, and the first indication information is also used to indicate the target number of bits corresponding to the first access layer identifier.

[0020] In this embodiment, the NACK message may include the first access stratum identifier described above. Since the first access stratum identifier may be the 4-bit AS ID, 8-bit AS ID, or 16-bit AS ID described above, when the NACK message includes access stratum identifiers of multiple terminals, the NACK message may also correspond to different format contents, thereby helping the terminal obtain the corresponding access stratum identifier through different format contents.

[0021] In the above format, the number of bits occupied by the compression enable and the terminal's AS ID are uniformly carried by 2 bits, which can reduce the overhead of the indicator bits.

[0022] In conjunction with the first aspect and the above implementation methods, in one possible implementation method, the negative acknowledgment message further includes a first indication information and a second indication information. The first indication information is used to indicate whether the first access layer identifier is obtained through compression processing; the second indication information is used to indicate the target number of bits corresponding to the first access layer identifier.

[0023] In conjunction with the first aspect and the above implementation methods, in one possible implementation method, the negative acknowledgment message further includes a first indication information, a second indication information, and a third indication information. The first indication information is used to indicate whether the first access layer identifier is obtained through compression processing; the second indication information is used to indicate the start bit corresponding to the first access layer identifier; and the third indication information is used to indicate the end bit corresponding to the first access layer identifier.

[0024] In combination with the first aspect and the above implementation methods, in one possible implementation method, if the reader does not receive upper-layer service data sent by the second terminal within a preset period, the negative confirmation message also includes a second access layer identifier. The second access layer identifier is determined based on the number of terminals that initiate random access to the reader and the random identity identifier of the second terminal. The second terminal is the terminal that initiates random access to the reader.

[0025] It should be noted that the method of using compressed AS IDs to identify multiple terminals in the NACK message described above can be applied to each access cycle, or in other words, within each access-to-feedback cycle. The reader can re-count the number of terminals within that access cycle and further determine the method for allocating access layer identifiers based on the range of terminal counts. Alternatively, a timer can be set on the reader side. Within the timer's period, the method for allocating access layer identifiers can be determined based on the range of terminal counts, the target number of bits for the new AS ID can be determined, and a compressed AS ID can be reassigned to each terminal within the current period.

[0026] In summary, the embodiments of this application overcome the limitation of using a traditional fixed 16-bit AS ID for each terminal in the NACK message. Instead of using a static, fixed-bit compressed AS ID, the access identifier of the terminal can be flexibly selected based on the number D of terminals accessing the reader, and different compression strategies can be matched according to the range of values ​​for the number D. This method can adapt to more scenarios, significantly reducing the length of the NACK message and the air interface transmission load, thus improving transmission efficiency.

[0027] Furthermore, this application's embodiments use a small number of reserved indicator bits R to achieve compression control, eliminating the need to reconstruct the existing NACK multiplexing framework. Moreover, the rules for updating and allocating AS IDs based on the dual trigger conditions of "access period + number of terminals" avoid identifier conflicts caused by fluctuations in the number of terminals, while retaining the traditional 16-bit AS ID fallback mode. This ensures compatibility in ultra-large-scale scenarios with D ≥ 256 terminals, reducing the risk of insufficient compressed AS ID identification capabilities. In terms of compatibility, it is directly compatible with the NACK multiplexing mechanisms of other proposals without requiring significant modifications to the terminal hardware or protocol stack. The 16-bit fallback mode ensures adaptation to ultra-large-scale scenarios, reducing the cost of standard upgrades and terminal adaptation.

[0028] Secondly, a communication method is provided. This method can be executed by a terminal device, such as the first terminal (Device#1) described in the embodiments of this application, or by a component (such as a circuit, chip, or chip system) configured in the terminal device, or by a logic module or software capable of implementing all or part of the functions of the terminal device. This application does not limit this. The following description uses the first terminal as an example. The method includes:

[0029] The first terminal sends a first message to the reader, the first message including the random identity identifier of the first terminal; receives a second message from the reader, the second message being a response message to the first message, the second message including a first access layer identifier, the first access layer identifier being determined based on the number of terminals initiating random access to the reader and the random identity identifier of the first terminal, and the first access layer identifier being associated with the random identity identifier of the first terminal; within a preset period, receives a negative acknowledgment message from the reader, and based on the negative acknowledgment message, determines whether the transmission of upper-layer service data sent to the reader has failed, the negative acknowledgment message carrying access layer identifier information corresponding to one or more terminals.

[0030] In conjunction with the second aspect and the above implementation methods, in one possible implementation, the first access layer identifier is determined based on the number of terminals initiating random access to the reader and the random identity identifier of the first terminal, including: when the number of terminals initiating random access to the reader is less than or equal to a first threshold, the first access layer identifier has a first number of bits; when the number of terminals initiating random access to the reader is greater than the first threshold and less than or equal to a second threshold, the first access layer identifier has a second number of bits; when the number of terminals initiating random access to the reader is greater than the second threshold, the first access layer identifier is the random identity identifier of the first terminal; wherein, the first threshold is less than the second threshold, and the first number of bits is less than or equal to the second number of bits.

[0031] In conjunction with the second aspect and the above implementation, in one possible implementation, the negative acknowledgment message further includes first indication information, which is used to indicate whether the first access layer identifier is obtained through compression processing, and the first indication information is also used to indicate the target number of bits corresponding to the first access layer identifier; and the method further includes: obtaining access layer identifier information corresponding to one or more terminals from the negative acknowledgment message according to the first indication information.

[0032] In conjunction with the second aspect and the above implementation, in one possible implementation, the negative acknowledgment message further includes first indication information and second indication information. The first indication information is used to indicate whether the first access layer identifier is obtained through compression processing; the second indication information is used to indicate the target number of bits corresponding to the first access layer identifier; and the method further includes: determining whether the first access layer identifier is obtained through compression processing based on the first indication information; and obtaining access layer identifier information corresponding to one or more terminals from the negative acknowledgment message based on the second indication information.

[0033] In conjunction with the second aspect and the above implementation, in one possible implementation, the negative acknowledgment message further includes first indication information, second indication information, and third indication information. The first indication information is used to indicate whether the first access stratum identifier is obtained through compression processing; the second indication information is used to indicate the start bit corresponding to the first access stratum identifier; the third indication information is used to indicate the end bit corresponding to the first access stratum identifier; and the method further includes: determining whether the first access stratum identifier is obtained through compression processing based on the first indication information; determining the target number of bits corresponding to the first access stratum identifier based on the second and third indication information; and obtaining access stratum identifier information corresponding to one or more terminals from the negative acknowledgment message based on the target number of bits.

[0034] In combination with the second aspect and the above implementation methods, in one possible implementation method, determining whether the upper-layer service data sent to the reader has failed to be transmitted based on the negative confirmation message includes: when the negative confirmation message includes the first access layer identifier, determining that the upper-layer service data sent by the first terminal to the reader has failed to be transmitted, and re-initiating the random access procedure to the reader; when the negative confirmation message does not include the first access layer identifier, determining that the upper-layer service data sent by the first terminal to the reader has been transmitted successfully.

[0035] The second aspect is the implementation on the network device side, which corresponds to the first aspect. The explanations, supplements, and descriptions of the beneficial effects of the first aspect also apply to the second aspect, and will not be repeated here.

[0036] Thirdly, a communication device is provided, comprising a communication unit and a processing unit, which cooperate to enable the communication device to perform the functions of a reader / writer as described in the method design of the first aspect. These functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the aforementioned functions.

[0037] Fourthly, a communication device is provided, comprising a communication unit and a processing unit, the communication unit and the processing unit cooperating with each other to enable the communication device to perform the functions of the first terminal in the method design of the second aspect described above. These functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the aforementioned functions.

[0038] 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.

[0039] 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 of the possible implementations 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.

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

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

[0042] 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 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.

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

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

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

[0046] 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.

[0047] 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.

[0048] Optionally, there may be one or more processors and one or more memories.

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

[0050] 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 executed on a computer, causes the computer to perform the methods in any possible implementation of any of the above aspects.

[0051] 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.

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

[0053] In a twelfth aspect, a communication system is provided, including the aforementioned first terminal and network device, namely, Device and Reader in the embodiments of this application. Optionally, the communication system may further include other devices that communicate with the terminal device and / or network device. Attached Figure Description

[0054] Figure 1 This is a schematic diagram of a communication system 100 used in an embodiment of this application.

[0055] Figure 2 This diagram illustrates the contention-based random access process between the Reader and the Device.

[0056] Figure 3 This is a structural diagram of a NACK message.

[0057] Figure 4 This is a schematic diagram of an example communication method 400 provided in an embodiment of this application.

[0058] Figure 5 This is a schematic diagram of another communication method 500 provided in the embodiments of this application.

[0059] Figure 6 This is a schematic diagram of the structure of an example NACK message provided in an embodiment of this application.

[0060] Figure 7 This is a schematic block diagram of a communication device provided in an embodiment of this application.

[0061] Figure 8 This is another schematic block diagram of the communication device 800 provided in the embodiments of this application. Detailed Implementation

[0062] In the embodiments of this application, the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise stated, "multiple" means two or more.

[0063] It should be noted that, in the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B; the "and / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0064] It should also be noted that in the embodiments of this application, "preset", "fixed value", etc. can be implemented by pre-saving the corresponding code, table or other means that can be used to indicate relevant information in the electronic device. This application does not limit the specific implementation method.

[0065] It should be understood that the methods, situations, categories, and classifications of embodiments in this application are for the convenience of description only and should not constitute a special limitation. Various methods, categories, situations, and features in embodiments can be combined with each other without contradiction.

[0066] It should also be understood that, in the description of this embodiment, unless otherwise stated, "multiple" means two or more. 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.

[0067] The communication method provided in this application can be used in the paging process of Internet of Things (IoT) terminals. IoT includes ambient IoT (A-IoT), narrowband IoT (NB-IoT), and other similar technologies. IoT technology is widely used in various industries, such as logistics, warehousing, industrial manufacturing, identity recognition, and environmental monitoring. IoT is based on radio frequency identification (RFID) technology. RFID technology is a contactless communication technology that utilizes radio frequency communication. Its principle is that the reader and tag do not need to make contact; data communication is achieved through radio waves. The reader can also be called a "reader," and this application does not limit this terminology.

[0068] The technical solutions provided in the embodiments of this application can be applied to IoT systems, such as A-IoT systems; they can also be applied to communication systems related to the 3rd Generation Partnership Project (3GPP), such as Long Term Evolution (LTE) communication systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Universal Mobile Telecommunication System (UMTS), 5th Generation (5G) mobile communication systems, or other next-generation mobile communication systems, such as 6th Generation (6G) mobile communication systems, or other similar communication systems. Other similar communication systems may include Wireless Fidelity (Wi-Fi), Vehicle-to-Everything (V2X), etc., and the embodiments of this application do not limit this.

[0069] Figure 1 This is a schematic diagram of a communication system 100 applied in an embodiment of this application. The communication system 100 includes at least one terminal device and at least one network device. For example, Figure 1As shown, the communication system 100 may include a network device 110 and terminal devices 120a, 120b, and 120c, etc. The network device 110 and the terminal devices 120a, 120b, and 120c can communicate via a wireless link. It should be understood that the embodiments of this application do not limit the number or type of network devices and terminal devices included in the communication system 100.

[0070] In an IoT system, network device 110 can be equipped with a reader, and terminal devices can be configured with tags. Terminal devices in an IoT system can also be called "IoT terminal devices", "IoT terminals", "tag devices", etc.

[0071] The network device 110 in this application can be network-side equipment such as access network or core network equipment. Access network equipment is sometimes also called an access node. Access network equipment has wireless transceiver capabilities for communicating with terminals. Access network equipment includes, but is not limited to, base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs) in the aforementioned communication systems, 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. Access network equipment can also be modules or units capable of implementing some of the functions of a base station. Access network equipment can be a macro base station, micro base station, indoor station, relay node, donor node, or a wireless controller in a cloud radioaccess network (CRAN) scenario. Optionally, access network equipment can also be a server, wearable device, or vehicle-mounted equipment, etc. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). Multiple access network devices in a communication system can be base stations of the same type or different types. Base stations can communicate with terminals directly or via relay stations. Terminals can communicate with multiple base stations using different access technologies. The embodiments of this application do not limit the specific technology or device form used in the access network equipment. In this application, the access network equipment is referred to as "network equipment".

[0072] In practical applications, multiple network devices can collaborate to assist terminal devices in achieving wireless access, with different network devices each implementing a portion of the base station's functions. For example, network devices can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be set up separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

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

[0074] In the embodiments of this application, the apparatus for implementing the functions of the network device can be the network device itself, or it can be an apparatus capable of supporting the network device in implementing the functions, such as a processor, circuit, chip, or chip system. This apparatus can be installed in the network device or connected to the network device for use. In the technical solutions provided in this application, the network device itself is used as an example to describe the technical solutions provided in this application. The embodiments of this application do not limit the specific technology or specific device form adopted by the network device.

[0075] The terminal device in this application can be a wireless terminal device capable of receiving network device scheduling and instruction information, that is, a device capable of data communication with network devices. The wireless terminal 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 terminal device can communicate with one or more core networks or the Internet via a radio access network (RAN). The terminal device can also be referred to as a terminal, user equipment (UE), mobile station, mobile terminal, etc. Terminal devices 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), 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 terminal can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, aircraft (such as drones, helicopters, airplanes), hot air balloon, ship, robot, robotic arm, or smart home device (such as television, air conditioner, robot vacuum cleaner, speaker, set-top box), relay, customer premises equipment (CPE), device with tag functionality, sensor device, etc. The embodiments of this application do not limit the form of the terminal device. For example, the terminal device in the embodiments of this application can be an IoT terminal or an A-IoT terminal, such as a tag, sensor, etc. Figure 1 Take A-IoT terminals as an example.

[0076] In this embodiment, the tag can also serve as a terminal device, also referred to as an "A-IoT terminal" or "A-IoT device." The tag can be called an RFID tag or electronic tag, and is generally attached to an object to identify the target. The tag can receive radio frequency signals from a reader. Using the energy obtained from the induced current, the tag can transmit information stored in its internal chip. Alternatively, the tag can actively send a signal of a certain frequency to the reader, which then reads the information from the tag.

[0077] Both tags and readers can be implemented based on cellular network infrastructure, or they can be devices within the cellular network. For example, the functionality of a reader can be implemented by a network device or a terminal device, while a tag can be implemented by a terminal device within the cellular network. For instance, a tag can be an extremely low-power, extremely low-complexity IoT terminal. When a terminal device has tag functionality, it can perform contactless data communication with a network device or another terminal device.

[0078] With the development of IoT technology, tags are widely used in various industries. For example, tags can be used for warehouse material transportation management, logistics management, industrial control, identification, environmental monitoring, and so on. Logistics management, as a typical application, achieves logistics management by inventorying physical tags. Tag inventory involves a reader performing an inventory operation on a subset of tags within its coverage area to obtain the tags' identifiers. Typically, the reader broadcasts a select message, which includes the range of tags to be inventoried. Any tag receiving the select message determines whether its identifier belongs to the selected message or the included tag identifier range. If it does, the tag connects to the reader.

[0079] The various terminal devices described above, if located on a vehicle (e.g., placed / installed inside the vehicle), can all be considered in-vehicle terminal devices. In-vehicle terminal devices can be built into a vehicle's in-vehicle module, in-vehicle component, in-vehicle chip, or in-vehicle unit as one or more components or units. In-vehicle terminal devices can also be whole-vehicle equipment, in-vehicle modules, vehicles, on-board units (OBU), roadside units (RSU), in-vehicle infotainment systems (or in-vehicle transmitting units) (telematics boxes, T-boxes), chips, or systems on chips (SOCs), etc. These chips or SOCs can be installed in vehicles, OBUs, RSUs, or T-boxes.

[0080] In this application embodiment, the device for implementing the functions of the terminal device can be the terminal device itself, or a device capable of supporting the terminal device in implementing the functions, such as a chip system or a combination of devices or components capable of implementing the functions of the terminal device. This device can be installed in the terminal device. The embodiments of this application do not limit the specific technology or device form used in the terminal device. For example, in this application embodiment, the terminal device can be in the form of a tag, or it can be in other terminal forms.

[0081] Network devices and / or terminal devices can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water; or in the air on aircraft, balloons, and satellites. This application does not limit the application scenarios of the network devices and terminal devices. They can be deployed in the same or different scenarios; for example, both network devices and terminal devices can be deployed on land simultaneously; or, network devices can be deployed on land and terminal devices on water, etc., and so on.

[0082] In the description of the embodiments of this application, a "reader" will be used as a network device and an "A-IoT device" will be used as a terminal device. Both the reader and the A-IoT device have the function of sending and receiving information.

[0083] To facilitate understanding of the embodiments of this application, the terminology used in this application is first briefly explained. Optionally, the explanation of some terms can also be found in the 3GPP standard protocols. It should be understood that the technical terms in this application are for illustrative purposes only and not as limiting. For example, as technology evolves, technical terms may also change; where the technical meaning remains the same, other technical terms should also apply to this application.

[0084] The random access procedure related to this application is described below:

[0085] 1. Non-contention-based random access procedure

[0086] In IoT systems, contention-based random access (CBRA) and contention-free random access (CFRA) are the core mechanisms for establishing connections between terminals and network devices. Whether a terminal device executes CBRA or CFRA depends on the random access event that triggers it and the random access resources configured for the terminal device by the access network device.

[0087] During the CFRA process, if the terminal device meets the CFRA conditions, it will send the Device ID and data to the reader using dedicated random access occasions. In other words, the access occasions used to send the random access request are dedicated time-frequency resources indicated by the paging message, and there is no contention during this process.

[0088] 2. Contention-based random access procedure

[0089] Figure 2 This diagram illustrates the contention-based random access process between the Reader and the Device.

[0090] For example, in an IoT system, when a Reader wants to communicate with one or more Devices, the Reader can first send a paging message to trigger one or more Devices to compete for random access. Data transmission only occurs after successful random access. When a paging message triggers multiple Devices to initiate random access, these Devices compete for random access. Specifically, as... Figure 2 As shown, the process may include the following steps S21 to S27:

[0091] S21, the Reader sends a paging message to trigger one or more Devices to initiate random access. The paging message can be a broadcast message, and it indicates the number of subsequent random access occasions.

[0092] S22, the target device receives the Paging message, randomly selects one random access occasion from the multiple random access occasions indicated in the Paging message, and generates a random identity identifier.

[0093] S23, the target device sends the random ID on the random access occasions. This message can be called "Msg1".

[0094] S24, the Reader sends a response message (Random ID Response) to the target Device, which may contain the random ID of the Device. This response message (Random ID Response) may be called "Msg2".

[0095] S25, the target device receives the response message (Random ID Response). If the random ID contained in the response message (RandomID Response) is the same as the random ID it sent, it confirms that the random access was successful.

[0096] S26, the Device sends the device identifier (ID) and service-related data to the Reader. This message can be called "Msg3".

[0097] After successful random access, the Device can send the device identifier (ID) and service-related upper-layer data to the Reader. Within an access cycle, if multiple Devices fail to transmit upper-layer data to the Reader, the Reader can indicate the ID information of the devices that failed to transmit upper-layer data through a negative acknowledgment (NACK) message.

[0098] As described above, NACK messages need to carry multiple device access stratum identifiers (AS IDs) to identify devices that have failed to transmit. The AS ID is a unique and persistent "official identity card" for a device.

[0099] Figure 3 This is a schematic diagram of the structure of a NACK message. For example, as shown below... Figure 3 As shown, NACK messages can be organized in units of octets, specifically including the following:

[0100] The first octet (Option 1): Contains the message type for relay-to-DU (R2D), called the "R2D Message Type," used to identify the type of the current message. Here, it's a NACK message, used to inform the Device that the current Reader has not correctly received or processed the upper-layer data. The remaining part is the R2D transport block size (TBS), the beginning of the R2D TBS, indicating the size of the transport block (TB) corresponding to this transmission, used by the Device side to match the configuration of the original transmission.

[0101] The second octet (option 2): continues the "R2D TBS" field (R2D transport block size (continued)) and contains multiple reserved bits. These are used to carry the remaining TBS bits when the TBS value is too long, ensuring complete transmission. "R" stands for reserved bits, a field reserved for future protocol expansions. In the current version, it is fixed with 0 and does not carry any valid information.

[0102] Starting from the third octet (option 3): the AS ID of Device #1. Starting from the third octet, an optional, expandable list of AS IDs for one or more Devices can be included to enumerate all devices that have failed to transmit, such as the AS ID of Device #2 in option 4, etc., which will not be listed here.

[0103] If a NACK message carries the AS IDs of multiple devices, the traditional AS ID uses a fixed 16-bit length design. As the number of access devices in a multicast scenario continues to increase, the length of the NACK message will increase proportionally with the number of devices. For example, for each additional device that fails to transmit, the NACK message needs to carry an additional 16 bits of AS ID information. Excessive redundant bits occupy a large amount of air interface transmission resources, reduce spectrum utilization, and lead to a waste of transmission resources. A large number of NACK messages can cause air interface transmission congestion and affect the overall network transmission efficiency.

[0104] To address the aforementioned issues, this application provides a communication method that breaks through the limitation of each terminal using a traditional fixed 16-bit AS ID in the NACK message. This method allows for flexible selection of terminal access identifiers with different bit counts, adapts to more scenarios, saves communication resources, and reduces the complexity of data processing.

[0105] The following detailed explanation of the solution provided in this application, in conjunction with the corresponding flowcharts, illustrates the method. 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 in this interactive illustration to demonstrate the method; however, 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 those devices, or they can be logic modules or software capable of implementing all or part of the functions of those devices.

[0106] 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.

[0107] Figure 4 This is a schematic diagram of an example communication method 400 provided in an embodiment of this application. It can be understood that... Figure 4 The first terminal (Device#1) in the system can be Figure 1 Any A-IoT terminal in the context can also refer to a device within a device (such as a processor, chip, or chip system). A reader can be... Figure 1Any access network device, or a device within an access network device (such as a processor, chip, or chip system).

[0108] like Figure 4 As shown, method 400 includes the following steps:

[0109] S401, the first terminal sends a first message to the reader / writer, the first message including the random identification of the first terminal, and the reader / writer receives the first message from the first terminal accordingly.

[0110] It should be understood that "first news" can be interpreted as the aforementioned Figure 2 The "Msg1" mentioned in the document can also be called a "random access request" or "random access message." This Msg1 contains a random identifier (random ID) for the first terminal. This random identifier (random ID) is used to identify the first terminal during random access. Before the network side completes the authentication of the first terminal, the random ID is a unique temporary identifier between the first terminal and the reader / writer. Typically, the random ID can be a 16-bit or 32-bit random number.

[0111] It should also be understood that prior to S401, it may include... Figure 2 The process described in S21 and S22 is as follows: for example, the Reader sends a paging message, which triggers one or more Devices to initiate random access. The first terminal can randomly select one random access resource from the multiple random access resources indicated by the paging message and then send a random identity identifier through the random access resource.

[0112] S402, the reader sends a second message to the first terminal. The second message is a response message to the first message. The second message includes a first access stratum identifier, which is determined based on the number of terminals that initiate random access to the reader and the random identity identifier of the first terminal. The first access stratum identifier is associated with the random identity identifier of the first terminal. Accordingly, the first terminal receives the second message from the reader.

[0113] It should be understood that "second message" can be interpreted as the aforementioned Figure 2 The “Msg2” described in S24 can also be called “response message for random access request” or “random access response message”.

[0114] In this embodiment of the application, the second message may be different from the description in S25 above. The second message includes a first access layer identifier, which is different from the random ID.

[0115] Optionally, the first access layer identifier is determined based on the number of terminals that initiate random access to the reader and the random identity identifier of the first terminal, and the first access layer identifier is associated with the random identity identifier of the first terminal.

[0116] Specifically, after receiving and parsing Msg1 sent by one or more devices, the Reader can accumulate and count the number of valid Devices in the current access period, for example, the number of valid Devices is denoted as D, and further determine the target number of bits of the first access layer identifier based on the value range of D.

[0117] The following describes several possible formats for determining the first access stratum identifier:

[0118] Case 1

[0119] In one possible implementation, when the number of terminals initiating random access to the reader is less than or equal to a first threshold, the first access layer identifier has a first number of bits.

[0120] Optionally, the first threshold can be 16, and the first number of bits can be 4 bits.

[0121] It should be understood that Case 1 applies to small-scale scenarios, such as home IoT, small workshops, etc., containing 16 or fewer valid Devices. When the number of valid Devices D in the current access period is less than or equal to 16, the reader can assign a 4-bit First Access Layer Identifier, or simply 4-bit AS ID, to each Device based on the number of valid Devices D.

[0122] For example, when the number of valid devices D is less than or equal to 16, the first access layer identifier for the 1st to 16th terminals is a 4-bit AS ID. Specifically, this 4-bit AS ID can take the following format:

[0123] The first access layer identifier of the first terminal is: 0000;

[0124] The first access layer identifier of the second terminal is: 0001;

[0125] ...;

[0126] The first access layer identifier of the 16th terminal is: 1111.

[0127] Accordingly, the reader returns a second message, including the first access layer identifier, to each device. The second message may include at least "4-bit AS ID + 4-bit all-zero + 8-bit random ID". In other words, in addition to the first access layer identifier, the second message may also include relevant information for indicating that the first access layer identifier is associated with a random ID.

[0128] Optionally, the 8-bit random ID can be obtained based on the random ID of each terminal. For example, the 8-bit random ID can be taken from the last eight bits or the first eight bits of the random ID of each terminal device, or the 8-bit random ID can be obtained by compressing the random ID of each terminal. This application embodiment does not limit this.

[0129] For example, the second message returned by the reader to each terminal may include:

[0130] The second message content of the first terminal: 0000 + 0000 + 8-digit random ID;

[0131] The second message content of the second terminal: 0001 + 0000 + 8-digit random ID;

[0132] ...;

[0133] The second message content for the 16th user: 1111 + 0000 + 8-digit random ID.

[0134] In the above manner, the information used to identify the device ID in the second message returned by the reader to the device is still 16 bits, without increasing the number of bits; and through this 16-bit content, a one-to-one correspondence can be established between the newly allocated first access layer identifier and the original random ID, such as a one-to-one correspondence between a 4-bit AS ID and an 8-bit random ID. In this way, after receiving the second message, the device can determine whether it is its own random access response message based on the 8-bit random ID, and can also obtain the 4-bit AS ID allocated to it by the reader.

[0135] Case 2

[0136] In one possible implementation, when the number of terminals initiating random access to the reader is greater than a first threshold and less than or equal to a second threshold, the first access layer identifier has a second number of bits.

[0137] Wherein, the first threshold is less than the second threshold, and the first bit length is less than or equal to the second bit length.

[0138] Optionally, the first threshold can be 16, the second threshold can be 256, and the second number of bits can be 8 bits.

[0139] It should be understood that scenario 2 applies to large-scale scenarios, such as large factories and smart parks, containing 17 to 256 valid devices. When the number of valid devices D in the current access period is greater than 16 and less than or equal to 256, the reader can assign an 8-bit first access layer identifier, or simply an 8-bit AS ID, to each device based on the number of valid devices D.

[0140] For example, when the number of valid devices D is greater than 16 and less than or equal to 256, the first access layer identifier of the 17th to 256th terminals is an 8-bit AS ID. Specifically, this 8-bit AS ID can take the following format:

[0141] The first access layer identifier of the 17th terminal is: 0000 0001;

[0142] The first access layer identifier of the 18th terminal is: 0000 0010;

[0143] ...;

[0144] The first access layer identifier of the 256th terminal is: 1111 1111.

[0145] Accordingly, the reader will return a second message, including the first access layer identifier, to each device. This second message may include at least "8-bit AS ID + 8-bit random ID".

[0146] Optionally, the 8-bit random ID can be obtained based on the random ID of each terminal. For example, the 8-bit random ID can be taken from the last eight bits or the first eight bits of the random ID of each terminal device, or the 8-bit random ID can be obtained by compressing the random ID of each terminal. This application embodiment does not limit this.

[0147] For example, the second message returned by the reader to each terminal may include:

[0148] The second message content of the 17th terminal: 0000 0001 + 8-bit random ID;

[0149] The second message content of the 18th terminal: 0000 0010 + 8-digit random ID;

[0150] ...;

[0151] The second message content of the 256th terminal: 1111 1111 + 8-digit random ID.

[0152] In the above manner, the information used to identify the device ID in the second message returned by the reader to the device is still 16 bits, without increasing the number of bits; and through this 16-bit content, a one-to-one correspondence can be established between the newly allocated first access layer identifier and the original random ID, such as a one-to-one correspondence between an 8-bit AS ID and an 8-bit random ID. In this way, after receiving the second message, the device can determine whether it is its own random access response message based on the 8-bit random ID, and can also obtain the 8-bit AS ID allocated to it by the reader.

[0153] Case 3

[0154] In one possible implementation, when the number of terminals initiating random access to the reader exceeds a second threshold, the first access layer identifier is a random identity identifier of the first terminal.

[0155] It should be understood that Case 3 applies to ultra-large-scale scenarios and is compatible with more extreme situations. When the number of valid Devices D in the current access cycle is greater than 256, the first access layer identifier can be a 16-bit AS ID.

[0156] Optionally, the 16-bit AS ID can be obtained based on the random ID of each terminal. For example, the 16-bit AS ID can be partially taken from the random ID of each terminal device and partially regenerated. For instance, 8 bits of the 16-bit AS ID are taken from the random ID of the terminal device, and the other 8 bits are newly generated information. After the first terminal receives the second message, it can determine whether it is associated with its own random ID based on the 16-bit AS ID, thereby determining whether the random access was successful.

[0157] Alternatively, the 16-bit AS ID can be obtained by processing the random ID of each terminal using a preset processing algorithm. After processing and conversion, a 16-bit AS ID can be obtained. In other words, there is a preset conversion relationship between the random ID and the 16-bit AS ID. This application embodiment does not limit the preset processing algorithm. After receiving the second message, the first terminal can also perform conversion processing on the 16-bit AS ID to determine whether it is associated with its own random ID, thereby determining whether the random access was successful.

[0158] Alternatively, if the random number (random ID) can meet the current requirements, the reader can directly use the random ID of some terminals as the 16-bit AS ID. This application does not limit this.

[0159] For example, when the number of valid devices D is greater than 256, the first access layer identifier of the 257th terminal is a 16-bit AS ID.

[0160] For example, the second message returned by the reader to each terminal may include:

[0161] Terminal 257: 16-bit AS ID

[0162] Terminal 258: 16-bit AS ID

[0163] ...;

[0164] Terminal number 65536: 16-bit AS ID.

[0165] By using the above method, when the number of valid Devices D in the current access period is greater than 256, choosing to use a 16-bit random ID as the identity identifier for each terminal can avoid effectively distinguishing the identity of each terminal and avoid duplicate identifiers for multiple terminals.

[0166] Based on the above possible scenarios, the Reader can accumulate the number of valid Devices in the current access period by receiving and parsing multiple Msg1s, and then determine the target number of first access layer identifiers for each terminal according to the range of D values. This allows the Reader to allocate different numbers of AS IDs to each terminal based on different scenarios and the number of valid terminals.

[0167] After receiving the second message, the first terminal can parse it to obtain the newly assigned first access layer identifier and 8-bit random ID from the reader. This allows it to establish a one-to-one correspondence between the newly assigned first access layer identifier and the original random ID. Thus, after receiving the second message, the device can determine whether it is its own random access response message based on the 8-bit random ID, and also obtain the first access layer identifier assigned to it by the reader. This provides a foundation for simplifying the NACK message content in the future.

[0168] S403, if the reader does not receive upper-layer service data from the first terminal within a preset period, it sends a negative acknowledgment message to the first terminal. The negative acknowledgment message includes the first access layer identifier. Accordingly, the first terminal receives the negative acknowledgment message from the reader.

[0169] In S402, after the first terminal confirms successful random access, it can send data related to upper-layer services, namely "Msg3", to the Reader.

[0170] If the Reader does not receive upper-layer service-related data from the first terminal during the current access period, it indicates that the data transmission process with the first terminal has failed. The Reader identifies all terminals that experienced transmission failures during this access period and indicates the information of these multiple devices that experienced upper-layer data transmission failures through a NACK message. In other words, a NACK message must carry the device identifiers of multiple devices.

[0171] The above describes the implementation process of a terminal. During an access period, multiple terminals may initiate a random access process to the reader. Figure 5 The process for multiple terminals is described accordingly.

[0172] Figure 5 This is a schematic diagram of another communication method 500 provided in an embodiment of this application. It can be understood that... Figure 5 The first terminal (Device #1) and the second terminal (Device #2) can be Figure 1 Any A-IoT terminal in the context can also refer to a device within a device (such as a processor, chip, or chip system). A reader can be... Figure 1 Any access network device, or a device within an access network device (such as a processor, chip, or chip system).

[0173] like Figure 5 As shown, method 500 includes the following steps:

[0174] S501, the reader sends a paging message to the first terminal; correspondingly, the first terminal receives the paging message sent by the reader.

[0175] S502, the first terminal sends a first message to the reader; correspondingly, the reader receives the first message sent by the first terminal.

[0176] S503, the reader sends a second message to the first terminal; correspondingly, the first terminal receives the second message sent by the reader.

[0177] The above S501 to S503 correspond to the processes S401 and S402 in the method 400 described above, which is the random access process of the first terminal. After the random access is successful, the first terminal can transmit data to the reader.

[0178] S504, the reader sends a paging message to the second terminal; correspondingly, the second terminal receives the paging message sent by the reader.

[0179] S505, the second terminal sends a first message to the reader; correspondingly, the reader receives the first message sent by the second terminal.

[0180] S506, the reader sends a second message to the second terminal; correspondingly, the second terminal receives the second message sent by the reader.

[0181] The above S504 to S505 correspond to the processes S401 and S402 in the method 400 described above, which is the random access process of the second terminal. After the random access is successful, the second terminal can transmit data to the reader.

[0182] It should be understood that the embodiments of this application may also include random access procedures initiated by more terminals to the reader. After successful random access, each terminal can transmit data to the reader. Within an access cycle, if the Reader does not receive upper-layer service-related data sent by some terminals, it proves that the data transmission process with those terminals has failed. The Reader identifies all terminals whose transmission failed within the access cycle and indicates the information of these multiple Devices whose upper-layer data transmission failed through a NACK message. In other words, a NACK message needs to carry the device identifiers of multiple Devices, corresponding to process S507:

[0183] S507, the reader sends NACK messages to multiple terminals. The NACK message may contain the access layer identifier of each terminal that has experienced all data transmission failures during the current access period.

[0184] In this embodiment, the NACK message may include the first access stratum identifier described above. Since the first access stratum identifier may be the 4-bit AS ID, 8-bit AS ID, or 16-bit AS ID described above, when the NACK message includes access stratum identifiers of multiple terminals, the NACK message may also correspond to different format contents, thereby helping the terminal obtain the corresponding access stratum identifier through different format contents.

[0185] The following describes several possible formats for NACK messages:

[0186] Format 1

[0187] In one possible implementation, the negative acknowledgment message may further include first indication information, which indicates whether the first access layer identifier is obtained through compression processing, and the first indication information is also used to indicate the target number of bits corresponding to the first access layer identifier.

[0188] Figure 6This is a schematic diagram of the structure of an example NACK message provided in an embodiment of this application.

[0189] For example, such as Figure 6 As shown, two bits of first indication information can be added to the reserved bits R1 and R2 of the second octet (option 2) of the NACK message. The two bits of first indication information can simultaneously indicate whether the first access layer identifier is obtained through compression processing, and the first indication information is also used to indicate the target number of bits corresponding to the first access layer identifier.

[0190] Table 1 provides an example of the content description of the first instruction information. As shown in Table 1, the fields of the first instruction information are located as follows: Figure 6 The indicator bits R1+R2 in the NACK message are 2 bits long; the 2 bits can include 00, 01, 10, and 11. Specifically, 00 indicates that the terminal identifier in the NACK message is disabled for compression and the terminal identifier is a 16-bit AS ID; 01 indicates that the terminal identifier in the NACK message is enabled for compression and the terminal identifier is a 4-bit AS ID; 10 indicates that the terminal identifier in the NACK message is enabled for compression and the terminal identifier is an 8-bit AS ID; and 11 indicates that the terminal identifier in the NACK message is enabled for compression and the terminal identifier is at least a 16-bit AS ID.

[0191] Table 1

[0192]

[0193] In the above format, the number of bits occupied by the compression enable and the terminal's AS ID are uniformly carried by 2 bits, which can reduce the overhead of the indicator bits.

[0194] The first terminal can obtain access layer identification information corresponding to one or more terminals from the NACK message according to the first indication information. Specifically, the AS IDs of N terminals can be sequentially compressed from the third octet (option 3) onwards in the NACK message. After receiving the NACK message, the first terminal can obtain the AS IDs of the N terminals according to the number of bits occupied by the AS ID indicated by the first indication information, and then further determine whether its own AS ID exists in the NACK message. For example, if the AS ID included in the NACK message is XXXXXXXXXXXXXXXXXXXXXXXXX, and the AS ID indicated by the first indication information is a 4-bit AS ID, then the first terminal can obtain the AS IDs of the N terminals according to XXXXXXXXXXXX… When its own AS ID exists among the AS IDs of multiple terminals, it is determined that the data transmission of the first terminal has failed, and random access can be initiated again, etc. This application embodiment does not limit this.

[0195] Format 2

[0196] In another possible implementation, the negative acknowledgment message may also include a first indication information and a second indication information. The first indication information is used to indicate whether the first access layer identifier is obtained through compression processing; the second indication information is used to indicate the target number of bits corresponding to the first access layer identifier.

[0197] Unlike Format 1, Format 2 can use two different indication messages. The first indication message is used to indicate compression enable; the second indication message is used to indicate the number of bits occupied by the terminal's AS ID.

[0198] For example, Table 2 provides an example of the content description of a first instruction message and a second instruction message. As shown in Table 2, the field positions of the first instruction message are as follows: Figure 6 The indicator bit R1 in the NACK message is 1 bit long; this 1-bit information can include 0 and 1. 0 indicates that compression is disabled for the terminal identifier in the NACK message, and 1 indicates the compressed ASID used by the terminal identifier in the NACK message. Furthermore, the field position of the second indicator information is... Figure 6 The indicator bits R2+R3 in the NACK message are 2 bits long; the 2 bits can include 00, 10, and 11. Specifically, 00 indicates that the terminal identifier in the NACK message is a 4-bit AS ID; 10 indicates that the terminal identifier is an 8-bit AS ID; and 11 indicates that the terminal identifier in the NACK message is at least a 16-bit AS ID.

[0199] Table 2

[0200]

[0201] The first terminal can determine whether the first access layer identifier is obtained through compression processing based on the first indication information; and obtain access layer identifier information corresponding to one or more terminals from the NACK message based on the second indication information. Specifically, the NACK message can sequentially compress the AS IDs of N terminals starting from the third octet (option 3). After receiving the NACK message, the first terminal can obtain the AS IDs of the N terminals according to the number of bits occupied by the AS ID indicated by the second indication information, and further determine whether its own AS ID exists in the NACK message.

[0202] As another example, Table 3 provides a different description of the content of the first and second instruction information. As shown in Table 3, the fields of the first instruction information are located as follows: Figure 6The indicator bit R1 in the NACK message is 1 bit long; this 1-bit information can include 0 and 1. 0 indicates that compression (i.e., the traditional 16-bit AS ID) is disabled for the terminal identifier in the NACK message, and 1 indicates that bitmap indication is enabled for the terminal identifier in the NACK message. Furthermore, the field position of the second indicator information is... Figure 6 The indicator bit R2 is a 16-bit bitmap, and the position of "1" in the 16-bit bitmap accurately indicates the effective length of the ASID.

[0203] For example, a 16-bit bitmap is: 0000000000011111, where the position 1 occupies 5 positions. The corresponding ASID bit length is L = 5 bits. Therefore, for N terminals with failed transmissions, the total length of the ASID list is L × N bits.

[0204] Table 3

[0205]

[0206] In the above format, the position of "1" in the 16-bit bitmap precisely indicates the effective length of the AS ID. This format can support AS IDs with any length from 1 bit to 16 bits, and can match more scenarios.

[0207] The NACK message can sequentially compress the AS IDs of N terminals starting from the third octet (option 3). After the first terminal receives the NACK message, it can obtain the AS IDs of the N terminals according to the number of bits occupied by the AS ID indicated by the length indicator bitmap, and then further determine whether the NACK message contains its own AS ID.

[0208] Format 3

[0209] In another possible implementation, the negative acknowledgment message may also include a first indication information, a second indication information, and a third indication information. The first indication information is used to indicate whether the first access layer identifier is obtained through compression processing; the second indication information is used to indicate the start bit corresponding to the first access layer identifier; and the third indication information is used to indicate the end bit corresponding to the first access layer identifier.

[0210] Unlike formats 1 and 2, format 3 can use three different indication messages. The first indication message is used to indicate compression enable; the second indication message is used to indicate the start position of valid bits (start); the third indication message is used to indicate the end position of valid bits (end), and the effective length L = (end - start + 1) bits.

[0211] For example, Table 4 provides a description of the content of a first instruction message, a second instruction message, and a third instruction message. As shown in Table 4, the field positions of the first instruction message are as follows: Figure 6 The indicator bit R1 in the NACK message is 1 bit long; this 1 bit can include 0 and 1. 0 indicates that compression is disabled for the terminal identifier in the NACK message, and 1 indicates that the terminal identifier in the NACK message uses a compression AS ID. Furthermore, the field position of the second indicator information is... Figure 6 The indicator bit R2, with a length of 4 bits, indicates the start position of the valid bits. The third indicator information field is located at... Figure 6 The indicator bit R3, which is 4 bits long, indicates the end position of the valid bits.

[0212] Table 4

[0213]

[0214] The first terminal can determine whether the first access layer identifier is obtained through compression processing based on the first indication information; based on the second and third indication information, it can determine the target number of bits corresponding to the first access layer identifier, and obtain access layer identifier information corresponding to one or more terminals from the NACK acknowledgment message based on the target number of bits. Specifically, the NACK message can sequentially compress the AS IDs of N terminals starting from the third octet (option 3). After receiving the NACK message, the first terminal can obtain the AS IDs of N terminals according to the number of bits occupied by the AS ID determined by the second and third indication information, and further determine whether its own AS ID exists in the NACK message.

[0215] When the NACK message includes the first access layer identifier, it is determined that the upper-layer service data transmission sent by the first terminal to the reader has failed, and the random access procedure is re-initiated to the reader; when the NACK message does not include the first access layer identifier, it is determined that the upper-layer service data transmission sent by the first terminal to the reader has succeeded.

[0216] It should be noted that the method of using compressed AS IDs to identify multiple terminals in the NACK message described above can be applied to each access cycle, or in other words, within each access-to-feedback cycle. The reader can re-count the number of terminals within that access cycle and further determine the method for allocating access layer identifiers based on the range of terminal counts. Alternatively, a timer can be set on the reader side. Within the timer's period, the method for allocating access layer identifiers can be determined based on the range of terminal counts, the target number of bits for the new AS ID can be determined, and a compressed AS ID can be reassigned to each terminal within the current period.

[0217] As described above, this application proposes a dynamic adjustment mechanism for the adaptive number of AS ID bits. The Reader can flexibly determine the length of the AS ID by counting the number of connected terminals D and using a fallback rule of using 4-bit AS ID when D is less than or equal to 16, 8-bit AS ID when 16≤D≤256, and 16-bit AS ID when D is greater than 256. This breaks through the limitation of the traditional fixed 16-bit AS ID and realizes a compression strategy of "demand matching".

[0218] On the other hand, the embodiments of this application also design a frame structure for a compatible NACK message, which only adds 1 bit of compression enable bit and 2 bit of indicator bit (3 bits in total) of control compression logic, without the need to reconstruct the existing NACK message multiplexing framework.

[0219] On the other hand, this application also establishes a dual-trigger AS ID periodic update mechanism based on "period + number of devices" to avoid identifier conflicts caused by fluctuations in the number of devices, while retaining a 16-bit AS ID fallback mode to cope with ultra-large-scale scenarios. In terms of technical benefits, the AS ID can be compressed by 75% in small-scale scenarios (D less than or equal to 16) and by 50% in large-scale scenarios (16≤D≤256), significantly reducing the length of NACK messages and the air interface transmission load, and improving transmission efficiency.

[0220] In summary, the embodiments of this application overcome the limitation of using a traditional fixed 16-bit AS ID for each terminal in the NACK message. Instead of using a static, fixed-bit compressed AS ID, the access identifier of the terminal can be flexibly selected based on the number D of terminals accessing the reader, and different compression strategies can be matched according to the range of values ​​for the number D. This method can adapt to more scenarios, significantly reducing the length of the NACK message and the air interface transmission load, thus improving transmission efficiency.

[0221] Furthermore, this application's embodiments use a small number of reserved indicator bits R to achieve compression control, eliminating the need to reconstruct the existing NACK multiplexing framework. Moreover, the rules for updating and allocating AS IDs based on the dual trigger conditions of "access period + number of terminals" avoid identifier conflicts caused by fluctuations in the number of terminals, while retaining the traditional 16-bit AS ID fallback mode. This ensures compatibility in ultra-large-scale scenarios with D ≥ 256 terminals, reducing the risk of insufficient compressed AS ID identification capabilities. In terms of compatibility, it is directly compatible with the NACK multiplexing mechanisms of other proposals without requiring significant modifications to the terminal hardware or protocol stack. The 16-bit fallback mode ensures adaptation to ultra-large-scale scenarios, reducing the cost of standard upgrades and terminal adaptation.

[0222] It should be understood that Figures 1 to 6 The flowcharts or scene diagrams shown are for illustrative purposes only and are not intended to limit the embodiments of this application to the examples illustrated. In fact, those skilled in the art can interpret the embodiments based on... Figures 1 to 6 The examples in the document can be transformed into equivalent ways to obtain more implementations.

[0223] The above text combined Figures 1 to 6 This document describes in detail the communication method provided in the embodiments of this application. The following will combine... Figures 7 to 8 The device embodiments of this application are described in detail below. It should be understood that the communication device of this application embodiment can execute the various communication methods of the foregoing embodiments of this application, that is, the specific working processes of the various products below can be referred to the corresponding processes in the foregoing method embodiments.

[0224] In the embodiments described above, the terminal device may execute some or all of the steps in each embodiment; the network device may execute some or all of the steps in each embodiment. These steps or operations are merely examples, and the embodiments of this application may also perform other operations or variations thereof. Furthermore, the steps may be executed in different orders as presented in the embodiments, and it is not necessary to execute 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.

[0225] Figure 7 This is a schematic block diagram of a communication device provided in an embodiment of this application. Figure 7 As shown, the communication device 700 may include a communication unit 720. The communication unit 720 can implement corresponding communication functions, which can be internal communication functions of the communication device 700 or communication functions between the communication device 700 and other devices. Optionally, the communication unit 720 may also be referred to as a communication interface or transceiver unit.

[0226] Optionally, the communication device 700 may further include a processing unit 710, which can perform corresponding processing functions.

[0227] Optionally, the communication device 700 may further include a storage unit, which can be used to store instructions and / or data; the processing unit 710 can read the instructions and / or data in the storage unit so that the communication device 700 can implement the aforementioned method embodiments.

[0228] In one possible design, the communication device 700 may correspond to the terminal (e.g., Device #1, Device #2) in the above method embodiments, or a component (such as a circuit, chip, or chip system) configured in the terminal device. The communication device 700 can be used to execute the steps or processes performed by the terminal device in any of the above method embodiments.

[0229] Alternatively, the communication device 700 may correspond to a network device (e.g., a reader) in the above method embodiments, or a component (such as a circuit, chip, or chip system) configured in a network device. The communication device 700 can be used to execute the steps or processes performed by the network device in any of the above method embodiments.

[0230] For example, the communication unit 720 is used to implement Figure 4 The S401-S403 process described herein, or, used to implement Figure 5 The related processes S501-S507 described herein are implemented by the processing unit 710. Figure 4 or Figure 5 The AS ID allocation process described in the previous section will not be repeated here for the sake of simplicity.

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

[0232] Figure 8 This is another schematic block diagram of the communication device 800 provided in the embodiments of this application. The communication device 800 may be a chip, chip system, or processor, etc., used by a terminal or network device to implement the above-described methods. The communication device 800 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.

[0233] like Figure 8 As shown, the communication device 800 may include one or more processors 810, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 810 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 800 (e.g., a base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.

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

[0235] In another alternative design, the communication device 800 may include a communication interface 820 for implementing receiving and transmitting functions. For example, the communication interface 820 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.

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

[0237] 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.

[0238] In one implementation, the communication device 800 may correspond to the terminal device in the above method embodiments and may be used to execute the various steps and / or processes executed by the terminal device in the above method embodiments. The processor 810 may be used to execute instructions stored in the memory 830, and when the processor 810 executes the instructions stored in the memory, the processor 810 is used to execute the various steps and / or processes of the above method embodiments corresponding to the terminal device.

[0239] In another implementation, the communication device 800 may correspond to the network device 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 810 may be used to execute instructions stored in the memory 830, and when the processor 810 executes the instructions stored in the memory, the processor 810 is used to execute the various steps and / or processes of the above method embodiments corresponding to the network device.

[0240] 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.

[0241] 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.

[0242] 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.

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

[0244] According to the method provided in the embodiments of this application, this application also provides a communication system, which includes the aforementioned network device, a first terminal (e.g., Device #1), a second terminal (e.g., Device #2), etc.

[0245] 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 executed by the network device or the first terminal in any of the foregoing method embodiments.

[0246] According to the method provided in the embodiments of this application, this application also provides a computer-readable storage medium storing program code, which, when run on a computer, causes the computer to execute the various steps or processes executed by the network device or the first terminal in any of the foregoing method embodiments.

[0247] 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.

[0248] 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.

[0249] 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. A computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated.

[0250] 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.

[0251] 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.

[0252] In summary, the above are merely preferred embodiments of the technical solutions of this application and are 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, The method includes: The reader receives a first message from the first terminal, the first message including a random identity identifier of the first terminal; The reader sends a second message to the first terminal. The second message is a response message to the first message. The second message includes a first access layer identifier. The first access layer identifier is determined based on the number of terminals that initiate random access to the reader and the random identity identifier of the first terminal. The first access layer identifier is associated with the random identity identifier of the first terminal. If the reader does not receive upper-layer service data from the first terminal within a preset period, it sends a negative confirmation message to the first terminal, the negative confirmation message including the first access layer identifier.

2. The method according to claim 1, characterized in that, The first access layer identifier is determined based on the number of terminals initiating random access to the reader and the random identity identifier of the first terminal, including: When the number of terminals initiating random access to the reader is less than or equal to a first threshold, the first access layer identifier has a first number of bits. When the number of terminals initiating random access to the reader is greater than the first threshold and less than or equal to the second threshold, the first access layer identifier has a second number of bits. When the number of terminals initiating random access to the reader exceeds the second threshold, the first access layer identifier is the random identity identifier of the first terminal. Wherein, the first threshold is less than the second threshold, and the first number of bits is less than or equal to the second number of bits.

3. The method according to claim 1 or 2, characterized in that, The negative confirmation message further includes first indication information, which is used to indicate whether the first access layer identifier is obtained through compression processing, and the first indication information is also used to indicate the target number of bits corresponding to the first access layer identifier.

4. The method according to claim 1 or 2, characterized in that, The negative confirmation message also includes a first indication information and a second indication information, wherein the first indication information is used to indicate whether the first access layer identifier is obtained through compression processing; The second indication information is used to indicate the target number of bits corresponding to the first access layer identifier.

5. The method according to claim 1 or 2, characterized in that, The negative confirmation message further includes a first indication information, a second indication information, and a third indication information, wherein the first indication information is used to indicate whether the first access layer identifier is obtained through compression processing; The second indication information is used to indicate the starting bit corresponding to the first access layer identifier; The third indication information is used to indicate the end bit corresponding to the first access layer identifier.

6. The method according to claim 1 or 2, characterized in that, If the reader does not receive upper-layer service data sent by the second terminal within the preset period, the negative confirmation message also includes a second access layer identifier. The second access layer identifier is determined based on the number of terminals that initiate random access to the reader and the random identity identifier of the second terminal, which is the terminal that initiates random access to the reader.

7. A communication method, characterized in that, The method includes: The first terminal sends a first message to the reader, the first message including the random identity identifier of the first terminal; The system receives a second message from the reader / writer. The second message is a response message to the first message. The second message includes a first access layer identifier. The first access layer identifier is determined based on the number of terminals that initiate random access to the reader / writer and the random identity identifier of the first terminal. The first access layer identifier is associated with the random identity identifier of the first terminal. Within a preset period, a negative confirmation message is received from the reader / writer. Based on the negative confirmation message, it is determined whether the upper-layer service data sent to the reader / writer has failed to be transmitted. The negative confirmation message carries access layer identification information corresponding to one or more terminals.

8. The method according to claim 7, characterized in that, The first access layer identifier is determined based on the number of terminals initiating random access to the reader and the random identity identifier of the first terminal, including: When the number of terminals initiating random access to the reader is less than or equal to a first threshold, the first access layer identifier has a first number of bits. When the number of terminals initiating random access to the reader is greater than the first threshold and less than or equal to the second threshold, the first access layer identifier has a second number of bits. When the number of terminals initiating random access to the reader exceeds the second threshold, the first access layer identifier is the random identity identifier of the first terminal. Wherein, the first threshold is less than the second threshold, and the first number of bits is less than or equal to the second number of bits.

9. The method according to claim 7 or 8, characterized in that, The negative confirmation message further includes first indication information, which is used to indicate whether the first access layer identifier is obtained through compression processing, and the first indication information is also used to indicate the target number of bits corresponding to the first access layer identifier. Furthermore, the method further includes: Based on the first indication information, the access layer identification information corresponding to the one or more terminals is obtained from the negative confirmation message.

10. The method according to claim 7 or 8, characterized in that, The negative confirmation message also includes a first indication information and a second indication information, wherein the first indication information is used to indicate whether the first access layer identifier is obtained through compression processing; The second indication information is used to indicate the target number of bits corresponding to the first access layer identifier; Furthermore, the method further includes: Based on the first indication information, determine whether the first access layer identifier is obtained through compression processing; According to the second instruction information, the access layer identification information corresponding to the one or more terminals is obtained from the negative confirmation message.

11. The method according to claim 7 or 8, characterized in that, The negative confirmation message further includes a first indication information, a second indication information, and a third indication information, wherein the first indication information is used to indicate whether the first access layer identifier is obtained through compression processing; The second indication information is used to indicate the starting bit corresponding to the first access layer identifier; The third indication information is used to indicate the end bit corresponding to the first access layer identifier; Furthermore, the method further includes: Based on the first indication information, determine whether the first access layer identifier is obtained through compression processing; Based on the second indication information and the third indication information, the target number of bits corresponding to the first access layer identifier is determined, and the access layer identifier information corresponding to the one or more terminals is obtained from the negative acknowledgment message based on the target number of bits.

12. The method according to claim 7, characterized in that, The step of determining whether the upper-layer service data sent to the reader failed to be transmitted based on the negative acknowledgment message includes: When the negative confirmation message includes the first access layer identifier, it is determined that the upper-layer service data transmission sent by the first terminal to the reader has failed, and the random access procedure is re-initiated to the reader. When the negative confirmation message does not include the first access layer identifier, it is determined that the upper-layer service data transmission sent by the first terminal to the reader / writer was successful.

13. A communication device, characterized in that, The communication device includes a module or unit for performing the method according to any one of claims 1 to 12.

14. A communication device, characterized in that, The device includes a processor and an interface circuit, the interface circuit being used to receive signals from other devices and transmit them to the processor or to send signals from the processor to other devices, the processor being used to implement the method as described in any one of claims 1 to 12 via logic circuits or executing code instructions.

15. A communication system, characterized in that, The communication system includes: a reader for performing the method of any one of claims 1 to 6 and a first terminal for performing the method of any one of claims 7 to 12.

16. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when run on a computer, enables the computer to perform the method of any one of claims 1 to 12.

Images