Communication method and communication apparatus

Abstract

Provided are a communication method and a communication apparatus. The method is applied to the field of communications. The method comprises: by sending request information, a first AIoT device requests a network device to allocate a device identifier (ID); or the first AIoT device receives the device ID allocated by the network device, and sends confirmation information to the network device. On the basis of the foregoing two manners of allocating the device ID, the device ID (for example, an AS ID) can be allocated to an AIoT device, so as to achieve data transmission between the network device and the first AIoT device on the basis of the device ID. In addition, compared with using a high-layer ID of the AIoT device, the device ID allocated in the present application occupies fewer bits, thereby being conducive to saving resources.

Description

Communication methods and communication devices

[0001] This application claims priority to Chinese Patent Application No. 202411958559.5, filed on December 27, 2024, entitled "Communication Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field

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

[0003] Ambient Internet of Things (AIoT) technology is an emerging communication technology. With the rapid development of communication technology, applying AIoT to communication technologies has become a major trend in order to provide users with richer communication experiences. When AIoT technology is applied to communication technologies (such as 5G mobile communication), data transmission can occur between network devices and AIoT devices. When data transmission occurs between network devices and AIoT devices, identifiers are needed to indicate the objects being processed. However, currently, there is no specific solution for assigning device identifiers to AIoT devices. Summary of the Invention

[0004] In view of this, this application provides a communication method, communication device, chip system, computer-readable storage medium, computer program product, and communication system capable of assigning device identifiers to AIoT devices.

[0005] In a first aspect, a communication method is provided. This method can be executed by, for example, a first AIoT device, or by a component (such as a circuit, chip, or chip system) configured in the first AIoT device, or by a logic module or software capable of implementing all or part of the functions of the AIoT device. This application does not limit this aspect.

[0006] Specifically, the method includes: a first AIoT device receiving first information from a first network device, the first information being used to indicate a device identifier, the device identifier being used to identify the first AIoT device; and sending second information, the second information being used to request or confirm the device identifier.

[0007] The second information, used to request a device identifier, can be understood as: the first AIoT device requests the first network device to assign a device identifier. That is, "the first AIoT device sending the second information" can occur before "the first AIoT device receiving the first information from the first network device."

[0008] The second information used to confirm the device identifier can be understood as follows: after the first network device sends the first information to the first AIoT device, the first AIoT device replies with the second information to the first network device to confirm the device identifier. That is, "the first AIoT device sending the second information" can occur after "the first AIoT device receiving the first information from the first network device".

[0009] The device identifier in this application serves to identify AIoT devices, ensuring that data transmission can be performed using the device identifier during subsequent data transmission. This application does not impose specific limitations on the naming of the device identifier. For example, the device identifier can be represented as an access identifier (AS ID) or an access layer identifier.

[0010] Based on the above technical solutions, in this embodiment, the first AIoT device requests a device identifier from the network device by sending a request message; or, the first AIoT device receives a device identifier assigned by the network device and sends an acknowledgment message to the network device. Based on these two methods of assigning device identifiers, a device identifier (e.g., AS ID) can be assigned to the first AIoT device, enabling data transmission between the network device and the first AIoT device based on the device identifier. Furthermore, compared to using a higher-layer identifier for the AIoT device, the device identifier assigned in this application occupies fewer bits, thus saving resources.

[0011] In one possible implementation, the first AIoT device sends the second information, including sending the second information if one or more of the following conditions are met:

[0012] The first AIoT device has the ability to use device identification;

[0013] The data to be transmitted by the first AIoT device meets preset conditions;

[0014] The energy of the first AIoT device meets the energy threshold value;

[0015] The first AIoT device supports data segmentation functionality;

[0016] The first AIoT device needs to perform segmentation processing on the uplink data.

[0017] For example, the first AIoT device has the ability to use a device identifier, including: the first AIoT device supports the allocation of a device identifier (such as an AS ID); the first AIoT device supports the use of a device identifier (such as an AS ID); the first AIoT device supports available or unavailable information provided by the network; the first AIoT device supports establishing a connection with the network side (such as a first network device), etc.

[0018] For example, the data to be transmitted by the first AIoT device meets preset conditions, including: the amount of data to be transmitted by the first AIoT device is greater than or equal to a first threshold value; and / or, the number of data packets to be transmitted by the first AIoT device is greater than or equal to a second threshold value.

[0019] For example, the energy of the first AIoT device meets an energy threshold value, including: the energy of the first AIoT device is greater than or equal to the energy threshold value.

[0020] For example, the first AIoT device supporting data segmentation means that the first AIoT device has the function of data segmentation. That is, when the data packet to be transmitted is relatively large, the data segmentation function can divide the data packet into multiple smaller data packets for transmission.

[0021] For example, the first AIoT device needs to perform segmentation processing on the uplink data, which can be understood as the first AIoT device needs to perform data segmentation on the D2R data in order to divide the D2R data into small data packets for transmission.

[0022] In other words, regardless of whether the first network device actively allocates the device identifier or the first AIoT device requests the first network device to allocate the device identifier, the first AIoT device can send the second information to obtain the device identifier if one or more of the above conditions are met.

[0023] In one possible implementation, the second information is one or more of the following: device identifier allocation request indication information, device identifier confirmation indication information, device identifier, first random number RN16, first preamble sequence, data segmentation indication information, energy indication information of the first AIoT device, amount of data to be transmitted indication information, number of data packets to be transmitted indication information, and capability indication information of environmental IoT services.

[0024] This application does not specifically limit whether the second information is the message body or an element within the message body. Optionally, the second information is carried in the AIoT device-to-network device (D2R) data.

[0025] This application does not specifically limit the specific form or generation method of the device identifier. Optionally, the device identifier includes one or more of the following: a random number of a first preset length; a first network device identifier; a first identifier, wherein the first identifier is one or more of the random number RN16 generated by the first AIoT device, a first random access preamble, and a resource number indication; and a second identifier, wherein the second identifier is an identifier generated based on the AIoT device's higher-layer identifier. The resource number indication includes a time-domain resource number indication and / or a frequency-domain resource number indication. The first preset length random number refers to a random number of a predefined length generated by the first network device.

[0026] The aforementioned first identifier can take several forms. For example, the first identifier can be one or more of the following: a 16-bit random number (which can be represented as RN16) sent by the first AIoT device, a first random access preamble, and a resource number indicator. RN16 is generated by the first AIoT device according to predetermined rules. The first random access preamble is a preamble identifier (or preamble sequence) sent by the first AIoT device during the access process. The resource number indicator includes a time-domain resource number indicator and / or a frequency-domain resource number indicator.

[0027] The aforementioned first information is sent by the first network device and is used to indicate the device identifier. The first information can have different forms of representation. The first information used to indicate the device identifier can be an explicit indication or an implicit indication, without specific limitations. Alternatively, the first information can directly or indirectly include the device identifier.

[0028] Optionally, the first information includes one or more of the following: reuse indication information, allocation indication information, and device identifier. The reuse indication information is used to indicate that the first identifier and / or the second identifier are used as the device identifier. The allocation indication (AI) information is used to instruct the first network device to allocate the device identifier.

[0029] Optionally, the first information may also include message type and / or resource indication information. The message type is used to indicate one or more of the following: whether the message body containing the first information or the first information itself contains the allocation of a device identifier. The resource indication information is used to indicate the transmission resources used for the current transmission of R2D data and / or the subsequent transmission of D2R data, specifically including time-domain resources and / or frequency-domain resources.

[0030] Optionally, the first information may also include: the allocation method of the device identifier; and the length (or number of bits) of the device identifier.

[0031] Optionally, the method further includes: a first AIoT device sending a device identifier, the device identifier being a device identifier determined by the first AIoT device based on the first information. For example, for security reasons, the first network device may not know the specific content of the higher-layer identifier of the AIoT device, but the first network device may instruct the first AIoT device to use certain bits of the higher-layer identifier; or instruct the first AIoT device to report the device identifier it uses.

[0032] Therefore, after determining the device identifier, the first AIoT device can report the device identifier to the first network device so that the first network device can know the device identifier. This ensures that the first network device and the first AIoT device have a consistent understanding of the device identifier, which facilitates subsequent data transmission based on the device identifier.

[0033] The embodiments of this application do not limit the specific method by which the first AIoT device determines the device identifier. It can be determined based on the first information sent by the first network device or based on the information sent by the second network device to the first AIoT device.

[0034] In one possible implementation, the device identifier can also have a time limit. From the perspective of time limit, the device identifier can be classified as either single-use or reusable (or long-term use). Furthermore, the validity period or invalidity period of the device identifier can be specified, or the size of the data transmitted using the device identifier or the number of data packets can be specified to describe the time limit of the device identifier.

[0035] It should be understood that the first network device may indicate various time-sensitive information regarding device identification through the first information when allocating device identification, or through a separate message or information cell, without specific limitations.

[0036] Optionally, the first information is further used to indicate one or more of the following: the type of the device identifier; validity information, which indicates that the first AIoT device can use the device identifier for a first duration, and / or that the first AIoT device can use the amount of data or data packets transmitted by the device identifier; and invalidity information, which indicates that the device identifier is invalid.

[0037] Invalidity information is used to indicate that the device identifier is invalid. Invalidity information can be understood as describing the validity of the device identifier from another perspective. Optionally, the invalidity information includes one or more of the following: second duration information, used to indicate that the device identifier will be released if no data is transmitted within a second duration; data packet count information, used to indicate that the device identifier will be released after transmitting a preset number of AIoT data packets; and first energy information, used to indicate that the device identifier will be released if the energy of the first AIoT device meets a preset condition.

[0038] Therefore, the first network device can also use the first information to indicate the timeliness of the device identifier, so as to make reasonable use of the device identifier and improve resource utilization.

[0039] Optionally, the first information is carried in the network device to AIoT device R2D data.

[0040] Secondly, a communication method is provided, which may be executed by a first network device, or by a component (such as a circuit, chip, or chip system) configured in the first network device, or by a logic module or software capable of implementing all or part of the functions of the first network device. This application does not limit this method.

[0041] Specifically, the method includes: a first network device sending first information, the first information being used to indicate a device identifier, the device identifier being used to identify a first AIoT device; and receiving second information, the second information being used to request or confirm the device identifier.

[0042] For the two implementation methods of assigning device identifiers to the first network device, please refer to the description in the first aspect. For the sake of brevity, they will not be elaborated here.

[0043] The device identifier in this application serves to identify AIoT devices, ensuring that data transmission can be performed using the device identifier during subsequent data transmission. This application does not impose specific limitations on the naming of the device identifier. For example, the device identifier can be represented as an access identifier (AS ID) or an access layer identifier.

[0044] Based on the above technical solutions, in this embodiment, the first network device receives request information and sends first information to the first AIoT device based on the request information (or uses the first information to indicate a device identifier); or, the first network device sends first information to the first AIoT device and receives confirmation information sent by the first AIoT device. Based on the aforementioned two methods of allocating device identifiers, it is possible to assign a device identifier (e.g., AS ID) to the AIoT device, enabling data transmission between the network device and the first AIoT device based on the device identifier. Furthermore, compared to using the higher-layer identifier of the AIoT device, the device identifier allocated in this application occupies fewer bits, which helps save resources.

[0045] In one possible implementation, the second information is one or more of the following: device identifier allocation request indication information, device identifier confirmation indication information, the device identifier, a first random number RN16, a first preamble sequence, data segmentation indication information, energy indication information of the first AIoT device, data volume indication information to be transmitted, number of data packets to be transmitted indication information, and capability indication information of the environmental IoT service.

[0046] For a description of the second piece of information, please refer to the first aspect. For the sake of brevity, it will not be elaborated here.

[0047] The preceding text described different implementation methods for the first network device to allocate device identifiers: proactive allocation of device identifiers or allocation of device identifiers based on a request from the first AIoT device. For the first network device, it can determine how to allocate device identifiers based on auxiliary information sent by the second network device.

[0048] In one possible implementation, the method further includes: a first network device receiving auxiliary information from a second network device, the auxiliary information being used to assign a device identifier to the first AIoT device. The auxiliary information can be used to assist the first network device in confirming whether the first AIoT device can be assigned a device identifier, and / or to assist the first network device in how to assign the device identifier.

[0049] This application embodiment does not specifically limit the specific content and / or presentation of the auxiliary information. Optionally, the auxiliary information includes one or more of the following: capability information of the first AIoT device, service type of the first AIoT device, energy status of the first AIoT device, second identifier, and device identifier allocation information; the device identifier allocation information is used to determine the device identifier; wherein, the capability information of the first AIoT device includes capability indication information for data segmentation function and / or capability indication information for using the device identifier; the second identifier is an identifier generated based on the higher-level identifier of the AIoT device.

[0050] Therefore, by receiving auxiliary information from the second network device, the first network device can assign appropriate device identifiers to the AIoT devices, ensuring that the device identifiers are synchronized between the network device and the AIoT devices for use in subsequent data transmission. Furthermore, the first network device can quickly release device identifiers that are unusable by the AIoT devices, improving the efficiency of device identifier usage.

[0051] Optionally, the device identifier is generated based on the AIoT device high-level identifier.

[0052] Optionally, the device identifier allocation information includes one or more of the following: a second preset length, which is the length of the device identifier generated based on some or all of the bits of the AIoT device high-level identifier; and a first bit range, which is the bit range of the device identifier generated based on some or all of the bits of the AIoT device high-level identifier.

[0053] This application does not specifically limit the specific form or generation method of the device identifier. Exemplarily, the device identifier includes one or more of the following: a first preset length random number; a first network device identifier; a first identifier, wherein the first identifier is one or more of the following: a random number RN16 generated by the first AIoT device, a first random access preamble, and a resource number indicator; and a second identifier, wherein the second identifier is an identifier generated based on the AIoT device's higher-layer identifier. The first preset length random number refers to a random number of a predefined length generated by the first network device.

[0054] The aforementioned first identifier can take several forms. For example, the first identifier can be one or more of the following: a 16-bit random number (which can be represented as RN16) sent by the first AIoT device, a first random access preamble, and a resource number indicator. RN16 is generated by the first AIoT device according to a predetermined rule. The first random access preamble is a preamble identifier (or preamble sequence) sent by the first AIoT device during the access process. The resource number indicator includes a time-domain resource number indicator and / or a frequency-domain resource number indicator. Optionally, the resource is the access resource of the first AIoT device.

[0055] The aforementioned first information is sent by the first network device and is used to indicate the device identifier. The first information can have different forms of representation. The first information used to indicate the device identifier can be an explicit indication or an implicit indication, without specific limitations. Alternatively, the first information can directly or indirectly include the device identifier.

[0056] This application does not specifically limit the form of the first information in its embodiments. Exemplarily, the first information includes one or more of the following: reuse indication information, allocation indication information, and the device identifier; wherein the reuse indication information is used to indicate that a first identifier and / or a second identifier are used as the device identifier; and the allocation indication information is used to indicate the allocation of a device identifier.

[0057] Optionally, the first information may also include message type and / or resource indication information. The message type is used to indicate one or more of the following: whether the message body containing the first information or the first information itself contains the allocation of a device identifier. The resource indication information is used to indicate the transmission resources used for the current transmission of R2D data and / or the subsequent transmission of D2R data, specifically including time-domain resources and / or frequency-domain resources.

[0058] Optionally, the first information may also include: the allocation method of the device identifier; and the length (or number of bits) of the device identifier.

[0059] Optionally, the method further includes: a first network device receiving the device identifier from a first AIoT device, the device identifier being a device identifier determined by the first AIoT device based on the first information. For example, for security reasons, the first network device may not know the specific content of the higher-layer identifier of the AIoT device, but the first network device may instruct the first AIoT device to use certain bits of the higher-layer identifier; or instruct the first AIoT device to report the device identifier it uses.

[0060] Therefore, the first network device can know the device identifier determined by the first AIoT device, which can ensure that the first network device and the first AIoT device have a consistent understanding of the device identifier, thereby facilitating subsequent data transmission based on the device identifier.

[0061] In one possible implementation, the device identifier can also have a time limit. From the perspective of time limit, the device identifier can be classified as either single-use or reusable (or long-term use). Furthermore, the validity period or invalidity period of the device identifier can be specified, or the size of the data transmitted using the device identifier or the number of data packets can be specified to describe the time limit of the device identifier.

[0062] It should be understood that the first network device may indicate various time-sensitive information regarding device identification through the first information when allocating device identification, or through a separate message or information cell, without specific limitations.

[0063] Optionally, the first information is further used to indicate one or more of the following: the type of the device identifier; validity information, which indicates that the first AIoT device can use the device identifier for a first duration, and / or that the first AIoT device can use the amount of data or data packets transmitted by the device identifier; and invalidity information, which indicates that the device identifier is invalid.

[0064] Invalidity information is used to indicate that the device identifier is invalid. Invalidity information can be understood as describing the validity of the device identifier from another perspective. Optionally, the invalidity information includes one or more of the following: second duration information, used to indicate that the device identifier will be released if no data is transmitted within a second duration; data packet count information, used to indicate that the device identifier will be released after transmitting a preset number of AIoT data packets; and first energy information, used to indicate that the device identifier will be released if the energy of the first AIoT device meets a preset condition.

[0065] Therefore, the first network device can also use the first information to indicate the timeliness of the device identifier, so as to make reasonable use of the device identifier and improve resource utilization.

[0066] Optionally, the first information is carried in the network device to AIoT device R2D data.

[0067] Thirdly, a communication method is provided, which may be executed by a first AIoT device, or by a component (such as a circuit, chip, or chip system) configured in the first AIoT device, or by a logic module or software capable of implementing all or part of the functions of the AIoT device. This application does not limit this method.

[0068] Specifically, the method includes: a first AIoT device receiving first information from a first network device, the first information indicating that the first network device supports the ability to assign a device identifier, the device identifier being used to identify the first AIoT device; sending second information, the second information being used to request the device identifier; and receiving third information from the first network device, the third information including the device identifier (e.g., AS ID) assigned by the first network device. Optionally, the third information may also include a reuse indication.

[0069] Based on the above technical solution, when the first AIoT device learns that the first network device has the ability to allocate device identifiers, it can send a request message to the first network device to request the first network device to allocate device identifiers, thereby enabling data transmission between the network device and the first AIoT device based on device identifiers. Furthermore, compared to using higher-layer identifiers of AIoT devices, the device identifiers allocated in this application occupy fewer bits, which helps save resources.

[0070] For explanations of the auxiliary information, please refer to the description in the second part. For the sake of brevity, it will not be repeated here.

[0071] Fourthly, a communication method is provided, which may be executed by a first network device, or by a component (such as a circuit, chip, or chip system) configured in the first network device, or by a logic module or software capable of implementing all or part of the functions of the first network device. This application does not limit this aspect.

[0072] Specifically, the method includes: a first network device sending first information, the first information indicating that the first network device supports the ability to allocate a device identifier, the device identifier being used to identify the first AIoT device; receiving second information, the second information being used to request the device identifier; and sending third information, the third information including the device identifier allocated by the first network device.

[0073] It should be noted that the purpose of the first information is to indicate that the first network device has the ability to assign device identifiers, and not to actually indicate the device identifier. The first network device assigns a device identifier to the AIoT device when it sends the third information.

[0074] This application does not specifically limit the form or method of the first network device being identified by the third information distribution device.

[0075] Optionally, the third information includes reuse instruction information. A description of the reuse instruction information can be found above; for brevity, it will not be repeated here.

[0076] In this embodiment, the first network device indicates its ability to allocate device identifiers to the AIoT device, enabling the AIoT device to request a device identifier from the first network device. Subsequently, based on the AIoT device's request, the first network device allocates a device identifier to the AIoT device, thereby achieving the purpose of device identifier allocation and enabling data transmission between the network device and the first AIoT device based on the device identifier. Furthermore, compared to using higher-layer identifiers of the AIoT device, the device identifier allocated in this application occupies fewer bits, helping to save resources.

[0077] Fifthly, a communication method is provided, which may be executed by a second network device, or by a component (such as a circuit, chip, or chip system) configured in the second network device, or by a logic module or software capable of implementing all or part of the functions of the second network device. This application does not limit this aspect.

[0078] Specifically, the method includes: a second network device sending auxiliary information to a first network device, the auxiliary information being used to assign a device identifier to a first AIoT device; the auxiliary information including one or more of the following: capability information of the first AIoT device, service type of the first AIoT device, energy status of the first AIoT device, device identifier allocation information, a second identifier, and device identifier allocation information; the device identifier allocation information being used to determine the device identifier; wherein, the capability information of the first AIoT device includes capability indication information for data segmentation function and / or capability indication information for using the device identifier; the second identifier is an identifier generated based on the higher-level identifier of the AIoT device.

[0079] Based on the above technical solution, the second network device sends auxiliary information to the first network device to assist the first network device in assigning appropriate device identifiers to the AIoT devices. This ensures that the device identifiers are synchronized between the network device and the AIoT devices, enabling the correct device identifiers to be used in subsequent data transmission. In this way, the first network device can quickly release device identifiers that are unusable by the AIoT devices, thereby improving the efficiency of device identifier utilization.

[0080] This application does not specifically limit how the second network device obtains auxiliary information. For example, the auxiliary information may be reported to the second network device by other network elements, or it may be predefined, or it may be sent to the core network device during the subscription process; no specific limitation is made in this regard.

[0081] Optionally, the device identifier is generated based on the AIoT device high-level identifier.

[0082] In one possible implementation, the device identifier allocation information includes one or more of the following: a second preset length, which is the length of the device identifier generated based on some or all of the bits of the AIoT device high-level identifier; and a first bit range, which is the bit range of the device identifier generated based on some or all of the bits of the AIoT device high-level identifier.

[0083] In a sixth aspect, a communication apparatus is provided, comprising modules or units for performing the method in any possible implementation of the first aspect described above.

[0084] In one design, the communication device may include modules that perform the methods / operations / steps / actions described in the foregoing aspects. These modules may be hardware circuits, software, or a combination of hardware circuits and software.

[0085] In one design, the communication device is a communication chip, which may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0086] In another design, the communication device is a communication equipment, which may include a transmitter for sending information or data and a receiver for receiving information or data.

[0087] In another design, the communication device is used to perform the method in any possible implementation of the first or third aspect described above. The communication device may be configured in the first AIoT device, or the communication device itself may be the first AIoT device.

[0088] In a seventh aspect, a communication apparatus is provided, comprising modules or units for performing the methods in any possible implementation of the second or fourth aspect described above.

[0089] In one design, the communication device may include modules that perform the methods / operations / steps / actions described in the foregoing aspects. These modules may be hardware circuits, software, or a combination of hardware circuits and software.

[0090] In one design, the communication device is a communication chip, which may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0091] In another design, the communication device is a communication equipment, which may include a transmitter for sending information or data and a receiver for receiving information or data.

[0092] In another design, the communication device is used to perform the method in any possible implementation of the second aspect described above. The communication device may be configured in the first network device, or the communication device itself may be the first network device.

[0093] Optionally, the first network device may be an access network device (e.g., gNB), a core network device (e.g., AMF network element, AF network element, NEF network element), a device capable of providing data transmission functions for AIoT devices (e.g., relay node, auxiliary node, UE, etc.), an AIoT controller, or a device with AIoT functions.

[0094] Eighthly, a communication apparatus is provided, comprising modules or units for performing the method in any possible implementation of the fifth aspect described above.

[0095] In one design, the communication device may include modules that perform the methods / operations / steps / actions described in the foregoing aspects. These modules may be hardware circuits, software, or a combination of hardware circuits and software.

[0096] In one design, the communication device is a communication chip, which may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0097] In another design, the communication device is a communication equipment, which may include a transmitter for sending information or data and a receiver for receiving information or data.

[0098] In another design, the communication device is used to perform the method in any possible implementation of the fifth aspect described above. The communication device may be configured in the second network device, or the communication device itself may be the second network device.

[0099] Optionally, the second network device may be a core network device (e.g., an AMF network element, an AF network element, or a NEF network element), an AIoT controller, or a device with AIoT functionality.

[0100] A ninth aspect provides a communication device including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the methods in any possible implementation of the first or third aspect described above. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

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

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

[0103] A tenth aspect provides a communication device including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the methods in any possible implementation of the second or fourth aspect described above. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

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

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

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

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

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

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

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

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

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

[0113] Optionally, the memory may be integrated with the processor, or the memory may be separated from the processor.

[0114] In specific implementation, the memory can be a non-transitory memory, such as read-only memory (ROM), which can be integrated with the processor on the same chip or set on different chips. The embodiments of this application do not limit the type of memory or the way the memory and processor are set.

[0115] It should be understood that the relevant data interaction process, such as sending indication information, can be the process of the processor outputting indication information, and receiving capability information can be the process of the processor receiving input capability information. Specifically, the data output by the processor can be sent to the transmitter, and the input data received by the processor can come from the receiver. Here, the transmitter and receiver can be collectively referred to as a transceiver.

[0116] The processing device mentioned in aspect thirteen above can be one or more chips. The processor in the processing device can be implemented in hardware or in software. When implemented in hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented in software, the processor can be a general-purpose processor that reads software code stored in memory. The memory can be integrated into the processor or located outside the processor and exist independently.

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

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

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

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

[0121] In a seventeenth aspect, a communication system is provided, including the aforementioned first AIoT device and first network device. Optionally, the communication system further includes a second network device. Optionally, the communication system further includes one or more first devices, such as environmental IoT devices.

[0122] Optionally, the communication system may also include other devices that communicate with the first AIoT device and / or the first network device.

[0123] Optionally, the communication system may also include other devices that communicate with the second network device. Attached Figure Description

[0124] Figure 1 is an example diagram of a communication system;

[0125] Figure 2 is an example diagram of various topologies shown in the embodiments of this application;

[0126] Figure 3 is an example diagram of an access network device;

[0127] Figure 4 is an example interaction diagram of a communication method according to an embodiment of this application;

[0128] Figures 5A to 5G are example diagrams of various message body formats of MSG2 according to embodiments of this application;

[0129] Figure 6A is another interactive example diagram of the communication method according to an embodiment of this application;

[0130] Figure 6B is an example diagram of confirmation information in an embodiment of this application;

[0131] Figure 7 is another interactive example diagram of the communication method according to an embodiment of this application;

[0132] Figure 8 is another interactive example diagram of the communication method according to an embodiment of this application;

[0133] Figure 9 is another interactive example diagram of the communication method according to an embodiment of this application;

[0134] Figure 10 is another interactive example diagram of the communication method according to an embodiment of this application;

[0135] Figure 11 is a schematic block diagram of a communication device provided in an embodiment of this application;

[0136] Figure 12 is another schematic block diagram of the communication device provided in the embodiments of this application. Detailed Implementation

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

[0138] In this application embodiment, "multiple" can be understood as "at least two"; "multiple items" can be understood as "at least two items".

[0139] This application can be applied to communication systems. Mobile communication systems include, but are not limited to, the following systems: Long Term Evolution (LTE) systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) systems, 5th Generation (5G) systems or new radio (NR) systems, 5.5G systems, and future mobile communication systems; vehicle-to-X (V2X) systems, where V2X can include vehicle-to-network (V2N), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), etc.; Long Term Evolution-Vehicle (LTE-V) technology for vehicle-to-everything (V2V) communication; vehicle-to-everything (V2X) communication; machine-type communication (MTC); Internet of Things (IoT); Long Term Evolution-Machine (LTE-M) technology for machine-to-machine (M2M) communication; and machine-to-machine (M2M) communication. Machine (M2M), etc.

[0140] The technical solutions of this application are applicable to communication systems that provide ambient internet of things (AIoT) services. Optionally, in some embodiments, the communication system providing AIoT services may include an ambient IoT device (AIoT device), or an ambient IoT AIoT terminal (which can be understood as a terminal capable of providing AIoT services). An ambient IoT device is an IoT device powered by energy harvesting and has limited energy storage capacity. For example, some or all of the characteristics of an ambient IoT device can be referred to the description in 3GPP standard TR 38.769. It should be understood that the description of some or all of the characteristics of an ambient IoT device referred to in 3GPP standard TR 38.769 is only a possible example description, and the embodiments of this application are not limited thereto. For example, as the communication standard protocol version evolves or is updated, some or all of the characteristics of the ambient IoT device can be referred to the evolved or updated version; or some or all of the characteristics of the ambient IoT device can also be referred to the description in related technologies.

[0141] The technical solutions of this application embodiment are also applicable to Internet of Things (IoT) communication scenarios and communication scenarios relying on backscatter technology. The aforementioned IoT can be passive IoT, semi-passive IoT, or ambient IoT (AIoT) (or named A-IoT), etc.

[0142] It should be understood that environmental IoT devices may also have other names or definitions, and this application embodiment does not specifically limit them.

[0143] For example, AIoT services can be called Ambient IoT Services / AIoT service. Ambient IoT services are used to support the functions and processes of environmental IoT application scenarios. Currently, there is no clear solution for environmental IoT services.

[0144] Figure 1 shows an example diagram of a communication system according to this application. As shown in Figure 1 (1), there is a first device, a first network device, and a second network device.

[0145] The first network device in this application embodiment can be a core network device, an access network device, or a terminal device. It should be noted that in this application embodiment, devices providing data transmission services for AIoT devices (such as access network devices, relay nodes, UEs, etc.) are collectively referred to as network devices or readers. It should also be noted that in the network architecture involving AIoT services, the role of a network device can be played not only by traditional network devices such as access network devices and core network devices; but also by terminal devices (such as UEs); and by devices with data forwarding functions (such as relay nodes, forwarding nodes, etc.). That is, in the network architecture of AIoT services, any device capable of providing data transmission services for AIoT devices can act as a network device. For ease of description or distinction, the following description uses the first network device as an example.

[0146] The reader in this application embodiment can also be a tag reader / writer, or an RFID reader / writer, or simply a reader / writer. It can be a handheld or fixed device that reads (and sometimes writes) information from electronic tags. A tag reader / writer can also be understood as a device that communicates with electronic tags. As mentioned above, its form can be a terminal or an access network device. It should be understood that a tag reader / writer can also be considered a device with read and write functions.

[0147] The second network device in this application embodiment can be a core network device. For example, the second network device can be an AIoT controller, an ambient internet of things function (AIoTF) network element, an access and mobility management function (AMF) network element, an application function (AF) network element, a network exposure function (NEF) network element, or other devices with AIoT functionality.

[0148] The first device in this application embodiment can be either the source device or the target device for AIoT service data packets. This application embodiment does not specifically limit the form of the first device.

[0149] For example, the first device can be an AIoT device, a passive tag, a semi-passive tag, an active tag, or an ambient IoT terminal.

[0150] For example, the first device in the embodiments of this application can also be an electronic tag. An electronic tag can also be called a radio frequency identification (RFID) tag, RFID, or simply a tag. RFID technology can be further divided into active, passive, and semi-active types. Passive tags can also be called passive IoT, i.e., passive Internet of Things devices, or environmental IoT terminals. Therefore, an electronic tag can also be considered a type of terminal.

[0151] In Figure 1, the first device can be connected to the first network device. This application embodiment does not specifically limit the form of the first network device. The first network device may be a relay node, an auxiliary node, a UE, or other devices. The following description is in conjunction with Figure 2.

[0152] For example, Figure 2 illustrates several possible topologies. The following describes different topologies when the first device is an AIoT device, the network device is an access network device, or a relay node, in conjunction with Figure 2.

[0153] As shown in Figure 2(1), in topology 1, the access network device provides data transmission services to AIoT devices through the wireless interface.

[0154] As shown in Figure 2(2), in topology 2, the intermediate node provides data transmission services to AIoT devices through a wireless interface. The intermediate node can communicate with access network devices through the Uu port. The difference between topology 2 and topology 1 is that data transmission between AIoT devices and access network devices can be forwarded through relay nodes.

[0155] This application does not limit the specific form of the device (such as the intermediate node shown in Figure 2(2)) that provides relay forwarding function for environmental IoT devices. For example, the intermediate node can be a UE, an integrated access and backhaul (IAB) node, a relay node, a relay node, a repeater, or other devices with relay capabilities.

[0156] As shown in Figure 2(3), in topology 3, the access network device and the assisting node communicate via the Uu port. The AIoT device can send uplink data to the access device. In some embodiments, the uplink data is AIoT device-to-network device data, such as device-to-reader (D2R) data. Data sent by the access network device to the AIoT device can be forwarded through the assisting node.

[0157] As shown in Figure 2 (4), the UE provides data transmission services to AIoT devices through the wireless interface. For example, the transmission channel between the UE and the AIoT device may include the physical reader-to-device channel (PRDCH) and the physical device-to-reader channel (PDRCH).

[0158] It should be understood that the PRDCH and PDRCH between the UE and the AIoT device are merely illustrative descriptions of their transmission channels. In fact, the transmission between the UE and the AIoT device is also wireless, and the transmission channel between them can also be other possible forms, which are not specifically limited in this application embodiment.

[0159] It should be noted that in the above topologies, the air interface between network devices (e.g., access network devices, relay nodes, auxiliary nodes, or UEs) and AIoT devices can be named AIoT air interface or AIoT air interface, or other names are not specifically limited. Furthermore, when network devices and AIoT devices transmit data through the AIoT air interface, the content transmitted from AIoT devices to network devices (e.g., data or signaling) can be collectively referred to as D2R data; and the content transmitted from network devices to AIoT devices (e.g., data or signaling) can be collectively referred to as network device to AIoT device data, such as reader to device (R2D) data.

[0160] For example, a network device can specify the resources used for D2R data transmission. Correspondingly, an AIoT device can send D2R data on the resources specified by the network device; and / or, the network device can indicate the resources used for R2D data and inform the AIoT device so that the AIoT device can receive the R2D data.

[0161] It should be understood that the topology shown in Figure 2 is merely an example, and the embodiments of this application are not limited thereto. It should also be understood that the Uu interface mentioned above can be an air interface or wireless interface according to 3GPP protocol specifications such as LTE air interface, NR air interface, and RedCap air interface, and this application does not limit it in this regard.

[0162] In addition, the access network device in this application embodiment is also referred to as an access node. The access network device has wireless transceiver capabilities for communicating with terminals. Access network devices include, but are not limited to, base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs), next-generation NodeBs (gNBs) in 5G mobile communication systems, access network devices or modules of access network devices in Open RAN (ORAN) systems, base stations in future mobile communication systems, or access nodes in WiFi systems. Access network devices can also be modules or units capable of implementing some of the functions of a base station. For example, access network devices can be the central unit (CU), distributed unit (DU), CU-control plane (CP), CU-user plane (UP), or radio unit (RU) described below. In the ORAN system, CU can also be called O-CU, DU can also be called open (O)-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CUP-UP, and RU can also be called O-RU. The access network equipment can be a macro base station, micro base station, indoor station, relay node, donor node, or a wireless controller in a cloud radio access network (CRAN) scenario. Optionally, the access network equipment can also be a server, wearable device, or vehicle-mounted equipment, etc. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). Multiple access network equipment in the communication system can be base stations of the same type or different types. Base stations can communicate with terminals or through relay stations. Terminals can communicate with multiple base stations in different access technologies. The embodiments of this application do not limit the specific technology or equipment form used in the access network equipment.

[0163] The UE in this application embodiment can also be referred to as: terminal device, station, mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user equipment, etc.

[0164] A UE can be a device that provides voice / data connectivity to a user, such as a handheld device or vehicle-mounted device with wireless connectivity. Currently, examples of terminals 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 with cloud gaming capabilities, wireless terminals in self-driving vehicles, 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, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks, or future public land mobile communication networks. Terminal devices in a network (PLMN), etc., are not limited to this in the embodiments of this application.

[0165] By way of example and not limitation, in this embodiment, the UE can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices worn directly on the body or integrated into a user's clothing or accessories. Wearable devices are not merely hardware devices; they achieve powerful functions through software support, data interaction, and cloud interaction. Broadly defined, wearable smart devices include those with comprehensive functions, large size, and the ability to perform complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those focused on a specific application function that require interaction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0166] Furthermore, in this embodiment, the UE can also be a terminal device in an Internet of Things (IoT) system. IoT is an important component of future information technology development, and its main technical feature is connecting objects to networks through communication technologies, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection. The embodiments of this application do not limit the specific technologies or device forms used in the terminal devices.

[0167] In this embodiment, the UE may include a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on top of the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, such as Linux, Unix, Android, iOS, or Windows. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software. Furthermore, this embodiment does not specifically limit the structure of the execution entity of the method provided in this embodiment, as long as it can communicate according to the method provided in this embodiment by running a program that records the code of the method provided in this embodiment. For example, the execution entity of the method provided in this embodiment can be a terminal device, or a functional module in the terminal device that can call and execute a program.

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

[0169] In the embodiments of this application, the communication device with access network device function can be an access network device, or a module (such as a chip, chip system, or software module) in the access network device, or a control subsystem containing access network device function. For example, a control subsystem containing access network device function can be a control center in scenarios where terminals can be applied, such as smart grids, industrial control, intelligent transportation, or smart cities.

[0170] In the embodiments of this application, the communication device with terminal functionality can be a terminal, a module within a terminal (such as a chip, chip system, modem, or software model), or a device that includes terminal functionality. For ease of description, the following description will use a terminal or UE as an example.

[0171] Communication between access network devices and terminal devices can follow a specific protocol layer structure. For example, this protocol layer structure may include a control plane protocol layer structure and a user plane protocol layer structure. For instance, the control plane protocol layer structure may include at least one of the following: radio resource control (RRC) layer, packet data convergence protocol (PDCP) layer, radio link control (RLC) layer, media access control (MAC) layer, or physical (PHY) layer. Similarly, the user plane protocol layer structure may include at least one of the following: service data adaptation protocol (SDAP) layer, PDCP layer, RLC layer, MAC layer, or physical layer.

[0172] Figure 3 is a schematic diagram of an access network device. As an implementation example, as shown in Figure 3, the access network device may include at least one CU and at least one DU. This design can be referred to as CU and DU separation. One CU can be connected to one or more DUs. CU and DU can be separated according to the protocol layer of the wireless network: for example, the functions of the PDCP layer and above (e.g., RRC layer and SDAP layer, etc.) are set in the CU, and the functions of the protocol layers below the PDCP layer (e.g., RLC layer, MAC layer, and PHY layer, etc.) are set in the DU; or, for another example, the functions of the protocol layers above the PDCP layer are set in the CU, and the functions of the protocol layers below the PDCP layer are set in the DU, without limitation. When the CU includes CU-CP and CU-UP, CU-CP is used to implement the control plane functions of the CU, and CU-UP is used to implement the user plane functions of the CU. For example, when the CU is configured to implement the functions of the PDCP layer, RRC layer, and SDAP layer, CU-CP is used to implement the RRC layer functions and the PDCP layer control plane functions, and CU-UP is used to implement the SDAP layer functions and the PDCP layer user plane functions. This application does not limit the names of CU and DU. The above division of CU and DU processing functions according to the protocol layer is just one example; other methods can also be used.

[0173] The CU can be connected to the core network. Optionally, the CU can have some of the functions of the core network.

[0174] Furthermore, some functions of the DU can be separated. As shown in Figure 3, this function can be implemented by a radio unit (RU). The RU can have radio frequency (RF) functionality. This application does not limit the name of the RU. The DU and RU can be split or separated at the PHY layer. For example, the DU can implement higher-level functions in the PHY layer, and the RU can implement lower-level functions in the PHY layer, or implement both lower-level functions and RF functions. Higher-level functions in the PHY layer include functions closer to the MAC layer, and lower-level functions in the PHY layer include functions closer to the RF layer. For example, higher-level functions in the PHY layer include one or more of the following: forward error correction (FEC) encoding / decoding, scrambling, or modulation / demodulation. Lower-level functions in the PHY layer include one or more of the following: fast Fourier transform (FFT) / inverse fast Fourier transform (IFFT), beamforming, or extraction and filtering of the physical random access channel (PRACH), etc. The RU can communicate with the terminal device via the air interface using RF signals. The pre-coding function of the PHY layer code can be located in the DU or the RU. The separation between the DU and RU can be done in various ways without restriction. An interface exists between the DU and RU. For example, depending on the separation method, the interface between the DU and RU can be a Common Public Radio Interface (CPRI) interface or an Enhanced Common Public Radio Interface (eCPRI) interface.

[0175] Optionally, any one of CU, CU-CP, CU-UP, DU, and RU can be a software module, a hardware structure, or a combination of software and hardware structures, without limitation. The different entities can exist in the same or different forms. For example, CU, CU-CP, CU-UP, and DU are software modules, and RU is a hardware structure. For the sake of brevity, all possible combinations are not listed here. These modules and the methods they execute are also within the protection scope of the embodiments of this application. For example, when the method of the embodiments of this application is executed by an access network device, it can be specifically executed by at least one of CU, CU-CP, CU-UP, DU, or RU.

[0176] The solution provided in this application will be described in detail below with reference to the corresponding flowcharts. It is understood that the illustrative flowcharts provided in this application mainly use different devices (e.g., a first device, a first network device, or a second network device) as examples of the execution subjects of the interaction to illustrate the method, but this application does not limit the execution subjects of the interaction. For example, the device in the illustrative flowchart (e.g., a first device, a first network device, or a second network device) can also be a chip, chip system, or processor that supports the implementation of the method on that device, or it can be a logic module or software that can implement all or part of the functions of that device. It is uniformly stated here that the message or signaling interactions involved in the interaction flow of the embodiments of this application can adopt standard messages or signaling, or they can be newly introduced messages or signaling; the embodiments of this application do not specifically limit this.

[0177] For ease of description, the following description uses an example where the first device is a first-environment Internet of Things (AIoT) device. Figure 4 is an example flowchart of a communication method according to an embodiment of this application. As shown in Figure 4, the method includes:

[0178] Step 410: The first network device sends first information to the first environment AIoT device. The first information is used to indicate a device identifier, which is used to identify the first environment AIoT device. Correspondingly, the first AIoT device receives the first information.

[0179] For a description of the first network device, please refer to the preceding text; for the sake of brevity, it will not be repeated here. For example, the first network device is a gNB, or a reader, or a UE, or a gNB and a UE.

[0180] For clarity, the number of bits occupied by the device identifier in this embodiment is less than the number of bits occupied by the higher-layer identifier of the AIoT device. The higher-layer identifier refers to the identifier assigned to the first AIoT device by the core network or a third party; it can be a temporary or permanent identifier. For example, the number of bits occupied by the device identifier in this embodiment may be a few bits, a dozen bits, or even less; while the higher-layer identifier of the AIoT device is much longer, occupying tens or even hundreds of bits; that is, the number of bits occupied by the two are on different orders of magnitude. Therefore, compared to using the higher-layer identifier of the AIoT device, using the device identifier of this embodiment reduces unnecessary resource waste.

[0181] The device identifier in this application serves to identify AIoT devices, ensuring that data transmission can be performed using the device identifier during subsequent data transmission. This application does not impose specific limitations on the naming of the device identifier. For example, the device identifier can be represented as an access identifier (AS ID) or an access layer identifier.

[0182] This application does not specifically limit the specific form or generation method of the device identifier. Optionally, the device identifier includes one or more of the following:

[0183] A random number of the first preset length;

[0184] The first identifier is one or more of the following: a random number RN16 generated by the first AIoT device, a first random access preamble, and a resource number indicator;

[0185] The second identifier is an identifier generated based on the high-level identifier of the AIoT device.

[0186] Here, the first preset length of random number refers to a random number of a corresponding length generated by the first network device according to a predefined length. For example, the first network device can send the first preset length of random number as a device identifier to the first AIoT device. The preset length can be a length determined by the first network device or defined by the protocol. For clarity, the specific implementation of "predefined" can include any of the following: protocol predefined, manufacturer-specified, defined by the communication device, pre-installed in the communication device at the factory, or agreed upon in advance by other agreed methods.

[0187] The aforementioned first identifier can take several forms. The first identifier can be one or more of the following: a 16-bit random number (which can be represented as RN16) sent by the first AIoT device, a first random access preamble, and a resource number indicator.

[0188] RN16 is generated by the first AIoT device according to a predetermined rule. This application does not limit the specific form of the predetermined rule. For example, the predetermined rule could be a method for generating RN16 in RFID, or other algorithms or rules for generating RN16 by those skilled in the art.

[0189] The first random access preamble is the preamble identifier (or preamble sequence) sent by the first AIoT device during the access process.

[0190] The resource number indication includes a time-domain resource number indication and / or a frequency-domain resource number indication. Optionally, the resource is an access resource of the first AIoT device. For example, the resource number is the number of the access resource selected by the first AIoT device to send message (MSG) 1. Another example is the resource number of the access resource where the first AIoT device receives a service trigger message (e.g., a paging message). Yet another example is the resource number of the first access resource allocated to the first AIoT device. Still another example is the resource number used when allocating an access identifier to the first AIoT device.

[0191] It should be noted that the above examples are provided for ease of understanding and do not constitute a limitation on the embodiments of this application. The resource number can be any combination of the resource numbers in the above examples, and is not limited here.

[0192] The aforementioned second identifier is introduced to describe the identifier generated based on the high-level identifier (or long identifier) ​​of the AIoT device. As mentioned earlier, the high-level identifier of the AIoT device occupies a large number of bits, so in this embodiment, a portion of the bits in the high-level identifier can be used as the device identifier, which can be referred to as the second identifier (or short identifier).

[0193] This application does not limit the specific rules for generating the second identifier. For example, the second identifier may be the first N bits of the higher-level identifier. Or, the second identifier may be the last N bits of the higher-level identifier of the AIoT device. Or, the second identifier may be any N bits of the higher-level identifier.

[0194] For example, the second identifier is N bits obtained by processing N bits at different positions in the higher-level identifier using a certain algorithm or rule. Of course, the embodiments of this application do not specifically limit the algorithm or rule.

[0195] Of course, the second identifier is unique under the first network device, that is, the second identifier corresponds to the first AIoT device, and the first network device will not assign the second identifier to other AIoT devices at the same time.

[0196] In the above example, N in "N bits" is an integer greater than 0. The specific value of N can be selected based on the implementation, and this application embodiment does not limit the specific value of N. For example, N can be 8 or 16.

[0197] It should be understood that the examples of device identifiers described above are merely illustrative and the embodiments of this application are not limited thereto. Optionally, the device identifier may also include information related to the first network device.

[0198] Optionally, the device identifier may also include the identifier of the first network device or a portion thereof. For example, the device identifier may also include a reader ID.

[0199] The aforementioned first information is sent by the first network device and is used to indicate the device identifier. The first information can have different forms of representation. The first information used to indicate the device identifier can be an explicit indication or an implicit indication, without specific limitations. Alternatively, the first information can directly or indirectly include the device identifier.

[0200] Optionally, the first information includes one or more of the following: reuse instruction information, allocation instruction information, and device identifier.

[0201] The reused indication information is used to indicate that the first identifier and / or the second identifier are used as device identifiers. For an explanation of the first and second identifiers, please refer to the preceding description; for the sake of brevity, it will not be repeated here.

[0202] The assignment indicator (AI) information is used to instruct the first network device to assign a device identifier. The assignment indicator information can be understood as the first network device assigning a new device identifier to the first AIoT device.

[0203] Optionally, the first information may also include message type and / or resource indication information. The message type is used to indicate one or more of the following: whether the message body containing the first information or the first information itself contains the allocation of a device identifier. The resource indication information is used to indicate the transmission resources used for the current transmission of R2D data and / or the subsequent transmission of D2R data, specifically including time-domain resources and / or frequency-domain resources.

[0204] Optionally, the first information may also include: the allocation method of the device identifier; and the length (or number of bits) of the device identifier.

[0205] This application does not limit the specific implementation method of allocating device identifiers for the first network device. The first information can be carried in any R2D data packet or R2D message. For example, the first information can be carried in a paging message or MSG2.

[0206] Taking MSG2 as an example, the first network device can send MSG2 for one or more AIoT devices, and the MSG2 includes a device identifier for each of the one or more AIoT devices. The message body structure of MSG2 is described below with reference to Figures 5A to 5G.

[0207] As shown in Figure 5A, MSG2 includes a 16-bit random number RN16 for each of multiple AIoT devices. These RN16s can be understood as follows: when the first network device receives RN16s from multiple AIoT devices (e.g., carried in MSG1), it will include some or all of the RN16s from each AIoT device in its reply to MSG2. Correspondingly, for the AIoT device that receives the MSG2 sent by the first network device, the RN16 is used as the device identifier, or in other words, the RN16 is reused as the device identifier. The MSG2 format shown in Figure 5A indicates that the first network device instructs the AIoT devices to reuse the device identifier; that is, the specific form of the device identifier is RN16.

[0208] For clarity, this application does not specify the exact number of RN16 included in MSG2; the specific number may vary depending on the actual application. The RN16 shown in Figures 5A to 5G are merely illustrative examples.

[0209] Optionally, the message body shown in Figure 5A may also include a message type, which may indicate whether MSG2 includes the allocation of a device identifier; the allocation method of the device identifier; and the length (or number of bits) of the device identifier.

[0210] Optionally, the message body shown in Figure 5A may also include resource indication information. This resource indication information can be used to indicate the transmission resources allocated by the first network device to the AIoT device.

[0211] As shown in Figure 5B, MSG2 includes 16-bit random numbers RN16 for multiple AIoT devices, and a bitmap for device identification (AS ID). The number of bits in the bitmap corresponds to the number of AIoT devices, and the value of each bit indicates whether an AIoT device reuses RN16. In other words, all reuse indication information for multiple AIoT devices is represented by a single bitmap. For example, assuming a bit with a value of 1 represents reusing RN16 and a bit with a value of 0 represents not reusing RN16, the bitmap for four AIoT devices is 1101. This can be interpreted as the first, second, and fourth AIoT devices reusing their respective RN16 as device identifiers, while the third AIoT device does not reuse RN16.

[0212] Optionally, the message body shown in Figure 5B may also include a message type. A description of message types can be found above and will not be repeated here.

[0213] As shown in Figure 5C, MSG2 includes a 16-bit random number RN16 for multiple AIoT devices, and an allocation indicator AI for each AIoT device. That is, the device identifier of each AIoT device can be determined through the corresponding allocation indicator AI. It should be noted that, as one possible implementation, AI can indicate not only newly allocated device identifiers but also reused device identifiers; in other words, one way to implement reuse indication information is through the value of the bits in the allocation indicator AI. For example, when AI is 1 bit, AI = 0 represents reusing RN16 as the AS ID, meaning the AIoT device corresponding to RN16 uses RN16 as its AS ID; AI = 1 represents AI followed by a newly allocated AS ID. It should be understood that the meanings of AI values ​​"0" and "1" here are merely examples, and in practice, their meanings can be interchanged; no specific limitation is made.

[0214] Similarly, the message body shown in Figure 5C can also include a message type. A description of message types can be found above and will not be repeated here.

[0215] As shown in Figure 5D, MSG2 includes a 16-bit random number RN16 for multiple AIoT devices, and the AS ID for each AIoT device. The AIoT device corresponding to RN16 uses this ASID as its device identifier for subsequent data transmission. It should be noted that in this method, if the ASID is a specific value, such as all 0s or all 1s, it means that the AIoT device corresponding to RN16 has no ASID. Similarly, the message body shown in Figure 5D can also include a message type. A description of message types can be found above and will not be repeated here.

[0216] As shown in Figure 5E, MSG2 includes 16-bit random numbers RN16 for multiple AIoT devices, an allocation indicator (AI) for each AIoT device, and an AS ID for each AIoT device. The AI ​​field also serves to indicate whether an AS ID field exists following the AI ​​field. When the AI ​​field uses different numbers of bits, its corresponding value can have different meanings.

[0217] When AI is 2 bits, there are four possible values ​​for AI, each representing a different meaning. See Table 1 below for reference:

[0218] In the case where AI is 10, the allocated AS ID in MSG2 can be located anywhere after AI, without specific limitation. For example, the 16 bits after AI represent the newly allocated AS ID. It should be understood that Table 1 above is merely an example, and the embodiments of this application are not limited to it. In fact, the number of bits in AI, the meaning represented by the value, etc., can all be implemented in other ways. For example, when AI is 1 bit, AI = 0 represents reusing RN16 as the AS ID, and AI = 1 represents including a newly allocated AS ID after AI.

[0219] The message body of MSG2 shown in Figure 5E above can not only indicate the reuse of RN16 as AS ID, but also reallocate AS ID, making the implementation more flexible; and when the value of AI indicates that no AS ID has been allocated, the AS ID field after AI can be omitted, which can save bits or overhead to a certain extent.

[0220] The message body of MSG2 shown in Figure 5F is similar to that shown in Figure 5E, containing similar content. The difference is that the content in the message body shown in Figure 5F is ordered from left to right, rather than from top to bottom as shown in Figure 5E.

[0221] The message body of MSG2 shown in Figure 5G includes the number of allocated AS IDs and / or the number of acknowledgment messages. The number of allocated AS IDs indicates the total number of AS IDs allocated in MSG2. The number of acknowledgment messages indicates the number of RN16s that can be reused as AS IDs or no AS IDs need to be allocated. Based on the message body shown in Figure 5G, the first network device can indicate the allocation of AS IDs and the reuse of AS IDs separately.

[0222] It should be noted that in the examples of Figures 5C, 5E and 5F above, AI-related instructions can be included in the message body of MSG2, or partially or entirely in the Layer 1 control signaling, without any limitation here.

[0223] The preceding text described various scenarios where the first information is used to indicate a device identifier. Furthermore, device identifiers can also have a time limit. From a time limit perspective, device identifiers can be categorized as single-use or reusable (or long-term use). Further, the validity period or invalidity period of the device identifier can be agreed upon, or the amount of data transmitted using the device identifier or the number of data packets can be agreed upon to describe the time limit of the device identifier. Regarding various time limit information for device identifiers, the first network device can indicate this through the first information when allocating device identifiers, or it can indicate it through separate messages or information cells; no specific limitation is made in this regard.

[0224] Taking the first information as an example of indicating the timeliness information of the device identifier, the first information is also used to indicate one or more of the following: the type of device identifier; validity information; invalid information.

[0225] Optionally, the types of device identifiers include: one-shot device identifiers (one-shot AS ID); and long-term device identifiers (long-term AS ID).

[0226] A one-time-use device identifier can only be used for one round, or in other words, it is applicable to one round of data transmission. For example, the device identifier assigned by the first network device to the first AIoT device can only be used in this round of data transmission; after this round of data transmission ends or in the next round of data transmission, the assigned device identifier becomes unavailable. Here, one round of data transmission refers to the data transmission duration or the number of data packets required to complete this A-IoT service. Taking AIoT service inventory as an example, one round of data transmission can include the first network device sending inventory and the first device responding with inventory. Taking command as an example, one round of data transmission can refer to the period from the first network device receiving the first command sent by the second network device to the first R2D data transmission, until the first network device receives the response to that command.

[0227] It should be noted that the specific definition of a round of data transmission can depend on the specific business logic. Furthermore, the timing of ASID activation may not necessarily be the start of a round of data transmission.

[0228] Alternatively, a round of data transmission can also be characterized by the number of predefined data packets transmitted, for example: n R2D and / or m D2R transmissions constitute one round; or p R2D+D2R transmissions constitute one round; where m, n, and p are all integers greater than 0.

[0229] Alternatively, in addition to the implementation methods described above, the energy state of the first device can also be considered as a factor in a round. For example, during the validity period of the ASID, if the energy consumption of the first device cannot support the completion of this round of data transmission, or if the energy of the first device cannot support continued data transmission, the ASID may become invalid.

[0230] Long-term used device identifiers refer to device identifiers that can be reused multiple times or used for a relatively long period of time. For example, a device identifier assigned by a first network device to a first AIoT device is not only usable in the current data transmission, but also stored by both the first network device and the first AIoT device after the data transmission is completed, and will continue to use the device identifier in the next round or the next data transmission.

[0231] The validity information is used to indicate the first duration that the first AIoT device can use, and / or, the amount of data or data packets that the first AIoT device can use to transmit the device identifier. The first duration can be understood as the valid duration for which the first AIoT device can use the device identifier.

[0232] The amount of data that the first AIoT device can transmit using its device identifier can be understood as: the amount of data that the first AIoT device can transmit using its device identifier within a certain data volume threshold; when the data volume threshold is exceeded, the device identifier becomes invalid. Optionally, this data volume is the amount of data transmitted via D2R. And / or, the number of data packets that the first AIoT device can transmit using its device identifier can be understood as: the number of data packets that the first AIoT device can transmit using its device identifier within a certain number threshold; when the number of data packets is exceeded, the device identifier becomes invalid. Optionally, this number of data packets is the number of data packets transmitted via D2R.

[0233] It should be noted that when configuring multiple validity information, the validity of the ASID can be determined by either the "data volume threshold" or the "data packet number threshold"; or, the validity can be determined by satisfying both the "data volume threshold" and the "data packet number threshold".

[0234] Invalidity information is used to indicate that a device identifier is invalid. Invalidity information can be understood as describing the validity of a device identifier from another perspective. Optionally, invalidity information includes one or more of the following: second duration information, packet count information, and first energy information.

[0235] The second duration information indicates that the device identifier should be released if no data is transmitted within the second duration. The data packet count information indicates that the device identifier should be released after a preset number of AIoT data packets have been transmitted.

[0236] The first energy information is used to indicate when the energy of the first AIoT device meets a preset condition for releasing the device identifier. For example, the device identifier is released when the energy of the first AIoT device is less than an energy threshold.

[0237] Therefore, the first network device can also use the first information to indicate the timeliness of the device identifier, so as to make reasonable use of the device identifier and improve resource utilization.

[0238] In step 420, the first AIoT device sends second information, which is used to request or confirm the device identifier. Correspondingly, the first network device receives the second information.

[0239] It should be noted that the execution order of steps 410 and 420 is not specifically limited in this embodiment of the application; steps 420 and 410 shown in Figure 4 are merely examples. For instance, step 410 may be executed first, followed by step 420. Alternatively, step 420 may be executed first, followed by step 410. The order of steps 410 and 420 can correspond to different interaction flows. These will be described in detail below with reference to Figures 6A and 7.

[0240] The first AIoT device can send second information to the first network device if preset conditions are met.

[0241] Optionally, step 420 includes: the first AIoT device sending second information when one or more of the following conditions are met: the first AIoT device has the ability to use a device identifier; the data to be transmitted by the first AIoT device meets preset conditions; the energy of the first AIoT device meets an energy threshold value; the first AIoT device supports data segmentation function; the first AIoT device needs to perform segmentation processing on the uplink data.

[0242] In some embodiments, the first AIoT device has the ability to use a device identifier, including: the first AIoT device supports the allocation of a device identifier (e.g., AS ID); the first AIoT device supports the use of a device identifier (e.g., AS ID); the first AIoT device supports available or unavailable information provided by the network; the first AIoT device supports establishing a connection with the network side (e.g., a first network device), etc. The available or unavailable information indicates the time period during which the first AIoT device and the network device can synchronously transmit data, facilitating smooth data transmission. For example, available information indicates that the network device will send data; the first AIoT device supporting available information provided by the network indicates that the first AIoT device can receive data sent by the network device; unavailable information indicates the time period during which the network device will not transmit data.

[0243] In some embodiments, the data to be transmitted by the first AIoT device meets preset conditions, including: the amount of data to be transmitted by the first AIoT device is greater than or equal to a first threshold value; and / or, the number of data packets to be transmitted by the first AIoT device is greater than or equal to a second threshold value.

[0244] The first threshold value and / or the second threshold value can be predefined or sent by the network device (first network device or second network device), and there is no specific limitation on this. For example, the first network device sends the first threshold value and / or the second threshold value to the AIoT device in the R2D data.

[0245] In some embodiments, the energy of the first AIoT device meets an energy threshold, including: the energy of the first AIoT device is greater than or equal to the energy threshold. The purpose of introducing "the energy of the first AIoT device meets an energy threshold" is to ensure that the energy of the first AIoT device is sufficient to support subsequent data transmission using the device identifier.

[0246] This application does not specifically limit the method of determining the energy threshold or its specific value. The energy threshold can be predefined or sent by the network device (first network device or second network device), and there is no specific limitation on this. For example, the first network device sends an energy threshold of 90% to the AIoT device in R2D data.

[0247] For example, the first AIoT device supporting data segmentation means that the first AIoT device has the function of data segmentation. That is, when the data packet to be transmitted is relatively large, the data segmentation function can divide the data packet into multiple smaller data packets for transmission.

[0248] For example, the first AIoT device needs to perform segmentation processing on the uplink data, which can be understood as the first AIoT device needs to perform data segmentation on the D2R data in order to divide the D2R data into small data packets for transmission.

[0249] It should be understood that the conditions shown above are merely illustrative examples, and the embodiments of this application are not limited thereto. For example, in different interaction processes, the first AIoT device may further satisfy one or more conditions corresponding to the interaction process.

[0250] For example, in the case where the second information is used to confirm the device identifier, the information sent by the first AIoT device includes: sending the second information after the first AIoT device receives the first information sent by the first network device.

[0251] This application does not limit the form or specific content of the second information in its embodiments. Optionally, the second information may be one or more of the following: device identifier allocation request indication information, device identifier confirmation indication information, device identifier, first random number RN16, first preamble sequence, data segmentation indication information, energy indication information of the first AIoT device, amount of data to be transmitted indication information, number of data packets to be transmitted indication information, and capability indication information of environmental IoT services.

[0252] It should be noted that the purpose of the second piece of information is for the first AIoT device to request the first network device to assign a device identifier, or to confirm the device identifier assigned by the first network device. Both the "request" and "confirmation" can be implemented explicitly or implicitly.

[0253] For example, the second information is a device identifier allocation request indication information; the first AIoT device sends the device identifier allocation request indication information in order to request the first network device to allocate a device identifier.

[0254] For example, the second information is a device identification confirmation instruction; the first AIoT device sends the device identification confirmation instruction to confirm the device identification assigned by the first network device.

[0255] For example, the second piece of information is the device identifier; the first AIoT device can send the device identifier assigned by the first network device back to the first network device in order to confirm the device identifier assigned by the first network device.

[0256] For example, the second piece of information is the first random number RN16; the first AIoT device can send the first random number RN16 it generates to the first network device to indirectly request or confirm the device identifier.

[0257] For example, the second information is the first preamble sequence; the first AIoT device can send the first preamble sequence as request information to the first network device to indirectly request the device identifier or confirm the device identifier.

[0258] For example, the second information is data segmentation indication information; the first AIoT device sends the amount of data to be transmitted indication information, which indicates that it has the data segmentation function or needs to segment the data to be transmitted, so as to indirectly request device identification or confirm device identification.

[0259] For example, the second information is the amount of data to be transmitted indication information; the first AIoT device sends the amount of data to be transmitted indication information to indirectly request or confirm the device identification by indicating that its amount of data to be transmitted exceeds the first threshold value.

[0260] For example, the second information is the number of data packets to be transmitted; the first AIoT device sends data segmentation indication information, which indicates that the number of data packets to be transmitted by itself exceeds the second threshold, thereby indirectly requesting device identification or confirming device identification.

[0261] For example, the second piece of information is capability indication information for environmental IoT services; the first AIoT device sends capability indication information to indirectly request or confirm the device identifier by indicating that it has the ability to use the device identifier.

[0262] It is understandable that once the device identifier of the first AIoT device is determined, the device identifier can be used to indicate the first AIoT device and achieve data scheduling when data is transmitted between the first AIoT device and the network device.

[0263] Optionally, in step 430, the first AIoT device and the first network device transmit data based on the device identifier.

[0264] In this embodiment, by determining (e.g., assigning) a device identifier for the first environment's AIoT device, the first AIoT device can be identified using the device identifier, facilitating scheduling during subsequent data transmission. Furthermore, compared to using a higher-level identifier for the AIoT device, the device identifier in this embodiment helps save resources.

[0265] As mentioned above, the second information is used to request or confirm the device identifier, and accordingly, the timing of the first AIoT device sending the second information can be implemented in different ways.

[0266] Referring to FIG6A, FIG6A illustrates an interactive example of a communication method according to an embodiment of this application. FIG6A is introduced to describe the implementation method in which a first network device actively assigns a device identifier to a first AIoT device. In FIG6A, the second information is confirmation information. As shown in FIG6A, the communication method includes at least the following steps:

[0267] Step 610: The first network device sends first information to the first AIoT device. Correspondingly, the first AIoT device receives the first information.

[0268] The relevant description of step 610 (such as the first information) can be found in the description of step 410 in Figure 4 above, and will not be elaborated here.

[0269] For example, the first information is a device identifier and / or a sending confirmation instruction. The sending confirmation instruction can be understood as a cell in the first information, which is used to instruct the first AIoT device to send confirmation information upon receiving the first information.

[0270] The first piece of information can be an allocation message. This application does not specifically limit the form of the allocation message. Optionally, the allocation message is an R2D message. For example, the allocation message is a paging message or MSG2.

[0271] Step 620: The first AIoT device sends confirmation information (i.e., second information, used to confirm the use of the device identifier assigned by the first network device) to the first network device. Correspondingly, the first network device receives the confirmation information.

[0272] Step 620 is performed after step 610. The confirmation information is used to confirm the device identifier assigned by the first network device. The confirmation information can be an example of the second information. For a description of the second information, please refer to the description of step 420 above; for the sake of brevity, it will not be elaborated here.

[0273] It should be noted that confirmation messages can be sent separately or included in a Layer 1 command (L1 commend), and there are no specific restrictions on this.

[0274] For example, the paging message sent by the first network device includes a confirmation instruction. After receiving the paging message, the first AIoT device can send confirmation information to the first network device.

[0275] For example, the allocation message sent by the first network device is an R2D message; correspondingly, the confirmation information sent by the first AIoT device is carried in a D2R message, which is a D2R message following the aforementioned R2D message.

[0276] For example, the allocation message sent by the first network device is a paging message; correspondingly, the acknowledgment information sent by the first AIoT device is carried in MSG1 or MSG3 or other D2R data. If the acknowledgment information sent by the first AIoT device is carried in MSG1, then this acknowledgment information can be part or all of the first RN16 and / or the first preamble sequence. The first RN16 and the first preamble sequence are RN16 and preamble sequences used for device identification acknowledgment, that is, the first RN16 and the first preamble sequence can serve as a device identifier.

[0277] For example, the allocation message sent by the first network device is MSG2; correspondingly, the confirmation information sent by the first AIoT device is carried in MSG3.

[0278] Figure 6B illustrates an example format of the confirmation message. As shown in Figure 6B, the confirmation message includes the message type, AI ID confirmation information, and a Network Access Stratum Protocol Data Unit (NAS PDU). The AI ​​ID confirmation information includes the assigned AS ID and / or the AS ID confirmation indicator.

[0279] It should be understood that the embodiments of this application do not specifically limit the form of the confirmation information. The confirmation information may be the message body or information elements in the message, and there is no specific limitation on this.

[0280] For clarity, the D2R data and R2D data used in the embodiments of this application are a general term or overview of the data (such as data packets) and / or messages (or signaling) transmitted between network devices and AIoT devices, but do not limit the specific form of the data. For example, D2R data and R2D data can be represented as protocol data units, control units, etc. Furthermore, all content sent from AIoT devices to network devices, regardless of whether it is in the form of data packets, messages, or signaling, is collectively referred to as D2R data; or, all content sent from network devices to AIoT devices, regardless of whether it is in the form of data packets, messages, or signaling, is collectively referred to as R2D data.

[0281] To put it another way, for example, the data transmitted between network devices and AIoT devices is messages (or signaling), and D2R data and R2D data can be specifically referred to as D2R messages and R2D messages, respectively. The data transmitted between network devices and AIoT devices is data packets, and D2R data and R2D data can be specifically referred to as D2R data packets and R2D data packets, respectively. Of course, network devices and AIoT devices may transmit both data packets and messages simultaneously, in which case it can be described as D2R data and R2D data.

[0282] Optionally, after receiving the confirmation information, the first network device may use the device identifier for data transmission during subsequent communication with the first AIoT device.

[0283] Based on the method shown in Figure 6A, the first network device can proactively assign a device identifier to the first AIoT device. Thus, if no confirmation message is received from the first AIoT device, or if the received confirmation message indicates that the first AIoT device does not support the device identifier, the first network device will not use the device identifier for data transmission with the first AIoT device and can reclaim the invalid device identifier.

[0284] Referring to Figure 7, Figure 7 illustrates another example of communication interaction according to an embodiment of this application. Figure 7 is introduced to describe the implementation of a first network device assigning a device identifier based on a request from a first AIoT device. The difference from Figure 6A is that the first network device sends the first information after receiving the request information from the first AIoT device. In Figure 7, the second information is the request information. As shown in Figure 7, the communication method includes at least the following steps:

[0285] Step 710: The first AIoT device sends request information (i.e., the second information) to the first network device. Correspondingly, the first network device receives the request information.

[0286] The request information is one implementation of the second information in step 420. The request information is used to request the first network device to allocate a device identifier. For example, the request information is an AS ID assignment request. Optionally, the request information is carried in a D2R message or an L1 commendation.

[0287] For example, the request information sent by the first AIoT device is carried in MSG1. This request information may be part or all of the first RN16 and / or the first preamble sequence. That is, the first network device is requested to allocate a device identifier through part or all of the first RN16 and / or the first preamble sequence.

[0288] Step 720: The first network device sends first information to the first AIoT device. Correspondingly, the first AIoT device receives the first information.

[0289] For example, the first information includes a device identifier assigned by the first network device to the first AIoT device. After the first network device assigns the device identifier to the first AIoT device, the first network device can subsequently use the device identifier to transmit data with the first AIoT device.

[0290] Based on the process shown in Figure 7, the first network device can assign a device identifier to the first AIoT device according to the request of the first AIoT device. For example, assigning a device identifier according to the capabilities of the first AIoT device helps to reduce unnecessary identifier allocation.

[0291] This application also provides another communication method. A first network device indicates its ability to assign device identifiers to an AIoT device, enabling the AIoT device to request a device identifier from the first network device. Subsequently, the first network device assigns a device identifier to the AIoT device based on the AIoT device's request. As shown in Figure 8, this includes at least the following steps:

[0292] In step 810, the first network device sends first information, which indicates the capability to allocate device identifiers. Correspondingly, the first AIoT device receives the first information.

[0293] The difference between the first information in step 810 and the first information mentioned earlier is that the purpose of the first information here is to indicate that the first network device has the ability to assign device identifiers, rather than actually indicating the device identifier. The first network device assigns a device identifier to the AIoT device in step 830 below, that is, after the first network device receives the request information from the first AIoT device.

[0294] Step 820: The first AIoT device sends second information to the first network device, the second information being used to request a device identifier (or, in other words, to request the first network device to assign a device identifier). Correspondingly, the first network device receives the second information.

[0295] Regarding the second piece of information, please refer to the previous description of how the second piece of information is used to request device identification.

[0296] Step 830: The first network device sends third information to the first AIoT device. The third information includes a device identifier assigned by the first network device. Optionally, the third information may also include a reuse indication. A description of the reuse indication can be found above, and for the sake of brevity, it will not be repeated here.

[0297] For details on the specific implementation of device identification, please refer to the previous description. For the sake of brevity, it will not be elaborated here.

[0298] The preceding text described different implementation methods for the first network device to allocate device identifiers: proactive allocation of device identifiers or allocation of device identifiers based on a request from the first AIoT device. For the first network device, it can determine how to allocate device identifiers based on auxiliary information sent by the second network device.

[0299] Figure 9 illustrates another interactive diagram of the communication method according to an embodiment of this application. Exemplarily, the first network device shown in Figure 9 is an access network device or a reader; the second network device is a core network device. As shown in Figure 9, the method includes at least the following steps:

[0300] Step 910: The second network device sends auxiliary information to the first network device, the auxiliary information being used to assign a device identifier to the first AIoT device. Correspondingly, the first network device receives the auxiliary information.

[0301] This application does not specifically limit how the second network device obtains auxiliary information. For example, the auxiliary information may be reported to the second network device by other network elements, or it may be predefined, or it may be sent to the core network device during the subscription process; no specific limitation is made in this regard.

[0302] The auxiliary information can be used to assist the first network device in confirming whether the first AIoT device can be assigned a device identifier, and / or to assist the first network device in how to assign a device identifier.

[0303] It should be noted that the embodiments of this application do not specifically limit the message or signaling in which the above-mentioned auxiliary information is contained. The auxiliary information can be carried in existing messages or signaling, or it can be a newly defined message or signaling. For example, the auxiliary information can be included in Next Generation Application Protocol (NGAP) messages or signaling. NGAP is an application layer protocol used for communication between NG-RAN and AMF in 5GC in 5G networks. For instance, NGAP signaling provides signaling services between AMF and NG-RAN.

[0304] For example, auxiliary information is carried in one or more of the following signaling: initial context establishment, registration signaling, non-access stratum (NAS) transmission messages, paging messages, messages in session management procedures, messages in UE context management procedures (including context establishment, modification, release, etc.), etc.

[0305] Optionally, the auxiliary information includes one or more of the following: capability information of the first AIoT device, service type of the first AIoT device, energy status of the first AIoT device, second identifier, and device identifier allocation information.

[0306] The capability information of the first AIoT device includes capability indication information for data segmentation and / or capability indication information for using a device identifier. The capability indication information for data segmentation can be understood as the first AIoT device supporting the data segmentation function. A description of the data segmentation function can be found above. The capability indication information for using a device identifier can be understood as the first AIoT device having the capability to use a device identifier. A description of the capability to use a device identifier can be found above.

[0307] The service type of the first AIoT device includes the size of the data to be transmitted and / or the number of data packets to be transmitted. The data to be transmitted includes the amount of data to be transmitted in D2R and / or R2D scenarios, or the number of data packets. For example, the first network device can know the size of the data to be transmitted and / or the number of data packets to be transmitted in the first AIoT device and decide whether to assign it a device identifier. Alternatively, the service type of the first AIoT device may also include other types of AIoT services such as Inventory and Command.

[0308] The energy state of the first AIoT device includes the charging method, etc. Optionally, the energy state may include the first AIoT device's battery level (e.g., 90% battery), energy storage status, or charging completion, etc. For example, the first network device can decide whether to assign a device identifier to the first AIoT device based on its energy state. Optionally, the charging method may include charging that is perceptible to the first network device or charging that is imperceptible to the first network device. Perceptible charging means that the first network device can obtain information such as the timing and / or completion of charging of the first AIoT device. Conversely, imperceptible charging means that the charging process of the first AIoT device is not perceived by the first network device.

[0309] The second identifier is an identifier generated based on the higher-level identifier of the AIoT device. Optionally, the device identifier is generated based on the higher-level identifier of the AIoT device.

[0310] The aforementioned device identifier allocation information is used to determine the device identifier. Optionally, the device identifier allocation information includes one or more of the following: a second preset length and a first bit range.

[0311] The second preset length is the length of the device identifier generated based on some or all of the bits of the AIoT device's higher-layer identifier. For example, the second preset length is 16 bits; the device identifier is a 16-bit device identifier generated based on some or all of the bits of the AIoT device's higher-layer identifier according to a preset algorithm or generation rule. For example, the first network device can instruct the first AIoT device to generate a device identifier of the second preset length.

[0312] The first bit range is the bit range of the device identifier generated based on some or all of the bits of the higher-layer identifier of the AIoT device. For example, the second preset length is the last N bits; the device identifier is the last N bits of some or all of the bits of the higher-layer identifier of the AIoT device. Of course, this is only an example of the last N bits, and the embodiments of this application are not limited thereto. For example, the first network device can instruct the first AIoT device to generate a device identifier with the first bit range.

[0313] Step 920: The first network device sends first information to the first AIoT device. Correspondingly, the first AIoT device receives the first information.

[0314] For further description of the first information, please refer to the description in step 410 above. For the sake of brevity, it will not be repeated here.

[0315] Optionally, step 920 includes: the first network device sending first information to the first AIoT device based on auxiliary information.

[0316] For example, for AIoT devices that have the ability to use device identifiers, the first network device assigns a device identifier to the AIoT device; for AIoT devices that do not have the ability to use device identifiers, the first network device does not assign a device identifier.

[0317] It should be noted that the first information in step 920 may also include some or all of the auxiliary information in step 910.

[0318] Based on the process shown in Figure 9, the second network device can assist the first network device in assigning appropriate device identifiers to the AIoT devices by sending auxiliary information. This ensures that the device identifiers are synchronized between the network device and the AIoT devices, enabling the correct device identifiers to be used in subsequent data transmission and helping to save resources on the AIoT air interface. Furthermore, the first network device can quickly release device identifiers that are unusable by the AIoT devices, thereby improving the efficiency of device identifier utilization.

[0319] Figure 10 illustrates another interaction diagram of the communication method according to an embodiment of this application. Figure 10 is introduced to describe how a first AIoT device reports the device identifier it uses. As shown in Figure 10, the method includes at least the following steps:

[0320] In step 1010, the second network device sends auxiliary information to the first network device. Correspondingly, the first network device receives the auxiliary information. For an explanation of step 1010, please refer to the description of step 910; it will not be repeated here.

[0321] Step 1020: The first network device sends first information to the first AIoT device. Correspondingly, the first AIoT device receives the first information.

[0322] Optionally, the first information is used to instruct the first AIoT device to use or report a device identifier.

[0323] It should be noted that the first information in step 1020 may include some or all of the auxiliary information in step 1010.

[0324] In other words, for security reasons, the first network device may not know the specific content of the higher-layer identifier of the AIoT device, but it can instruct the first AIoT device to use certain bits of the higher-layer identifier; or it can instruct the first AIoT device to report the device identifier it uses. After determining the device identifier, the first AIoT device can report the device identifier to the first network device so that the first network device can know the device identifier. This ensures that the first network device and the first AIoT device have a consistent understanding of the device identifier, thereby facilitating subsequent data transmission based on the device identifier.

[0325] For further description of the first information, please refer to the description in step 410 above. For the sake of brevity, it will not be repeated here.

[0326] Step 1030: The first AIoT device sends second information to the first network device. Correspondingly, the first network device receives the second information. Optionally, the second information includes a device identifier determined by the first AIoT device.

[0327] In other words, the first AIoT device can report its device identifier to the first network device. In this way, the first network device can also know the device identifier used by the first AIoT device, and the two can then perform data transmission based on this device identifier.

[0328] For example, the first AIoT device sends a device identifier to the first network device, the device identifier being determined by the first AIoT device based on first information. In other words, after determining the device identifier, the first AIoT device can report the device identifier to the first network device so that the first network device can be aware of the device identifier. This ensures that the first network device and the first AIoT device have a consistent understanding of the device identifier, thereby facilitating subsequent data transmission based on the device identifier.

[0329] The embodiments of this application do not limit the specific method by which the first AIoT device determines the device identifier. It can be determined based on the first information sent by the first network device or based on the information sent by the second network device to the first AIoT device.

[0330] It should be noted that the device identifier allocation process involved in the embodiments of this application can also be applied to the device identifier allocation between AIoT devices and core network devices. For example, the embodiments of this application are also applicable to the device identifier allocation between AIoT devices and application functions, or to the device identifier allocation between AIoT devices and core network elements. For example, core network elements include one or more of the following: AIoTF, AMF, AF, etc.

[0331] It should be understood that the various interactive processes shown above are merely exemplary descriptions, and the embodiments of this application are not limited thereto. In fact, the various embodiments described above can be implemented independently or in reasonable combinations, and the embodiments of this application do not specifically limit them in this regard.

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

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

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

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

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

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

[0338] In one possible design, the communication module 1120 is used to receive first information from a first network device, the first information being used to indicate a device identifier, the device identifier being used to identify the first AIoT device;

[0339] The communication module 1120 is also used to send second information, which is used to request or confirm the device identifier.

[0340] Optionally, as an embodiment, the communication module 1120 is used to send second information, including:

[0341] The second message is sent if one or more of the following conditions are met:

[0342] The first AIoT device has the ability to use device identification;

[0343] The data to be transmitted by the first AIoT device meets preset conditions;

[0344] The energy of the first AIoT device meets the energy threshold value;

[0345] The first AIoT device supports data segmentation functionality;

[0346] The first AIoT device needs to perform segmentation processing on the uplink data.

[0347] Optionally, as an embodiment, the second information is used to confirm the device identifier; the communication module 1120 is used to send the second information, including: sending the second information when the first AIoT device receives the first information.

[0348] Optionally, as an embodiment, the communication module 1120 is further configured to send the device identifier, which is the device identifier determined by the first AIoT device based on the first information.

[0349] Alternatively, in another possible design, the communication module 1120 is used to receive first information from the first network device, the first information being used to indicate the ability to assign a device identifier;

[0350] The communication module 1120 is also used to send second information, which is used to request a device identifier.

[0351] The communication module 1120 is further configured to receive third information from the first network device, the third information including a device identifier, the device identifier being used to identify the first AIoT device.

[0352] It should be understood that the communication device 1100 may correspond to the first AIoT device in Figures 2 to 10 according to the embodiments of this application; the communication device 1100 may include modules or units for performing the methods executed by the first AIoT device in Figures 2 to 10. Furthermore, each module in the communication device 1100 and the other operations and / or functions described above are respectively for implementing the corresponding processes of Figures 1 to 10.

[0353] It should also be understood that when the communication device 1100 is the first AIoT device, the processing module 1110 in the communication device 1100 can be implemented by at least one processor, for example, it can correspond to the processor 1210 in the communication device 1200 shown in FIG. 12. For example, the communication module 1120 can correspond to the communication interface 1220 in the communication device 1200 shown in FIG. 12.

[0354] It should also be understood that when the communication device 1100 is a chip or chip system configured in the first AIoT device, the processing module 1110 of the communication device 1100 can be implemented by a processor, microprocessor or integrated circuit integrated on the chip or chip system.

[0355] Alternatively, in one possible design, the communication device 1100 may correspond to the first network device in the above method embodiments, or a component (such as a circuit, chip, or chip system) configured in the first network device. The communication device 1100 may be used to perform the steps or processes performed by the first network device in any of the above method embodiments.

[0356] In one possible design, the communication module 1120 is used to send first information, the first information being used to indicate a device identifier, the device identifier being used to identify a first AIoT device;

[0357] The communication module 1120 is also used to receive second information, which is used to request or confirm the device identifier.

[0358] Optionally, as an embodiment, the communication module 1120 is further configured to receive auxiliary information from a second network device, the auxiliary information being used to assign a device identifier to the first AIoT device.

[0359] Optionally, as an embodiment, the communication module 1120 is further configured to receive the device identifier from the first AIoT device, wherein the device identifier is a device identifier determined by the first AIoT device based on the first information.

[0360] It should be understood that the communication device 1100 may correspond to the first network device in Figures 2 to 10 according to the embodiments of this application; the communication device 1100 may include modules or units for performing the methods executed by the first network device in Figures 2 to 10. Furthermore, each module in the communication device 1100 and the other operations and / or functions described above are respectively for implementing the corresponding processes of Figures 2 to 10.

[0361] It should also be understood that when the communication device 1100 is a first network device, the processing module 1110 in the communication device 1100 can be implemented by at least one processor, for example, it can correspond to the processor 1210 in the communication device 1200 shown in FIG. 12. For example, the communication module 1120 can correspond to the communication interface 1220 in the communication device 1200 shown in FIG. 12.

[0362] It should also be understood that when the communication device 1100 is a chip or chip system configured in the first network device, the processing module 1110 of the communication device 1100 can be implemented by a processor, microprocessor or integrated circuit integrated on the chip or chip system.

[0363] Alternatively, in one possible design, the communication device 1100 may correspond to the second network device in the above method embodiments, or a component (such as a circuit, chip, or chip system) configured in the second network device. The communication device 1100 can be used to perform the steps or processes performed by the second network device in any of the above method embodiments.

[0364] In one possible design, the communication module 1120 is used to send auxiliary information to the first network device, the auxiliary information being used to assign a device identifier to the first AIoT device; the auxiliary information includes one or more of the following:

[0365] The first AIoT device's capability information, the first AIoT device's service type, the first AIoT device's energy status, device identifier allocation information, a second identifier, and the device identifier allocation information; the device identifier allocation information is used to determine the device identifier; wherein, the first AIoT device's capability information includes data segmentation function capability indication information and / or capability indication information using the device identifier; the second identifier is an identifier generated based on the AIoT device's higher-level identifier.

[0366] It should be understood that the communication device 1100 may correspond to the second network device in Figures 9 and 10 according to embodiments of this application; the communication device 1100 may include modules or units for performing the methods executed by the second network device in Figures 9 and 10. Furthermore, each module in the communication device 1100 and the other operations and / or functions described above are respectively for implementing the corresponding processes of Figures 9 and 10.

[0367] It should also be understood that when the communication device 1100 is a second network device, the processing module 1110 in the communication device 1100 can be implemented by at least one processor, for example, it can correspond to the processor 1210 in the communication device 1200 shown in FIG. 12. For example, the communication module 1120 can correspond to the communication interface 1220 in the communication device 1200 shown in FIG. 12.

[0368] It should also be understood that when the communication device 1100 is a chip or chip system configured in the second network device, the processing module 1110 of the communication device 1100 can be implemented by a processor, microprocessor or integrated circuit integrated on the chip or chip system.

[0369] Figure 12 is another schematic block diagram of the communication device 1200 provided in an embodiment of this application. The communication device 1200 may be a first AIoT device, a first network device, or a second network device; it may also be a chip, chip system, or processor that supports the first AIoT device, the first network device, or the second network device in implementing the above methods. The communication device 1200 can be used to implement the methods described in the above method embodiments, and specific details can be found in the descriptions of the above method embodiments.

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

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

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

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

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

[0375] Optionally, if the communication device 1200 includes a processor 1210, a communication interface 1220, and a memory 1230, the processor 1210, the communication interface 1220, and the memory 1230 communicate with each other through internal connection paths.

[0376] Optionally, the memory 1230 may include read-only memory and random access memory, and provide instructions and data to the processor. A portion of the memory may also include non-volatile random access memory. The memory 1230 may be a separate device or integrated into the processor 1210.

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

[0378] In another implementation, the communication device 1200 may correspond to the first network device in the above method embodiments, and may be used to execute the various steps and / or processes executed by the first network device in the above method embodiments. The processor 1210 may be used to execute instructions stored in the memory 1230, and when the processor 1210 executes the instructions stored in the memory, the processor 1210 is used to execute the various steps and / or processes of the above method embodiments corresponding to the first network device.

[0379] In another implementation, the communication device 1200 may correspond to the second network device in the above method embodiments, and may be used to execute the various steps and / or processes executed by the second network device in the above method embodiments. The processor 1210 may be used to execute instructions stored in the memory 1230, and when the processor 1210 executes the instructions stored in the memory, the processor 1210 is used to execute the various steps and / or processes of the above method embodiments corresponding to the second network device.

[0380] Optionally, the communication interface 1220 is a transceiver, which may include a transmitter and a receiver. The transceiver may further include an antenna, and the number of antennas may be one or more. The processor 1210 and memory 1230, along with the communication interface 1220, may be devices integrated on different chips. For example, the processor 1210 and memory 1230 may be integrated in a baseband chip, and the communication interface 1220 may be integrated in a radio frequency chip. Alternatively, the processor 1210, memory 1230, and communication interface 1220 may be devices integrated on the same chip. This application does not limit this.

[0381] This application also provides a processing apparatus, including a processor and an interface; the processor is used to execute the communication method in any of the above method embodiments.

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

[0383] In implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software. The steps of the method disclosed in the embodiments of this application can be directly implemented by a hardware processor, or by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are omitted here.

[0384] It should be noted that the processor in the embodiments of this application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiments can be completed by the integrated logic circuitry in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above methods.

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

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

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

[0388] According to the method provided in the embodiments of this application, this application also provides a communication system, which includes the aforementioned first AIoT device and first network device. Optionally, the communication system further includes a second network device. Optionally, the communication system further includes the first device.

[0389] Optionally, the communication system also includes other devices that communicate with the first AIoT device. Optionally, the communication system also includes other devices that communicate with the first network device. Optionally, the communication system also includes other devices that communicate with the second network device.

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

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

[0392] The computer-readable storage medium 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 RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0393] The above-described device and method embodiments are completely corresponding, with corresponding modules or units performing corresponding steps. For example, a communication unit or communication interface performs the receiving or sending steps in the method embodiment, while other steps besides sending and receiving can be performed by a processing unit or processor.

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

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

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

[0397] Furthermore, the terms "system" and "network" are often used interchangeably in this paper. The term "and / or" in this paper merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Additionally, the character " / " in this paper generally indicates that the preceding and following related objects have an "or" relationship. For example, A / B can represent A or B.

[0398] The terms (or numbers) "first," "second," etc., appearing in the embodiments of this application are for descriptive purposes only, that is, only to distinguish different objects, such as different "network devices," and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, features defined with "first," "second," etc., may explicitly or implicitly include one or more features. In the description of the embodiments of this application, "at least one (item)" refers to one or more. "Multiple" means two or more. "At least one (item) below" or similar expressions refer to any combination of these items, including any combination of a single item or a plurality of items.

[0399] For example, expressions like "the item includes at least one of the following: A, B, and C" appearing in the embodiments of this application generally mean, unless otherwise specified, that the item can be any one of the following: A; B; C; A and B; A and C; B and C; A, B and C; A and A; A, A and A; A, A and B; A, A and C, A, B and B; A, C and C; B and B, B, B and B, B, B and C, C and C; C, C and C, and other combinations of A, B, and C. The above uses three elements, A, B, and C, as examples to illustrate the possible entries for the item. When expressed as "the item includes at least one of the following: A, B, ..., and X," that is, when the expression contains more elements, then the applicable entries for the item can also be obtained according to the aforementioned rules.

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

Claims

1. A communication method characterized by comprising: The method, applied to an AIoT device in a first-environment Internet of Things (IoT) environment, includes: Receive first information from a first network device, the first information being used to indicate a device identifier, the device identifier being used to identify the first AIoT device; Send a second message, which is used to request or confirm the device identifier.

2. The method according to claim 1, characterized in that, The sending of the second information includes: The second message is sent if one or more of the following conditions are met: The first AIoT device has the ability to use device identification; The data to be transmitted by the first AIoT device meets preset conditions; The energy of the first AIoT device meets the energy threshold value; The first AIoT device supports data segmentation functionality; The first AIoT device needs to perform segmentation processing on the uplink data.

3. The method according to claim 1 or 2, characterized in that, The second information is used to confirm the device identifier; The sending of the second information includes: Upon receiving the first information, the first AIoT device sends the second information.

4. The method according to any one of claims 1 to 3, characterized in that, The second information is one or more of the following: Device identifier allocation request indication information, device identifier confirmation indication information, the device identifier, first random number RN16, first preamble sequence, data segmentation indication information, energy indication information of the first AIoT device, data volume indication information to be transmitted, number of data packets to be transmitted indication information, and environmental IoT service capability indication information.

5. The method according to any one of claims 1 to 4, characterized in that, The second information is carried in the AIoT device-to-network device (D2R) data.

6. The method according to any one of claims 1 to 5, characterized in that, The device identifier includes one or more of the following: A random number of the first preset length; First network device identifier; The first identifier is one or more of the following: a random number RN16 generated by the first AIoT device, a first random access preamble, and a resource number indicator; The second identifier is an identifier generated based on the AIoT device high-level identifier.

7. The method according to any one of claims 1 to 6, characterized in that, The first information includes one or more of the following: Reuse instruction information, allocate instruction information, and the device identifier; The reuse indication information is used to indicate that the first identifier and / or the second identifier are used as the device identifier; The allocation instruction information is used to indicate the allocation device identifier.

8. The method according to any one of claims 1 to 7, characterized in that, The method further includes: Send the device identifier, which is the device identifier determined by the first AIoT device based on the first information.

9. The method according to any one of claims 1 to 8, characterized in that, The first information is also used to indicate one or more of the following: The type of device identifier; Validity information, which is used to indicate that the first AIoT device can use the device identifier for a first duration, and / or that the first AIoT device can use the device identifier to transmit the amount of data or data packets; Invalidity information, which is used to indicate that the device identifies invalid information.

10. The method of claim 9, wherein, The invalid information includes one or more of the following: The second duration information is used to indicate that the device identifier will be released if no data is transmitted within the second duration. The data packet count information is used to indicate that the device identifier will be released after a preset number of AIoT data packets have been transmitted; First energy information is used to indicate that the device identifier will be released when the energy of the first AIoT device meets preset conditions.

11. A communication method characterized by comprising: Applied to a first network device, the method includes: Send first information, the first information being used to indicate a device identifier, the device identifier being used to identify a first environment Internet of Things (AIoT) device; Receive second information, which is used to request or confirm the device identifier.

12. The method of claim 11, wherein, The second information is one or more of the following: Device identifier allocation request indication information, device identifier confirmation indication information, the device identifier, first random number RN16, first preamble sequence, data segmentation indication information, energy indication information of the first AIoT device, data volume indication information to be transmitted, number of data packets to be transmitted indication information, and environmental IoT service capability indication information.

13. The method according to claim 11 or 12, characterized in that, The method further includes: Receive auxiliary information from a second network device, the auxiliary information being used to assign a device identifier to the first AIoT device.

14. The method of claim 13, wherein, The auxiliary information includes one or more of the following: The first AIoT device's capability information, the first AIoT device's service type, the first AIoT device's energy status, a second identifier, and device identifier allocation information; the device identifier allocation information is used to determine the device identifier. The capability information of the first AIoT device includes capability indication information for data segmentation function and / or capability indication information using device identifier; The second identifier is an identifier generated based on the AIoT device's high-level identifier.

15. The method according to claim 13 or 14, characterized in that, The device identifier is generated based on the AIoT device high-level identifier.

16. The method according to claim 14 or 15, characterized in that The device identifier allocation information includes one or more of the following: The second preset length is the length of the device identifier generated based on some or all of the bits of the AIoT device high-level identifier. The first bit range is the bit range of the device identifier generated based on some or all of the bits of the AIoT device high-level identifier.

17. The method according to any one of claims 11 to 16, characterized in that, The device identifier includes one or more of the following: A random number of the first preset length; First network device identifier; The first identifier is one or more of the following: a random number RN16 generated by the first AIoT device, a first random access preamble, and a resource number indicator; The second identifier is an identifier generated based on the AIoT device high-level identifier.

18. The method according to any one of claims 11 to 17, characterized in that, The first information includes one or more of the following: Reuse instruction information, allocate instruction information, and the device identifier; The reuse indication information is used to indicate that the first identifier and / or the second identifier are used as the device identifier; The allocation instruction information is used to indicate the allocation device identifier.

19. The method according to any one of claims 11 to 18, characterized in that, The method further includes: Receive the device identifier from the first AIoT device, wherein the device identifier is a device identifier determined by the first AIoT device based on the first information.

20. The method according to any one of claims 11 to 19, characterized in that, The first information is also used to indicate one or more of the following: The type of device identifier; Validity information, which is used to indicate that the first AIoT device can use the device identifier for a first duration, or that the first AIoT device can use the device identifier to transmit a amount of data or data packets. Invalidity information, which is used to indicate that the device identifies invalid information.

21. The method of claim 20, wherein, The invalid information includes one or more of the following: The second duration information is used to indicate that the device identifier will be released if no data is transmitted within the second duration. The data packet count information is used to indicate that the device identifier will be released after a preset number of AIoT data packets have been transmitted; First energy information is used to indicate that the device identifier will be released when the energy of the first AIoT device meets preset conditions.

22. A communication method, characterized in that, Applied to a second network device, the method includes: Sending auxiliary information to a first network device, the auxiliary information being used to assign a device identifier to the first AIoT device; the auxiliary information includes one or more of the following: The first AIoT device's capability information, the first AIoT device's service type, the first AIoT device's energy status, device identifier allocation information, a second identifier, and device identifier allocation information; the device identifier allocation information is used to determine the device identifier. The capability information of the first AIoT device includes capability indication information for data segmentation function and / or capability indication information using device identifier; The second identifier is an identifier generated based on the AIoT device's high-level identifier.

23. The method according to claim 22, characterized in that, The device identifier is generated based on the AIoT device high-level identifier.

24. The method of claim 22 or 23, wherein, The device identifier allocation information includes one or more of the following: The second preset length is the length of the device identifier generated based on some or all of the bits of the AIoT device high-level identifier. The first bit range is the bit range of the device identifier generated based on some or all of the bits of the AIoT device high-level identifier.

25. A communication method, characterized in that, The method, applied to an AIoT device in a first-environment Internet of Things (IoT) environment, includes: Receive first information from a first network device, the first information being used to indicate the ability to allocate a device identifier; Send a second message, which is used to request a device identifier; The system receives third information from the first network device, the third information including a device identifier, which is used to identify the first AIoT device.

26. A communication system, characterized by Includes one or more first AIoT devices, a first network device, and a second network device; The first AIoT device is used to perform the method as described in any one of claims 1-10 or 25; The first network device is configured to perform the method as described in any one of claims 11-21; The second network device is used to perform the method as described in any one of claims 22-24.

27. A communications device, characterized by The device includes a processor coupled to a memory for storing programs or instructions that, when executed by the processor, cause the device to perform the method as described in any one of claims 1-10 or 25; or cause the device to perform the method as described in any one of claims 11-21; or cause the device to perform the method as described in any one of claims 22-24.

Images