Operation execution method and apparatus, and device and node

By scheduling the execution of AIoT processes within the AIoT system and utilizing execution time and service identification information, the problem of service conflicts among multiple readers and writers is resolved, thereby improving the success rate of AIoT services.

WO2026233274A1PCT designated stage Publication Date: 2026-11-12VIVO MOBILE COMM CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2026/094750
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2026-05-06
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

In environmental IoT (AIoT) systems, business conflicts may occur between multiple readers, which increases the probability of AIoT business failure.

Method used

The first device performs operations associated with the AIoT process based on information sent by the first node, and sends instruction information to the second device to schedule the execution of the AIoT process, including execution time information, control information and business identification information of the AIoT process, in order to negotiate the start or end of the AIoT process.

Benefits of technology

This reduces the probability of business conflicts in AIoT services and increases the success rate of AIoT services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2026094750_12112026_PF_FP_ABST
    Figure CN2026094750_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The present application relates to the technical field of communications. Disclosed are an operation execution method and apparatus, and a device and a node. The operation execution method in the embodiments of the present application comprises: a first device executing a target operation, the target operation comprising at least one of the following: executing a first operation on the basis of first information sent by a first node, wherein the first operation is associated with an ambient Internet of Things (AIoT) procedure, and the first information comprises at least one of the following: execution time information of the AIoT procedure, control information of the AIoT procedure, and service identification information; and sending to a second device at least one of first indication information and the execution time information of the AIoT procedure, wherein the first indication information is used for indicating that the first device has started executing the AIoT procedure, or the first indication information is used for indicating that the first device has ended the execution of the AIoT procedure.
Need to check novelty before this filing date? Find Prior Art

Description

Operation execution methods, devices, equipment and nodes

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202510591451.5, filed in China on May 8, 2025, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application belongs to the field of communication technology, and specifically relates to an operation execution method, apparatus, device and node. Background Technology

[0004] Ambient Internet of Things (AIoT), also known as Ambient Power-enabled Internet of Things (AIoT), is a type of IoT service. AIoT devices are low-power IoT devices, characterized by low overall power consumption, including low-power signal reception and transmission. Due to their low overall power consumption, the energy for communication can be derived from the environment, such as wind power, kinetic energy, heat energy, and radio frequency signals.

[0005] In an AIoT system, multiple readers may be deployed. Business conflicts may occur between these readers, which could lead to a higher probability of AIoT business failure. Summary of the Invention

[0006] This application provides an operation execution method, apparatus, device, and node that can solve the problem of a high probability of AIoT service failure.

[0007] Firstly, an operation execution method is provided, the method comprising:

[0008] The first device performs the target operation;

[0009] The target operation includes at least one of the following:

[0010] A first operation is performed based on first information sent by a first node, wherein the first operation is associated with an environmental Internet of Things (AIoT) process, and the first information includes at least one of the following: execution time information of the AIoT process; control information of the AIoT process; and service identification information.

[0011] Send at least one of a first indication message and an AIoT process execution time message to the second device, wherein the first indication message is used to indicate that the first device has started executing the AIoT process, or the first indication message is used to indicate that the first device has finished executing the AIoT process.

[0012] Secondly, an operation execution method is provided, the method comprising:

[0013] The first node sends the first information to the first device;

[0014] The first information includes at least one of the following: execution time information of the AIoT process; control information of the AIoT process; and service identification information.

[0015] Thirdly, an operation execution device is provided, comprising:

[0016] The processing module is used to execute the target operation;

[0017] The target operation includes at least one of the following:

[0018] A first operation is performed based on first information sent by a first node, wherein the first operation is associated with an environmental Internet of Things (AIoT) process, and the first information includes at least one of the following: execution time information of the AIoT process; control information of the AIoT process; and service identification information.

[0019] Send at least one of a first indication message and an AIoT process execution time message to the second device, wherein the first indication message is used to indicate that the first device has started executing the AIoT process, or the first indication message is used to indicate that the first device has finished executing the AIoT process.

[0020] Fourthly, an operation execution device is provided, comprising:

[0021] The sending module is used to send first information to the first device;

[0022] The first information includes at least one of the following: execution time information of the AIoT process; control information of the AIoT process; and service identification information.

[0023] Fifthly, an operation execution device is provided, the device being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0024] In a sixth aspect, a first device is provided, the first device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0025] In a seventh aspect, a first device is provided, including a processor and a communication interface, wherein the processor is used for:

[0026] Perform the target operation;

[0027] The target operation includes at least one of the following:

[0028] A first operation is performed based on first information sent by a first node, wherein the first operation is associated with an environmental Internet of Things (AIoT) process, and the first information includes at least one of the following: execution time information of the AIoT process; control information of the AIoT process; and service identification information.

[0029] Send at least one of a first indication message and an AIoT process execution time message to the second device, wherein the first indication message is used to indicate that the first device has started executing the AIoT process, or the first indication message is used to indicate that the first device has finished executing the AIoT process.

[0030] In an eighth aspect, a first node is provided, the first node including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect.

[0031] Ninthly, a first node is provided, including a processor and a communication interface, wherein,

[0032] A communication interface for sending first information to the first device;

[0033] The first information includes at least one of the following: execution time information of the AIoT process; control information of the AIoT process; and service identification information.

[0034] In a tenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.

[0035] Eleventhly, a wireless communication system is provided, comprising: a first device and a first node, wherein the first device is configured to perform the steps of the method described in the first aspect, and the first node is configured to perform the steps of the method described in the second aspect.

[0036] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0037] In a thirteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0038] In this embodiment, the first device performs a first operation based on first information sent by the first node. The first operation is associated with an AIoT process. The first information includes at least one of the following: execution time information of the AIoT process, control information of the AIoT process, and service identification information. By scheduling the execution of the AIoT process using the first information, the probability of business conflicts in the AIoT service can be reduced, thereby increasing the probability of success of the AIoT service. Alternatively, the first device sends at least one of first instruction information and execution time information of the AIoT process to the second device. Negotiation of the AIoT process execution is achieved through the first instruction information, which can reduce the probability of business conflicts in the AIoT service and thus increase the probability of success of the AIoT service. Attached Figure Description

[0039] Figure 1 is a block diagram of a wireless communication system applicable to an embodiment of this application;

[0040] Figure 2a is a schematic diagram of the overall AS process between AIoT devices and readers in related technologies;

[0041] Figure 2b is a schematic diagram of the inventory process in related technologies;

[0042] Figure 2c is a schematic diagram of the command process in the related technology;

[0043] Figure 2d is one of the topological diagrams in the related technology;

[0044] Figure 2e is a second topological diagram in the related technology;

[0045] Figure 3 is a flowchart of one of the operation execution methods provided in an embodiment of this application;

[0046] Figure 4a is a second flowchart of an operation execution method provided in an embodiment of this application;

[0047] Figure 4b is a flowchart of an operation execution method provided in an embodiment of this application;

[0048] Figure 5a is a third flowchart of an operation execution method provided in an embodiment of this application;

[0049] Figure 5b is a flowchart of an operation execution method provided in an embodiment of this application;

[0050] Figure 6a is a flowchart of an operation execution method provided in an embodiment of this application;

[0051] Figure 6b is a flowchart of an operation execution method provided in an embodiment of this application;

[0052] Figure 7 is a flowchart of an operation execution method provided in an embodiment of this application;

[0053] Figure 8 is a schematic diagram of one of the operation execution devices provided in an embodiment of this application;

[0054] Figure 9 is a second schematic diagram of the structure of an operation execution device provided in an embodiment of this application;

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

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

[0057] Figure 12 is one of the structural schematic diagrams of a network-side device provided in an embodiment of this application;

[0058] Figure 13 is a second schematic diagram of the structure of a network-side device provided in an embodiment of this application. Detailed Implementation

[0059] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0060] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0061] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as the sender explicitly informing the receiver of specific information, the required operation, or the requested result in the instruction sent. An indirect instruction can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the required operation or requested result based on the judgment result.

[0062] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used in the systems and radio technologies mentioned above, as well as in other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th Generation (6G) communication systems.

[0063] Figure 1 shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as User Equipment (UE), and can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (APs), or Wireless Fidelity (WiFi) nodes, etc.Among them, base stations can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmission and Reception Point (TRP), and Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform). The term "base station" can be any suitable term in the field, such as "station" or any other appropriate term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to any specific technical term. It should be noted that the embodiments of this application only use the base station in the NR system as an example for introduction, and do not limit the specific type of base station.

[0064] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), and Binding Support. Functions include BSF, Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), Network Data Analytics Function (NWDAF), and Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform station).It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment. If the name of the core network equipment mentioned in the embodiments of this application changes in subsequent protocol versions (e.g., 6G), it is also within the scope of protection of this application.

[0065] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0066] For ease of understanding, the following explains some aspects of the embodiments of this application:

[0067] 1. Ambient IoT (Enabled by Ambient Energy)

[0068] Ambient IoT (AIoT), also known as Ambient Power-enabled Internet of Things, is a type of IoT service. AIoT terminals are powered through energy harvesting; they either do not have batteries or have limited energy storage capacity (e.g., using a capacitor). These devices have low overall power consumption, including low-power signal reception and low-power signal transmission. Ambient IoT terminals feature ultra-low complexity and ultra-low power consumption. Due to the low overall power consumption, the energy for communication can be derived from the environment, such as wind power, kinetic energy, heat energy, radio frequency (RF) signals, etc. They can also be called Ambient IoT or passive IoT devices, or response devices.

[0069] In this application embodiment, AIoT is equivalent to A-IoT.

[0070] Ambient IoT terminals can be categorized based on their energy source, energy storage capability, and whether they are passive or active transmitters, encompassing various device types:

[0071] Passive devices, such as device 1, do not have independent signal generation / amplification capabilities and communicate through backscattering;

[0072] Semi-passive devices, such as device 2a, also belong to the category of passive devices. They have energy storage but do not generate independent signals. They communicate through backscattering, and the stored energy can be used to amplify the reflected signal.

[0073] Active devices, such as device 2b, have energy storage and independent signal generation capabilities, meaning they contain active radio frequency components for transmission.

[0074] 2. AIoT transmission method:

[0075] AIoT transmission methods include:

[0076] DO: Device-originated. DO devices typically send various data, requests, or instructions, meaning they are initiated by the device itself.

[0077] DT: Device-terminated. DT devices typically receive instructions, data, or requests from other devices or systems, meaning they are terminated at the device.

[0078] DO data indicates that the data stream originates from an AIoT device (similar to an RFID tag). DT data indicates that the data stream is transmitted to an AIoT device.

[0079] For data streams originating from AIoT devices, i.e., DO data, they can be further categorized as follows:

[0080] 1) Device autonomously initiates data transmission, i.e., DO-A data;

[0081] For example, readers connect to a wide variety of sensors that collect and proactively report information about the environment, equipment, or organisms when necessary.

[0082] 2) Device-terminated triggered (DO device-terminated triggered): Base station and other reader devices trigger AIoT devices to initiate data transmission, i.e., DO-DTT data.

[0083] For example, asset identification, status reporting, and tracking are all downlink (DL) triggered reports, where the reader collects data from the AIoT device by triggering inventory procedures. Since the data is generated / initiated within the AIoT device, this service should be considered a DO service initiated by the AIoT device via control commands from the reader side.

[0084] 3. AIoT Business Types

[0085] The main business types of AIoT include: inventory and issuing commands.

[0086] Inventory is the most basic and important business of AIoT, used to enable AIoT servers to learn about one or more known or unknown AIoT devices within the Reader's coverage area via the 3GPP network.

[0087] After recognizing that an AIoT device has been identified by the network, the AIoT server can issue commands to the device via the 3GPP network, specifically including:

[0088] 4. AIoT Communication Process

[0089] As shown in Figure 2a, the basic AIoT communication process is as follows:

[0090] Step A: AIoT Paging.

[0091] Based on the AIoT service request, the reader sends a paging message to indicate which device needs to respond.

[0092] Step B: Connect.

[0093] The instructed device performs an access procedure, which can be a contention-based access procedure or a contention-free access procedure, and ultimately transmits the device identifier to the reader.

[0094] Step C: Possible interactions between higher-level commands and responses after access:

[0095] Step C1: Possible R2D transmission, the reader is used for transmitting higher-level command instructions after access.

[0096] Step C2: Possible D2R transmission, the transmission the device uses in response to a command.

[0097] 5. Business Process

[0098] The AIoT business process is shown in Figures 2b and 2c.

[0099] AIoT Core Network (CN) node: The core network node that the gNB connects to the 5GC for AIoT operations. More specifically, it is the AIOTF when the gNB is directly connected to the AIOTF, and it includes both the AMF and AIOTF when the gNB connects to the AIOTF via the AMF.

[0100] 6. Connection Topology

[0101] AIoT has the following potential deployment scenarios:

[0102] As shown in Figure 2d, Topology 1: BS Ambient IoT device

[0103] AIoT base stations (BS) and small base stations coexist at the same location. The BS sends R2D messages to the AIoT device, and the AIoT device performs backscattering, i.e., transmits D2R messages to the BS.

[0104] As shown in Figure 2e, Topology 2: BS Intermediate node Ambient IoT device

[0105] The AIoT BS and large base stations coexist at the same location, with the indoor UE acting as an intermediate node. The BS controls the UE through air interface signaling. The UE sends R2D messages to the AIoT device, and the AIoT device performs backscattering, i.e., D2R message transmission to the UE. The UE then forwards the AIoT device's response to the BS through the air interface.

[0106] 7. Transaction Identifier (ID)

[0107] A Transaction ID can also be translated as a transaction ID or processing ID. The Transaction ID is included in the paging message sent by the Reader to the AIoT device. A new Transaction ID signifies a new session or service. The AIoT device stores the received Transaction ID value. If the AIoT device receives a paging message with the same Transaction ID as a previously stored one, the AIoT device recognizes it as the same session or service and can avoid duplicate responses using the Transaction ID. The Transaction ID is generated by the Reader based on the association identifier provided by the core network.

[0108] It should be noted that Transaction ID can also be called AIoT Transaction ID, or any other name.

[0109] The following description, in conjunction with the accompanying drawings, details the operation execution methods, apparatus, and related equipment provided in this application through some embodiments and application scenarios.

[0110] Referring to Figure 3, which is a flowchart of an operation execution method provided in an embodiment of this application, the operation execution method includes the following steps:

[0111] Step 101: The first device performs the target operation;

[0112] The target operation includes at least one of the following:

[0113] A first operation is performed based on first information sent by a first node, wherein the first operation is associated with an environmental Internet of Things (AIoT) process, and the first information includes at least one of the following: execution time information of the AIoT process; control information of the AIoT process; and service identification information.

[0114] Send at least one of a first indication message and an AIoT process execution time message to the second device, wherein the first indication message is used to indicate that the first device has started executing the AIoT process, or the first indication message is used to indicate that the first device has finished executing the AIoT process.

[0115] The first information can be scheduling information. This first information can be used to schedule the first device to execute an AIoT process or AIoT service.

[0116] Additionally, the AIoT process may include processes such as inventory or command. The first operation being associated with the AIoT process can mean that the first operation is an operation related to the AIoT process; for example, the object of the first operation is the AIoT process.

[0117] The execution time information of the AIoT process can also be described as AIoT execution time information.

[0118] In one embodiment, the execution time information of the AIoT process may include: a time range, for example, the time period for executing an AIoT service or AIoT process, which can be indicated by an absolute time period, such as an absolute time period [00:00:10~00:00:20], or by a time period starting from the time the message containing the first information is received, such as the time period for executing an AIoT service or AIoT process being [starting time~starting time+10 minutes].

[0119] In one embodiment, the execution time information of the AIoT process may include periodic time information, wherein the periodic time information includes period, time length, start time or time offset, etc., and the first device can execute AIoT services or AIoT processes within the periodic time range indicated by the periodic time information.

[0120] In one implementation, the execution time information of the AIoT process is indicated by the number of paging rounds. That is, the time period for executing the AIoT service or AIoT process is represented by the number of paging rounds completed by the first device. For example, N paging rounds. This is beneficial for the first device to complete at least one round of inventory process, thereby generating an inventory report and improving the efficiency of the first device in executing AIoT tasks.

[0121] In one implementation, the execution time information of the AIoT process may include an execution duration, such as 20 seconds. That is, after receiving the first information, the first device executes the AIoT service or AIoT process within this execution duration. Optionally, this execution duration can be referred to as the maximum execution duration. After the first device reaches the maximum execution duration, it ends or pauses the execution of the AIoT process. It is understood that if the AIoT process is completed before reaching the maximum execution duration, it ends upon completion. After ending or pausing the AIoT process, the first device can start or continue the paused AIoT process upon receiving second information (which can be considered new first information) or an AIoT task request message (such as an inventory request or command request) sent by the first node to indicate the start or continuation of the AIoT process.

[0122] The Transaction ID information is used to indicate the Transaction ID available to the first device.

[0123] Business identification information may include at least one of the following:

[0124] (d1) Transaction ID: The first node configures a Transaction ID for the first device. This allows multiple first devices to use the same Transaction ID when executing the same AIoT service, avoiding duplicate responses from the AIoT device. The AIoT service can also be represented by an AIoT session or a Correlation ID.

[0125] (d2) Available Transaction ID Range. The first node configures an available Transaction ID range for the first device, and the first device determines the Transaction ID within this range. It can be understood that when multiple first devices simultaneously execute AIoT services, the first node provides the first devices with selectable or unused Transaction IDs to prevent multiple first devices from using the same Transaction ID.

[0126] (d3) At least one Transaction ID already used. The first node provides the first device with the Transaction IDs already used. The first device needs to use a Transaction ID that is different from the Transaction ID already used. In this way, multiple first devices avoid using the same Transaction ID when performing different AIoT services.

[0127] In one embodiment, the first device sends the execution time information of the AIoT process to the second device, so that the second device can know when the first device starts executing the AIoT process or when it ends executing the AIoT process through the execution time information of the AIoT process.

[0128] It should be noted that the first device can receive the first information sent by the first node multiple times, and the scheduling instructions corresponding to these multiple first messages can be different.

[0129] Additionally, the first device can be a Reader, and the first node can be a node used to schedule the Reader. For example, the first device is a gNB (here, the gNB acts as the Reader), and the first node is an AIoT core network (CN) node (such as AIOTF); or, the first device is a UE Reader, and the first node is an AIoT core network node (such as AIOTF); or, the first device is a UE Reader, and the first node is a gNB (in this case, the gNB acts as the node that schedules the Reader); and so on. This embodiment does not limit the specific implementation of the first device and the first node.

[0130] In the embodiments of this application, the AIoT core network node can be a core network device, such as a core network node, core network function, or core network element.

[0131] In one implementation, the first device can be a gNB or a Reader, and the first node can be an AIOTF. The AIOTF can send the first information through the following interfaces: AIOTF-gNB-Reader interface (or direct interface) or AIOTF-AMF-gNB-Reader (or indirect interface). For example, in scenarios involving inter-gNB coordination, the AIOTF, based on the Reader deployment, knows which Readers may have business conflicts. The AIOTF can send the first information to notify the relevant Readers to suspend, resume, inventory, or command, or release, cancel, or end the relevant AIoT process.

[0132] In one implementation, the first device can be a UE Reader, the first node can be a gNB, and the gNB can send the first information through the air interface.

[0133] In one implementation, the first device can be a Reader, the second device can be a Reader, and the first device can send first instruction information through a Reader-Reader interface.

[0134] It should be noted that the first node (such as gNB or AIOTF) can coordinate AIoT services per reader; or the first node (such as AIOTF or gNB) can coordinate AIoT services per gNB; or the first node (such as AIOTF) can coordinate AIoT services per area.

[0135] In one embodiment, the first device receives first information sent by the first node and performs a first operation based on the first information.

[0136] In this embodiment, the first device performs a first operation based on first information sent by the first node. The first operation is associated with an AIoT process, and the first information includes at least one of the following: execution time information of the AIoT process, control information of the AIoT process, and service identification information. By scheduling the execution of the AIoT process using the first information, the probability of business conflicts in the AIoT service can be reduced, thereby increasing the probability of AIoT service success. Alternatively, the first device sends at least one of first instruction information and the execution time information of the AIoT process to the second device. Negotiation of the AIoT process execution is achieved through the first instruction information, which can reduce the probability of business conflicts in the AIoT service and thus increase the probability of AIoT service success.

[0137] Optionally, the control information of the AIoT process is used to indicate any of the following: start the AIoT process, pause the AIoT process, suspend the AIoT process, continue the AIoT process, release the AIoT process, cancel the AIoT process, or end the AIoT process;

[0138] And / or,

[0139] The business identification information includes at least one of the following: one or more business identifiers (Transaction IDs) that can be used in the AIoT process, and at least one business identifier (Transaction ID) that has been used;

[0140] And / or,

[0141] The execution time information is characterized by at least one of the following: time range; number of paging rounds; periodic time information; execution duration.

[0142] The control information of the AIoT process can also be described as AIoT process operation information.

[0143] The one or more Transaction IDs that can be used in the AIoT process can refer to one or more Transaction ID values ​​that can be used in the AIoT process. At least one Transaction ID that has been used can refer to at least one Transaction ID value that has been used.

[0144] In this embodiment, through the control information of the AIoT process, the first device can start, pause, continue, release, cancel, or end the AIoT process according to the instructions of the first node, thereby enabling the scheduling of AIoT process execution, reducing the probability of business conflicts in AIoT services, and thus increasing the probability of success of AIoT services.

[0145] In this embodiment, the first device can determine the Transaction ID of the AIoT process based on the service identification information in the first information, thereby avoiding conflicts between the Transaction IDs of multiple AIoT services.

[0146] Optionally, the first information is carried in at least one of the following:

[0147] Inventory request; command request; AIoT task request; Radio Resource Control (RRC) message; Non-Access Stratum (NAS) message.

[0148] The AIoT task request is a message used to request the first device to perform an AIoT task.

[0149] In this embodiment, including the first information in the AIoT task-related request message (such as inventory request, command request, or AIoT task request) helps the first device to execute the AIoT process according to the scheduling requirements of the first node.

[0150] Optionally, the method further includes:

[0151] The first device sends a first response message to the first node. The first response message is used to indicate that the first message has been received, or to indicate that the operation indicated by the first message has been completed.

[0152] In this embodiment, the first device sends a first response message to the first node, thereby enabling the first node to confirm that the first device has received the first message or completed the operation indicated by the first message. This allows the first node to continue scheduling other nodes to execute their AIoT processes, avoiding conflicts between multiple first devices performing AIoT services.

[0153] Optionally, the first operation includes any one of the following:

[0154] The AIoT process is executed based on the execution time information of the AIoT process;

[0155] Pause, suspend, or terminate the AIoT process;

[0156] Continue executing the AIoT process;

[0157] Execute the AIoT process again;

[0158] The transaction ID of the AIoT process is determined based on the transaction identification information.

[0159] It is understood that when the first operation includes continuing the AIoT process, the AIoT process may have been previously paused or suspended. When the first operation includes resuming the AIoT process, the AIoT process may have been previously terminated.

[0160] In this embodiment, the first device performs the first operation based on the first information sent by the first node, which can realize the scheduling of AIoT process execution, thereby reducing or avoiding conflicts between multiple first devices in executing AIoT services, and reducing or avoiding failures when multiple first devices perform inventory or command processes on the same AIoT device.

[0161] Optionally, when the first operation includes pausing, suspending, or ending the AIoT process, the first operation further includes at least one of the following:

[0162] Save the first information;

[0163] Retain the business request information of the AIoT process;

[0164] Maintain the state of the AIoT process;

[0165] The AIoT process was interrupted during recording;

[0166] The AIoT paging process of the AIoT wireless interface terminates the aforementioned AIoT process;

[0167] Maintain AIoT session information for the AIoT process;

[0168] Save the transaction ID of the AIoT process;

[0169] Maintain the AIoT device context information during the AIoT process.

[0170] It is understood that when the control information of the AIoT process in the first information indicates that the AIoT process should be paused, the first operation includes pausing the AIoT process; when the control information of the AIoT process in the first information indicates that the AIoT process should be suspended, the first operation includes suspending the AIoT process; when the control information of the AIoT process in the first information indicates that the AIoT process should be terminated, the first operation includes terminating the AIoT process.

[0171] The business request information in the AIoT process may include inventory requests or command requests, which facilitates the continued execution of the AIoT process.

[0172] The state of the AIoT process can include: start, pause, continue, cancel, end, etc., so that AIoT tasks can be executed according to the state in the future.

[0173] The AIoT session information in the AIoT process can include the AIoT session, correlation ID, etc., to facilitate the continuation of the AIoT session or AIoT service in the future.

[0174] It is understood that during the period when the first device is paused, suspended, or terminated in executing its AIoT process, the first node may schedule other nodes to execute the AIoT process. These other nodes may interfere with the first device, have overlapping coverage, or possess identical or partially identical AIoT devices.

[0175] In this embodiment, when the AIoT process is paused, suspended, or terminated by the first information, the first device performs the first operation described above, which facilitates the first device to re-execute or continue the AIoT process.

[0176] Optionally, if the first operation includes pausing, suspending, or terminating the AIoT process, the method further includes:

[0177] The first device performs a second operation based on second information sent by the first node, the second information being used to indicate whether to continue the AIoT process or to start the AIoT process;

[0178] The second operation includes at least one of the following:

[0179] Continue the AIoT process or begin the AIoT process;

[0180] Send a paging message.

[0181] The second information may be information of the same type as the first information, meaning that both the first and second information are information used to schedule the AIoT process.

[0182] In one implementation, the second information can be considered as new first information.

[0183] For example, the second information includes at least one of the following: execution time information of the AIoT process; control information of the AIoT process; and service identification information.

[0184] In one implementation, the control information of the AIoT process in the second information is used to indicate whether to continue the AIoT process or start the AIoT process.

[0185] In one implementation, when continuing or starting the AIoT process, for the same AIoT session or AIoT service, a saved Transaction ID is used, or a previously applied Transaction ID is continued to be used.

[0186] In one implementation, the second operation includes sending a paging message. When sending the paging message, AIoT devices that have completed their services are filtered out, or only AIoT devices that have not completed their services are paged. For AIoT devices that have completed old services and have already executed new services sent by other nodes, the old services might still be considered new services, leading to duplicate inventory responses. The first device can use initial paging, carrying AIoT device selection information, which filters out AIoT devices that have completed their services, thus avoiding duplicate inventory responses.

[0187] In one implementation, the second operation includes sending a paging message containing access resource configuration, or sending an initial paging message without using subsequent paging, access timing messages, R2D trigger messages, or other messages to continue the interrupted AIoT process. This is because after an interruption, the AIoT device may have cleared the access resource configuration from the initial paging. This method allows the AIoT device to be provided with access resource configuration again.

[0188] For example, when the first device is performing an AIoT inventory process, it receives the first information sent by the first node to pause or terminate the AIoT process. Then, the first device pauses or terminates the AIoT process. When the first device is requested to continue or restart the AIoT process, it can correctly continue the unfinished AIoT task through the aforementioned first and second operations. For example, in the AIoT inventory service, the first device does not continue the inventory by sending an access timing indication message or an R2D trigger message, but instead initiates a new paging process by sending a paging message.

[0189] In one embodiment, the first device receives second information sent by the first node and performs a second operation based on the second information.

[0190] In this embodiment, when the first operation includes pausing, suspending, or ending the AIoT process, the first device performs the second operation based on the second information sent by the first node. This allows the first device to re-execute or continue the AIoT process or send a paging message to initiate a new round of paging if the AIoT process is interrupted, thus preventing errors in the AIoT process.

[0191] Optionally, for the same AIoT session or AIoT service, the saved transaction ID can be used in the second operation, or the transaction ID that was applied before the second operation can continue to be used.

[0192] In one implementation, the saved (or stored) or previously used Transaction ID is used in the second operation. That is, the message sent to the AIoT device through the second operation uses the same Transaction ID as the one used in the previous execution of the AIoT process. The saved Transaction ID is the Transaction ID used in the previous execution of the AIoT process.

[0193] It is understandable that, for the same AIoT session or AIoT service, the same Transaction ID is used in the AIoT process as in the previous AIoT process.

[0194] In this implementation, for the same AIoT session or AIoT service, the second operation uses the saved Transaction ID or continues to use the Transaction ID that was applied before the second operation, which can avoid being mistaken for a new AIoT service and thus avoid the execution of duplicate AIoT operations.

[0195] Optionally, the method further includes:

[0196] The first device sends third information to the first node, the third information being used for at least one of the following:

[0197] The first device is instructed to initiate the AIoT process;

[0198] The first node is requested to coordinate the first device to execute the AIoT process.

[0199] The first node is requested to send the first information.

[0200] In this embodiment, the first device sends third information to the first node, so that the first node can send first information to the first device based on the third information. By scheduling the execution of the AIoT process through the first information, the probability of business conflicts in AIoT services can be reduced, thereby increasing the probability of success of AIoT services.

[0201] Optionally, the first device performs a first operation based on the first information sent by the first node, including:

[0202] The first device receives the first message sent by the first node;

[0203] Wherein, if the first message carries the first information, the first device performs the first operation based on the first information sent by the first node; or,

[0204] If the first message does not carry the first information, the first device performs the AIoT process.

[0205] In one implementation, if the first message does not carry the first information, the first device directly executes the AIoT process.

[0206] In one implementation, the first message includes at least one of the following:

[0207] Inventory request; command request; AIoT task request.

[0208] In this implementation, if the first message carries the first information, the first device performs the first operation based on the first information sent by the first node; or, if the first message does not carry the first information, the first device directly executes the AIoT process. This allows for flexible scheduling of the first device to execute the AIoT process, avoiding conflicts between multiple first devices and reducing signaling load between nodes.

[0209] Optionally, when sending at least one of the first instruction information and the execution time information of the AIoT process to the second device, the method further includes:

[0210] Send the transaction ID of the AIoT process to the second device.

[0211] Understandably, to reduce signaling overhead, the first device can send at least one of the first indication information and the execution time information of the AIoT process, as well as the Transaction ID of the AIoT process, to the second device via a single signaling message.

[0212] Optionally, the first device is an access network device, and the first node is an AIoT core network node;

[0213] or,

[0214] The first device is a user equipment (UE) reader / writer, and the first node is an AIoT core network node;

[0215] or,

[0216] The first device is a UE reader / writer, and the first node is an access network device;

[0217] or,

[0218] Both the first device and the second device are UE readers or access network devices;

[0219] or,

[0220] The first device is a UE reader / writer, and the second device is an access network device.

[0221] Optionally, the first device is associated with at least one of the following:

[0222] The access network device selected by the first node for AIoT services;

[0223] The reader / writer selected by the first node for AIoT services;

[0224] The AIoT region selected by the first node for AIoT services;

[0225] The target reader / writer overlaps with other readers / writers.

[0226] The AIoT service mentioned above refers to the AIoT service corresponding to the AIoT process.

[0227] In one embodiment, the first device may be an access network device among the access network devices selected by the first node for AIoT services, or a UE reader managed by the access network device among the access network devices selected by the first node for AIoT services.

[0228] In one implementation, the first device may be a reader / writer selected by the first node for AIoT services.

[0229] In one embodiment, the first device can be a reader / writer corresponding to the AIoT area selected by the first node for AIoT services.

[0230] In one embodiment, the first device can be a target reader / writer, that is, the first device is a reader / writer that overlaps with other readers / writers.

[0231] In this implementation, the first device to be scheduled can be determined based on at least one of the following: the access network device selected by the first node for AIoT services, the reader selected by the first node for AIoT services, the AIoT area selected by the first node for AIoT services, and the reader that has coverage overlap with other readers, which can reduce signaling load.

[0232] In this embodiment, when multiple first devices are deployed, the first node schedules the first devices to execute AIoT services. Firstly, signal transmission and reception between multiple first devices may interfere with each other. This embodiment schedules the execution times of multiple first devices to be staggered, for example, using TDM mode, to avoid conflicts between the first devices. Secondly, multiple first devices may perform AIoT processes such as inventory checks or commands on the same AIoT device. Without coordination, this may lead to errors in the AIoT process execution, such as failure to inventory some AIoT devices. This embodiment can identify such situations and coordinate the service execution times of the first devices.

[0233] It's important to note that multiple Readers may be deployed in an AIoT system. From the perspective of communication between multiple Readers and the Device, there is a potential for service conflicts between them. Therefore, how the network-side devices coordinate multiple Readers to execute AIoT services and avoid failures caused by service conflicts is a problem that needs to be solved. For example, if an AIoT device is performing an ongoing inventory check and then receives a request message (such as a paging message) from another AIoT reader, it's unclear how the AIoT device should handle this request message. If the AIoT device terminates its ongoing service to process the newly received request message, then the services between the readers need to be coordinated to avoid service conflicts leading to failures.

[0234] In scenarios involving multiple Readers, it is necessary to address the business scheduling issue among them to avoid conflicts in business execution. This application provides an AIoT scheduling method to coordinate AIoT services or processes.

[0235] The following examples will provide further explanation:

[0236] Example 1:

[0237] This example illustrates how an AIoT core network node (first node) schedules an NG-RAN node (first device) to execute AIoT services or processes.

[0238] In this example, with multiple Readers deployed, the AIoT core network node (such as AIOTF) schedules NG-RAN nodes (such as gNBs) to execute AIoT services. Firstly, signal transmission and reception between Readers (such as gNBs) may interfere with each other. This example staggers the execution times of multiple Readers, for example, using TDM mode, to avoid conflicts between Readers. Secondly, multiple Readers may perform inventory checks or command executions on the same AIoT devices. Without coordination, this could lead to errors, such as inventory checks failing on some AIoT devices. This example identifies this situation and coordinates the service execution times of the Readers.

[0239] As shown in Figure 4a, this example includes the following signaling flow:

[0240] Step (1): The gNB receives the first information sent by the AIoT core network node (AIoT CN Node). The first information is used to schedule the gNB to execute AIoT services or AIoT processes, or to indicate the execution time information of the AIoT process. The AIoT core network node can be AIOTF or AMF.

[0241] The AIoT core network node (AIoT CN Node) can be the core network node for a gNB to connect to the 5GC for AIoT operations. If the gNB is directly connected to the AIOTF, the AIoT core network node can be the AIOTF; if the gNB is connected to the AIOTF through the AMF, the AIoT core network node can include both the AMF and the AIOTF.

[0242] Among them, gNB can also be called Next Generation Radio Access Network (NG-RAN) node. AIoT process refers to processes such as inventory and command.

[0243] The first information includes at least one of the following:

[0244] (a) AIoT execution time information.

[0245] For example, AIoT execution time information may include the time period for executing AIoT services or processes. This time period may be an absolute time period, such as an absolute time period [00:00:10~00:00:20], or a time period starting from the time the message containing the first information is received, such as 10 minutes.

[0246] The AIoT execution time information may include an execution duration, such as 20 seconds, meaning that after receiving the first information, the gNB executes the AIoT service or AIoT process within this execution duration. Optionally, the execution duration may refer to a maximum execution duration, meaning that the gNB ends or pauses the execution of the AIoT process after reaching the maximum execution duration. The gNB may start or continue the paused AIoT process after receiving the first information or an AIoT task request message (such as an inventory request or command request) sent by the AIoT core network.

[0247] The AIoT execution time information may include periodic time, which includes period, duration, start time or time offset, etc.

[0248] Alternatively, AIoT execution time information can include a Paging Round, which represents the time period for executing AIoT services or processes based on the number of AIoT paging rounds completed by the gNB. This allows the gNB to complete at least one round of inventory processing, thereby generating an inventory report and improving the efficiency of the gNB in ​​executing AIoT tasks.

[0249] (b) AIoT process operation information. The AIoT process operation information includes operations such as Start, Suspend, Resume, Release, Cancel, and End.

[0250] (c) Transaction ID information, used to indicate the Transaction ID available to the Reader, including at least one of the following:

[0251] (c1) Transaction ID: The AIoT CN node configures a Transaction ID for each Reader. This allows multiple Readers to use the same Transaction ID when executing the same AIoT service, avoiding duplicate responses from the AIoT device. The AIoT service can also be represented by an AIoT session or a Correlation ID.

[0252] (c2) Available Transaction ID Range. The AIoT CN node configures an available Transaction ID range for the Reader, and the Reader determines the Transaction ID within this range. It is understood that when multiple Readers execute AIoT services simultaneously, the AIoT CN node provides the Reader with selectable unused Transaction IDs to prevent multiple Readers from using the same Transaction ID.

[0253] (c3) At least one Transaction ID that has been used. The AIoT CN node provides the Reader with the Transaction IDs that have been used. The Reader needs to use a Transaction ID that is different from the Transaction ID that has been used.

[0254] The first information may be included in a first message, and the first message includes at least one of the following:

[0255] Inventory Request, for example, the first information can be included in Inventory Assistance Information, as shown in Figure 4b;

[0256] Command Request, for example, the first information may be included in Command Assistance Information;

[0257] AIoT task request messages are messages used to request gNBs to perform AIoT tasks, such as sensor data reporting and positioning.

[0258] Including the first information in the above AIoT task-related request messages helps the gNB execute the AIoT process according to the scheduling requirements of the core network node.

[0259] Optionally, the AIoT core network node schedules a target gNB, which includes at least one of the following:

[0260] The gNB in ​​the gNB list is at least one gNB selected by the AIoT service;

[0261] The gNB corresponding to the Reader list is determined based on at least one Reader selected for AIoT services.

[0262] The gNB corresponding to the AIoT area is determined based on the AIoT area selected for the AIoT service.

[0263] There are duplicate gNBs.

[0264] In this way, determining the target gNB that needs to be scheduled based on the above information can reduce the signaling load.

[0265] Step (2): gNB executes AIoT processes, such as inventory or commands, based on the first information.

[0266] Optionally, the gNB performing the AIoT process based on the first information includes any of the following:

[0267] gNB executes the AIoT process based on AIoT execution time information;

[0268] gNB can pause, suspend, or terminate an ongoing AIoT process.

[0269] gNB continues to execute the AIoT process, which may have been previously paused or suspended;

[0270] The gNB re-executes the AIoT process, which may have been terminated previously.

[0271] The above methods allow for flexible coordination of gNBs to execute AIoT processes.

[0272] Optionally, if the first message contains the first information, the gNB executes the AIoT process based on the first information. If the first message does not contain the first information, the gNB directly executes the AIoT process. It can be understood that the AIoT core network node sends the first information when it needs to schedule multiple gNBs; or, the AIoT core network node does not send the first information when it does not need to schedule gNBs to execute the AIoT process, i.e., the first information is not carried in the first message.

[0273] In this way, gNBs can be flexibly scheduled to execute AIoT processes, avoiding conflicts between multiple gNBs and reducing the signaling load between nodes.

[0274] Optionally, the gNB sends a first response message to the AIoT core network node. This first response message can be included in the inventory response. The first response message is a response to the first information, indicating confirmation of receipt of the first information or completion of the operation indicated by the first information. Based on the first response message, the AIoT core network node can continue to schedule other Readers (such as gNB, UE Reader, etc.) to execute the AIoT process, avoiding conflicts between Readers executing AIoT services.

[0275] Optionally, the gNB receives the first message sent by the AIoT core network node multiple times. It is understood that steps (1) and (2) above can be repeated, as shown in message 1a and message 1b in Figure 4b.

[0276] As shown in Figure 4b, taking the inventory process as an example, the first information is carried in the inventory request, and the first response information is carried in the inventory response. The above step (2) is executed in the inventory procedure over A-IoT radio interface.

[0277] An AIoT core network node can request the gNB to pause its AIoT inventory process in message 1a, and then request the gNB to continue its AIoT inventory process in message 1b.

[0278] It is understood that during the period when the gNB suspends its AIoT inventory process, the AIoT core network node can schedule other gNBs to perform the AIoT process. These other gNBs may interfere with the gNB in ​​question, have overlapping coverage, or be inventorying identical or partially identical AIoT devices.

[0279] This example demonstrates how AIOTF schedules Readers to perform AIoT services. On the one hand, this reduces or avoids conflicts between Readers; on the other hand, it prevents failures when multiple Readers perform inventory checks or commands on the same AIoT device.

[0280] Example 2:

[0281] This example illustrates how an AIoT core network node (first node) schedules a UE Reader (first device).

[0282] In this example, with at least one UE Reader deployed on the gNB, the AIoT core network node (such as AIOTF) schedules the UE Reader to execute AIoT services.

[0283] As shown in Figure 5a, this example includes the following signaling flow:

[0284] Step (1): The UE Reader receives the first information sent by the AIoT core network node (AIoT CN Node). The first information is used to schedule the UE Reader to execute AIoT services or AIoT processes, or to indicate the execution time information of the AIoT process. The AIoT core network node can be AIOTF or AMF.

[0285] The first information includes at least one of the following:

[0286] (a) AIoT execution time information.

[0287] For example, AIoT execution time information may include the time period for executing AIoT services or processes. This time period may be an absolute time period, such as an absolute time period [00:00:10~00:00:20], or a time period starting from the time the message containing the first information is received, such as 10 minutes.

[0288] The AIoT execution time information may include an execution duration, such as 20 seconds. This means that after receiving the first information, the UE Reader executes the AIoT service or AIoT process within this execution duration. Optionally, the execution duration may refer to a maximum execution duration, meaning that the UE Reader ends or pauses the AIoT process after reaching the maximum execution duration. The UE Reader can start or continue the paused AIoT process after receiving the first information or an AIoT task request message (such as an inventory request or command request) sent by the AIoT core network.

[0289] The AIoT execution time information may include periodic time, which includes period, duration, start time or time offset, etc.

[0290] Alternatively, AIoT execution time information can include a Paging Round, which represents the time period for executing AIoT services or processes based on the UE Reader completing one or more rounds of AIoT paging. This allows the UE Reader to complete at least one round of inventory processing, thereby generating an inventory report and improving the efficiency of the UE Reader in executing AIoT tasks.

[0291] (b) AIoT process operation information. The AIoT process operation information includes operations such as Start, Suspend, Resume, Release, Cancel, and End.

[0292] (c) Transaction ID information, used to indicate the Transaction ID available to the Reader, including at least one of the following:

[0293] (c1) Transaction ID: The AIoT CN node configures a Transaction ID for each Reader. This allows multiple Readers to use the same Transaction ID when executing the same AIoT service, avoiding duplicate responses from the AIoT device. The AIoT service can also be represented by an AIoT session or a Correlation ID.

[0294] (c2) Available Transaction ID Range. The AIoT CN node configures an available Transaction ID range for the Reader, and the Reader determines the Transaction ID within this range. It is understood that when multiple Readers execute AIoT services simultaneously, the AIoT CN node provides the Reader with selectable unused Transaction IDs to prevent multiple Readers from using the same Transaction ID.

[0295] (c3) At least one Transaction ID that has been used. The AIoT CN node provides the Reader with the Transaction IDs that have been used. The Reader needs to use a Transaction ID that is different from the Transaction ID that has been used.

[0296] The first information may be included in a first message, and the first message includes at least one of the following:

[0297] Inventory Request, for example, the first information may be included in Inventory Assistance Information;

[0298] Command Request, for example, the first information may be included in Command Assistance Information;

[0299] AIoT task request messages are messages used to request the UE Reader to perform AIoT tasks, such as sensor data reporting and positioning.

[0300] Including the first information in the above AIoT task-related request messages helps the UE Reader execute the AIoT process according to the scheduling requirements of the core network node.

[0301] The first piece of information can be included in the NAS message.

[0302] The first information may be generated by AIoTF and then sent to the UE Reader via AMF and gNB; or, the first information may also be generated by AMF and then sent to the UE Reader via gNB.

[0303] Optionally, the AIoT core network node schedules a target UE Reader, which includes at least one of the following:

[0304] The UE Reader corresponding to the gNB list is the UE Reader under at least one gNB selected by the AIoT service;

[0305] The UE Readers in the UE Reader list are selected based on at least one UE Reader for the AIoT service;

[0306] The UE Reader corresponding to the AIoT area is determined based on the AIoT area selected for the AIoT service;

[0307] There is a UE Reader with duplicate coverage.

[0308] In this way, determining the target UE Reader that needs to be scheduled based on the above information can reduce the signaling load.

[0309] Step (2): The UE Reader executes AIoT processes, such as inventory or commands, based on the first information.

[0310] Optionally, the UE Reader performs the AIoT process based on the first information, including any of the following:

[0311] The UE Reader executes the AIoT process based on the AIoT execution time information;

[0312] The UE Reader can pause, suspend, or terminate the ongoing AIoT process.

[0313] The UE Reader continues to execute the AIoT process, which may have been previously paused or suspended;

[0314] The UE Reader re-executes the AIoT process, which may have been previously terminated.

[0315] The above methods allow for flexible coordination of the UE Reader to execute the AIoT process.

[0316] Optionally, if the first message contains the first information, the UE Reader executes the AIoT process based on the first information; if the first message does not contain the first information, the UE Reader directly executes the AIoT process. It can be understood that the AIoT core network node sends the first information when it needs to schedule multiple Readers; or, the AIoT core network node does not send the first information when it does not need to schedule Readers to execute the AIoT process, i.e., the first information is not carried in the first message.

[0317] In this way, Readers can be flexibly scheduled to execute AIoT processes, avoiding conflicts between multiple Readers and reducing signaling load between nodes.

[0318] Optionally, the UE Reader sends a first response message to the AIoT core network node. This first response message is a response to the first information, indicating confirmation of receipt of the first information or completion of the operation indicated by the first information. Based on the first response message, the AIoT core network node can continue to schedule other Readers (such as gNB, UE Reader, etc.) to execute the AIoT process, avoiding conflicts between Readers executing AIoT services.

[0319] Optionally, the UE Reader receives the first information sent by the AIoT core network node multiple times.

[0320] As shown in Figure 5b, taking the inventory process as an example, the first information is carried in the inventory request, and the first response information is carried in the inventory response. The above step (2) is executed in the inventory procedure over A-IoT radio interface.

[0321] The AIoT core network node can request the UE Reader to pause its AIoT inventory process in message 1a, and then the AIoT core network node can request the UE Reader to continue its AIoT inventory process in message 1b.

[0322] It is understood that during the period when the UE Reader suspends its AIoT inventory process, the AIoT core network node can schedule other Readers to perform the AIoT process. These other Readers may interfere with the UE Reader, have overlapping coverage, or be inventorying identical or partially identical AIoT devices.

[0323] In this example, the AIoT core network node (such as AIOTF) schedules the UE Reader to execute AIoT services. On the one hand, this reduces or avoids conflicts between Readers; on the other hand, it avoids failures when multiple Readers perform inventory checks or commands on the same AIoT device. The Reader includes the UE Reader, gNB, etc.

[0324] Example 3:

[0325] This example illustrates how gNB (first node) schedules UE Reader (first device).

[0326] In this example, with at least one UE Reader deployed on the gNB, the gNB schedules the UE Reader to perform AIoT services.

[0327] As shown in Figure 6a, this example includes the following signaling flow:

[0328] Step (1): The UE Reader receives the first information sent by the gNB. The first information is used to schedule the UE Reader to execute AIoT services or AIoT processes, or to indicate the execution time information of the AIoT process.

[0329] The content of the first information is the same as in Example 2. Furthermore, the gNB can also control the UE Reader to execute the AIoT process by allocating or coordinating AIoT radio resources. For example, the gNB can release the configured AIoT radio resources to stop the UE Reader from executing the AIoT process. Subsequently, the gNB can reconfigure the AIoT radio resources, causing the UE Reader to resume executing the AIoT process.

[0330] Optionally, the gNB provides the UE Reader with transaction ID information.

[0331] Transaction ID information, used to indicate the Transaction ID available to the Reader, includes at least one of the following:

[0332] (a1) Transaction ID: The gNB configures a Transaction ID for the Reader. This allows multiple Readers to use the same Transaction ID when executing the same AIoT service, avoiding duplicate responses from the AIoT device. The AIoT service can also be represented by an AIoT session or a Correlation ID.

[0333] (a2) Available Transaction ID Range. The gNB configures an available Transaction ID range for the Reader, and the Reader determines the Transaction ID within this range. It can be understood that when multiple Readers execute AIoT services simultaneously, the gNB provides the Reader with selectable unused Transaction IDs to prevent multiple Readers from using the same Transaction ID.

[0334] (a3) At least one Transaction ID that has been used. The gNB provides the Reader with the Transaction IDs that have been used. The Reader needs to use a Transaction ID that is different from the Transaction ID that has been used.

[0335] Optionally, the gNB generates the first information and sends it to the UE Reader. Alternatively, the gNB generates the first information according to the AMF's service request and sends it to the UE Reader.

[0336] The first information may be included in an RRC message.

[0337] Optionally, the gNB schedules a target UE Reader, which is within the coverage area of ​​the gNB or connected to the gNB.

[0338] Step (2): The UE Reader executes AIoT processes, such as inventory checks or commands, based on the first information.

[0339] Optionally, the UE Reader performs the AIoT process based on the first information, including any of the following:

[0340] The UE Reader executes the AIoT process based on the AIoT execution time information;

[0341] The UE Reader can pause, suspend, or terminate the ongoing AIoT process.

[0342] The UE Reader continues to execute the AIoT process, which may have been previously paused or suspended;

[0343] The UE Reader re-executes the AIoT process, which may have been previously terminated.

[0344] The above methods allow for flexible coordination of the UE Reader to execute the AIoT process.

[0345] Optionally, if the first message contains the first information, the UE Reader executes the AIoT process based on the first information; if the first message does not contain the first information, the UE Reader directly executes the AIoT process. It can be understood that the gNB sends the first information when it needs to schedule multiple Readers; or, the gNB does not send the first information when it does not need to schedule Readers to execute the AIoT process, i.e., the first information is not carried in the first message.

[0346] In this way, Readers can be flexibly scheduled to execute AIoT processes, avoiding conflicts between multiple Readers and reducing signaling load between nodes.

[0347] Optionally, the UE Reader sends a first response message to the gNB. This first response message is a response to the first information, indicating confirmation of receipt of the first information or completion of the operation indicated by the first information. Based on the first response message, the gNB can continue to schedule other Readers (such as the gNB, UE Reader, etc.) to execute the AIoT process, avoiding conflicts between Readers executing AIoT services.

[0348] Optionally, the UE Reader receives the first message sent by the gNB multiple times.

[0349] As shown in Figure 6b, taking the inventory process as an example, the first information is carried in the inventory request, and the first response information is carried in the inventory response. The above step (2) is executed in the inventory procedure over A-IoT radio interface.

[0350] The gNB can request the UE Reader to pause its AIoT inventory process in message 1a, and then request the UE Reader to continue its AIoT inventory process in message 1b.

[0351] It is understood that during the period when the UE Reader pauses its AIoT inventory process, the gNB can schedule other Readers to perform the AIoT process. These other Readers may interfere with the UE Reader, have overlapping coverage, or be inventorying identical or partially identical AIoT devices.

[0352] In this example, the gNB schedules the UE Reader to execute AIoT services. On the one hand, this reduces or avoids conflicts between Readers; on the other hand, it prevents failures when multiple Readers perform inventory checks or commands on the same AIoT device. The Readers include the UE Reader, gNB, etc.

[0353] Example 4:

[0354] This example illustrates how a Reader (the first device) executes an AIoT process according to a schedule.

[0355] In this example, if the AIoT process is interrupted, the Reader needs to restart the inventory process, initiate a new round of paging, or filter and select AIoT devices to avoid errors in the AIoT process and avoid repeated inventory checks.

[0356] In this example, Reader includes gNB, UE Reader, etc.

[0357] This example includes the following signaling flow:

[0358] Step (1): After receiving the first information, the Reader performs a first operation, including at least one of the following:

[0359] Pause or terminate the AIoT process;

[0360] Save the first information;

[0361] Retain business request information, such as inventory requests and command requests, for easy follow-up.

[0362] Maintain the state of the AIoT process, including: start, pause, continue, cancel, end, etc., so that AIoT tasks can be executed according to this state in the future;

[0363] The recording was interrupted during the AIoT process, which includes inventory, commands, etc.

[0364] The termination of the AIoT paging process on the AIoT wireless interface can be understood as the Reader ending the ongoing paging round. The next time the Reader needs to send a paging message, it will start the inventory again.

[0365] Maintain AIoT session information, such as AIoT Session and correlation ID, to facilitate the continuation of the AIoT session or AIoT service in the future.

[0366] Save the Transaction ID so that it can be used in the future to execute AIoT processes over the AIoT air interface;

[0367] Maintain AIoT device context information, such as NGAP Context;

[0368] The Transaction ID is determined based on the business identification information.

[0369] For example, when the Reader is performing the AIoT inventory process, it receives the first message from the AIoT core network node to pause or terminate the AIoT process. The Reader then pauses or terminates the AIoT process. When the Reader is requested to continue or restart the AIoT process, it can correctly continue the unfinished AIoT tasks. For example, in the AIoT inventory service, the Reader cannot send an access timing indication message or an R2D trigger message to continue the inventory; instead, it must send a paging message to initiate a new paging process.

[0370] Step (2): The Reader performs a second operation based on the new first information received.

[0371] The second operation includes at least one of the following:

[0372] (b1) Continue or begin the AIoT process;

[0373] For the same AIoT session or Correlation ID, the Reader uses the same Transaction ID as the previous AIoT process.

[0374] Optionally, AIoT devices that have completed their transactions can be filtered out, or AIoT devices that have not completed their transactions can be paged.

[0375] For AIoT devices that have completed old tasks and then executed new tasks sent by other Readers, the old tasks might still be treated as new tasks, leading to duplicate inventory responses. Using initial paging, which carries AIoT device selection information, and filters out devices that have already completed tasks, can avoid duplicate inventory responses.

[0376] (b2) Send a paging message containing access resource configuration, or in other words, send an initial paging message without using subsequent paging, access timing messages, R2D trigger messages, or other messages to continue the interrupted AIoT process.

[0377] Because the initial paging configuration in the AIoT device may have been cleared after an interruption, this method allows the AIoT device to be provided with access resource configuration again.

[0378] Example 5:

[0379] This example demonstrates how a Reader initiates a negotiation.

[0380] In this example, when a Reader initiates an AIoT process, it requests the gNB or AIoT core network node to coordinate with other Readers to avoid process conflicts between Readers, or for Readers to negotiate the AIoT execution time with each other.

[0381] In this example, Reader includes gNB, UE Reader, etc.

[0382] Scenario 1: For the case where the AIoT core network node (first node) schedules the NG-RAN node (first device) to execute AIoT services, the corresponding signaling flow is as follows:

[0383] Step (0): Optionally, the gNB sends third information to the AIoT core network node for at least one of the following:

[0384] The gNB will be instructed to initiate the AIoT process;

[0385] Request the AIoT core network node to coordinate the gNB to execute the AIoT process;

[0386] Request the AIoT core network node to send the first information;

[0387] Business identification information, such as the Transaction ID used.

[0388] Steps (1) to (2): Same as steps (1) to (2) in Example 1.

[0389] Scenario 2: For the case where the AIoT core network node (first node) schedules the UE Reader (first device) to execute AIoT services, the corresponding signaling flow is as follows:

[0390] Step (0): Optionally, the UE Reader sends third information to the AIoT core network node for at least one of the following:

[0391] The UE Reader is instructed to initiate the AIoT process;

[0392] Request the AIoT core network node to coordinate the UE Reader to execute the AIoT process;

[0393] Request the AIoT core network node to send the first information;

[0394] Business identification information, such as the Transaction ID used.

[0395] Steps (1) to (2): Same as steps (1) to (2) in Example 2.

[0396] Scenario 3: For the case where the gNB (first node) schedules the UE Reader (first device) to execute AIoT services, the corresponding signaling process is as follows:

[0397] Step (0): Optionally, the UE Reader sends third information to the gNB for at least one of the following:

[0398] The UE Reader is instructed to initiate the AIoT process;

[0399] Request gNB to coordinate UE Reader to execute AIoT process;

[0400] Request gNB to send the first information;

[0401] Business identification information, such as the Transaction ID used.

[0402] Steps (1) to (2): Same as steps (1) to (2) in Example 3.

[0403] Scenario 4: Readers negotiate the AIoT execution time with each other.

[0404] Optionally, when the first Reader is about to execute the AIoT process, the first Reader (first device) sends a first instruction message to the second Reader (second device) to instruct the first Reader to start executing the AIoT process; optionally, the first Reader may also send the Transaction ID used, etc., to the second Reader.

[0405] Optionally, the second Reader sends a second response message to the first Reader to indicate that the first indication message has been received;

[0406] After receiving the second response information, the first Reader begins to execute the AIoT process.

[0407] Optionally, when the first Reader is about to end the AIoT process, the first Reader sends a first instruction message to the second Reader to instruct the first Reader to end the execution of the AIoT process; optionally, the first Reader may also send the Transaction ID used, etc., to the second Reader.

[0408] Optionally, the second Reader sends a second response message to the first Reader to indicate that the first indication message has been received.

[0409] In this example, while allowing Readers to initiate new AIoT services or AIoT processes on their own, Readers are also allowed to initiate negotiations to determine the timing of AIoT process execution and suspend the AIoT processes of other Readers that may conflict with each other, thereby reducing conflicts within the system and improving system efficiency.

[0410] The solution proposed in this application, which schedules Readers to execute AIoT services, reduces or avoids conflicts between Readers and prevents failures when multiple Readers perform inventory checks or commands on the same AIoT device. This application's implementation reduces system conflicts and improves system efficiency.

[0411] Referring to Figure 7, which is a flowchart of an operation execution method provided in an embodiment of this application, the operation execution method includes the following steps:

[0412] Step 201: The first node sends the first information to the first device;

[0413] The first information includes at least one of the following: execution time information of the AIoT process; control information of the AIoT process; and service identification information.

[0414] Optionally, the control information of the AIoT process is used to indicate any of the following:

[0415] Start AIoT process, pause AIoT process, suspend AIoT process, continue AIoT process, release AIoT process, cancel AIoT process, end AIoT process;

[0416] And / or,

[0417] The service identification information includes at least one of the following: one or more service identifiers that can be used in the AIoT process, and at least one service identifier that has been used;

[0418] And / or,

[0419] The execution time information is characterized by at least one of the following: time range; number of paging rounds; periodic time information; execution duration.

[0420] Optionally, the first information is carried in at least one of the following:

[0421] Inventory request; Command request; AIoT task request; RRC message; NAS message.

[0422] Optionally, the method further includes:

[0423] The first node receives a first response message sent by the first device. The first response message is used to indicate that the first message has been received, or to indicate that the operation indicated by the first message has been completed.

[0424] Optionally, the first information is used to schedule the first device to perform the first operation;

[0425] The first operation includes any one of the following:

[0426] The AIoT process is executed based on the execution time information of the AIoT process;

[0427] Pause, suspend, or terminate the AIoT process;

[0428] Continue executing the AIoT process;

[0429] Execute the AIoT process again;

[0430] The business identifier of the AIoT process is determined based on the business identifier information.

[0431] Optionally, if the first operation includes pausing, suspending, or terminating the AIoT process, the method further includes:

[0432] The first node sends second information to the first device, the second information being used to schedule the first device to perform a second operation;

[0433] The second operation includes at least one of the following:

[0434] Continue the AIoT process or begin the AIoT process;

[0435] Send a paging message.

[0436] Optionally, the method further includes:

[0437] The first node allocates or coordinates AIoT wireless resources for at least one of the first and second operations.

[0438] Optionally, the method further includes:

[0439] The first node receives third information sent by the first device, the third information being used for at least one of the following:

[0440] The first device is instructed to initiate the AIoT process;

[0441] The first node is requested to coordinate the first device to execute the AIoT process.

[0442] The first node is requested to send the first information.

[0443] Optionally, the first device is an access network device, and the first node is an AIoT core network node;

[0444] or,

[0445] The first device is a user equipment (UE) reader / writer, and the first node is an AIoT core network node;

[0446] or,

[0447] The first device is a UE reader / writer, and the first node is an access network device.

[0448] Optionally, the first device is determined by the first node based on at least one of the following:

[0449] The access network device selected by the first node for AIoT services;

[0450] The reader / writer selected by the first node for AIoT services;

[0451] The AIoT region selected by the first node for AIoT services;

[0452] The target reader / writer overlaps with other readers / writers.

[0453] The AIoT service refers to the AIoT service corresponding to the AIoT process.

[0454] It should be noted that this embodiment is an implementation of the first node corresponding to the embodiment shown in Figure 3. For the specific implementation, please refer to the relevant description of the embodiment shown in Figure 3. To avoid repetition, this embodiment will not be described again.

[0455] The operation execution method provided in this application can be executed by an operation execution device. This application uses an operation execution device executing the operation execution method as an example to illustrate the operation execution device provided in this application.

[0456] This application provides an operation execution device. As an example, the operation execution device may be a communication device or a component within a communication device, such as a chip. The communication device may be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal may include, but is not limited to, the type of terminal 11 listed above, and the network-side device may include, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0457] The operation execution device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, etc., such as central processing units (CPUs), microprocessors, digital signal processors (DSPs), artificial intelligence (AI) processors, graphics processing units (GPUs), application-specific integrated circuits (ASICs), network processors (NPs), field-programmable gate arrays (FPGAs), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceivers, pins, circuits, buses, radio frequency units, etc.

[0458] Specifically, referring to Figure 8, when the operation execution device is the first device or a component of the first device, the operation execution device 300 includes:

[0459] Processing module 301 is used to perform the target operation;

[0460] The target operation includes at least one of the following:

[0461] A first operation is performed based on first information sent by a first node, wherein the first operation is associated with an environmental Internet of Things (AIoT) process, and the first information includes at least one of the following: execution time information of the AIoT process; control information of the AIoT process; and service identification information.

[0462] Send at least one of a first indication message and an AIoT process execution time message to the second device, wherein the first indication message is used to indicate that the first device has started executing the AIoT process, or the first indication message is used to indicate that the first device has finished executing the AIoT process.

[0463] Optionally, the control information of the AIoT process is used to indicate any of the following: start the AIoT process, pause the AIoT process, suspend the AIoT process, continue the AIoT process, release the AIoT process, cancel the AIoT process, or end the AIoT process;

[0464] And / or,

[0465] The service identification information includes at least one of the following: one or more service identifiers that can be used in the AIoT process, and at least one service identifier that has been used;

[0466] And / or,

[0467] The execution time information is characterized by at least one of the following: time range; number of paging rounds; periodic time information; execution duration.

[0468] Optionally, the first information is carried in at least one of the following:

[0469] Inventory request; Command request; AIoT task request; Radio Resource Control (RRC) message; Non-Access Stratum (NAS) message.

[0470] Optionally, the device further includes:

[0471] The sending module is used to send a first response message to the first node. The first response message is used to indicate that the first message has been received, or to indicate that the operation indicated by the first message has been completed.

[0472] Optionally, the first operation includes any one of the following:

[0473] The AIoT process is executed based on the execution time information of the AIoT process;

[0474] Pause, suspend, or terminate the AIoT process;

[0475] Continue executing the AIoT process;

[0476] Execute the AIoT process again;

[0477] The business identifier of the AIoT process is determined based on the business identifier information.

[0478] Optionally, when the first operation includes pausing, suspending, or terminating the AIoT process, the first operation further includes at least one of the following:

[0479] Save the first information;

[0480] Retain the business request information of the AIoT process;

[0481] Maintain the state of the AIoT process;

[0482] The AIoT process was interrupted during recording;

[0483] The AIoT paging process of the AIoT wireless interface terminates the aforementioned AIoT process;

[0484] Maintain AIoT session information for the AIoT process;

[0485] Save the service identifier of the AIoT process;

[0486] Maintain the AIoT device context information during the AIoT process.

[0487] Optionally, if the first operation includes pausing, suspending, or ending the AIoT process, the processing module is further configured to: perform a second operation based on second information sent by the first node, wherein the second information is used to indicate whether to continue the AIoT process or start the AIoT process;

[0488] The second operation includes at least one of the following:

[0489] Continue the AIoT process or begin the AIoT process;

[0490] Send a paging message.

[0491] Optionally, for the same AIoT session or AIoT service, the saved service identifier can be used in the second operation, or the service identifier that was applied before the second operation can continue to be used.

[0492] Optionally, the transmitting module of the device is further configured to:

[0493] Send third information to the first node, the third information being used for at least one of the following:

[0494] The first device is instructed to initiate the AIoT process;

[0495] The first node is requested to coordinate the first device to execute the AIoT process.

[0496] The first node is requested to send the first information.

[0497] Optionally, the device further includes:

[0498] The receiving module is used to receive the first message sent by the first node;

[0499] Wherein, if the first message carries the first information, the first device performs the first operation based on the first information sent by the first node; or,

[0500] If the first message does not carry the first information, the first device performs the AIoT process.

[0501] Optionally, when sending at least one of the first instruction information and the execution time information of the AIoT process to the second device, the sending module is further configured to:

[0502] Send the service identifier of the AIoT process to the second device.

[0503] Optionally, the first device is an access network device, and the first node is an AIoT core network node;

[0504] or,

[0505] The first device is a user equipment (UE) reader / writer, and the first node is an AIoT core network node;

[0506] or,

[0507] The first device is a UE reader / writer, and the first node is an access network device;

[0508] or,

[0509] Both the first device and the second device are UE readers or access network devices;

[0510] or,

[0511] The first device is a UE reader / writer, and the second device is an access network device.

[0512] Optionally, the first device is associated with at least one of the following:

[0513] The access network device selected by the first node for AIoT services;

[0514] The reader / writer selected by the first node for AIoT services;

[0515] The AIoT region selected by the first node for AIoT services;

[0516] The target reader / writer overlaps with other readers / writers.

[0517] The AIoT service mentioned above refers to the AIoT service corresponding to the AIoT process.

[0518] Referring to Figure 9, when the operation execution device is a first node or a component within the first node, the operation execution device 400 includes:

[0519] The sending module 401 is used to send first information to the first device;

[0520] The first information includes at least one of the following: execution time information of the AIoT process; control information of the AIoT process; and service identification information.

[0521] Optionally, the control information of the AIoT process is used to indicate any of the following:

[0522] Start AIoT process, pause AIoT process, suspend AIoT process, continue AIoT process, release AIoT process, cancel AIoT process, end AIoT process;

[0523] And / or,

[0524] The service identification information includes at least one of the following: one or more service identifiers that can be used in the AIoT process, and at least one service identifier that has been used;

[0525] And / or,

[0526] The execution time information is characterized by at least one of the following: time range; number of paging rounds; periodic time information; execution duration.

[0527] Optionally, the first information is carried in at least one of the following:

[0528] Inventory request; Command request; AIoT task request; RRC message; NAS message.

[0529] Optionally, the device further includes:

[0530] The receiving module is configured to receive first response information sent by the first device, wherein the first response information is used to indicate that the first information has been received, or to indicate that the operation indicated by the first information has been completed.

[0531] Optionally, the first information is used to schedule the first device to perform the first operation;

[0532] The first operation includes any one of the following:

[0533] The AIoT process is executed based on the execution time information of the AIoT process;

[0534] Pause, suspend, or terminate the AIoT process;

[0535] Continue executing the AIoT process;

[0536] Execute the AIoT process again;

[0537] The business identifier of the AIoT process is determined based on the business identifier information.

[0538] Optionally, if the first operation includes pausing, suspending, or ending the AIoT process, the sending module is further configured to: send second information to the first device, the second information being used to schedule the first device to perform a second operation;

[0539] The second operation includes at least one of the following:

[0540] Continue the AIoT process or begin the AIoT process;

[0541] Send a paging message.

[0542] Optionally, the device further includes:

[0543] The processing module is configured to allocate or coordinate AIoT wireless resources for at least one of the first and second operations.

[0544] Optionally, the receiving module of the device is configured to: receive third information sent by the first device, the third information being used for at least one of the following:

[0545] The first device is instructed to initiate the AIoT process;

[0546] The first node is requested to coordinate the first device to execute the AIoT process.

[0547] The first node is requested to send the first information.

[0548] Optionally, the first device is an access network device, and the first node is an AIoT core network node;

[0549] or,

[0550] The first device is a user equipment (UE) reader / writer, and the first node is an AIoT core network node;

[0551] or,

[0552] The first device is a UE reader / writer, and the first node is an access network device.

[0553] Optionally, the first device is determined by the first node based on at least one of the following:

[0554] The access network device selected by the first node for AIoT services;

[0555] The reader / writer selected by the first node for AIoT services;

[0556] The AIoT region selected by the first node for AIoT services;

[0557] The target reader / writer overlaps with other readers / writers.

[0558] The AIoT service refers to the AIoT service corresponding to the AIoT process.

[0559] The operation execution device provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG3 or FIG7 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0560] As shown in Figure 10, this application embodiment also provides a communication device 500, including a processor 501 and a memory 502. The memory 502 stores a program or instructions that can run on the processor 501. For example, when the communication device 500 is a first device, when the program or instructions are executed by the processor 501, they implement the various steps of the above-described operation execution method embodiment and achieve the same technical effect. When the communication device 500 is a first node, when the program or instructions are executed by the processor 501, they implement the various steps of the above-described operation execution method embodiment and achieve the same technical effect. To avoid repetition, this will not be repeated here.

[0561] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the method embodiment shown in FIG3. This terminal embodiment corresponds to the first device-side method embodiment described above, and all implementation processes and methods of the above method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. The terminal can be the operation execution device shown in FIG8. Specifically, FIG11 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0562] The terminal 600 includes, but is not limited to, at least some of the following components: radio frequency unit 601, network module 602, audio output unit 603, input unit 604, sensor 605, display unit 606, user input unit 607, interface unit 608, memory 609, and processor 610.

[0563] Those skilled in the art will understand that terminal 600 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to processor 610 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 11 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0564] It should be understood that, in this embodiment, the input unit 604 may include a graphics processor 6041 and a microphone 6042. The graphics processor 6041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 606 may include a display panel 6061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 607 includes at least one of a touch panel 6071 and other input devices 6072. The touch panel 6071 is also called a touch screen. The touch panel 6071 may include two parts: a touch detection device and a touch controller. Other input devices 6072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0565] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 601 can transmit it to the processor 610 for processing; in addition, the radio frequency unit 601 can send uplink data to the network-side device. Typically, the radio frequency unit 601 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0566] The memory 609 can be used to store software programs or instructions, as well as various data. The memory 609 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 609 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 609 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0567] Processor 610 may include one or more processing units; optionally, processor 610 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 610.

[0568] The processor 610 is used for:

[0569] Perform the target operation;

[0570] The target operation includes at least one of the following:

[0571] A first operation is performed based on first information sent by a first node, wherein the first operation is associated with an environmental Internet of Things (AIoT) process, and the first information includes at least one of the following: execution time information of the AIoT process; control information of the AIoT process; and service identification information.

[0572] Send at least one of a first indication message and an AIoT process execution time message to the second device, wherein the first indication message is used to indicate that the first device has started executing the AIoT process, or the first indication message is used to indicate that the first device has finished executing the AIoT process.

[0573] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description in Figure 3 of the method embodiment and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0574] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method embodiment shown in FIG7. This network-side device embodiment corresponds to the above-described first device or first node method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.

[0575] Specifically, this application embodiment also provides a network-side device, which can be the operation execution device shown in FIG8 or FIG9. As shown in FIG12, the network-side device 700 includes: an antenna 701, a radio frequency device 702, a baseband device 703, a processor 704, and a memory 705. The antenna 701 is connected to the radio frequency device 702. In the uplink direction, the radio frequency device 702 receives information through the antenna 701 and sends the received information to the baseband device 703 for processing. In the downlink direction, the baseband device 703 processes the information to be transmitted and sends it to the radio frequency device 702. The radio frequency device 702 processes the received information and transmits it through the antenna 701.

[0576] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 703, which includes a baseband processor.

[0577] The baseband device 703 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG12. One of the chips is, for example, a baseband processor, which is connected to the memory 705 via a bus interface to call the program or instructions in the memory 705 to execute the network-side device operation shown in the above method embodiment.

[0578] The network-side device may also include a network interface 706, such as a Common Public Radio Interface (CPRI).

[0579] In the case where the network-side device is the first device, the processor 704 is used for:

[0580] Perform the target operation;

[0581] The target operation includes at least one of the following:

[0582] A first operation is performed based on first information sent by a first node, wherein the first operation is associated with an environmental Internet of Things (AIoT) process, and the first information includes at least one of the following: execution time information of the AIoT process; control information of the AIoT process; and service identification information.

[0583] Send at least one of a first indication message and an AIoT process execution time message to the second device, wherein the first indication message is used to indicate that the first device has started executing the AIoT process, or the first indication message is used to indicate that the first device has finished executing the AIoT process.

[0584] In the case where the network-side device is the first node, network interface 706 is used for:

[0585] Send the first message to the first device;

[0586] The first information includes at least one of the following: execution time information of the AIoT process; control information of the AIoT process; and service identification information.

[0587] In addition, the network-side device 700 of this application embodiment also includes: a program or instructions stored in a memory 705 and executable on a processor 704. The processor 704 calls the program or instructions in the memory 705 to execute the methods executed by the modules shown in FIG8 or FIG9 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0588] Specifically, this application also provides a network-side device. As shown in FIG13, the network-side device 800 includes a processor 801, a network interface 802, and a memory 803. The network-side device may be the operation execution device shown in FIG8 or FIG9. The network interface 802 is, for example, a common public radio interface (CPRI).

[0589] In the case where the network-side device is the first device, the processor 801 is used for:

[0590] Perform the target operation;

[0591] The target operation includes at least one of the following:

[0592] A first operation is performed based on first information sent by a first node, wherein the first operation is associated with an environmental Internet of Things (AIoT) process, and the first information includes at least one of the following: execution time information of the AIoT process; control information of the AIoT process; and service identification information.

[0593] Send at least one of a first indication message and an AIoT process execution time message to the second device, wherein the first indication message is used to indicate that the first device has started executing the AIoT process, or the first indication message is used to indicate that the first device has finished executing the AIoT process.

[0594] In the case where the network-side device is the first node, network interface 802 is used for:

[0595] Send the first message to the first device;

[0596] The first information includes at least one of the following: execution time information of the AIoT process; control information of the AIoT process; and service identification information.

[0597] In addition, the network-side device 800 in this application embodiment also includes: a program or instructions stored in a memory 803 and executable on a processor 801. The processor 801 calls the program or instructions in the memory 803 to execute the methods executed by the modules shown in FIG8 or FIG9 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0598] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described operation execution method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0599] The processor mentioned above is either the processor in the terminal described in the above embodiments or the processor in the network-side device. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0600] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described operation execution method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0601] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0602] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described operation execution method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0603] This application also provides a wireless communication system, including: a first device and a first node, wherein the first device can be used to execute the steps of the operation execution method applied to the first device as described above, and the first node can be used to execute the steps of the operation execution method applied to the first node as described above.

[0604] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0605] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.), and the computer software product includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0606] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. An operation execution method, comprising: The first device performs the target operation; The target operation includes at least one of the following: A first operation is performed based on first information sent by a first node, wherein the first operation is associated with an environmental Internet of Things (AIoT) process, and the first information includes at least one of the following: execution time information of the AIoT process; control information of the AIoT process; and service identification information. Send at least one of a first indication message and an AIoT process execution time message to the second device, wherein the first indication message is used to indicate that the first device has started executing the AIoT process, or the first indication message is used to indicate that the first device has finished executing the AIoT process.

2. The method according to claim 1, wherein, The control information of the AIoT process is used to indicate any of the following: start the AIoT process, pause the AIoT process, suspend the AIoT process, continue the AIoT process, release the AIoT process, cancel the AIoT process, or end the AIoT process; And / or, The service identification information includes at least one of the following: one or more service identifiers that can be used in the AIoT process, and at least one service identifier that has been used; And / or, The execution time information is characterized by at least one of the following: time range; number of paging rounds; periodic time information; execution duration.

3. The method according to claim 1 or 2, wherein, The first information is carried in at least one of the following: Inventory request; Command request; AIoT task request; Radio Resource Control (RRC) message; Non-Access Stratum (NAS) message.

4. The method according to any one of claims 1-3, wherein, The method further includes: The first device sends a first response message to the first node. The first response message is used to indicate that the first message has been received, or to indicate that the operation indicated by the first message has been completed.

5. The method according to any one of claims 1-4, wherein, The first operation includes any one of the following: The AIoT process is executed based on the execution time information of the AIoT process; Pause, suspend, or terminate the AIoT process; Continue executing the AIoT process; Execute the AIoT process again; The business identifier of the AIoT process is determined based on the business identifier information.

6. The method according to claim 5, wherein, When the first operation includes pausing, suspending, or ending the AIoT process, the first operation further includes at least one of the following: Save the first information; Retain the business request information of the AIoT process; Maintain the state of the AIoT process; The AIoT process was interrupted during recording; The AIoT paging process of the AIoT wireless interface terminates the aforementioned AIoT process; Maintain AIoT session information for the AIoT process; Save the service identifier of the AIoT process; Maintain the AIoT device context information during the AIoT process.

7. The method according to any one of claims 1-6, wherein, If the first operation includes pausing, suspending, or terminating the AIoT process, the method further includes: The first device performs a second operation based on second information sent by the first node, the second information being used to indicate whether to continue the AIoT process or to start the AIoT process; The second operation includes at least one of the following: Continue the AIoT process or begin the AIoT process; Send a paging message.

8. The method according to claim 7, wherein, For the same AIoT session or AIoT service, the saved service identifier can be used in the second operation, or the service identifier that was applied before the second operation can continue to be used.

9. The method according to any one of claims 1-8, wherein, The method further includes: The first device sends third information to the first node, the third information being used for at least one of the following: The first device is instructed to initiate the AIoT process; The first node is requested to coordinate the first device to execute the AIoT process. The first node is requested to send the first information.

10. The method according to any one of claims 1-9, wherein, The first device performs a first operation based on the first information sent by the first node, including: The first device receives the first message sent by the first node; Wherein, if the first message carries the first information, the first device performs the first operation based on the first information sent by the first node; or, If the first message does not carry the first information, the first device performs the AIoT process.

11. The method according to any one of claims 1-10, wherein, When sending at least one of the first instruction information and the execution time information of the AIoT process to the second device, the method further includes: Send the service identifier of the AIoT process to the second device.

12. The method according to any one of claims 1-11, wherein, The first device is an access network device, and the first node is an AIoT core network node; or, The first device is a user equipment (UE) reader / writer, and the first node is an AIoT core network node; or, The first device is a UE reader / writer, and the first node is an access network device; or, Both the first device and the second device are UE readers or access network devices; or, The first device is a UE reader / writer, and the second device is an access network device.

13. The method according to any one of claims 1-12, wherein, The first device is associated with at least one of the following: The access network device selected by the first node for AIoT services; The reader / writer selected by the first node for AIoT services; The AIoT region selected by the first node for AIoT services; The target reader / writer overlaps with other readers / writers. The AIoT service mentioned above refers to the AIoT service corresponding to the AIoT process.

14. An operation execution method, comprising: The first node sends the first information to the first device; The first information includes at least one of the following: execution time information of the AIoT process; control information of the AIoT process; and service identification information.

15. The method according to claim 14, wherein, The control information for the AIoT process is used to indicate any one of the following: Start AIoT process, pause AIoT process, suspend AIoT process, continue AIoT process, release AIoT process, cancel AIoT process, end AIoT process; And / or, The service identification information includes at least one of the following: one or more service identifiers that can be used in the AIoT process, and at least one service identifier that has been used; And / or, The execution time information is characterized by at least one of the following: time range; number of paging rounds; periodic time information; execution duration.

16. The method according to claim 14 or 15, wherein, The first information is carried in at least one of the following: Inventory request; Command request; AIoT task request; RRC message; NAS message.

17. The method according to any one of claims 14-16, wherein, The method further includes: The first node receives a first response message sent by the first device. The first response message is used to indicate that the first message has been received, or to indicate that the operation indicated by the first message has been completed.

18. The method according to any one of claims 14-17, wherein, The first information is used to schedule the first device to perform the first operation; The first operation includes any one of the following: The AIoT process is executed based on the execution time information of the AIoT process; Pause, suspend, or terminate the AIoT process; Continue executing the AIoT process; Execute the AIoT process again; The business identifier of the AIoT process is determined based on the business identifier information.

19. The method according to claim 18, wherein, If the first operation includes pausing, suspending, or terminating the AIoT process, the method further includes: The first node sends second information to the first device, the second information being used to schedule the first device to perform a second operation; The second operation includes at least one of the following: Continue the AIoT process or begin the AIoT process; Send a paging message.

20. The method according to claim 18 or 19, wherein, The method further includes: The first node allocates or coordinates AIoT wireless resources for at least one of the first and second operations.

21. The method according to any one of claims 14-20, wherein, The method further includes: The first node receives third information sent by the first device, the third information being used for at least one of the following: The first device is instructed to initiate the AIoT process; The first node is requested to coordinate the first device to execute the AIoT process. The first node is requested to send the first information.

22. The method according to any one of claims 14-21, wherein, The first device is an access network device, and the first node is an AIoT core network node; or, The first device is a user equipment (UE) reader / writer, and the first node is an AIoT core network node; or, The first device is a UE reader / writer, and the first node is an access network device.

23. The method according to any one of claims 14-22, wherein, The first device is determined by the first node based on at least one of the following: The access network device selected by the first node for AIoT services; The reader / writer selected by the first node for AIoT services; The AIoT region selected by the first node for AIoT services; The target reader / writer overlaps with other readers / writers. The AIoT service mentioned above refers to the AIoT service corresponding to the AIoT process.

24. An operation execution device, comprising: The processing module is used to execute the target operation; The target operation includes at least one of the following: A first operation is performed based on first information sent by a first node, wherein the first operation is associated with an environmental Internet of Things (AIoT) process, and the first information includes at least one of the following: execution time information of the AIoT process; control information of the AIoT process; and service identification information. Send at least one of a first indication message and an AIoT process execution time message to the second device, wherein the first indication message is used to indicate that the first device has started executing the AIoT process, or the first indication message is used to indicate that the first device has finished executing the AIoT process.

25. The apparatus according to claim 24, wherein, The first operation includes any one of the following: The AIoT process is executed based on the execution time information of the AIoT process; Pause, suspend, or terminate the AIoT process; Continue executing the AIoT process; Execute the AIoT process again; The business identifier of the AIoT process is determined based on the business identifier information.

26. An operation execution device, comprising: The sending module is used to send first information to the first device; The first information includes at least one of the following: execution time information of the AIoT process; control information of the AIoT process; and service identification information.

27. A first device comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the operation execution method as claimed in any one of claims 1 to 13.

28. A first node comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the operation execution method as claimed in any one of claims 14 to 23.

29. A readable storage medium storing a program or instructions that, when executed by a processor, implement the steps of the operation execution method as claimed in any one of claims 1 to 13, or implement the steps of the operation execution method as claimed in any one of claims 14 to 23.