QoS processing method and device for AIoT service, terminal and network element

Abstract

The invention provides a QoS processing method and device of an AIoT service, a terminal and a network element, and the method comprises the steps that the terminal receives an AIoT service request message, and the AIoT service request message comprises a first AIoT service type; the terminal determines QoS information of an AIoT service corresponding to the first AIoT service type; according to the embodiment of the invention, the AIoT service type is associated with the QoS information of the AIoT service, and the terminal can determine the QoS information of the corresponding AIoT service according to the AIoT service type carried by the AIoT service request message, so that the QoS control of the AIoT service is realized to meet the performance requirement of the AIoT service.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of wireless communication, and particularly relates to a QoS processing method and device for AIoT service, a terminal and a network element. BACKGROUND

[0002] Ambient IoT (AIoT) is a new emerging Internet of Things technology, which can be widely applied to automatic logistics, smart power grids, internal logistics in production and manufacturing, and sensing data reporting in smart homes. For example, in the automatic warehouse scenario, AIoT technology can be used to count goods when the goods are put into and taken out of the warehouse. AIoT devices refer to devices that have no energy or only have very limited energy and communicate by obtaining energy from the external environment, such as Radio Frequency Identification (RFID) devices. AIoT devices generally have very low complexity and cost, very small data volume (for example, only tag information needs to be reported) and very low frequency (for example, only one data transmission may be performed).

[0003] When a terminal communicates with an AIoT device as a Reader, the terminal communicates with the network through a Uu interface. However, when the terminal communicates with the AIoT device as the Reader, how to meet the performance requirements of the AIoT service is a problem that has not been solved in the prior art. SUMMARY

[0004] The purpose of the embodiments of the present application is to provide a QoS processing method and device for AIoT service, a terminal and a network element, to solve the problem of how to meet the performance requirements of the AIoT service in the prior art.

[0005] To solve the above problem, the embodiments of the present application provide a service quality (QoS) processing method for AIoT service, which comprises the following steps:

[0006] The terminal receives an AIoT service request message, wherein the AIoT service request message comprises a first AIoT service type.

[0007] The terminal determines QoS information of the AIoT service corresponding to the first AIoT service type.

[0008] The QoS information of the AIoT service comprises at least one of the following information:

[0009] Time information required for performing one AIoT service;

[0010] Communication distance between the terminal and the AIoT device;

[0011] a number of AIoT devices performing AIoT services.

[0012] The first AIoT service type includes at least one of the following:

[0013] an inventory service;

[0014] a command service;

[0015] sensor data collection service;

[0016] a tracking service;

[0017] an actuator control service.

[0018] The AIoT service request message further includes QoS information of the AIoT service corresponding to the first AIoT service type.

[0019] The terminal determines the QoS information of the AIoT service corresponding to the first AIoT service type, including:

[0020] The terminal determines the QoS information of the AIoT service corresponding to the first AIoT service type according to the AIoT service request message.

[0021] The method further includes:

[0022] The terminal obtains one or more AIoT service types and QoS information of AIoT services corresponding to each different AIoT service type;

[0023] The terminal determines the QoS information of the AIoT service corresponding to the first AIoT service type according to the QoS information of the AIoT service corresponding to each different AIoT service type.

[0024] The terminal obtains one or more AIoT service types and QoS information of AIoT services corresponding to each different AIoT service type, including:

[0025] The terminal obtains one or more AIoT service types and QoS information of AIoT services corresponding to each different AIoT service type through a registration process;

[0026] Alternatively,

[0027] The terminal obtains one or more AIoT service types and QoS information of AIoT services corresponding to each different AIoT service type through an AIoT session establishment process.

[0028] The terminal obtains one or more AIoT service types and QoS information of AIoT services corresponding to each different AIoT service type through a registration process, including:

[0029] The terminal sends a registration request message to a target network element.

[0030] The terminal receives a registration acceptance message sent by the target network element, and the registration acceptance message includes AIoT service types authorized for the terminal to perform and QoS information of AIoT services corresponding to each AIoT service type.

[0031] The registration request message includes AIoT service types supported by the terminal.

[0032] The terminal obtains one or more AIoT service types and QoS information of AIoT services corresponding to each different AIoT service type through an AIoT session establishment process, including:

[0033] The terminal sends an AIoT session establishment request message to a target network element.

[0034] The terminal receives an AIoT session establishment response message sent by the target network element, and the AIoT session establishment response message includes AIoT service types authorized for the terminal to perform and QoS information of AIoT services corresponding to each AIoT service type.

[0035] The AIoT session establishment request message includes AIoT service types supported by the terminal.

[0036] The method further includes that the terminal determines that it can communicate with an AIoT device.

[0037] The terminal determines that it can communicate with an AIoT device, including:

[0038] The terminal sends a registration request message to a target network element, and the registration request message carries first indication information used to indicate a capability of the terminal to support communication with an AIoT device.

[0039] The terminal receives a registration acceptance message sent by the target network element, and the registration acceptance message carries second indication information used to indicate that the terminal is allowed to communicate with the AIoT device.

[0040] The method further includes:

[0041] The terminal performs the AIoT service according to the QoS information of the AIoT service.

[0042] The embodiment of the application further provides a QoS processing method of an AIoT service, and the method comprises the following steps:

[0043] The target network element sends an AIoT service request message to the terminal, wherein the AIoT service request message comprises a first AIoT service type; and the AIoT service request message is used for instructing the terminal to determine the QoS information of the AIoT service corresponding to the first AIoT service type.

[0044] The QoS information of the AIoT service comprises at least one of the following information:

[0045] Time information required for executing an AIoT service once;

[0046] Communication distance between the terminal and the AIoT device;

[0047] The number of AIoT devices for executing the AIoT service.

[0048] The first AIoT service type comprises at least one of the following:

[0049] Inventory service;

[0050] Command service;

[0051] Sensor data collection service;

[0052] Tracking service;

[0053] Actuator control service.

[0054] The AIoT service request message further comprises the QoS information of the AIoT service corresponding to the first AIoT service type.

[0055] The method further comprises the following steps:

[0056] The target network element sends one or more AIoT service types and the QoS information of the AIoT service corresponding to each different AIoT service type to the terminal.

[0057] The target network element sends one or more AIoT service types and the QoS information of the AIoT service corresponding to each different AIoT service type to the terminal, and the method comprises the following steps:

[0058] The target network element sends one or more AIoT service types and the QoS information of the AIoT service corresponding to each different AIoT service type to the terminal through a terminal registration process;

[0059] Or,

[0060] The target network element sends one or more AIoT service types and QoS information of AIoT services corresponding to each different AIoT service type to the terminal through an AIoT session establishment process.

[0061] The target network element sends one or more AIoT service types and QoS information of AIoT services corresponding to each different AIoT service type to the terminal through an AIoT session establishment process, including:

[0062] The target network element receives a registration request message sent by the terminal.

[0063] The target network element sends a registration acceptance message to the terminal, and the registration acceptance message includes AIoT service types authorized for the terminal to perform and QoS information of AIoT services corresponding to each AIoT service type.

[0064] The registration request message includes AIoT service types supported by the terminal.

[0065] The target network element sends one or more AIoT service types and QoS information of AIoT services corresponding to each different AIoT service type to the terminal through an AIoT session establishment process, including:

[0066] The target network element receives an AIoT session establishment request message sent by the terminal.

[0067] The target network element sends an AIoT session establishment response message to the terminal, and the AIoT session establishment response message includes AIoT service types authorized for the terminal to perform and QoS information of AIoT services corresponding to each AIoT service type.

[0068] The AIoT session establishment request message includes AIoT service types supported by the terminal.

[0069] The method further includes that the target network element indicates that the terminal can communicate with an AIoT device; and the target network element indicating that the terminal can communicate with an AIoT device includes:

[0070] The target network element receives a registration request message sent by the terminal and carrying first indication information, and the first indication information is used to indicate a capability of the terminal supporting communication with an AIoT device.

[0071] The target network element sends a registration acceptance message to the terminal and carrying second indication information, and the second indication information is used to indicate that the terminal is allowed to communicate with the AIoT device.

[0072] The embodiment of the application further provides a terminal, comprising a memory, a transceiver and a processor.

[0073] The memory is used for storing a computer program; the transceiver is used for transceiving data under the control of the processor; and the processor is used for reading the computer program in the memory and performing the following operations:

[0074] receiving an AIoT service request message, wherein the AIoT service request message comprises a first AIoT service type;

[0075] determining QoS information of an AIoT service corresponding to the first AIoT service type.

[0076] The QoS information of the AIoT service comprises at least one of the following information:

[0077] time information required for performing one AIoT service;

[0078] a communication distance between the terminal and an AIoT device;

[0079] a number of AIoT devices performing the AIoT service.

[0080] The first AIoT service type comprises at least one of the following:

[0081] inventory service;

[0082] command service;

[0083] sensor data collection service;

[0084] tracking service;

[0085] actuator control service.

[0086] The AIoT service request message further comprises QoS information of the AIoT service corresponding to the first AIoT service type.

[0087] The processor is further used for reading the computer program in the memory and performing the following operations:

[0088] determining, according to the AIoT service request message, the QoS information of the AIoT service corresponding to the first AIoT service type.

[0089] The processor is further used for reading the computer program in the memory and performing the following operations:

[0090] obtaining one or more AIoT service types and QoS information of an AIoT service corresponding to each different AIoT service type;

[0091] determine the QoS information of the AIoT service corresponding to the first AIoT service type according to the QoS information of the AIoT service corresponding to each different AIoT service type.

[0092] The processor is further configured to read a computer program in the memory and perform the following operations:

[0093] obtain one or more AIoT service types and the QoS information of the AIoT service corresponding to each different AIoT service type through a registration process;

[0094] or,

[0095] obtain one or more AIoT service types and the QoS information of the AIoT service corresponding to each different AIoT service type through an AIoT session establishment process.

[0096] The processor is further configured to read a computer program in the memory and perform the following operations:

[0097] send a registration request message to a target network element;

[0098] receive a registration acceptance message sent by the target network element, wherein the registration acceptance message includes the AIoT service types authorized to be executed by the terminal and the QoS information of the AIoT service corresponding to each AIoT service type.

[0099] The registration request message includes the AIoT service types supported by the terminal.

[0100] The processor is further configured to read a computer program in the memory and perform the following operations:

[0101] send an AIoT session establishment request message to a target network element;

[0102] receive an AIoT session establishment response message sent by the target network element, wherein the AIoT session establishment response message includes the AIoT service types authorized to be executed by the terminal and the QoS information of the AIoT service corresponding to each AIoT service type.

[0103] The AIoT session establishment request message includes the AIoT service types supported by the terminal.

[0104] The processor is further configured to read a computer program in the memory and perform the following operations:

[0105] determine that the terminal is capable of communicating with the AIoT device; wherein determining that the terminal is capable of communicating with the AIoT device includes:

[0106] sending a registration request message carrying first indication information to a target network element, the first indication information being used to indicate that the terminal supports the capability of communicating with an AIoT device;

[0107] receiving a registration accept message carrying second indication information sent by the target network element, the second indication information being used to indicate that the terminal is allowed to communicate with the AIoT device.

[0108] The processor is further configured to read the computer program in the memory and perform the following operations:

[0109] performing the AIoT service according to the QoS information of the AIoT service.

[0110] Embodiments of the present application also provide a target network element, comprising a memory, a transceiver, and a processor:

[0111] The memory is configured to store a computer program; the transceiver is configured to transceive data under the control of the processor; and the processor is configured to read the computer program in the memory and perform the following operations:

[0112] sending an AIoT service request message to a terminal, the AIoT service request message comprising a first AIoT service type; the AIoT service request message being used to instruct the terminal to determine the QoS information of the AIoT service corresponding to the first AIoT service type.

[0113] The AIoT service request message further comprises the QoS information of the AIoT service corresponding to the first AIoT service type.

[0114] The processor is further configured to read the computer program in the memory and perform the following operations:

[0115] sending one or more AIoT service types and the QoS information of the AIoT service corresponding to each different AIoT service type to a terminal.

[0116] The processor is further configured to read the computer program in the memory and perform the following operations:

[0117] sending one or more AIoT service types and the QoS information of the AIoT service corresponding to each different AIoT service type to a terminal through a terminal registration process;

[0118] alternatively,

[0119] sending one or more AIoT service types and the QoS information of the AIoT service corresponding to each different AIoT service type to a terminal through an AIoT session establishment process.

[0120] The processor is further configured to read a computer program in the memory and perform the following operations:

[0121] receive a registration request message sent by a terminal;

[0122] send a registration acceptance message to the terminal, the registration acceptance message including AIoT service types authorized to be executed by the terminal and QoS information of AIoT services corresponding to each AIoT service type.

[0123] The registration request message includes AIoT service types supported by the terminal.

[0124] The processor is further configured to read a computer program in the memory and perform the following operations:

[0125] receive an AIoT session establishment request message sent by a terminal;

[0126] send an AIoT session establishment response message to the terminal, the AIoT session establishment response message including AIoT service types authorized to be executed by the terminal and QoS information of AIoT services corresponding to each AIoT service type.

[0127] The AIoT session establishment request message includes AIoT service types supported by the terminal.

[0128] The processor is further configured to read a computer program in the memory and perform the following operations:

[0129] indicate that the terminal can communicate with an AIoT device; wherein indicating that the terminal can communicate with an AIoT device includes:

[0130] receive a registration request message sent by the terminal, the registration request message carrying first indication information, the first indication information being used to indicate a capability of the terminal to support communication with an AIoT device;

[0131] send a registration acceptance message to the terminal, the registration acceptance message carrying second indication information, the second indication information being used to indicate that the terminal is allowed to communicate with the AIoT device.

[0132] Embodiments of the present application also provide a QoS processing device for AIoT services, applied to a terminal, the device comprising:

[0133] a first receiving unit configured to receive an AIoT service request message, the AIoT service request message including a first AIoT service type;

[0134] a first determining unit configured to determine QoS information of an AIoT service corresponding to the first AIoT service type.

[0135] This application embodiment also provides a QoS processing device for AIoT services, applied to a target network element, the device comprising:

[0136] The first sending unit is configured to send an AIoT service request message to the terminal, the AIoT service request message including a first AIoT service type; the AIoT service request message is used to instruct the terminal to determine the QoS information of the AIoT service corresponding to the first AIoT service type.

[0137] This application also provides a processor-readable storage medium storing a program for causing the processor to perform the method described above.

[0138] The above-mentioned technical solution of this application has at least the following beneficial effects:

[0139] In the QoS processing method, apparatus, terminal, and network element of AIoT services in the embodiments of this application, the AIoT service type is associated with the QoS information of the AIoT service. The terminal can determine the QoS information of the corresponding AIoT service based on the AIoT service type carried in the AIoT service request message, thereby realizing QoS control of the AIoT service to meet the performance requirements of the AIoT service. Attached Figure Description

[0140] Figure 1 A block diagram illustrating a wireless communication system to which embodiments of this application may be applied;

[0141] Figure 2 This is a flowchart illustrating one of the steps of the QoS processing method for AIoT services provided in an embodiment of this application.

[0142] Figure 3 This is the second flowchart illustrating the steps of the QoS processing method for AIoT services provided in this application embodiment.

[0143] Figure 4 A flowchart illustrating Example 1 provided in the embodiments of this application;

[0144] Figure 5 A flowchart illustrating Example 2 provided in the embodiments of this application;

[0145] Figure 6 A flowchart illustrating Example 3 provided in the embodiments of this application;

[0146] Figure 7 This is a schematic diagram of the structure of the terminal provided in the embodiments of this application;

[0147] Figure 8 This is a schematic diagram illustrating the structure of the target network element provided in the embodiments of this application;

[0148] Figure 9 This is a schematic diagram of one of the structures of the QoS processing device for AIoT services provided in the embodiments of this application;

[0149] Figure 10 This is the second schematic diagram illustrating the structure of the QoS processing device for AIoT services provided in this application embodiment. Detailed Implementation

[0150] To make the technical problems, technical solutions and advantages of this application clearer, a detailed description will be provided below in conjunction with the accompanying drawings and specific embodiments.

[0151] Figure 1 This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal device 11 and a network-side device 12. The terminal device 11 can also be referred to as a terminal or a user equipment (UE). It should be noted that this application does not limit the specific type of the terminal 11. The network-side device 12 can be a base station or a core network. It should be noted that this application uses a base station in an NR system as an example, but does not limit the specific type of base station.

[0152] In the embodiments of this application, the term "and / or" describes the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following associated objects have an "or" relationship.

[0153] In the embodiments of this application, the term "multiple" refers to two or more, and other quantifiers are similar.

[0154] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0155] The technical solutions provided in this application can be applied to a variety of systems. For example, applicable systems may include Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Long Term Evolution Advanced (LTE-A) systems, Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) systems, 5G New Radio (NR) systems and their evolved communication systems, and 6G (sixth generation mobile communication technology) systems. These systems may include terminal equipment and network equipment. The systems may also include a core network component, such as the Evolved Packet Core (EPC) and the 5G Core Network (5GC).

[0156] The terminal devices involved in the embodiments of this application can be devices that provide voice and / or data connectivity to users, handheld devices with wireless connectivity, or other processing devices connected to a wireless modem. The names of the terminal devices may differ in different systems; for example, in a 5G system, a terminal device can be called User Equipment (UE). Wireless terminal devices can communicate with one or more core networks (CNs) via a Radio Access Network (RAN). Wireless terminal devices can be mobile terminal devices, such as mobile phones (or "cellular" phones) and computers with mobile terminal devices, for example, portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile devices that exchange voice and / or data with the RAN. Examples include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). Wireless terminal equipment can also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, remote terminal, access terminal, user terminal, user agent, or user device, but is not limited to these terms in the embodiments of this application.

[0157] The network device involved in this application embodiment can be a base station, which may include multiple cells providing services to terminals. Depending on the specific application, a base station may also be called an access point, or a device in an access network that communicates with a wireless terminal device through one or more sectors on the air interface, or other names. The network device can be used to exchange received air frames with Internet Protocol (IP) packets, acting as a router between the wireless terminal device and the rest of the access network, where the rest of the access network may include an Internet Protocol (IP) communication network. The network device can also coordinate the attribute management of the air interface. For example, the network equipment involved in the embodiments of this application can be a base transceiver station (BTS) in a Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA), a NodeB in a Wide-band Code Division Multiple Access (WCDMA) system, an evolved Node B (eNB or e-NodeB) in a long term evolution (LTE) system, a 5G base station (gNB) in a next generation system, a Home evolved Node B (HeNB), a relay node, a femto, a pico, etc., and is not limited in the embodiments of this application. In some network structures, the network equipment may include centralized unit (CU) nodes and distributed unit (DU) nodes, and the centralized unit and distributed unit may be geographically separated.

[0158] Network devices and terminal devices can each use one or more antennas for multiple-input multiple-output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multiple-user MIMO (MU-MIMO). Depending on the configuration and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO, and can also be diversity transmission, precoding transmission, or beamforming transmission, etc.

[0159] In order to achieve QoS processing for AIoT services, this application embodiment adds a new network element in the core network, such as the AIoT Function (AIoTF) network element, which is responsible for AIoT service management and forwarding of AIoT service messages.

[0160] like Figure 2 As shown in the figure, this application embodiment provides a method for processing the Quality of Service (QoS) of passive Internet of Things (AIoT) services, the method comprising:

[0161] Step 201: The terminal receives an AIoT service request message, the AIoT service request message including a first AIoT service type;

[0162] Step 202: The terminal determines the QoS information of the AIoT service corresponding to the first AIoT service type.

[0163] Optionally, when the terminal communicates with the AIoT device as a reader, this embodiment associates the AIoT service type with the QoS information of the AIoT service. The terminal can determine the QoS information of the corresponding AIoT service based on the AIoT service type carried in the AIoT service request message, thereby realizing QoS control of the AIoT service to meet the performance requirements of the AIoT service.

[0164] In at least one optional embodiment of this application, the QoS information of the AIoT service is QoS information defined to satisfy certain conditions, wherein the QoS information of the AIoT service includes at least one of the following:

[0165] Information such as end-to-end latency is required to execute an AIoT service.

[0166] The communication range between the terminal and the AIoT device;

[0167] The number of AIoT devices performing AIoT services, such as Device number.

[0168] Here, end-to-end latency is the time required to execute one AIoT service. Taking the Inventory service as an example, end-to-end latency is from the time the Application Function (AF) sends the Inventory request until the AF receives the Inventory response from the AIoT device.

[0169] Communication range refers to the communication distance between the terminal and the AIoT device.

[0170] Device number refers to the number of AIoT devices performing AIoT services. For example, Device number can be defined as the expected number of AIoT devices performing AIoT services.

[0171] As an optional embodiment, the first AIoT service type described above is used to indicate service operations performed on AIoT devices, and the first AIoT service type includes at least one of the following:

[0172] Inventory operations;

[0173] Command-based operations;

[0174] Sensor data collection services;

[0175] Tracking business;

[0176] Actuator control services.

[0177] For example, the Inventory business operation requests the AIoT device to report its device ID, while the command business operation can read relevant data from the AIoT device or write relevant data to the AIoT device.

[0178] As an optional embodiment, the terminal receives an AIoT service request message, including:

[0179] The terminal receives an AIoT service request message sent by the target network element.

[0180] For example, the target network element is the Access and Mobility Management Function (AMF) network element registered by the terminal.

[0181] As another optional embodiment, the method further includes:

[0182] The terminal executes the AIoT service based on the QoS information of the AIoT service.

[0183] To support QoS control for AIoT services, this application provides three methods for obtaining QoS information of the AIoT service corresponding to the AIoT service type:

[0184] Method 1: The AIoT service request message also includes: QoS information of the AIoT service corresponding to the first AIoT service type.

[0185] In other words, the AIoT service request message directly carries the first AIoT service type and the QoS information of the AIoT service corresponding to the first AIoT service type; the terminal can directly determine the service type of the AIoT service and the QoS information for executing the AIoT service based on the received AIoT service request message.

[0186] Method 2: The terminal obtains one or more AIoT service types and the QoS information of the AIoT services corresponding to each different AIoT service type through the registration process. The terminal determines the QoS information for executing the AIoT service based on the above information and the first AIoT service type carried in the service request message.

[0187] Method 3: The terminal obtains one or more AIoT service types and the QoS information of the AIoT services corresponding to each different AIoT service type through the AIoT session establishment process. The terminal determines the QoS information for executing the AIoT service based on the above information and the first AIoT service type carried in the service request message.

[0188] Accordingly, the method further includes:

[0189] The terminal acquires one or more AIoT service types and the QoS information of the AIoT services corresponding to each different AIoT service type;

[0190] Optionally, step 202 includes:

[0191] The terminal determines the QoS information of the AIoT service corresponding to the first AIoT service type based on the QoS information of the AIoT service corresponding to each different AIoT service type.

[0192] In other words, before the terminal receives the AIoT service request message, the terminal first obtains one or more AIoT service types and the QoS information of the AIoT services corresponding to each AIoT service type. Then, after the terminal receives the AIoT service request message, it determines the QoS information of the AIoT service corresponding to the first AIoT service type based on the first AIoT service type carried in the AIoT service request message and "one or more AIoT service types and the QoS information of the AIoT services corresponding to each AIoT service type".

[0193] Specifically, the terminal acquires one or more AIoT service types and the QoS information of the AIoT services corresponding to each different AIoT service type, including:

[0194] The terminal obtains one or more AIoT service types and the QoS information of the AIoT services corresponding to each different AIoT service type through the registration process;

[0195] or,

[0196] The terminal obtains one or more AIoT service types and the QoS information of the AIoT services corresponding to each different AIoT service type through the AIoT session establishment process.

[0197] As an optional embodiment, the terminal obtains one or more AIoT service types and the QoS information of the AIoT services corresponding to each different AIoT service type through the registration process, including:

[0198] The terminal sends a registration request message to the target network element;

[0199] The terminal receives a registration acceptance message sent by the target network element. The registration acceptance message includes the type of AIoT service that the terminal is authorized to execute and the QoS information of the AIoT service corresponding to each type of AIoT service.

[0200] Optionally, the registration request message includes the AIoT service types supported by the terminal.

[0201] Optionally, the method further includes: the terminal determining that it is capable of communicating with AIoT devices; wherein,

[0202] Wherein, the terminal is determined to be able to communicate with AIoT devices, including:

[0203] The terminal sends a registration request message carrying first indication information to the target network element, wherein the first indication information is used to indicate that the terminal supports the ability to communicate with AIoT devices;

[0204] The terminal receives a registration acceptance message carrying second indication information sent by the target network element. The second indication information is used to indicate that the terminal is allowed to communicate with the AIoT device.

[0205] For example, the target network element is the Access and Mobility Management Function (AMF) network element.

[0206] As another optional embodiment, the terminal obtains one or more AIoT service types and the QoS information of the AIoT services corresponding to each different AIoT service type through the AIoT session establishment process, including:

[0207] The terminal sends an AIoT session establishment request message to the target network element;

[0208] The terminal receives an AIoT session establishment response message sent by the target network element. The AIoT session establishment response message includes the type of AIoT service authorized by the terminal and the QoS information of the AIoT service corresponding to each AIoT service type.

[0209] Optionally, the AIoT session establishment request message includes the AIoT service types supported by the terminal.

[0210] Optionally, before the AIoT session establishment process begins, the method further includes:

[0211] The terminal is determined to be capable of communicating with AIoT devices; wherein...

[0212] Wherein, the terminal is determined to be able to communicate with AIoT devices, including:

[0213] The terminal sends a registration request message carrying first indication information to the target network element, wherein the first indication information is used to indicate that the terminal supports the ability to communicate with AIoT devices;

[0214] The terminal receives a registration acceptance message carrying second indication information sent by the target network element. The second indication information is used to indicate that the terminal is allowed to communicate with the AIoT device.

[0215] Optionally, the target network element is an AIoTF network element.

[0216] In summary, this application embodiment associates AIoT service types with AIoT service QoS information. The terminal can determine the corresponding AIoT service QoS information based on the AIoT service type carried in the AIoT service request message, thereby achieving QoS control of AIoT services to meet the performance requirements of AIoT services.

[0217] like Figure 3 As shown in the embodiments of this application, a QoS processing method for AIoT services is also provided, the method comprising:

[0218] Step 301: The target network element sends an AIoT service request message to the terminal. The AIoT service request message includes a first AIoT service type. The AIoT service request message is used to instruct the terminal to determine the QoS information of the AIoT service corresponding to the first AIoT service type.

[0219] Optionally, when the terminal communicates with the AIoT device as a reader, this embodiment associates the AIoT service type with the QoS information of the AIoT service. The terminal can determine the QoS information of the corresponding AIoT service based on the AIoT service type carried in the AIoT service request message, thereby realizing QoS control of the AIoT service to meet the performance requirements of the AIoT service.

[0220] For example, the target network element is the Access and Mobility Management Function (AMF) network element for terminal registration.

[0221] In at least one optional embodiment of this application, the QoS information of the AIoT service is QoS information defined to satisfy certain conditions, wherein the QoS information of the AIoT service includes at least one of the following:

[0222] Information such as end-to-end latency is required to execute an AIoT service.

[0223] The communication range between the terminal and the AIoT device;

[0224] The number of AIoT devices performing AIoT services, such as Device number.

[0225] Here, end-to-end latency is the time required to execute one AIoT service. Taking the Inventory service as an example, end-to-end latency is from the time the Application Function (AF) sends the Inventory request until the AF receives the Inventory response from the AIoT device.

[0226] Communication range refers to the communication distance between the terminal and the AIoT device.

[0227] Device number refers to the number of AIoT devices performing AIoT services. For example, Device number can be defined as the expected number of AIoT devices performing AIoT services.

[0228] As an optional embodiment, the first AIoT service type described above is used to indicate service operations performed on AIoT devices, and the first AIoT service type includes at least one of the following:

[0229] Inventory operations;

[0230] Command-based operations;

[0231] Sensor data collection services;

[0232] Tracking business;

[0233] Actuator control services.

[0234] For example, the Inventory business operation requests the AIoT device to report its device ID, while the command business operation can read relevant data from the AIoT device or write relevant data to the AIoT device.

[0235] To support QoS control for AIoT services, this application provides three methods for providing QoS information for AIoT services corresponding to the aforementioned AIoT service types:

[0236] In Method 1, the AIoT service request message further includes: QoS information of the AIoT service corresponding to the first AIoT service type.

[0237] In other words, the AIoT service request message directly carries the first AIoT service type and the QoS information of the AIoT service corresponding to the first AIoT service type; the terminal can directly determine the service type of the AIoT service and the QoS information for executing the AIoT service based on the received AIoT service request message.

[0238] Method 2: The target network element sends one or more AIoT service types and the QoS information of the AIoT services corresponding to each different AIoT service type to the terminal through the terminal registration process. The terminal determines the QoS information for executing the AIoT service based on the above information and the first AIoT service type carried in the service request message.

[0239] Method 3: The target network element sends one or more AIoT service types and the QoS information of the AIoT services corresponding to each different AIoT service type to the terminal through the AIoT session establishment process. The terminal determines the QoS information for executing the AIoT service based on the above information and the first AIoT service type carried in the service request message.

[0240] Accordingly, the method further includes:

[0241] The target network element sends one or more AIoT service types and the QoS information of the AIoT services corresponding to each different AIoT service type to the terminal. Optionally, the terminal determines the QoS information of the AIoT service corresponding to the first AIoT service type based on the QoS information of the AIoT services corresponding to each of the AIoT service types.

[0242] In other words, before the terminal receives the AIoT service request message, the terminal first obtains one or more AIoT service types and the QoS information of the AIoT services corresponding to each AIoT service type. Then, after the terminal receives the AIoT service request message, it determines the QoS information of the AIoT service corresponding to the first AIoT service type based on the first AIoT service type carried in the AIoT service request message and "one or more AIoT service types and the QoS information of the AIoT services corresponding to each AIoT service type".

[0243] Specifically, the target network element sends one or more AIoT service types and QoS information of the AIoT services corresponding to each different AIoT service type to the terminal, including:

[0244] The target network element sends one or more AIoT service types and QoS information of the AIoT services corresponding to each different AIoT service type to the terminal through the terminal registration process.

[0245] or,

[0246] The target network element sends one or more AIoT service types and the QoS information of the AIoT services corresponding to each different AIoT service type to the terminal through the AIoT session establishment process.

[0247] As an optional embodiment, the target network element sends one or more AIoT service types and QoS information of the AIoT services corresponding to each different AIoT service type to the terminal through a registration process, including:

[0248] The target network element receives the registration request message sent by the terminal;

[0249] The target network element sends a registration acceptance message to the terminal. The registration acceptance message includes the type of AIoT service that the terminal is authorized to execute and the QoS information of the AIoT service corresponding to each AIoT service type.

[0250] Optionally, the registration request message includes the AIoT service types supported by the terminal.

[0251] Optionally, the method further includes: the target network element instructing the terminal to communicate with the AIoT device; wherein, the target network element instructing the terminal to communicate with the AIoT device includes:

[0252] The target network element receives a registration request message sent by the terminal, which carries first indication information. The first indication information is used to indicate that the terminal supports the ability to communicate with AIoT devices.

[0253] The target network element sends a registration acceptance message to the terminal carrying second indication information, which is used to indicate that the terminal is allowed to communicate with the AIoT device.

[0254] For example, the target network element is the Access and Mobility Management Function (AMF) network element.

[0255] As another optional embodiment, the target network element sends one or more AIoT service types and QoS information of the AIoT services corresponding to each different AIoT service type to the terminal through the AIoT session establishment process, including:

[0256] The target network element receives the AIoT session establishment request message sent by the terminal;

[0257] The target network element sends an AIoT session establishment response message to the terminal. The AIoT session establishment response message includes the type of AIoT service that the terminal is authorized to execute and the QoS information of the AIoT service corresponding to each AIoT service type.

[0258] Optionally, the AIoT session establishment request message includes the AIoT service types supported by the terminal.

[0259] Optionally, the method further includes: the target network element instructing the terminal to communicate with the AIoT device; wherein, the target network element instructing the terminal to communicate with the AIoT device includes:

[0260] The target network element receives a registration request message sent by the terminal, which carries first indication information. The first indication information is used to indicate that the terminal supports the ability to communicate with AIoT devices.

[0261] The target network element sends a registration acceptance message to the terminal carrying second indication information, which is used to indicate that the terminal is allowed to communicate with the AIoT device.

[0262] Optionally, the target network element is an AIoTF network element.

[0263] In summary, this application embodiment associates AIoT service types with AIoT service QoS information. The terminal can determine the corresponding AIoT service QoS information based on the AIoT service type carried in the AIoT service request message, thereby achieving QoS control of AIoT services to meet the performance requirements of AIoT services.

[0264] To more clearly describe the QoS processing method for AIoT services provided in the embodiments of this application, the following description is provided in conjunction with three examples and accompanying drawings.

[0265] Example 1, such as Figure 4 As shown:

[0266] Step 41: The terminal initiates the registration process. In the registration request message, the terminal indicates its ability to communicate with AIoT devices. Optionally, the terminal may also indicate the types of AIoT services it supports.

[0267] Step 42: The AMF determines that the terminal can communicate with AIoT devices based on the terminal's subscription information. The AMF sends a Create UE Context Request message to the AIoTF. This message contains the terminal identifier, indication information that the terminal supports communication with AIoT devices, and the types of AIoT services supported by the terminal.

[0268] Step 43: AIoTF obtains the terminal's subscription information from UDM (Unified Data Management) or UDR (Unified Data Repository), including the AIoT service type subscribed to by the UE and the corresponding AIoT service QoS information. The AIoT service type and QoS information in the terminal's subscription data can be provided to the UDR by AF (Application Function).

[0269] Step 44: AIoTF sends a Create UE Context Response message to AMF, which contains the type of AIoT service authorized for the UE and the corresponding AIoT service QoS information.

[0270] Step 45: In the registration acceptance message, AMF indicates to the terminal that AIoT device communication is permitted. This message also includes the type of AIoT service authorized by the terminal and the corresponding AIoT service QoS information.

[0271] Steps 46a-46b: The AF sends an inventory request message to the AIoTF via the Network Exposure Function (NEF). The Inventory service is a type of AIoT service that requests AIoT devices to report their device IDs.

[0272] Step 46c: AIoTF selects a terminal that can perform inventory services and sends an inventory request message to the AMF registered with the terminal. This message contains the terminal identifier.

[0273] In step 46d, the AMF sends an inventory request message (non-access layer NAS message) to the terminal. This message contains indication information of the AIoT service type, which indicates that the service type to be operated is Inventory.

[0274] Step 47: The terminal determines the QoS information for executing the AIoT service (Inventory) based on the AIoT service type (Inventory) in step 46d and the AIoT service type and corresponding AIoT service QoS information in step 45. The terminal can determine the execution time of this Inventory operation based on the end-to-end latency in the QoS information; for example, when inventorying multiple AIoT devices, the time for the last AIoT device to return its Device ID cannot exceed the end-to-end latency. The terminal can determine the transmit power when inventorying AIoT devices based on the communication range. The terminal can determine the inventory time for each AIoT device based on the Device number.

[0275] Step 48a: The terminal sends an inventory response message (NAS message) to the AMF, which contains the Device ID of the AIoT device.

[0276] Steps 48b-48d: AMF sends the Device ID to AF via AIoTF and NEF.

[0277] Example 2, such as Figure 5 As shown:

[0278] Step 51: The terminal initiates the registration process, and in the registration request message, the terminal indicates its ability to communicate with AIoT devices.

[0279] Step 52: The AMF obtains the terminal's subscription information from the UDM. Based on the terminal's subscription information, the AMF determines that the terminal can communicate with AIoT devices.

[0280] Step 53: In the registration acceptance message, AMF instructs the terminal to allow AIoT device communication.

[0281] Step 54: The terminal sends an AIoT session establishment request message (via AMF) to the AIoTF, in which the terminal indicates the types of AIoT services it supports.

[0282] Step 55: AIoTF obtains the terminal's subscription information from UDM, including the type of AIoT service the terminal has subscribed to and the corresponding AIoT service QoS information.

[0283] Step 56: The AIoTF determines the authorized AIoT service type based on the AIoT service types supported by the terminal and the AIoT service types subscribed to by the terminal. The AIoTF sends an AIoT session establishment response message to the terminal (via the AMF), which contains the authorized AIoT service type and the corresponding AIoT service QoS information.

[0284] In steps 57a-57b, the AF sends an inventory request message to the AIoTF via the NEF. The inventory service is a type of AIoT service that requests AIoT devices to report their Device IDs.

[0285] Step 57c: AIoTF sends an Inventory request message to the terminal through AMF. This message contains indication information of the AIoT service type, which indicates that the service type to be operated is Inventory.

[0286] Step 58: The terminal determines the QoS information for executing the AIoT service (Inventory) based on the AIoT service type (Inventory) in step 57c and the AIoT service type and corresponding AIoT service QoS information in step 56. The terminal can determine the execution time of this Inventory operation based on the end-to-end latency in the QoS information; for example, when inventorying multiple AIoT devices, the time for the last AIoT device to return its Device ID cannot exceed the end-to-end latency. The terminal can determine the transmission power when inventorying AIoT devices based on the communication range. The terminal can determine the inventory time for each AIoT device based on the Device number.

[0287] Step 59a: The terminal sends an inventory response message to the AIoTF via the AMF, which contains the Device ID of the AIoT device.

[0288] In steps 59b-59c, AIoTF sends the Device ID to AF via NEF.

[0289] Example 3, such as Figure 6 As shown:

[0290] Step 61: The terminal initiates the registration process, and in the registration request message, the terminal indicates its ability to communicate with AIoT devices.

[0291] Step 62: The AMF obtains the terminal's subscription information from the UDM. Based on the terminal's subscription information, the AMF determines that the terminal can communicate with AIoT devices.

[0292] Step 63: In the registration acceptance message, AMF instructs the terminal to allow AIoT device communication.

[0293] Step 64: AF sends an inventory request message to NEF, which contains the AIoT service type and the corresponding AIoT service QoS information.

[0294] Step 65: NEF performs an authorization check on the inventory request message sent by AF, including determining whether the AIoT service is allowed to use the corresponding AIoT service QoS information based on the subscription information.

[0295] Step 66a: NEF sends an inventory request message to AIoTF, which contains the AIoT service type and the corresponding AIoT service QoS information.

[0296] Step 66b: AIoTF selects a terminal that can perform the inventory service. AIoTF sends an inventory request message to the AMF registered with the terminal. This message contains the terminal identifier, as well as the AIoT service type and the corresponding AIoT service QoS information.

[0297] Step 66c: AMF sends an inventory request message (NAS message) to the terminal. This message contains AIoT service type indication information and corresponding AIoT service QoS information.

[0298] Step 67: The terminal performs an inventory operation based on the AIoT service type (Inventory) from step 66c and the corresponding AIoT service QoS information. For example, the terminal can determine the time to perform this inventory operation based on the end-to-end latency in the QoS information; for instance, when inventorying multiple AIoT devices, the time for the last AIoT device to return its Device ID cannot exceed the end-to-end latency. The terminal can determine the transmit power when inventorying AIoT devices based on the communication range. The terminal can determine the inventory time for each AIoT device based on the Device number.

[0299] In steps 68a-68d, the terminal sends an inventory response message to the AIoTF via the AMF, which contains the Device ID of the AIoT device. The AIoTF then sends the Device ID to the AF via the NEF.

[0300] This application embodiment associates AIoT service types with AIoT service QoS information. The terminal can determine the corresponding AIoT service QoS information based on the AIoT service type carried in the AIoT service request message, thereby realizing QoS control of AIoT services to meet the performance requirements of AIoT services.

[0301] like Figure 7 As shown in the illustration, this application also provides a terminal, including a memory 720, a transceiver 710, and a processor 700.

[0302] The memory 720 is used to store computer programs; the transceiver 710 is used to send and receive data under the control of the processor 700; the processor 700 is used to read the computer program in the memory 720 and perform the following operations:

[0303] Receive an AIoT service request message, wherein the AIoT service request message includes a first AIoT service type;

[0304] Determine the QoS information of the AIoT service corresponding to the first AIoT service type.

[0305] As an optional embodiment, the QoS information of the AIoT service includes at least one of the following:

[0306] Information on the time required to execute one AIoT service;

[0307] The communication distance between the terminal and AIoT devices;

[0308] The number of AIoT devices performing AIoT services.

[0309] As an optional embodiment, the first AIoT service type includes at least one of the following:

[0310] Inventory of business operations;

[0311] Command services;

[0312] Sensor data acquisition services;

[0313] Track business operations;

[0314] Actuator control services.

[0315] As an optional embodiment, the AIoT service request message further includes: QoS information of the AIoT service corresponding to the first AIoT service type;

[0316] The processor is also configured to read the computer program in the memory and perform the following operations:

[0317] Based on the AIoT service request message, determine the QoS information of the AIoT service corresponding to the first AIoT service type.

[0318] As an optional embodiment, the processor is also configured to read a computer program from the memory and perform the following operations:

[0319] Obtain one or more AIoT service types and the QoS information of the AIoT services corresponding to each different AIoT service type;

[0320] Based on the QoS information of the AIoT services corresponding to each different AIoT service type, the QoS information of the AIoT service corresponding to the first AIoT service type is determined.

[0321] As an optional embodiment, the processor is also configured to read a computer program from the memory and perform the following operations:

[0322] The registration process obtains one or more AIoT service types and the QoS information of the AIoT services corresponding to each different AIoT service type.

[0323] or,

[0324] The AIoT session establishment process obtains one or more AIoT service types and the QoS information of the AIoT services corresponding to each different AIoT service type.

[0325] As an optional embodiment, the processor is also configured to read a computer program from the memory and perform the following operations:

[0326] Send a registration request message to the target network element;

[0327] The system receives a registration acceptance message sent by the target network element. The registration acceptance message includes the type of AIoT service executed by the authorized terminal and the QoS information of the AIoT service corresponding to each of the AIoT service types.

[0328] As an optional embodiment, the registration request message includes the AIoT service types supported by the terminal.

[0329] As an optional embodiment, the processor is also configured to read a computer program from the memory and perform the following operations:

[0330] Send an AIoT session establishment request message to the target network element;

[0331] The system receives an AIoT session establishment response message sent by the target network element. The AIoT session establishment response message includes the type of AIoT service executed by the authorized terminal and the QoS information of the AIoT service corresponding to each of the AIoT service types.

[0332] As an optional embodiment, the AIoT session establishment request message includes the AIoT service types supported by the terminal.

[0333] As an optional embodiment, the processor is also configured to read a computer program from the memory and perform the following operations:

[0334] Determining the ability to communicate with AIoT devices; wherein determining the ability to communicate with AIoT devices includes:

[0335] A registration request message carrying first indication information is sent to the target network element, wherein the first indication information is used to indicate that the terminal supports the ability to communicate with AIoT devices;

[0336] The target network element sends a registration acceptance message carrying second indication information, which is used to indicate that the terminal is allowed to communicate with the AIoT device.

[0337] As an optional embodiment, the processor is also configured to read a computer program from the memory and perform the following operations:

[0338] The AIoT service is executed based on the QoS information of the AIoT service.

[0339] Among them, Figure 7 In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 700 and memory represented by memory 720 together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 710 can be multiple components, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, etc. For different user equipment, the user interface 730 can also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc.

[0340] The processor 700 is responsible for managing the bus architecture and general processing, while the memory 720 can store the data used by the processor 700 during operation.

[0341] Optionally, the processor 700 can be a CPU (Central Processing Unit), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), or CPLD (Complex Programmable Logic Device), and the processor can also adopt a multi-core architecture.

[0342] The processor executes any of the methods described in the embodiments of this application according to the obtained executable instructions by calling a computer program stored in memory. The processor and memory may also be physically separated.

[0343] This application embodiment associates AIoT service types with AIoT service QoS information. The terminal can determine the corresponding AIoT service QoS information based on the AIoT service type carried in the AIoT service request message, thereby realizing QoS control of AIoT services to meet the performance requirements of AIoT services.

[0344] It should be noted that the terminal provided in this application embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0345] like Figure 8 As shown in the figure, this application embodiment also provides a target network element, including a memory 820, a transceiver 810, and a processor 800:

[0346] The memory 820 is used to store computer programs; the transceiver 810 is used to send and receive data under the control of the processor 800; the processor 800 is used to read the computer program in the memory 820 and perform the following operations:

[0347] Send an AIoT service request message to the terminal, the AIoT service request message including a first AIoT service type; the AIoT service request message is used to instruct the terminal to determine the QoS information of the AIoT service corresponding to the first AIoT service type.

[0348] As an optional embodiment, the AIoT service request message may further include: QoS information of the AIoT service corresponding to the first AIoT service type.

[0349] As an optional embodiment, the processor is also configured to read a computer program from the memory and perform the following operations:

[0350] Send one or more AIoT service types and the QoS information of the AIoT services corresponding to each different AIoT service type to the terminal.

[0351] As an optional embodiment, the processor is also configured to read a computer program from the memory and perform the following operations:

[0352] The registration process sends one or more AIoT service types and the QoS information of the AIoT services corresponding to each different AIoT service type to the terminal.

[0353] or,

[0354] During the AIoT session establishment process, one or more AIoT service types and the QoS information of the corresponding AIoT services are sent to the terminal.

[0355] As an optional embodiment, the processor is also configured to read a computer program from the memory and perform the following operations:

[0356] Receive registration request messages sent by the terminal;

[0357] A registration acceptance message is sent to the terminal, which includes the type of AIoT service authorized for the terminal to execute and the QoS information of the AIoT service corresponding to each AIoT service type.

[0358] As an optional embodiment, the registration request message includes the AIoT service types supported by the terminal.

[0359] As an optional embodiment, the processor is also configured to read a computer program from the memory and perform the following operations:

[0360] Receive the AIoT session establishment request message sent by the terminal;

[0361] Send an AIoT session establishment response message to the terminal. The AIoT session establishment response message includes the type of AIoT service authorized to be executed by the terminal and the QoS information of the AIoT service corresponding to each AIoT service type.

[0362] As an optional embodiment, the AIoT session establishment request message includes the AIoT service types supported by the terminal.

[0363] As an optional embodiment, the processor is also configured to read a computer program from the memory and perform the following operations:

[0364] Instructing the terminal to communicate with AIoT devices; wherein, instructing the terminal to communicate with AIoT devices includes:

[0365] The terminal receives a registration request message carrying first indication information, which indicates that the terminal supports the ability to communicate with AIoT devices.

[0366] A registration acceptance message carrying second indication information is sent to the terminal, the second indication information being used to indicate that the terminal is allowed to communicate with the AIoT device.

[0367] Among them, Figure 8In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 800) and memory (memory 820). The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 810 can be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, etc. The processor 800 is responsible for managing the bus architecture and general processing, and the memory 820 can store data used by the processor 800 during operation.

[0368] The processor 800 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0369] This application embodiment associates AIoT service types with AIoT service QoS information. The terminal can determine the corresponding AIoT service QoS information based on the AIoT service type carried in the AIoT service request message, thereby realizing QoS control of AIoT services to meet the performance requirements of AIoT services.

[0370] It should be noted that the target network element provided in this application embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0371] like Figure 9 As shown in the illustration, this application also provides a QoS processing device for AIoT services, applied to a terminal, the device comprising:

[0372] The first receiving unit 901 is configured to receive an AIoT service request message, wherein the AIoT service request message includes a first AIoT service type;

[0373] The first determining unit 902 is used to determine the QoS information of the AIoT service corresponding to the first AIoT service type.

[0374] As an optional embodiment, the QoS information of the AIoT service includes at least one of the following:

[0375] Information on the time required to execute one AIoT service;

[0376] The communication distance between the terminal and AIoT devices;

[0377] The number of AIoT devices performing AIoT services.

[0378] As an optional embodiment, the first AIoT service type includes at least one of the following:

[0379] Inventory of business operations;

[0380] Command services;

[0381] Sensor data acquisition services;

[0382] Track business operations;

[0383] Actuator control services.

[0384] As an optional embodiment, the AIoT service request message further includes: QoS information of the AIoT service corresponding to the first AIoT service type;

[0385] The first determining unit includes:

[0386] The first determining subunit is used to determine the QoS information of the AIoT service corresponding to the first AIoT service type based on the AIoT service request message.

[0387] As an optional embodiment, the apparatus further includes:

[0388] The acquisition unit is used to acquire one or more AIoT service types and the QoS information of the AIoT services corresponding to each different AIoT service type;

[0389] The first determining unit includes:

[0390] The second determining subunit is used to determine the QoS information of the AIoT service corresponding to the first AIoT service type based on the QoS information of the AIoT service corresponding to each different AIoT service type.

[0391] As an optional embodiment, the acquisition unit includes:

[0392] The first acquisition subunit is used to acquire one or more AIoT service types and the QoS information of the AIoT services corresponding to each different AIoT service type through the registration process;

[0393] or,

[0394] The second acquisition subunit is used to acquire one or more AIoT service types and the QoS information of the AIoT services corresponding to each different AIoT service type through the AIoT session establishment process.

[0395] As an optional embodiment, the first acquisition subunit is further configured to:

[0396] Send a registration request message to the target network element;

[0397] The system receives a registration acceptance message sent by the target network element. The registration acceptance message includes the type of AIoT service executed by the authorized terminal and the QoS information of the AIoT service corresponding to each AIoT service type.

[0398] As an optional embodiment, the registration request message includes the AIoT service types supported by the terminal.

[0399] As an optional embodiment, the second acquisition subunit is further configured to:

[0400] Send an AIoT session establishment request message to the target network element;

[0401] The system receives an AIoT session establishment response message sent by the target network element. The AIoT session establishment response message includes the type of AIoT service executed by the authorized terminal and the QoS information of the AIoT service corresponding to each AIoT service type.

[0402] As an optional embodiment, the AIoT session establishment request message includes the AIoT service types supported by the terminal.

[0403] As an optional embodiment, the apparatus further includes:

[0404] The second determining unit is configured to determine whether communication with an AIoT device is possible; wherein determining whether communication with an AIoT device is possible includes:

[0405] A registration request message carrying first indication information is sent to the target network element, wherein the first indication information is used to indicate that the terminal supports the ability to communicate with AIoT devices;

[0406] The target network element sends a registration acceptance message carrying second indication information, which is used to indicate that the terminal is allowed to communicate with the AIoT device.

[0407] As an optional embodiment, the apparatus further includes:

[0408] An execution unit is used to execute the AIoT service based on the QoS information of the AIoT service.

[0409] This application embodiment associates AIoT service types with AIoT service QoS information. The terminal can determine the corresponding AIoT service QoS information based on the AIoT service type carried in the AIoT service request message, thereby realizing QoS control of AIoT services to meet the performance requirements of AIoT services.

[0410] It should be noted that the apparatus provided in this application embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0411] like Figure 10 As shown in the illustration, this application also provides a QoS processing device for AIoT services, applied to a target network element, the device comprising:

[0412] The first sending unit 1001 is used to send an AIoT service request message to the terminal. The AIoT service request message includes a first AIoT service type. The AIoT service request message is used to instruct the terminal to determine the QoS information of the AIoT service corresponding to the first AIoT service type.

[0413] As an optional embodiment, the QoS information of the AIoT service includes at least one of the following:

[0414] Information on the time required to execute one AIoT service;

[0415] The communication distance between the terminal and AIoT devices;

[0416] The number of AIoT devices performing AIoT services.

[0417] As an optional embodiment, the first AIoT service type includes at least one of the following:

[0418] Inventory of business operations;

[0419] Command services;

[0420] Sensor data acquisition services;

[0421] Track business operations;

[0422] Actuator control services.

[0423] As an optional embodiment, the AIoT service request message may further include: QoS information of the AIoT service corresponding to the first AIoT service type.

[0424] As an optional embodiment, the apparatus further includes:

[0425] The second sending unit is used to send one or more AIoT service types and the QoS information of the AIoT services corresponding to each different AIoT service type to the terminal.

[0426] As an optional embodiment, the second transmitting unit includes:

[0427] The first transmitting subunit is used to transmit one or more AIoT service types and the QoS information of the AIoT services corresponding to each different AIoT service type to the terminal through the terminal registration process.

[0428] or,

[0429] The second transmitting subunit is used to send one or more AIoT service types and QoS information of the AIoT services corresponding to each different AIoT service type to the terminal through the AIoT session establishment process.

[0430] As an optional embodiment, the first transmitting subunit is further configured to:

[0431] Receive registration request messages sent by the terminal;

[0432] A registration acceptance message is sent to the terminal, which includes the type of AIoT service authorized for the terminal to execute and the QoS information of the AIoT service corresponding to each AIoT service type.

[0433] As an optional embodiment, the registration request message includes the AIoT service types supported by the terminal.

[0434] As an optional embodiment, the second transmitting subunit is further configured to:

[0435] Receive the AIoT session establishment request message sent by the terminal;

[0436] Send an AIoT session establishment response message to the terminal. The AIoT session establishment response message includes the type of AIoT service authorized to be executed by the terminal and the QoS information of the AIoT service corresponding to each AIoT service type.

[0437] As an optional embodiment, the AIoT session establishment request message includes the AIoT service types supported by the terminal.

[0438] As an optional embodiment, the apparatus further includes:

[0439] An indication unit is configured to indicate that the terminal is capable of communicating with an AIoT device; wherein, indicating that the terminal is capable of communicating with an AIoT device includes:

[0440] The received registration request message sent by the terminal carries first indication information, wherein the first indication information is used to indicate that the terminal supports the ability to communicate with AIoT devices;

[0441] A registration acceptance message carrying second indication information is sent to the terminal, the second indication information being used to indicate that the terminal is allowed to communicate with the AIoT device.

[0442] This application embodiment associates AIoT service types with AIoT service QoS information. The terminal can determine the corresponding AIoT service QoS information based on the AIoT service type carried in the AIoT service request message, thereby realizing QoS control of AIoT services to meet the performance requirements of AIoT services.

[0443] It should be noted that the apparatus provided in this application embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0444] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

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

[0446] This application also provides a processor-readable storage medium storing a computer program. The computer program is used to cause the processor to execute the various processes described in the above-described embodiments of the QoS processing method for AIoT services, achieving the same technical effects. To avoid repetition, these processes will not be repeated here. The processor-readable storage medium can be any available medium or data storage device accessible to the processor, including but not limited to magnetic storage (e.g., floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND flash), solid-state drives (SSDs)).

[0447] This application also provides a computer program product, including computer instructions. When the computer instructions are executed by a processor, they implement the various processes in the QoS processing method embodiment of AIoT services as described above, and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0448] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0449] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0450] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means, which are implemented in a processFigure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0451] These processors can execute instructions that can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0452] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A method for quality of service (QoS) processing of a passive Internet of Things (AIoT) service, the method comprising: The method comprises: The terminal receives an AIoT service request message, wherein the AIoT service request message comprises a first AIoT service type; The terminal determines the QoS information of the AIoT service corresponding to the first AIoT service type.

2. The method of claim 1, wherein, The QoS information of the AIoT service comprises at least one of the following information: Time information required for executing an AIoT service once; Communication distance between the terminal and an AIoT device; Number of AIoT devices for executing an AIoT service.

3. The method of claim 1, wherein, The first AIoT service type comprises at least one of the following: Inventory service; Command service; Sensor data collection service; Tracking service; Actuator control service.

4. The method according to any one of claims 1 to 3, characterized in that, The AIoT service request message further comprises the QoS information of the AIoT service corresponding to the first AIoT service type. The terminal determines the QoS information of the AIoT service corresponding to the first AIoT service type, comprising: The terminal determines the QoS information of the AIoT service corresponding to the first AIoT service type according to the AIoT service request message.

5. The method according to any one of claims 1 to 3, characterized in that, The method further comprises: The terminal acquires one or more AIoT service types and the QoS information of the AIoT service corresponding to each different AIoT service type; The terminal determines the QoS information of the AIoT service corresponding to the first AIoT service type, comprising: The terminal determines the QoS information of the AIoT service corresponding to the first AIoT service type according to the QoS information of the AIoT service corresponding to each different AIoT service type.

6. The method of claim 5, wherein, The terminal acquires one or more AIoT service types and the QoS information of the AIoT service corresponding to each different AIoT service type, comprising: The terminal acquires one or more AIoT service types and the QoS information of the AIoT service corresponding to each different AIoT service type through a registration process; Or, The terminal acquires one or more AIoT service types and the QoS information of the AIoT service corresponding to each different AIoT service type through an AIoT session establishment process.

7. The method of claim 6, wherein, The terminal acquires one or more AIoT service types and the QoS information of the AIoT service corresponding to each different AIoT service type through a registration process, comprising: The terminal sends a registration request message to a target network element; The terminal receives a registration acceptance message sent by the target network element, wherein the registration acceptance message comprises the AIoT service type authorized to be executed by the terminal and the QoS information of the AIoT service corresponding to each AIoT service type.

8. The method of claim 6, wherein, The terminal acquires one or more AIoT service types and the QoS information of the AIoT service corresponding to each different AIoT service type through an AIoT session establishment process, comprising: The terminal sends an AIoT session establishment request message to a target network element; The terminal receives an AIoT session establishment response message sent by the target network element, and the AIoT session establishment response message includes an AIoT service type authorized to be executed by the terminal and QoS information of an AIoT service corresponding to each AIoT service type.

9. The method of claim 6, wherein, The method further includes determining, by the terminal, that the terminal is capable of communicating with an AIoT device. The method further includes determining, by the terminal, that the terminal is capable of communicating with an AIoT device. The terminal sends a registration request message carrying first indication information to the target network element, and the first indication information is used to indicate that the terminal supports the capability of communicating with an AIoT device. The terminal receives a registration acceptance message carrying second indication information sent by the target network element, and the second indication information is used to indicate that the terminal is allowed to communicate with the AIoT device.

10. The method according to any one of claims 1 to 9, characterized in that, The method further includes: The terminal executes the AIoT service according to the QoS information of the AIoT service. 11.A method for QoS processing of AIoT traffic, the method comprising: The method includes: The target network element sends an AIoT service request message to the terminal, and the AIoT service request message includes a first AIoT service type; and the AIoT service request message is used to instruct the terminal to determine QoS information of an AIoT service corresponding to the first AIoT service type.

12. The method of claim 11, wherein, The AIoT service request message further includes the QoS information of the AIoT service corresponding to the first AIoT service type.

13. The method of claim 11, wherein, The method further includes: The target network element sends one or more AIoT service types and QoS information of an AIoT service corresponding to each different AIoT service type to the terminal.

14. A terminal, characterized by The method includes a memory, a transceiver, and a processor. The memory is used to store a computer program; the transceiver is used to transceive data under the control of the processor; and the processor is used to read the computer program in the memory and perform the following operations: The AIoT service request message includes a first AIoT service type. The processor is further used to read the computer program in the memory and perform the following operations:

15. The terminal according to claim 14, characterized by The AIoT service request message includes a first AIoT service type. The QoS information of the AIoT service includes at least one of the following information: Time information required for executing an AIoT service once; Communication distance between the terminal and an AIoT device; 16. The terminal according to claim 14, characterized by Number of AIoT devices for executing an AIoT service. The first AIoT service type includes at least one of the following: Inventory service; Command service; Sensor data collection service; Tracking service; 17. The terminal according to any of claims 14-16, characterized by Actuator control service. The AIoT service request message further includes the QoS information of the AIoT service corresponding to the first AIoT service type. The processor is further used to read the computer program in the memory and perform the following operations:

18. The terminal according to any of claims 14-16, characterized by According to the AIoT service request message, the QoS information of the AIoT service corresponding to the first AIoT service type is determined. The processor is further used to read the computer program in the memory and perform the following operations: One or more AIoT service types and QoS information of an AIoT service corresponding to each different AIoT service type are acquired. determine the QoS information of the AIoT service corresponding to the first AIoT service type according to the QoS information of the AIoT service corresponding to each different AIoT service type.

19. The terminal according to claim 18, characterized by The processor is further configured to read a computer program in the memory and perform the following operations: obtain one or more AIoT service types and the QoS information of the AIoT service corresponding to each different AIoT service type through a registration process; Or, obtain one or more AIoT service types and the QoS information of the AIoT service corresponding to each different AIoT service type through an AIoT session establishment process.

20. The terminal according to claim 19, characterized by The processor is further configured to read a computer program in the memory and perform the following operations: send a registration request message to a target network element; receive a registration acceptance message sent by the target network element, wherein the registration acceptance message includes the AIoT service types authorized to be executed by the terminal and the QoS information of the AIoT service corresponding to each AIoT service type.

21. The terminal according to claim 19, characterized by The processor is further configured to read a computer program in the memory and perform the following operations: send an AIoT session establishment request message to a target network element; receive an AIoT session establishment response message sent by the target network element, wherein the AIoT session establishment response message includes the AIoT service types authorized to be executed by the terminal and the QoS information of the AIoT service corresponding to each AIoT service type.

22. The terminal of claim 19, wherein, The processor is further configured to read a computer program in the memory and perform the following operations: determine that the terminal is capable of communicating with an AIoT device; The determination that the terminal is capable of communicating with the AIoT device includes: sending a registration request message carrying first indication information to a target network element, wherein the first indication information is used to indicate the capability of the terminal supporting communication with the AIoT device; receiving a registration acceptance message carrying second indication information sent by the target network element, wherein the second indication information is used to indicate that the terminal is allowed to communicate with the AIoT device.

23. The terminal according to any of claims 14-22, characterized by The processor is further configured to read a computer program in the memory and perform the following operations: perform the AIoT service according to the QoS information of the AIoT service.

24. A target network element, characterized by The apparatus includes a memory, a transceiver, and a processor: The memory is configured to store a computer program; the transceiver is configured to transceive data under the control of the processor; and the processor is configured to read a computer program in the memory and perform the following operations: send an AIoT service request message to a terminal, wherein the AIoT service request message includes a first AIoT service type; and the AIoT service request message is used to instruct the terminal to determine the QoS information of the AIoT service corresponding to the first AIoT service type. 25.A QoS processing apparatus for AIoT traffic, the apparatus comprising: The apparatus includes: a first receiving unit configured to receive an AIoT service request message, wherein the AIoT service request message includes a first AIoT service type; a first determining unit configured to determine the QoS information of the AIoT service corresponding to the first AIoT service type. 26.A QoS processing apparatus for AIoT traffic, the apparatus comprising: The apparatus includes: The first sending unit is configured to send an AIoT service request message to the terminal, wherein the AIoT service request message comprises a first AIoT service type; and the AIoT service request message is used to instruct the terminal to determine QoS information of an AIoT service corresponding to the first AIoT service type.

27. A processor-readable storage medium, comprising: The processor readable storage medium stores a program for causing the processor to execute the method in any one of claims 1 to 10, or the program for causing the processor to execute the method in any one of claims 11 to 13.

Images