Communication method and communication apparatus

Abstract

Provided in the present application are a communication method and a communication apparatus. The communication method comprises: a terminal receiving first information, wherein the first information indicates a first resource, and the first resource is used for executing a first AIoT service; the terminal sending second information, wherein the second information comprises first data and third information, the first data is associated with the first AIoT service, and the third information is used for making a request to release or stop using the first resource, or the third information indicates that the first AIoT service has been finished or completed, or the third information indicates that the first data is associated with the first AIoT service; and the terminal releasing or stopping using the first resource.

Description

A communication method and a communication device

[0001] This application claims priority to Chinese Patent Application No. 202411774929.X, filed on December 2, 2024, entitled "A 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 communication technology, and more specifically, to a communication method and a communication device. Background Technology

[0003] With the development of communication technology, the 3rd Generation Partnership Project (3GPP) defined the Ambient Internet of Things (AIoT or A-IoT) technology. In AIoT and other related technologies, the communication system can include readers and tags. Readers can be implemented by network devices (such as base stations) or user equipment (UE), while tags can be IoT terminals, such as passive / semi-passive / active tags. AIoT technology is mainly used to achieve the following services: inventory management, positioning, sensing, or command. Typical application scenarios for AIoT technology include logistics, warehousing, industrial manufacturing, identity recognition, and environmental monitoring.

[0004] For example, when the reader / writer is implemented by the UE, core network elements that support or enable AIoT can send AIoT data and / or signaling to the UE via a base station. The UE can then send the received AIoT data and / or signaling to the AIoT device, for example, to sequentially execute inventory and command services. However, in practice, core network elements may not immediately issue commands after obtaining the inventory results, resulting in underutilization of the AIoT resources used by the UE and wasted resources. Summary of the Invention

[0005] To address the aforementioned technical problems, this application provides a communication method and a communication device that can avoid resource waste and improve resource utilization.

[0006] Firstly, a communication method is provided. This method can be executed by a terminal, or by components within the terminal (e.g., processors, chips, or chip systems, such as circuits or chips in the terminal responsible for communication functions (e.g., modem chips, also known as baseband chips, or system-on-chip (SoC) chips or system-in-package (SIP) chips containing modem cores)), or by logic modules or software capable of implementing all or part of the terminal's functions.

[0007] The method includes: receiving first information from an access network device, the first information indicating a first resource, the first resource being used to execute a first AIoT service; sending second information to the access network device, the second information including first data and / or third information, the first data being associated with the first AIoT service, the third information indicating the end or completion of the first AIoT service, or the third information indicating the first data being associated with the first AIoT service, or the third information being used to request the release or cessation of use of the first resource; and releasing or cessation of use of the first resource.

[0008] In this application, the first resource may be configured by the access network device for the terminal, or it may be configured by the DU in the access network device for the terminal; there is no limitation on this.

[0009] Based on the above scheme, while reporting the execution result (first data) of the first AIoT service, the terminal can implicitly or explicitly request or instruct the release or cessation of the use of the first resource by sending second information. This allows the access network device to instruct the terminal to release or cease using the first resource. Therefore, before the access network device subsequently issues commands or service requests, the terminal does not need to continuously occupy the resource, avoiding resource waste. Furthermore, the access network device can allocate the released or deactivated first resource to other terminals, improving resource utilization.

[0010] In conjunction with the first aspect, in some implementations of the first aspect, before releasing or ceasing the use of the first resource, the method further includes: receiving fourth information from the access network device, the fourth information indicating the release or cessation of the use of the first resource.

[0011] Based on the above scheme, the terminal can determine whether to release or stop using the first resource by receiving the fourth information. That is, the terminal does not need to continuously occupy the resource, which can avoid resource waste and improve resource utilization.

[0012] In conjunction with the first aspect, in some implementations of the first aspect, the third information instructs the terminal to stop using the first resource, and the method further includes: receiving fifth information from the access network device, the fifth information instructing the resumption of use or continued use of the first resource.

[0013] Optionally, the method further includes: receiving seventh information from the access network device, the seventh information indicating the execution of a second AIoT service, at which time the terminal can use the first resources to execute the second AIoT service.

[0014] Optionally, the fifth and seventh messages can be sent simultaneously or separately; the fifth and seventh messages can be sent in the same signaling or sent separately through different signaling, without limitation.

[0015] Based on the above scheme, when the terminal stops using the first resource, receiving the fifth information can determine whether to resume or continue using the first resource, for example, to use the first resource to execute a second AIoT service. This not only allows the first resource to be stopped when there is no need to execute an AIoT service, avoiding resource waste and improving resource utilization, but also allows the first resource to be used or resumed when the second AIoT service needs to be executed, ensuring the orderly execution of AIoT services and improving the user experience.

[0016] In conjunction with the first aspect, in some implementations of the first aspect, the third information instructs the terminal to release the first resource, and the method further includes: receiving sixth information from the access network device, the sixth information indicating a second resource, the second resource being used to execute a second AIoT service. At this time, the terminal can use the second resource to execute the second AIoT service.

[0017] Optionally, the first resource and the second resource can be the same or different, without limitation.

[0018] Optionally, the method further includes: receiving eighth information from the access network device, the eighth information indicating the execution of a second AIoT service, at which time the terminal can use the second resources to execute the second AIoT service.

[0019] Optionally, the sixth and eighth messages can be sent simultaneously or separately; the sixth and eighth messages can be sent in the same signaling or sent separately through different signaling, without limitation.

[0020] Based on the above scheme, when the terminal releases the first resource, the second resource can be acquired by receiving the sixth information. For example, the second resource can be used to execute a second AIoT service. This not only allows the use of the first resource to be stopped when AIoT services are not needed, avoiding resource waste and improving resource utilization, but also allows the acquisition and use of the second resource to execute the second AIoT service when it is required, ensuring the orderly execution of AIoT services and enhancing the user experience.

[0021] Secondly, a communication method is provided. This method can be executed by an access network device, or by a component in the access network device (e.g., a processor, chip, or chip system, such as a circuit or chip in the access network device responsible for communication functions (e.g., a modem chip, also known as a baseband chip, or a SoC chip or SIP chip containing a modem core)), or by a logic module or software capable of implementing all or part of the terminal functions.

[0022] The method includes: sending first information to a terminal, the first information indicating a first resource, the first resource being used to perform a first AIoT service; receiving second information from the terminal, the second information including first data and / or third information, the first data being associated with the first AIoT service, the third information indicating the end or completion of the first AIoT service, or the third information indicating the first data being associated with the first AIoT service, or the third information being used to request the release or cessation of use of the first resource.

[0023] Based on the above scheme, while reporting the execution result of the first AIoT service (e.g., the first data), the terminal can implicitly or explicitly request or instruct the release or cessation of the use of the first resource by sending third information to the access device. The access device then instructs the terminal to release or cease using the first resource. Therefore, the terminal does not need to continuously occupy resources before the access device subsequently issues command service requests, avoiding resource waste. Furthermore, the access device can allocate the released or deactivated first resource to other terminals, improving resource utilization.

[0024] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: sending a fourth message to the terminal, the fourth message indicating the release or cessation of use of the first resource.

[0025] In conjunction with the second aspect, in some implementations of the second aspect, the third information instructs the terminal to stop using the first resource, and the method further includes: sending a fifth information to the terminal, the fifth information instructing the resumption of use or continued use of the first resource.

[0026] Optionally, the method further includes: sending a seventh message to the terminal, the seventh message indicating the execution of a second AIoT service, at which time the terminal can use the first resources to execute the second AIoT service.

[0027] In conjunction with the second aspect, in some implementations of the second aspect, the third information indicates the release of the first resource, and the method further includes: sending a sixth information to the terminal, the sixth information indicating the second resource, the second resource being used to perform a second AIoT service.

[0028] Optionally, the method further includes: sending an eighth message to the terminal, the eighth message indicating the execution of a second AIoT service, at which time the terminal can use the second resources to execute the second AIoT service.

[0029] The beneficial effects of the second aspect and some implementations thereof can be referred to the relevant descriptions in the first aspect, and will not be repeated here.

[0030] Thirdly, a communication method is provided. This method can be executed by a terminal, or by components in the terminal (e.g., processors, chips, or chip systems, such as circuits or chips in the terminal responsible for communication functions), or by logic modules or software that can implement all or part of the terminal's functions.

[0031] The method includes: receiving first information and / or second information from an access network device, wherein the first information indicates a first resource, the first resource is used to perform a first AIoT service, and the second information indicates a time for ceasing the use of the first resource; performing the first AIoT service using the first resource; and / or, ceasing the use of the first resource according to the second information.

[0032] Optionally, the first information and the second information can be sent simultaneously or separately; the first information and the second information can be sent in the same signaling or sent through different signaling, without limitation.

[0033] Based on the above scheme, while allocating the first resource, the access network device can send a second message to the terminal to indicate the time for stopping the use of the first resource. This allows the terminal to stop using the first resource during the first timer operation or within the first time period, and to continue using or resume using the first resource after the first timer expires or within the second time period. This avoids resource waste and improves resource utilization.

[0034] In conjunction with the third aspect, in some implementations of the third aspect, the second information includes at least one of the following: a first timer, a first time period, a second time period, or a first duration, and the method further includes: stopping the use of the first resource during the operation of the first timer, or during the first time period, or during the first duration.

[0035] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes: after the first timer expires, or during the second time period, or after the first duration ends, resuming or continuing to use or releasing the first resource.

[0036] In conjunction with the third aspect, in some implementations of the third aspect, the method also includes: starting the first timer when the second information is received.

[0037] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes: receiving third information from the access network device, the third information indicating the execution of a second AIoT service; and continuing to use the first resource to execute the second AIoT service after the first timer expires, or during a second time period, or after the first duration ends.

[0038] The beneficial effects of the third aspect and some implementations thereof can be referred to the relevant descriptions in the first aspect, and will not be repeated here.

[0039] Fourthly, a communication method is provided. This method can be executed by an access network device, or by a component in the access network device (e.g., a processor, chip, or chip system, such as a circuit or chip in the access network device responsible for communication functions), or by a logic module or software capable of implementing all or part of the terminal functions.

[0040] The method includes: determining first information and / or second information, wherein the first information indicates a first resource, the first resource is used to perform a first AIoT service, and the second information indicates a time for ceasing the use of the first resource; and sending the first information and / or the second information to a terminal.

[0041] Alternatively, the method may include: sending first information and / or second information to the terminal, wherein the first information indicates a first resource, the first resource is used to perform a first AIoT service, and the second information indicates the time for ceasing the use of the first resource.

[0042] Based on the above scheme, while allocating the first resource, the access network device can send a second message to the terminal to indicate the time for stopping the use of the first resource. This allows the terminal to stop using the first resource during the first timer operation or within the first time period, and to continue using or resume using the first resource after the first timer expires or within the second time period. This avoids resource waste and improves resource utilization.

[0043] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the second information includes at least one of the following: a first timer, a first time period, a second time period, or a first duration, wherein the first resource is stopped from use during the operation of the first timer, or during the first time period, or during the first duration.

[0044] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the first resource is resumed for use, continued for use, or released after the first timer expires, or during the second time period, or after the first duration ends.

[0045] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the method further includes: sending third information to the terminal, the third information instructing the execution of a second AIoT service; wherein, after the first timer expires, or during the second time period, or after the first duration ends, the first resource is used to execute the second AIoT service.

[0046] The beneficial effects of the fourth aspect and some of its implementations can be found in the description of the third aspect, and will not be repeated here.

[0047] Fifthly, a communication method is provided. This method can be executed by an AIoT device, or by a component in the AIoT device (e.g., a processor, chip, or chip system, such as a circuit or chip in the AIoT device responsible for communication functions), or by a logic module or software capable of implementing all or part of the functions of the AIoT device.

[0048] The method includes: receiving first information from an access network device or terminal, the first information indicating a time for stopping monitoring AIoT interface signaling or a time for stopping the use of a first resource or a sleep time for an AIoT device, the first resource being used to execute a first AIoT service; stopping monitoring AIoT interface signaling, or stopping the use of the first resource, or going into sleep mode, the AIoT interface signaling being associated with the first AIoT service.

[0049] Optionally, the AIoT interface signaling or AIoT air interface signaling in the embodiments of this application can be replaced with the first signaling, which is related to the first AIoT service. That is to say, this application does not limit the specific name of the first signaling.

[0050] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the first information includes at least one of the following: a second timer, a third time period and a fourth time period, or a second duration, and the method further includes: during the operation of the second timer, or during the third time period, or during the second duration, stopping monitoring AIoT interface signaling or stopping the use of the first resource, or putting the device into sleep mode.

[0051] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the method further includes: after the second timer expires, or during the fourth time period, or after the second time period ends, resuming or continuing to use or releasing the first resource.

[0052] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the method further includes: starting a second timer upon receiving first information from an access network device or terminal.

[0053] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the method further includes: receiving second information from an access network device or terminal, the second information indicating the execution of a second AIoT service; after the first timer expires, during a fourth time period, after the second time period ends, continuing to monitor or resuming monitoring AIoT interface signaling, or continuing to use or resuming use or releasing the first resource, or executing the second AIoT service.

[0054] Optionally, the terminal may resume using or continue using the first resource to perform the second AIoT service, or use the second resource to perform the second AIoT service.

[0055] The beneficial effects of the fifth aspect and some of its implementations can be referred to the relevant descriptions in the first aspect, and will not be repeated here.

[0056] Sixthly, a communication method is provided. This method can be executed by a terminal or access network device, or by a component within the terminal or access network device (e.g., a processor, chip, or chip system, such as circuitry or a chip in the terminal or access network device responsible for communication functions), or by a logic module or software capable of implementing all or part of the functions of the terminal or access network device.

[0057] The method includes: acquiring first information, the first information indicating the time for stopping monitoring AIoT interface signaling or stopping the use of first resources or the sleep time of the AIoT device, the first resources being used to execute a first AIoT service; and sending the first information to the AIoT device.

[0058] Alternatively, the method may include: sending a first message to an AIoT device, the first message indicating a time for stopping monitoring of AIoT interface signaling or a time for stopping the use of a first resource or a sleep time for the AIoT device, the first resource being used to execute a first AIoT service.

[0059] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the first information includes at least one of the following: a second timer, a third time period and a fourth time period, or a second duration, wherein the first information instructs the AIoT device to monitor AIoT interface signaling or stop using the first resource or go into sleep mode during the operation of the second timer, or during the third time period, or during the second duration.

[0060] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the first information further instructs the AIoT device to resume monitoring the AIoT interface signaling or to continue using or resume using the first resource after the second timer expires, or during the fourth time period, or after the second time period ends.

[0061] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the method further includes: sending a second message to the AIoT device, the second message instructing the execution of a second AIoT service; after the second timer expires, or during a third time period, or after the second time period ends, continuing to monitor the AIoT interface signaling, or resuming or continuing to use or releasing the first resource.

[0062] Optionally, the terminal may resume using or continue using the first resource to perform the second AIoT service, or use the second resource to perform the second AIoT service.

[0063] The beneficial effects of the sixth aspect and some of its implementations can be found in the description of the fifth aspect, and will not be repeated here.

[0064] In a seventh aspect, a communication device is provided. This communication device has the functions described in the first aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the first aspect. These modules, units, or means can be implemented through software, hardware, or a combination of software and hardware.

[0065] In one possible design, the communication device includes: a communication module for receiving first information from an access network device, the first information indicating a first resource, the first resource being used to execute a first AIoT service; the communication module is further configured to send second information to the access network device, the second information including first data and third information, the first data being associated with the first AIoT service, the third information indicating the end or completion of the first AIoT service, or the third information indicating the first data being associated with the first AIoT service, or the third information being used to request the release or cessation of use of the first resource; and a processing module for releasing or cessation of use of the first resource.

[0066] Eighthly, a communication device is provided. This communication device has the functions described in the second aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the second aspect above. These modules, units, or means can be implemented in software, hardware, or a combination of software and hardware.

[0067] In one possible design, the communication device includes: a communication module for sending first information to a terminal, the first information indicating a first resource, the first resource being used to perform a first AIoT service; the communication module is further configured to receive second information from the terminal, the second information including first data and / or third information, the first data being associated with the first AIoT service, the third information indicating the end or completion of the first AIoT service, or the third information indicating the first data being associated with the first AIoT service, or the third information being used to request the release or cessation of use of the first resource.

[0068] Ninthly, a communication device is provided. This communication device has the functions described in the third aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the third aspect. These modules, units, or means can be implemented in software, hardware, or a combination of software and hardware.

[0069] In one possible design, the communication device includes: a communication module for receiving first information and / or second information from an access network device, wherein the first information indicates a first resource, the first resource is used to perform a first AIoT service, and the second information indicates a time for ceasing the use of the first resource; a processing module for performing the first AIoT service using the first resource; and / or, the processing module for ceasing the use of the first resource based on the second information.

[0070] In a tenth aspect, a communication device is provided. This communication device has the functions described in the fourth aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the fourth aspect. These modules, units, or means can be implemented in software, hardware, or a combination of software and hardware.

[0071] In one possible design, the communication device includes: a processing module for determining first information and / or second information, the first information indicating a first resource, the first resource being used to perform a first AIoT service, and the second information indicating a time for ceasing the use of the first resource; and a communication module for sending the first information and / or the second information to a terminal.

[0072] Alternatively, a communication module is used to send first information to the terminal, the first information indicating a first resource and second information, the first resource being used to execute a first AIoT service, and the second information indicating the time for ceasing the use of the first resource.

[0073] Eleventhly, a communication device is provided. This communication device has the functions described in the fifth aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the fifth aspect. These modules, units, or means can be implemented through software, hardware, or a combination of software and hardware.

[0074] In one possible design, the communication device includes: a communication module for receiving first information from an access network device or terminal, the first information indicating a time for stopping monitoring AIoT interface signaling or a time for stopping the use of a first resource or a sleep time for the AIoT device, the first resource being used to execute a first AIoT service; and a processing module for stopping monitoring AIoT interface signaling, or stopping the use of the first resource, or going into sleep mode, the AIoT interface signaling being associated with the first AIoT service.

[0075] In a twelfth aspect, a communication device is provided. This communication device has the functions described in the sixth aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the sixth aspect. These modules, units, or means can be implemented in software, hardware, or a combination of software and hardware.

[0076] In one possible design, the communication device includes: a communication module for acquiring first information, the first information indicating a time for ceasing monitoring of AIoT interface signaling, a time for ceasing use of first resources, or a sleep time for the AIoT device, the first resources being used to execute a first AIoT service; the communication module is also used to send the first information to the AIoT device. Alternatively, the communication device includes: a communication module for sending the first information to the AIoT device, the first information indicating a time for ceasing monitoring of AIoT interface signaling, a time for ceasing use of first resources, or a sleep time for the AIoT device, the first resources being used to execute a first AIoT service.

[0077] In a thirteenth aspect, a communication device is provided, comprising an interface circuit and one or more processors. The one or more processors are coupled to a memory. The memory stores part or all of a computer program or instructions necessary for implementing the functions involved in any of the first to sixth aspects described above. The one or more processors are executable to carry out the computer program or instructions, which, when executed, cause the communication device to implement the methods in any possible design or implementation of the first to sixth aspects described above. The interface circuit is used to implement communication functions within the communication device and / or communication functions between the communication device and other devices or components.

[0078] In one possible design, the processor is used to communicate with other devices or components through the interface circuit.

[0079] In one possible design, the communication device may also include the memory.

[0080] The aforementioned communication device may be a terminal, a communication module in a terminal, or a chip in a terminal that is responsible for communication functions, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module.

[0081] The aforementioned communication device may be an AIoT device, or a communication module in an AIoT device, or a chip in an AIoT device that is responsible for communication functions, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module.

[0082] The aforementioned communication device may be an access network device, or a module (such as a circuit, chip, or chip system) in the access network device, or a logical node, logical module, or software that can realize all or part of the functions of the access network device.

[0083] In a fourteenth aspect, a communication system is provided, which includes at least one of the communication devices of any one of the seventh to twelfth aspects.

[0084] In a fifteenth aspect, a computer-readable storage medium is provided. This computer-readable storage medium stores computer program code or instructions, which, when read and executed by a computer, cause the method in any of the possible implementations of the first to sixth aspects to be implemented.

[0085] In a sixteenth aspect, a computer program product is provided. The computer program product includes computer program code or instructions that, when read and executed by a computer, cause the methods in any of the possible implementations of the first to sixth aspects to be implemented.

[0086] Page seventeen provides a computer program. When the computer program is run, it causes the methods in any of the possible implementations of aspects one through six above to be implemented.

[0087] It should be understood that the beneficial effects of aspects seven through seventeen above can be referenced from aspects one through six above and any possible implementation thereof, and will not be elaborated here. Attached Figure Description

[0088] Figures 1 to 3 are schematic diagrams of a communication system applicable to embodiments of this application;

[0089] Figure 4 is a schematic diagram of the protocol stack structure;

[0090] Figures 5 and 6 are schematic flowcharts illustrating the execution methods of inventory and command operations;

[0091] Figures 7 to 18 are schematic flowcharts of the communication method provided in the embodiments of this application;

[0092] Figure 19 is a possible exemplary block diagram of the communication device involved in the embodiments of this application;

[0093] Figure 20 is a schematic diagram of the structure of a terminal provided in an embodiment of this application;

[0094] Figure 21 is a schematic diagram of the structure of the baseband processor in the terminal provided in the embodiment of this application. Detailed Implementation

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

[0096] Before introducing the scheme of this application, the following points should be noted.

[0097] (1) In this application, unless otherwise specified or logically conflicting, the terms and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0098] (2) In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and c can mean: a, or, b, or, c, or, a and b, or, a and c, or, b and c, or, a, b, and c. Where a, b, and c can be single or multiple.

[0099] (3) In this application, "first," "second," and "#1," "#2" are merely for descriptive convenience and are used to distinguish objects, and are not intended to limit the scope of the embodiments of this application. For example, they are used to distinguish different messages, rather than to describe a specific order or sequence. It should be understood that such described objects can be interchanged where appropriate so as to describe solutions other than those in the embodiments of this application.

[0100] (4) In this application, "instruction" can include direct instruction, indirect instruction, explicit instruction, implicit instruction, etc. When describing an instruction information as indicating A, it can be understood as the instruction information carrying A, carrying the identifier of A, carrying B which is associated with A, carrying the identifier of B which is associated with A, etc. In other words, if the receiving side of an instruction information can determine A based on the instruction information, it can be described as the instruction information indicating A, and the specific method of determination is not limited. When it is understood that the instruction information carries A, "instruction" can be replaced with "includes". In this case, expressions such as "send / receive instruction information, the instruction information indicates A" can be replaced with "send / receive A".

[0101] In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementations, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly indicate the information to be instructed by indicating other information, where there is a relationship between the other information and the information to be instructed. It can also indicate only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. Furthermore, the information to be instructed can be sent as a whole or divided into multiple sub-information pieces, and the sending period and / or timing of these sub-information pieces can be the same or different.

[0102] (5) In this application, "predefined" may refer to a standard protocol predefined, or it may refer to a pre-agreed or pre-negotiated agreement between devices. "Pre-configuration" can be achieved by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device, and this application does not limit the implementation method. "Protocol" may refer to a standard protocol in the field of communication, such as fourth-generation (4G) protocols. th Generation 4G network, fifth generation (5G) network th This application does not limit the scope to network protocols such as 5G (generation, 5G), New Radio (NR), 5.5G, and related protocols applied in future communication networks.

[0103] (6) In this application, “message”, “information”, “signal” or “information element (IE)” can be used interchangeably. There are no restrictions on the name of the message or information, as long as it can achieve the corresponding function.

[0104] "Sending information to XX (device)" can be understood as the destination of the information being that device. This can include sending information to that device directly or indirectly. "Receiving information from XX (device), or receiving information from XX (device)" can be understood as the source of the information being that device. This can include receiving information from that device directly or indirectly. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be interpreted similarly, and will not be elaborated further here.

[0105] "Communication" can also be described as data transmission, information transmission, data processing, etc. "Transmission" includes sending and / or receiving. "Transmission" can be described as output. "Sending" can also be understood as the output of a chip interface, and "receiving" can be understood as the input of a chip interface. In other words, "sending" or "receiving" can occur between devices, for example, between access network devices and terminal devices via an air interface. "Sending" or "receiving" can also occur within a device, for example, between components, modules, chips, software modules, or hardware modules within a device via a bus, wiring, or interface.

[0106] For example, "sending information" can be understood as one device sending information to another device, or it can also be understood as one logical module within a device sending information to another logical module. For instance, "access network device sending information" can be understood as the access network device sending information to another device (such as a terminal), or it can be understood as logical module 1 within the access network device sending information to logical module 2 within the access network device. Similarly, "receiving information" can be understood as one device receiving information from another device, or it can also be understood as one logical module within a device receiving information from another logical module. For instance, "access network device receiving information" can be understood as the access network device receiving information from another device (such as a terminal), or it can be understood as logical module 1 within the access network device receiving information from logical module 2 within the access network device.

[0107] (7) In this application, the words “exemplary,” “for example,” etc., are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as an “example” in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the word “example” is intended to present the concept in a concrete manner. In the embodiments of this application, “of,” “corresponding, relevant,” “corresponding,” and “associate” may sometimes be used interchangeably, and it should be noted that their intended meanings are consistent unless their distinctions are emphasized.

[0108] (8) In this application, the configuration can be signaling configuration, such as RRC messages, downlink control information (DCI), or system information blocks (SIBs). Optionally, the signaling configuration can be pre-configured signaling configuration given to the terminal device, or configured to the terminal device through pre-configuration. Here, pre-configuration means defining or configuring the values ​​of corresponding parameters in advance in a protocol manner, and storing them in the terminal device during communication. The pre-configured messages can be modified or updated when the terminal device is connected to the network.

[0109] The following describes the communication system to which this application applies.

[0110] The technical solutions provided in this application can be applied to various communication systems, such as: 5th generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FD) systems, LTE time division duplex (TD) systems, wireless local area network (WLAN) systems, satellite communication systems, future communication systems, or integrated systems of multiple systems. The technical solutions provided in this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.

[0111] The technical solutions provided in this application can also be applied to non-terrestrial network (NTN) systems such as inter-satellite communication and satellite communication. As an example, a satellite communication system includes a satellite base station and a terminal. The satellite base station provides communication services to the terminal. The satellite base station can also communicate with other base stations. A satellite can act as a base station or as a terminal. Here, "satellite" can refer to unmanned aerial vehicles (UAVs), hot air balloons, low-Earth orbit (LEO) satellites, medium-Earth orbit (MEO) satellites, high-Earth orbit (HEO) satellites, etc. "Satellite" can also refer to non-terrestrial base stations or non-terrestrial equipment, etc.

[0112] In a communication system, a device can send signals to or receive signals from another device. These signals can include information, signaling, or data. The device can also be replaced by an entity, network entity, communication device, mobile device, network element, communication module, node, communication node, communication apparatus, etc. This disclosure uses a device as an example. For instance, a communication system can include at least one terminal and at least one network device. The network device can send downlink signals to the terminal, and / or the terminal can send uplink signals to the network device. It is understood that the terminal in this disclosure can be replaced by a first communication device, and the network device can be replaced by a second communication device, both performing the corresponding communication methods described in this disclosure. Alternatively, the corresponding communication methods in this disclosure can be applied between network devices or between terminals, without limitation herein.

[0113] The terminal in this embodiment can be a device or module that accesses the aforementioned communication system and has corresponding communication functions. The terminal can include various devices with wireless communication capabilities, which can be used to connect people, objects, machines, etc. The terminal can be widely applied in various scenarios, such as: cellular communication, D2D, V2X, peer-to-peer, M2M, MTC, IoT, virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery, etc. The terminal can be a terminal in any of the above scenarios, such as an MTC terminal, an IoT terminal, etc. Terminals can be user equipment (UE), terminals, fixed equipment, mobile stations or mobile devices, subscriber units, handheld devices, vehicle-mounted devices, wearable devices, cellular phones, smartphones, session initiation protocol (SIP) phones, wireless data cards, personal digital assistants (PDAs), computers, tablets, laptops, wireless modems, handsets, laptop computers, computers with wireless transceiver capabilities, smart books, vehicles, satellites, global positioning system (GPS) devices, target tracking devices, aircraft (e.g., drones, helicopters, multiple helicopters, four helicopters, or airplanes), ships, remote control devices, smart home devices, industrial equipment, transportation vehicles with wireless communication capabilities, communication modules, and roadside units with terminal functionality, all conforming to the 3GPP standard. The terminal refers to a wireless unit (RSU), or a device built into the aforementioned equipment (e.g., a communication module, modem, or chip in the aforementioned equipment), or other processing devices connected to the wireless modem. For ease of description, the terminal will be described below as a terminal or UE.

[0114] It should be understood that in certain scenarios, a UE can also be used as a base station. For example, a UE can act as a scheduling entity, providing sidelink signaling between UEs in scenarios such as V2X, D2D, or end-to-end.

[0115] In this embodiment, the device for implementing the terminal's functions can be a terminal itself, or a device capable of supporting the terminal in implementing those functions, such as a chip system. This device can be installed in the terminal or used in conjunction with the terminal. In this embodiment, the chip system can consist of chips or include chips and other discrete components. This embodiment only uses a terminal as an example to illustrate the device for implementing the terminal's functions and does not limit the solution of this embodiment.

[0116] The network device in this application embodiment can be a device or module with corresponding communication functions. The network device can be a device used to communicate with a terminal; it can also be called an access network device or a wireless access network device, such as a base station. In this application embodiment, the network device can refer to a radio access network (RAN) node (or device) that connects a terminal to a wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), relay station, access point, transmitting and receiving point (TRP), transmitter, master station, auxiliary station, motor slide retainer (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or similar entities, or combinations thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and M2M communications, or a device that performs base station functions in future communication systems. A base station can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0117] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0118] In some deployments, the network device in this application embodiment may be a device including a CU, or a DU, or a device including both CU and DU, or a control plane CU node (central unit-control plane (CU-CP)) and a user plane CU node (central unit-user plane (CU-UP)) and a DU node. For example, the network device may include gNB-CU-CP, gNB-CU-UP, and gNB-DU.

[0119] In some deployments, multiple RAN nodes collaborate to assist terminals in achieving wireless access, with different RAN nodes each implementing some of the base station's functions. For example, RAN nodes can be CUs, DUs, CU-CPs, CU-UPs, or RUs. CUs and DUs can be configured separately or included in the same network element, such as a BBU. RUs can be included in radio frequency equipment or radio frequency units, such as RRUs, AAUs, or RRHs.

[0120] In some deployments, the CU (Core Unit) is a logical node that carries the RRC (Resource Control Code) layer, Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, and other control functions of the access network equipment. The CU connects to network nodes such as the core network through interfaces, which may be E2 interfaces, etc. Optionally, the CU possesses some core network (CN) functions. The CU (e.g., the PDCP layer and higher) connects to the DU (e.g., the Radio Link Control (RLC) layer and lower) through interfaces, which may be F1 interfaces, etc. In some examples, these interfaces (e.g., the F1 interface) can provide control plane (CP) and user plane (UP) functions (e.g., interface management, system information management, UE context management, RRC message transmission, etc.). The F1 application protocol (F1AP) is the application protocol for the F1 interface, and in some examples, it defines the F1 signaling procedures. The F1 interface supports both the control plane (F1-C) and the user plane (F1-U).

[0121] In some deployments, the CU can be split into CU-CP and CU-UP. CU-CP is a logical node carrying the RRC layer and the control plane part of PDCP (PDCP-C) layer, used to implement the CU's control plane functions. CU-CP can interact with network elements in the core network used to implement control plane functions. These network elements in the core network can be access and mobility function network elements. CU-UP is a logical node carrying the SDAP layer and the user plane part of PDCP (PDCP-U) layer, used to implement the CU's user plane functions. CU-UP can interact with network elements in the core network used to implement user plane functions. The above CU and DU configurations are merely examples; the functions of CU and DU can be configured as needed. For example, CU or DU can be configured to have more protocol layer functions, or CU or DU can be configured to have only partial protocol layer processing functions. For example, some functions of the RLC layer and the functions of the protocol layer above the RLC layer can be placed in the CU, while the remaining functions of the RLC layer and the functions of the protocol layer below the RLC layer can be placed in the DU. Another example is that the functions of the CU or DU can be divided according to service type or other system requirements. For instance, based on latency, functions that need to meet low latency requirements can be placed in the DU, while functions that do not need to meet this latency requirement can be placed in the CU.

[0122] In some deployments, the DU (Distributed Unit) is a logical node that carries the RLC (Real-Time Control) layer, the medium access control (MAC) layer, the higher physical layer (Higher PHY) layer, and other functions. In some examples, the DU can control at least one RU (Remote Root). The DU connects to the RU through interfaces, which can be fronthaul interfaces. In some examples, the Higher PHY layer includes the PHY layer processing, such as forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation.

[0123] In some deployments, the RU is a logical node that carries both lower physical layer (PHY) and radio frequency (RF) processing. In some examples, the RU can be a TRP, RRH, or other similar entity. In some examples, the Low-PHY includes portions of the PHY processing, such as Fast Fourier Transform (FFT), Inverse Fast Fourier Transform (IFFT), digital beamforming, and filtering. The RU communicates with one or more UEs via a radio link.

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

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

[0126] In one possible design, the processing unit in the BBU used to implement baseband functions is called the baseband high (BBH) unit, and the processing unit in the RRU / AAU / RRH used to implement baseband functions is called the baseband low (BBL) unit.

[0127] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, a radio access network can also be an open radio access network (O-RAN) architecture. In an O-RAN system, CU can also be called an open CU (open CU, O-CU), DU can also be called an open DU (open DU, O-DU), CU-CP can also be called an open CU-CP (O-CU-CP), CU-UP can also be called an open CU-UP (O-CU-UP), and RU can also be called an open RU (open RU, O-RU). Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

[0128] In this embodiment, the device for implementing the functions of a network device can be a network device itself, or a device capable of supporting the network device in implementing those functions, such as a chip system, chip, circuit, or communication module (i.e., a communication module that performs communication functions). This device can be installed within the network device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices. Furthermore, the device can be configured with program instructions for performing corresponding communication functions. This embodiment only uses a network device as an example to illustrate the device for implementing the functions of a network device, and does not limit the solution of this embodiment.

[0129] Network devices and terminals can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminals are located. Furthermore, terminals and network devices can be hardware devices, software functions running on dedicated hardware, or software functions running on general-purpose hardware, such as virtualization functions instantiated on a platform (e.g., a cloud platform), or entities that include dedicated or general-purpose hardware devices and software functions. This application does not limit the specific form of the terminals and network devices.

[0130] This application's embodiments apply to a network architecture of topology 1, where AIoT devices communicate directly with network devices and execute AIoT services. This application's embodiments also apply to a network architecture of topology 2, where AIoT devices communicate with network devices through intermediate nodes. These intermediate nodes can act as readers to execute AIoT services. For example, intermediate nodes can be repeaters, integrated access backhaul (IAB) nodes, or UEs, with the UE acting as an AIoT-enabled UE to execute AIoT services. This application's embodiments also apply to a network architecture of topology 3, where AIoT devices can communicate with auxiliary nodes and / or network devices. This application's embodiments apply to a network architecture of topology 4, where AIoT devices communicate directly with terminals or terminal devices and execute AIoT services. In Topology 2, the xx interface between the AIoT-enabled gNB and the AIoT CN is an NG interface. The AIoT-enabled gNB includes the AIoT RAN node function, and the AIoT-enabled UE includes the common reader function.

[0131] Figure 1 is a schematic diagram of a communication system applicable to an embodiment of this application. As shown in Figure 1(a), the communication system includes a network device 110 and an AIoT device 120. The network device 110 and the AIoT device 120 communicate bidirectionally. The communication between the network device 110 and the AIoT device 120 includes environmental IoT data and / or signaling. That is, the network device 110 sends downlink data and / or signaling to the AIoT device 120, and the AIoT device 120 sends uplink data and / or signaling to the network device 110. It can also be understood that the network device 110 and the AIoT device 120 transmit uplink and downlink data and / or signaling.

[0132] In Topology 1, the interface between the AIoT RAN (node) and the AIoT CN is the NG-C interface (NG control plane interface). The AIoT RAN, as part of the RAN's functionality, supports AIoT-related functions. The AIoT RAN can include common reader functions and AIoT RAN node functions. The common reader function refers to the ability to communicate with AIoT devices via the AIoT interface (AIoT radio), and the AIoT RAN node function includes the ability to control AIoT radio resources.

[0133] For topology 1, network devices act as readers. The AIoT RAN (e.g., RAN) and AIoT CN (e.g., AIoTF) can be directly connected or indirectly connected. Indirect connection means the AIoT RAN connects to the AIoTF via the AMF. As shown in Figure 1(b), RAN 140 and AIoTF 130 are directly connected; as shown in Figure 1(c), RAN 170 and AIoTF 160 are indirectly connected, for example, via the AMF 180 (indirect path via AMF). That is, the AIoT data / signaling transmitted between AIoTF 160 (or AIoT CN) and RAN 170 (or replaced by AIoT RAN, or BS Reader) is carried on the NGAP.

[0134] For topology 4, as shown in Figure 1(d), the communication system includes UE 190 and AIoT device 191. UE 190 and AIoT device 191 communicate bidirectionally. The communication between UE 190 and AIoT device 191 includes environmental IoT data and / or signaling. Specifically, UE 190 sends downlink data and / or signaling to AIoT device 191, and AIoT device 191 sends uplink data and / or signaling to UE 190. Alternatively, it can be understood that UE 190 and AIoT device 191 transmit uplink and downlink data and / or signaling.

[0135] Figure 2 is a schematic diagram of another communication system applicable to embodiments of this application. As shown in Figure 2(a), the communication system includes a network device 210, an intermediate node 220, and an AIoT device 230. The network device 210 and the AIoT device 230 communicate bidirectionally with the intermediate node 220. For example, the network device 210 communicates bidirectionally with the intermediate node 220, and then the intermediate node 220 communicates bidirectionally with the AIoT device 230. That is, the network device 210 transmits uplink and downlink data and / or signaling between itself and the intermediate node 220, and the intermediate node 220 transmits uplink and downlink data and / or signaling between itself and the AIoT device 230. As shown in Figure 2(b), for the topology 2 RRC based solution, the AIoT-enabled gNB and AIoTF are directly connected, where Nx / xx can be an NG interface. This communication system includes a network device 201, a UE 202, an AIoT device 203, and an AIoTF 204. The AIoT-enabled network device 201 and the AIoTF 204 are directly connected. As shown in Figure 2(c), for the topology 2 RRC-based solution, the AIoT-enabled gNB and AIoTF are connected via AMF in a non-direct connection architecture, where Nx / xx are NG interfaces. This communication system includes network device 205, UE 206, AIoT device 207, AMF 208, and AIoTF 209. The AIoT-enabled network device 205 and AIoTF 209 are not directly connected, for example, via AMF 208 (indirect path via AMF). That is, the AIoT data / signaling transmitted between AIoTF 209 (or AIoT CN) and network device 205 (A-IoT-enabled gNB) is carried on NGAP.

[0136] The embodiments of this application are also applicable to topology 3 network architectures, where AIoT devices can communicate with auxiliary nodes or network devices. The network devices perform AIoT services, and the auxiliary nodes can be UEs or RANs, etc.

[0137] As shown in Figure 2(d), for Topology 3 with downlink assistance, the communication system includes a network device 240, an auxiliary node 250, and an AIoT device 260. The AIoT device 260 sends data and / or signaling to the network device 240, the network device 240 sends data and / or signaling to the auxiliary node 250 via the Uu interface, and then the AIoT device 260 receives data and / or signaling from the auxiliary node 250. As shown in Figure 2(e), for Topology 3 with uplink assistance, the communication system includes a network device 270, an auxiliary node 280, and an AIoT device 290. The AIoT device 290 receives data and / or signaling from the network device 270 and sends data and / or signaling to the relay node 220, and then the network device 270 receives data and / or signaling from the auxiliary node 280 via the Uu interface. Alternatively, the AIoT device 290 sends data / signaling to the network device 270 and receives data / signaling from the auxiliary node 280. In topology 3, auxiliary node 250 or auxiliary node 280 can be UE or RAN, etc., which can realize the Internet of Things.

[0138] In one implementation, the technical solution of this application can also be applied to the O-RAN system architecture.

[0139] Figure 3 is a schematic diagram of another communication system applicable to embodiments of this application. As shown in Figure 3(a), the O-RAN system may include a core network device (CN), a network device (RAN), and a terminal device (UE). The RAN communicates with the core network device via a backhaul link and with the UE via an air interface. For example, the BBU in the RAN communicates with the core network device via a backhaul link, and the RU in the RAN communicates with the UE via an air interface. The BBU communicates with the RU via a fronthaul link, wherein the BBU and RU may be co-located or not. The BBU includes at least one CU and at least one DU, and the CU and DU can communicate via at least one midhaul link. As shown in Figure 3(b), the O-RAN system includes a RAN intelligent controller (RIC). The RIC includes a near-real-time RIC (near-RT RIC) and a non-real-time RIC (non-RT RIC). Among them, the non-real-time RIC mainly processes non-real-time information, such as data that is not sensitive to latency, and the latency of this data can be on the order of seconds. Real-time RICs primarily process near-real-time information, such as latency-sensitive data with latency in the tens of milliseconds range. Optionally, near-real-time or non-real-time RICs can be configured as separate network elements; alternatively, they can be integrated into other devices. For example, near-real-time RICs can be located in RAN nodes (e.g., CUs or DUs), while non-real-time RICs can be located in operation administration and maintenance (OAM) systems, cloud servers, core network elements, or other network devices.

[0140] Figures 1 to 3 above are merely schematic diagrams for ease of understanding. The communication system to which the embodiments of this application are applicable may also include other devices, such as wireless relay devices and / or wireless backhaul devices, which are not shown in Figures 1 to 3.

[0141] Figure 4 is a schematic diagram of the protocol stack structure applicable to the communication system shown in Figure 1 or Figure 2. As shown in Figure 4, AIoT devices and AIoT-enabled UEs can exchange AIoT data and / or signaling through the AIoT radio interface. AIoT-enabled UEs and AIoT-enabled core network elements (such as AIoT CN or AIoTF) can exchange AIoT data and / or signaling through AIoT-enabled gNBs. The communication methods between the AIoT-enabled gNB and the AIoT CN can be varied, such as direct communication between the gNB and the AIoT CN, or communication between the gNB and the AIoT CN through the AMF or UPF; there are no limitations on this.

[0142] Under the Topology 2 architecture, there are currently three solutions that can be used to transmit one or more of the following: messages, data, or signaling related to AIoT services.

[0143] Solution 1: RRC-based solution.

[0144] The protocol stack for solution 1 can be seen in Figure 4(a). The AIoT device includes AIoT radio protocol layers for communication with the AIoT-enabled UE. The AIoT-enabled UE includes: the AIoT radio protocol layer for communication with the AIoT device, and the RRC layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and Physical (PHY) layer for communication with the AIoT-enabled gNB. The AIoT-enabled gNB includes: the RRC layer, PDCP layer, RLC layer, MAC layer, and PHY layer for communication with the AIoT-enabled UE, and the XXAP layer, Stream Control Transmission Protocol (SCTP) layer, Internet Protocol (IP) layer, Layer 2 (L2), and Layer 1 (L1) layer for communication with the AIoT CN. AIoT-enabled NICs (e.g., AIoT CNs) include layers such as XXAP, SCTP, IP, L2, and L1 that communicate with AIoT-enabled gNBs. This AIoT CN can be an ambient IoT function (AIoTF), or an access and mobile management function (AMF) capable of executing AIoT services or implementing AIoT functions. When an AIoT-enabled gNB receives AIoT service-related requests from the AIoT CN via XXAP, it can send the relevant information to the AIoT-enabled UE via RRC messages. Similarly, when an AIoT-enabled gNB receives AIoT service-related data / signaling from an AIoT-enabled UE via RRC messages, it can send the relevant information to the AIoT CN via XXAP. The XX interface is the NG-C interface (NG control plane interface). One possible implementation of XXAP is to include AIoTF information / cells within the NGAP; another is to carry a newly defined protocol layer on top of the NGAP protocol.

[0145] Solution 2: NAS-based solution.

[0146] The protocol stack for solution 2 can be found in Figure 4(b). The AIoT device includes an AIoT radio protocol layer that communicates with the AIoT-enabled UE. The AIoT-enabled UE includes: an AIoT radio protocol layer that communicates with the AIoT device; 5G-access network protocol layers (AN protocol layers) that communicate with the AIoT-enabled gNB; an AIoT application layer (AIoT-AP) that communicates with the AIoT CN; and a NAS layer that communicates with the AMF. The AIoT-enabled gNB includes: a 5G-access network protocol layer that communicates with the AIoT-enabled UE; and a next generation application protocol (NGAP) layer, SCTP layer, IP layer, L2 layer, and L1 layer that communicate with the AMF. The AIoT CN (e.g., AIoTF) includes: an AIoT-AP layer that communicates with the AIoT-enabled UE; and a 5GC internal protocol layer that communicates with the AMF. AMF includes: the NAS layer for communicating with AIoT-enabled UEs, the NGAP layer, SCTP layer, IP layer, L2 and L1 layer for communicating with AIoT-enabled gNBs, and the 5GC internal protocol layer for communicating with AIoT CNs.

[0147] Solution 2 can be understood as follows: at least one of the AIoT service-related messages, data, or signaling between the AIoT CN and the AIoT-enabled UE is carried in the DL NAS or UL NAS message of the AIoT-enabled UE (wherein, the AIoT-enabled gNB transparently transmits the NAS packet). The AIoT-enabled gNB can process the NAS packets of the AIoT-enabled UE through DL NAS transport messages (DL NAS Transport msg) and / or UL NAS Transport msg on the NGAP interface. In other words, the AIoT-enabled gNB does not see the AIoT-related processes; these processes are implemented within the NAS layer of the AIoT-enabled UE. A NAS layer exists between the AIoT-enabled UE and the AIoT CN for transmitting AIoT service-related information. When the AIoT CN knows about the AIoT-enabled UE and the AIoT-enabled gNB, AIoT service-related information (e.g., service requests) can be transmitted through the NAS between the AIoT-enabled UE and the AIoT CN.

[0148] Solution 3: User-plane-based solution.

[0149] The protocol stack corresponding to solution 3 can be referred to in Figure 4(c). The AIoT device includes the AIoT radio protocol layer for communication with the AIoT-enabled UE. The AIoT-enabled UE includes: the AIoT radio protocol layer for communication with the AIoT device, the 5G-access network protocol layers (AN protocol layers) for communication with the AIoT-enabled gNB, the AIoT-AP layer and transport / IP layer for communication with the AIoT CN, and the protocol data unit (PDU) layer for communication with the AMF. The AIoT-enabled gNB includes: the 5G-access network protocol layer for communication with the AIoT-enabled UE, and the GPRS tunneling protocol user plane (GTP-U) layer, user datagram protocol (UDP) layer, IP layer, L2, and L1 layers for communication with the AMF. The AIoT CN (e.g., AIoTF) includes: the AIoT-AP layer and the transport / IP layer for communicating with AIoT-enabled UEs, and the 5GC internal protocol layer for communicating with AMF-enabled UEs.

[0150] Solution 3 can be understood as follows: the gNB does not see the AIoT-related processes. AIoT service-related data / signaling between the AIoT CN and the AIoT-enabled UE can be transmitted over the PDU session of the AIoT-enabled UE (the AIoT-enabled RAN can transmit this information transparently). The AIoT-enabled RAN can process the user plane data of the AIoT-enabled UE through channels such as the next generation user plane (NG-U) or GTP-U. A PDU layer exists between the AIoT-enabled UE and the AIoT CN for transmitting AIoT service-related information. When the AIoT CN knows about the AIoT-enabled UE and the AIoT-enabled gNB, AIoT service-related information (e.g., service requests) can be transmitted through the PDU between the AIoT-enabled UE and the AIoT CN.

[0151] In Topology 1 architecture, one possible implementation of "XXAP" in the Topology 1 protocol stack is to include AIoTF information / cells in NGAP; another possible implementation is to carry a newly defined protocol layer on top of the NGAP protocol. A possible protocol stack diagram is shown in Figure 4(d). Here, the AIoT device includes an AIoT wireless protocol layer (which may include an AIoT MAC layer and an AIoT physical layer) that communicates with the AIoT RAN. The AIoT RAN includes: the AIoT wireless protocol layer that communicates with the AIoT device, and the XXAP layer, SCTP layer, IP layer, L2, and L1 that communicate with the AIoT CN. The AIoT CN (e.g., AIoTF / AMF) includes: the XXAP layer, SCTP layer, IP layer, L2, and L1 that communicate with the AIoT RAN. Optionally, the name of the xx interface between the AIoT RAN and the AIoT CN can be interchanged with the name of the Nx interface in Figure 1, without limitation. In Topology 1, the xx interface / Nx interface is the NG-C interface.

[0152] It is understood that the AIoT-enabled gNB shown in Figure 4 includes at least one of the following functions: allocating time-frequency resources for communication between AIoT-enabled UEs and AIoT devices, or transmitting AIoT service-related data and / or signaling. The AIoT CN can be at least one of the following: core network user plane equipment such as UPF, AMF, AIoT tag management function (TMF) network element, ambient IoT management function (AIoTMF), ambient IoT function (AIoTF), ambient IoT aware core network (AIoT aware CN), or other core network elements / nodes / devices that support or enable AIoT. An AIoT-enabled UE refers to a UE that is AIoT-enabled, which can be called an AIoT-enabled UE or an intermediate node. An AIoT-enabled gNB refers to a gNB that is AIoT-enabled, which can be called an AIoT-enabled gNB. An AIoT-enabled CN refers to a CN that is AIoT-enabled, which can be called an AIoT-enabled CN.

[0153] Figure 4 above is just an exemplary protocol stack corresponding to the three solutions mentioned above. This application does not exclude the possibility that it can correspond to other forms of protocol stacks, and does not impose any restrictions on this.

[0154] To facilitate understanding of the technical solution of this application, the relevant terms or technologies involved in this application are introduced.

[0155] 1. Passive Radio Frequency Identification (RFID):

[0156] Radio frequency identification (RFID) technology is a type of automatic identification technology that uses wireless radio frequency for non-contact two-way data communication. It reads and writes RFID tags using wireless radio frequency to achieve the purpose of identifying targets and exchanging data.

[0157] The primary application of RFID is identification, but it can also be used for data reading and writing. The tags have the following characteristics:

[0158] 1) The label design is simple, for example, the application layer and air interface signaling are combined into one design.

[0159] 2) The tag supports power consumption in the microwatt (μW) level or hundreds of microwatts level, but cannot support complex designs or complex measurements.

[0160] 3) When using multi-tag communication, time-division multiplexing is used, and multiple tags are read serially. It does not support the distinction between the frequency domain and the code domain, and its parallel performance is poor.

[0161] An RFID system consists of an interrogator and tags, which communicate with each other without contact. The interrogator can read information from the tag or write information to the tag. The tag itself is simple, requiring excitation from the interrogator to transmit information; it converts the wireless signal emitted by the interrogator into energy to power itself. If RFID is applied to mobile communication systems, such as 5G systems, the base station can act as the interrogator, fulfilling its functions.

[0162] 2. AIoT:

[0163] Devices in AIoT technology can include network devices and Type I terminals; or, in other words, AIoT-based communication systems can include network devices and Type I terminals. Type I terminals can be terminals with AIoT device functionality, also referred to as AIoT devices. In this case, both AIoT-enabled UEs and AIoT devices can be implemented based on cellular network infrastructure. In other words, both AIoT-enabled UEs and AIoT devices can be devices within a cellular network. For example, the functionality of an AIoT-enabled UE can be implemented by network devices, such as base stations; or, the functionality of an AIoT-enabled UE can also be implemented by a terminal. AIoT devices can also be called devices and can be implemented by terminals within a cellular network, such as ultra-low-power, ultra-low-complexity IoT terminals (e.g., Type I terminals). Network devices and Type I terminals can perform contactless data communication, thereby reading information from and / or writing information that needs to be stored into Type I terminals. AIoT technology can be used to implement one or more of the following services: inventory, positioning, sensing, or command. In terms of application scope, AIoT technology can be applied to scenarios such as logistics, warehousing, industrial manufacturing, identity recognition, or environmental monitoring.

[0164] Inventory management involves using readers (e.g., base stations or terminals) to connect to AIoT devices within the coverage area. Successfully connected devices need to send their unique identifier (identifiable by the network, such as the EPC in RFID) to the reader. Inventory management, also known as a checklist operation, retrieves tag identification information. For example, readers can use commands like `query` and `ACK` to obtain tag identification information. To facilitate tag inventory, tags include four session identifiers, each corresponding to two inventory states: A and B. The inventory state is indicated by a sessInventoried flag. When a reader selects a tag, the selection command sent to it includes a session identifier, which the tag then stores. When the reader performs inventory management on the tag, the query command sent to it includes the session identifier, at which point the tag can flip its inventory state from A to B. If the reader sends a query command to perform inventory operations again, the tag will not respond to the reader because the inventory status of the tag is B, thus avoiding the same tag being inventoried multiple times in the same inventory cycle.

[0165] Positioning is the process of using location signals to pinpoint the location of AIoT devices.

[0166] Sensing involves AIoT devices reporting sensor data to the base station, such as temperature data.

[0167] Commands are operational instructions, such as read, write, disable, enable, kill, or lock. Read commands can read the EPC, tag identifier (TID), content stored in the tag's reserved area, or content stored in the user's storage area from the tag's memory. Write commands can perform write operations on the tag's storage area; for example, a network device (e.g., a base station) can send a downlink command and data to instruct the AIoT device to write data to its storage area. Disable commands are used to request the AIoT device to permanently or temporarily disable its RF transmission capabilities. Enable commands are used to request the activation of a temporarily disabled AIoT device. Kill commands can permanently disable the tag. Lock commands can lock the tag's information, preventing read or write operations on that tag. Alternatively, locking can also lock the storage area to prevent or disallow read or write operations on that storage area. For example, a network device can send a downlink command to instruct the AIoT device to lock the location of a specified address in the storage area, making the contents of that storage area unchangeable and / or unreadable.

[0168] 3. AIoT devices:

[0169] With the evolution and development of 5G IoT, the demand for supporting lower-power terminals in 5G networks is increasing. Passive Radio Frequency Identification (RFID) technology provides a good technical reference in the low-power direction, supporting microwatt-level power consumption. RFID terminals (tags) use low-precision, low-power mid-to-low frequency ring oscillators or completely oscillator-less receivers to receive downlink signals. When the tag is working, the energy and carrier wave for communication are supplied by the reader, and communication is based on reflected carrier waves.

[0170] Given the low power consumption advantage of RFID communication technology, 5G AIoT has emerged. To meet ultra-low power consumption requirements, terminals in AIoT also use low-precision, low-power mid-to-low frequency ring oscillators or receivers without a local oscillator to receive downlink signals. This receiving method can further reduce the power consumption of downlink reception. However, for such low-power receiving methods, only amplitude detection, such as envelope detection, can be performed because a low-precision ring oscillator alone cannot guarantee accurate demodulation of signal phase information.

[0171] AIoT devices can be divided into three categories: device A, device B, and device C.

[0172] (1) Device A (similar to a passive tag): It has no energy storage, cannot generate independent signals, and uses backscattering to transmit signals.

[0173] (2) Device B (similar to a semi-passive tag): It has energy storage but cannot generate signals independently; it uses backscattering to transmit signals. The energy it stores can amplify the reflected signal.

[0174] (3) Device C (similar to an active tag): It has energy storage, can generate signals independently, and has active radio frequency (RF) components for transmission.

[0175] In addition, the following three types of AIoT devices have been further defined: device 1, device 2a, and device 2b.

[0176] (1) Device 1: Peak power consumption is approximately 1μW, with energy storage function, and initial sampling frequency offset (SFO) reaches 10. X At parts per million (ppm), it cannot amplify downlink (DL) or uplink (UL) signals. It requires an external carrier signal for backscatter communication to enable uplink transmission.

[0177] (2) Device 2a: Peak power consumption less than or equal to several hundred μW, with energy storage function, and initial sampling frequency offset of 10. X ppm can amplify DL and / or UL signals. An external carrier signal is required for backscatter communication in order to perform uplink transmission.

[0178] (3) Device 2b: Peak power consumption less than or equal to several hundred μW, with energy storage function, and initial sampling frequency offset of 10. X ppm, capable of DL and / or UL signal amplification. The device can perform uplink transmission without relying on an externally provided carrier.

[0179] 4. AIoT data and / or signaling:

[0180] AIoT data and / or signaling are related to AIoT services. For example, for inventory services, AIoT data and / or signaling may include a device ID or an encrypted device ID; for read command services, AIoT data and / or signaling may include read commands and / or read response data; for write command services, AIoT data and / or signaling may include write commands and / or write feedback; for other AIoT services, AIoT data and / or signaling may include the corresponding uplink (UL) data (UL Data) reported by the AIoT device to the AIoT-enabled UE.

[0181] The following section, in conjunction with Figures 5 and 6, explains the specific implementation methods of inventory and command services under the Topology 2 architecture.

[0182] Figure 5 is a schematic flowchart illustrating the method for executing inventory and command services under the communication system shown in Figure 2. Specifically, taking the RRC-based solution of topology 2 solution 1 as an example, the method is explained with AIoT devices, UEs, gNBs, and CNs as the execution entities. As shown in Figure 5, this method 500 may include the following steps; for details not covered, please refer to the relevant descriptions in existing protocols.

[0183] S501, the CN sends an inventory request message to the gNB; correspondingly, the gNB receives the inventory request message from the CN. The inventory request message includes an AIoT device identifier (e.g., AIoT Device ID) and a command indication (e.g., Command Indication). The AIoT device identifier identifies the AIoT device, and the command indication indicates that the AIoT device will subsequently execute a command service, or in other words, the CN will subsequently issue a command to the AIoT device for execution.

[0184] S502, gNB sends an inventory response message to CN; correspondingly, CN receives the inventory response message from gNB.

[0185] In step S503, the gNB sends an RRC message to the UE via the NR Uu interface; correspondingly, the UE receives an RRC message from the gNB via the NR Uu interface. The RRC message includes inventory information, such as the AIoT device identifier.

[0186] S504, the UE triggers (or executes) the inventory process on the AIoT wireless interface, and the specific implementation method of the inventory process is not limited.

[0187] In step S505, the UE sends an RRC message to the gNB via the NR Uu interface; correspondingly, the gNB receives the RRC message from the UE via the NR Uu interface. The RRC message includes uplink data packets, such as UL Data, carrying the AIoT Device ID.

[0188] S506, the gNB sends an inventory report (e.g., Inventory Report) to the CN; correspondingly, the CN receives the inventory report from the gNB. The inventory report includes UL Data (carrying the AIoT Device ID). Simultaneously, when reporting UL Data (carrying the AIoT Device ID) to the CN, the gNB can also assign a RAN Device XXAP ID to each AIoT Device, used to identify the AIoT Device on the XX interface.

[0189] S507, CN performs security testing on AIoT devices, without specifying the specific implementation method of the security testing (such as authentication and verification).

[0190] S508, the CN sends a downlink command transport (e.g., DL Command Transport) message, a command request message, or other NGAP messages to the gNB; correspondingly, the gNB receives the downlink command transport message, command request message, or other NGAP messages from the CN. These messages include command instructions, such as read, write, disable, deactivate, or lock commands; optionally, they also include corresponding data for the command, such as data information to be written to the AIoT device.

[0191] For example, after a successful security detection of the AIoT Device, the CN triggers a DL Command Transport, Command Request, or other NGAP message to be sent to the gNB. Simultaneously, when sending the Command, the CN can assign a CN Device XXAP ID to the Device, which is used to identify the Device on the XX interface. Therefore, the DL Command Transport message, Command Request, or other NGAP message may also include the RAN / CN Device XXAP ID.

[0192] S509, the gNB sends an RRC message to the UE; correspondingly, the UE receives the RRC message from the gNB. This RRC message includes DL Data (carrying a Command). The RRC message can be a downlink command transport (e.g., DL Command Transport) message, a Command Request message, or other RRC messages.

[0193] In step S510, the UE sends downlink transmission (e.g., DL Transport) messages or other A-IoT interface (A-IoT radio) messages (such as AIoT MAC layer or physical layer messages or indication information) to the AIoT device; correspondingly, the AIoT device receives the downlink transmission messages or other A-IoT interface (A-IoT radio) messages from the UE. These messages include commands, and optionally, also include corresponding data for the commands, such as data information to be written to the AIoT device.

[0194] In step S511, the AIoT device sends an uplink transmission (e.g., UL Transport) message or other A-IoT interface (A-IoT radio) message (such as AIoT MAC layer or physical layer messages or indication information) to the UE; correspondingly, the UE receives the uplink transmission message or other A-IoT interface (A-IoT radio) message from the AIoT device. These messages include Command Response / feedback. That is, after receiving a Command, the AIoT device executes the Command service and sends a Command Response / feedback to the UE after completing the Command service.

[0195] S512, the UE sends an RRC message to the gNB; correspondingly, the gNB receives the RRC message from the UE. This RRC message includes UL Data (carrying Command Response / feedback). The RRC message can be an uplink command transport (e.g., UL Command Transport) message, a command response message, or other RRC messages.

[0196] In step S513, the gNB sends an uplink command transport (e.g., UL Command Transport) message, a command response message, or other NGAP messages to the CN; correspondingly, the CN receives the uplink command transport message, command response message, or other NGAP messages from the gNB. These messages include Command Response / feedback. They may also include the RAN / CN Device XXAP ID.

[0197] Figure 6 is a schematic flowchart illustrating the method for executing inventory and command services under the communication system shown in Figure 2. Specifically, it uses the NAS-based solution of topology 2 solution 2 or the UP-based solution of solution 3 as examples, with AIoT devices, UE, gNB, and CN as the execution entities. As shown in Figure 6, this method 600 may include the following steps; for details not covered, please refer to the relevant descriptions in existing protocols.

[0198] S601, the CN sends an inventory request message to the UE; correspondingly, the UE receives the inventory request message from the CN. The inventory request message includes an AIoT device identifier (e.g., AIoT Device ID) and a command indication (e.g., Command Indication). The AIoT device identifier identifies the AIoT device, and the command indication indicates that the AIoT device will subsequently execute a command service, or in other words, the CN will subsequently issue a command to the AIoT device for execution.

[0199] S602, gNB sends an inventory response message to CN; correspondingly, CN receives the inventory response message from gNB.

[0200] In steps S601 and S602 above, the CN and UE can transmit AIoT-related data / signaling through the UE's NAS PDU / PDU Session (e.g., through gNB pass-through).

[0201] S603, the UE triggers (or executes) the inventory process on the AIoT wireless interface, and the specific implementation method of the inventory process is not limited.

[0202] S604, the UE sends an inventory report (e.g., Inventory Report) to the CN; correspondingly, the CN receives the inventory report from the UE. The inventory report includes UL Data (carrying the AIoT Device ID).

[0203] S605, CN performs security testing on AIoT devices, without specifying the specific implementation method of the security testing (such as authentication and verification).

[0204] S606, the CN sends a NAS / PDU Session to the UE (e.g., via a Command Request, downlink command transport, or other information, or through gNB transparent transmission); correspondingly, the UE receives the NAS / PDU Session from the CN. The NAS / PDU Session includes command instructions, such as read, write, disable, deactivate, or lock commands. Optionally, it also carries corresponding data; for example, for a write command, the NAS / PDU Session also includes the data to be written to the A-IoT device.

[0205] S607, the UE sends downlink transmission (e.g., DL Transport) messages or other A-IoT interface (A-IoT radio) messages (such as AIoT MAC layer or physical layer messages or indication information) to the AIoT device; correspondingly, the AIoT device receives the downlink transmission messages or other A-IoT interface (A-IoT radio) messages from the UE. These messages include Commands, and optionally, also include corresponding data for the Commands, such as data information to be written to the AIoT device.

[0206] In step S608, the AIoT device sends an uplink transmission (e.g., UL Transport) message or other A-IoT interface (A-IoT radio) message (such as AIoT MAC layer or physical layer messages or indication information) to the UE; correspondingly, the UE receives the uplink transmission message or other A-IoT interface (A-IoT radio) message from the AIoT device. These messages include Command Response / feedback. That is, after receiving a Command, the AIoT device executes the Command service and sends a Command Response / feedback to the UE after completing the Command service.

[0207] S609, the UE sends a NAS / PDU Session to the CN (e.g., via Command Response, uplink command transport (e.g., UL Command Transport), or other information, or through gNB pass-through); correspondingly, the CN receives the NAS / PDU Session from the UE. The NAS / PDU Session includes Command Response / feedback.

[0208] It should be noted that, for methods 500 or 600 mentioned above, the gNB can allocate AIoT resources to the UE during the inventory process for executing AIoT services (including inventory services and / or Command services), or for communication between the AIoT device and the UE on the AIoT radio interface. However, after the UE reports the inventory report, the CN may not immediately issue Command services. Therefore, before the CN issues the Command services, the AIoT device has no Command services to execute, and the AIoT resources configured by the gNB for the UE are unused, resulting in ineffective resource utilization or resource waste.

[0209] In view of this, embodiments of this application provide a communication method and a communication device that can avoid resource waste and improve resource utilization.

[0210] The method provided by the embodiments of this application will be described in detail below with reference to the accompanying drawings. The embodiments provided by this application can be applied to the communication systems shown in Figures 1 to 3 above, and are not limited thereto.

[0211] It should be noted that the following illustration uses a terminal and access network equipment as examples of the execution subjects of this interaction, but this application does not limit the execution subjects of the interaction. For example, the method executed by the access network equipment in this application can also be implemented by a module (e.g., a circuit, chip, or chip system) in the access network equipment, or a logical node, logical module, or software that can implement all or part of the network functions; as another example, the method executed by the terminal in this application can also be implemented by a communication module in the terminal or a circuit or chip in the terminal responsible for communication functions (such as a modem chip (also known as a baseband chip), or a SoC chip containing a modem core, or a SIP chip), and there is no limitation on this.

[0212] Figure 7 is a schematic diagram of a communication method 700 provided in an embodiment of this application. As shown in Figure 7, this method is applicable to RRC-based solutions, NAS-based solutions, and UP-based solutions. During the process of reporting the execution result of the first AIoT service, the terminal implicitly or explicitly instructs the access device to release or stop using the first resource, thereby avoiding resource waste. Method 700 may include the following steps; for details not covered herein, please refer to relevant descriptions in existing protocols.

[0213] S710, the access network device sends the first information to the terminal, and correspondingly, the terminal receives the first information from the access network device.

[0214] The first information indicates the first resource, which is used to execute the first AIoT service, or in other words, the first resource is used for communication between the terminal and the AIoT device(s) via the AIoT radio interface.

[0215] In this embodiment, the access network device refers to an AIoT-enabled access network device (e.g., an AIoT-enabled gNB), or an access network device that supports AIoT (e.g., an AIoT-enabled gNB). An AIoT-enabled access network device may include the function of providing resource allocation, meaning it can allocate resources to the UE to support communication between the UE and AIoT devices. The terminal refers to an AIoT-enabled terminal (e.g., an AIoT-enabled UE), or an AIoT-enabled terminal (e.g., an AIoT-enabled UE). An AIoT-enabled terminal can act as a UE reader, an intermediate node, or an intermediate UE to perform AIoT services.

[0216] For example, the first information may be an RRC message or a NAS PDU / PDU Session, and the first AIoT service may be an inventory service or other AIoT services, without limitation.

[0217] For example, the first resource can be an AIoT Radio Resource, which may include time-domain resources and / or frequency-domain resources. The effective area of ​​the first resource can be a single cell or multiple cells. The resource configuration information of the first resource includes time-domain resource configuration information and / or frequency-domain resource configuration information. Optionally, the resource configuration information may also include the maximum power transmitted by the terminal to the AIoT device. The time-domain resource configuration information can be a duration. If the terminal determines that the duration configured by the access network device is insufficient to complete the first AIoT service, the terminal can request AIoT resources (such as duration) from the access network device, and then the access network device will allocate or schedule AIoT resources (such as duration) to the terminal.

[0218] In this application, the first resource may be configured by the access network device for the terminal, or it may be configured by the DU in the access network device for the terminal; there is no limitation on this.

[0219] Optionally, the terminal uses the first resource to execute the first AIoT service and obtain the first data.

[0220] This application does not limit the specific implementation method of the terminal executing the first AIoT service to obtain the first data.

[0221] Understandably, the technical solution of this application is applicable to Topology 2 architecture. The following describes the implementation method of the terminal implicitly or explicitly instructing the terminal to release or stop using the first resource.

[0222] S720, the terminal sends second information to the access network device, and correspondingly, the access network device receives the second information from the terminal.

[0223] The second information includes first data and / or third information. The first data is associated with the first AIoT service, and the third information indicates that the first AIoT service has ended or been completed. Alternatively, the third information indicates that the first data is associated with the first AIoT service, or the third information is used to request the release or cessation of the use of the first resource.

[0224] Optionally, "stop using" in the embodiments of this application can be replaced with: pause use or suspend. The specific description is not limited, and other related parts will not be repeated.

[0225] It is understood that this implementation method is applicable to RRC-based solutions, NAS-based solutions, and UP-based solutions. That is, while reporting the execution result (i.e., the first data) of the first AIoT service (e.g., inventory service), the terminal can send third information to the access network device to explicitly instruct or request the access network device to release or stop using the first resource, so as to avoid wasting the first resource.

[0226] Scenario 1: Explicit instruction.

[0227] In one implementation, for an RRC-based solution, the second information includes first data and third information. In this case, the third information is used to request the release or cessation of the use of the first resource. That is, when the terminal reports the first data, it explicitly indicates the release or cessation of the use of the first resource.

[0228] In one implementation, for both NAS-based and UP-based solutions, since the access network device transmits information transparently, the second information includes the first data and the third information. In this case, the third information is used to request the release or cessation of the use of the first resource. That is, when the terminal reports the first data, it explicitly indicates the release or cessation of the use of the first resource; or, the third information indicates the end or completion of the first AIoT service (inventory complete indication).

[0229] For example, in an RRC-based solution, the second information can be an RRC message. The first data can be UL Data; assuming the first AIoT service is an inventory service, the UL Data can carry the AIoT Device ID. Specifically, when the second message is an RRC message, the RRC message carries UL Data and third information, where the UL Data carries the AIoT Device ID.

[0230] For example, for a NAS-based solution or an UP-based solution, the first data can be a NAS PDU / PDU Session, which carries an inventory report, and the inventory report carries the AIoT Device ID.

[0231] Optionally, the first data and / or the third information may be sent simultaneously or separately; the first data and / or the third information may be sent in the same signaling (e.g., the first information) or sent separately through different signaling, without limitation.

[0232] Scenario 2: Implicit indication.

[0233] In one implementation, for an RRC-based solution, the second information includes first data, which is associated with a first AIoT service. That is, when the terminal reports the first data, it implicitly indicates the release or cessation of the use of the first resource. Furthermore, the access network device can determine the association between the first data and the first AIoT service based on the received first data, and then instruct the terminal to release or cease the use of the first resource.

[0234] In one implementation, for both NAS-based and UP-based solutions, since the access network device transmits information transparently, the second information includes first data and third information. The third information indicates the end or completion of the first AIoT service, or it indicates that the first data is associated with the first AIoT service. That is, while the terminal reports the first data, it implicitly indicates the release or cessation of the use of the first resource through the third information. Furthermore, the access network device can determine the association between the first data and the first AIoT service based on the received first data, and then instruct the terminal to release or cease the use of the first resource.

[0235] For example, in an RRC-based solution, the second information can be an RRC message. The first data can be UL Data; assuming the first AIoT service is an inventory management service, the UL Data can carry the AIoT Device ID. Specifically, when the second message is an RRC message, the RRC message carries the UL Data, which in turn carries the AIoT Device ID. It can be understood that the UL Data is associated with the inventory management service; in other words, the UL Data is the inventory management result obtained by the UE performing the inventory management service.

[0236] For example, for a NAS-based solution or an UP-based solution, the first data can be a NAS PDU / PDU Session, and the third information can be an inventory report indication. The NAS PDU / PDU Session carries an inventory report, which in turn carries an AIoT Device ID. In this implementation, assuming the first AIoT service is an inventory service, since the access network device transparently transmits the second information, it cannot parse the first data carried in the second information, and therefore cannot determine whether the first data is associated with the first AIoT service. Therefore, the terminal can indicate the association between the first data and the first AIoT service through the third information. Specifically, the third information indicates that the first data is the inventory result obtained from performing the inventory service, thereby implicitly instructing the access network device to release or stop using the first resource.

[0237] S730, the terminal releases or stops using the first resource.

[0238] In wireless communication, "releasing the first resource" typically refers to returning wireless resources allocated to a device or application to the system under specific circumstances, so that they can be reallocated to other devices (such as other readers or applications). "Suspending the first resource" can be replaced with "pausing the use of the first resource" or "suspending the first resource," without specifying a particular name.

[0239] No specific implementation method is specified regarding the release or cessation of use of the first resource.

[0240] Understandably, the first resources released or deactivated can be used for other terminals or to perform other AIoT services in order to improve resource utilization.

[0241] Optionally, before the terminal releases or stops using the first resource, the method 700 further includes the following step S701 (not shown in the figure).

[0242] S701, the access network device sends the fourth information to the terminal, and correspondingly, the terminal receives the fourth information from the access network device.

[0243] The fourth message indicates the release or cessation of the use of the first resource.

[0244] For example, the fourth information may be an RRC message, a MAC CE, or a DCI message. That is, based on the explicit or implicit instruction from the terminal in step S720 above, the access network device feeds back the fourth information to the terminal, indicating that the access network device agrees to the terminal releasing or stopping the use of the first resource in order to avoid wasting resources.

[0245] Based on the above steps, during the execution of the first AIoT service (e.g., inventory management), the terminal simultaneously reports first data and indication information, i.e., explicitly or implicitly requesting or indicating the release or cessation of use of the first resource. Furthermore, core network elements can request the execution of a second AIoT service (e.g., a command service). Below, examples illustrating the execution of the second AIoT service are provided, using either scenario one or scenario two.

[0246] Case 1: When the third information instructs the terminal to stop using the first resource, the method 700 further includes the following step S702 (not shown in the figure).

[0247] S702, the access network device sends the fifth information to the terminal, and correspondingly, the terminal receives the fifth information from the access network device.

[0248] The fifth message indicates whether to resume or continue using the first resource.

[0249] Optionally, the method further includes: the access network device sending a seventh message to the terminal, the seventh message indicating the execution of a second AIoT service, at which time the terminal can use the first resources to execute the second AIoT service.

[0250] Optionally, the fifth and seventh messages can be sent simultaneously or separately; the fifth and seventh messages can be sent in the same signaling or sent separately through different signaling, without limitation.

[0251] For example, the fifth information can be an RRC message, and the seventh information can be a NAS PDU / PDU Session. The NAS PDU / PDU Session carries DL Data. Assuming that the second AIoT service is a command service, the DL Data carries commands, such as read, write, disable, deactivate, or lock operation instructions.

[0252] Case 2: When the third information instructs the terminal to release the first resource, the method 700 further includes the following step S703 (not shown in the figure).

[0253] S703, the access network device sends the sixth information to the terminal, and correspondingly, the terminal receives the sixth information from the access network device.

[0254] The sixth piece of information indicates the second resource, which is used to execute the second AIoT service.

[0255] Optionally, the method further includes: the access network device sending an eighth message to the terminal, the eighth message indicating the execution of a second AIoT service, at which time the terminal can use the second resources to execute the second AIoT service.

[0256] Optionally, the sixth and eighth messages can be sent simultaneously or separately; the sixth and eighth messages can be sent in the same signaling or sent separately through different signaling, without limitation.

[0257] For example, the sixth information can be an RRC message, and the seventh information can be a NAS PDU / PDU Session. The NAS PDU / PDU Session carries DL Data. Assuming that the second AIoT service is a command service, the DL Data carries commands, such as read, write, disable, deactivate, or lock operation instructions.

[0258] For example, the second resource can be an AIoT Radio Resource, which may include time-domain resources and / or frequency-domain resources. The effective area of ​​the second resource can be a single cell or multiple cells. The resource configuration information of the second resource includes time-domain resource configuration information and / or frequency-domain resource configuration information. Optionally, the resource configuration information may also include the maximum power transmitted by the terminal to the AIoT device. The time-domain resource configuration information can be a duration. If the terminal determines that the duration configured by the access network device is insufficient to complete the second AIoT service, the terminal can request AIoT resources from the access network device, and then the access network device will reallocate or schedule AIoT resources to the terminal.

[0259] Optionally, the second resource and the first resource may be the same or different, and this application does not limit this.

[0260] Optionally, in the O-RAN architecture, if the access network equipment is a CU-DU separated architecture, the CU can forward the information to the DU after receiving the information from the core network element (e.g., AIoTF); or the DU can forward the information to the CU after receiving the information from the terminal.

[0261] In one implementation, for either an RRC-based solution architecture or an UP / NAS-based solution architecture, the CU carries inventory information and AIoT resources via an F1AP message and forwards it to the DU; the DU carries first information via an F1AP message and forwards it to the CU; the CU carries an instruction to release or stop using the first AIoT resource via an F1AP message and forwards it to the DU. The remaining steps can be referred to the relevant description in Figure 7 above, and will not be repeated here.

[0262] Based on the above scheme, while reporting the execution result (first data) of the first AIoT service, the terminal implicitly or explicitly requests or instructs the release or cessation of the first resource by sending third or fifth information to the access device. The access network device then instructs the terminal to release or cease using the first resource. Thus, the terminal does not need to continuously occupy resources before issuing subsequent commands, avoiding resource waste. The access network device can then allocate the released or deactivated first resource to other terminals, improving resource utilization.

[0263] For ease of understanding, Figures 8 and 9 are used to illustrate the implementation of a terminal requesting or instructing the release or cessation of AIoT resource usage. In the examples below, the terminal is described as a UE (or AIoT UE), the access network device as a gNB (or AIoT gNB), and the core network element as a CN (or AIoT CN). In this application, the AIoT device, the terminal UE, the access network device gNB, and the core network element CN are all devices that support or enable AIoT services. It is understood that the process described below is merely illustrative, and the embodiments of this application are not limited thereto. Content not described in detail below can be referred to the relevant description in Figure 7 above, and will not be repeated here.

[0264] Figure 8 is a schematic diagram of a communication method 800 provided in an embodiment of this application. As shown in Figure 8, this method is applicable to an RRC-based solution architecture, where the terminal explicitly requests or instructs the access network device to release or stop using AIoT resources to avoid resource waste. This method may include several steps; for details not covered herein, please refer to the relevant description in Figure 5 above, which will not be repeated here.

[0265] S801, CN sends a disk storage request message to gNB; correspondingly, gNB receives the disk storage request message from CN.

[0266] The Inventory Request message includes an AIoT device identifier (such as a mask / group ID) and a command indication (such as a command indication). The AIoT device identifier is used to identify the AIoT device, or to identify one / group or all AIoT devices. The command indication is used to indicate that there are subsequent command operations in the inventory, or that CN will subsequently issue a command to the AIoT device for execution.

[0267] Optionally, the inventory request message may also include at least one of the following: a service ID, a session ID, a task ID, or a transaction ID, used to identify the AIoT service;

[0268] For example, the interface between the gNB and the CN is a first interface (XX interface). The first interface may be an NG interface, and the information exchanged on the first interface includes NGAP msg. Alternatively, the first interface may be a newly defined interface, in which case the information exchanged on the first interface includes XXAP msg, used to provide signaling services on the XX interface (e.g., AIoT business processes, such as inventory requests, inventory reporting, command issuance, command responses, etc.). In one example, the CN sends an Inventory Request to the gNB via XXAP / NGAP msg to request inventory services.

[0269] In this application embodiment, the CN that supports / enables AIoT can be at least one of the following: UPF, AMF, TMF, AIoTMF, AIoTF, AIoT-aware core network (AIoT-aware CN), or other core network elements / nodes / devices that support or enable AIoT, and the specific name is not limited.

[0270] Optionally, the gNB and CN can communicate directly (direct connection), i.e., the gNB-A-IoT CN architecture. Alternatively, the gNB can communicate with the CN through the AMF / UPF, i.e., the gNB-AMF / UPF-A-IoT CN architecture, i.e., the gNB connects to the AMF / UPF through the NG interface, and the AMF connects to the A-IoT CN.

[0271] S802, gNB sends an inventory response message to CN;

[0272] Correspondingly, CN receives inventory response messages from gNB.

[0273] S803, gNB sends inventory information and AIoT resource #1 (AIoT radio resource, i.e., the first resource) to UE;

[0274] Correspondingly, the UE receives inventory information and AIoT resource #1 from the gNB. For a detailed explanation of AIoT resource #1, please refer to the relevant description of the first resource in method 700 above, which will not be explained here.

[0275] The inventory information and AIoT resource #1 can be carried in the RRC message (i.e., the second information). The inventory information may include the AIoT device identifier, which is used to identify the AIoT device(s). The AIoT resource #1 is used to perform inventory services and command services, or in other words, for communication between the AIoT device and the UE on the AIoT radio interface.

[0276] For example, the gNB sends an RRC message to the UE via the NR Uu interface; correspondingly, the UE receives an RRC message from the gNB via the NR Uu interface. The RRC message includes inventory information and AIoT resource #1.

[0277] S804, the UE triggers (or executes) the inventory process on the AIoT wireless interface, and the specific implementation method of the inventory process is not limited.

[0278] S805, the UE sends indication information #1 (i.e., third information) and the identifier of the AIoT device (i.e., first data) to the gNB;

[0279] Correspondingly, the gNB receives indication information #1 from the UE and the identifier of the AIoT device.

[0280] Among them, the identification of AIoT devices is associated with inventory management, and indication information #1 indicates that the terminal releases or stops using AIoT resource #1.

[0281] S806, the access network device sends indication information #2 (i.e., the sixth information) to the terminal; correspondingly, the terminal receives indication information #2 from the access network device. This indication information #2 indicates the release or cessation of the use of AIoT resource #1.

[0282] For example, indication information #2 can be carried in an RRC message, MAC CE, or DCI message. That is, the gNB instructs the UE to release or stop using AIoT resources #1 based on indication information #1. In other words, the access network device agrees to the terminal releasing or stopping the use of AIoT resources to avoid wasting resources.

[0283] S807, gNB sends an inventory report (e.g., Inventory Report) to CN; correspondingly, CN receives the inventory report from gNB.

[0284] The inventory report includes UL Data (carrying the AIoT Device ID). Additionally, when the gNB reports UL Data (carrying the AIoT Device ID) to the CN, it can also assign a RAN Device XXAP ID to each AIoT Device, which is used to identify the AIoT Device on the XX interface.

[0285] S808,CN performs security testing on AIoT devices, without specifying the specific implementation method of the security testing (such as authentication and verification).

[0286] In S809, the CN sends a downlink command transport (e.g., DL Command Transport) message, a command request message, or other NGAP messages to the gNB; correspondingly, the gNB receives the downlink command transport message, command request message, or other NGAP messages from the CN. The downlink command transport message includes downlink data (DL Data) and carries command instructions, such as read, write, disable, deactivate, or lock operation instructions.

[0287] For example, after a successful security detection of the AIoT Device, the CN triggers a DL Command Transport, Command Request, or other NGAP message to be sent to the gNB. Simultaneously, when sending the Command, the CN can assign a CN Device XXAP ID to the Device, which is used to identify the Device on the XX interface. Therefore, the DL Command Transport message, Command Request, or other NGAP message may also include the RAN / CN Device XXAP ID.

[0288] S810, the gNB sends downlink data and indication information #3 to the UE; correspondingly, the UE receives downlink data and indication information #3 from the gNB.

[0289] The downlink data (DL Data) carries commands, such as read, write, disable, deactivate, or lock operation instructions, for executing command services (i.e., the second AIoT service). Indication information #3 indicates the restoration or continued use of AIoT resource #1, or indicates AIoT resource #2 (i.e., the second resource) for executing command services.

[0290] For example, downlink data and indication information #3 can be carried in an RRC message, MAC CE, or DCI message. For instance, when the gNB sends an RRC message to the UE, the RRC message includes DL Data (carrying Command) and indication information #3.

[0291] S811, the UE sends downlink data to the AIoT device; correspondingly, the AIoT device receives downlink data from the UE.

[0292] For example, downlink data can be carried in downlink transport (e.g., DL Transport) messages.

[0293] S812, the AIoT device sends uplink data (UL Data) to the UE; correspondingly, the UE receives uplink data from the AIoT device.

[0294] For example, uplink data can be carried in uplink transmission (e.g., UL Transport) messages or other A-IoT interface (A-IoT radio) messages (such as AIoT MAC layer or physical layer messages or indication information), and this application does not limit its specific name. The uplink data carries Command Response / feedback. That is, after receiving DL Data (carrying Command), the AIoT device executes the Command service and, after completing the Command service, sends UL Data (carrying Command Response / feedback) to the UE.

[0295] S813, the UE sends uplink data to the gNB; correspondingly, the gNB receives uplink data from the UE.

[0296] For example, uplink data can be carried in an RRC message, such as when the UE sends an RRC message to the gNB.

[0297] S814, the gNB sends an uplink command transmission message or command response message or other NGAP message to the CN; correspondingly, the CN receives the uplink command transmission message or command response message or other NGAP message from the gNB.

[0298] The uplink command transport message (e.g., UL Command Transport) includes uplink data (UL Data) and carries command response / feedback. It may also include the RAN / CN Device XXAP ID.

[0299] Optionally, in the O-RAN architecture, the gNB is a CU-DU separated architecture. For the RRC-based solution architecture or the UP / NAS-based solution architecture, after the CU receives information from the CN (e.g., the inventory request message in step S801, or the downlink command transmission message in step S809), it can forward the information to the DU; or, after the DU receives information from the UE (e.g., the indication information #1 and the AIoT device identifier in step S805, or the uplink data in step S813), it can forward the information to the CU. The remaining steps can be referred to the relevant description in Figure 8 above, and will not be repeated here.

[0300] Based on the above scheme, when the UE reports the AIoT Device ID, it displays an instruction / instruction to the gNB to release or stop using AIoT resources. The gNB then instructs the UE to release or stop using AIoT resources via RRC messages or DCI, thus eliminating the need for the UE to continuously occupy resources before the CN issues a command, avoiding resource waste. The gNB can subsequently instruct the UE to resume or continue using the released AIoT resources via RRC messages or DCI. Furthermore, the gNB can allocate the released or stopped AIoT resources to other UE readers, improving resource utilization.

[0301] Figure 9 is a schematic diagram of a communication method 900 provided in an embodiment of this application. As shown in Figure 9, this method is applicable to UP / NAS-based solution architectures. The terminal explicitly or implicitly requests or instructs the access network device to release or stop using AIoT resources to avoid resource waste. The method 900 may include several steps, and the parts not detailed here can be referred to the relevant descriptions in Figure 8 or Figure 6 above, which will not be repeated here.

[0302] S901, CN sends an AIoT indication and a NAS PDU / PDU session to the gNB;

[0303] Correspondingly, the gNB receives AIoT indication and NAS PDU / PDU Session from the CN.

[0304] The NAS PDU / PDU Session carries an Inventory Request message. For a detailed explanation of the Inventory Request message, please refer to the relevant description of step S801 in method 800 above.

[0305] For example, the CN can explicitly indicate an AIoT indicator on the NG / XX interface to indicate AIoT services, and the gNB can subsequently allocate AIoT resources to the UE based on this AIoT indicator.

[0306] Optionally, the CN may not send an AIoT indication. In this case, after the UE receives the Inventory Request included in the NAS PDU / PDU Session, it can request AIoT resources from the gNB via an RRC message, and then the gNB can send the AIoT resources to the UE via an RRC message.

[0307] Optionally, the CN can send an AIoT resource request to the gNB via NGAP / XXAP. For example, the CN can request the gNB to allocate AIoT resources for the current AIoT session / service (e.g., send an AIoT session resource request), or the CN can request the gNB to allocate AIoT resources for one or more specified UE Readers. Alternatively, the CN can first initiate the AIoT resource request process with the gNB, and then the CN can communicate with the AIoT device via a NAS / UP-based solution; or, the above-mentioned process of the CN requesting AIoT resources from the gNB can be performed simultaneously with the communication based on the NAS / UP-based solution.

[0308] S902, gNB sends AIoT resource #1 (AIoT radio resource, i.e., the first resource) and NAS PDU / PDU Session to UE;

[0309] Correspondingly, the UE receives AIoT resource #1 and NAS PDU / PDU Session from the gNB.

[0310] For a detailed explanation of AIoT resource #1, please refer to the relevant description of method 800 above, which will not be repeated here.

[0311] S903, the UE sends an inventory response message to the CN; correspondingly, the CN receives the inventory response message from the UE. For example, the UE sends the inventory response message to the CN via the gNB.

[0312] Understandably, in the above steps S901-S903, the CN and UE can transmit AIoT-related data / signaling through the UE's NAS PDU / PDU Session (e.g., through gNB pass-through).

[0313] S904, the UE triggers (or executes) the inventory process on the AIoT wireless interface, and the specific implementation method of the inventory process is not limited.

[0314] S905, the UE sends an inventory report indication (i.e., the fifth information) or indication information #a (i.e., the third information) and a NAS PDU / PDU Session to the gNB; correspondingly, the gNB receives the indication information #a and the identifier of the AIoT device from the UE.

[0315] The NAS PDU / PDU Session carries an inventory report, which includes the identifier of the AIoT device. For a detailed explanation of the inventory report, please refer to the relevant description in Method 800 above. The AIoT device identifier is associated with the inventory service. The indication information #a indicates that the terminal releases or stops using AIoT resources #1. The inventory report indication is used to indicate the association between the inventory report and the inventory service.

[0316] Understandably, instruction information #a corresponds to an explicit instruction or instruction to the terminal to release or stop using AIoT resource #1, and inventory report instruction corresponds to an implicit instruction or instruction to the terminal to release or stop using AIoT resource #1.

[0317] S906, the access network device sends indication information #b to the terminal; correspondingly, the terminal receives indication information #b from the access network device. This indication information #b indicates the release or cessation of use of AIoT resource #1.

[0318] For example, the indication information #b can be carried in an RRC message, a MAC CE message, or a DCI message. That is, the gNB instructs the UE to release or stop using AIoT resource #1 based on the indication information #b. In other words, the access network device agrees to the terminal releasing or stopping using AIoT resource #1 to avoid wasting resources.

[0319] S907, the gNB sends a NAS PDU / PDU Session to the CN; correspondingly, the CN receives the NAS PDU / PDU Session from the gNB.

[0320] The NAS PDU / PDU Session contains inventory reports.

[0321] S908, CN performs security testing on AIoT devices, without specifying the specific implementation method of the security testing (such as authentication and verification).

[0322] In S909, the CN sends a NAS PDU / PDU Session to the gNB (e.g., via a Command Request, downlink command transport, or other information, which the gNB then transmits transparently); correspondingly, the gNB receives the NAS PDU / PDU Session from the CN (e.g., via a Command Request, downlink command transport, or other information). The NAS PDU / PDU Session includes downlink data (DL Data) and carries Command instructions, such as read, write, disable, deactivate, or lock commands.

[0323] For example, after the AIoT Device security detection is successful, the CN triggers a NAS PDU / PDU Session to be sent to the gNB, carrying downlink data.

[0324] S910, the gNB sends the NAS PDU / PDU Session and indication information #c to the UE; correspondingly, the UE receives the NAS PDU / PDU Session and indication information #c from the gNB.

[0325] The NAS PDU / PDU Session carries downlink data for executing command services (i.e., the second AIoT service). The indication information #c indicates the resumption or continued use of AIoT resource #1, or indicates AIoT resource #2 (i.e., the second resource) for executing command services. The indication information #c can be included in RRC, MAC CE, or DCI.

[0326] Optionally, AIoT resource #1 and AIoT resource #2 may be the same or different, and there is no limitation on this.

[0327] Optionally, the NAS PDU / PDU Session and the indication information #c can be sent simultaneously or independently. Understandably, the gNB needs to know that the service is an AIoT service (e.g., a command service) before sending the indication information #c to the UE. For example, if the NAS PDU / PDU Session and the indication information #c can be sent simultaneously, in step S909, the CN sends a command request message to the gNB, carrying the NAS PDU / PDU Session; or, in step S909, the CN also sends a command service indication (or AIoT service indication or AIoT service type indication) to the gNB to indicate that the service is a command service; if the NAS PDU / PDU Session and the indication information #c are sent independently, the gNB can receive the request message from the UE after sending the NAS PDU / PDU Session and then send the indication information #c, without limitation.

[0328] S911, the UE sends a command to the AIoT device through MAC layer information or physical layer information of the AIoT interface (AIoT radio);

[0329] Correspondingly, the AIoT device receives a command from the UE.

[0330] S912, the AIoT device sends uplink data (UL Data) to the UE; correspondingly, the UE receives uplink data from the AIoT device.

[0331] For example, uplink data can be carried in uplink transmission (e.g., UL Transport) messages or other A-IoT interface (A-IoT radio) messages (such as AIoT MAC layer or physical layer messages or indication information). The uplink data carries a Command Response / feedback. That is, after receiving DL Data (carrying a Command), the AIoT device executes the Command service and, after completing the Command service, sends UL Data (carrying a Command Response / feedback) to the UE.

[0332] S913, the UE sends uplink data to the gNB; correspondingly, the gNB receives uplink data from the UE.

[0333] S914, the gNB sends a command response message or NAS / PDU Session to the CN (e.g., via command response, uplink command transport, or other information, which the gNB transmits transparently); correspondingly, the CN receives the command response message or NAS / PDU Session from the gNB (e.g., via command response, uplink command transport, or other information, which the gNB transmits transparently).

[0334] Command response / feedback messages can be carried in uplink UL data, and uplink UL data can be carried in uplink command transport messages (e.g., UL Command Transport messages).

[0335] Optionally, in the O-RAN architecture, the gNB is a CU-DU separated architecture. For the RRC-based solution architecture or the UP / NAS-based solution architecture, after the CU receives the information from the CN (e.g., the AIoT indication and NAS PDU / PDU Session in step S901, or the NAS PDU / PDU Session in step S909), it can forward the information to the DU; or, after the DU receives the information from the UE (e.g., the inventory report indication / indication information #a and NAS PDU / PDU Session in step S905, or the indication information #c and NAS PDU / PDU Session in step S910), it can forward the information to the CU. The remaining steps can be referred to the relevant description in Figure 9 above, and will not be repeated here.

[0336] Based on the above scheme, when the UE reports the AIoT Device ID, it displays an instruction / instruction to the gNB to release or stop using AIoT resources. The gNB then instructs the UE to release or stop using AIoT resources via RRC messages or DCI, thus eliminating the need for the UE to continuously occupy resources before the CN issues a command, avoiding resource waste. The gNB can subsequently instruct the UE to resume or continue using the released AIoT resources via RRC messages or DCI. Furthermore, the gNB can allocate the released or stopped AIoT resources to other UE readers, improving resource utilization.

[0337] Figure 10 is a schematic diagram of a communication method 1000 provided in an embodiment of this application. As shown in Figure 10, this method is applicable to an RRC-based solution. During the process of reporting the execution result of a first AIoT service, the terminal implicitly instructs the access device to release or stop using the first resource, thereby avoiding resource waste. The method 1000 may include the following steps; for details not covered herein, please refer to the relevant description in Figure 7 above.

[0338] S1010, the access network device sends the first information to the terminal, and correspondingly, the terminal receives the first information from the access network device.

[0339] The first information indicates the first resource, which is used to execute the first AIoT service, or in other words, the first resource is used for communication between the terminal and the AIoT device(s) via the AIoT radio interface.

[0340] For example, the first information can be an RRC message, and the first AIoT service can be an inventory service.

[0341] For example, the first resource may be an AIoT Radio Resource, which may include time-domain resources and / or frequency-domain resources, etc. For a specific interpretation of the first resource, please refer to the relevant description of S710 in Figure 7 above.

[0342] S1020, the terminal sends the second information to the access network device, and correspondingly, the access network device receives the second information from the terminal.

[0343] The second information includes the first data, which is associated with the first AIoT business.

[0344] For example, the second information could be an RRC message.

[0345] It is understood that this implementation method is applicable to RRC-based solutions. That is, after the terminal reports the execution result (i.e., the first data) of the first AIoT service (e.g., inventory service), the access network device can know that the first data is associated with the first AIoT service, and thus instruct the terminal to release or stop using the first resource. In other words, the terminal implicitly instructs or requests the access network device to release or stop using the first resource to avoid wasting the first resource.

[0346] S1030, the access network device determines, based on the second information, that the terminal instructs the terminal to release or stop using the first resource.

[0347] In one implementation, the access network device determines, based on the second information, that the first data is associated with the first AIoT service. Then, based on the association between the first data and the first AIoT service, it determines whether the terminal instructs the terminal to release or stop using the first resource. That is, the terminal implicitly instructs or requests the access network device to release or stop using the first resource to avoid wasting it.

[0348] S1040, the terminal releases or stops using the first resource.

[0349] For a detailed explanation and implementation of releasing or ceasing the use of the first resource, please refer to the relevant description of method 700 above.

[0350] Understandably, the first resources released or deactivated can be used for other terminals or to perform other AIoT services in order to improve resource utilization.

[0351] Optionally, before the terminal releases or stops using the first resource, the method 1000 further includes the following step S1001 (not shown in the figure).

[0352] S1001, the access network device sends third information to the terminal, and correspondingly, the terminal receives the third information from the access network device. This third information indicates the release or cessation of use of the first resource.

[0353] For example, the third information may be an RRC message, a MAC CE, or a DCI message. That is, based on the terminal's implicit instruction in step S1020 above to release or stop using the first resource, the access network device feeds back the third information to the terminal, that is, the access network device agrees to the terminal releasing or stopping using the first resource in order to avoid wasting resources.

[0354] Based on the above steps, during the execution of the first AIoT service (e.g., inventory management), the terminal reports the first data associated with the first AIoT service, implicitly instructing the terminal to release or cease using the first resource. Furthermore, core network elements can request the execution of a second AIoT service (e.g., a command service). Below, examples illustrating the execution of the second AIoT service are provided, using either scenario one or scenario two.

[0355] Case 1: If the third information indicates that the use of the first resource should be stopped, the method 1000 further includes the following step S1002 (not shown in the figure).

[0356] S1002, the access network device sends fourth information to the terminal, and correspondingly, the terminal receives the fourth information from the access network device. This fourth information includes fifth and sixth information; the fifth information indicates the execution of a second AIoT service, and the sixth information indicates the resumption or continued use of the first resource.

[0357] For example, the fourth message can be an RRC message, and the fifth message can be DL Data. Assuming that the second AIoT service is a command service, the DL Data carries commands, such as read, write, disable, deactivate, or lock operation instructions.

[0358] Optionally, the terminal may use the first resource to execute a second AIoT service.

[0359] Case 2: When the third information indicates the release of the first resource, the method 1000 further includes the following step S1003 (not shown in the figure).

[0360] S1003, the access network device sends the seventh information to the terminal, and correspondingly, the terminal receives the seventh information from the access network device.

[0361] The seventh information includes the eighth and ninth information. The eighth information indicates the execution of the second AIoT service, and the ninth information indicates the second resource, which is used to execute the second AIoT service.

[0362] In one implementation, the terminal uses a second resource to execute a second AIoT service.

[0363] For example, the seventh message can be an RRC message, and the eighth message can be DL Data. Assuming that the second AIoT service is a command service, the DL Data carries commands, such as read, write, disable, deactivate, or lock operation instructions.

[0364] For example, the second resource can be an AIoT Radio Resource, which may include time-domain resources and / or frequency-domain resources, etc. For a specific interpretation of the second resource, please refer to the relevant description of S1003 in Figure 10 above.

[0365] Optionally, the second resource and the first resource may be the same or different, and this application does not limit this.

[0366] Optionally, in the O-RAN architecture, if the access network equipment is a CU-DU separated architecture, the CU can forward the information to the DU after receiving the information from the core network element (e.g., AIoTF); or the DU can forward the information to the CU after receiving the information from the terminal.

[0367] In one implementation, for an RRC-based solution architecture, the CU carries inventory information and AIoT resources via an F1AP message and forwards it to the DU; the DU carries first information via an F1AP message and forwards it to the CU; the CU carries an instruction to release or stop using the first AIoT resource via an F1AP message and forwards it to the DU. The remaining steps can be referred to the relevant description in Figure 10 above, and will not be repeated here.

[0368] Based on the above scheme, after executing the first AIoT service, the terminal reports the first data associated with the first AIoT service, implicitly requesting or instructing the release or cessation of the use of the first resource. The access network device then instructs the terminal to release or cease using the first resource. Thus, during the period before subsequent command issuance, the terminal does not need to continuously occupy resources, avoiding resource waste. The access network device can then allocate the released or deactivated first resource to other terminals, improving resource utilization.

[0369] For ease of understanding, Figure 11 is used as a reference to illustrate the implementation of a terminal requesting or instructing the release or cessation of AIoT resource usage. In the examples below, the terminal is described as a UE (or AIoT UE), the access network device as a gNB (or AIoT gNB), and the core network element as a CN (or AIoT CN). In this application, the AIoT device, the terminal UE, the access network device gNB, and the core network element CN are all devices that support or enable AIoT services. It is understood that the process described below is merely illustrative, and the embodiments of this application are not limited thereto. Content not described in detail below can be referred to the relevant descriptions in Figure 10 above, and will not be repeated here.

[0370] Figure 11 is a schematic diagram of a communication method 1100 provided in an embodiment of this application. As shown in Figure 11, this method is applicable to an RRC-based solution architecture, where the terminal explicitly requests or instructs the access network device to release or stop using AIoT resources to avoid resource waste. This method may include the following steps; for details not covered herein, please refer to the relevant descriptions in Figure 8 or Figure 5 above. The only difference from Figure 8 is the description of step S1105.

[0371] S1101, CN sends an inventory request message to gNB; correspondingly, gNB receives the inventory request message from CN.

[0372] For a detailed explanation of the Inventory Request message, please refer to the relevant description of step S801 in method 800 above.

[0373] S1102, gNB sends an inventory response message to CN; correspondingly, CN receives the inventory response message from gNB.

[0374] For a detailed explanation of the Inventory Response message, please refer to the relevant description of step S801 in method 800 above.

[0375] S1103, gNB sends inventory information and AIoT resource #1 (AIoT radio resource, i.e., the first resource) to UE;

[0376] Correspondingly, the UE receives inventory information and AIoT resource #1 from the gNB.

[0377] For a detailed explanation of inventory information and AIoT resource #1, please refer to the relevant description of step S803 of method 800 above.

[0378] S1104, the UE triggers (or executes) the inventory process on the AIoT wireless interface, and the specific implementation method of the inventory process is not limited.

[0379] S1105, the UE sends the identifier of the AIoT device (i.e., the first data) to the gNB;

[0380] Correspondingly, the gNB receives the identifier of the AIoT device from the UE. The identifier of the AIoT device is associated with the inventory service.

[0381] For example, the identifier of an AIoT device can be carried in an RRC message (e.g., second information).

[0382] S1106, The access network device sends instruction information #2 (i.e., third information) to the terminal;

[0383] Correspondingly, the terminal receives instruction information #2 from the access network device.

[0384] Among them, instruction #2 indicates the release or cessation of use of AIoT resource #1.

[0385] S1107, gNB sends an inventory report to CN; correspondingly, CN receives the inventory report from gNB.

[0386] For a detailed explanation of inventory reports (e.g., Inventory Report), please refer to the relevant description of step S807 of method 800 above.

[0387] S1108, CN performs security testing on AIoT devices.

[0388] S1109, the CN sends a downlink command transport (e.g., DL Command Transport) message, a command request message, or other NGAP messages to the gNB; correspondingly, the gNB receives the downlink command transport message, command request message, or other NGAP messages from the CN.

[0389] For a detailed explanation of the downlink command transmission message, please refer to the relevant description of step S809 in method 800 above.

[0390] S1110, the gNB sends downlink data (i.e., the fifth or eighth information) and indication information #3 (i.e., the sixth or ninth information) to the UE; correspondingly, the UE receives the downlink data and indication information #3 from the gNB.

[0391] For a detailed explanation of the downlink data and indication information #3, please refer to the relevant description of step S810 in method 800 above.

[0392] S1111, the UE sends downlink data to the AIoT device; correspondingly, the AIoT device receives downlink data from the UE.

[0393] For example, downlink data can be carried in downlink transport (e.g., DL Transport) messages.

[0394] S1112, the AIoT device sends uplink data (UL Data) or other A-IoT interface (A-IoT radio) messages (such as AIoT MAC layer or physical layer messages or indication information) to the UE; correspondingly, the UE receives uplink data from the AIoT device.

[0395] For example, uplink data can be carried in uplink transmissions (e.g., UL Transport) messages. The uplink data carries a Command Response / feedback.

[0396] S1113, the UE sends uplink data to the gNB; correspondingly, the gNB receives uplink data from the UE.

[0397] For example, uplink data can be carried in an RRC message, such as when the UE sends an RRC message to the gNB.

[0398] S1114, the gNB sends an uplink command transmission message or command response message or other NGAP message to the CN; correspondingly, the CN receives the uplink command transmission message or command response message or other NGAP message from the gNB.

[0399] The uplink command transport message (e.g., UL Command Transport) includes uplink data (UL Data) and carries Command Response / feedback.

[0400] Optionally, in the O-RAN architecture, the gNB is a CU-DU separated architecture. For the RRC-based solution architecture, after the CU receives information from the CN (e.g., the inventory request message in step S1101, or the downlink command transmission message in step S1109), it can forward the information to the DU; or, after the DU receives information from the UE (e.g., the AIoT device identifier in step S1105, or the uplink data in step S1113), it can forward the information to the CU. The remaining steps can be referred to the relevant description in Figure 11 above, and will not be repeated here.

[0401] Based on the above scheme, when the UE reports the AIoT Device ID after performing inventory services, it implicitly indicates to the gNB / instructs the terminal to release or stop using AIoT resources. The gNB then instructs the UE to release or stop using AIoT resources via RRC messages or DCI, thus avoiding continuous resource occupation by the UE before the CN issues a command, preventing resource waste. The gNB can subsequently instruct the UE to resume or continue using the released AIoT resources via RRC messages or DCI. Furthermore, the gNB can allocate the released or stopped AIoT resources to other UE readers, improving resource utilization.

[0402] Figure 12 is a schematic diagram of a communication method 1200 provided in an embodiment of this application. As shown in Figure 12, this method is applicable to RRC-based solutions, NAS-based solutions, and UP-based solutions. The access network device configures an effective timer / period pattern to the terminal, and uses the timer / period pattern / duration to align with the terminal to release or suspend A-IoT resources, thereby avoiding resource waste. This method 1200 may include the following steps; for details not covered herein, please refer to the relevant description in Figure 7 above.

[0403] S1210, The access network device sends the first information and / or the second information to the terminal;

[0404] Correspondingly, the terminal receives first information and / or second information from the access network device.

[0405] The first information indicates the first resource, which is used to execute the first AIoT service, or in other words, the first resource is used for communication between the terminal and the AIoT device(s) via the AIoT radio interface. The second information indicates the time for ceasing the use of the first resource.

[0406] For example, the first information may be an RRC message or a NAS PDU / PDU Session, and the first AIoT service may be an inventory service.

[0407] For example, the first resource may be an AIoT Radio Resource, which may include time-domain resources and / or frequency-domain resources, etc. For a specific interpretation of the first resource, please refer to the relevant description of step S710 in Figure 7 above.

[0408] For example, the second information indicates a first timer, or indicates a first time period and a second time period (period pattern), or indicates a first duration.

[0409] For example, after receiving the first timer or the first duration, the terminal can start the timer / duration.

[0410] S1220, Optionally, the terminal sends third information to the access network device, and correspondingly, the access network device receives the third information from the terminal.

[0411] The second information includes the first data, which is associated with the first AIoT business.

[0412] It is understood that this implementation method is applicable to RRC-based solutions, NAS-based solutions, and UP-based solutions. That is, after the terminal executes the first AIoT service (e.g., inventory management service), it reports the execution result of the first AIoT service (i.e., the first data).

[0413] For example, in an RRC-based solution, the second information can be an RRC message. The first data can be UL Data; assuming the first AIoT service is an inventory service, the UL Data can carry the AIoT Device ID. Specifically, when the second message is an RRC message, the RRC message carries the UL Data, where the UL Data carries the AIoT Device ID.

[0414] For example, for a NAS-based solution or an UP-based solution, the first data can be a NAS PDU / PDU Session, which carries an inventory report, and the inventory report carries the AIoT Device ID.

[0415] S1230, the terminal uses the first resource to execute the first AIoT service; and / or, releases or stops using the first resource according to the second information.

[0416] For a detailed explanation and implementation of releasing or ceasing the use of the first resource, please refer to the relevant description of step S730 in method 700 above.

[0417] Understandably, the first resources released or deactivated can be used for other terminals or to perform other AIoT services in order to improve resource utilization.

[0418] In one implementation, if the second information in step S1210 indicates the first timer, the terminal can stop using the first resource during the first timer's operation; and after the first timer expires, it can resume use (or continue using) or release the first resource. For example, if the first timer's duration is 1 hour, the terminal can start the first timer while sending the third information. Within 1 hour after the first timer starts, the first resource is stopped, and the terminal cannot use the first resource. After the first timer expires, that is, after 1 hour, the terminal can resume use or continue using the first resource, for example, using the first resource to perform other AIoT services (such as a second AIoT service). For example, if the access network device sends a fourth information to the terminal to indicate the execution of a second AIoT service, the terminal receives the fourth information from the access network device, and after the first timer expires, it continues to use the first resource to execute the second AIoT service.

[0419] In one implementation, if the second information in step S1210 indicates a first time period and a second time period (period pattern), the terminal can stop using the first resource during the first time period; and resume use (or continue use) or release the first resource during the second time period. For example, if the first time period is time slot 1 to time slot 3 and the second time period is time slot 4 to time slot 8, the terminal can stop using the first resource during time slots 1 to 3, meaning the terminal cannot use the first resource during time slots 1 to 3; and during time slots 4 to 8, the terminal can resume use or continue using the first resource, for example, using the first resource to perform other AIoT services (e.g., a second AIoT service). For example, if the access network device sends fourth information to the terminal to instruct the execution of a second AIoT service, the terminal receives the fourth information from the access network device and continues to use the first resource to execute the second AIoT service during the second time period.

[0420] In one implementation, if the second information in step S1210 indicates a first duration, the terminal can stop using the first resource within the duration; and resume use (or continue use) or release the first resource after the first duration ends. Optionally, the time unit of the first duration can be absolute time (e.g., minutes / seconds / milliseconds) or relative time (e.g., superframes / frames / subframes / slots / symbols). Optionally, the first duration can be a period of time, such as 1 hour, or it can be represented by specific time information (e.g., from x o'clock x minutes x seconds to y o'clock y minutes y seconds), etc., which is not limited in this application. Optionally, the start time of the first duration can be when the terminal reports the third information (e.g., UL Data (device ID)), which is not limited in this application. For example, if the access network device sends fourth information to the terminal to instruct the execution of a second AIoT service, the terminal receives the fourth information from the access network device and continues to use the first resource to execute the second AIoT service after the first duration ends.

[0421] Optionally, if the terminal releases the first resource after the first timer expires, or during the second time period, or after the first duration ends, then when a subsequent access network device requests the terminal to execute the second AIoT service, it can allocate the second AIoT resource to the terminal for executing the second AIoT service. The second resource and the first resource may be the same or different; this application does not impose any limitation on this.

[0422] Optionally, in the O-RAN architecture, if the access network equipment is a CU-DU separated architecture, the CU can forward the information to the DU after receiving the information from the core network element (e.g., AIoTF); or the DU can forward the information to the CU after receiving the information from the terminal.

[0423] In the embodiments of this application, "after timeout" can be replaced with "when timeout", "after completion" can be replaced with "when completion", and "within time period" can be replaced with "during time period". Other relevant parts of the text will not be repeated.

[0424] In one implementation, for either an RRC-based solution architecture or a UP / NAS-based solution architecture, the CU carries inventory information and AIoT resources via an F1AP message and forwards it to the DU; the DU carries first information via an F1AP message and forwards it to the CU; the CU carries an instruction to release or stop using the first AIoT resource via an F1AP message and forwards it to the DU. The remaining steps can be referred to the relevant description in Figure 12 above, and will not be repeated here.

[0425] Based on the above scheme, while allocating the first resource, the access network device sends a second message to the terminal, indicating the time for stopping the use of the first resource. This allows the terminal to stop using the first resource during the first timer's operation or within the first time period, and to continue using or resume using the first resource after the first timer expires or within the second time period. This avoids resource waste and improves resource utilization.

[0426] For ease of understanding, Figures 13 and 14 are used to illustrate the implementation method of stopping the use of AIoT resources by the terminal. In the examples below, the terminal is UE (or AIoT UE), the access network device is gNB (or AIoT gNB), and the core network element is CN (or AIoT CN) as the execution subject. In this application, the AIoT device, terminal UE, access network device gNB, and core network element CN are all devices that support or enable AIoT services. It is understood that the process described below is only an example, and the embodiments of this application are not limited thereto. Content not described in detail below can be referred to the relevant description in Figure 12 above, and will not be repeated here.

[0427] Figure 13 is a schematic diagram of a communication method 1300 provided in an embodiment of this application. As shown in Figure 13, this method is applicable to an RRC-based solution architecture. The access network device configures an effective Timer / period pattern / duration to the terminal, and uses the timer / period pattern / duration to align with the UE to stop using AIoT resources, thereby avoiding resource waste. This method may include the following multiple steps.

[0428] S1301, CN sends an Inventory Request message to gNB;

[0429] Correspondingly, the gNB receives inventory request messages from the CN.

[0430] S1302, gNB sends an inventory response message to CN;

[0431] Correspondingly, CN receives inventory response messages from gNB.

[0432] For the specific implementation of steps S1301 and S1302 above, please refer to the relevant descriptions of steps S801 and S802 in method 800 above.

[0433] S1303, gNB sends inventory information, AIoT resource #1 (AIoT radio resource, i.e., the first resource), duration (i.e., the first duration), and Timer / period pattern (i.e., the first time period and the second time period) (i.e., the second information) to UE.

[0434] Correspondingly, the UE receives inventory information, AIoT resource #1, and Timer / period pattern / duration from the gNB.

[0435] For a detailed explanation of inventory information and AIoT resource #1, please refer to the relevant description of step S803 of method 800 above.

[0436] For example, after the UE receives a valid timer or duration, it can enable the timer / duration.

[0437] Optionally, inventory information, AIoT resource #1, and Timer / period pattern / duration can be carried in the RRC message (i.e., the second message).

[0438] S1304, the UE triggers (or executes) the inventory process on the AIoT wireless interface, and the specific implementation method of the inventory process is not limited.

[0439] S1305, the UE sends the identifier of the AIoT device (i.e., the first data) to the gNB;

[0440] Correspondingly, the gNB receives the identifier of the AIoT device from the UE.

[0441] Among them, the identification of AIoT devices is associated with inventory management.

[0442] S1306, the UE stops or resumes using AIoT resource #1 according to Timer / period / pattern / duration;

[0443] In one implementation, the UE stops or resumes using AIoT resource #1 based on a Timer. Specifically, the UE can stop using AIoT resource #1 during the Timer's operation; and after the Timer expires, it can resume using (or continue using) or release AIoT resource #1. For example, if the Timer duration is 1 hour, the UE can start the Timer while sending the identifier of the AIoT device. During the 1 hour after the Timer starts, AIoT resource #1 is stopped, and the UE cannot use it. After the Timer expires, that is, after 1 hour, the UE can resume using or continue using AIoT resource #1, for example, to perform other AIoT services (such as a second AIoT service). For instance, the gNB sends a fourth message to the UE to instruct the execution of a second AIoT service. Correspondingly, the UE receives the fourth message from the gNB, and after the first timer expires, it continues to use the first resource to execute the second AIoT service.

[0444] Optionally, after the Timer expires, the UE can release AIoT resource #1. When the access network device subsequently sends the fourth information to indicate the execution of the second AIoT service, it can reallocate AIoT resource #2 (i.e., the second AIoT resource). AIoT resource #1 and AIoT resource #2 can be the same or different, and there is no limitation on this.

[0445] In one implementation, the UE stops or resumes using AIoT resource #1 according to a periodic pattern. Specifically, the periodic pattern indicates time periods T1 and T2. The UE can stop using AIoT resource #1 during time period T1, meaning the terminal cannot use AIoT resource #1 during time period T1; and resume using (or continue using) or release AIoT resource #1 during time period T2, meaning the UE can continue using AIoT resource #1 or AIoT resource #2 (reassigned by the access network device) to perform other AIoT services (e.g., a second AIoT service). For example, the gNB sends a fourth message to the UE to instruct the execution of a second AIoT service. Correspondingly, the UE receives the fourth message from the gNB and continues to use AIoT resource #1 to perform the second AIoT service during time period T2.

[0446] In one implementation, the UE stops or resumes using AIoT resource #1 based on a duration. Specifically, the UE can stop using AIoT resource #1 within the duration; and resume using (or continue using) or release AIoT resource #1 after the duration ends. For example, if the duration is 1 hour, specifically from 10:00:00 to 11:00:00, the UE can send the identifier of the AIoT device at 10:00:00 and start timing, at which point AIoT resource #1 is stopped, meaning the UE cannot use AIoT resource #1. After the 1-hour timeout, that is, after 11:00:00, the UE can resume using or continue using AIoT resource #1, for example, to perform other AIoT services (such as a second AIoT service). For instance, the access network device sends a fourth message to the terminal to instruct the execution of a second AIoT service. Correspondingly, the terminal receives the fourth message from the access network device and continues to use the first resource to execute the second AIoT service after the first duration ends.

[0447] S1307, gNB sends an inventory report to CN; correspondingly, CN receives the inventory report from gNB.

[0448] For a detailed explanation of inventory reports (e.g., Inventory Report), please refer to the relevant description of step S807 of method 800 above.

[0449] S1308, CN performs security testing on AIoT devices.

[0450] S1309, the CN sends a downlink command transmission message or command request message or other NGAP message to the gNB; correspondingly, the gNB receives the downlink command transmission message or command request message or other NGAP message from the CN.

[0451] The downlink command transport message (e.g., DL Command Transport) includes downlink data (DL Data) and carries command instructions, such as read, write, disable, deactivate, or lock operations.

[0452] S1310, the gNB sends downlink data to the UE; correspondingly, the UE receives downlink data from the gNB.

[0453] The downlink data (DL Data) carries commands, such as read, write, disable, deactivate, or lock instructions, which are used to execute command services (i.e., the second AIoT service).

[0454] For example, downlink data can be carried in an RRC message, a MAC CE, or a DCI message, such as when the gNB sends an RRC message to the UE.

[0455] S1311, the UE sends downlink data to the AIoT device; correspondingly, the AIoT device receives downlink data from the UE.

[0456] For example, downlink data can be carried in downlink transport (e.g., DL Transport) messages.

[0457] S1312, the AIoT device sends uplink data (UL Data) to the UE; correspondingly, the UE receives uplink data from the AIoT device.

[0458] For example, uplink data can be carried in uplink transmission (e.g., UL Transport) messages or other A-IoT interface (A-IoT radio) messages (such as AIoT MAC layer or physical layer messages or indication information). Command Response / feedback is carried in the uplink data.

[0459] S1313, the UE sends uplink data to the gNB; correspondingly, the gNB receives uplink data from the UE.

[0460] For example, uplink data can be carried in an RRC message, such as when the UE sends an RRC message to the gNB.

[0461] S1314, the gNB sends an uplink command transport message or command response message or other NGAP message to the CN; correspondingly, the CN receives the uplink command transport message or command response message or other NGAP message from the gNB. The uplink command transport message (e.g., UL Command Transport) includes uplink data (UL Data) and carries a command response / feedback.

[0462] For the specific implementation of steps S1307-S1314 above, please refer to the relevant description of steps S506-S513 of method 500 above.

[0463] Optionally, in the O-RAN architecture, the gNB is a CU-DU separated architecture. For the RRC-based solution architecture or the UP / NAS-based solution architecture, after the CU receives information from the CN (e.g., the inventory request message in step S1301, or the downlink command transmission message in step S1309), it can forward the information to the DU; or, after the DU receives information from the UE (e.g., the AIoT device identifier in step S1305, or the uplink data in step S1313), it can forward the information to the CU. The remaining steps can be referred to the relevant description in Figure 13 above, and will not be repeated here.

[0464] Based on the above scheme, the gNB sends an effective Timer / period pattern / duration to the UE, and uses the timer / period pattern / duration to align the release of AIoT resources with the UE. This allows the UE to stop using AIoT resources during the effective Timer's operation or within the T1 time period indicated by the period pattern, and to continue using or resume using AIoT resources after the effective Timer expires or within the T2 time period indicated by the period pattern. This avoids resource waste and improves resource utilization.

[0465] Figure 14 is a schematic diagram of a communication method 1400 provided in an embodiment of this application. As shown in Figure 14, this method is applicable to UP / NAS-based solution architectures. The access network device configures an effective Timer / period pattern / duration to the terminal, and uses the timer / period pattern / duration to align with the UE to stop using AIoT resources, thereby avoiding resource waste. This method may include the following multiple steps.

[0466] S1401, CN sends an AIoT indication and a NAS PDU / PDU session to gNB;

[0467] Correspondingly, the gNB receives inventory request messages from the CN.

[0468] The NAS PDU / PDU Session carries an Inventory Request message. For a detailed explanation of the Inventory Request message, please refer to the relevant description of step S901 in method 900 above.

[0469] For example, the CN can explicitly indicate an AIoT indicator on the NG / XX interface to indicate AIoT services, and the gNB can subsequently allocate AIoT resources to the UE based on this AIoT indicator.

[0470] Optionally, the CN may not send an AIoT indication. In this case, after the UE receives the Inventory Request included in the NAS PDU / PDU Session, it can request AIoT resources from the gNB via an RRC message, and then the gNB can send the AIoT resources to the UE via an RRC message.

[0471] Optionally, the CN can send an AIoT resource request to the gNB via NGAP / XXAP. For example, the CN can request the gNB to allocate AIoT resources for the current AIoT session / service (e.g., send an AIoT session resource request), or the CN can request the gNB to allocate AIoT resources for one or more specified UE Readers. Alternatively, the CN can first initiate the AIoT resource request process with the gNB, and then the CN can communicate with the AIoT device via a NAS / UP-based solution; or, the above-mentioned process of the CN requesting AIoT resources from the gNB can be performed simultaneously with the communication based on the NAS / UP-based solution.

[0472] S1402, gNB sends AIoT resource #1 (AIoT radio resource, i.e., the first resource), NAS PDU / PDU Session and Timer (i.e., the first timer) / period pattern (i.e., the first time period and the second time period) / duration (i.e., the first duration) (i.e., the second information) to UE;

[0473] Correspondingly, the UE receives AIoT resource #1, NAS PDU / PDU Session, and Timer / period pattern / duration from the gNB.

[0474] For a detailed explanation of AIoT resource #1 and NAS PDU / PDU Session, please refer to the relevant description of step S902 of method 900 above, which will not be explained here.

[0475] For example, after the UE receives a valid timer or duration, it can enable the timer / duration.

[0476] S1403, the UE sends an inventory response message to the CN;

[0477] Correspondingly, the CN receives the inventory response message from the UE.

[0478] For example, the UE sends a storage response message to the CN via the gNB.

[0479] Understandably, in the above steps S1401-S1403, the CN and UE can transmit AIoT-related data / signaling through the UE's NAS PDU / PDU Session (e.g., through gNB pass-through).

[0480] S1404, the UE triggers (or executes) the inventory process on the AIoT wireless interface, and the specific implementation method of the inventory process is not limited.

[0481] S1405, the UE sends the identifier of the AIoT device (i.e., the first data) to the gNB;

[0482] Correspondingly, the gNB receives the identifier of the AIoT device from the UE. The identifier of the AIoT device is associated with the inventory service.

[0483] S1406, the UE stops or resumes using AIoT resource #1 according to Timer / period / pattern / duration;

[0484] S1407, gNB sends an inventory report (e.g., Inventory Report) to CN; correspondingly, CN receives the inventory report from gNB.

[0485] S1408, CN performs security testing on AIoT devices.

[0486] S1409, the CN sends a downlink command transport (e.g., DL Command Transport) message, a command request message, or other NGAP messages to the gNB; correspondingly, the gNB receives the downlink command transport message, command request message, or other NGAP messages from the CN. The downlink command transport message includes downlink data (DL Data) and carries command instructions, such as read, write, disable, deactivate, or lock operation instructions.

[0487] S1410, the gNB sends downlink data to the UE; correspondingly, the UE receives downlink data from the gNB.

[0488] The downlink data (DL Data) carries commands, such as read, write, disable, deactivate, or lock instructions, which are used to execute command services (i.e., the second AIoT service).

[0489] For example, downlink data can be carried in an RRC message, a MAC CE, or a DCI message, such as when the gNB sends an RRC message to the UE.

[0490] S1411, the UE sends downlink data to the AIoT device; correspondingly, the AIoT device receives downlink data from the UE.

[0491] For example, downlink data can be carried in downlink transport (e.g., DL Transport) messages.

[0492] S1412, the AIoT device sends uplink data (UL Data) to the UE; correspondingly, the UE receives uplink data from the AIoT device.

[0493] For example, uplink data can be carried in uplink transmission (e.g., UL Transport) messages or other A-IoT interface (A-IoT radio) messages (such as AIoT MAC layer or physical layer messages or indication information). Command Response / feedback is carried in the uplink data.

[0494] S1413, the UE sends uplink data to the gNB; correspondingly, the gNB receives uplink data from the UE.

[0495] For example, uplink data can be carried in an RRC message, such as when the UE sends an RRC message to the gNB.

[0496] In S1414, the gNB sends an uplink command transport message, command response message, or other NGAP message to the CN; correspondingly, the CN receives the uplink command transport message, command response message, or other NGAP message from the gNB. The uplink command transport message (e.g., UL Command Transport) includes uplink data (UL Data) and carries a command response / feedback.

[0497] For the specific implementation of steps S1404-S1414 above, please refer to the relevant description of steps S1304-S1314 in method 1300 above.

[0498] Optionally, in the O-RAN architecture, the gNB is a CU-DU separated architecture. For the RRC-based solution architecture or the UP / NAS-based solution architecture, after the CU receives information from the CN (e.g., the AIoT indication and NAS PDU / PDU Session in step S1401, or the downlink command transmission message in step S1409), it can forward the information to the DU; or, after the DU receives information from the UE (e.g., the NAS PDU / PDU Session in step S1405, or the uplink data in step S1413), it can forward the information to the CU. The remaining steps can be referred to the relevant description in Figure 14 above, and will not be repeated here.

[0499] Based on the above scheme, the gNB sends an effective Timer / period pattern / duration to the UE, and uses the timer / period pattern / duration to align the release of AIoT resources with the UE. This allows the UE to stop using AIoT resources during the effective Timer's operation or within the T1 time period indicated by the period pattern, and to continue using or resume using AIoT resources after the effective Timer expires or within the T2 time period indicated by the period pattern. This avoids resource waste and improves resource utilization.

[0500] Figure 15 is a schematic diagram of a communication method 1500 provided in an embodiment of this application. As shown in Figure 15, this method is applicable to topology 1 and topology 2 architectures. The access network device configures an effective timer / period pattern / duration for the AIoT device(s), and uses the timer / period pattern / duration to stop or pause monitoring of AIoT interface signaling, thereby avoiding resource waste. This method 1500 may include the following steps; for details not covered herein, please refer to the relevant descriptions in existing protocols.

[0501] S1510, the access network device or terminal obtains the first information.

[0502] The first information indicates the time for ceasing monitoring of AIoT interface signaling, the time for ceasing use of the first resource, or the sleep time of the AIoT device. The first resource is used to execute the first AIoT service, or in other words, the first resource is used for communication between the AIoT device and the access network device on the AIoT radio interface. It is understandable that the AIoT interface signaling is associated with the first AIoT service, or in other words, the AIoT interface signaling is used to execute the first AIoT service. Therefore, ceasing monitoring of the AIoT interface signaling or ceasing use of the first resource indicates that the AIoT device stops executing or does not execute the first AIoT service.

[0503] Optionally, the AIoT interface signaling or AIoT air interface signaling in the embodiments of this application can be replaced with a first signaling, which is related to the first AIoT service. In other words, this application does not limit the specific name of the first signaling.

[0504] In this application embodiment, the AIoT interface (A-IoT radio) can be understood as: the interface between the AIoT device and the AIoT enabled UE, or the interface between the AIoT device and the AIoT RAN node, etc.

[0505] For example, the first resource may include at least one of time-domain resources, frequency-domain resources, spatial-domain resources, or code-domain resources. For a specific definition of the first resource, please refer to the relevant description of step S710 in Figure 7 above.

[0506] For example, the first information indicates a second timer, or indicates a third and fourth time period (period pattern), or indicates a second duration, during which the AIoT device stops monitoring AIoT interface signaling or stops using the first resource.

[0507] For example, after receiving a second timer or a second duration, the AIoT device can start the timer / duration.

[0508] S1520, the access network device or terminal sends the first information to the AIoT device;

[0509] Correspondingly, the AIoT device receives the first information from the access network device or terminal.

[0510] S1530, the AIoT device stops monitoring AIoT interface signaling, or stops using the first resource AIoT, or goes into hibernation.

[0511] For a detailed explanation and implementation of stopping the use of the first resource, please refer to the relevant description of step S730 in method 700 above.

[0512] Understandably, stopping monitoring AIoT interface signaling, ceasing to use the first resource, or going into hibernation indicates that the AIoT device is not performing the first AIoT service. In this case, the first resource can be used for other terminals or to perform other AIoT services to improve resource utilization.

[0513] In one implementation, if the first information in step S1510 indicates a second timer, the AIoT device can stop monitoring AIoT interface signaling, stop using the first resource, or go into sleep mode during the second timer's operation. After the second timer expires, it can resume monitoring AIoT interface signaling, resume use (or continue using), or release the first resource. For example, if the second timer's duration is 1 hour, the AIoT device can start the second timer while sending inventory results (e.g., the AIoT device's identifier). Within 1 hour after the second timer starts, the second resource is deactivated, and the AIoT device cannot use the first resource, or in other words, the AIoT device stops monitoring AIoT interface signaling. After the second timer expires, that is, after 1 hour, the AIoT device can resume monitoring AIoT interface signaling, or resume use or continue using the first resource, for example, using the first resource to perform other AIoT services (e.g., a second AIoT service). For example, an access network device or terminal sends a second message to an AIoT device to instruct the execution of a second AIoT service. Correspondingly, the terminal receives the second message from the access network device or terminal, and after the second timer expires, it continues to use the second resources to execute the second AIoT service.

[0514] In one implementation, if the first information in step S1510 indicates a third time period and a fourth time period (period pattern), the AIoT device can stop monitoring AIoT interface signaling or stop using the first resource or go into sleep mode during the third time period (e.g., T1); and resume monitoring AIoT interface signaling or resume use (or continue use) or release the first resource during the fourth time period (e.g., T2). For example, if the third time period is time slot 1 to time slot 3 and the fourth time period is time slot 4 to time slot 8, the AIoT device can stop monitoring AIoT interface signaling or stop using the first resource or go into sleep mode during time slots 1 to 3, meaning the AIoT device cannot use the first resource during time slots 1 to 3; and during time slots 4 to 8, the AIoT device can resume monitoring AIoT interface signaling or resume use or continue using the first resource, for example, using the first resource to perform other AIoT services (e.g., a second AIoT service). For example, the access network device or terminal sends a second message to the AIoT device to instruct the execution of a second AIoT service. Correspondingly, the terminal receives the second message from the access network device or terminal and continues to monitor the AIoT interface signaling or continue to use the first resource to execute the second AIoT service during the fourth time period.

[0515] In one implementation, if the first information in step S1510 indicates a second duration, the AIoT device can stop monitoring AIoT interface signaling, stop using the first resource, or go into sleep mode within the second duration; and after the second duration ends, it can resume monitoring AIoT interface signaling, resume use (or continue using), or release the first resource. Optionally, the time unit of the second duration can be absolute time (e.g., minutes / seconds / milliseconds) or relative time (e.g., superframes / frames / subframes / slots / symbols). Optionally, the second duration can be a period of time, such as 1 hour, or it can be represented by specific time information (e.g., from x o'clock x minutes x seconds to y o'clock y minutes y seconds), etc., which is not limited in this application. Optionally, the start time of the second duration can be when the AIoT device reports the inventory results (e.g., UL Data (device ID)), which is not limited in this application. For example, the access network device or terminal sends a second message to the AIoT device to instruct the execution of a second AIoT service. Correspondingly, the terminal receives the second message from the access network device or terminal, and after the second duration ends, continues to monitor the AIoT interface signaling or continues to use the first resource to execute the second AIoT service.

[0516] Optionally, if the AIoT device releases the first resource after the second timer expires, or during the fourth time period, or after the second time period ends, then when a subsequent access network device or terminal requests the AIoT device to perform a second AIoT service, the second AIoT resource can be allocated to the AIoT device for performing the second AIoT service. The second resource and the first resource can be the same or different; this application does not impose any limitation on this.

[0517] In this embodiment, the timing of the access network device or terminal sending the first information to the AIoT device is not limited. For example, the first information can be sent to the AIoT device after receiving the device ID reported by the AIoT device through the AIoT interface, or before the access network device or terminal reports the inventory results, or after the access network device or terminal reports the inventory results, or at the same time as the access network device or terminal reports the inventory results. There is no limitation on this.

[0518] Optionally, in the O-RAN architecture, if the access network equipment is a CU-DU separated architecture, the CU can forward the information to the DU after receiving the information from the core network element (e.g., AIoTF); or the DU can forward the information to the CU after receiving the information from the terminal.

[0519] In one implementation, the CU carries a storage request message via an F1AP message and forwards it to the DU; the DU carries the identifier of the AIoT device via an F1AP message and forwards it to the CU; the CU carries the first information via an F1AP message and forwards it to the DU. The remaining steps can be referred to the relevant description in Figure 15 above, and will not be repeated here.

[0520] Based on the above scheme, the access network device or terminal sends a first information instruction to the AIoT device to stop monitoring the AIoT interface signaling or stop using the first resource for a certain period of time or the sleep time of the AIoT device. This allows the AIoT device to stop monitoring the AIoT interface signaling or stop using the first resource during the second timer operation, or within the third time period, or within the first duration. After the second timer expires, or within the fourth time period, or after the first duration ends, it can continue to monitor the AIoT interface signaling or continue to use or resume using the first resource. This can avoid resource waste and improve resource utilization.

[0521] For ease of understanding, Figures 16 to 18 are used to illustrate the implementation methods for AIoT devices to stop monitoring AIoT interface signaling or stop using AIoT resources. In the examples below, the terminal is UE (or AIoT UE), the access network device is gNB (or AIoT gNB), and the core network element is CN (or AIoT CN) as the execution entity. In this application, the AIoT device, terminal UE, access network device gNB, and core network element CN are all devices that support or enable AIoT services. It is understood that the process described below is only an example, and the embodiments of this application are not limited thereto. Content not described in detail below can be referred to the relevant description in Figure 15 above, and will not be repeated here.

[0522] Figure 16 is a schematic diagram of a communication method 1600 provided in an embodiment of this application. As shown in Figure 16, this method is applicable to a topology 1 architecture. The access network device configures an effective Timer / period pattern / duration for the AIoT device, and uses the timer / period pattern / duration to align with the UE to stop using AIoT resources, thereby avoiding resource waste. This method may include the following multiple steps.

[0523] S1601, CN sends an Inventory Request message to gNB;

[0524] Correspondingly, the gNB receives inventory request messages from the CN.

[0525] S1602, gNB sends an inventory response message to CN;

[0526] Correspondingly, CN receives inventory response messages from gNB.

[0527] For the specific implementation of steps S1601 and S1602 above, please refer to the relevant descriptions of steps S801 and S802 in method 800 above.

[0528] S1603, the AIoT device triggers (or executes) an inventory process on the AIoT wireless interface, and the specific implementation method of the inventory process is not limited.

[0529] S1604, UE sends the effective Timer / period pattern / duration to the AIoT device;

[0530] Correspondingly, the AIoT device receives a valid Timer / period pattern / duration from the UE.

[0531] For a detailed explanation of the effective Timer / period pattern / duration, please refer to the relevant description in Figure 15 above. It will not be explained here.

[0532] For example, after receiving a valid timer or duration, an AIoT device can enable the timer / duration.

[0533] S1605, gNB sends an inventory report (e.g., Inventory Report) to CN, which includes the identifier of the AIoT device;

[0534] Correspondingly, the CN receives inventory reports from the gNB. The identifiers of the AIoT devices are associated with the inventory process.

[0535] Regarding the specific timing of the UE sending the effective Timer / period pattern / duration to the AIoT device, this application does not limit this; please refer to the relevant description in Figure 15 above for details, which will not be explained here.

[0536] S1606, the AIoT device stops monitoring AIoT air interface signaling, stops or resumes using AIoT resources, or goes into sleep mode according to the Timer / period pattern / duration. For details, please refer to the relevant description of step S1530 in Figure 15 above, which will not be explained here.

[0537] S1607, CN performs security testing on AIoT devices, and the specific implementation method is not limited.

[0538] S1608, the CN sends a downlink command transport (e.g., DL Command Transport) message, a command request message, or other XX messages to the gNB; correspondingly, the gNB receives the downlink command transport message, command request message, or other XX messages from the CN.

[0539] The downlink command transmission message includes downlink data (DL Data) carrying command instructions, such as read, write, disable, deactivate, or lock operations.

[0540] S1609, the gNB sends downlink data to the AIoT device; correspondingly, the AIoT device receives downlink data from the gNB.

[0541] For example, downlink data can be carried in downlink transport (e.g., DL Transport) messages.

[0542] S1610, the AIoT device sends uplink data (UL Data) to the gNB; correspondingly, the gNB receives the uplink data from the AIoT device.

[0543] For example, uplink data can be carried in uplink transmission (e.g., UL Transport) messages or other A-IoT interface (A-IoT radio) messages (such as AIoT MAC layer or physical layer messages or indication information). Command Response / feedback is carried in the uplink data.

[0544] S1611, the gNB sends an uplink command transport (e.g., UL Command Transport) message or a command response message or other XX message to the CN; correspondingly, the CN receives the uplink command transport message or command response message or other XX message from the gNB.

[0545] The uplink command transmission message includes uplink data (UL Data) and carries a command response / feedback.

[0546] Optionally, in the O-RAN architecture, the gNB is a CU-DU separated architecture. For topology 1, after the CU receives information from the CN (e.g., the inventory request message in step S1601, or the downlink command transmission message in step S1608), it can forward the information to the DU; or, after the DU receives information from the UE (e.g., the inventory result (identifier of the AIoT device)), it can forward the information to the CU. The remaining steps can be referred to the relevant description in Figure 16 above, and will not be repeated here.

[0547] Based on the above scheme, the gNB sends a valid Timer / period pattern / duration to the AIoT device, enabling the AIoT device to stop monitoring AIoT interface signaling or stop using AIoT resources during the valid Timer's operation, or within the T1 time period indicated by the period pattern or the duration, and to continue monitoring AIoT interface signaling or continue using or resume using AIoT resources after the valid Timer expires, or within the T2 time period indicated by the period pattern or the duration ends. This avoids resource waste and improves resource utilization.

[0548] Figure 17 is a schematic diagram of a communication method 1700 provided in an embodiment of this application. As shown in Figure 17, this method is applicable to the RRC-based solution architecture of topology 2. The access network device or terminal configures an effective Timer / period pattern / duration for the AIoT device, and uses the timer / period pattern / duration to align with the UE to stop using AIoT resources, thereby avoiding resource waste. This method may include the following multiple steps.

[0549] S1701, CN sends an Inventory Request message to gNB;

[0550] Correspondingly, the gNB receives inventory request messages from the CN.

[0551] S1702, gNB sends an inventory response message to CN;

[0552] Correspondingly, CN receives inventory response messages from gNB.

[0553] For the specific implementation of steps S1701 and S1702 above, please refer to the relevant descriptions of steps S801 and S802 in method 800 above.

[0554] S1703, gNB sends inventory information, AIoT resources (AIoT radio resource, i.e., the first resource), duration (i.e., the second duration), and Timer (i.e., the second timer) / period pattern (i.e., the third and fourth time periods) to UE.

[0555] Correspondingly, the UE receives inventory information, AIoT resources, and Timer / period pattern / duration from the gNB.

[0556] For a detailed explanation of inventory information and AIoT resources, please refer to the relevant description of step S803 in method 800 above.

[0557] Optionally, inventory information, AIoT resources, and Timer / period pattern / duration can be carried in the RRC message.

[0558] S1704, the UE and AIoT device trigger (or execute) the inventory process on the AIoT wireless interface.

[0559] S1705, the UE sends the identifier of the AIoT device to the gNB;

[0560] Correspondingly, the gNB receives the identifier of the AIoT device from the UE. The identifier of the AIoT device is associated with the inventory service.

[0561] S1706, the UE sends the Timer / period pattern / duration to the AIoT device;

[0562] Correspondingly, the AIoT device receives the Timer / period pattern / duration from the UE.

[0563] For example, after receiving a valid timer or duration, an AIoT device can enable the timer / duration.

[0564] S1707, the AIoT device stops monitoring AIoT interface signaling, stops or resumes using AIoT resources, or goes into sleep mode according to the Timer / period pattern / duration. For details, please refer to the relevant description of step S1530 in Figure 15 above, which will not be explained here.

[0565] S1708, gNB sends an inventory report (e.g., Inventory Report) to CN; correspondingly, CN receives the inventory report from gNB.

[0566] For a detailed interpretation of the inventory report, please refer to the relevant description of step S807 of method 800 above.

[0567] S1709, CN performs security testing on AIoT devices.

[0568] S1710, the CN sends a downlink command transport (e.g., DL Command Transport) message or a command request message or other NGAP message to the gNB; correspondingly, the gNB receives the downlink command transport message or command request message or other NGAP message from the CN.

[0569] The downlink command transmission message includes downlink data (DL Data) carrying command instructions, such as read, write, disable, deactivate, or lock operations.

[0570] S1711, the gNB sends downlink data to the UE; correspondingly, the UE receives downlink data from the gNB.

[0571] The downlink data (DL Data) carries commands, such as read, write, disable, deactivate, or lock instructions, which are used to execute command services (i.e., the second AIoT service).

[0572] For example, downlink data can be carried in an RRC message, a MAC CE, or a DCI message, such as when the gNB sends an RRC message to the UE.

[0573] S1712, the UE sends downlink data to the AIoT device; correspondingly, the AIoT device receives downlink data from the UE.

[0574] For example, downlink data can be carried in downlink transport (e.g., DL Transport) messages.

[0575] S1713, the AIoT device sends uplink data (UL Data) to the UE; correspondingly, the UE receives uplink data from the AIoT device.

[0576] For example, uplink data can be carried in uplink transmission (e.g., UL Transport) messages or other A-IoT interface (A-IoT radio) messages (e.g., AIoT MAC layer or physical layer messages or indication information), and the uplink data carries Command Response / feedback.

[0577] S1714, the UE sends uplink data to the gNB; correspondingly, the gNB receives uplink data from the UE.

[0578] For example, uplink data can be carried in an RRC message, such as when the UE sends an RRC message to the gNB.

[0579] S1715, the gNB sends an uplink command transport (e.g., UL Command Transport) message or a command response message or other NGAP message to the CN; correspondingly, the CN receives the uplink command transport message or command response message or other NGAP message from the gNB.

[0580] The uplink command transmission message includes uplink data (UL Data) and carries a command response / feedback.

[0581] For details on the implementation of steps S1709-S1715 above, please refer to the relevant description of method 1300 above.

[0582] Optionally, in the O-RAN architecture, the gNB is a CU-DU separated architecture. For the RRC-based solution architecture, after the CU receives information from the CN (e.g., the inventory request message in step S1701, or the downlink command transmission message in step S1710), it can forward the information to the DU; or, after the DU receives information from the UE (e.g., the AIoT device identifier in step S1705, or the uplink data in step S1714), it can forward the information to the CU. The remaining steps can be referred to the relevant description in Figure 17 above, and will not be repeated here.

[0583] Based on the above scheme, the gNB sends a valid Timer / period pattern / duration to the AIoT device, enabling the AIoT device to stop monitoring AIoT interface signaling or stop using AIoT resources during the valid Timer's operation, or within the T1 time period indicated by the period pattern or the duration, and to continue monitoring AIoT interface signaling or continue using or resume using AIoT resources after the valid Timer expires, or within the T2 time period indicated by the period pattern or the duration ends. This avoids resource waste and improves resource utilization.

[0584] Figure 18 is a schematic diagram of a communication method 1800 provided in an embodiment of this application. As shown in Figure 18, this method is applicable to the UP / NAS-based solution architecture of topology 2. The access network device or terminal configures an effective Timer / period pattern / duration for the AIoT device, and uses the timer / period pattern / duration to align with the UE to stop using AIoT resources, so as to avoid resource waste. This method may include the following multiple steps.

[0585] S1801, CN sends an AIoT indication and a NAS PDU / PDU session to gNB;

[0586] Correspondingly, the gNB receives inventory request messages from the CN.

[0587] The NAS PDU / PDU Session carries an Inventory Request message. For a detailed explanation of the Inventory Request message, please refer to the relevant description of step S901 in method 900 above.

[0588] For example, the CN can explicitly indicate an AIoT indicator on the NG / XX interface to indicate AIoT services, and the gNB can subsequently allocate AIoT resources to the UE based on this AIoT indicator.

[0589] Optionally, the CN may not send an AIoT indication. In this case, after the UE receives the Inventory Request included in the NAS PDU / PDU Session, it can request AIoT resources from the gNB via an RRC message, and then the gNB can send the AIoT resources to the UE via an RRC message.

[0590] Optionally, the CN can send an AIoT resource request to the gNB via NGAP / XXAP. For example, the CN can request the gNB to allocate AIoT resources for the current AIoT session / service (e.g., send an AIoT session resource request), or the CN can request the gNB to allocate AIoT resources for one or more specified UE Readers. Alternatively, the CN can first initiate the AIoT resource request process with the gNB, and then the CN can communicate with the AIoT device via a NAS / UP-based solution; or, the above-mentioned process of the CN requesting AIoT resources from the gNB can be performed simultaneously with the communication based on the NAS / UP-based solution.

[0591] S1802, gNB sends AIoT resources (AIoT radio resource, i.e., the first resource), NAS PDU / PDU Session and Timer (i.e., the second timer) / period pattern (i.e., the third and fourth time periods) / duration (i.e., the second duration) to UE;

[0592] Correspondingly, the UE receives AIoT resources, NAS PDU / PDU Session, and Timer / period pattern / duration from the gNB.

[0593] For a detailed explanation of AIoT resources and NAS PDU / PDU Session, please refer to the relevant description of step S902 in method 900 above.

[0594] S1803, the UE sends an inventory response message to the CN;

[0595] Correspondingly, the CN receives the inventory response message from the UE.

[0596] For example, the UE sends a storage response message to the CN via the gNB.

[0597] Understandably, in the above steps S1801-S1803, the CN and UE can transmit AIoT-related data / signaling through the UE's NAS PDU / PDU Session (e.g., through gNB pass-through).

[0598] S1804, the UE and AIoT device trigger (or execute) the inventory process on the AIoT wireless interface.

[0599] S1805, the UE sends the identifier of the AIoT device to the gNB;

[0600] Correspondingly, the gNB receives the identifier of the AIoT device from the UE. The identifier of the AIoT device is associated with the inventory service.

[0601] S1806, the UE sends a Timer / period pattern / duration to the AIoT device, and correspondingly, the AIoT device receives the Timer / period pattern / duration from the UE.

[0602] S1807, the AIoT device stops monitoring AIoT interface signaling, stops or resumes using AIoT resources, or goes into sleep mode according to the Timer / period pattern / duration. For details, please refer to the relevant description of step S1530 in Figure 15 above, which will not be explained here.

[0603] S1808, gNB sends an inventory report (e.g., Inventory Report) to CN; correspondingly, CN receives the inventory report from gNB.

[0604] S1809, CN performs security testing on AIoT devices.

[0605] S1810, the CN sends a downlink command transport (e.g., DL Command Transport) message, a command request message, or other NGAP messages to the gNB; correspondingly, the gNB receives the downlink command transport message, command request message, or other NGAP messages from the CN. The downlink command transport message includes downlink data (DL Data) and carries command instructions, such as read, write, disable, deactivate, or lock operation instructions.

[0606] S1811, the gNB sends downlink data to the UE; correspondingly, the UE receives downlink data from the gNB.

[0607] The downlink data (DL Data) carries commands, such as read, write, disable, deactivate, or lock instructions, which are used to execute command services (i.e., the second AIoT service).

[0608] For example, downlink data can be carried in an RRC message, a MAC CE, or a DCI message, such as when the gNB sends an RRC message to the UE.

[0609] S1812, the UE sends downlink data to the AIoT device; correspondingly, the AIoT device receives downlink data from the UE.

[0610] For example, downlink data can be carried in downlink transport (e.g., DL Transport) messages.

[0611] S1813, the AIoT device sends uplink data (UL Data) to the UE; correspondingly, the UE receives uplink data from the AIoT device.

[0612] For example, uplink data can be carried in uplink transmission (e.g., UL Transport) messages or other A-IoT interface (A-IoT radio) messages (such as AIoT MAC layer or physical layer messages or indication information). Command Response / feedback is carried in the uplink data.

[0613] S1814, the UE sends uplink data to the gNB; correspondingly, the gNB receives uplink data from the UE.

[0614] For example, uplink data can be carried in an RRC message, such as when the UE sends an RRC message to the gNB.

[0615] In step S1815, the gNB sends an uplink command transport (e.g., UL Command Transport) message, a command response message, or other NGAP messages to the CN; correspondingly, the CN receives the uplink command transport message, command response message, or other NGAP messages from the gNB. The uplink command transport message includes uplink UL data and carries a command response / feedback.

[0616] Optionally, in the O-RAN architecture, the gNB adopts a CU-DU separation architecture. For the UP / NAS-based solution architecture, after the CU receives information from the CN (e.g., the AIoT indication and NAS PDU / PDU Session in step S1801, or the downlink command transmission message in step S1810), it can forward the information to the DU; or, after the DU receives information from the UE (e.g., the AIoT device identifier in step S1805, or the uplink data in step S1814), it can forward the information to the CU. The remaining steps can be referred to the relevant description in Figure 18 above, and will not be repeated here.

[0617] Based on the above scheme, the gNB sends a valid Timer / period pattern / duration to the AIoT device, enabling the AIoT device to stop monitoring AIoT interface signaling or stop using AIoT resources during the valid Timer's operation, or within the T1 time period indicated by the period pattern or the duration, and to continue monitoring AIoT interface signaling or continue using or resume using AIoT resources after the valid Timer expires, or within the T2 time period indicated by the period pattern or the duration ends. This avoids resource waste and improves resource utilization.

[0618] As described above, the access network equipment involved in the technical solution of this application can be O-RAN. Under the O-RAN architecture, the RIC can directly control either the gNB-CU or the gNB-DU, requiring the "access network equipment" in the communication method steps shown in Figures 7, 10, 12, or 15 to be expanded to "CU" and "DU". Optionally, in various embodiments of this application, if the access network equipment is a CU-DU separated architecture, after the CU receives information (e.g., inventory request message) from a core network element (e.g., AIoTF), it can forward the information to the DU; or, after the DU receives information (e.g., first information) from the UE, it can forward the information to the CU.

[0619] In one implementation, after receiving an xxAP / NGAP message from the CN, the CU forwards the xxAP / NGAP message to the DU via an F1AP message, or sends the AIoT information contained in the xxAP / NGAP message to the DU via an F1AP message. After receiving an RRC message from the UE, the DU forwards the RRC message to the CU via an F1AP message, or sends the AIoT information contained in the RRC message to the CU via an F1AP message. The xxAP / NGAP messages transmitted on the F1 interface and the xxAP / NGAP messages transmitted on the XX / NG interface can be different; that is, the CU can perform related processing on the messages, including deletion, filtering, mapping, modification, and adding auxiliary information.

[0620] For example, if the access network device is a CU-DU separated architecture, for topology 1, or for topology 2's RRC-based solution architecture or UP / NAS-based solution architecture, the CU carries inventory information and AIoT resources via an F1AP message and forwards it to the DU; the DU carries first information via an F1AP message and forwards it to the CU; the CU carries an instruction to release or stop using the first AIoT resource via an F1AP message and forwards it to the DU. The remaining steps can be referred to the relevant descriptions in Figures 7 to 18 above, and will not be repeated here.

[0621] The communication method embodiments of this application have been described in detail above with reference to Figures 1 to 18. The communication device embodiments of this application will now be described in detail below with reference to Figures 19 to 21. It should be understood that the descriptions of the device embodiments correspond to the descriptions of the method embodiments; therefore, any parts not described in detail can be referred to the preceding method embodiments.

[0622] Figure 19 is a possible exemplary block diagram of the communication device involved in the embodiments of this application. As shown in Figure 19, the communication device 10 may include modules or units for implementing the method embodiments described above. In one possible design, the communication device 10 includes a communication unit 1003 and a processing unit 1002. Optionally, the communication device 10 may further include a storage unit 1001 for storing device program code and / or data. The communication unit 1003 may also be referred to as a communication interface, transceiver unit, or interface unit.

[0623] The communication device 10 can be a terminal-side device as described in the above embodiments, such as a terminal or a communication module in a terminal, or a circuit or chip in a terminal that is responsible for communication functions.

[0624] For example, in one embodiment, the communication unit 1003 is used to receive first information from the access network device, the first information indicating a first resource, the first resource being used to execute a first AIoT service; the communication unit 1003 is also used to send second information to the access network device, the second information including first data and third information, the first data being associated with the first AIoT service, the third information indicating that the terminal releases or stops using the first resource; or, the communication unit 1003 is also used to send third information to the access network device, the third information indicating that the first resource is released or stopped using; or, the communication unit 1003 is also used to send fourth information to the access network device, the fourth information including first data and fifth information, the fifth information indicating that the first data is associated with the first AIoT service; the processing unit 1002 is used to release or stop using the first resource.

[0625] For example, in one embodiment, the communication unit 1003 is used to receive first information from the access network device, the first information indicating a first resource, the first resource being used to execute a first AIoT service; the communication unit 1003 is also used to send second information to the access network device, the second information including first data, the first data being associated with the first AIoT service; the processing unit 1002 is used to release or stop using the first resource.

[0626] For example, in one embodiment, the communication unit 1003 is used to receive first information from the access network device, the first information indicating first resources and second information, the first resources being used to execute a first AIoT service, and the second information indicating the time for stopping the use of the first resources; the processing unit 1002 is used to stop using the first resources according to the second information.

[0627] For example, in one embodiment, the communication unit 1003 is used to acquire first information, which indicates the time for stopping monitoring AIoT interface signaling, the time for stopping using first resources, or the sleep time of the AIoT device, wherein the first resources are used to execute a first AIoT service; the communication unit 1003 is also used to send the first information to the AIoT device. Alternatively, the communication unit 1003 is used to send the first information to the AIoT device, which indicates the time for stopping monitoring AIoT interface signaling, the time for stopping using first resources, or the sleep time of the AIoT device, wherein the first resources are used to execute a first AIoT service.

[0628] In one possible design, when the communication device 10 is a terminal or a communication module within a terminal, the function of the processing unit 1002 can be implemented by one or more processors. Specifically, the processor may include a modem chip, or a system-on-a-chip (SoC) chip or a SIP chip containing a modem core. The function of the communication unit 1003 can be implemented by transceiver circuitry.

[0629] In one possible design, when the communication device 10 is a circuit or chip in a terminal responsible for communication functions, such as a modem chip or a system-on-a-chip (SoC) or SIP chip containing a modem core, the function of the processing unit 1002 can be implemented by a circuit system in the aforementioned chip that includes one or more processors or processor cores. The function of the communication unit 1003 can be implemented by the interface circuitry or data transceiver circuitry on the aforementioned chip.

[0630] The communication device 10 can be a network-side device in the above embodiments, such as an access network device, or a module (e.g., a circuit, a chip, or a chip system) in the access network device, or a logical node or logical module that can realize all or part of the functions of the access network device.

[0631] For example, in one embodiment, the communication unit 1003 is used to send first information to the terminal, the first information indicating a first resource, the first resource being used to execute a first AIoT service; the communication unit 1003 is also used to receive second information from the terminal, the second information including first data and third information, the first data being associated with the first AIoT service, the third information indicating the release or cessation of use of the first resource; or, the communication unit 1003 is also used to receive third information from the terminal, the third information indicating the release or cessation of use of the first resource; or, the communication unit 1003 is also used to receive fourth information from the terminal, the fourth information including first data and fifth information, the fifth information indicating that the first data is associated with the first AIoT service.

[0632] For example, in one embodiment, the communication unit 1003 is used to send first information to the terminal, the first information indicating a first resource, the first resource being used to execute a first AIoT service; the communication unit 1003 is also used to receive second information from the terminal, the second information including first data, the first data being associated with the first AIoT service; the processing unit 1002 is used to determine, based on the second information, that the terminal instructs the terminal to release or stop using the first resource.

[0633] For example, in one embodiment, the processing unit 1002 is used to determine first information, the first information indicating first resources and second information, the first resource being used to execute a first AIoT service, and the second information indicating the time for ceasing the use of the first resource; the communication unit 1003 is used to send the first information to the terminal. Alternatively, the communication unit 1003 is used to send the first information to the terminal, the first information indicating first resources and second information, the first resource being used to execute the first AIoT service, and the second information indicating the time for ceasing the use of the first resource.

[0634] For example, in one embodiment, the communication unit 1003 is used to acquire first information, which indicates the time for stopping monitoring AIoT interface signaling, the time for stopping using first resources, or the sleep time of the AIoT device, wherein the first resources are used to execute a first AIoT service; the communication unit 1003 is also used to send the first information to the AIoT device. Alternatively, the communication unit 1003 is used to send the first information to the AIoT device, which indicates the time for stopping monitoring AIoT interface signaling, the time for stopping using first resources, or the sleep time of the AIoT device, wherein the first resources are used to execute a first AIoT service.

[0635] In one possible design, when the communication device 10 is an access network device or a communication module within an access network device, the function of the processing unit 1002 can be implemented by one or more processors. Specifically, the processor may include a chip. The function of the communication unit 1003 can be implemented by a transceiver circuit.

[0636] In one possible design, when the communication device 10 is a circuit or chip responsible for communication functions in an access network device, the function of the processing unit 1002 can be implemented by a circuit system in the chip that includes one or more processors or processor cores. The function of the communication unit 1003 can be implemented by an interface circuit or data transceiver circuit on the chip.

[0637] The communication device 10 can be an AIoT device-side device in the above embodiments, such as an AIoT device or a communication module in an AIoT device, or a circuit or chip in an AIoT device that is responsible for communication functions.

[0638] For example, in one embodiment, the communication unit 1003 is used to receive first information from the access network device or terminal. The first information indicates the time for stopping monitoring AIoT interface signaling, the time for stopping using the first resource, or the sleep time of the AIoT device. The first resource is used to execute the first AIoT service. The processing unit 1002 is used to stop monitoring AIoT interface signaling, or stop using the first resource, or put the device into sleep mode. The AIoT interface signaling is associated with the first AIoT service.

[0639] In one possible design, when the communication device 10 is an AIoT device or a communication module within an AIoT device, the functionality of the processing unit 1002 can be implemented by one or more processors. Specifically, the processor may include a modem chip, or a system-on-a-chip (SoC) or SIP chip containing a modem core. The functionality of the communication unit 1003 can be implemented by transceiver circuitry.

[0640] In one possible design, when the communication device 10 is a circuit or chip responsible for communication functions in an AIoT device, such as a modem chip or a system-on-a-chip (SoC) or SIP chip containing a modem core, the function of the processing unit 1002 can be derived from the chip including one or more processors. It is understood that the division of units in the above device is merely a logical functional division; one function can correspond to one functional unit, or two or more functions can be integrated into one functional unit. In actual implementation, all or some units can be integrated onto a single physical entity, or distributed across different physical entities. Furthermore, the above functional units can be implemented in hardware, software, or a combination of both.

[0641] In one example, the functional unit in any of the above devices may be one or more integrated circuits configured to implement the above methods, such as: one or more application-specific integrated circuit (ASIC) designs, or one or more central processing units (CPUs), one or more microprocessor units (MPUs), one or more microcontroller units (MCUs), one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms.

[0642] In one example, storage unit 1001 may include random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory and / or registers, etc.

[0643] Figure 20 is a schematic diagram of a terminal 2000 provided in an embodiment of this application. The terminal 2000 corresponds to the terminal shown in Figure 1 and is used to implement the operation of the terminal in the above embodiments. As shown in Figure 20, the terminal 2000 includes: one or more antennas 2010, a radio frequency processing system 2020, and a processor system 2030.

[0644] In the downlink or sidelink direction, the RF processing system 2020 receives RF signals through the antenna 2010 and sends the RF-processed signals to the processor system 2030 for further processing. In the uplink or sidelink direction, the processor system 2030 processes the terminal-side information and sends it to the RF processing system 2020, which then processes the signal and transmits it through the antenna 2010.

[0645] In one example, the radio frequency (RF) processing system 2020 serves as the communication interface for external communication of the terminal and may include a radio frequency front end (RFFE) 2021 and an RF transceiver 2022. The RFFE 2021 is primarily used for one or more processing operations, such as shaping, passband selection, or gain adjustment, on the RF signals received by the antenna or those to be transmitted through the antenna. It may include one or more components such as RF switches, duplexers, filters, power amplifiers, antenna tuning, and low-noise amplifiers. The RFFE 2021 can be a circuit system composed of multiple discrete components or integrated into one or more chips. The RF transceiver 2022 processes the RF signals received by the RFFE into baseband / IF signals for further processing by the processor system 2030, and processes the baseband / IF signals provided by the processor system 2030 into RF signals for transmission to the RFFE 2021. The baseband / IF signals transmitted between the RF transceiver 2022 and the processor system 2030 can be digital or analog signals. An RF transceiver 2022 can be implemented by one or more chips, which are commonly referred to as RF chips.

[0646] In one example, the processor system 2030 may include one or more processors for processing signals and executing one or more communication protocols. Optionally, the processor system 2030 may also include a memory 2036. In one example, the one or more processors include at least one baseband processor 2031 (also known as a modem processor). The memory 2036 is used to store data and / or computer program instructions. Optionally, the processor system 2030 may also include one or more application processors 2032 for implementing processing of the terminal operating system and application layer. Optionally, the processor system 2030 may also include one or more of a voice subsystem 2033, a multimedia subsystem 2034, or an interface circuit 2035. The voice subsystem 2033 is used to process voice signals, the multimedia subsystem 2034 is used to handle multimedia-related operations, such as video encoding / decoding, image processing, etc., and the interface circuit 2035 is used to implement communication with other terminal components, such as a display 2040, an input device 2050, a memory 2060, etc. The above-mentioned components in the processor system 2030 can communicate with each other via a bus or communication interface circuit.

[0647] In one example, the processor system 2030 can be packaged as a single processor chip, such as a SoC chip or a SIP chip. In another example, the processor system 2030 can be a system composed of multiple chips; for example, the baseband processor 2031 can be packaged as a single chip, or packaged with part or all of the circuitry of the radio frequency processing system into a single chip.

[0648] In one example, memory 2036 can be on-chip memory, i.e., located on the processor system 2030 chip. In another example, memory 2060 can be off-chip memory, i.e. located outside the processor system 2030 chip.

[0649] Figure 21 is a schematic diagram of the structure of the baseband processor 2031 of the terminal 2000 provided in this application embodiment. As shown in Figure 21, the baseband processor 2031 in the terminal 2000 provided in this application embodiment may include one or more processor cores 20311 and interface circuits 20314. The one or more processor cores 20311 are used to process signals and execute one or more communication protocols. Optionally, the baseband processor 2031 may also include a memory 20312, which is used to store at least a portion of the corresponding computer program instructions and / or data. In one example, the one or more processor cores 20311 implement the relevant operations in the above method embodiment by executing the computer program instructions stored in the memory 20312. In this application, the memory 20312 is used to store corresponding computer program instructions and / or data. This can mean that the memory 20312 stores all corresponding computer program instructions and / or data for execution by the processor core 20311; or it can mean that the memory 20312 stores a portion of the corresponding computer program instructions and / or data, including the computer program instructions and / or data currently required to be executed by the processor core 20311. The memory 20312 can store different portions of computer program instructions and / or data multiple times for execution by the processor core 20311 to implement the relevant operations in the above method embodiments. The interface circuit 20314 serves as a communication interface for communication with other components, such as transmitting signals with the radio frequency processing system 2020, communicating with other subsystems and related components of the processor system 2030 via a bus, such as transmitting data control signals with the application processor 2032, and transmitting data or computer program instructions with the memory 2036 or memory 2060. Optionally, in order to reduce the load on the processor core, a baseband signal processing circuit 20313 can be set to perform at least some baseband signal processing, including one or more of signal demodulation, modulation, encoding or decoding.

[0650] In one example, the communication device provided in this application may be a terminal 2000, a communication module including a processor system 2030 and a radio frequency processing system 2020, or a baseband processor 2031.

[0651] The processor, processor system, application processor, baseband processor, processor circuit or processor core mentioned above can be collectively referred to as a processor. The processor may include one or more of the following: CPU, DSP, MPU, MCU, GPU, FPGA, ASIC, artificial intelligence (AI) processor or neural network processing unit (NPU).

[0652] The aforementioned memory may include one or more of the following storage media: random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), phase-change memory (PCM), resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), cache, register, read-only memory (ROM), flash memory, erasable programmable read-only memory (EPROM), hard disk, etc. In one example, computer program instructions for executing the above embodiments may be stored on non-volatile memory, such as at least a portion of the aforementioned memory 2060 (e.g., one or more of ROM, flash memory, EPROM, or hard disk). When the terminal is running, the corresponding computer program instructions may be partially or wholly loaded onto a memory with a faster transfer speed than the processor, such as at least a portion of memory 2036 and / or memory 20312 (e.g., one or more of RAM, SRAM, DRAM, PCM, RERAM, MRAM, FRAM, cache, or register), for the processor to execute in order to implement the steps in the above method embodiments.

[0653] In one example, the RF transceiver 2022 and the RF front-end 2021 can also be packaged in a single chip. In another example, the RF transceiver 2022, the RF front-end 2021, and the baseband processor 2031 can also be packaged in a single chip.

[0654] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by a communication device (e.g., a terminal-side device and / or a network-side device) in the above-described method embodiments.

[0655] This application also provides a computer program product comprising instructions which, when executed by a computer, implement the methods described above as being performed by a communication device (e.g., a terminal-side device and / or a network-side device).

[0656] This application also provides a communication system, which includes the terminal-side device and / or network-side device described in the above embodiments.

[0657] Optionally, the communication system may also include the terminal-side device and / or network-side device described in the above embodiments.

[0658] The explanations and beneficial effects of the relevant contents in any of the devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0659] In the various embodiments of this application, the order of the above-mentioned processes 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.

[0660] This application will present various aspects, embodiments, or features relating to systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches are also possible.

[0661] In this application, examples may reference each other without logical contradiction. For example, methods and / or terms between method embodiments may reference each other, functions and / or terms between device embodiments may reference each other, and functions and / or terms between device examples and method examples may reference each other.

[0662] In this application, any embodiments may be combined or combined with each other without conflict, and the combined or combined technical solutions are also within the scope of this application.

[0663] It should be understood that the above embodiments are mainly illustrated using devices in existing network architectures as examples, and the specific form of the devices is not limited in the embodiments of this application. For example, any device that can achieve the same function in the future is applicable to the embodiments of this application.

[0664] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0665] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be described again here.

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

[0667] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this implementation scheme according to actual needs.

[0668] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0669] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to existing solutions, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a server, or an access network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0670] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, The method, applied to a terminal or a chip within a terminal, includes: Receive first information, the first information instructing a first resource, the first resource being used to execute a first environment Internet of Things (AIoT) service; Send a second message, the second message including the first data and / or a third message, the first data being associated with the first AIoT service, the third message indicating the end or completion of the first AIoT service, or the third message indicating the first data being associated with the first AIoT service, or the third message being used to request the release or cessation of the use of the first resource; Release or stop using the first resource.

2. The method according to claim 1, characterized in that, Before releasing or ceasing the use of the first resource, the method further includes: Receive a fourth message, which indicates that the first resource should be released or its use should be stopped.

3. The method according to claim 1 or 2, characterized in that, The third information instructs the terminal to stop using the first resource, and the method further includes: Receive a fifth message, which indicates whether to resume or continue using the first resource.

4. The method according to claim 1 or 2, characterized in that, The third information instructs the terminal to release the first resource, and the method further includes: Receive a sixth message, the sixth message indicating a second resource, the second resource being used to execute a second AIoT service; The second resource is used to execute the second AIoT service.

5. A communication method, characterized in that, A chip applied to or in an access network device, the method comprising: Send a first message, the first message indicating a first resource, the first resource being used to execute a first environment Internet of Things (AIoT) service; Receive second information, the second information including first data and / or third information, the first data being associated with the first AIoT service, the third information indicating the end or completion of the first AIoT service, or the third information indicating the first data being associated with the first AIoT service, or the third information being used to request the release or cessation of use of the first resource.

6. The method according to claim 5, characterized in that, The method further includes: Send a fourth message indicating that the first resource should be released or its use should be stopped.

7. The method according to claim 5 or 6, characterized in that, The third information indicates that the use of the first resource should be stopped, and the method further includes: Send a fifth message, which indicates whether to resume or continue using the first resource.

8. The method according to claim 5 or 6, characterized in that, The third information indicates the release of the first resource, and the method further includes: A sixth message is sent, which instructs a second resource to perform a second AIoT service.

9. A communication method, characterized in that, The method, applied to a terminal or a chip within a terminal, includes: Receive first information and / or second information, wherein the first information indicates a first resource, the first resource is used to perform a first environment Internet of Things (AIoT) service, and the second information indicates the time for which the first resource is to be stopped; Use the first resource to execute the first AIoT service; and / or, Based on the second information, stop using the first resource.

10. The method according to claim 9, characterized in that, The second information includes at least one of the following: a first timer, a first time period, a second time period, or a first duration; the method further includes: The first resource is stopped from being used during the operation of the first timer, or during the first time period, or during the first duration.

11. The method according to claim 10, characterized in that, The method further includes: After the first timer expires, or during the second time period, or after the first duration ends, the first resource is restored, used again, or released.

12. The method according to claim 10 or 11, characterized in that, The method further includes: Upon receiving the second information, the first timer is started.

13. The method according to any one of claims 10 to 12, characterized in that, The method further includes: Receive a third message, which instructs the execution of a second AIoT service; After the first timer expires, or during the second time period, or at the end of the first duration, the first resource continues to be used to execute the second AIoT service.

14. A communication method, characterized in that, A chip applied to or in an access network device, the method comprising: Determine first information and / or second information, wherein the first information indicates a first resource, the first resource is used to perform a first environment Internet of Things (AIoT) service, and the second information indicates the time during which the first resource is no longer used; Send the first information and / or the second information.

15. The method according to claim 14, characterized in that, The second information includes at least one of the following: a first timer, a first time period, a second time period, or a first duration, wherein the first resource is stopped from use during the operation of the first timer, or during the first time period, or during the first duration.

16. The method according to claim 15, characterized in that, The first resource is resumed for use, continued for use, or released after the first timer expires, or during the second time period, or after the first duration ends.

17. The method according to claim 15 or 16, characterized in that, The method further includes: Send a third message, which instructs the execution of a second AIoT service; Wherein, after the first timer expires, or during the second time period, or after the first duration ends, the first resource is used to execute the second AIoT service.

18. A communication method, characterized in that, The method, applicable to an environmental Internet of Things (AIoT) device or a chip within an AIoT device, includes: Receive first information, the first information indicating the time to stop monitoring AIoT interface signaling or the time to stop using the first resource or the sleep time of the AIoT device, the first resource being used to execute the first AIoT service; Stop monitoring AIoT interface signaling, or stop using the first resource, or put the device into hibernation.

19. The method according to claim 18, characterized in that, The first information includes at least one of the following: a second timer, a third time period and a fourth time period, or a second duration; the method further includes: During the operation of the second timer, or during the third time period, or during the second duration, monitoring of AIoT interface signaling is stopped or the first resource is stopped, or the system goes into hibernation.

20. The method according to claim 19, characterized in that, The method further includes: After the second timer expires, or during the fourth time period, or after the second duration ends, the monitoring of the AIoT interface signaling is resumed, or the first resource is resumed or continues to be used or released.

21. The method according to claim 19 or 20, characterized in that, The method further includes: Receive a second message, which instructs the execution of a second AIoT service; After the second timer expires, or during the fourth time period, or after the second duration ends, continue to monitor AIoT interface signaling, or continue to use, resume use, or release the first resource, or execute the second AIoT service.

22. A communication method, characterized in that, The method, applicable to an access network device or a chip within an access network device, or a terminal or a chip within a terminal, comprises: Obtain first information, the first information indicating the time to stop monitoring the IoT AIoT interface signaling of the environment, or the time to stop using the first resource, or the sleep time of the AIoT device, the first resource being used to execute the first AIoT service; Send the first message.

23. The method according to claim 22, characterized in that, The first information includes at least one of the following: a second timer, a third time period, a fourth time period, or a second duration. The first information indicates that the AIoT device monitors AIoT interface signaling or stops using the first resource or goes into hibernation during the operation of the second timer, or during the third time period, or during the second duration.

24. The method according to claim 23, characterized in that, The first information also instructs the AIoT device to resume monitoring AIoT interface signaling, or to resume or continue using or release the first resource after the second timer expires, or during the fourth time period, or after the second duration ends.

25. The method according to claim 23 or 24, characterized in that, The method further includes: Send a second message, which instructs the execution of a second AIoT service; After the second timer expires, or during the fourth time period, or after the second duration ends, continue monitoring AIoT interface signaling, or resume monitoring AIoT interface signaling, or resume use or continue to use or release the first resource, or execute the second AIoT service.

26. A communication device, characterized in that, It includes modules or units for implementing the method as described in any one of claims 1-4, 9-13, or 22-25; or modules or units for implementing the method as described in any one of claims 5-8, 14-17, or 22-25; or modules or units for implementing the method as described in any one of claims 18-21.

27. The communication device according to claim 26, characterized in that, The communication device includes any one of the following: a terminal or a chip; or, The communication device includes any one of the following: access network equipment, chip, central unit (CU), or distributed unit (DU); or... The communication device includes any one of the following: an AIoT device or a chip.

28. A communication device, characterized in that, It includes at least one processor for executing a computer program or instructions to cause the method as described in any one of claims 1-4, 9-13, or 22-25 to be executed, or to cause the method as described in any one of claims 5-8, 14-17, or 22-25 to be executed, or to cause the method as described in any one of claims 18-21 to be executed.

29. The communication device according to claim 28, characterized in that, The communication device further includes a memory for storing the computer program or instructions.

30. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed, cause the method as described in any one of claims 1-25 to be implemented.

31. A computer program product, characterized in that, When the computer program product is run, the method as described in any one of claims 1-25 is implemented.

Images