Communication method and apparatus

Abstract

The present application relates to the technical field of communications. Provided are a communication method and apparatus. The method comprises: receiving a first message, the first message comprising first information, and the first information indicating a first transport block size (TBS); and sending a second message, wherein if the first TBS is less than a first threshold, the second message comprises an access stratum identifier (AS ID) or a temporary identifier of a first apparatus. The method and apparatus can reduce air interface overheads and improve security.

Description

A communication method and apparatus

[0001] This application claims priority to Chinese patent applications filed on March 28, 2025, with application number 202510392982.1 and entitled "A Communication Method and Apparatus", and on May 9, 2025, with application number 202510601049.0 and entitled "A Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0003] In a communication system, each terminal device has a unique device identification (device ID). The terminal device reports its device ID to the network device, thereby enabling data storage. The terminal device can be an ambient internet of things (A-IoT) device, and the network device can be a reader.

[0004] However, the device identifier has a large number of bits, resulting in high air interface overhead. Furthermore, the device identifier is exposed to the air interface, leading to poor security. Summary of the Invention

[0005] To address the aforementioned technical problems, this application provides a communication method and apparatus that saves air interface overhead and offers high security. To achieve the above objectives, this application adopts the following technical solution:

[0006] Firstly, a communication method is provided. This method can be executed by a first device. The first device can be a terminal device, a component within the terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the terminal device's functions. The following description uses the first device as the executing entity. The method includes:

[0007] Receive a first message, the first message including first information indicating a first transport block size (TBS). Send a second message. Wherein, if the first TBS is less than a first threshold, the second message includes the access layer identifier (AS ID) or a temporary identifier of the first device.

[0008] Wherein, the first TBS is less than or equal to the first threshold, which can be understood as scheduling the transmission of the AS ID or temporary identifier of the first device.

[0009] The first TBS may also be described in other ways, such as the first payload size.

[0010] Based on the above technical solution, the first information indicates the first TBS, and the first device determines the identifier included in the second message based on the first TBS. For example, if the first TBS is less than the first threshold, the second message includes the AS ID or temporary identifier of the first device. Since the AS ID and temporary identifier of the first device correspond to the device identifier of the first device, the first device can report the AS ID or temporary identifier of the first device instead of reporting the device identifier, reducing the possibility of the device identifier being exposed over the air interface. Typically, the AS ID and temporary identifier of the first device have fewer bits, which helps to save air interface overhead.

[0011] In one possible design, the method further includes receiving a third message indicating that the AS ID be saved for use in subsequent processes without having to reassign the AS ID, thus saving air interface overhead.

[0012] Secondly, a communication method is provided. This method can be executed by a second device. The second device can be a network device, a component within the network device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the network device. The following description uses the second device as the executing entity. The method includes:

[0013] Send a first message, the first message including first information, the first information indicating a first transport block size (TBS). Receive a second message. Wherein, if the first TBS is less than a first threshold, the second message includes the access layer identifier (AS ID) or temporary identifier of the first device.

[0014] In one possible design, the method further includes sending a third message indicating that the AS ID be saved.

[0015] In conjunction with the first or second aspect, in one possible design, if the first TBS is greater than or equal to the first threshold, the second message includes a first identifier of the first device, the length of which is greater than the length of the AS ID and the length of the temporary identifier.

[0016] Wherein, the first TBS is greater than the first threshold, which can be understood as scheduling the transmission of the first identifier of the first device.

[0017] The term "length" can also be described in other ways, such as "size". For example, the length of the first identifier can be described as the size of the first identifier. The length of the AS ID can be described as the size of the AS ID. The length of the temporary identifier can be described as the size of the temporary identifier.

[0018] In one possible design, in conjunction with either the first or second aspect, the first identifier is a device identifier.

[0019] Since the first TBS is greater than or equal to the first threshold, the first device can report an identifier with a large number of bits, such as the first identifier of the first device, so that the network side can obtain the device identifier of the first device, thereby realizing services such as initial inventory.

[0020] In conjunction with the first or second aspect, in one possible design, the first message is used to page the first device or indicate contention resolution for the first device. For example, the first message is a paging message or a contention resolution message.

[0021] Thirdly, a communication method is provided. This method can be executed by a first device. The first device can be a terminal device, a component within the terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the terminal device's functions. The following description uses the first device as the executing entity.

[0022] The method includes:

[0023] Upon receiving first information indicating that the Access Layer Identifier (AS ID) of the first device is part of a second identifier, the second identifier including at least one of a first identifier, a temporary identifier, or a random identifier of the first device, wherein the length of the first identifier is greater than the length of the temporary identifier, the AS ID of the first device is determined based on the first information.

[0024] Wherein, the AS ID of the first device is a part of the second identifier, which can be understood as the AS ID of the first device being a truncated version of the second identifier, or the AS ID of the first device being a truncated identifier.

[0025] Based on the above technical solution, the first information indicates that the AS ID of the first device is part of the second identifier, so that the first device can determine its AS ID according to the first information, thereby realizing the allocation of the AS ID. That is to say, what is transmitted over the air interface is the first information, not the AS ID of the first device. The AS ID of the first device is 8 bits or 16 bits, while the first information has fewer bits, such as 1 bit, resulting in low air interface overhead.

[0026] In one possible design, the first identifier is a device identifier.

[0027] In one possible design, the first information includes at least one of the following: a paging message, a random access trigger message, a contention resolution message, or downlink data. The downlink data includes a command.

[0028] Fourthly, a communication method is provided. This method can be executed by a second device. The second device can be a network device, a component within the network device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the network device. The following description uses the second device as the executing entity.

[0029] The method includes:

[0030] First information is determined, indicating that the Access Layer Identifier (AS ID) of the first device is part of a second identifier, the second identifier including at least one of the first device's first identifier, a temporary identifier, or a random identifier, wherein the length of the first identifier is greater than the length of the temporary identifier. The first information is then sent to the first device.

[0031] In one possible design, the first identifier is a device identifier.

[0032] In one possible design, the first information includes at least one of the following: a paging message, a random access trigger message, a contention resolution message, or downlink data. The downlink data includes a command.

[0033] In one possible design, the method further includes receiving the AS ID from a third device.

[0034] In a contention-based random access (CBRA) scenario, the device identifier of the first device is included in the non-access stratum (NAS) packet. After receiving the NAS packet from the first device, the second device forwards the NAS packet to the third device. That is, the third device obtains the device identifier of the first device through the NAS packet, while the second device does not parse the NAS packet and cannot obtain the device identifier of the first device through it. Therefore, in this application, the third device provides identification information to the second device so that the second device can learn the AS ID of the first device for use in subsequent processes.

[0035] The technical effects of the fourth aspect and any of the design methods in the fourth aspect can be found in the technical effects of the different design methods in the third aspect, and will not be repeated here.

[0036] Fifthly, a communication method is provided. This method can be executed by a first device. The first device can be a terminal device, a component within the terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the terminal device's functions. The following description uses the first device as the executing entity.

[0037] The method includes:

[0038] Send first data. Receive first information. The first information indicates that the first data transmission failed, and the first information also indicates that the access stratum identifier (AS ID) be saved or released, or the first information includes the AS ID.

[0039] Based on the above technical solution, in the scenario where the first data transmission fails, the first information indicates both the failure of the first data transmission and whether to save the AS ID. For example, if the first information indicates to save the AS ID or includes the AS ID, it means that the first device needs to save the AS ID for use in subsequent processes. Alternatively, if the first information indicates to release the AS ID, it means that the first device needs to release the AS ID to save storage overhead.

[0040] In one possible design, the method further includes receiving a paging message. If the paging message includes the AS ID, second data is sent to achieve contention-free random access CFRA without needing to obtain the AS ID again.

[0041] The paging message includes the AS ID, which can be understood as the paging message paging the first device.

[0042] Sixthly, a communication method is provided. This method can be executed by a second device. The second device can be a network device, a component within the network device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the network device. The following description uses the second device as the executing entity.

[0043] The method includes:

[0044] A first data transmission of the first device is determined to have failed. A first message is sent, indicating that the first data transmission has failed, and the first message further indicates that the access layer identifier (AS ID) should be saved or released, or the first message includes the AS ID.

[0045] In one possible design, the method further includes: sending a paging message, the paging message including the AS ID; and receiving second data from the first device.

[0046] The technical effects of the sixth aspect and any of the design methods in the sixth aspect can be found in the technical effects of the different design methods in the fifth aspect, and will not be repeated here.

[0047] Seventhly, a communication method is provided. This method can be executed by a first device. The first device can be a terminal device, a component within the terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the terminal device's functions. The following description uses the first device as the executing entity.

[0048] The method includes:

[0049] A paging message is received, comprising Access Layer (AS) information and a paging identifier, wherein the AS information precedes the paging identifier, and the paging identifier ends at the least significant bit (LSB) of the paging message. The AS information and the paging identifier are determined based on the paging message.

[0050] Based on the above technical solution, the positions of the AS information and the paging identifier are constrained in the paging message. For example, the AS information is located before the paging identifier, and the format of the AS information is fixed. Therefore, even if the length of the paging identifier varies, the first device can still determine the paging identifier in the paging message. For example, it first reads the AS information with a fixed format in the paging message, and then the remaining part is the paging identifier, which is then delivered to upper layers. Based on this, the paging message does not need to indicate the length of the paging identifier or the length of the information delivered to upper layers, simplifying the design of the paging message and saving signaling overhead.

[0051] Eighthly, a communication method is provided. This method can be executed by a second device. The second device can be a network device, a component within the network device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the network device. The following description uses the second device as the executing entity.

[0052] The method includes:

[0053] Determine the paging message, which includes Access Layer (AS) information and a paging identifier. The AS information precedes the paging identifier, and the paging identifier ends at the least significant bit (LSB) of the paging message. Send the paging message.

[0054] In conjunction with the seventh or eighth aspect, in one possible design, the starting position of the AS information is the most significant bit (MSB) of the paging message.

[0055] In conjunction with the seventh or eighth aspect, in one possible design, the end position of the AS information is adjacent to the start position of the paging identifier.

[0056] In conjunction with the seventh or eighth aspect, in one possible design, the AS information includes at least one of the following: message type, or control information, or access resource indication.

[0057] In conjunction with the seventh or eighth aspect, in one possible design, the paging identifier (or paging identifier field) will be placed at the end of the paging message, in which case the paging identifier (or paging identifier field) does not need to have a length field set in the paging message.

[0058] In conjunction with the seventh or eighth aspect, in one possible design, the paging message does not contain Media Access Control (MAC) layer padding content, or the paging message does not contain Media Access Control (MAC) layer padding content of varying length.

[0059] The technical effects of the eighth aspect and any of the design methods in the eighth aspect can be found in the technical effects of the different design methods in the seventh aspect, and will not be repeated here.

[0060] Ninthly, a communication method is provided. This method can be executed by a first device. The first device can be a terminal device, a component within the terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the terminal device. The following description uses the first device as the executing entity.

[0061] The method includes:

[0062] Receive a first message, which includes a first access layer identifier (AS ID) and is a contention resolution message. Send first data. The first AS ID is the same as a second AS ID, which is stored in the first device.

[0063] Wherein, the first AS ID is the same as the second AS ID, which can be understood as the AS ID carried in the first message being the same as the AS ID stored in the first device, or the first message including the AS ID stored in the first device. This means that the first message also instructs the first device to transmit (or retransmit) the first data, or that the first device needs to transmit (or retransmit) the first data. Accordingly, the first device sends the first data to ensure data transmission performance.

[0064] In one possible design, the method further includes receiving a second message, which includes the second AS ID, before receiving the first message, to achieve AS ID allocation.

[0065] Tenthly, a communication method is provided. This method can be executed by a second device. The second device can be a network device, a component within the network device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the network device. The following description uses the second device as the executing entity.

[0066] The method includes:

[0067] Send a first message and a second message, both of which include the same Access Layer Identifier (AS ID). The first and second messages are contention resolution messages, and the second message is used to trigger the transmission of first data. Receive the first data.

[0068] Eleventhly, a communication method is provided. This method can be executed by a first device. The first device can be a terminal device, a component within the terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the terminal device's functions. The following description uses the first device as the executing entity.

[0069] The method includes:

[0070] Receive a paging message, the paging message including a network identifier. Send first data, the first data including a first identifier, the first identifier being part of a second identifier and not including the network identifier, the second identifier being the device identifier of the first device.

[0071] For different devices selected by the same paging message, the network identifier is the same in the device identifier of the different devices and is carried by the same paging message. Based on this, when the first device determines that it needs to respond to the paging message and sends the first data according to the network identifier included in the paging message, it can carry an incomplete device identifier in the first data, such as the first identifier, which at least does not include the network identifier, in order to save air interface overhead.

[0072] In one possible design, the paging message may also include a third-party identifier. The first identifier may not include the third-party identifier to further reduce air interface overhead.

[0073] In one possible design, the method further includes receiving first information indicating whether to report the first identifier. For example, the first information is included in the paging message to indicate whether to report the first identifier.

[0074] In a twelfth aspect, a communication method is provided. This method can be executed by a second device. The second device can be a network device, a component within the network device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the network device. The following description uses the second device as the executing entity.

[0075] The method includes:

[0076] Send a paging message, the paging message including a network identifier. Receive first data, the first data including a first identifier, the first identifier being part of a second identifier and not including the network identifier, the second identifier being the device identifier of the first device.

[0077] In one possible design, the paging message may also include a third-party identifier. The first identifier may not include the third-party identifier to further reduce air interface overhead.

[0078] In one possible design, the method further includes sending first information indicating whether to report the first identifier. For example, the first information is included in the paging message to indicate whether to report the first identifier.

[0079] The technical effects of the twelfth aspect and any of the design methods in the twelfth aspect can be found in the technical effects of the different design methods in the eleventh aspect, and will not be repeated here.

[0080] In a thirteenth aspect, a communication method is provided. This method can be executed by a first device. The first device can be a terminal device, a component within the terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the terminal device. The following description uses the first device as the executing entity.

[0081] The method includes:

[0082] Receive a paging message indicating at least two first values. Receive a first message indicating a second value, which is included among the at least two first values. Send first data. Receive second data during a first time period. The end time of the first time period is determined based on the transmission time of the first data and the second value, and the second data is response data to the first data.

[0083] In this context, for the first device, the transmission time of the first data can be understood as the sending time of the first data.

[0084] In other words, after the first device sends the first data, a second data transmission is expected as a response to the first data transmission, and the second data transmission is expected to occur within a first time period. The end time of the first time period is determined based on the transmission time of the first data and the second value. Since the second value is selected from at least two first values, the selection of the second value is more flexible and adaptable to the transmission of the second data, thereby helping to reduce power consumption on the first device side or enabling the first device to receive the second data in a timely manner.

[0085] In one possible design, the paging message further indicates at least two third values. The first message also indicates a fourth value, which is included among the at least two third values. The start time of the first time period is determined based on the transmission time of the first data and the fourth value.

[0086] In one possible design, the method further includes: starting a first timer, the runtime of which is the first time period.

[0087] In other words, during the operation of the first timer, the first device receives the second data from the second device. Since the operation of the first timer is determined based on the first time period, the power consumption of the timer operation can also be reduced.

[0088] In a fourteenth aspect, a communication method is provided. This method can be executed by a second device. The second device can be a network device, a component within the network device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the network device. The following description uses the second device as the executing entity.

[0089] The method includes:

[0090] A paging message is sent, indicating at least two first values. A first message is sent, indicating a second value, which is included among the at least two first values. First data is received. Second data is sent during a first time period. The end time of the first time period is determined based on the transmission time of the first data and the second value, and the second data is response data to the first data.

[0091] In this context, for the second device, the transmission time of the first data can be understood as the reception time of the first data.

[0092] The transmission time can be understood as the end time of the first data (e.g., postamble) or the start time of the first data (e.g., preamble).

[0093] In one possible design, the paging message further indicates at least two third values. The first message also indicates a fourth value, which is included among the at least two third values. The start time of the first time period is determined based on the transmission time of the first data and the fourth value.

[0094] The technical effects of any design method in aspect fourteen can be found in aspect thirteen and the technical effects of different design methods in aspect thirteen, and will not be repeated here.

[0095] In a fifteenth aspect, a communication method is provided. This method can be executed by a first device. The first device can be a terminal device, a component within the terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the terminal device. The following description uses the first device as the executing entity.

[0096] The method includes:

[0097] A random identifier is generated. Upon generation of the random identifier, the Access Layer Identifier (AS ID) is released, or the random identifier replaces the AS ID. The AS ID is stored in the first device.

[0098] In other words, during a new random access, the random identifier is generated, and the AS ID is released / reset / discarded / saved to avoid the phenomenon of the same AS ID being stored indefinitely, thereby saving storage overhead and reducing the conflict or error response problems caused by the same AS ID being stored indefinitely.

[0099] Alternatively, during a new random access, the random identifier is generated and replaced with the saved AS ID to update the saved AS ID, thereby improving storage resource utilization and reducing conflicts or error responses caused by the same AS ID being saved continuously.

[0100] In a sixteenth aspect, a communication method is provided. This method can be executed by a first device. The first device can be a terminal device, a component within the terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the terminal device. The following description uses the first device as the executing entity.

[0101] The method includes:

[0102] Receive a first message, the first message including a first identifier, the first message being a contention resolution message.

[0103] Send the first data. The first identifier includes a first access layer identifier (AS ID), which is the same as a second identifier stored in the first device.

[0104] Based on the above technical solution, for the first device, when the first device (again) receives the first message, it determines whether the access is successful based on whether the first AS ID in the first message is the same as the second identifier. If they are the same, the access is successful, and the first data is (re)transmitted. There is no need to identify which identifier the second identifier is. It can be compared with the identifier in the first message, such as the first AS ID, to determine whether the access is successful and realize data transmission.

[0105] In one possible design, before receiving the first message, the method further includes: receiving a second message, the second message including a second AS ID, the second message being a contention resolution message. The second identifier is the second AS ID.

[0106] In other words, if the second device assigns an AS ID (such as the second AS ID) to the first device, the first device saves the assigned AS ID, determines whether the access is successful based on the identifier it has saved, and then transmits the first data.

[0107] In one possible design, the first identifier may also include a first random identifier.

[0108] If the first AS ID is different from the second identifier, the first random identifier is the same as the second identifier.

[0109] In other words, the first device first compares the AS ID. If the first AS ID is different from the second identifier, it continues to compare the random identifier. If the first random identifier is the same as the second identifier, the first data is sent. The first device does not need to identify the second identifier as an identifier. It can simply compare it with the identifier in the first message, such as comparing it with the first AS ID and then comparing it with the first random identifier, thereby determining whether the access is successful and realizing data transmission.

[0110] In one possible design, before receiving the first message, the method further includes sending a third message, the third message including a second random identifier, the second identifier being the second random identifier. For example, the third message is message Msg1.

[0111] In other words, the first device saves the second random identifier, then determines whether the connection is successful based on the identifier it has saved, and transmits the first data.

[0112] In one possible design, the first AS ID corresponds to the first random identifier, and / or the second AS ID corresponds to the second random identifier.

[0113] In a seventeenth aspect, a communication method is provided. This method can be executed by a first device. The first device can be a terminal device, a component within the terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the terminal device's functions. The following description uses the first device as the executing entity. The first device stores a second identifier. The method includes:

[0114] The second identifier is determined to be the second access layer identifier AS ID.

[0115] Receive a first message, the first message including a first identifier, the first message being a contention resolution message.

[0116] Send the first data. The second AS ID is the same as the first AS ID, and the first identifier includes the first AS ID.

[0117] Based on the above technical solution, when the first device determines that the second identifier is the second AS ID, it determines whether the second AS ID is the same as the first AS ID in the first message. If they are the same, the access is successful, and the first data is (re)transmitted. The first device identifies which identifier the second identifier is. For example, if the second identifier is the second AS ID, it compares it with the first AS ID in the first message to determine whether the access is successful and to realize data transmission, thus simplifying the identifier comparison process.

[0118] In one possible design, the method further includes: determining the second identifier as a second random identifier.

[0119] The second random identifier is the same as the first random identifier, and the first identifier also includes the first random identifier.

[0120] In other words, for the first device, when the first device determines that the second identifier is the second random identifier, it determines whether the second random identifier is the same as the first random identifier in the first message. If they are the same, the first device sends the first data. The first device identifies which identifier the second identifier is. For example, if the second identifier is the second random identifier, it compares it with the first random identifier in the first message to determine whether the access is successful and to realize data transmission, thus simplifying the identifier comparison process.

[0121] In one possible design, the first AS ID corresponds to the first random identifier, and / or the second AS ID corresponds to the second random identifier.

[0122] Eighteenthly, a communication method is provided. This method can be executed by a first device. The first device can be a terminal device, a component within the terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the terminal device. The following description uses the first device as the executing entity.

[0123] The method includes:

[0124] Receive a first message, the first message including a first identifier, the first message being a contention resolution message.

[0125] Send first data. The first identifier includes at least one Access Layer Identifier (AS ID), and one AS ID of the at least one AS ID is identical to a second identifier, which is stored in the first device.

[0126] In other words, when the first identifier is the at least one AS ID, the AS IDs of the first message are traversed to determine that one AS ID of the at least one AS ID is the same as the second identifier.

[0127] In one possible design, the first identifier may also include at least one random identifier.

[0128] If each of the at least one AS IDs is different from the second identifier, then one of the random identifiers of the at least one random identifier is the same as the second identifier.

[0129] In other words, after traversing the AS IDs of the first message and determining that each AS ID of the at least one AS ID is different from the second identifier, the random identifiers are then compared. For example, if the first identifier is the at least one random identifier, the random identifiers of the first message are traversed to determine that one of the at least one random identifiers is the same as the second identifier.

[0130] The technical effects of any design method in aspect eighteen can be found in aspect sixteen and the technical effects of different design methods in aspect sixteen, and will not be repeated here.

[0131] Nineteenthly, a communication method is provided. This method can be executed by a first device. The first device can be a terminal device, a component within the terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the terminal device's functions. The following description uses the first device as the executing entity. The first device stores a second identifier, and the method includes:

[0132] The second identifier is determined to be the second access layer identifier AS ID.

[0133] Receive a first message, the first message including a first identifier, the first message being a contention resolution message.

[0134] Send first data. The second AS ID is identical to one of at least one AS IDs, and the first identifier includes the at least one AS ID.

[0135] In other words, when the first identifier is the at least one AS ID, the AS IDs of the first message are traversed to determine that one AS ID of the at least one AS ID is the same as the second AS ID.

[0136] In one possible design, the method further includes: determining the second identifier as a second random identifier.

[0137] The second random identifier is the same as one of the random identifiers of at least one random identifier, and the first identifier also includes the at least one random identifier.

[0138] In other words, when the first identifier is the at least one random identifier, the random identifiers of the first message are traversed to determine that one of the random identifiers of the at least one random identifier is the same as the second random identifier.

[0139] The technical effects of any design method in aspect 19 and aspect 19 can be found in aspect 17 and aspect 17, and will not be repeated here.

[0140] In conjunction with aspect eighteen or nineteen, in one possible design, there is a correspondence between the at least one AS ID and the at least one random identifier. And / or, the second AS ID corresponds to the second random identifier.

[0141] In a twentieth aspect, a communication method is provided. This method can be executed by a first device. The first device can be a terminal device, a component within the terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the terminal device. The following description uses the first device as the executing entity.

[0142] The method includes:

[0143] Receive first information and first identifier. The first information indicates the number M of access layer identifiers (AS IDs) in the first identifier. The first identifier includes N random identifiers and M AS IDs. There is a correspondence between the first M random identifiers and the M AS IDs among the N random identifiers. M and N are positive integers.

[0144] Based on the first information and the first identifier, the AS ID of the first device is determined. The AS ID of the first device is either a first AS ID or a first random identifier. The first AS ID is included in the M AS IDs, and the first random identifier is included in the N random identifiers.

[0145] Based on the above technical solution, the first device can correctly parse the AS ID of the first device according to the first information and the first identifier. Furthermore, the first information indicates the number of AS IDs in the first identifier, and there is a correspondence between the first M random identifiers among the N random identifiers and the M AS IDs, thus constraining the position of the random identifiers in the first identifier and saving signaling overhead. For example, compared to the bitmap method (i.e., a bitmap includes N bits; if the Nth bit... i When the first bit is the first value, it indicates the Nth random identifier among N random identifiers. i Each random identifier corresponds to one of the M AS IDs; if the Nth bit in the N bits... i When the last bit is the second value, it indicates the Nth random identifier among the N random identifiers. i Each random identifier does not correspond to any one of the M AS IDs; N i(where N is a positive integer less than or equal to N). By using the first information and the first identifier in this application, signaling overhead can be saved.

[0146] In a twenty-first aspect, a communication method is provided. This method can be executed by a second device. The second device can be a terminal device, a component within the terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the terminal device's functions. The following description uses the second device as the executing entity. The method includes:

[0147] Determine the first information and the first identifier. The first information indicates the number M of access layer identifiers (AS IDs) in the first identifier. The first identifier includes N random identifiers and M AS IDs. There is a correspondence between the first M random identifiers and the M AS IDs among the N random identifiers. M and N are positive integers.

[0148] Send the first information and the first identifier.

[0149] The technical effects of aspect 21 can be found in aspect 20, and will not be repeated here.

[0150] In conjunction with aspect 20 or 21, in one possible design, the first information occupies 3 or 4 bits.

[0151] In conjunction with aspect 20 or aspect 21, in one possible design, there is a correspondence between the first M random identifiers among the N random identifiers and the M AS IDs, including: the first M random identifiers among the N random identifiers correspond one-to-one with the M AS IDs.

[0152] In conjunction with aspect 20 or 21, in one possible design, there is no correspondence between the last (NM) random identifiers among the N random identifiers and any one of the M AS IDs.

[0153] In a twenty-second aspect, a communication method is provided. This method can be executed by a first device. The first device can be a terminal device, a component within the terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the terminal device's functions. The following description uses the first device as the executing entity. The method includes:

[0154] Receive a first identifier and a first bitmap. The first identifier includes N random identifiers and M access layer identifiers (AS IDs). The N random identifiers correspond one-to-one with N frequency domain resources, which are included in K frequency domain resources. The first bitmap includes K bits. If the Kth bit in the K bits... i When the first bit is the first value, it indicates the Kth bit in the K frequency domain resources. i Each frequency domain resource corresponds to one of the M AS IDs; if the Kth bit in the K bits i When the first bit is the second value, it indicates the Kth bit in the K frequency domain resources. i Each frequency domain resource does not correspond to any one of the M AS IDs; K, M, and N are positive integers, K i It is a positive integer less than or equal to K.

[0155] Based on the first bitmap and the first identifier, the AS ID of the first device is determined. The AS ID of the first device is either a first AS ID or a first random identifier. The first AS ID is included in the M AS IDs, and the first random identifier is included in the N random identifiers.

[0156] The K frequency domain resources can be understood as random access to frequency domain resources on the same time domain resource.

[0157] Based on the above technical solution, it can be seen that the first device can correctly parse the AS ID of the first device according to the first bitmap and the first identifier. In addition, the length of the first bitmap is consistent with or related to the number of random access frequency domain resources on the same time domain resource, and the number of random access frequency domain resources on the same time domain resource is fixed (or determined, such as indicated / configured by paging messages), so there is no need to additionally indicate the length of the first bitmap, thereby saving signaling overhead.

[0158] In a twenty-third aspect, a communication method is provided. This method can be executed by a second device. The second device can be a terminal device, a component within the terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the terminal device's functions. The following description uses the second device as the executing entity. The method includes:

[0159] A first identifier and a first bitmap are determined. The first identifier includes N random identifiers and M access layer identifiers (AS IDs). The N random identifiers correspond one-to-one with N frequency domain resources, which are included in K frequency domain resources. The first bitmap includes K bits. If the Kth bit in the K bits... i When the first bit is the first value, it indicates the Kth bit in the K frequency domain resources.i Each frequency domain resource corresponds to one of the M AS IDs; if the Kth bit in the K bits i When the first bit is the second value, it indicates the Kth bit in the K frequency domain resources. i Each frequency domain resource does not correspond to any one of the M AS IDs; K, M, and N are positive integers, K i It is a positive integer less than or equal to K.

[0160] Send the first bitmap and the first identifier.

[0161] The technical effects of aspect 23 can be found in aspect 22, and will not be repeated here.

[0162] In conjunction with aspect 22 or 23, in one possible design, K takes the value of one of the following: 4 or 8.

[0163] In conjunction with aspect 22 or 23, in one possible design, the N random identifiers correspond to the same time-domain resource, and the first bitmap is associated with the time-domain resource.

[0164] In a twenty-fourth aspect, a communication method is provided. This method can be executed by a first device. The first device can be a terminal device, a component within the terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the terminal device's functions. The following description uses the first device as the executing entity. The method includes: determining an access type.

[0165] When the access type is contention-free random access, the reception of the fourth message is cancelled, and the first data is sent through the first resource. The fourth message is a random access trigger message, and the first resource is configured by the paging message.

[0166] Here, the first resource can be understood as the resource available at the first moment.

[0167] Based on the above technical solution, in the contention-free random access scenario, the paging message indicates a resource (such as the first resource). Therefore, the first device can determine on which resource to send the first data. In this case, the second device does not need to receive the fourth message, thereby saving signaling overhead.

[0168] In a twenty-fifth aspect, a communication method is provided. This method can be executed by a second device. The second device can be a terminal device, a component within the terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the terminal device's functions. The following description uses the second device as the executing entity. The method includes: determining an access type.

[0169] When the access type is contention-free random access, the sending of the fourth message is cancelled, and the first data is received through the first resource. The fourth message is a random access trigger message, and the first resource is configured by the paging message.

[0170] The technical effects of aspect 25 can be found in aspect 24, and will not be repeated here.

[0171] In a twenty-sixth aspect, a communication method is provided. This method can be executed by a first device. The first device can be a terminal device, a component within the terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the terminal device's functions. The following description uses the first device as the executing entity. The method includes: determining an access type.

[0172] When the access type is contention-based random access, a fourth message is received, and a third message is sent through the first resource.

[0173] The first resource is included in at least two resources and is determined according to the fourth message. The at least two resources are configured by the paging message. The third message includes a random identifier. The fourth message is a random access trigger message.

[0174] For example, the third message is message Msg1. For example, the third message can be understood as an access request message.

[0175] The "at least two resources" can be understood as at least two time resources.

[0176] Here, the first resource can be understood as the resource available at the first moment.

[0177] Based on the above technical solution, in the contention-based random access scenario, the paging message indicates at least two resources. Therefore, the first device cannot determine on which resource to send the third message. In this case, the first device determines the first resource by receiving the fourth message. Since the first resource has been calibrated by the fourth message, sending the third message through the first resource has high accuracy.

[0178] In a twenty-seventh aspect, a communication method is provided. This method can be executed by a second device. The second device can be a terminal device, a component within the terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the terminal device's functions. The following description uses the second device as the executing entity. The method includes: determining an access type.

[0179] When the access type is contention-based random access, a fourth message is sent, and a third message is received through the first resource.

[0180] The first resource is included in at least two resources and is determined according to the fourth message. The at least two resources are configured by the paging message. The third message includes a random identifier. The fourth message is a random access trigger message.

[0181] The technical effects of aspect 27 are similar to those of aspect 26, and will not be repeated here.

[0182] In a twenty-eighth aspect, a communication apparatus is provided for implementing the various methods described above. The communication apparatus includes modules, units, or means corresponding to the implementation of the methods, which can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions.

[0183] In one possible design, the communication device may include a processing module and a transceiver module. The processing module can be used to implement the processing functions performed by the communication device in any of the above aspects and any possible implementations thereof. The transceiver module, also referred to as a transceiver unit, is used to implement the sending and / or receiving functions performed by the communication device in any of the above aspects and any possible implementations thereof. The transceiver module may consist of transceiver circuitry, a transceiver, a transceiver unit, or a communication interface.

[0184] In one possible design, the transceiver module includes a transmitting module and / or a receiving module, which are used to implement the transmitting or receiving functions performed by the communication device in any of the above aspects and any possible implementations thereof.

[0185] In a twenty-ninth aspect, a communication device is provided for implementing the method performed by the communication device in any of the above aspects or any possible design of any of the above aspects.

[0186] In a thirtieth aspect, a communication device is provided, comprising: a processor; the processor being configured to execute a computer program or instructions to cause the communication device to perform the method described in any aspect or the method performed by the communication device in any possible design of any aspect.

[0187] Optionally, the communication device further includes a memory, which may be coupled to the processor, or the memory may exist independently of the processor; for example, the memory and the processor may be two separate modules. The memory may be located outside or inside the communication device.

[0188] In a thirty-first aspect, a computer-readable storage medium is provided. This computer-readable storage medium stores a computer program or instructions that, when executed, cause the methods described in any of the preceding aspects or the methods executed by a communication device in any possible design of any of the preceding aspects to be implemented.

[0189] In a thirty-second aspect, a computer program product containing instructions is provided, which, when run, causes the method described in any of the foregoing aspects or the method executed by a communication device in any possible design of any of the foregoing aspects to be implemented.

[0190] The communication device provided in any of the 28th to 32nd aspects may be a first device, or a component included in the first device, such as a chip or chip system, as described in the 1st, 3rd, 5th, 7th, 9th, 11th, 13th, 15th to 20th, 22nd, 24th, or 26th aspects. Alternatively, it may be a second device, or a component included in the second device, such as a chip or chip system, as described in the 2nd, 4th, 6th, 8th, 10th, 12th, 14th, 21st, 23rd, 25th, or 27th aspects. When the device is a chip system, it may be composed of chips or may include chips and other discrete devices.

[0191] It is understandable that when the communication device provided in any of the twenty-eighth to thirty-second aspects is a chip, the transmitting action / function of the communication device can be understood as outputting information, and the receiving action / function of the communication device can be understood as inputting information.

[0192] The technical effects of any of the design methods in aspects 28 to 32 can be found in the technical effects of any of the design methods in aspects 1 to 15, and will not be repeated here. Attached Figure Description

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

[0194] Figure 2 is a schematic diagram of the architecture of another communication system provided in an embodiment of this application;

[0195] Figure 3 is a schematic diagram of the architecture of another communication system provided in an embodiment of this application;

[0196] Figure 4 is a schematic diagram of the architecture of another communication system provided in an embodiment of this application;

[0197] Figure 5 is a schematic diagram of the architecture of another communication system provided in an embodiment of this application;

[0198] Figure 6 is a schematic diagram of the architecture of another communication system provided in an embodiment of this application;

[0199] Figure 7 is a schematic diagram of the architecture of another communication system provided in an embodiment of this application;

[0200] Figure 8a is a schematic diagram of an access layer process provided in an embodiment of this application;

[0201] Figure 8b is a schematic diagram of the structure of message 2 provided in an embodiment of this application;

[0202] Figure 8c is a schematic diagram of the structure of a media access control subheader provided in an embodiment of this application;

[0203] Figure 8d is a schematic diagram of another media access control subheading provided in an embodiment of this application;

[0204] Figure 9 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0205] Figure 10 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0206] Figure 11 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0207] Figure 12 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0208] Figure 13 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0209] Figure 14 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0210] Figure 15 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0211] Figure 16 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0212] Figure 17 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0213] Figure 18 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0214] Figure 19 is a schematic diagram of the structure of an identifier provided in an embodiment of this application;

[0215] Figure 20 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0216] Figure 21 is a schematic diagram of a paging message provided in an embodiment of this application;

[0217] Figure 22 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0218] Figure 23 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0219] Figure 24 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0220] Figure 25 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0221] Figure 26 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0222] Figure 27 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0223] Figure 28 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0224] Figure 29 is a schematic diagram of another message 2 provided in an embodiment of this application;

[0225] Figure 30 is a schematic diagram of the structure of another message 2 provided in an embodiment of this application;

[0226] Figure 31 is a schematic diagram of the structure of another message 2 provided in an embodiment of this application;

[0227] Figure 32 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0228] Figure 33 is a schematic diagram of the structure of another message 2 provided in an embodiment of this application;

[0229] Figure 34 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0230] Figure 35 is a schematic diagram of the structure of another message 2 provided in an embodiment of this application;

[0231] Figure 36 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0232] Figure 37 is a schematic diagram of the structure of a device provided in an embodiment of this application;

[0233] Figure 38 is a schematic diagram of another device provided in an embodiment of this application;

[0234] Figure 39 is a schematic diagram of another device provided in an embodiment of this application. Detailed Implementation

[0235] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0236] The technical solution of this application can be applied to various wireless communication systems, including but not limited to fourth-generation mobile communication technology (the 4G). th The fifth generation (4G) system (also known as the Long Term Evolution (LTE) system), is a mobile communication technology. th The technology can be applied to 5G (also known as New Radio, NR) systems, ambient internet of things (A-IoT) systems or their evolutions, or it can also be applied to future mobile communication systems, etc., without any specific restrictions.

[0237] The technical solutions provided in this application can also be applied to: device-to-device (D2D) scenarios, such as NR-D2D scenarios, or vehicle-to-everything (V2X) scenarios, such as NR-V2X scenarios. The technical solutions provided in this application can also be applied to factory manufacturing scenarios, terrestrial cellular communication, non-terrestrial networks (NTN), satellite communication, high altitude platform station (HAPS) communication, integrated access and backhaul (IAB) communication, and reconfigurable intelligent surface (RIS) communication, etc.

[0238] In the embodiments of this application, a terminal device refers to a device that provides voice and / or data connectivity to a user. A terminal device may be called a terminal apparatus, user equipment (UE), terminal, mobile station (MS), mobile terminal (MT), etc. For example, it may be a handheld device with wireless connectivity or an in-vehicle device. Currently, examples of terminal devices include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in vehicle-to-everything (V2X) communication, wireless terminals in self-driving cars, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, and machine-to-machine / machine-type communications (M2M / MTC) terminal devices, etc. In addition, terminal equipment can also be vehicle equipment, vehicle modules, vehicles, on-board units (OBU), roadside units (RSU), vehicle infotainment systems (or on-board transmitters) (telematics boxes, T-box), chips or systems on chips (SOC), etc. The above-mentioned chips or SOCs can be installed in vehicles, OBUs, RSUs or T-boxes.Terminal equipment can also be V2X communication terminal devices, such as smart cars, digital cars, unmanned cars, driverless cars, pilotless cars, autonomous cars, pure electric vehicles, hybrid electric vehicles (HEVs), range-extended electric vehicles (REEVs), plug-in hybrid electric vehicles (PHEVs), and new energy vehicles. Terminal equipment can also be D2D communication terminal devices, such as electricity meters and water meters.

[0239] In addition, in this embodiment, the terminal device can also be a device in A-IoT, such as an A-IoT device, an A-IoT terminal device, or a tag. For ease of description, this application uses an A-IoT device as an example. An A-IoT device can be implemented by a terminal device in a cellular network, such as an ultra-low power, ultra-low complexity IoT terminal device. The network device and the A-IoT device can perform contactless data communication, thereby reading information from the A-IoT device and / or writing information that needs to be stored into the A-IoT device.

[0240] Terminal devices can include passive terminal devices, semi-passive terminal devices, and active terminal devices. Passive terminal devices require an excitation signal from the network device; some energy is used for internal processing such as encoding / decoding and modulation / demodulation. This excitation signal can also serve as a carrier wave for reflecting uplink information from the terminal device. Semi-passive terminal devices contain a battery, and internal processing such as encoding / decoding and modulation / demodulation can be performed using the battery, but they still require the network device to send an excitation signal as a reflected carrier. Active terminal devices contain a battery and perform encoding / decoding and modulation / demodulation. Active terminal devices include a radio transmitter and can actively send data to other devices.

[0241] In one implementation, terminal devices in A-IoT can be divided into three categories:

[0242] One type of device (which can be referred to as Device A): This device has neither downlink (DL) amplification nor uplink (UL) amplification; the device's UL transmission is backscattered on an externally provided carrier. Optionally, this type of device has energy storage. Optionally, this type of device is similar to a passive A-IoT device.

[0243] Another type of device (which may be referred to as Device B): This device has DL amplification and / or UL amplification capabilities. The device's UL transmission is backscattered on an externally provided carrier. Optionally, this type of device has energy storage. Optionally, this type of device is similar to a semi-passive A-IoT device.

[0244] Another type of device (which can be referred to as Device C): This device has DL amplification and / or UL amplification capabilities. The UL transmission of the device is generated internally. Optionally, this type of device has energy storage. Optionally, this type of device is similar to an active A-IoT device.

[0245] It should be noted that the embodiments of this application do not limit the communication system used by the terminal device, nor the type of terminal device.

[0246] In the embodiments of this application, the network device can be a device in a wireless network, and can also be referred to as a network apparatus or a wireless access network device. For example, the network device can be a radio access network (RAN) node that connects terminal devices to the wireless network, and can also be referred to as an access network (AN) device. Network equipment includes, but is not limited to: base stations (BS), evolved NodeBs (eNodeBs), transmission reception points (TRPs), next-generation NodeBs (gNBs) in 5G systems, access network equipment in open radio access networks (O-RAN or ORAN), base stations in future mobile communication systems or access points (APs) in wireless fidelity (WiFi) systems, radio network controllers (RNCs), base station controllers (BSCs), base transceiver stations (BTSs), home base stations (e.g., home evolved NodeBs or home Node Bs, HNBs), base band units (BBUs), etc.; or it can be a module or unit that performs some of the functions of a base station, such as a central unit (CU), a distributed unit (DU), a central unit control plane (CU-CP) module, or a central unit user plane (CU-UP) module. Network equipment can be macro base stations, micro base stations, indoor stations, relay nodes, or donor nodes, etc.

[0247] In addition, in the embodiments of this application, the network device can also be a reader or interrogator in A-IoT. For ease of description, this application uses a reader as an example. This application does not limit the specific technology or device form used by the network device.

[0248] In some implementations, network devices may include CUs and DUs. This includes RAN devices with CUs and DUs that separate the protocol layers of the gNB in ​​the NR system. Some protocol layer functions are centrally controlled by the CU, while the remaining partial or complete protocol layer functions are distributed in the DU, which is centrally controlled by the CU. For example, the CU is responsible for handling non-real-time protocols and services, implementing the functions of the radio resource control (RRC) layer. The DU is responsible for handling physical layer protocols and real-time services, implementing the functions of the radio link control (RLC), media access control (MAC), and physical (PHY) layers. Furthermore, the CU can be divided into a control plane (CU-CP) and a user plane (CU-UP). The CU-CP is responsible for control plane functions, mainly including RRC and the corresponding packet data convergence protocol (PDCP) (i.e., control plane part of PDCP, PDCP-C)). CU-UP is responsible for user plane functions, mainly including the Service Data Adaptation Protocol (SDAP) and the user plane corresponding PDCP (i.e., user plane part of PDCP, PDCP-U). CU-CP and CU-UP are connected via the E1 interface. CU-CP represents the gNB connecting to the core network through the next-generation (NG) interface, and to the DU through the F1 interface control plane (i.e., F1-C). CU-UP connects to the DU through the F1 interface user plane (i.e., F1-U). Alternatively, PDCP-C may also be located within CU-UP.

[0249] It is understood that CU (including CU-CP or CU-UP) or DU may have different names in different systems, but those skilled in the art will understand their meaning. For example, in an O-RAN system, CU can also be called an open CU (O-CU), DU can also be called an open DU (O-DU), CU-CP can also be called O-CU-CP, and CU-UP can also be called O-CU-UP. For ease of description, this application uses CU, CU-CP, CU-UP, and DU as examples. Network devices may also include active antenna units (AAU).

[0250] Optionally, this application embodiment also involves core network (CN) equipment. Core network equipment is a collective term for various functional entities on the network side that manage users, data transmission, and base station configuration, including access and mobility management function (AMF), user plane function (UPF), session management function (SMF), tag management function (TMF), ambient IoT management function (AIoTMF), ambient IoT function (AIoTF), and application function (AF), etc.

[0251] Figure 1 shows a schematic diagram of a network architecture for a communication system. As shown in Figure 1, the network devices are access network devices, which include CU and / or DU.

[0252] In some examples, the CU is a logical node carrying the RRC, SDAP, PDCP, and other control functions of the access network equipment. The CU connects to network nodes such as the core network through interfaces including the E2 interface. Optionally, the CU may have some core network functions. The CU (e.g., PDCP layer and higher layers) connects to the DU (e.g., RLC layer and lower layers) through interfaces including the F1 interface. In some examples, these interfaces (e.g., the F1 interface) can provide control plane (C-Plane) and user plane (U-Plane) functions (e.g., interface management, system information management, UE context management, RRC message transmission, etc.). F1AP is the application protocol for the F1 interface, defining the F1 signaling procedures in some examples. The F1 interface supports control plane F1-C and user plane F1-U.

[0253] In some examples, the CU can be split, such as including CU-CP and CU-UP. CU-CP is a logical node carrying the RRC and PDCP-C layers, used to implement the CU's control plane functions. CU-CP can interact with network elements in the core network used to implement control plane functions. These network elements in the core network can be Access and Mobility Function (AMF) network elements, such as the AMF network element in a 5G system. The AMF network element is responsible for mobility management in the mobile network, such as terminal device location updates, terminal device registration with the network, and terminal device handover. CU-UP is a logical node carrying the SDAP and PDCP-U layers, used to implement the CU's user plane functions. CU-UP can interact with network elements in the core network used to implement user plane functions. These network elements in the core network, such as the UPF network element in a 5G system, are responsible for data forwarding and receiving in terminal devices. The above CU and DU configurations are merely examples; the functions of CU and DU can be configured as needed. The link between CU and DU can be a midhaul link.

[0254] In some examples, the DU is a logical node that carries the RLC layer, MAC layer, PHY layer, and other functions. In some examples, the DU can control at least one radio unit (RU). The DU connects to the RU through interfaces, which may be fronthaul interfaces.

[0255] In some examples, the RU is a logical node that carries both lower physical layer (PHY) and radio frequency (RF) processing. In some examples, the RU may be a 3rd Generation Partnership Project (3GPP) node. rd The TRP or remote radio head (RRH) or other similar entity in the Generation Partnership Project (3GPP).

[0256] The DU and RU can be co-located or not. The DU and RU exchange control plane and user plane information via a lower-layer split-control, user, and synchronization (LLS-CUS) interface through a fronthaul link. LLS-CUS may include LLS-C and LLS-U interfaces that provide the control plane (C-Plane) and user plane (U-Plane), respectively. In some examples, the control plane (C-Plane) refers to real-time control between the DU and RU. The DU and RU exchange management information via an LLS-M interface on the fronthaul link; the management plane (M-Plane) refers to non-real-time management operations between the DU and RU.

[0257] DUs and RUs can work together to implement the functions of the PHY layer. A DU can be connected to one or more RUs. The functions of DUs and RUs can be configured in various ways depending on the design. For example, a DU can be configured to implement baseband functions, and an RU can be configured to implement mid-RF functions. Alternatively, a DU can be configured to implement higher-level functions in the PHY layer, and an RU can be configured to implement lower-level functions in the PHY layer, or both lower-level and RF functions. Higher-level functions in the physical layer can include a portion of the physical layer's functions that are closer to the MAC layer, while lower-level functions in the physical layer can include another portion of the physical layer's functions that are closer to the mid-RF side.

[0258] In some examples, network devices also include RAN intelligent controllers (RICs). RICs include near-real-time RICs (near-RT RICs) and non-real-time RICs (non-RT RICs).

[0259] Optionally, near real-time RIC and non-real-time RIC can be set up as separate network elements, or they can be part of other devices. For example, near real-time RIC can be set up in access network devices, while non-real-time RIC can be set up in operation administration and maintenance (OAM) network elements, cloud servers, core network devices, or other devices.

[0260] Optionally, the network device can be a single RAN node or include multiple RAN nodes, such as CU and DU. The CU and / or DU can also be configured with one or more artificial intelligence (AI) modules. In some examples, the CU can also be split into CU-CP and CU-UP. One or more AI models are configured in the CU-CP and / or CU-UP.

[0261] Figure 2 illustrates a network architecture diagram of an O-RAN system. As shown in Figure 2, access network devices (e.g., eNBs, gNBs, or next-generation access network devices) communicate with core network devices via backhaul links and with terminal devices via air interfaces. It can be understood that an O-RAN system may include components other than those shown in the figure.

[0262] To facilitate understanding of the embodiments of this application, a communication system applicable to the embodiments of this application will be described in detail. This communication system includes at least two devices, such as a network device and a terminal device, or two terminal devices.

[0263] As shown in Figure 3, the communication system includes network devices and terminal devices. The network devices can communicate bidirectionally with the terminal devices. Specifically, the network devices can send excitation signals to the terminal devices via the forward link to provide power. The terminal devices receive the excitation signals sent by the network devices and send reflected signals back to the network devices via the reverse link. In this way, the network devices can identify the terminal devices' identifiers (IDs) and perform read and write operations on the terminal devices. Uplink and downlink data / signaling exist between the network devices and the terminal devices.

[0264] As shown in Figure 4, the communication system includes network devices, intermediate nodes, and terminal devices. Two-way information exchange is possible between the network devices and intermediate nodes, and between the intermediate nodes and terminal devices. Specifically, the network devices can send signaling to the intermediate nodes via the fronthaul downlink. The intermediate nodes receive the signaling and, based on it, send an excitation signal to the terminal devices via the fronthaul link. The terminal devices send reflected signals via the reverse link; correspondingly, the intermediate nodes can receive the reflected signals from the terminal devices via the reverse link and send them back to the network devices. Furthermore, the network devices and intermediate nodes can exchange other signaling on the fronthaul uplink and fronthaul downlink, such as resource configuration signaling, which will not be detailed here.

[0265] Optionally, the intermediate node can be a repeater, an IAB node, or a UE, etc., and this application does not limit this. The intermediate node transmits data and / or signaling between network devices and terminal devices.

[0266] As shown in Figure 5 or Figure 6, the communication system includes network devices, assisting nodes, and terminal devices. While the network devices and terminal devices exchange information bidirectionally, the network devices can also exchange information bidirectionally with assisting nodes, and the assisting nodes can also exchange information bidirectionally with terminal devices. For example, a terminal device sends signaling to a network device and also sends signaling to an assisting node; the assisting node then sends the same signaling back to the network device to assist the terminal device in sending data and enhance the network device's reception. The same logic applies when the network device sends signaling to the terminal device, which will not be elaborated further. In some implementations, the assisting node and the network device can communicate via the Uu interface.

[0267] Optionally, the auxiliary node can be a repeater, IAB, UE, etc., and this application does not limit this. The terminal device sends data / signaling to the network device and receives data / signaling from the auxiliary node; or the network device sends data / signaling to the terminal device and receives data / signaling from the auxiliary node.

[0268] Optionally, the network devices in Figures 3-6 above may be base stations or readers, or any of the network devices involved in this application described above. The terminal devices may be A-IoT devices, or any of the terminal devices involved in this application described above, but this application does not limit them.

[0269] Furthermore, the communication link between the network device and the terminal device can include a device-to-reader (DR or D2R) link and a reader-to-device (RD or R2D) link. The communication data between the network device and the terminal device can include D2R data and R2D data.

[0270] As shown in Figure 7, terminal device 1 and terminal device 2 can perform bidirectional information interaction. In one possible implementation, the communication between terminal device 1 and terminal device 2 adopts 5G NR technology or 5G sidelink technology.

[0271] Optionally, terminal device 1 in Figure 7 above can be a UE, and terminal device 2 can be an A-IoT terminal device. Alternatively, terminal device 2 can be a UE, and terminal device 1 can be an A-IoT terminal device. Terminal device 1 and terminal device 2 can also be any of the terminal devices involved in this application described above, but this application does not limit them.

[0272] It should be understood that the number of network devices, terminal devices, intermediate nodes, and auxiliary nodes in the above communication system example may be more or less, and this application does not limit this.

[0273] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0274] The names or processes in the embodiments of this application will be explained below to facilitate understanding by those skilled in the art.

[0275] 1. A-IoT

[0276] A-IoT is an important component of future information technology development. Its main technical feature is connecting objects to networks via communication technology, thereby realizing an intelligent network that enables human-machine interaction and machine-to-machine interaction. A-IoT can realize business functions such as inventory, positioning, sensing, and operation commands. Typical application scenarios include logistics, warehousing, industrial manufacturing, identity recognition, and environmental monitoring.

[0277] For example, the inventory management service utilizes a reader (which can be a base station / terminal device) to access A-IoT devices within the coverage area. Successfully connected A-IoT devices need to send their unique identifier to the reader. This unique identifier can be a device ID.

[0278] For example, the location service uses location signals to locate the position of A-IoT devices.

[0279] For example, sensing services involve A-IoT devices reporting sensing data to a reader (which could be a base station), such as temperature data.

[0280] For example, command operations can implement write or lock processes.

[0281] The write process includes: the reader (which can be a base station) sends a downlink command and data, instructing the A-IoT device to write the data into its own memory. The lock process includes: the reader (which can be a base station) sends a downlink command, instructing the A-IoT device to lock the location at a specified address in the memory, making the contents of that memory area unchangeable and / or unreadable.

[0282] 2. Air Interface / Access Layer (AS) Process in A-IoT

[0283] In this embodiment, taking an A-IoT device and a reader as examples, the AS process is described. As shown in Figure 8a, it includes the following steps:

[0284] Step A: A-IoT paging.

[0285] The reader sends an A-IoT paging message to the A-IoT device based on the service request. The A-IoT device then receives the A-IoT paging message from the reader.

[0286] Among them, the A-IoT paging message indicates the device that needs to respond.

[0287] Additionally, the A-IoT paging message can be replaced with an initial trigger message. For simplicity, no restrictions are imposed.

[0288] In addition, A-IoT paging messages can also be described in other ways, such as paging message.

[0289] Understandably, at the AS layer, A-IoT paging messages indicate which devices need to respond.

[0290] For A-IoT paging messages, an identifier is used to identify the device / group of devices indicated or associated in this triggering message (e.g., a single device, a group of devices, or all devices). Examples include the following:

[0291] Scenario 1: A-IoT paging messages can contain a single A-IoT device ID;

[0292] Scenario 2: The A-IoT paging message contains a group ID mapped to multiple A-IoT devices;

[0293] Scenario 3: The A-IoT paging message does not contain any identifier, indicating that all A-IoT devices capable of receiving the A-IoT paging message need to respond;

[0294] Case 4: The A-IoT paging message contains multiple A-IoT device identifiers.

[0295] Optionally, for A-IoT paging messages, it can also indicate that the device can determine the resources (such as time-domain and / or frequency-domain resources) for D2R response messages based on this information.

[0296] Optionally, the paging function of A-IoT devices can be understood as not supporting traditional paging messages, traditional paging timing, and traditional discontinuous reception (DRX) from NR. It can be assumed that the A-IoT device has sufficient power to receive A-IoT paging messages.

[0297] Step B: D2R data transmission.

[0298] The triggered A-IoT device performs device ID transmission either through the A-IoT random access procedure or without using the A-IoT random access procedure (e.g., contention-free resolution).

[0299] Step C: Data transmission.

[0300] The triggered A-IoT device and the reader may exchange data. For example, step C includes steps C1 and / or C2:

[0301] Step C1: Possible R2D data transmission (e.g., for sending commands, such as read, write, lock, deactivate, sensor, etc.).

[0302] Step C2: Possible D2R data transfer (e.g., responses to commands, such as data read by a read command, success / failure feedback for a write command, etc.).

[0303] Then, the above process can support inventory and command scenarios in the following ways:

[0304] For inventory-only scenarios, the baseline solution includes steps A and B.

[0305] For inventory and command scenarios, the baseline scheme includes steps A, B, C1, and C2.

[0306] For command-only scenarios:

[0307] It can also be supported by a baseline scheme having steps A, B, C1, and C2.

[0308] Alternatively, another candidate solution supporting this scenario is as follows:

[0309] Step A': A-IoT Paging. The reader sends an A-IoT paging message containing commands based on the service request, instructing the device to process / respond to the commands.

[0310] Step C2: Perform possible D2R data transmission (e.g., device ID or response to a command) with or without the A-IoT random access procedure.

[0311] 3. A-IoT random access

[0312] The A-IoT random access procedure is used for A-IoT devices to access the network for data transmission.

[0313] A-IoT random access is triggered by the reader, including access triggered by a single A-IoT device, a group of A-IoT devices, or all A-IoT devices under the reader's coverage.

[0314] Slotted-ALOHA is the baseline for the A-IoT random access process.

[0315] When an A-IoT device responds to an A-IoT paging message, the A-IoT device performs the following process:

[0316] Step 1, Random access type and access timing / resource determination:

[0317] If the random access is contention-free random access (CFRA):

[0318] The selected D2R opportunity / resource can be chosen, for example, from the resources indicated in the paging message; or, a specified resource can be selected. For instance, the reader indicates one or more access occasions (AOs), each AO corresponding to (or mapping to) an A-IoT device. If each AO corresponds to an A-IoT device identifier, the A-IoT device selects the AO corresponding to its own identifier. An AO includes access time resources and / or access frequency domain resources. The A-IoT device identifier includes one of the following: device ID, access stratum identifier (AS ID), or temp ID, etc.

[0319] Skip the race resolution in step 2 and proceed to step 3 to perform data transmission.

[0320] If it is contention-based random access (CBRA):

[0321] Determining / selecting the timing / resources for access, such as randomly selecting from resources indicated by the paging message;

[0322] Step 2 of the competition resolution procedure.

[0323] Step 2, Contention-based random access contention resolution:

[0324] Regarding the contention solution, two candidate solutions are shown below:

[0325] Option 1: A-IoT Message (mmessage, Msg) 1 No data

[0326] A-IoT Msg1: When an A-IoT device recognizes that its AO has started, it sends A-IoT Msg1 to the reader.

[0327] The A-IoT Msg1 includes a random identifier. This random identifier can be randomly generated by the A-IoT device or based on the device ID. The size of the random identifier is also not limited, for example, it can be a 16-bit random number.

[0328] A-IoT Msg2: A random identifier indicating successful reception by the reader.

[0329] For example, the reader sends A-IoT Msg2 to the A-IoT device. The A-IoT device then receives A-IoT Msg2 from the reader. If the A-IoT device receives A-IoT Msg2 containing a random identifier, and this random identifier is the same as the one previously sent in A-IoT Msg1, then the race condition is considered successfully resolved.

[0330] It is understandable that A-IoT Msg2 is used for contention resolution because it is assumed that the size of the random identifier in A-IoT Msg1 should be sufficient for contention resolution purposes. The probability that A-IoT devices with the same AO will send the same random identifier in A-IoT Msg1 is sufficiently low, and the range of values ​​for the random identifier can be considered sufficiently large.

[0331] Option 2: A-IoT Msg1 has data

[0332] A-IoT Msg1: When an A-IoT device recognizes that its AO has started, it sends A-IoT Msg1 to the reader.

[0333] In this context, A-IoT Msg1 includes upper-layer data. This upper-layer data may include the device ID and / or any other upper-layer data. Optionally, in Scheme Two, A-IoT Msg1 may or may not include a random identifier.

[0334] A-IoT Msg2: The reader can respond with at least one of the following: a successfully received random identifier, or a device ID (partial or complete), or an acknowledgment (ACK). Of course, the reader may also choose not to respond.

[0335] If the A-IoT device does not receive a signal indicating failure, reconnection, or retransmission, it is considered that the access was successful, the data transmission was successful, or the service was successful.

[0336] Alternatively, if the A-IoT device receives A-IoT Msg2, and A-IoT Msg2 contains at least one of the following: a random identifier, or a device ID (partial or complete), or an ACK. That is, the information in A-IoT Msg2 is part of the information previously sent in A-IoT Msg1 or generated based on A-IoT Msg1 (e.g., by hashing A-IoT Msg1), then the A-IoT device considers the race condition resolved successfully.

[0337] It can be understood that A-IoT Msg1 is Msg1 in A-IoT, and can also be written as Msg1. A-IoT Msg2 is Msg2 in A-IoT, and can also be written as Msg2.

[0338] It should be noted that, in this application, the format of Msg2 is described as follows:

[0339] Msg2 can be carried at the MAC layer, such as a Media Access Control Protocol Data Unit (MAC PDU). A MAC PDU includes at least one MAC subPDU, as shown in Figure 8b.

[0340] Typically, a MAC subPDU includes a MAC subheader and a media access control element (MAC CE).

[0341] The MAC subheader includes the message type, which is located in the most significant bit string of the message, as shown in Figure 8c or Figure 8d. Optionally, the MAC subheader also includes at least one of the following: reserved (R) bits, length (L) information, etc. The length information indicates the length of the MAC CE in its own message, and occupies 1 or 2 bytes.

[0342] The length of the MAC CE can be fixed, such as a fixed-size MAC CE. Alternatively, the length of the MAC CE can be variable, such as a variable-size MAC CE, as shown in Figure 8b.

[0343] Optionally, among the multiple MAC subPDUs, at least one MAC subPDU includes a MAC subheader and a media access control service data unit (MAC SDU), as shown in Figure 8b.

[0344] Optionally, among multiple MAC subPDUs, one MAC subPDU is used for padding. This can be understood as a MAC subPDU including padding, as shown in Figure 8b.

[0345] It should be added that when a MAC PDU includes a MAC subPDU, it can be understood that Msg2 includes a MAC subheader and a MAC CE, or Msg2 includes a MAC header and a MAC CE. In this case, the MAC subPDU can also be called a MAC PDU.

[0346] It should be added that when a MAC PDU includes multiple MAC subPDUs, it can be understood that Msg2 includes multiple MAC subheaders and multiple MAC CEs, and the multiple MAC subheaders correspond one-to-one with the multiple MAC CEs. Please refer to the introduction of MAC subPDUs.

[0347] It is understood that with the evolution of communication technology, the above names (such as MAC PDU, MAC subPDU, MAC subheader, or MAC CE) may also have other descriptions. This application only uses the above names as examples for introduction and should not be construed as limiting this application.

[0348] For example, the MAC subheader can also have other descriptions, such as subheader, MAC header, or message header, etc.

[0349] For example, MAC CE can also be described in other ways, such as element, signaling element, or MAC signaling element.

[0350] Step 3, Data Transmission:

[0351] If contention-based random access is used, or if contention-free random access is used, upper-layer data transmission with the reader is performed after the A-IoT device considers the contention to be resolved successfully. The upper-layer data transmission may be the device ID and / or any other upper-layer data (if any).

[0352] In step 3, it can be understood that subsequent R2D transmissions after a D2R transmission do not always need to be sent. The use / existence of subsequent R2D transmissions requires further research; for example, handling retransmissions or reconnections after a D2R transmission failure could be considered (due to various reasons).

[0353] 4. Reporting of device identification (device ID)

[0354] Each terminal device (such as an A-IoT device) has a device identifier. In inventory management scenarios, the terminal device (such as an A-IoT device) reports its device identifier to the network device (such as a reader) to achieve inventory management. However, the device identifier has a large number of bits, resulting in high air interface overhead, and the device identifier is exposed to the air interface, leading to poor security.

[0355] In view of this, this application provides a communication method. This method can be applied to the systems shown in Figures 1-7. The method includes:

[0356] Receive a first message, which includes first information indicating the first transport block size (TBS).

[0357] Send a second message. If the first TBS is less than the first threshold, the second message includes the access stratum identification (AS ID) or temporary (temp or temporary) identifier of the first device.

[0358] Based on the above technical solution, the first information indicates the first TBS, and the first device determines the identifier included in the second message based on the first TBS. For example, if the first TBS is less than a first threshold, the second message includes the AS ID or temporary identifier of the first device. Since the AS ID and temporary identifier correspond to the device identifier of the first device, the first device can report the AS ID or temporary identifier instead of reporting the device identifier, reducing the possibility of the device identifier being exposed over the air interface. Typically, the AS ID and temporary identifier have fewer bits, which helps save air interface overhead.

[0359] It should be noted that in this application, one terminal device (such as an A-IoT device) corresponds to one device identifier. Furthermore, one terminal device (such as an A-IoT device) also corresponds to an AS ID and / or a temporary identifier.

[0360] Among them, the device identifier is the unique identifier of the terminal device, which has a large number of bits, such as 128 bits.

[0361] The AS ID can be assigned to the terminal device by the network device (such as a reader), and it has a small number of bits, such as 8 bits or 16 bits. In other words, the network device (such as the reader) stores the correspondence between the device identifier and the AS ID. Therefore, when the AS ID is reported instead of the device identifier, the network device can still determine the device identifier corresponding to the reported AS ID based on the reported AS ID and the stored correspondence (such as the correspondence between the device identifier and the AS ID).

[0362] Temporary identifiers can be assigned to terminal devices by core network equipment. For example, a temporary identifier is assigned to a terminal device when it first joins the network or is stored in inventory. Temporary identifiers are relatively few bits long, such as 80 bits. In other words, the core network equipment stores the correspondence between device identifiers and temporary identifiers. Therefore, when a temporary identifier is reported instead of a device identifier, the core network equipment can still determine the device identifier corresponding to the reported temporary identifier based on the reported temporary identifier and the stored correspondence (such as the correspondence between device identifiers and temporary identifiers).

[0363] Optionally, in this application, the reporting of identifiers (such as AS IDs or temporary identifiers) can be performed in the following process:

[0364] For example, in the CBRA procedure, the first device sends an identifier via Msg3 (either after contention resolution or after successful access). This identifier is either an AS ID or a temporary identifier. Correspondingly, the second message is Msg3.

[0365] Alternatively, in the CFRA process, the first device sends an identifier via Msg1 (or D2R (upper-layer) data, or the first D2R (upper-layer) data). This identifier is either an AS ID or a temporary identifier. Correspondingly, the second message is Msg1 (or D2R (upper-layer) data, or the first D2R (upper-layer) data).

[0366] Alternatively, in the CFRA procedure, after the first device receives a downlink trigger message or paging message, it sends an identifier on the access / transmission resource corresponding to that message. This identifier is either an AS ID or a temporary identifier.

[0367] It should be noted that the first device can be a network device, such as a reader, or a terminal device, such as an A-IoT device, or a chip in the aforementioned devices (such as network devices or terminal devices). For details on network devices and terminal devices, please refer to Figures 1-7, which will not be elaborated further. In this application, we will use an A-IoT device as an example for explanation.

[0368] The second device can be a network device, such as a reader, or a terminal device, such as an A-IoT device, or a chip within the aforementioned devices (such as network devices or terminal devices). The network device and terminal device are illustrated in Figures 1-7 and will not be described further. In this application, a reader is used as an example for the description of the second device.

[0369] The third device can be a core network device or a chip within the core network device. The core network device is illustrated in Figures 1-7 and will not be described further. In this application, we will use a core network device as an example for illustration.

[0370] The communication method proposed in this application embodiment will now be described in detail with reference to Figure 9. The communication method 900 proposed in this application embodiment includes the following operations:

[0371] S901, the second device sends a first message. Correspondingly, the first device receives the first message from the second device.

[0372] The first message includes first information, second information, or third information. The first information indicates the first TBS, the second information indicates the AS ID or temporary identifier to be reported, and the third information indicates the size of the AS ID or the size of the temporary identifier.

[0373] The following is an introduction to First Information and First TBS:

[0374] Optionally, the first TBS is a D2R TBS, or the payload size for D2R transmission.

[0375] Optionally, the first TBS can be a specific value or a range. For example, the first TBS can indicate 2 to 8 bytes to further reduce signaling overhead.

[0376] Optionally, the first TBS can be understood as including (or equal to) the sum of the size of the MAC subheader and the MAC SDU, or including (or equal to) the sum of the size of the MAC subheader and the MAC CE, or including (or equal to) the sum of the size of the MAC subheader and the MAC cell, or including (or equal to) the size of the MAC carried information.

[0377] It should be noted that TBS can also be described in other ways, such as information related to TBS, such as time domain resource, duration, or payload size. Among these, time domain resource and duration can determine TBS. This application uses TBS as an example for introduction, and it should not be construed as limiting this application.

[0378] It's important to note that, essentially, TBS (Transmission Block Size) refers to the payload size that the physical layer needs to carry from layers above the physical layer. Typically, TBS does not include the message header. The message header usually refers to a sequence of physical layer elements such as the preamble. The payload size does not include the physical layer sequence; rather, it refers to the payload received by the physical layer from upper layers (such as the MAC layer). This payload can refer to upper-layer payloads, MAC layer payloads (such as the size of a MAC PDU), AS layer payloads, payloads above the AS layer, MAC subheadings and MAC SUDs, MAC subheadings and MAC CEs, or MAC subheadings and MAC cells.

[0379] Optionally, the first information indicates that the first TBS is the same size as the AS ID of the first device. This can be understood as the first information indicating that the AS ID of the first device is reported, and indicating the size of the AS ID of the first device. Here, the AS ID size can be understood as the length of the AS ID, or the number of bits in the AS ID. Alternatively, the first information indicates that the first TBS is the same as a first value. Here, the first value is equal to the sum of the AS ID size and the MAC subheader size of the first device. Or, the first value is greater than the sum of the AS ID size and the MAC subheader size of the first device. For example, in the second message, in addition to the AS ID and MAC subheader, there is other information (more data indication), including but not limited to segmentation indication information. The segmentation indication can be 1 bit, where 0 indicates no segmentation, and 1 indicates segmentation. This can be understood as the first value being equal to the sum of the AS ID size of the first device, the MAC subheader size, and the size of other information.

[0380] Optionally, the first information indicates that the first TBS is the same size as the temporary identifier of the first device. This can be understood as the first information indicating that the temporary identifier of the first device is reported, and indicating the size of the temporary identifier of the first device. The temporary identifier size can be understood as the length of the temporary identifier or the number of bits in the temporary identifier. Alternatively, the first information indicates that the first TBS is the same as the second value. This second value is equal to the sum of the temporary identifier size of the first device and the MAC subheader size. Or, the second value is greater than the sum of the temporary identifier size of the first device and the MAC subheader size. For example, in the second message, in addition to the temporary identifier and the MAC subheader, there is other information (more data indication), including but not limited to segmentation indication information. The segmentation indication can be 1 bit, where 0 indicates no segmentation, and 1 indicates segmentation. This can be understood as the second value being equal to the sum of the temporary identifier size of the first device, the MAC subheader size, and the size of other information.

[0381] The second piece of information is described below:

[0382] The second information indicates the reporting of the AS ID or temporary identifier. For example, this can be indicated by 1 bit. When this bit is 1, it indicates the reporting of the AS ID or temporary identifier. Conversely, when this bit is 0, it indicates the reporting of the first identifier, such as the device identifier of the first device.

[0383] The following is an introduction to third-party information:

[0384] When the third information indicates the size of the AS ID, it can be understood as the third information indicating the AS ID to be reported and indicating the size of the AS ID.

[0385] It is understandable that when the first message includes the third information, the third information indicates the AS ID size. In this case, the indicated size is not the TBS, because the TBS is the sum of the AS ID size and the MAC sub-header size. Therefore, when determining the TBS, the first device also needs to add the MAC sub-header size to the indicated AS ID size.

[0386] When the third information indicates the size of the temporary identifier, it can be understood as the third information indicating the reporting of the temporary identifier and indicating the size of the temporary identifier.

[0387] It is understandable that when the first message includes the third information, the third information indicates the temporary identifier size. In this case, the indicated size is not the TBS, because the TBS is the sum of the temporary identifier size and the MAC sub-header size. Therefore, when determining the TBS, the first device also needs to add the MAC sub-header size to the indicated temporary identifier size.

[0388] Optionally, the description of the first message is as follows:

[0389] Optionally, the first message is used to page the first device; for example, the first message is a paging message, as shown in Figure 10 or Figure 11. Exemplarily, the paging message does not include the first and third information, but includes the second information.

[0390] Alternatively, the first message may indicate the contention resolution of the first device; for example, the first message may be a contention resolution message, i.e., Msg2, as shown in Figure 10 or Figure 11. Exemplarily, the contention resolution message may include first information, second information, or third information.

[0391] Alternatively, the first message may be used to trigger one or more Access Activations (AOs). For example, the first message may be a Random Access Trigger (RA) message. Exemplarily, a RA trigger message may not include the first and third information, but may include the second information.

[0392] It should be added that, in this application, the RA trigger message is used to trigger / determine / indicate an AO set, or to trigger / determine / indicate one or more AOs. An AO set includes one or more access time-domain resources and / or one or more access frequency-domain resources. An AO includes time-domain resources and / or frequency-domain resources.

[0393] For the first device, after receiving the first message, it executes S902:

[0394] S902, the first device sends a second message to the second device. Correspondingly, the second device receives the second message from the first device.

[0395] The second message is described as follows:

[0396] Case 1, taking the first message including the first information as an example:

[0397] In case 1, as a first possible example, if the AS ID size of the first device is within the range of the first TBS, then the second message includes the AS ID of the first device. Alternatively, if the temporary identifier size of the first device is within the range of the first TBS, then the second message includes the temporary identifier of the first device. Alternatively, if the device identifier size of the first device is within the range of the first TBS, then the second message includes the device identifier of the first device.

[0398] For example, if the first TBS indicates bytes 2-8, the AS ID of the first device is 2 bytes, and the device identifier (device ID) of the first device is 12 bytes, then when the first TBS indicates bytes 2-8, the first device can determine to send the AS ID, for example, by sending the AS ID through a second message. Alternatively, the first device can determine to send segments of the device ID (e.g., the first 8 bytes of the device ID).

[0399] For example, if the first TBS indicates 6 to 12 bytes, the AS ID of the first device is 2 bytes, and the device ID of the first device is 12 bytes, then when the first TBS indicates 6 to 12 bytes, the first device can determine to send the device ID, for example, by sending the device ID through the second message.

[0400] In scenario 1, as a second possible example, if the first value is within the range of the first TBS, then the second message includes the AS ID of the first device. The first value is greater than or equal to the sum of the AS ID size and the MAC subheader size of the first device. Alternatively, if the second value is within the range of the first TBS, then the second message includes a temporary identifier of the first device. The second value is greater than or equal to the sum of the temporary identifier size and the MAC subheader size of the first device. Alternatively, if the third value is within the range of the first TBS, then the second message includes the device identifier of the first device. The third value is greater than or equal to the sum of the device identifier size and the MAC subheader size of the first device.

[0401] For example, the first TBS indicates 2 to 8 bytes, the first device's AS ID is 2 bytes, and the MAC subheader is 1 byte. The sum of the first device's AS ID and MAC subheader is 3 bytes, falling within the range of 2 to 8 bytes. Therefore, the first device can determine to send the AS ID, for example, by sending a segment of the AS ID or device ID via the second message. Alternatively, as an alternative, the first device can determine to send a segment of the device ID. However, if sending a segment of the device ID, the size of the MAC subheader also needs to be considered, so only a 7-byte device ID segment and a 1-byte MAC subheader are sent.

[0402] For example, if the first TBS indicates bytes 7 to 13, the first device's AS ID is 2 bytes, the MAC subheader is 1 byte, and the first device's device ID is 12 bytes, then when the first TBS indicates bytes 7 to 13, the first device can determine to send the device ID, for example, by sending the device ID through the second message.

[0403] In scenario 1, as a third possible example, if the first TBS is less than or equal to the first threshold, the second message includes the AS ID or temporary identifier of the first device. If the first TBS is greater than the first threshold, the second message includes the device identifier of the first device.

[0404] The first threshold is less than the device identifier size and greater than or equal to the temporary identifier size and the AS ID size. For example, the first threshold can be the AS ID size, or the first threshold can be the sum of the AS ID size and the MAC subheader, or the first threshold can be the sum of the AS ID size, the MAC subheader, and other MAC information (such as More Data Indication).

[0405] For example, the first threshold can be a specific value, such as 90 bits, 95 bits, or 100 bits, or 10 bytes, 15 bytes, etc. The first threshold can also be other values, without limitation.

[0406] If the first TBS is less than the first threshold, the second message includes the AS ID or temporary identifier of the first device. Since the first TBS is less than the first threshold, the first device needs to report a fewer-bit identifier, such as the first device's AS ID and temporary identifier, to save air interface overhead. Because the first device's AS ID and temporary identifier correspond to the first device's device identifier, the first device can report the AS ID or temporary identifier instead of the device identifier, reducing the possibility of the device identifier being exposed over the air interface and improving security. Typically, the AS ID and temporary identifier have fewer bits, which helps save air interface overhead.

[0407] For example, the case where the first TBS is less than or equal to the first threshold is given:

[0408] Taking the AS ID of the first device as an example, the first information indicates that the first TBS is the same size as the AS ID of the first device, or the first information indicates that the first TBS is the same as the first value. Wherein, the first value is greater than or equal to the sum of the AS ID size of the first device and the MAC sub-header size.

[0409] Taking the temporary identifier of the first device as an example, the first information indicates that the first TBS is the same size as the temporary identifier of the first device, or the first information indicates that the first TBS is the same as the second value. Wherein, the second value is greater than or equal to the sum of the temporary identifier size of the first device and the MAC sub-header size.

[0410] If the first TBS is greater than or equal to the first threshold, the second message includes the first identifier of the first device, the length of which is greater than the length of the AS ID and the length of the temporary identifier. For example, the first identifier is a device identifier, such as a device ID. Since the first TBS is greater than or equal to the first threshold, the first device can report an identifier with a larger number of bits, such as the first identifier of the first device, so that the network side can obtain the device identifier of the first device, thereby realizing services such as initial inventory.

[0411] For example, consider the case where the first TBS is greater than the first threshold:

[0412] The first information indicates that the first TBS is the same size as the device identifier of the first device, or the first information indicates that the first TBS is the same as the third value. Wherein, the third value is greater than or equal to the sum of the device identifier size of the first device and the MAC subheader size.

[0413] As a possible alternative example, if the first TBS equals the second threshold, the second message includes the first identifier of the first device, the length of which is greater than the length of the AS ID and the length of the temporary identifier. For example, the first identifier is a device identifier, such as a device ID. Since the first TBS equals the second threshold, the first device can report an identifier with a larger number of bits, such as the first identifier of the first device, so that the network side can obtain the device identifier of the first device, thereby enabling services such as initial inventory management.

[0414] For example, the second threshold may be the device identifier size, or the second threshold may be the sum of the device identifier size and the MAC subheader, or the second threshold may be the sum of the device identifier size, the MAC subheader and other MAC information (such as More Data Indication).

[0415] It is understood that in this application, the device identifier, AS ID, and temporary identifier of the first device are of different sizes. Correspondingly, the TBS (Transmission Limits) for transmitting the complete device identifier, AS ID, and temporary identifier are also different. Based on this, the first TBS determines which piece of information is transmitted, or the comparison result between the first TBS and a first threshold determines which piece of information is transmitted. It can be understood that when the first TBS is less than or equal to the first threshold, it means that the AS ID or temporary identifier of the first device is scheduled for transmission. When the first TBS is greater than the first threshold, it means that the device identifier of the first device is scheduled for transmission.

[0416] Scenario 2, taking the first message including the second message as an example:

[0417] If the second message indicates that the AS ID should be reported, the second message includes the AS ID of the first device. Since the AS ID of the first device corresponds to the device identifier of the first device, the first device reports the AS ID instead of the device identifier, which provides high security. Furthermore, the AS ID of the first device has fewer bits, such as fewer bits than the device identifier of the first device, thereby saving air interface overhead.

[0418] If the second message indicates that a temporary identifier should be reported, the second message includes the temporary identifier of the first device. Since the temporary identifier of the first device corresponds to the device identifier of the first device, the first device reports the temporary identifier instead of the device identifier, which provides high security. Furthermore, the temporary identifier of the first device has fewer bits, such as fewer bits than the device identifier of the first device, thereby saving air interface overhead.

[0419] For example, the second message is Msg3, as shown in Figure 10 or Figure 11.

[0420] Case 3, taking the first message including the third message as an example:

[0421] If the third message indicates the AS ID size, it means that the AS ID of the first device is scheduled to be transmitted. Accordingly, the second message includes the AS ID of the first device, thereby saving air interface overhead and improving security.

[0422] In some embodiments, the size of the AS ID to be reported is indicated in advance via a paging message to save overhead. For example, compared to indicating the AS ID size to each device (such as an A-IoT device) separately later, such as by indicating it separately via Msg2, indicating the size of the AS ID to be reported in advance via a paging message results in less air interface overhead.

[0423] If the third message indicates the size of the temporary identifier, it means that the temporary identifier of the first device is scheduled for transmission. Accordingly, the second message includes the temporary identifier of the first device, thereby saving air interface overhead and improving security.

[0424] In some embodiments, the size of the temporary identifier to be reported is indicated in advance via a paging message to save overhead. For example, compared to indicating the size of the temporary identifier to each device (such as an A-IoT device) separately later, such as by indicating it separately via Msg2, indicating the size of the temporary identifier to be reported in advance via a paging message results in less air interface overhead.

[0425] In some embodiments, when the second message includes the AS ID of the first device, due to the correspondence between the storage device identifier and the AS ID, the second device can also determine the device identifier corresponding to the AS ID carried in the second message, i.e., the device identifier of the first device, based on the correspondence between the AS ID carried in the second message and the storage (such as the correspondence between the device identifier and the AS ID). Then, the second device sends uplink data to the third device. The uplink data includes the device identifier of the first device, thereby enabling services such as non-initial inventory checks, as shown in Figure 10.

[0426] It should be noted that the second device pre-establishes a mapping between device identifiers and AS IDs. For example, the third device sends service request 1 to the second device. Correspondingly, the second device receives service request 1 from the third device. Here, service request 1 is an initial inventory service request. Based on service request 1, the second device performs an initial inventory to obtain the device identifier of the first device. The second device determines the AS ID of the first device (e.g., the AS ID of the first device reuses the random identifier of the first device, or the AS ID of the first device is reassigned), and establishes a mapping between the device identifier and the AS ID of the first device for use in subsequent processes (such as non-initial inventory), as shown in Figure 10.

[0427] It should be added that, in this application, non-initial inventory refers to at least one of the following: periodic inventory, repeated inventory, and processes associated with the same service / mask. Associating with the same service can be understood as multiple transmissions of the same service, such as the issuance and feedback of write commands in a command service. Associating with the same mask can be understood as multiple terminal devices associating with the same service, and the device identifiers of the multiple terminal devices meeting certain conditions, such as a portion of the device identifier (e.g., the first 10 bits of the device identifier) ​​being the same.

[0428] Optionally, the third device instructs the second device to repeatedly execute the same service multiple times via indication information, such as periodic inventory or repeated inventory. The indication method can be implicit, such as using the same mask, the same service identifier, or the type of service to be repeatedly executed. The service type includes at least one of the following: periodic service, periodic inventory, tracking, periodic location / command, etc.

[0429] In some embodiments, the second device sends a third message to the first device. Correspondingly, the first device receives the third message from the second device. The third message indicates that the AS ID of the first device should be saved. In response to the third message, the first device saves its AS ID for use in subsequent processes (such as periodic inventory processes), eliminating the need to reassign the AS ID and saving air interface overhead.

[0430] In some embodiments, when the second message includes a temporary identifier of the first device, the second device sends uplink data to the third device. The uplink data includes the temporary identifier of the first device. Because the third device stores the correspondence between the device identifier and the temporary identifier, the third device can also determine the device identifier corresponding to the temporary identifier carried in the uplink data, i.e., the device identifier of the first device, based on the stored correspondence (such as the correspondence between the device identifier and the temporary identifier), thereby enabling services such as non-initial inventory checks, as shown in Figure 11.

[0431] It should be noted that the third device pre-establishes a correspondence between the device identifier and the temporary identifier. For example, the third device obtains the device identifier of the first device through initial inventory. The third device establishes a correspondence between the device identifier of the first device and the temporary identifier of the first device for use in subsequent processes (such as non-initial inventory), as shown in Figure 11.

[0432] It should be added that if the temporary identifier is stored in the register of the first device, and the register's power is depleted or insufficient to store the temporary identifier, then the device identifier of the first device will still be sent even if the first TBS is less than the first threshold. For example, the second message may include the device identifier of the first device. Optionally, the second device may send the device identifier of the first device in a TBS segmented manner.

[0433] If the temporary identifier is stored in the nonvolatile memory (NVM) of the first device, and the NVM does not discard the temporary identifier when the power is depleted, then the temporary identifier of the first device is sent when the first TBS is less than the first threshold.

[0434] In related technologies, the AS ID is an access layer identifier. It can reuse a random identifier or be assigned by a second device (such as a reader) and indicated to the first device (such as an A-IoT device) that successfully resolves the access / contention issue via Msg2. The AS ID is transmitted over the air interface, which incurs significant air interface overhead.

[0435] In view of this, this application provides a communication method. This method can be applied to the systems shown in Figures 1-7. The method includes:

[0436] Upon receiving first information, the first information indicates that the AS ID of the first device is part of a second identifier, the second identifier including at least one of the first identifier, a temporary identifier, or a random identifier of the first device, wherein the length of the first identifier is greater than the length of the temporary identifier. For example, the first identifier is a device identifier, i.e., a device ID. Based on the first information, the AS ID is determined.

[0437] The AS ID of the first device is part of the second identifier. This can be understood as the AS ID of the first device being a truncation of the second identifier, or the AS ID of the first device being a truncation identifier.

[0438] For example, the AS ID of the first device includes a portion of the second identifier, such as the first 4 bits, the last 4 bits, or other numbers of bits. Alternatively, the AS ID of the first device may be derived from the second identifier, for example, by performing a hash operation on the second identifier to obtain the AS ID of the first device, or by performing a hash operation on the second identifier to obtain the result, and using a portion of the result (such as the first 4 bits or the last 4 bits) as the AS ID of the first device, without limitation.

[0439] For details on device identification and temporary identification, please refer to the introduction of communication method 900, which will not be repeated here.

[0440] The random identifier is generated by the first device. For example, the random identifier is a 16-bit random number or pseudo-random number (RN16).

[0441] Based on the above technical solution, the first information indicates that the AS ID of the first device is part of the second identifier, so that the first device can determine its AS ID according to the first information, thereby realizing the allocation of the AS ID. That is to say, what is transmitted over the air interface is the first information, not the AS ID. Among them, the AS ID is 8 bits or 16 bits, while the first information has fewer bits, such as 1 bit, resulting in less air interface overhead.

[0442] The communication method proposed in this application embodiment will now be described in detail with reference to Figure 12. The communication method 1200 proposed in this application embodiment includes the following operations:

[0443] S1201, The second device determines the first information.

[0444] The first information indicates that the AS ID of the first device is part of the second identifier, which includes at least one of the first identifier, a temporary identifier, or a random identifier of the first device, wherein the length of the first identifier is greater than the length of the temporary identifier. For example, the first identifier is a device identifier, i.e., a device ID.

[0445] It is understandable that the first information has a relatively small number of bits. For example, the first information occupies at least one bit. Let's take an example where the first information occupies 1 bit. For instance, when this bit is 1, it indicates that the AS ID of the first device is a part of the second identifier; when this bit is 0, it indicates that the AS ID of the first device reuses the random identifier of the first device. Alternatively, when this bit is 0, it indicates that the AS ID of the first device is a part of the second identifier; when this bit is 1, it indicates that the AS ID of the first device reuses the random identifier of the first device.

[0446] For the second device, after determining the first information, it executes S1202:

[0447] S1202, the second device sends the first information. Correspondingly, the first device receives the first information from the second device.

[0448] For example, the first information includes at least one of the following: a paging message, a random access trigger message, a contention resolution message, or downlink data. The random access trigger message can be denoted as RA trigger. The contention resolution message can be denoted as Msg2. The downlink data includes a command, for example, sending the first information via a command.

[0449] For example, in a CFRA scenario, the first information is included in the paging message or random access trigger message, as shown in Figure 13.

[0450] For example, in a CBRA scenario, the first information is included in the paging message, random access trigger message, or contention resolution message, as shown in Figure 14. Of course, the first information can also be included in the downlink data (not shown in Figures 13 and 14).

[0451] For the first device, after receiving the first information, it executes S1203:

[0452] S1203. The first device determines the AS ID of the first device based on the first information.

[0453] For example, the first device determines its AS ID based on the first information and the second identifier to achieve AS ID allocation. Since the first information, rather than the AS ID, is transmitted over the air interface, and the first information has fewer bits, air interface overhead is saved.

[0454] In some embodiments, the third device sends the AS ID of the first device to the second device. Accordingly, the second device receives the AS ID of the first device from the third device. The AS ID of the first device is part of the second identifier, as described in S1201, and will not be repeated here.

[0455] For example, in a CFRA scenario, after the third device sends the service type to the second device, it sends the AS ID of the first device to the second device. The service type indicates the command service, as shown in Figure 13.

[0456] For example, in a CBRA scenario, after the third device obtains the device identifier of the first device, it sends the AS ID of the first device to the second device. For instance, the third device obtains the device identifier of the first device through uplink (UL) data, as shown in Figure 14.

[0457] In the CBRA scenario, the device identifier of the first device is included in the non-access stratum (NAS) packet. After receiving the NAS packet from the first device, the second device forwards the NAS packet to the third device. That is, the third device obtains the device identifier of the first device through the NAS packet, while the second device does not parse the NAS packet and cannot obtain the device identifier of the first device through it. Therefore, in this application, the third device provides identification information to the second device so that the second device can know the AS ID of the first device for use in subsequent processes.

[0458] In some embodiments, after the first device determines its AS ID, it sends first data to the second device. Correspondingly, the second device receives the first data from the first device. The first data is associated with the AS ID of the first device. After receiving the first data, the second device sends UL data to the third device, as shown in FIG13.

[0459] In this application, the first data is associated with the AS ID of the first device, which can be understood as the first data including the AS ID of the first device, or the first data being masked using the AS ID of the first device.

[0460] In some embodiments, after the second device sends the first information, the second device sends a first command to the first device. Accordingly, the first device receives the first command from the second device. The first command is associated with the AS ID of the first device, as shown in FIG13 or FIG14.

[0461] In this application, the first command is associated with the AS ID of the first device, which can be understood as the first command including the AS ID of the first device, or the first command using the AS ID of the first device masked.

[0462] In related technologies, the AS ID is an access layer identifier. It can be a reused random identifier or assigned by a second device (such as a reader) and indicated to the first device (such as an A-IoT device) that successfully resolves the access / contention issue via Msg2. However, whether the first device stores the AS ID is not disclosed in these technologies. For example, if the first device stores the AS ID but subsequent processes do not use it, it will consume the first device's storage resources. Conversely, if the first device releases the AS ID but subsequent processes use it, it will affect those processes.

[0463] In view of this, this application provides a communication method. This method can be applied to the systems shown in Figures 1-7. The method includes:

[0464] Send the first data. Receive the first message. The first message indicates that the first data transmission failed, and the first message also indicates whether to save or release the AS ID, or the first message includes the AS ID.

[0465] If the first piece of information includes the AS ID, it means that the first piece of information indicates that the AS ID should be saved. Conversely, if the first piece of information does not include the AS ID, it means that the first piece of information indicates that the AS ID should be released.

[0466] In this context, "release" can be understood as "discard". This application will use "release" as an example for explanation.

[0467] For example, the first information is feedback information.

[0468] Based on the above technical solution, in the scenario where the first data transmission fails, the first information indicates both the failure of the first data transmission and whether to save the AS ID. For example, if the first information indicates that the AS ID should be saved, or if the first information includes the AS ID, it means that the first device saves the AS ID for use in subsequent processes. Conversely, if the first information indicates that the AS ID should be released, or if the first information does not include the AS ID, it means that the first device releases the AS ID to save storage overhead.

[0469] The communication method proposed in this application embodiment will now be described in detail with reference to Figure 15. The communication method 1500 proposed in this application embodiment includes the following operations:

[0470] S1501, The first device sends the first data to the second device.

[0471] For example, the first data is included in Msg3.

[0472] It's understandable that the first piece of data might be transmitted successfully or it might fail.

[0473] For the second device, the second device executes S1502:

[0474] S1502, the second device sends first information to the first device. Correspondingly, the first device receives the first information from the second device.

[0475] The first information indicates that the first data transmission failed.

[0476] For example, a first data transmission failure includes at least one of the following: first data reception failure; or first data reception success but decoding failure.

[0477] For example, the first data is included in Msg3, that is, Msg3 transmission fails, as shown in Figure 16 or Figure 17.

[0478] The first information may also indicate the release of the AS ID. For example, if the second device determines that the AS ID will not be used in subsequent processes, the first information may also indicate the release of the AS ID, or the first information may not include the AS ID.

[0479] Alternatively, the first information may also instruct the storage of the AS ID. For example, when the second device determines that the AS ID will be used in a subsequent process, the first information may also instruct the storage of the AS ID.

[0480] Alternatively, the first information may also include the AS ID. For example, when the second device determines that the AS ID will be used in a subsequent process, the first information may also include the AS ID.

[0481] Optionally, if the first information also includes an AS ID, the first device saves the AS ID. For example, if AS ID1 is currently saved, and the received first information includes AS ID2, then AS ID2 is used instead of AS ID1 and saved as AS ID2.

[0482] For example, the first piece of information is feedback, which indicates whether the AS ID should be saved.

[0483] For the first device, if the first information indicates that the AS ID should be saved, or if the first information includes the AS ID, the first device saves the AS ID for use in subsequent processes. If the first information indicates that the AS ID should be released, or if the first information does not include the AS ID, the first device releases the AS ID to save storage resources.

[0484] It is understandable that the first device obtains the AS ID in advance before executing S1501. For example, the AS ID is a reused random identifier, or the AS ID is assigned by the second device.

[0485] As a possible example, the AS ID is assigned by the second device via Msg2, as shown in Figure 16 or Figure 17:

[0486] S1, the second device sends an RA trigger message to the first device. Correspondingly, the first device receives the RA trigger message from the second device.

[0487] S2, in response to the RA trigger message, the first device sends Msg1 to the second device. Correspondingly, the second device receives Msg1 from the first device. Msg1 includes a random identifier. The first device also stores the random identifier.

[0488] S3, when the first device successfully resolves the random access contention, the second device sends Msg2 to the first device. Correspondingly, the first device receives Msg2 from the second device. Wherein, if the AS ID reuses the random identifier, then Msg2 does not include the AS ID. The first device uses the random identifier as the AS ID. If the second device assigns an AS ID to the first device, the assigned AS ID is included in Msg2, and the first device replaces the random identifier with the assigned AS ID.

[0489] Based on the above S1-S3, the first device obtains the AS ID.

[0490] As another possible example, the AS ID is assigned by the second device via a feedback message.

[0491] As another possible example, the AS ID is assigned by the second device via downlink data. This downlink data includes at least one of the following: R2D upper layer data (or commands, or upper-layer data).

[0492] As another possible example, the AS ID is assigned by a second device via dedicated signaling.

[0493] In some embodiments, if the first information indicates that the AS ID is stored or if the first information includes the AS ID, the second device sends a paging message to the first device. Accordingly, the first device receives the paging message from the second device. The paging message includes the AS ID of the first device, as shown in FIG17. The inclusion of the AS ID in the paging message can be understood as the paging message paging the first device.

[0494] When the paging message includes the AS ID of the first device, the first device sends second data to the second device. Accordingly, the second device receives the second data from the first device, as shown in Figure 17, thereby achieving CFRA without needing to obtain the AS ID again.

[0495] In some embodiments, when the first information indicates the release of the AS ID or the first information does not include the AS ID, the second device, when paging the first device, sends the RA trigger message again to achieve re-access through the access procedure.

[0496] This application further provides a communication method. This method can be applied to the systems shown in Figures 1-7. The method includes:

[0497] Receive first data, the first data including first information, the first information indicating to save or release AS ID or the first information including AS ID.

[0498] If the first piece of information includes the AS ID, it means that the first piece of information indicates that the AS ID should be saved. Conversely, if the first piece of information does not include the AS ID, it means that the first piece of information indicates that the AS ID should be released.

[0499] For example, the first data is a command, such as read, write, lock, deactivate, or sense commands.

[0500] For example, the first data includes upper-layer data. Upper-layer data refers to data above the AS layer, or higher-level data. The upper layer may include the NAS layer, or the application layer, etc.

[0501] Based on the above technical solution, in a command scenario, the first command indicates both read, write, lock, deactivate, and sensor operations, and whether to save the AS ID. For example, if the first information indicates saving the AS ID or includes the AS ID, it means that the first device saves the AS ID for use in subsequent processes. Conversely, if the first information indicates releasing the AS ID or does not include the AS ID, it means that the first device releases the AS ID to save storage overhead.

[0502] The communication method proposed in this application embodiment will now be described in detail with reference to Figure 18. The communication method 1800 proposed in this application embodiment includes the following operations:

[0503] S1801, the second device sends first data to the first device. Correspondingly, the first device receives the first data from the second device.

[0504] The first data includes first information. The first information indicates whether to save or release the AS ID, or the first information includes the AS ID. For example, when the second device determines that the AS ID will be used in a subsequent process, the first information indicates whether to save the AS ID, or the first information includes the AS ID. As another example, when the second device determines that the AS ID will not be used in a subsequent process, the first information indicates whether to release the AS ID, or the first information does not include the AS ID.

[0505] For example, the first data includes commands such as read, write, lock, deactivate, and sense commands, to indicate whether to save the AS ID.

[0506] For the first device, if the first information indicates that the AS ID should be saved, or if the first information includes the AS ID, the first device saves the AS ID for use in subsequent processes. If the first information indicates that the AS ID should be released, or if the first information does not include the AS ID, the first device releases the AS ID to save storage resources.

[0507] In some embodiments, the first data may also implicitly indicate that the second data transmission was successful. For example, the first device sends the second data to the second device. Accordingly, the second device receives the second data from the first device. Then, the second device executes S1801. That is, the first data is downlink data following the second data. In this case, the first data may also implicitly indicate that the second data transmission was successful.

[0508] It is understandable that the first device obtains the AS ID in advance before executing S1801. For example, the AS ID is a reused random identifier, or the AS ID is assigned by the second device, as shown in Figure 18:

[0509] In a CFRA scenario, the second device sends a paging message to the first device. Correspondingly, the first device receives the paging message from the second device. The paging message includes an AS ID, which is an AS ID assigned to the first device by the second device.

[0510] In related technologies, paging messages include a paging identifier to indicate the paging device. The length of the paging identifier is variable, so the paging message also indicates the length of the paging identifier, resulting in high overhead.

[0511] In view of this, this application provides a communication method. This method can be applied to the systems shown in Figures 1-7. The method includes:

[0512] Receive a paging message, which includes Access Layer (AS) information and a paging identifier. The AS information precedes the paging identifier, and the paging identifier ends at the least significant byte (LSB) of the paging message. Determine the AS information and paging identifier based on the paging message.

[0513] In the paging message, the AS information and the paging identifier are positioned as follows: the AS information precedes the paging identifier. In other words, the AS information is located before / to the left of the paging identifier, or the paging identifier is located after / to the right of the AS information.

[0514] The paging identifier ends at the LSB of the paging message, which can be understood as the paging identifier being located at the end of the paging message.

[0515] The format of AS information is fixed. For example, AS information is a MAC subheader.

[0516] The length of the paging identifier is dynamically variable. A paging identifier can be one of the following: a permanent identifier, a temporary identifier, or a mask / filter / group identifier.

[0517] As shown in Figure 19, each type of identifier includes two parts. Part 1 includes the identifier type (ID type) and the network identifier. Optionally, Part 1 also includes information used to identify a third party. The lengths of the identifier type, the network identifier (if present), and the information used to identify a third party (if present) are fixed; therefore, the length of Part 1 is fixed. Part 2, for example, includes electronic product code (EPC) information. The length of Part 2 is dynamically variable. Therefore, the length of the paging identifier is dynamically variable.

[0518] Furthermore, the length of the mask is also variable. Therefore, the length of the paging identifier changes dynamically.

[0519] Based on the above technical solution, the positions of the AS information and the paging identifier are constrained in the paging message. For example, the AS information is located before the paging identifier, and the format of the AS information is known or can be known by the first device. Therefore, the first device can determine the length of the AS information (or determine the length or end position of the information other than the paging identifier), thereby determining the start position of the paging identifier. Then, the paging identifier is delivered to the upper layers, as shown in Figure 21. Based on this, the paging message does not need to indicate the length of the paging identifier, or the length of the information delivered to the upper layers, which simplifies the design of the paging message and saves the signaling overhead of the paging message.

[0520] Compared to related technologies, the paging message signaling overhead of this application is small, as detailed below:

[0521] In related technologies, the positions of the AS information and the paging identifier are not restricted, so the paging message needs to indicate the length of the paging identifier. For example, the length of the paging identifier is variable. When the paging identifier precedes the AS information, the first device needs to determine the paging identifier based on the length of the paging identifier indicated by the paging message.

[0522] In this application, the constraint AS information is located before the paging identifier, and the format of the AS information is fixed. Therefore, even if the length of the paging identifier varies and the paging message does not indicate the length of the paging identifier, the first device can still determine the paging identifier in the paging message, simplifying the design of the paging message and saving the signaling overhead of the paging message.

[0523] It should be added that, in this application, LSB refers to the least significant bit of the signaling (or MAC message or MAC layer content), such as the rightmost / bottommost position of the signaling. LSB can be described in other ways, such as least significant byte, least significant byte (LSB), least (or most significant or least significant or rightmost) bit / byte / bit string / string / byte string / position. The position refers to the location of one or more bits / bytes.

[0524] It should be added that, in this application, the most significant bit (MSB) refers to the highest bit of the signaling (or MAC message or MAC layer content), such as the leftmost / topmost position of the signaling. MSB can be described in other ways, such as highest bit, most significant byte (MSB), highest (or most significant or most significant or leftmost or first) bit / byte / bit string / string / byte string / position. The position refers to the location of one or more bits / bytes.

[0525] The communication method proposed in this application embodiment will now be described in detail with reference to Figure 20. The communication method 2000 proposed in this application embodiment includes the following operations:

[0526] S2001, The second device determines the paging message.

[0527] The paging message includes AS information and a paging identifier. The AS information precedes the paging identifier, and the paging identifier ends at the LSB of the paging message.

[0528] For example, a paging message includes an AS field and a paging identifier field, with the AS field preceding the paging identifier field. The AS field includes AS information, and the paging identifier field includes the paging identifier.

[0529] It should be noted that in this application, "domain" can also be described in other ways, such as "field". For example, the AS domain can also be described as the AS field. The paging identifier domain can also be described as the paging identifier field.

[0530] It should be noted that AS information can also be described in other ways, such as AS layer information. AS information is located in the MAC subheader.

[0531] Optionally, the AS information begins at the MSB of the paging message.

[0532] Optionally, the end position of the AS information is adjacent to the start position of the paging identifier. This can be understood as the last bit of the AS information being adjacent to the first bit of the paging identifier; or, for the last bit of the AS information, the next bit is the first bit of the paging identifier.

[0533] It is understood that when the start position of the AS information is the MSB of the paging message, the end position of the AS information is adjacent to the start position of the paging identifier, and the end position of the paging identifier is the LSB of the paging message, it means that there is no MAC layer padding content in the paging message. It is also understood that in this application, the end position of the paging identifier can be described in other ways, such as a field or domain of the paging identifier.

[0534] Optionally, the AS information includes at least one of the following: message type, control information, or access resource indication information, etc. The formats of the message type, control information, and access resource indication information are fixed.

[0535] For the second device, after determining the paging message, it executes S2002:

[0536] S2002, the second device sends a paging message to the first device. Correspondingly, the first device receives the paging message from the second device.

[0537] For the first device, after receiving the paging message, it executes S2003:

[0538] S2003. The first device determines the AS information and paging identifier based on the paging message.

[0539] The paging message, as described in S2001, will not be repeated here. For the first device, it determines the AS information and paging identifier based on the message format of the paging message.

[0540] For example, the first device first reads the fixed-format AS information in the paging message, and the remaining part is the paging identifier, which is then delivered to the upper layers. The paging message does not need to indicate the length of the paging identifier, and the paging message overhead is small.

[0541] It is understandable that in Communication Method 2000, the paging identifier can also be replaced with upper-layer information. This upper-layer information refers to information above the access layer, such as NAS, application layer, and A-IoT layer.

[0542] Based on the above scheme, as a possible interpretation, the paging identifier field will be placed at the end of the paging message. Therefore, the paging identifier field does not need to have a length field in the paging message. Optionally, the paging message does not contain MAC layer padding content, or the paging message does not contain MAC layer padding content with varying lengths.

[0543] Based on the above scheme, as another possible interpretation, assuming that there is no MAC layer padding in the paging message and the paging identifier field will be placed at the end of the paging message, then the paging identifier field does not need to have a length field.

[0544] In related technologies, after the first device successfully connects randomly, data transmission begins. This data transmission may succeed or fail. The first device determines whether to retransmit the data based on Msg2. However, in some scenarios, the first device cannot determine whether to retransmit, affecting data transmission performance.

[0545] To ensure data transmission performance, this application provides a communication method. This method can be applied to the systems shown in Figures 1-7. The method includes:

[0546] Receive a first message, which includes a first AS ID. This first message is a contention resolution message. Send first data. The first AS ID is the same as a second AS ID, which is stored in the first device.

[0547] The fact that the first AS ID is the same as the second AS ID can be understood as the AS ID carried in the first message being the same as the AS ID stored in the first device, or the first message including the AS ID stored in the first device. This means that the first message also instructs the first device to transmit (or retransmit) the first data, or that the first device needs to transmit (or retransmit) the first data. Accordingly, the first device sends the first data to ensure data transmission performance.

[0548] It should be noted that, in this application, retransmission can be understood as transmission or retransmission. For example, replacing retransmission with transmission or retransmission.

[0549] In related technologies, the first device cannot determine whether to retransmit, as detailed below:

[0550] The first device generates a random identifier and then sends it as Msg1. Msg1 contains the random identifier. After sending Msg1, the first device saves the random identifier for later use. For example, when the first device receives Msg2, it compares the saved random identifier with the random identifier in Msg2; if they are the same, the connection is successful.

[0551] In some embodiments, the second device assigns an AS ID to the first device via Msg2. The assigned AS ID corresponds to the aforementioned random identifier. Considering the storage overhead of the first device, upon receiving a newly assigned AS ID, the first device replaces (discards) the previously stored random identifier, rendering the random identifier invalid. That is, the first device stores only one identifier: before receiving a newly assigned AS ID, it stores the random identifier; after receiving the newly assigned AS ID, it discards the random identifier and stores the newly assigned AS ID.

[0552] However, for the first device that successfully connects, it sends Msg3 to achieve uplink data (or D2R data) transmission. If Msg3 transmission fails, the second device retransmits Msg2 to trigger the retransmission of Msg3. The retransmitted Msg2 carries a random identifier, which is identical to the random identifier in Msg1, thus triggering the first device to retransmit Msg3.

[0553] However, when the first device obtains the newly assigned AS ID, it has replaced (discarded) the originally saved random identifier, and cannot determine whether to retransmit Msg3 through the random identifier, which affects the data transmission performance.

[0554] In this application, the first message includes a first AS ID. If the first AS ID is the same as the second AS ID, it means that the first device needs to send (e.g., retransmit) the first data. In other words, this application determines whether to transmit the first data based on the AS ID, thereby ensuring data transmission performance.

[0555] The communication method proposed in this application embodiment will now be described in detail with reference to Figure 22. The communication method 2200 proposed in this application embodiment includes the following operations:

[0556] S2201, the second device sends a first message to the first device. Correspondingly, the first device receives the first message from the second device.

[0557] The first message is the contention resolution message. For example, if the first message is Msg2, it could be either an initial transmission of Msg2 or a retransmission of Msg2.

[0558] The first message includes a first random identifier and a first AS ID. The first random identifier corresponds to the first AS ID.

[0559] In this application, the first random identifier corresponds to the first AS ID, which can be understood as follows: the first random identifier and the first AS ID correspond to the same device (such as an A-IoT device or a chip in an A-IoT device), the first random identifier is generated and sent by the device, and the first AS ID is the AS ID assigned to the device. In this application, the first random identifier and the first AS ID correspond to the first device.

[0560] For the first device, after receiving the first message, it executes S2202:

[0561] S2202, the first device sends first data to the second device. Correspondingly, the second device receives the first data from the first device.

[0562] The first data includes the device identifier and / or upper-layer data. The first data is included in Msg3. Sending the first data can also be described as sending Msg3.

[0563] Next, S2202 will be introduced through two cases (case 1-case 2 below):

[0564] Case 1, for random identifiers:

[0565] In scenario 1, the first random identifier and the second random identifier are the same, and the second random identifier is stored in the first device. That is, if the first random identifier and the second random identifier are the same, the first device sends the first data to the second device.

[0566] In scenario 1, the first message is either the initial transmission of Msg2 or a retransmission of Msg2.

[0567] In this application, the first random identifier and the second random identifier are the same. This can be understood as the first random identifier carried in the first message being the same as the second random identifier stored in the first device, or the first message including the random identifier stored in the first device. This means that the first device has successfully resolved the random access contention, or that the first device is able to transmit the first data. In this case, the first device sends the first data to the second device, including: initial transmission or retransmission of the first data. For example, before executing S2201, the first device sends the first data to the second device, but the second device does not receive the first data from the first device. Then, the second device sends a first message to the second device based on the first random identifier to indicate initial transmission or retransmission of the first data.

[0568] Scenario 2, for AS ID:

[0569] In scenario 2, the first AS ID and the second AS ID are the same, and the second AS ID is stored in the first device. That is, if the first AS ID and the second AS ID are the same, the first device sends the first data to the second device.

[0570] In scenario 2, the first message is a retransmission of Msg2.

[0571] In this application, the first AS ID and the second AS ID are the same. This can be understood as the first AS ID carried in the first message being the same as the second AS ID stored in the first device, or the first message including the AS ID stored in the first device. This means that the first message also instructs the first device to transmit (or retransmit) the first data, or that the first device needs to transmit (or retransmit) the first data. In this case, the first device sending the first data to the second device includes retransmitting the first data. For example, before executing S2201, the first device sends the first data to the second device, but the second device does not receive the first data from the first device. In this case, the second device sends a first message to the second device based on the first AS ID to instruct the retransmission of the first data.

[0572] Based on the above technical solution, situation 2 can be understood as follows:

[0573] In scenario 2, the first message is Msg2, and Msg2 is retransmitted. For the first device, when it receives Msg2 again, it determines whether to send Msg3 based on whether Msg2 includes the currently stored AS ID (such as the second AS ID). If it does, it retransmits Msg3; if it does not, it does not respond to Msg2.

[0574] Based on the above technical solution, S2202 can be understood as follows:

[0575] The first device (after sending Msg1) receives Msg2. Based on whether Msg2 includes a currently stored random identifier (such as a second random identifier) ​​or AS ID (such as a second AS ID), it determines whether to send Msg3 and / or upper-layer data. If it does, it (re)transmits Msg3; otherwise, it does not respond to Msg2. Alternatively, if Msg2 has not been received, upon receiving it, it determines whether to send Msg3 based on the random ID, such as whether Msg2 includes a currently stored random identifier (such as a second random identifier).

[0576] It should be noted that in this application, the first device stores an identifier. This identifier can be a second random identifier or a second AS ID. If the first random identifier carried by the first message is the same as the second random identifier stored by the first device, the first device sends first data to achieve data transmission. If the first AS ID carried by the first message is the same as the second AS ID stored by the first device, the first device sends first data to achieve data transmission.

[0577] It should be added that, in this application, the second random identifier is stored in the first device. For example, before executing S2201, the first device performs the following operations:

[0578] The first device generates a second random identifier. The first device sends Msg1 to the second device. Msg1 includes the second random identifier. The first device stores the second random identifier until it receives an assigned AS ID, such as the first AS ID.

[0579] It should be added that, in this application, the second AS ID is stored in the first device. For example, before executing S2201, the first device performs the following operations:

[0580] The first device generates a second random identifier. The first device sends Msg1 to the second device. Msg1 includes the second random identifier. The first device receives a second message from the second device, such as Msg2. The second message (Msg2) includes the second random identifier and a second AS ID. The second AS ID is an AS ID assigned to the first device by the second device. The first device stores the second AS ID. Additionally, considering the storage overhead of the first device, the first device also replaces (discards) the previously stored second random identifier.

[0581] Below, with reference to Figure 23, possible examples are given:

[0582] S2301, the first device sends Msg1 to the second device. Correspondingly, the second device receives Msg1 from the first device.

[0583] Msg1 includes a second random identifier.

[0584] The second random identifier is generated and stored by the first device until the first device is assigned an AS ID, such as the second AS ID.

[0585] S2302, the second device sends Msg2 to the first device. Correspondingly, the first device receives Msg2 from the second device.

[0586] Msg2 includes a first random identifier and a second AS ID. The first random identifier corresponds to the second AS ID. The first random identifier and the second random identifier are the same. Please refer to the introduction of S2201 for details.

[0587] For example, in S2302, Msg2 is the initial transmission Msg2.

[0588] For the first device, the first device stores the second AS ID and also replaces (discards) the originally stored second random identifier.

[0589] S2303, The first device sends Msg3 to the second device.

[0590] In this process, the first random identifier is the same as the second random identifier, and the second random identifier is stored in the first device. That is to say, if the first random identifier carried by the initial transmission Msg2 is the same as the second random identifier, the first device sends Msg3 to the second device. For the initial transmission of Msg3, please refer to the description of S2202, which will not be repeated here.

[0591] Msg3 includes the first data, which can be found in the description of S2202 and will not be repeated here.

[0592] For the second device, it did not receive Msg3 from the first device. The second device executes S2304:

[0593] S2304. The second device sends Msg2 to the first device. Correspondingly, the first device receives Msg2 from the second device.

[0594] Msg2 includes a first random identifier and a first AS ID. The first AS ID is the same as the second AS ID. Please refer to the introduction of S2201 for details, which will not be repeated here.

[0595] For example, in S2304, Msg2 is a retransmission of Msg2.

[0596] In other words, the initial Msg2 and the retransmitted Msg2 carry the same random identifier (such as the first random identifier) ​​and AS ID (such as the first AS ID).

[0597] S2305, the first device sends Msg3 to the second device. Correspondingly, the second device receives Msg3 from the first device.

[0598] In this configuration, the first AS ID is the same as the second AS ID, and the second AS ID is stored in the first device. That is, if the first AS ID carried by the retransmission Msg2 is the same as the second AS ID, the first device sends Msg3 to the second device. For retransmission of Msg3, please refer to the description of S2202, which will not be repeated here.

[0599] In addition, after the first device discards the second random identifier, it no longer compares the random identifier of the retransmitted Msg2.

[0600] To ensure data transmission performance, this application also provides a communication method. This method can be applied to the systems shown in Figures 1-7.

[0601] As shown in Figure 24, the communication method 2400 of this application includes the following operations:

[0602] S2401, the first device sends Msg1 to the second device. Correspondingly, the second device receives Msg1 from the first device.

[0603] Msg1 includes a second random identifier.

[0604] The second random identifier is generated and stored by the first device.

[0605] It should be noted that in communication method 2400, the first device does not replace (discard) the second random identifier even if it is assigned an AS ID. Of course, the first device stores the assigned AS ID.

[0606] S2402, the second device sends Msg2 to the first device. Correspondingly, the first device receives Msg2 from the second device.

[0607] Msg2 includes a first random identifier and a second AS ID. The first random identifier corresponds to the second AS ID. The first random identifier and the second random identifier are the same. Please refer to the introduction of S2201 for details.

[0608] For example, in S2402, Msg2 is the initial transmission Msg2.

[0609] For the first device, the first device stores the second AS ID, but does not replace (discard) the previously stored second random identifier. That is, the first device stores the newly assigned AS ID, but does not replace (discard) the previously stored second random identifier with the newly assigned AS ID.

[0610] S2403, The first device sends Msg3 to the second device.

[0611] In this process, the first random identifier is the same as the second random identifier, and the second random identifier is stored in the first device. That is to say, if the first random identifier carried by the initial transmission Msg2 is the same as the second random identifier, the first device sends Msg3 to the second device. For the initial transmission of Msg3, please refer to the description of S2202, which will not be repeated here.

[0612] Msg3 includes the first data.

[0613] For the second device, it did not receive Msg3 from the first device. The second device executes S2404:

[0614] S2404, the second device sends Msg2 to the first device. Correspondingly, the first device receives Msg2 from the second device.

[0615] Msg2 includes a first random identifier and a first AS ID.

[0616] For example, in S2404, Msg2 is a retransmission of Msg2.

[0617] In other words, the initial Msg2 and the retransmitted Msg2 carry the same random identifier (such as the first random identifier).

[0618] It should be noted that the AS ID carried by the initial Msg2 and the retransmitted Msg2 can be the same or different. In other words, the first AS ID and the second AS ID can be the same or different.

[0619] S2405, the first device sends Msg3 to the second device. Correspondingly, the second device receives Msg3 from the first device.

[0620] In this process, the first random identifier is the same as the second random identifier, and the second random identifier is stored in the first device. That is, if the first random identifier carried by the retransmitted Msg2 is the same as the second random identifier, the first device sends Msg3 to the second device, and so on, such as retransmitting Msg3.

[0621] In addition, if the first random identifier is the same as the second random identifier, but the first AS ID is different from the second AS ID, the first device saves the first AS ID and replaces (discards) the originally saved second AS ID.

[0622] Based on the above technical solution, it can be understood as follows:

[0623] The first device (after sending Msg1) receives Msg2. Based on whether Msg2 includes a currently stored random identifier (such as a second random identifier), it determines whether to send Msg3. If it does, it (re)transmits Msg3; otherwise, it does not respond to Msg2. Alternatively, if Msg2 has not been received, upon receiving it, it determines whether to send Msg3 based on the random ID, such as whether Msg2 includes a currently stored random identifier (such as a second random identifier).

[0624] In related technologies, each terminal device (such as an A-IoT device) possesses a device identifier. In inventory management scenarios, the terminal device (such as an A-IoT device) reports the complete device identifier to the network device (such as a reader) to achieve inventory management. However, the complete device identifier has a large number of bits, resulting in significant air interface overhead.

[0625] To reduce air interface overhead, this application provides a communication method. This method can be applied to the systems shown in Figures 1-7. The method includes:

[0626] Receive a first message, which includes a network identifier. Send first data, which includes a first identifier, which is part of a second identifier and does not include the network identifier. The second identifier is the device identifier of the first device.

[0627] The device identifier comprises two parts. Part 1 includes the ID type and network identifier. Optionally, Part 1 also includes information used to identify a third party. Part 2 includes, for example, evolved packet core (EPC) information, as shown in Figure 19.

[0628] The first identifier is a part of the second identifier and does not include the network identifier. This can be understood as the first identifier not including the network identifier from the second identifier. In other words, the first identifier is an incomplete device identifier.

[0629] For different devices selected by the same first message, the network identifier is the same in the device identifier of each device and is carried by the same first message. Based on this, when the first device determines that it needs to respond to the first message and sends first data according to the network identifier included in the first message, it can carry an incomplete device identifier, such as a first identifier, which at least does not include the network identifier, to save air interface overhead. Compared to reporting the complete device identifier, the air interface overhead of this application is smaller.

[0630] The communication method proposed in this application embodiment will now be described in detail with reference to Figure 25. The communication method 2500 proposed in this application embodiment includes the following operations:

[0631] S2501, the second device sends a first message to the first device. Correspondingly, the first device receives the first message from the second device.

[0632] The first message includes the network identifier.

[0633] Optionally, the first message may include third-party identifiers, such as information used to identify third parties.

[0634] For example, the first message includes a paging identifier to indicate the paging device. The paging identifier is a device identifier, as illustrated in Figure 19.

[0635] For example, the first message can be one of the following: a paging message, an R2D trigger message, or Msg2, etc.

[0636] For the first device, after receiving the first message, it executes S2502:

[0637] S2502, the first device sends first data to the second device. Correspondingly, the second device receives the first data from the first device.

[0638] The first data includes a first identifier, which is part of a second identifier and does not include a network identifier. The second identifier is the device identifier of the first device. In other words, the first identifier is an incomplete device identifier, at least not including the network identifier.

[0639] For example, the first identifier includes the identifier type, third-party identifier, and EPC information, but does not include the network identifier, thus saving air interface overhead.

[0640] For example, the first identifier includes the identifier type and EPC information, but does not include the network identifier and third-party identifier, thereby further saving air interface overhead.

[0641] In some embodiments, the first message includes first information, which indicates that a first identifier should be reported. Accordingly, S2502 includes: in response to the first information, the first device sends first data to second data. The first data includes the first identifier. That is, the first message indicates whether a network identifier is carried during the device identifier reporting process.

[0642] In related technologies, after each device (such as an A-IoT device) sends D2R data, it expects to receive R2D data within a certain time period. This time period is determined by the parameter T_D2R. However, the parameter T_D2R is uniformly configured, leading to high power consumption or the inability to receive R2D data in a timely manner on the device side (such as the A-IoT device).

[0643] In view of this, this application provides a communication method. This method can be applied to the systems shown in Figures 1-7. The method includes:

[0644] Receive a paging message indicating at least two first values. Receive a first message indicating a second value, which is included among the at least two first values. Send first data. Receive second data during a first time period. The end time of the first time period is determined based on the transmission time of the first data and the second value, and the second data is the response data to the first data.

[0645] The first value, T_D2R(max), can be understood as the maximum duration between a D2R transmission and the corresponding R2D transmission that follows. For example, taking the first device as an example, T_D2R(max) refers to the maximum duration between the D2R transmission time and the R2D reception time.

[0646] It should be noted that in this application, duration can also be described in other ways, such as time unit. Duration can be a relative time length or an absolute time length. A relative time length can be understood as one or more time slots, one or more subframes, one or more frames, or one or more messages, etc. An absolute time length can be understood as microseconds (µs), milliseconds (ms), or seconds (s).

[0647] The end time of the first time period is determined based on the transmission time of the first data and the second value. For example, the end time of the first time period is the sum of the transmission time of the first data and the second value.

[0648] In other words, after the first device sends the first data, a second data transmission is expected as a response to the first data transmission, and the second data transmission is expected to occur within a first time period. The end time of the first time period is determined based on the transmission time of the first data and a second value. Since the second value is selected from at least two first values, the selection of the second value is more flexible and adaptable to the transmission of the second data, thereby helping to reduce power consumption on the first device side or enabling the first device to receive the second data in a timely manner.

[0649] For example, in some situations (such as inventory scenarios, direct feedback from the second device, short inventory time in cases with good coverage, or short processing time for the first device by the second device), the second value is smaller to reduce the power consumption on the first device side.

[0650] For example, in some situations (such as when the coverage is far and the access / storage time of each device is long, or when a third device needs to participate in the interaction in a command scenario, or when a device sends uplink data and needs to wait for a long time for feedback, such as when the feedback time of the third device is longer than that of the second device), the second value is larger so that the first device can receive the second data in a timely manner.

[0651] The communication method proposed in this application embodiment will now be described in detail with reference to Figure 26. The communication method 2600 proposed in this application embodiment includes the following operations:

[0652] S2601, the second device sends a paging message to the first device. Correspondingly, the first device receives the paging message from the second device.

[0653] The paging message indicates at least two first values.

[0654] It is understandable that, in at least two first values, each first value is described as follows:

[0655] The first value, which can be denoted as T_D2R(max), refers to the maximum duration between a D2R transmission and the corresponding R2D transmission that immediately follows. For example, taking the first device as an example, T_D2R(max) refers to the maximum duration between the D2R transmission time and the R2D reception time.

[0656] It is understandable that paging messages can be replaced with other broadcast messages.

[0657] S2602, the second device sends a first message to the first device. Correspondingly, the first device receives the first message from the second device.

[0658] The first message indicates a second value, which is included in at least two first values. This can be understood as the first message indicating that the second value is used for receiving second data.

[0659] For example, the first message includes at least one of the following: Msg2, a feedback message. Alternatively, the first message may be replaced with downlink data.

[0660] For the first device, after receiving the paging message and the first message, it executes S2603:

[0661] S2603, The first device sends first data to the second device. Correspondingly, the second device receives the first data from the first device.

[0662] For example, the first data is D2R data.

[0663] For example, the transmission time of the first data is denoted as t.

[0664] It should be noted that, for the first device, the transmission time of the first data can be understood as the sending time of the first data.

[0665] It should be noted that the transmission time of the first data can be understood as the start time of the first data (such as the moment when the first data begins) or the end time of the first data (such as the moment when the transmission of the first data ends).

[0666] S2604. The second device sends second data to the first device during the first time period. Correspondingly, the first device receives the second data from the second device during the first time period.

[0667] The second data is the response data to the first data. For example, the second data is R2D data.

[0668] The end time of the first time period is determined based on the transmission time of the first data and the second value. For example, the end time of the first time period is the sum of the transmission time of the first data and the second value, denoted as t+T_D2R(max).

[0669] Based on the above technical solution, the second value is selected from at least two first values. Therefore, the selection of the second value is more flexible and can better adapt to the transmission of the second data, thereby reducing the power consumption of the first device or enabling the first device to receive the second data in a timely manner.

[0670] In some embodiments, the paging message further indicates at least two third values. Furthermore, the first message also indicates a fourth value, which is included among the at least two third values. Accordingly, the start time of the first time period is determined based on the transmission time of the first data and the fourth value. Exemplarily, the start time of the first time period is the sum of the transmission time of the first data and the fourth value, denoted as t+T_D2R(min). Accordingly, the first time period is denoted as [t+T_D2R(min), t+T_D2R(max)].

[0671] It should be noted that, in at least two third values, each third value is described as follows:

[0672] The third value, which can be denoted as T_D2R(min), refers to the shortest duration between a D2R transmission and the corresponding R2D transmission that immediately follows. For example, taking the first device as an example, T_D2R(max) refers to the shortest duration between the D2R transmission time and the R2D reception time.

[0673] In some embodiments, this application further includes: a first device starting a first timer. The runtime of the first timer is a first time period. That is, the first time period is indicated by the running state of the first timer. It can be understood that S2604 includes: during the operation of the first timer, the first device receiving second data from the second device. Since the operation of the first timer is determined according to the first time period, the power consumption of the timer operation can also be reduced.

[0674] In related technologies, the AS ID is identification information visible to both the first and second devices. The AS ID can be a reused random identifier or assigned by the second device and indicated to the first device that successfully resolves the access / contention issue via Msg2. The first device's inability to continuously store the AS ID leads to high storage overhead, conflicts between the stored AS ID and a new AS ID causing erroneous responses, or conflicts between the stored AS ID and a new random identifier causing erroneous responses.

[0675] In view of this, this application provides a communication method. This method can be applied to the systems shown in Figures 1-7. The method includes:

[0676] A random identifier is generated. If a random identifier is generated, the AS ID is released, or the random identifier replaces the AS ID. The AS ID is stored in the first device. The AS ID stored in the first device can be a reused random identifier or it can be assigned by the second device.

[0677] In other words, during a new random access, a random identifier is generated, and the AS ID is released / reset / discarded / saved to avoid the phenomenon of the same AS ID being stored indefinitely, thereby saving storage overhead and reducing conflicts or error response problems caused by the same AS ID being stored indefinitely.

[0678] Alternatively, during a new random access, a random identifier can be generated and used to replace the saved AS ID, thereby updating the saved AS ID. This can improve storage resource utilization and reduce conflicts or error response issues caused by the same AS ID being saved continuously.

[0679] In related technologies, the first device determines whether it has successfully connected based on Msg2. If the connection is successful, data transmission proceeds. However, in some scenarios, the first device cannot determine which Msg2 corresponds to itself, causing it to be unable to determine whether the connection has been successful and affecting data transmission performance.

[0680] In view of this, this application provides two communication methods (communication method 2700 and communication method 2800 hereinafter). The communication methods provided in this application can be applied to the systems shown in Figures 1-7.

[0681] The communication method 2700 proposed in this application will be described in detail below with reference to Figure 27:

[0682] S2701, the second device sends a first message to the first device. Correspondingly, the first device receives the first message from the second device.

[0683] The first message is the contention resolution message. For example, if the first message is Msg2, it could be either an initial transmission of Msg2 or a retransmission of Msg2.

[0684] The first message includes a first random identifier and a first AS ID. The first random identifier corresponds to the first AS ID.

[0685] In this application, the first random identifier corresponds to the first AS ID, which can be understood as follows: the first random identifier and the first AS ID correspond to the same device (such as an A-IoT device or a chip in an A-IoT device), the first random identifier is generated and sent by the device, and the first AS ID is the AS ID assigned to the device. In this application, the first random identifier and the first AS ID correspond to the first device.

[0686] For the first device, after receiving the first message, it executes S2702:

[0687] S2702, the first device sends first data to the second device. Correspondingly, the second device receives the first data from the first device.

[0688] The first data includes the device identifier and / or upper-layer data. The first data is included in Msg3. Sending the first data can also be described as sending Msg3.

[0689] Sending the first data can be understood as either transmitting the first data initially or retransmitting the first data.

[0690] Next, S2702 will be introduced through two cases (case 1-case 2 below):

[0691] Scenario 1, for AS ID:

[0692] In scenario 1, the first AS ID and the second identifier are the same, and the second identifier is stored in the first device. That is, if the first AS ID and the second identifier are the same, the first device successfully connects and sends the first data to the second device. If the first AS ID and the second identifier are different, please refer to the description of scenario 2 below, which will not be elaborated here.

[0693] In this application, the first AS ID and the second identifier are the same. This can be understood as the first AS ID carried in the first message being the same as the second identifier stored in the first device, or the first message including the second identifier stored in the first device. This means that the first message corresponds to the first device, or the first message indicates that the first device has successfully accessed the network, or the first message indicates that the first device transmits (or retransmits) the first data, or the first device needs to transmit (or retransmit) the first data.

[0694] It should be noted that, as one possible interpretation, when the first AS ID and the second identifier are the same, it can be understood that the second identifier stored by the first device is the AS ID, such as denoted as the second AS ID. The second AS ID is assigned by the second device, as detailed in Example 2 below, and will not be elaborated further here.

[0695] Based on the above technical solution, for situation 1, it can be understood as follows:

[0696] For the first device, upon receiving the first message again, it determines whether the access was successful based on whether the first AS ID and the second identifier of the first message are the same. If they are the same, the access is successful, and the first data is (re)transmitted. If they are different, the random identifier is compared, as detailed in the description of case 2 below, which will not be repeated here. It should be understood that in communication methods 2700 and 2800 of this application, successful access can also be replaced by other behavioral descriptions: for example, triggering the transmission of the first data, or successfully resolving the contention, or indicating that the previous transmission of the first data failed (it was sent once before, but the transmission failed).

[0697] Alternatively, for the first device, when the first device (again) receives the first message, it determines whether to (re)transmit the first data based on whether the first AS ID and the second identifier of the first message are the same. If they are the same, the first data is (re)transmitted. If they are different, the random identifier is compared. See the description of case 2 below for details, which will not be repeated here.

[0698] Alternatively, for the first device, if the first device (again) receives the first message, in which the first AS ID is the same as the second identifier, or the first message includes an AS ID that is the same as the second identifier, then the access is successful, and the first data is (re)transmitted.

[0699] Case 2, for random identifiers:

[0700] In scenario 2, if the first AS ID and the second identifier are different, the first random identifier and the second identifier are the same, and the second identifier is stored in the first device. That is, when the first device determines that the first AS ID and the second identifier are different, the first device continues to determine whether the first random identifier and the second identifier are the same. If they are the same, the first device successfully connects and sends the first data to the second device. If they are different, the first device fails to connect (or continues to receive Msg2), or the first device does not respond to the first message, or the first device does not send the first data.

[0701] In this application, the first random identifier and the second identifier are the same. This can be understood as the first random identifier carried in the first message being the same as the second identifier stored in the first device, or the first message including the second identifier stored in the first device. This means that the first message corresponds to the first device, or the first message indicates that the first device has successfully accessed the network, or the first message indicates that the first device transmits (or retransmits) the first data, or the first device needs to transmit (or retransmit) the first data.

[0702] It should be noted that, as one possible interpretation, when the first random identifier and the second identifier are the same, it can be understood that the second identifier stored by the first device is a random identifier, such as denoted as the second random identifier. The second random identifier is generated by the first device, as detailed in Example 1 or Example 2 below, and will not be elaborated further here.

[0703] It should be noted that in the communication method 2700 of this application, the first AS ID is different from the second identifier, which can be understood as the first message not containing an AS ID that is the same as the second identifier.

[0704] Based on the above technical solution, situation 2 can be understood as follows:

[0705] For the first device, when the first device (again) receives the first message, if the first AS ID and the second identifier are different, it determines whether the access is successful based on whether the first random identifier and the second identifier of the first message are the same. If they are the same, the access is successful and the first data is (re)transmitted. If they are different, the first device fails to access (or continues to receive Msg2), or the first device does not respond to the first message, or the first device does not send the first data.

[0706] Alternatively, for the first device, if the first device receives the first message again and the first AS ID is different from the second identifier, it determines whether to send the first data based on whether the first random identifier and the second identifier of the first message are the same. If they are the same, the first data is (re)transmitted. If they are different, the first device fails to access (or continues to receive Msg2), or the first device does not respond to the first message, or the first device does not send the first data.

[0707] Alternatively, for the first device, if the first device (again) receives the first message, and the first AS ID in the first message is different from the second identifier, or the first random identifier in the first message is the same as the second identifier, then the access is successful, and the first data is (re)transmitted.

[0708] Alternatively, for the first device, if the first device (again) receives the first message, and the first AS ID in the first message is different from the second identifier, and the first message includes a random identifier that is the same as the second identifier, then the access is successful, and the first data is (re)transmitted.

[0709] It should be understood that in the communication method 2700 of this application, the first device always stores an identifier, denoted as the second identifier. The second identifier can be a second AS ID or a second random identifier. The second AS ID corresponds to the second random identifier.

[0710] It should be understood that in the communication method 2700 of this application, the first device does not need to identify which identifier the second identifier it stores is. After receiving the first message, it can simply compare the second identifier with the first identifier of the first message. For details, please refer to the descriptions of Case 1 and Case 2 above, which will not be repeated here.

[0711] Next, we will use two examples (Example 1 and Example 2 below) to illustrate the communication method 2700 of this application:

[0712] Example 1

[0713] Step 1: The first device sends a third message to the second device. Correspondingly, the second device receives the third message from the first device.

[0714] The third message includes a second random identifier. This second random identifier is generated and stored by the first device. For example, the third message could be Msg1. This can be understood as an access request message.

[0715] Step 2: The second device sends a first message to the first device. Correspondingly, the first device receives the first message from the second device.

[0716] The first message includes a first identifier, which comprises a first AS ID and a first random identifier. The first message is a contention resolution message; see the description in S2701 for details, which will not be repeated here.

[0717] It should be noted that, for the first device, it stores an identifier, denoted as the second identifier. As can be seen from step 1, the second identifier stored by the first device is a random identifier, denoted as the second random identifier. Alternatively, the first message in step 2 is a retransmitted second message. For example, after step 1 and before step 2, the second device has sent the first message, but the sending failed, or the transmission failed, resulting in the first device not receiving it. In this case, the second identifier stored by the first device is still a random identifier, i.e., the aforementioned second random identifier.

[0718] Step 3: The first device sends first data to the second device. Correspondingly, the second device receives the first data from the first device.

[0719] For example, the first device first determines whether the second identifier is the same as the first AS ID. If they are different, it then determines whether the second identifier is the same as the first random identifier. Specifically, the second identifier is different from the first AS ID, and the second identifier is the same as the first random identifier. In this case, the first device sends the first data.

[0720] Example 2

[0721] Step 4: The first device sends a third message to the second device. Correspondingly, the second device receives the third message from the first device.

[0722] The third message includes a second random identifier. This second random identifier is generated and stored by the first device. For example, the third message could be Msg1. This can be understood as an access request message.

[0723] Step 5: The second device sends a second message to the first device. Correspondingly, the first device receives the second message from the second device.

[0724] The second message includes a second AS ID and a first random identifier. The second message is a contention resolution message. For example, the second message could be Msg2.

[0725] For the first device, after receiving the second message, it saves the second AS ID from the second message and deletes the second random identifier. In this case, the second identifier saved by the first device is the AS ID, i.e., the second AS ID.

[0726] Step 6: The first device sends first data to the second device, but the second device does not receive the first data. For example, the first device fails to send the first data, or the first data transmission fails, resulting in the second device not receiving the first data.

[0727] Step 7: The second device sends a first message to the first device. Correspondingly, the first device receives the first message from the second device.

[0728] The first message includes a first identifier, which comprises a first AS ID and a first random identifier. The first message is a contention resolution message; see the description in S2701 for details, which will not be repeated here.

[0729] The first message can be understood as a retransmission of the second message. The second AS ID in the second message is the same as the first AS ID in the first message.

[0730] Step 8: The first device (re)sends the first data to the second device. Accordingly, the second device receives the first data from the first device.

[0731] For example, the first device first determines whether the second identifier is the same as the first AS ID. If they are the same, there is no need to further determine whether the second identifier is the same as the first random identifier. Here, the second identifier is the same as the first AS ID. In this case, the first device (re)transmits the first data.

[0732] The communication method 2800 proposed in this application will be described in detail below with reference to Figure 28:

[0733] S2801, The first device determines that the second identifier is the second AS ID or the second random identifier.

[0734] The second identifier is stored in the first device.

[0735] It should be understood that in the communication method 2800 of this application, the first device always stores an identifier, namely a second identifier. Furthermore, the first device identifies which identifier the second identifier it stores is.

[0736] For example, the second identifier is the second AS ID. The second AS ID is assigned by the second device, as detailed in the description of S2702, and will not be repeated here.

[0737] For example, the second identifier is a second random identifier. The second random identifier is generated by the first device, as detailed in the description of S2702, and will not be repeated here.

[0738] S2802, the second device sends a first message to the first device. Correspondingly, the first device receives the first message from the second device.

[0739] The first message is the contention resolution message. For example, if the first message is Msg2, it could be either an initial transmission of Msg2 or a retransmission of Msg2.

[0740] The first message includes a first random identifier and a first AS ID. The first random identifier corresponds to the first AS ID.

[0741] It should be understood that the first device may execute S2801 first and then S2802, or it may execute S2802 first and then S2801, or it may execute S2801 and S2802 simultaneously, without limitation.

[0742] For the first device, after receiving the first message, it executes S2803:

[0743] S2803, the first device sends first data to the second device. Correspondingly, the second device receives the first data from the first device.

[0744] The first data includes the device identifier and / or upper-layer data. The first data is included in Msg3. Sending the first data can also be described as sending Msg3.

[0745] Sending the first data can be understood as either transmitting the first data initially or retransmitting the first data.

[0746] For example, S2803 includes:

[0747] Case 1: The second AS ID is the same as the first AS ID.

[0748] Regarding scenario 1, it can be understood as:

[0749] For the first device, when it determines that the second identifier is the second AS ID, it checks whether the second AS ID is the same as the first AS ID of the first message. If they are the same, the access is successful, and the first data is (re)transmitted. If they are different, the first device fails to access (or continues to receive Msg2), or the first device does not respond to the first message, or the first device does not send the first data. Unlike communication method 2700, when the second AS ID is different from the first AS ID of the first message, the first device does not need to continue to check whether the second identifier is the same as the first random identifier of the first message.

[0750] Alternatively, for the first device, when the first device determines that the second identifier is the second AS ID, it determines whether the second AS ID is the same as the first AS ID of the first message. If they are the same, the first data is (re)transmitted. If they are different, the first device fails to access (or continues to receive Msg2), or the first device does not respond to the first message, or the first device does not send the first data.

[0751] Alternatively, for the first device, when the first device determines that the second identifier is the second AS ID, if the first AS ID in the first message is the same as the second AS ID, or if the first message includes an AS ID that is the same as the second AS ID, then the access is successful and the first data is (re)transmitted.

[0752] Case 2: The second random identifier is the same as the first random identifier.

[0753] Regarding scenario 1, it can be understood as:

[0754] For the first device, when the first device determines that the second identifier is the second random identifier, it determines whether the second random identifier is the same as the first random identifier of the first message. If they are the same, the first device sends the first data. If they are different, the first device fails to access (or continues to receive Msg2), or the first device does not respond to the first message, or the first device does not send the first data.

[0755] Alternatively, for the first device, when the first device determines that the second identifier is the second random identifier, it determines whether the second random identifier is the same as the first random identifier of the first message. If they are the same, the first data is (re)transmitted. If they are different, the first device fails to access (or continues to receive Msg2), or the first device does not respond to the first message, or the first device does not send the first data.

[0756] Alternatively, for the first device, when the first device determines that the second identifier is the second random identifier, if the first random identifier in the first message is the same as the second random identifier, or if the first message includes a random identifier that is the same as the second random identifier, then the access is successful and the first data is (re)transmitted.

[0757] It should be understood that the first message includes at least one AS ID and at least one random identifier. As an example, in the first message, an AS ID is adjacent to a random identifier, which can be understood as the two appearing in pairs, as shown in Figure 29. In the communication methods 2700 and 2800 described above, the first AS ID corresponds to the first random identifier, as shown in bold.

[0758] Furthermore, in the first message, when an AS ID is adjacent to a random identifier, the AS ID is located before or after the random identifier. Optionally, indication information may also be included between the AS ID and the random identifier, which is used to determine whether to include / assign an AS ID. For example, the indication information may indicate whether to include / assign an AS ID.

[0759] Taking the random identifier preceding the AS ID as an example, in some embodiments, indication information is used to determine whether to include / assign the AS ID. For example, when the indication information is 0, it indicates that the AS ID is not included / assigned; conversely, when the indication information is 1, it indicates that the AS ID is included / assigned.

[0760] As a possible alternative description, the indication information used to determine (not) include the AS ID can be replaced by the description: The indication information indicates that the first message (does not) include the AS ID.

[0761] It should be understood that in the communication methods 2700 and 2800 of this application, the first AS ID can be understood as the AS ID assigned by the second device, or the AS ID assigned by the second device to the first device.

[0762] It should be understood that the first message includes at least one AS ID and at least one random identifier. As another example, in the first message, the AS IDs are placed together, and the random identifiers are placed together, as shown in Figure 30. In the communication methods 2700 and 2800 described above, the first AS ID is included in M ​​AS IDs, and the first random identifier is included in N random identifiers. The first AS ID corresponds to the first random identifier, as shown in bold. M and N are positive integers.

[0763] In this case, for the first device, when comparing AS IDs, the AS IDs in the first message are traversed; when comparing random identifiers, the random identifiers in the first message are traversed.

[0764] Taking communication method 2700 as an example, the first device performs the following operations:

[0765] The first device receives a first message. For example, the first device receives a first message from the second device. The first message includes a first identifier and is a contention resolution message.

[0766] The first device sends first data. For example, the first device sends first data to the second device.

[0767] The first identifier includes at least one AS ID, and one AS ID of the at least one AS ID is the same as the second identifier, which is stored in the first device.

[0768] Alternatively, the first identifier includes at least one AS ID and at least one random identifier. If each AS ID of the at least one AS ID (which can be understood as traversing the AS IDs of the first message) is different from the second identifier, then one random identifier of the at least one random identifier is the same as the second identifier.

[0769] It should be understood that if each AS ID of the at least one AS ID (which can be understood as the AS ID of the first message) is different from the second identifier, and each random identifier of the at least one random identifier (which can be understood as the random identifier of the first message) is different from the second identifier, the first device determines that the access has failed (or continues to receive Msg2), or does not respond to the first message, or does not send the first data.

[0770] Taking communication method 2800 as an example, the first device performs the following operations:

[0771] Regarding AS ID:

[0772] The first device determines the second identifier as the second AS ID, and the second identifier is stored in the first device.

[0773] The first device receives a first message. For example, the first device receives a first message from the second device. The first message includes a first identifier and is a contention resolution message.

[0774] The first device sends the first data.

[0775] The first identifier includes at least one AS ID, and the second AS ID is the same as one of the at least one AS IDs.

[0776] It should be understood that when each AS ID of the at least one AS ID (which can be understood as the AS ID of the first message) is different from the second identifier, the first device determines that the access has failed (or continues to receive Msg2), or does not respond to the first message, or does not send the first data.

[0777] Alternatively, for random identifiers:

[0778] The first device determines the second identifier as the second random identifier, and the second identifier is stored in the first device.

[0779] The first device receives a first message. For example, the first device receives a first message from the second device. The first message includes a first identifier and is a contention resolution message.

[0780] The first device sends the first data.

[0781] The first identifier includes at least one random identifier, and the second random identifier is the same as one of the random identifiers of the at least one random identifier.

[0782] It should be understood that when each random identifier of the at least one random identifier (which can be understood as the random identifier of the first message) is different from the second random identifier, the first device determines that the access has failed (or continues to receive Msg2), or does not respond to the first message, or does not send the first data.

[0783] It should be understood that when the first message includes at least one AS ID and at least one random identifier, there is a correspondence between the at least one AS ID and the at least one random identifier. Taking N random identifiers and M AS IDs as an example, the correspondence between the N random identifiers and the M AS IDs can be understood as follows:

[0784] When M=N, there is a one-to-one correspondence between the N random identifiers and the M AS IDs.

[0785] When M < N, among the N random identifiers, M random identifiers correspond one-to-one with M AS IDs, and (NM) random identifiers do not correspond to any of the M AS IDs.

[0786] Here, a random identifier corresponds to an AS ID, which can be understood as: the random identifier and the AS ID correspond to the same device (such as an A-IoT device). For example, the random identifier is generated and sent by the device, and the AS ID is the AS ID assigned to the device. "Assigned" can be understood as being reassigned.

[0787] In related technologies, the AS ID can be indicated to the device that successfully resolves the access / contention issue (such as an A-IoT device or a chip within an A-IoT device) via Msg2. When the same Msg2 corresponds to multiple devices, some of these devices may be assigned an AS ID. Accordingly, Msg2 includes at least one random identifier and at least one AS ID. The number of random identifiers and AS IDs may be the same or different. Even if the number of random identifiers and AS IDs is the same, the order of the random identifiers may differ from the order of the AS IDs. For the receiving device, it cannot know whether its own AS ID is carried in Msg2, affecting AS ID resolution.

[0788] For example, taking A-IoT devices as an example, each of the seven A-IoT devices (e.g., A-IoT devices 1 / 2 / 3 / 4 / 5 / 6 / 7) generates a random identifier and sends Msg1 to the same reader. Each Msg1 includes a random identifier. Specifically, A-IoT device 1 sends Msg1 on AO1 containing random identifier 'a', A-IoT device 2 sends Msg1 on AO2 containing random identifier 'b', and so on for the other A-IoT devices. In this application, AO1 refers to AO numbered 1. AO2 refers to AO numbered 2. Other AOs follow the same pattern. Among the seven A-IoT devices (e.g., A-IoT devices 1 / 2 / 3 / 4 / 5 / 6 / 7), four A-IoT devices (e.g., A-IoT devices 1 / 3 / 5 / 7) successfully resolve the random access contention, while three A-IoT devices (e.g., A-IoT devices 2 / 4 / 6) fail to resolve the random access contention. Of the four A-IoT devices that successfully resolved the random access contention (e.g., A-IoT devices 1 / 3 / 5 / 7), three A-IoT devices (e.g., A-IoT devices 1 / 3 / 5) were assigned an AS ID, while one A-IoT device (e.g., A-IoT device 7) was not assigned an AS ID. Accordingly, Msg2 includes four random identifiers (e.g., random identifiers a / c / e / g) to indicate that the corresponding A-IoT device successfully resolved the random access contention, and Msg2 also includes three AS IDs (e.g., AS ID a / c / e) to indicate that the corresponding A-IoT device was assigned an AS ID, as shown in Figure 31.

[0789] However, on the A-IoT device side, after receiving Msg2, the A-IoT device cannot know whether its own AS ID is included among the above three AS IDs, that is, the A-IoT device cannot correctly parse the AS ID.

[0790] In view of this, this application provides two communication methods (communication method 3200 and communication method 3400 hereinafter). The communication methods provided in this application can be applied to the systems shown in Figures 1-7.

[0791] The communication method 3200 proposed in this application will be described in detail below with reference to Figure 32:

[0792] S3201, The second device determines the first identifier and the first information.

[0793] The first information indicates the number M of AS IDs in the first identifier, where M is a positive integer.

[0794] Optionally, the first information occupies X bits (in other words, the length of the first information is X bits). X is a positive integer. For example, X can take one of the following values: 3 or 4.

[0795] If the first information occupies 3 bits, then M is a positive integer less than or equal to 8. This can be understood as the first information, through 3 bits, indicating a maximum of 8 AS IDs (that have been reallocated).

[0796] If the first information occupies 4 bits, then M is a positive integer less than or equal to 16. This can be understood as the first information, through 4 bits, indicating a maximum of 16 AS IDs (that have been reallocated).

[0797] The first identifier comprises N random identifiers and M AS IDs, where M and N are positive integers. Furthermore, there is a one-to-one correspondence between the first M random identifiers and the M AS IDs. The last (NM) random identifiers do not correspond to any of the M AS IDs.

[0798] Taking Figure 33 as an example, N=4, M=3. Among the four random identifiers, the first three correspond one-to-one with the three AS IDs. That is: random identifier a corresponds to AS ID a, random identifier c corresponds to AS ID c, and random identifier e corresponds to AS ID e. The last random identifier does not correspond to any of the three AS IDs. That is: random identifier g does not correspond to AS IDs a / c / e.

[0799] It should be understood that each of the N random identifiers corresponds to one device (such as an A-IoT device, or a chip within an A-IoT device), and the random access contention for that device is successfully resolved. Each of the M AS IDs corresponds to one device (such as an A-IoT device, or a chip within an A-IoT device), and the random access contention for that device is successfully resolved and an AS ID is assigned to it. Optionally, N is greater than or equal to M.

[0800] Based on the above examples, as shown in Figure 33, the N random identifiers include 4 random identifiers (such as random identifiers a / c / e / g) to indicate that the random access contention of the corresponding A-IoT device has been successfully resolved, and the M AS IDs include 3 AS IDs (such as AS ID a / c / e) to indicate that the corresponding A-IoT device has been assigned an AS ID.

[0801] Optionally, the N random identifiers include a first random identifier, which corresponds to the first device. For example, the first random identifier is the random identifier of the first device. Taking Figure 33 as an example, the first random identifier is random identifier a.

[0802] Optionally, the M AS IDs include the first AS ID. Taking Figure 33 as an example, the first AS ID is AS ID a.

[0803] Optionally, when the first identifier and the first information are included in the same message, this message is denoted as the first message. The first message also includes a padding portion to achieve byte alignment, as shown in Figure 33. For example, the length of the first information is 3 bits, and correspondingly, the padding portion is 5 bits to achieve byte alignment. It should be noted that in this application, each byte includes 8 bits. Exemplarily, the first message can be Msg2, a feedback message, or downlink data, such as R2D data.

[0804] Optionally, as a possible example, the first identifier is included in the MAC CE of Msg2, as shown in Figure 33. This can be understood as the first identifier not being in the MAC(sub) header. The first information is included in the MAC(sub) header of Msg2, as shown in Figure 33. Here, Msg2 includes one MAC CE and one MAC(sub) header. Alternatively, Msg2 may include only one MAC CE and one MAC(sub) header.

[0805] For the second device, after determining the first identifier, the second device sends the first identifier; and after determining the first information, the second device sends the first information. The second device may send the first identifier first, then send the first information, or send both the first identifier and the first information simultaneously, or send the first information first, then send the first identifier; there is no limitation on this. For example, after executing S3201, the second device executes S3202:

[0806] S3202, the second device sends a first identifier and first information. Correspondingly, the first device receives the first identifier and first information from the second device.

[0807] The first identifier and the first information can be found in the description of S3201, and will not be repeated here.

[0808] Optionally, the first identifier and the first information can be included in the same message.

[0809] For example, the first identifier and the first information are included in Msg2, which can be found in the description of S3201, and will not be repeated here.

[0810] For example, the first identifier and the first information are included in the feedback message.

[0811] For example, the first identifier and the first information are included in the downlink data.

[0812] Optionally, the first identifier and the first information may be included in different messages, such as the first identifier being included in Msg2 and the first information being included in other messages besides Msg2.

[0813] For the first device, after receiving the first identifier and the first information, it executes S3203:

[0814] S3203. The first device determines the AS ID of the first device based on the first identifier and the first information.

[0815] The AS ID of the first device is either the first AS ID or the first random identifier.

[0816] For example, when the AS ID of the first device is assigned, the AS ID of the first device is included in M ​​AS IDs, such as the AS ID of the first device being the first AS ID. The first device determines the AS ID of the first device as the first AS ID based on the first random identifier in the first identifier and the correspondence between the first random identifier and the first AS ID, thereby achieving correct resolution of the AS ID.

[0817] For example, when the AS ID of the first device reuses the first random identifier, the AS ID of the first device is the first random identifier. The correspondence indicated by the first information includes: the first random identifier does not correspond to any one of the M AS IDs. Based on the first random identifier in the first identifier and the first information, the first device determines that the AS ID of the first device is the first random identifier, thereby achieving correct AS ID resolution.

[0818] Based on the above technical solution, the first device can correctly parse the AS ID of the first device according to the first information and the first identifier, as detailed in the preceding paragraph. Furthermore, the first information indicates the number of AS IDs in the first identifier, and there is a correspondence between the first M random identifiers and the M AS IDs among the N random identifiers, thus constraining the position of the random identifiers in the first identifier and saving signaling overhead. For example, compared to the bitmap method (i.e., a bitmap includes N bits; if the Nth bit... i When the first bit is the first value, it indicates the Nth random identifier among N random identifiers. i Each random identifier corresponds to one of the M AS IDs; if the Nth bit in the N bits... i When the last bit is the second value, it indicates the Nth random identifier among the N random identifiers. i Each random identifier does not correspond to any one of the M AS IDs; N i (where N is a positive integer less than or equal to N), the first information and the first identifier of this application can save signaling overhead.

[0819] For example, when N=8, the bitmap method has a length of 8 bits. However, when the first information indicates the number of AS IDs in the first identifier, the first information occupies 3 bits, thus saving 5 bits of signaling overhead.

[0820] For example, taking N=16 as an example, when using the bitmap method, the bitmap length is 16 bits. And using the first information to indicate the...

[0821] The communication method 3400 proposed in this application will be described in detail below with reference to Figure 34:

[0822] S3401, The second device determines the first identifier and the first figure.

[0823] The first identifier comprises N random identifiers and M AS IDs, with each of the N random identifiers corresponding one-to-one with one of the N frequency domain resources. These N frequency domain resources are included within the K frequency domain resources. Each of the N random identifiers corresponds to a specific time domain resource.

[0824] It should be noted that the N random identifiers correspond one-to-one with the N frequency domain resources. This can be understood as follows: for each of the N random identifiers, the random identifier is transmitted through the frequency domain resources corresponding to that random identifier.

[0825] It should be noted that N frequency domain resources are included in K frequency domain resources. K frequency domain resources refer to frequency domain resources that are randomly accessed (or transmitted) on the same time domain resource.

[0826] Within the same time domain resource, the number of random access ( / transmission) frequency domain resources is fixed (or deterministic, for example, indicated / configured via paging messages). For example, a maximum of 4, or a maximum of 8. That is, K can take one of the following values: 4, or 8.

[0827] It should be understood that in the communication method 3400 of this application, random access resources may be described in other ways, such as random access opportunities or frequency domain resources used to transmit random identifiers.

[0828] The first bit consists of K bits. If the Kth bit... i When the first bit is the first value, it indicates the Kth bit in the K frequency domain resources. i Each frequency domain resource corresponds to one of M AS IDs. If the Kth bit... i When the first bit is the second value, it indicates the Kth bit in the K frequency domain resources. i Each frequency domain resource does not correspond to any one of the M AS IDs; K is a positive integer, K i It is a positive integer less than or equal to K.

[0829] It should be noted that in the communication method 3400 of this application, the length of the first bit diagram is fixed. Next, two implementation methods (implementation method 1 and implementation method 2 below) will be introduced:

[0830] In implementation 1, the length (or number of bits) of the first bitmap may be: the number allocated for transmitting the random identifier (or access resources / opportunities), or related to the number allocated for transmitting the random identifier (or access resources / opportunities).

[0831] For example, the number of allocated random access time-domain resources is 2, and the number of allocated random access frequency-domain resources is 8. Wherein, the number 2 of random access time-domain resources and the number 8 of random access frequency-domain resources may be indicated by a paging message. In this case, when the first message (e.g., Msg2) responds to the third message (e.g., Msg1) sent through the first time-domain resource or the second time-domain resource, the length of the first bitmap may be 8 bits.

[0832] For another example, the number of allocated random access time-domain resources is 2, and the number of allocated random access frequency-domain resources is 4. Wherein, the number 2 of random access time-domain resources and the number 4 of random access frequency-domain resources may be indicated by a paging message. In this case, when the first message (e.g., Msg2) responds to the third message (e.g., Msg1) sent through the first time-domain resource or the second time-domain resource, the length of the first bitmap may be 4 bits.

[0833] In implementation 2, the length (or number of bits) of the first bitmap may be: the maximum number of random access frequency-domain resources. Wherein, the number of (actual) effective bits of the first bitmap may be: the number of currently allocated random access frequency-domain resources.

[0834] That is, in implementation 2, the maximum number of random access ( / transmission) frequency-domain resources is K (the protocol stipulates that the maximum does not exceed K), and the number of bits of the first bitmap is fixed at K bits. Optionally, when the number of allocated random access frequency-domain resources is L and L<K, the effective bits of the first bitmap are the first L bits of the first bitmap, and optionally, the last (K-L) bits of the first bitmap may be padded with "0" by default.

[0835] For example, the maximum number of random access ( / transmission) frequency-domain resources is 4 (the protocol stipulates that the maximum does not exceed 4), and the number of bits of the first bitmap is fixed at 4 bits.

[0836] For another example, the maximum number of random access ( / transmission) frequency-domain resources is 8 (the protocol stipulates that the maximum does not exceed 8), and the number of bits of the first bitmap is fixed at 8 bits. Further, when the number of allocated random access frequency-domain resources is 4, the effective bits of the first bitmap are the first 4 bits. Optionally, the last 4 bits may be padded with '0' by default.

[0837] With reference to the above examples, as shown in Figure 35, the first bitmap includes 7 bits, and the 7 bits are in one-to-one correspondence with 7 frequency-domain resources (e.g., resource 1 / 2 / 3 / 4 / 5 / 6 / 7). The first bitmap is introduced as follows:

[0838] The first bit corresponds to the first frequency domain resource (e.g., frequency domain resource 1) among the seven frequency domain resources (e.g., frequency domain resources 1 / 2 / 3 / 4 / 5 / 6 / 7). The random identifier transmitted on this frequency domain resource includes random identifier 'a'. When the value of the first bit is 1, it indicates that the frequency domain resource (e.g., frequency domain resource 1) corresponds to an AS ID, such as the first AS ID among three AS IDs (e.g., AS ID a).

[0839] The second bit corresponds to the second frequency domain resource (e.g., frequency domain resource 2) among the seven frequency domain resources (e.g., frequency domain resources 1 / 2 / 3 / 4 / 5 / 6 / 7). The random identifier transmitted on this frequency domain resource includes random identifier b. When the value of the second bit is 0, it indicates that the frequency domain resource (e.g., frequency domain resource 2) does not correspond to any of the three AS IDs.

[0840] The third bit corresponds to the third frequency domain resource (e.g., frequency domain resource 3) out of the seven frequency domain resources (e.g., frequency domain resources 1 / 2 / 3 / 4 / 5 / 6 / 7). The random identifier transmitted on this frequency domain resource includes random identifier c. When the value of the third bit is 1, it indicates that the frequency domain resource (e.g., frequency domain resource 3) corresponds to an AS ID, such as the second AS ID out of three AS IDs (e.g., AS ID c).

[0841] The same applies to the other bits.

[0842] It should be understood that in the communication method 3500 of this application, different bitmaps are associated with different time-domain resources. For example, N random identifiers correspond to the same time-domain resource, such as the first time-domain resource, which is associated with the first bitmap. The association of the first time-domain resource with the first bitmap can be understood as the first bitmap indicating whether each frequency-domain resource on the first time-domain resource corresponds to an AS ID, as detailed in the preceding paragraphs, and will not be repeated here.

[0843] It should be understood that each of the N random identifiers corresponds to one device (such as an A-IoT device, or a chip within an A-IoT device), and the random access contention for that device is successfully resolved. Each of the M AS IDs corresponds to one device (such as an A-IoT device, or a chip within an A-IoT device), and the random access contention for that device is successfully resolved and an AS ID is assigned to it. Optionally, N is greater than or equal to M.

[0844] Based on the above examples, as shown in Figure 35, the N random identifiers include 4 random identifiers (such as random identifiers a / c / e / g) to indicate that the random access contention of the corresponding A-IoT device has been successfully resolved, and the M AS IDs include 3 AS IDs (such as AS ID a / c / e) to indicate that the corresponding A-IoT device has been assigned an AS ID.

[0845] Optionally, the N random identifiers include a first random identifier, which corresponds to the first device. For example, the first random identifier is the random identifier of the first device. Taking Figure 35 as an example, the first random identifier is random identifier a.

[0846] Optionally, the N frequency domain resources include a first frequency domain resource, which corresponds to a first random identifier. For example, the first random identifier is transmitted through the first frequency domain resource.

[0847] Optionally, the M AS IDs include the first AS ID. Taking Figure 35 as an example, the first AS ID is AS ID a.

[0848] Optionally, when the first identifier and the first bit image are included in the same message, this message is denoted as the first message. The first message also includes a padding portion to achieve byte alignment, as shown in Figure 35. For example, if the length of the first bit image is 4 bits, the corresponding padding portion is 4 bits to achieve byte alignment. It should be noted that in this application, each byte includes 8 bits. Exemplarily, the first message can be Msg2, a feedback message, or downlink data, such as R2D data.

[0849] Optionally, as a possible example, the first identifier is included in the MAC CE of Msg2, as shown in Figure 35. This can be understood as the first identifier not being in the MAC(sub) header. The first identifier is included in the MAC(sub) header of Msg2, as shown in Figure 35. Here, Msg2 includes one MAC CE and one MAC(sub) header. Alternatively, Msg2 may include only one MAC CE and one MAC(sub) header.

[0850] For the second device, after determining the first identifier, the second device sends the first identifier, and after determining the first image, the second device sends the first image. The second device may send the first identifier first and then send the first image, or send the first identifier and the first image simultaneously, or send the first image first and then send the first identifier; there is no limitation on this. For example, after executing S3401, the second device executes S3402:

[0851] S3402, the second device sends a first identifier and a first bit pattern. Correspondingly, the first device receives the first identifier and the first bit pattern from the second device.

[0852] The first identifier and the first figure can be found in the description of S3401, and will not be repeated here.

[0853] Optionally, the first identifier and the first image can be included in the same message.

[0854] For example, the first identifier and the first figure are included in Msg2, which can be found in the description of S3401, and will not be repeated here.

[0855] For example, the first identifier and the first image are included in the feedback message.

[0856] For example, the first identifier and the first image are included in the downlink data.

[0857] Optionally, the first identifier and the first image can be included in different messages, such as the first identifier being included in Msg2 and the first image being included in other messages besides Msg2.

[0858] For the first device, after receiving the first identifier and the first bit diagram, it executes S3403:

[0859] S3403. The first device determines the AS ID of the first device based on the first identifier and the first bit diagram.

[0860] The AS ID of the first device is either the first AS ID or the first random identifier.

[0861] For example, when the AS ID of the first device is assigned, the AS ID of the first device is included in M ​​AS IDs, such as the AS ID of the first device being the first AS ID. The first device determines the AS ID of the first device as the first AS ID based on the first random identifier in the first identifier, the correspondence between the first random identifier and the first frequency domain resource, and the correspondence between the first frequency domain resource indicated by the first bit diagram and the first AS ID, thereby achieving correct resolution of the AS ID.

[0862] For example, when the AS ID of the first device reuses the first random identifier, the AS ID of the first device is the first random identifier. The first random identifier corresponds to the first frequency domain resource, and the correspondence indicated by the first bit diagram includes: the first frequency domain resource does not correspond to any one of the M AS IDs. Based on the first random identifier in the first identifier and the first bit diagram, the first device determines that the AS ID of the first device is the first random identifier, thereby achieving correct AS ID resolution.

[0863] Based on the above technical solution, it can be seen that the first device can correctly parse the AS ID of the first device according to the first bit diagram and the first identifier, as detailed in the preceding paragraph. In addition, the length of the first bit diagram is consistent with or related to the number of random access frequency domain resources on the same time domain resource, and the number of random access frequency domain resources on the same time domain resource is fixed (or determined, such as indicated / configured by paging messages), so there is no need to additionally indicate the length of the first bit diagram, thereby saving signaling overhead.

[0864] In related technologies, the network side configures at least one resource (such as at least one time-domain resource) through paging messages, and then sends a random access trigger message. The random access trigger message is used to trigger a portion of the at least one resource to transmit Msg1 or data. However, the random access trigger message consumes certain resources and has significant signaling overhead.

[0865] In view of this, this application provides a communication method 3600. The communication method provided by this application can be applied to the systems shown in Figures 1-7.

[0866] The communication method 3600 proposed in this application will be described in detail below with reference to Figure 36:

[0867] S3601, The first device determines the access type.

[0868] The access types include: contention-based random access and contention-free random access. For contention-based random access, please refer to the CBRA (Content-Based Access Restriction and Access Control Restriction) documentation; for contention-free random access, please refer to the CFRA (Content-Free Access Restriction and Access Control Restriction) documentation. Further details will not be provided here.

[0869] S3602. The first device determines whether to receive the fourth message based on the access type.

[0870] The fourth message is a random access trigger message. For example, the fourth message is QueryRep, or RA trigger.

[0871] When the access type is contention-based random access, the first device determines that it has received a fourth message and sends a third message through a first resource (such as a first time resource). The first resource (such as a first time resource) is included in at least two resources (such as at least two time resources) configured in the paging message and is determined according to the fourth message. For example, the third message is Msg1. This can be understood as an access request message.

[0872] For example, a first device receives a paging message from a second device. The paging message indicates at least two resources (e.g., at least two time resources). Then, the first device receives a fourth message from the second device, and based on the fourth message, determines a first resource (e.g., a first time resource) from the at least two resources (e.g., at least two time resources), and sends a third message through the first resource (e.g., the first time resource).

[0873] In contention-based random access scenarios, the paging message indicates at least two resources (e.g., at least two time resources), so the first device cannot determine on which resource to send the third message. In this case, the first device determines the first resource by receiving the fourth message. Since the first resource (e.g., the first time resource) is calibrated by the fourth message, sending the third message through the first resource (e.g., the first time resource) has high accuracy.

[0874] Alternatively, when the access type is contention-free random access, the first device cancels receiving (or does not receive, or does not need to receive) the fourth message, and sends the first data through the first resource (such as the first time resource), which is configured by the paging message.

[0875] For example, the first device receives a paging message from the second device. The paging message indicates a first resource (such as a first time resource). Then, the first device cancels receiving a fourth message to save signaling overhead and sends first data through the first resource (such as the first time resource) configured in the paging message.

[0876] In a contention-free random access scenario, the paging message indicates a resource (such as the first resource), so the first device can determine on which resource to send the first data. In this case, the second device does not need to receive a fourth message, thus saving signaling overhead.

[0877] Similarly, for the second device, the second device performs the following operations;

[0878] S3603, The second device determines the access type.

[0879] The access types include contention-based random access and contention-free random access, which can be found in the description of S3601 and will not be repeated here.

[0880] S3604. The second device determines whether to send a fourth message based on the access type.

[0881] The fourth message is a random access trigger message. For example, the fourth message is QueryRep, or RA trigger.

[0882] When the access type is contention-based random access, the second device determines to send a fourth message and receives a third message through a first resource (such as a first time resource). The first resource (such as a first time resource) is included in at least two resources (such as at least two time resources) configured in the paging message and is determined according to the fourth message. For example, the third message is Msg1, which can be found in the description of S3602 and will not be repeated here.

[0883] Alternatively, when the access type is contention-free random access, the second device cancels (or does not send, or does not need to send) the fourth message, and receives the first data through the first resource (such as the first time resource). The first resource (such as the first time resource) is configured by the paging message, which can be referred to in the description of S3602, and will not be repeated here.

[0884] In addition, one possible implementation method is extended:

[0885] Step 1: The second device sends a paging message to the first device. Correspondingly, the first device receives the paging message from the second device.

[0886] The paging message indicates at least one resource (such as at least one time resource), and the paging message triggers a first resource (such as a first time resource). The first resource is the first of the at least one resources (the at least one resource indicated by the paging message). This can be understood as the earliest of the at least one resources.

[0887] Taking the above resource as an AO as an example, it can be understood as follows: the paging message indicates at least one AO, and the paging message triggers the first AO, which is the first AO among the at least one AO. Here, AO can also be replaced with a set of AOs.

[0888] Step 2: The first device sends first data or a third message to the second device through the first resource. Correspondingly, the second device receives the first data or the third message from the second device through the first resource.

[0889] The first data includes the device identifier and / or upper-layer data. The first data is included in Msg3. Sending the first data can also be described as sending Msg3.

[0890] The third message includes a random identifier. For example, the third message is Msg1.

[0891] Taking CBRA as an example, the first device sends a third message to the second device through the first resource, without needing to receive a fifth message, thus saving transmission overhead and waiting latency. The fifth message is a random access trigger message, such as QueryRep or RA trigger. The fifth message is transmitted after the paging message and before the first resource. The fifth message is used to trigger the first resource. Based on the above technical solution, it can be seen that the paging message also serves as a trigger message to trigger the first resource, eliminating the need for the fifth message to trigger the first resource, thereby saving transmission overhead and waiting latency. Correspondingly, the second device receives the third message from the first device through the first resource.

[0892] Taking CFRA as an example, the first device sends first data to the second device through the first resource, without needing to receive a fifth message, thus saving transmission overhead and waiting latency. Correspondingly, the second device receives the first data from the first device through the first resource.

[0893] In other words, the first resource is the first resource indicated by the paging message. Besides indicating at least one resource, the paging message also acts as a trigger message to activate the first resource, thereby enabling the first device to transmit first data or a third message on the first resource. Compared to related technologies where the first resource is triggered by a fifth message (e.g., QueryRep; or RA trigger), this application triggers the first resource via a paging message, which saves message transmission overhead and reduces the waiting latency of the first device.

[0894] Optionally, the paging message may also indicate that a fifth message is not required / not needed. This fifth message is a random access trigger message, such as a QueryRep or RA trigger, as described in the preceding paragraphs and will not be repeated here.

[0895] It should be added that, in this application, such as in communication methods 2700 / 2800 / 3200 / 3400 / 3600, the first and second devices are described as follows:

[0896] The first device can be a network device, such as a reader, or a terminal device, such as an A-IoT device, or a chip within the aforementioned devices (such as network devices or terminal devices). The network device and terminal device are illustrated in Figures 1-7 and will not be described further. In the communication methods 2700 / 2800 / 3200 / 3400 / 3600 of this application, an A-IoT device as the first device is used as an example for description.

[0897] The second device can be a network device, such as a reader, or a terminal device, such as an A-IoT device, or a chip within the aforementioned devices (such as network devices or terminal devices). The network device and terminal device are illustrated in Figures 1-7 and will not be described further. In the communication methods 2700 / 2800 / 3200 / 3400 / 3600 of this application, a reader is used as an example for description.

[0898] It should be added that, in this application, such as in communication methods 2700 / 2800 / 3200 / 3400 / 3600, the first data is described as follows:

[0899] On one hand, the first data includes the device identifier and / or upper-layer data. The first data is included in Msg3. Sending the first data can also be described as sending Msg3.

[0900] On the other hand, sending the first data can be understood as either transmitting the first data initially or retransmitting the first data.

[0901] It should be added that in this application, such as in communication methods 2700 / 2800 / 3200 / 3400 / 3600, the AS ID is assigned, which can be understood as the AS ID being reassigned.

[0902] It is understood that the names mentioned in this application may also be described in other ways, such as:

[0903] First, R2D data (or R2D information, or R2D messages) or D2R data (or D2R information, or D2R messages) can be carried on the MAC layer, such as MAC CE, MAC SDU (service data unit), or MAC PDU (protocol data unit). The MAC layer can also be replaced by the A-IoT AS layer.

[0904] Second, in this application, the terms signaling / information / message / information element / field are generally not distinguished, and the names can be used interchangeably.

[0905] Third, paging messages:

[0906] Paging can be used to instruct A-IoT devices to connect to the reader, for example:

[0907] When the reader is a base station / access network device, Paging can be used to indicate that the device is connected to the network;

[0908] When the reader is a terminal device, Paging can be used to instruct the device to connect to the terminal device. Optionally, the device can connect to the network through the terminal device.

[0909] Paging can also be used to trigger / instruct a device to send uplink data, or to trigger / instruct / request a device to perform a first service. The first service can include at least one of the following: paging service, inventory service, command service (such as read, write, deactivate, lock, etc.), location service, and sensing service.

[0910] Paging, also known as the (initial) DL trigger message or indication, can be triggered by core network elements (such as AMF elements, AIoTMF elements, AIoTF elements, etc.).

[0911] Optionally, paging may include data related to the primary business, such as commands (the contents of read, write, etc.).

[0912] Optionally, in some implementations, paging and access round indication, or paging and random access trigger (RA trigger) are sent together.

[0913] Fourth, Access round indication:

[0914] Access round indication, also known as access resource / occasion configuration or access round trigger / query, is used to trigger / indicate at least one access opportunity (or a set of access opportunities), or to trigger / indicate the next round of access (e.g., for re-access). Optionally, access round indication can directly or indirectly indicate the total number of access opportunities (or access time-domain and / or frequency-domain resources) in the (next round), or it can be used to trigger the first access opportunity (or set). Optionally, paging can be used for access round indication, such as triggering the next round of access.

[0915] Optionally, paging can carry downlink data.

[0916] Optionally, an access process triggered by paging may include one or more rounds of access.

[0917] One implementation method is to achieve access round indication through paging retransmission or paging carrying different content. Optionally, paging triggers / indicates the next round of access.

[0918] Fifth, RA trigger

[0919] RA trigger, which may also have other names such as (next) access occasion indication / trigger / QueryRep, is used to trigger / indicate the next (or more, or the next group of) access occasions (or a set of access occasions). It can also be understood as indicating / associating with the boundary (start or end) of an access occasion.

[0920] The aforementioned access opportunities can also be described as access resources, access opportunities, access time slots, access time domain resources, access time resources, random access opportunities, etc. Each access opportunity can allow a device to send an access (request), and / or contention resolution, and / or data transmission, etc.

[0921] Sixth, Msg1

[0922] Msg1, with no specific name, may include (or be replaced with) a random identifier (random ID), a random access identifier (random access ID), a random number, etc. In one implementation, Msg1 may include at least one of the following: a random identifier, uplink data (such as a device ID, a response to a command). Msg1 is used for contention during random access, or to distinguish different terminal devices during random access / contention resolution. Optionally, the random identifier may be 16 bits or 8 bits, without limitation.

[0923] Seventh, Msg2

[0924] Msg2, with no specific name, may also be called an Access ID response, a Random ID Response message, an access response, a random access response, a UE / device Contention Resolution Identity, or a contention resolution message. Msg2 is used for contention resolution, specifically indicating which Msg1 (or devices) have successfully contentioned (resolved) / sent successfully / accessed successfully. In this application, the contention resolution message is used as an example for description and should not be construed as limiting this application.

[0925] Optionally, Msg2 includes at least one of random ID and AS ID.

[0926] Optionally, Msg2 carries a random ID or identification information derived from the random ID. This can be understood as a contention resolution identification information. For example, if random ID#1 is successfully accessed / the contention is resolved, Msg2 can carry random ID#1.

[0927] Optionally, Msg2 may carry one or more random IDs, indicating one or more Msg1 contention resolutions.

[0928] Optionally, Msg2 may carry access resource (or opportunity) related identifiers (such as the index of access time domain and / or frequency domain resources) to indicate which access opportunity (or access resource) the device that sent Msg1, or through a bitmap indication, such as 000100 indicating which devices / Msg1 / random IDs were successfully accessed on the 4th access opportunity (resource) indicated by Msg2.

[0929] Optionally, Msg2 may carry an AS ID, which indicates the AS ID assigned to the device that successfully resolves access / contention.

[0930] If Msg2 carries the random ID (or a value derived from the random ID, such as through a hash function) sent by the device in Msg1, it indicates that the device has successfully resolved contention / accessed the network. Optionally, in addition to the above conditions, Msg2 must also be associated with the access opportunity / resource that the device sent Msg1 to; that is, if Msg2 indicates the identifier of the access opportunity / resource that the device is accessing and carries a matching random ID, then it is successful.

[0931] If Msg2 does not carry the random ID (or a value derived from the random ID, such as through a hash function) sent by the device in Msg1, it indicates that the device has failed to resolve contention / access. Optionally, in addition to the above conditions, Msg2 must also be associated with the access opportunity / resource that the device sent Msg1 to; that is, if Msg2 indicates the identifier of the access opportunity / resource that the device is trying to access but does not carry a matching random ID, it fails.

[0932] If the access is successful, continue the process (e.g., send Msg3); if the access fails, a re-access can be performed.

[0933] In this application, Access Round Indication, RA Trigger, and Msg2 can be carried by access layer information (such as MAC CE and MAC cells). Paging and Msg1 can include access layer information (such as MAC CE and MAC cells) or data from upper access layers. For example, in addition to control information and resource configuration information in MAC cells, paging can also include information from upper access layers (such as identification information, device ID, and group ID). In this application, uplink data and downlink data refer to data above the access layer.

[0934] Eighth, Msg3

[0935] Msg3, whose name is not limited and can also be called D2R data, can include at least one of the following: random identifier, device ID, and upper-layer data.

[0936] Ninth, Downlink Data

[0937] Downlink data: also known as R2D data.

[0938] Optionally, downlink data can come from the core network, such as from AIoTF network elements / AMF network elements / AF network elements, etc.

[0939] For example, downlink data may include commands such as at least one of read, write, sensing, locking, deactivation, and location.

[0940] Tenth, Uplink Data

[0941] Uplink data: also known as D2R data.

[0942] Optionally, uplink data can be sent to the core network, such as AIoTF network elements / AMF network elements / AF network elements, etc.

[0943] For example, uplink data can be a response to downlink data, such as a response to a command, such as a response to at least one of the commands read, write, sense, lock, deactivate, or locate.

[0944] The uplink or downlink data can refer to data from an upper layer, such as NAS layer data, application layer data, or A-IoT layer data. In this application, the names of these data can be replaced, such as referring to them as upper-layer data, where "upper layer" refers to the layer above the access layer. For example, if the access layer only has a MAC layer, then it refers to the layer above the MAC layer.

[0945] Eleventh, Feedback

[0946] Feedback, used for responding to uplink data / Msg3.

[0947] Alternatively, as feedback to Msg3, it can be called Msg4.

[0948] Optionally, feedback can be provided for multiple devices or multiple uplink data / Msg3s.

[0949] Optionally, feedback can indicate success or failure by default.

[0950] Optionally, feedback can explicitly indicate success or failure, such as indicating success with a value of 1 and failure with a value of 0.

[0951] Optionally, feedback can be associated with a device. For example, the feedback may carry the device's identification information, or the feedback may be scrambled (descrambled) or CRC masked (demasked) using the device's identification information. The device's identification information can be at least one of AS ID, random ID, and device ID, or a part of AS ID, random ID, and device ID, or derived from AS ID, random ID, and device ID (e.g., through hash operations).

[0952] If feedback is associated with a device, the device can determine whether the uplink data / Msg3 sent before receiving the feedback was successfully transmitted based on the feedback.

[0953] Twelfth, in the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can mean A or B. "And / or" in this application is merely a description of the relationship between the related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. A and B can be singular or plural.

[0954] Thirteenth, in the description of this application, unless otherwise stated, "multiple" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0955] Fourteenth, in the embodiments of this application, the terms "first," "second," etc., distinguish between identical or similar items that have substantially the same function and effect. Those skilled in the art will understand that the terms "first," "second," etc., do not limit the quantity or execution order, and that the terms "first," "second," etc., are not necessarily different.

[0956] In the embodiments of this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0957] Fifteenth, the term "embodiment" as used in this application means that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of this application. Therefore, various embodiments throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It is 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.

[0958] Sixteenth, in this application, "...when" and "if" both refer to the corresponding processing that will be carried out under certain objective circumstances, and are not limited to a specific time, nor do they require a judgment action to be performed during implementation, nor do they imply any other limitations.

[0959] It is understood that, in the above embodiments, the methods and / or steps implemented by the first device can also be implemented by components (e.g., processors, chips, chip systems, circuits, logic modules, or software) that can be used in the first device; similarly, the methods and / or steps implemented by the second device can also be implemented by components (e.g., processors, chips, chip systems, circuits, logic modules, or software) that can be used in the second device. The chip system can be composed of chips, or it can include chips and other discrete devices.

[0960] It is understood that, in order to achieve the above-mentioned functions, the device (such as the first device, the second device) includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0961] This application embodiment can divide the device (such as the first device or the second device) into functional modules according to the above method embodiments. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0962] Figure 37 shows a schematic diagram of the structure of a device 3700. The device 3700 includes a processing module 3701 and a transceiver module 3702. The device 3700 can be used to implement the functions of the first device or the second device described above.

[0963] In some embodiments, the device 3700 further includes a storage module (not shown in FIG37) for storing program instructions and data.

[0964] In some embodiments, the transceiver module 3702, also referred to as a transceiver unit, is used to implement sending and / or receiving functions. The transceiver module 3702 may consist of a transceiver circuit, a transceiver, a transceiver unit, or a communication interface.

[0965] In some embodiments, the transceiver module 3702 may include a receiving module and a sending module, respectively configured to perform receiving and sending steps performed by the first device (or the second device) in the above method embodiments, and / or other processes to support the technology described herein; the processing module 3701 may be configured to perform processing steps (e.g., determination) performed by the first device (or the second device) in the above method embodiments, and / or other processes to support the technology described herein.

[0966] In one possible design, taking device 3700 as the first device in the above method embodiment as an example:

[0967] The transceiver module 3702 is used to receive a first message, which includes first information indicating a first transport block size (TBS).

[0968] The transceiver module 3702 is also used to send a second message. If the first TBS is less than the first threshold, the second message includes the access layer identifier (AS ID) or a temporary identifier of the first device. The second message is determined by the processing module 3701.

[0969] In one possible design, taking device 3700 as the second device in the above method embodiment as an example:

[0970] The transceiver module 3702 is used to send a first message, which includes first information indicating a first transport block size (TBS). The first message is determined by the processing module 3701.

[0971] The transceiver module 3702 is also used to receive a second message. If the first TBS is less than the first threshold, the second message includes the access layer identifier (AS ID) or a temporary identifier of the first device.

[0972] In one possible design, taking device 3700 as the first device in the above method embodiment as an example:

[0973] The transceiver module 3702 is used to receive first information, the first information indicating that the access layer identifier AS ID of the first device is part of a second identifier, the second identifier including at least one of the first identifier, temporary identifier or random identifier of the first device, and the length of the first identifier is greater than the length of the temporary identifier.

[0974] Processing module 3701 is used to determine the AS ID of the first device based on the first information.

[0975] In one possible design, taking device 3700 as the second device in the above method embodiment as an example:

[0976] Processing module 3701 is used to determine first information, the first information indicating that the access layer identifier AS ID of the first device is part of a second identifier, the second identifier including at least one of the first identifier, temporary identifier or random identifier of the first device, and the length of the first identifier is greater than the length of the temporary identifier.

[0977] The transceiver module 3702 is used to send first information to the first device.

[0978] In one possible design, taking device 3700 as the first device in the above method embodiment as an example:

[0979] The transceiver module 3702 is used to send the first data. The first data is determined by the processing module 3701.

[0980] The transceiver module 3702 is also used to receive first information. The first information indicates that the first data transmission failed. The first information also indicates whether to save or release the access stratum identifier (AS ID) or includes the AS ID in the first information.

[0981] In one possible design, taking device 3700 as the second device in the above method embodiment as an example:

[0982] Processing module 3701 is used to determine that the first data transmission of the first device has failed.

[0983] The transceiver module 3702 is used to send first information. The first information indicates that the first data transmission failed. The first information also indicates whether to save or release the access stratum identifier (AS ID), or the first information includes the AS ID.

[0984] In one possible design, taking device 3700 as the first device in the above method embodiment as an example:

[0985] The transceiver module 3702 is used to receive paging messages, which include access layer (AS) information and a paging identifier. The AS information is located before the paging identifier, and the end position of the paging identifier is the least significant bit (LSB) of the paging message.

[0986] Processing module 3701 is used to determine the AS information and the paging identifier based on the paging message.

[0987] In one possible design, taking device 3700 as the second device in the above method embodiment as an example:

[0988] Processing module 3701 is used to determine a paging message, the paging message including access layer (AS) information and a paging identifier, the AS information being located before the paging identifier, and the end position of the paging identifier being the least significant bit (LSB) of the paging message.

[0989] The transceiver module 3702 is used to send the paging message.

[0990] In one possible design, taking device 3700 as the first device in the above method embodiment as an example:

[0991] The transceiver module 3702 is used to receive a first message, the first message including a first access layer identifier (AS ID), and the first message is a contention resolution message.

[0992] The transceiver module 3702 is also used to send first data. The first AS ID is the same as the second AS ID, and the second AS ID is stored in the first device. The processing module 3701 is used to determine that the first AS ID and the second AS ID are the same.

[0993] In one possible design, taking device 3700 as the first device in the above method embodiment as an example:

[0994] The transceiver module 3702 is used to receive paging messages, which include a network identifier.

[0995] The transceiver module 3702 is further configured to transmit first data, the first data including a first identifier, the first identifier being a part of a second identifier and excluding the network identifier, the second identifier being the device identifier of the first device. The processing module 3701 is configured to determine the first data.

[0996] In one possible design, taking device 3700 as the second device in the above method embodiment as an example:

[0997] The transceiver module 3702 is used to send a paging message, the paging message including a network identifier. The processing module 3701 is used to determine the paging message.

[0998] The transceiver module 3702 is also used to receive first data, the first data including a first identifier, the first identifier being part of a second identifier and not including the network identifier, the second identifier being the device identifier of the first device.

[0999] In one possible design, taking device 3700 as the first device in the above method embodiment as an example:

[1000] The transceiver module 3702 is used to receive paging messages, wherein the paging messages indicate at least two first values.

[1001] The transceiver module 3702 is also configured to receive a first message indicating a second value, the second value being included in the at least two first values.

[1002] The transceiver module 3702 is also used to send the first data.

[1003] The transceiver module 3702 is further configured to receive second data during a first time period. The end time of the first time period is determined based on the transmission time of the first data and the second value, whereby the second data is response data to the first data. The processing module 3701 is configured to determine the first time period.

[1004] In one possible design, taking device 3700 as the second device in the above method embodiment as an example:

[1005] The transceiver module 3702 is used to send a paging message, the paging message indicating at least two first values.

[1006] The transceiver module 3702 is also configured to send a first message indicating a second value, the second value being included in the at least two first values.

[1007] The transceiver module 3702 is also used to receive the first data.

[1008] The transceiver module 3702 is further configured to send second data during a first time period. The end time of the first time period is determined based on the first data and the second value, where the second data is response data to the first data. The processing module 3701 is configured to determine the first time period.

[1009] In one possible design, taking device 3700 as the first device in the above method embodiment as an example:

[1010] The processing module 3701 is used to generate random identifiers.

[1011] The processing module 3701 is further configured to, in the event of the random identifier generation, release the access layer identifier (AS ID) or replace the AS ID with the random identifier. The AS ID is stored in the first device.

[1012] All relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[1013] Optionally, in this application, the transceiver module receiving / sending information can also be understood as the processing module receiving / sending information through the transceiver module. The processing module receiving / sending information through the transceiver module can also be understood as the processing module controlling the transceiver module to receive / send information. Alternatively, the processing module sending information through the transceiver module can be understood as the processing module outputting information to the transceiver module, which then sends that information; the processing module receiving information through the transceiver module can be understood as the transceiver module receiving information and inputting that information into the processing module.

[1014] In this application, the device 3700 can be presented in an integrated manner, divided into various functional modules. Here, "module" can refer to an application-specific integrated circuit (ASIC), a circuit, a processor and memory that executes one or more software or firmware programs, integrated logic circuits, and / or other devices that can provide the above functions.

[1015] In some embodiments, when the device 3700 in FIG37 is a chip or chip system, the function / implementation process of the transceiver module 3702 can be implemented through the input / output interface (or communication interface) of the chip or chip system, and the function / implementation process of the processing module 3701 can be implemented through the processor (or processing circuit) of the chip or chip system.

[1016] Since the device 3700 provided in this embodiment can perform the above method, the technical effects it can achieve can be referred to the above method embodiment, and will not be repeated here.

[1017] As a possible product form, the first or second device described in the embodiments of this application can also be implemented using one or more field programmable gate arrays (FPGAs), programmable logic devices (PLDs), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits capable of performing the various functions described throughout this application.

[1018] As another possible product form, the first or second device described in this application embodiment can be implemented using a general bus architecture. For ease of explanation, refer to FIG38, which is a schematic diagram of the structure of device 3800 provided in this application embodiment. Device 3800 includes a processor 3801 and a transceiver 3802. Device 3800 can be the first device, or a chip or chip system therein; or, device 3800 can be the second device, or a chip or chip system therein. FIG38 only shows the main components of device 3800. In addition to the processor 3801 and transceiver 3802, device 3800 may further include a memory 3803 and input / output devices (not shown in the figure).

[1019] Optionally, the processor 3801 is mainly used to process communication protocols and communication data, control the entire device, execute software programs, and process the data of the software programs. The memory 3803 is mainly used to store software programs and data. The transceiver 3802 may include radio frequency (RF) circuitry and an antenna. The RF circuitry is mainly used for converting baseband signals to RF signals and processing RF signals. The antenna is mainly used for transmitting and receiving RF signals in the form of electromagnetic waves. Input / output devices, such as touch screens, displays, and keyboards, are mainly used to receive user input data and output data to the user.

[1020] Optionally, the processor 3801, transceiver 3802, and memory 3803 can be connected via a communication bus.

[1021] It should be noted that the memory 3803 can exist independently of the processor 3801, or it can be integrated with the processor 3801. The memory 3803 can be located inside or outside the device 3800, without restriction.

[1022] When the device is powered on, the processor 3801 can read the software program in the memory 3803, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be transmitted wirelessly, the processor 3801 performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency (RF) circuit. The RF circuit processes the baseband signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor 3801. The processor 3801 converts the baseband signal into data and processes the data.

[1023] In another implementation, the radio frequency circuitry and antenna can be set up independently of the processor performing baseband processing. For example, in a distributed scenario, the radio frequency circuitry and antenna can be arranged remotely, independent of the device.

[1024] In some embodiments, those skilled in the art will recognize that the above-described device 3700 can be implemented in the form of the device 3800 shown in FIG38.

[1025] As an example, the function / implementation of the processing module 3701 in Figure 37 can be achieved by the processor 3801 in the device 3800 shown in Figure 38 calling computer execution instructions stored in the memory 3803. The function / implementation of the transceiver module 3702 in Figure 37 can be achieved by the transceiver 3802 in the device 3800 shown in Figure 38.

[1026] As another possible product form, the first or second device in this application may adopt the composition structure shown in FIG39, or include the components shown in FIG39. FIG39 is a schematic diagram of the composition of a device 3900 provided in this application.

[1027] As shown in Figure 39, the device 3900 includes at least one processor 3901. Optionally, the device also includes a communication interface 3902.

[1028] When the relevant program instructions are executed in the at least one processor 3901, the device 3900 can implement the methods provided in any of the foregoing embodiments and any of the possible designs therein. Alternatively, the processor 3901 can implement the methods provided in any of the foregoing embodiments and any of the possible designs therein through logic circuits or executable code instructions.

[1029] The communication interface 3902 can be used to receive program instructions and transmit them to the processor, or the communication interface 3902 can be used for device 3900 to communicate and interact with other communication devices, such as exchanging control signaling and / or service data. For example, the communication interface 3902 can be used to receive signals from other devices besides device 3900 and transmit them to the processor 3901, or to send signals from the processor 3901 to other devices besides device 3900.

[1030] Optionally, the communication interface 3902 can be a code and / or data read / write interface circuit, or the communication interface 3902 can be a signal transmission interface circuit between a communication processor and a transceiver, or a pin of a chip.

[1031] Optionally, the device 3900 may also include at least one memory 3903, which may be used to store the required program instructions and / or data.

[1032] It should be noted that the memory 3903 can exist independently of the processor 3901, or it can be integrated with the processor 3901. The memory 3903 can be located inside or outside the device 3900, without restriction.

[1033] Optionally, the device 3900 may further include a power supply circuit 3904, which can be used to power the processor 3901. The power supply circuit 3904 may be located in the same chip as the processor 3901, or in a separate chip outside the chip containing the processor 3901.

[1034] Optionally, the device 3900 also includes a bus 3905, through which the various parts of the device 3900 can be interconnected.

[1035] In some embodiments, those skilled in the art will recognize that the device 3700 shown in FIG37 can be implemented in the form of the device 3900 shown in FIG39.

[1036] As an example, the function / implementation of the processing module 3701 in Figure 37 can be achieved by the processor 3901 in the device 3900 shown in Figure 39 calling computer execution instructions stored in the memory 3903. The function / implementation of the transceiver module 3702 in Figure 37 can be achieved by the communication interface 3902 in the device 3900 shown in Figure 39.

[1037] It should be noted that the structure shown in Figure 39 does not constitute a specific limitation on the first or second device. For example, in other embodiments of this application, the first or second device may include more or fewer components than shown, or combine some components, or split some components, or have different component arrangements. The components shown can be implemented in hardware, software, or a combination of software and hardware.

[1038] Optionally, the processor in this application can be a central processing unit (CPU), or it can be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The general-purpose processor can be a microprocessor, or it can be any conventional processor.

[1039] Optionally, the memory in this application can be volatile memory or non-volatile memory, or it can 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 random access memory (RAM) are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDR SDRAM), enhanced synchronous DRAM (ESDRAM), synchronous linked DRAM (SLDRAM), or direct rambus RAM (DR RAM).

[1040] Optionally, the power supply circuit described in the embodiments of this application includes, but is not limited to, at least one of the following: a power supply line for an electronic system, a power management chip, a power management processor, or a power management control circuit.

[1041] In some embodiments, this application also provides an apparatus including a processor for implementing the methods in any of the above method embodiments.

[1042] As one possible implementation, the device also includes a memory. This memory stores necessary computer programs and data. The computer program may include instructions, which the processor can invoke to instruct the device to execute the methods in any of the above method embodiments. Alternatively, the memory may not be present in the device.

[1043] As another possible implementation, the device also includes an interface circuit, which is a code / data read / write interface circuit, used to receive computer execution instructions (which are stored in memory and may be read directly from memory or may be transmitted through other devices) and transmit them to the processor.

[1044] As another possible implementation, the device also includes a communication interface for communicating with modules outside the device.

[1045] It is understood that the device can be a chip or a chip system. When the device is a chip system, it can be composed of chips or may include chips and other discrete devices. This application does not specifically limit this.

[1046] This application also provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed by a computer, implements the functions of any of the above-described method embodiments.

[1047] This application also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

[1048] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[1049] It is understood that the systems, apparatuses, and methods described in this application can also 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 shown or discussed mutual couplings or direct couplings or communication connections may be through some interfaces, or indirect couplings or communication connections between devices or units, which may be electrical, mechanical, or other forms. The units described as separate components may or may not be physically separate, i.e., they may be located in one place or distributed across multiple network units. The components shown as units may or may not be physical units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs. Additionally, the functional units in the various embodiments of this application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. In the above embodiments, they can be implemented entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software programs, it can be implemented entirely or partially in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device including one or more servers, data centers, etc., that can be integrated with the medium. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive (SSD)). In the embodiments of this application, the computer may include the aforementioned devices. Although this application has been described herein in conjunction with various embodiments, other variations of the disclosed embodiments can be understood and implemented by those skilled in the art in carrying out the claimed application by reviewing the accompanying drawings, the disclosure, and the appended claims.In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple components. A single processor or other unit can implement several functions listed in the claims. Although different dependent claims may describe certain measures, this does not mean that these measures cannot be combined to produce a good effect.

Claims

1. A communication method, characterized in that, Applied to a first device, the method includes: Receive a first message, the first message including first information, the first information indicating a first transport block size (TBS); Send a second message; If the first TBS is less than the first threshold, the second message includes the access layer identifier (AS ID) or temporary identifier of the first device.

2. The method according to claim 1, characterized in that, The method further includes receiving a third message, the third message indicating that the AS ID be saved.

3. A communication method, characterized in that, include: Send a first message, the first message including first information, the first information indicating a first transport block size (TBS); Receive the second message; If the first TBS is less than the first threshold, the second message includes the access layer identifier (AS ID) or temporary identifier of the first device.

4. The method according to claim 3, characterized in that, The method further includes sending a third message, the third message instructing that the AS ID be saved.

5. The method according to any one of claims 1-4, characterized in that, If the first TBS is greater than or equal to the first threshold, the second message includes a first identifier of the first device, the length of which is greater than the length of the AS ID and the length of the temporary identifier.

6. The method according to claim 5, characterized in that, The first identifier is the device identifier.

7. The method according to any one of claims 1-6, characterized in that, The first message is used to page the first device or to instruct the first device to resolve contention.

8. A communication device, characterized in that, The communication device is a first device, comprising a module for implementing the method as described in any one of claims 1-2 and 5-7.

9. The communication device according to claim 8, characterized in that, The communication device is an environmental IoT device or a chip in an environmental IoT device.

10. A communication device, characterized in that, The communication device is a second device, including a module for implementing the method as described in any one of claims 3-7.

11. The communication device according to claim 10, characterized in that, The communication device is a reader or a chip in a reader.

12. A computer-readable storage medium, comprising a first device, the computer-readable storage medium storing a computer program or instructions, characterized in that, When the computer program or instructions are run, the method as described in any one of claims 1-2 and 5-7 is implemented.

13. A computer program product, said computer program product being contained in a first device, characterized in that, When the computer program product is run, the method as described in any one of claims 1-2 and 5-7 is implemented.

14. A computer-readable storage medium, comprising a second device, the computer-readable storage medium storing a computer program or instructions, characterized in that, When the computer program or instructions are run, the method as described in any one of claims 3-7 is implemented.

15. A computer program product, said computer program product being included in a second device, characterized in that, When the computer program product is run, the method as described in any one of claims 3-7 is implemented.

Images