Quality-of-service guarantee method and communication apparatus

Abstract

Disclosed in the present application are a quality-of-service guarantee method and a communication apparatus. The method comprises: a first network element receiving a first message, which comprises first information, or, the first network element receiving the first message and the first information; determining a first identifier and / or second information on the basis of the first information, wherein the first identifier is associated with the second information; and executing a traffic processing action on the first message on the basis of the second information, wherein the first information comprises one or more of the following: an identifier of an AF, a service type, a service object, the priority of the first message, the type of a terminal device, a first service time budget, a destination network address, and a network address of the terminal device, and the second information comprises one or more of the following: a priority corresponding to an Internet-of Things service, a resource type, a second service time budget, the size of an uplink data packet, and an uplink and / or downlink rate. The present application is conducive to guaranteeing the quality of service of the Internet of Things under conditions of scarce and limited resources on the network side.

Description

Method for guaranteeing quality of service and communication device

[0001] The present application claims priority to the Chinese patent application No. 202411391035.2, filed on September 30, 2024, and entitled "Method for guaranteeing quality of service and communication device", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] Embodiments of the present application relate to the field of communication, in particular to a method for guaranteeing quality of service and a communication device. BACKGROUND

[0003] In a communication system, in order to improve the sustainability and performance of communication and reduce the power consumption of wireless communication, an Ambient Internet of things (A-IoT) technology is introduced. The so-called A-IoT, also known as passive Internet of things, is a network communication technology based on passive terminals. Passive terminals are usually devices that do not need to be built-in with a battery and do not have an external power supply line for power supply. Such devices can obtain energy through other means to ensure their normal operation.

[0004] With the commercialization of A-IoT, more and more A-IoT devices are connected to the network, which increases the burden of network traffic processing. In the case of limited network resources, the quality of service of A-IoT cannot be effectively guaranteed at present. SUMMARY

[0005] Embodiments of the present application provide a method for guaranteeing quality of service and a communication device. Based on the method described in the present application, the quality of service of Internet of things can be effectively guaranteed in the case of limited network resources.

[0006] In a first aspect, the present application provides a method for guaranteeing quality of service, applied to a first network element, the method comprising: receiving a first message, the first message comprising first information; or receiving a first message and first information; determining a first identifier and / or second information based on the first information, the first identifier being associated with the second information; and then performing a traffic processing action on the first message based on the second information.

[0007] The first information comprises one or more of the following: an identifier of an application function (AF), a service type, a service object, a priority of the first message, a terminal device type, a first service time budget, a destination network address, and a network address of a terminal device. The second information comprises one or more of the following: a priority corresponding to an Internet of things service, a resource type, a second service time budget, a size of an uplink data packet, and an uplink and / or downlink rate size.

[0008] In the embodiments of the present application, the first network element can be a user plane network element, for example, a user plane function (UPF). The terminal device can include a user equipment (UE), an Internet of Things device. The first message can be understood as a request for an Internet of Things service (such as an A-IoT request), and the first information can be carried in the packet header of the data packet. Of course, the first message and the first information can also be sent separately. The Internet of Things service can be an A-IoT service.

[0009] After the first network element receives the first information, the first network element can determine the first identifier (such as a QoS-like ID) or the second information according to the first information. The first identifier here is associated with a new quality of service indicator (that is, the second information, such as a QoS-like indicator) defined for the A-IoT service, for example, a priority corresponding to the Internet of Things service, a resource type, a second service time budget, a size of an uplink data packet, an uplink and / or downlink rate size, and the like. Each network node (that is, a UPF, an access network device, a UE, and an Internet of Things device) on a subsequent UP transmission scheme path can perform a traffic processing action according to the second information, thereby facilitating the provision of quality of service for A-IoT in the case of network side resource shortage and limitation.

[0010] In a possible implementation, the identifier of the AF includes one or more of the following: a uniform resource identifier (URL) of the AF, an internet protocol (IP) address of the AF, a media access control (MAC) address of the AF, a Local Area Network (LAN) address of the AF, port information of the AF, or an identification (ID) of the AF.

[0011] In a possible implementation, the service type includes one or more of the following: inventory, command, or registration.

[0012] In a possible implementation, the service object includes a group of terminal devices or a single terminal device.

[0013] In a possible implementation, when the service object is a group of terminal devices, the size of the uplink data packet is the sum of the sizes of the uplink data packets of all terminal devices in the group of terminal devices, or the size of the uplink data packet of a single terminal device in the group of terminal devices.

[0014] In a possible implementation, the terminal device type includes Type A and Type B, Type A is used to indicate a terminal device with extremely low power consumption and / or extremely low complexity, and Type B is used to indicate a terminal device with low power consumption and / or low complexity.

[0015] In a possible implementation, the priority corresponding to the Internet of Things service includes one or more of the following: a priority of the AF, a priority of the service type, a priority of the first message, or a priority of the terminal device type.

[0016] In a possible implementation, the first service time budget or the second service time budget includes: a time length from the start of receiving the first message to the reception of the response message of the last first message; or, a time length from the start of receiving the first message to the reception of the response message of the last first message and returning to the AF; or, a time length from the start of receiving the first message to the reception of the response message of the first message.

[0017] In a possible implementation, the resource type includes: a guaranteed bit rate (GBR) or a non-guaranteed bit rate (Non-GBR) provided for the first message of the Internet of Things service.

[0018] In a possible implementation, before receiving the first message or the first information, the method further includes: receiving first rule information from a session management function (SMF), the first rule information including first indication information, the first indication information being used to indicate a traffic processing action.

[0019] It can be understood that the first network element receives the first message, or the SMF pre-configures the first network element with the first rule information before receiving the first message and the first information. The first rule information can be considered as a packet detection rule (i.e., PDR(s)) issued by the SMF, and the PDR(s) contains related instructions (i.e., the first indication information) for processing the data packet, which is used to indicate specific traffic processing actions (including forwarding action rules (i.e., traffic forwarding), QoS execution rules, etc.). After the first network element receives the first message (i.e., the data packet), the first network element identifies the packet forwarding control protocol (PFCP) session corresponding to the data packet, finds the PDR matching the data packet in the packet detection rule (i.e., PDR(s)) configured for the PFCP session. If there are multiple PDRs that match, a PDR with the highest priority is selected to detect the data packet, and then the data packet is processed according to the requirement of the second information, i.e., the traffic processing action is performed, and finally the data packet is sent out of the user plane network element.

[0020] In a possible implementation, the method further includes: sending the first identifier and / or the second information to the access network device. Based on this manner, subsequent other network nodes can perform traffic processing actions according to the first identifier and / or the second information, so as to realize the guarantee of the quality of service.

[0021] In a second aspect, the present application provides a quality of service guarantee method, applied to an access network device or a terminal device. The method includes: receiving a first identifier and / or a second information, the first identifier being associated with the second information, and the second information including one or more of the following: a priority corresponding to an Internet of Things service, a resource type, a second service time budget, a size of an uplink data packet, and an uplink and / or downlink rate size; and then performing a resource allocation action and / or a traffic processing action based on the second information.

[0022] In the embodiments of the present application, the beneficial effects of the possible implementation manners of the second aspect can be referred to the beneficial effects of the possible implementation manners of the first aspect, which will not be described herein.

[0023] In a possible implementation, the priority corresponding to the Internet of Things service includes one or more of the following: a priority of an AF, a priority of a service type, a priority of the first message, or a priority of a terminal device type.

[0024] In a possible implementation, the resource type includes: a GBR or a Non-GBR provided for the first message of the Internet of Things service.

[0025] In a possible implementation, the second service time budget includes: a time length from receiving the first message to receiving a response message of the last first message; or, a time length from receiving the first message to receiving a response message of the last first message and returning to the AF; or, a time length from receiving the first message to receiving a response message of the first message.

[0026] In a possible implementation, when the service object is a terminal device group, the size of the uplink data packet is the sum of the sizes of the uplink data packets of all terminal devices in the terminal device group, or the size of the uplink data packet of a single terminal device in the terminal device group.

[0027] In a possible implementation, before receiving the first identifier and / or the second information, the method further includes: receiving a configuration file from the SMF, the configuration file including the first identifier and second indication information, the second indication information being used to indicate a resource allocation action and / or a traffic processing action.

[0028] It can be understood that, before receiving the first identifier and / or the second information, the SMF will preconfigure the first configuration file for the access network device through an access and mobility management function (AMF), and will preconfigure the second configuration file for the terminal device through the AMF and the access network device.

[0029] The first configuration file herein can be considered as a QoS configuration file issued by the SMF, including the first identifier and second indication information, wherein the second indication information is used to indicate a specific traffic processing action (including a forwarding action rule (i.e., traffic forwarding), a QoS execution rule, etc.). After receiving the data packet, the access network device can find the first configuration file through the first identifier, and process the data packet according to the requirement of the second information, that is, execute the traffic processing action.

[0030] The second configuration file herein can be considered as a QoS rule issued by the SMF, including the first identifier and second indication information, wherein the second indication information is used to indicate a specific traffic processing action (including a forwarding action rule (i.e., traffic forwarding), a QoS execution rule, etc.). After receiving the data packet, the terminal device can find the first configuration file through the first identifier, and process the data packet according to the requirement of the second information, that is, execute the traffic processing action.

[0031] In a possible implementation, when the service quality guarantee method is applied to the access network device, the method further includes: sending the first identifier and / or the second information to the terminal device. Based on the method, subsequent other network nodes can perform traffic processing actions according to the first identifier and / or the first information, so as to guarantee the service quality.

[0032] In a third aspect, the present application provides a service quality guarantee method, applied to a first network element or an access network device, the method including: receiving third information, the third information including one or more of the following: a priority corresponding to an Internet of Things service, a resource type, a second service time budget, a size of an uplink data packet, and an uplink and / or downlink rate size; and then performing a traffic processing action based on the third information.

[0033] In the embodiments of the present application, the first network element can be a user plane network element, for example, a UPF. The terminal device can include a UE and an Internet of Things device. The first network element receives third information including new service quality indicators (such as QoS-like indicators) defined for A-IoT services, for example, a priority corresponding to an Internet of Things service, a resource type, a second service time budget, a size of an uplink data packet, and an uplink and / or downlink rate size. Each network node (i.e., a UPF, an access network device, a UE, and an Internet of Things device) on a subsequent UP transmission scheme path can directly perform a traffic processing action according to these service quality indicators, thereby facilitating the guarantee of the service quality of A-IoT in the case of network side resource shortage and limitation, and reducing the signaling interaction overhead.

[0034] In a possible implementation, the priority corresponding to the Internet of Things service includes one or more of the following: a priority of an AF, a priority of a service type, a priority of the first message, or a priority of a terminal device type.

[0035] In a possible implementation, the resource type includes GBR or Non-GBR provided for the first message of the Internet of Things service.

[0036] In a possible implementation, the second service time budget includes: a time length from the start of receiving the first message to the reception of a response message to the last first message; or, a time length from the start of receiving the first message to the reception of a response message to the last first message and returning to the AF; or, a time length from the start of receiving the first message to the reception of a response message to the first message.

[0037] In a possible implementation, when the service object is a terminal device group, the size of the uplink data packet is the sum of the sizes of the uplink data packets of all terminal devices in the terminal device group, or the size of the uplink data packet of a single terminal device in the terminal device group.

[0038] In a possible implementation, the method further includes: sending the third information to the access network device or the terminal device.

[0039] Specifically, when the service quality guarantee method is applied to the first network element, the first network element sends the third information to the access network device. When the service quality guarantee method is applied to the access network device, the access network device sends the third information to the terminal device. In this way, subsequent other network nodes can perform traffic processing actions according to the third information, and the service quality is guaranteed.

[0040] In a fourth aspect, the present application provides a service quality guarantee method applied to a terminal device, the method including: receiving third information, the third information including one or more of the following: a priority corresponding to an Internet of Things service, a resource type, a second service time budget, a size of an uplink data packet, an uplink and / or downlink rate size; and then performing a traffic processing action based on the third information.

[0041] In the embodiments of the present application, the terminal device can include a UE, an Internet of Things device. The beneficial effects of possible implementation manners of the fourth aspect can be referred to the beneficial effects of possible implementation manners of the third aspect, which will not be described here.

[0042] In a possible implementation, the priority corresponding to the Internet of Things service includes one or more of the following: a priority of an AF, a priority of a service type, a priority of the first message, or a priority of a terminal device type.

[0043] In a possible implementation, the resource type includes: GBR or Non-GBR provided for the first message of the Internet of Things service.

[0044] In a possible implementation, the second service time budget includes: a time length from the start of receiving the first message to the reception of a response message of the last first message; or, a time length from the start of receiving the first message to the reception of a response message of the last first message and returning to the AF; or, a time length from the start of receiving the first message to the reception of a response message of the first message.

[0045] In a fifth aspect, the present application provides a service quality guarantee method applied to a second network element, the method including: receiving a second message including fourth information; or, receiving a second message and fourth information; wherein the fourth information includes one or more of the following: an identifier of an AF, a service type, a terminal device type, or a priority of the second message.

[0046] In the embodiments of the present application, the second network element can be an A-IoT NF network element. The terminal device can include a UE, an Internet of Things device. In the case of network side resource shortage and limitation, so that each network node on the subsequent CP transmission scheme path can find the corresponding priority information by using the fourth information, thereby performing traffic processing actions according to the priorities, and realizing the guarantee of service quality.

[0047] In a possible implementation, the identifier of the AF includes one or more of the following: a URL of the AF, an Internet Protocol (IP) address of the AF, a MAC address of the AF, a LAN address of the AF, port information of the AF, or an identity (ID) of the AF.

[0048] In a possible implementation, the service type includes one or more of the following: inventory, command, or registration.

[0049] In a possible implementation, the terminal device type includes a type A and a type B, the type A being used to indicate a terminal device with extremely low power consumption and / or extremely low complexity, and the type B being used to indicate a terminal device with low power consumption and / or low complexity.

[0050] In a possible implementation, the fourth information includes an identifier of the AF and a service type, or the fourth information includes an identifier of the AF and a terminal device type; and if the priority of the service type or the priority of the terminal device type is included in the application subscription information corresponding to the AF, the priority of the service type or the priority of the terminal device type is sent to a first access and mobility management function (AMF).

[0051] In the embodiments of the present application, when the fourth information includes an identifier of the AF and a service type, or the fourth information includes an identifier of the AF and a terminal device type, after the second network element receives the fourth information, if the priority of the service type or the priority of the terminal device type is included in the application subscription information corresponding to the AF, the second network element sends the priority of the service type or the priority of the terminal device type to a first AMF, where the first AMF can be an AMF that meets the load requirement expected by the second network element, so as to select an AMF network element with appropriate load to complete communication. Each network node (for example, an A-IoT NF network element, a first AMF, an access network device, a UE, and an Internet of Things device) on the subsequent CP transmission scheme path can perform traffic processing actions according to the priorities, which is beneficial to reduce the congestion of network forwarding processing.

[0052] In a possible implementation, the fourth information includes an identifier of the AF and a priority of the second message; and if the AF is authenticated successfully, the priority of the second message is sent to a first AMF.

[0053] In the implementation of the present application, when the fourth information includes the identifier of the AF and the priority of the second message, after the second network element receives the fourth information, if the AF is authenticated successfully, the second network element sends the priority of the second message to the first AMF, where the first AMF can be an AMF that meets the load requirement expected by the second network element. Thus, each network node (for example, the A-IoT NF network element, the first AMF, the access network device, the UE, and the Internet of Things device) on the CP path can perform traffic processing actions according to the priority, which is beneficial to reducing the congestion of network forwarding processing.

[0054] In a possible implementation, the method further includes: sending, to a network storage function (NRF), a first request for address information of an AMF, the first request including fifth information for indicating a load requirement of the AMF; and receiving, from the NRF, the address information of the first AMF that meets the load requirement. Based on this manner, it is beneficial to reduce the congestion of network forwarding processing of the AMF network element.

[0055] In a sixth aspect, an embodiment of the present application provides a communication apparatus for performing the method in the first aspect to the fifth aspect, or any possible implementation manner of any one of the first aspect to the fifth aspect. The communication apparatus includes a module for performing the method in the first aspect to the fifth aspect, or any possible implementation manner of any one of the first aspect to the fifth aspect.

[0056] In a seventh aspect, an embodiment of the present application provides a communication apparatus including processing circuitry for performing the method in the first aspect to the fifth aspect, or any possible implementation manner of any one of the first aspect to the fifth aspect. The processing circuitry is configured to execute a program stored in a memory, and when the program is executed, the method in any one of the first aspect to the fifth aspect or any possible implementation manner is performed.

[0057] In a possible implementation, the memory is located outside the communication apparatus.

[0058] In a possible implementation, the memory is located inside the communication apparatus.

[0059] In the embodiment of the present application, the processing circuitry and the memory can also be integrated into one device, that is, the processing circuitry and the memory can also be integrated together. For example, the communication apparatus can be a chip.

[0060] In a possible implementation, the communication apparatus further includes transceiver circuitry for receiving information (or input information) or sending information (or output information).

[0061] In an eighth aspect, an embodiment of the present application provides a communication apparatus, the communication apparatus comprising processing circuitry and transceiver circuitry, the processing circuitry can be a logic circuit, and the transceiver circuitry can be an interface circuit, the logic circuit and the interface circuit are coupled; the interface circuit is configured to input and / or output information, and the logic circuit is configured to execute the method in any possible implementation of the first aspect to the fifth aspect, or any one of the first aspect to the fifth aspect.

[0062] In a ninth aspect, an embodiment of the present application provides a chip, the chip comprising processing circuitry and interface circuitry, the processing circuitry and the interface circuitry are coupled; the interface circuitry is configured to input and / or output information, and the processing circuitry is configured to execute code instructions so that the method shown in any one of the first aspect to the fifth aspect or any possible implementation is executed.

[0063] In a tenth aspect, an embodiment of the present application provides a computer readable storage medium, the computer readable storage medium is configured to store a computer program, when the computer program is executed on a computer, the method shown in any one of the first aspect to the fifth aspect or any possible implementation is executed.

[0064] In an eleventh aspect, an embodiment of the present application provides a computer program product, when the computer program product is executed on a computer, the method shown in any one of the first aspect to the fifth aspect or any possible implementation is executed.

[0065] In a twelfth aspect, the present application provides a communication system, the communication system comprising a first network element, an access network device and a terminal device, the first network element is configured to execute the method shown in the first aspect or any possible implementation of the first aspect, the access network device is configured to execute the method shown in the second aspect or any possible implementation of the second aspect, and the terminal device is configured to execute the method shown in the second aspect or any possible implementation of the second aspect.

[0066] In a thirteenth aspect, the present application provides a communication system, the communication system comprising a first network element, an access network device and a terminal device, the first network element is configured to execute the method shown in the third aspect or any possible implementation of the third aspect, the access network device is configured to execute the method shown in the third aspect or any possible implementation of the third aspect, and the terminal device is configured to execute the method shown in the fourth aspect or any possible implementation of the fourth aspect.

[0067] In a fourteenth aspect, the present application provides a communication system, the communication system comprising a second network element, the second network element is configured to execute the method shown in the fifth aspect or any possible implementation of the fifth aspect. BRIEF DESCRIPTION OF DRAWINGS

[0068] FIG. 1 is a schematic diagram of an architecture of a communication system according to an embodiment of the present application;

[0069] FIG. 2 is a schematic diagram of a network architecture of a 5G communication system according to an embodiment of the present application;

[0070] FIG. 3 is a schematic diagram of a topology of a communication system according to an embodiment of the present application;

[0071] FIG. 4A is a schematic diagram of a CP transmission scheme according to an embodiment of the present application;

[0072] FIG. 4B is a schematic diagram of a UP transmission scheme according to an embodiment of the present application;

[0073] FIG. 5 is a schematic diagram of a quality of service guarantee method according to an embodiment of the present application;

[0074] FIG. 6A is a schematic diagram of a GTP-U packet format according to an embodiment of the present application;

[0075] FIG. 6B is a schematic diagram of another quality of service guarantee method according to an embodiment of the present application;

[0076] FIG. 7 is a schematic diagram of another quality of service guarantee method according to an embodiment of the present application;

[0077] FIG. 8 is a schematic diagram of another quality of service guarantee method according to an embodiment of the present application;

[0078] FIG. 9 is a schematic diagram of a structure of a communication apparatus according to an embodiment of the present application;

[0079] FIG. 10 is a schematic diagram of a structure of another communication apparatus according to an embodiment of the present application;

[0080] FIG. 11 is a schematic diagram of a structure of another communication apparatus according to an embodiment of the present application. DETAILED DESCRIPTION

[0081] For the purpose of understanding the technical solution of the present application, the present application will be further described below with reference to the accompanying drawings.

[0082] The terms "first" and "second" and the like in the description, claims, and drawings of the present application merely mean different objects and do not imply a particular order. Furthermore, the terms "include" and "have" and any variations thereof are intended to cover a non-exclusive inclusion. For example, a process, a method, a system, a product, or an apparatus, or the like including a series of steps or units is not limited to the listed steps or units but can optionally further include other steps or units not listed or inherent to such processes, methods, products, or apparatuses.

[0083] Reference within this document to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase "in one embodiment" in various places in the specification are not necessarily all referring to the same embodiment, nor are they necessarily all referring to a common embodiment, or an embodiment that is independent of other embodiments. One of ordinary skill in the art will recognize that the embodiments described herein can be combined with other embodiments in various ways.

[0084] In this application, "at least one", "multiple", "two or more", "at least two", "and / or" are used to describe the relationship between associated objects, which means that there can be three relationships, for example, "A and / or B" can mean: only A, only B, and A and B exist at the same time, where A and B can be singular or plural. "Or" means that there can be two relationships, such as only A, only B; when A and B are not mutually exclusive, it can also mean that there are three relationships, such as only A, only B, and A and B exist at the same time. The character " / " generally represents an "or" relationship between the associated objects before and after it. "At least one of the following" or similar expressions means any combination of these items. For example, at least one of a, b, or c, can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c".

[0085] In this application, "sending" and "receiving" represent the direction of signal transmission. For example, "sending information to XX" can be understood as the destination of the information being XX, which can include direct transmission through the air interface, or indirect transmission through other units or modules through the air interface. "Receiving information from YY" can be understood as the source of the information being YY, which can include direct reception from YY through the air interface, or indirect reception from YY through other units or modules through the air interface. "Sending" can also be understood as the "output" of the chip interface, and "receiving" can also be understood as the "input" of the chip interface. In other words, sending and receiving can be between devices, such as between network devices and terminal devices, or within a device, such as between components, modules, chips, software modules or hardware modules within a device through a bus, wire or interface.

[0086] In order to better understand the embodiments of the application, first, the communication system related to the embodiments of the application will be introduced:

[0087] The method provided by the embodiments of the present application can be applied to various communication systems, for example, a wireless local area network (WLAN) communication system, a wireless fidelity (Wi-Fi) system, a multiple-in multiple-out (MIMO) communication system, a long term evolution (LTE) system, an internet of things (IoT) system, a narrow band internet of things (NB-IoT) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD), a 4th generation (4G) system, a 5th generation (5G) system or a new radio (NR), and other future communication systems, for example, a 6th generation (6G) system, and the like. The IoT network may, for example, include but is not limited to a vehicle internet. The communication mode in the vehicle internet system can be collectively referred to as vehicle-to-everything (V2X, X may represent any thing). For example, the V2X may include vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication or vehicle-to-network (V2N) communication, and the like. The method provided by the embodiments of the present application also supports a communication system of multiple wireless technology fusion, for example, can also be applied to a system of unmanned aerial vehicle, satellite communication system, high altitude platform station (HAPS) communication and the like non-terrestrial network (NTN) fusion ground mobile communication network. In addition, it can also be applicable to low frequency (sub 6 GHz) and high frequency (above 6 GHz) communication scenarios. It can be understood that the system architecture described in the embodiments of the present application is for more clearly illustrating the technical solutions provided by the embodiments of the present application, and does not constitute a limitation on the technical solutions provided by the embodiments of the present application.

[0088] The following introduces the infrastructure of the communication system provided by the embodiments of the present application, as shown in FIG. 1, which is a schematic diagram of the infrastructure of the communication system applicable to the embodiments of the present application. The communication system 10 includes a radio access network (RAN) 100, a core network (CN) 200, and a data network (DN) 300. The RAN 100 includes at least one RAN node (such as 110a and 110b in FIG. 1, collectively referred to as 110) and at least one terminal (such as 120a-120j in FIG. 1, collectively referred to as 120). The RAN 100 can also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in FIG. 1), etc. The terminal 120 is connected to the RAN node 110 in a wireless manner. The RAN node 110 is connected to the core network 200 in a wireless or wired manner. The core network device in the core network 200 and the RAN node 110 in the RAN 100 can be different physical devices respectively, or can be the same physical device integrated with the logical functions of the core network and the logical functions of the radio access network. The core network 200 can also be connected to the data network 300 in a wireless or wired manner.

[0089] The RAN 100 can be a 3rd generation partnership project (3GPP) related cellular system, such as a 4G, 5G mobile communication system, or a future-oriented evolution system. The RAN 100 can also be an open radio access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. The RAN 100 can also be a communication system that combines two or more of the above systems.

[0090] Specifically, the following describes the terminal device, the RAN node (which can also be referred to as an access network device), the core network device, and the data network involved in the communication system in FIG. 1 in detail, respectively.

[0091] I. Terminal device (which can also be referred to as terminal)

[0092] A terminal can be a device or module with corresponding communication functions to access the above-mentioned communication system. The terminal can also be referred to as a terminal device, a user equipment (UE), a mobile station, a mobile terminal, etc. The terminal can be widely applied to various scenarios, such as device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-type communication (MTC), internet of things (IoT), extended reality (ER), virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, remote medical treatment, smart power grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc. The terminal can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a wearable device (such as a smart watch, a smart bracelet, a pedometer, etc.), a vehicle, a drone, a helicopter, an airplane, a ship, a robot, a mechanical arm, a smart home device, a transport vehicle with wireless communication function, a communication module, etc. In addition, the terminal here can also be a passive terminal. Embodiments of the present application do not limit the device form of the terminal. The terminal is usually provided with a communication module, circuit or chip for executing corresponding communication functions. The terminal is also configured with program instructions for executing corresponding communication functions.

[0093] II. RAN node

[0094] The RAN node 110, which can also be referred to as an access network device, a RAN entity or an access node, etc., constitutes a part of the communication system to help the terminal to realize wireless access. The RAN nodes 110 in the communication system 10 can be nodes of the same type or nodes of different types. In some scenarios, the roles of the RAN node 110 and the terminal 120 are relative, for example, the network element 120i in FIG. 1 can be a helicopter or a drone, which can be configured as a mobile base station. For those terminals 120j accessing the RAN 100 through the network element 120i, the network element 120i is a base station; but for the base station 110a, the network element 120i is a terminal. The RAN node 110 and the terminal 120 are sometimes referred to as communication apparatuses, for example, the network elements 110a and 110b in FIG. 1 can be understood as communication apparatuses with base station functions, and the network elements 120a-120j can be understood as communication apparatuses with terminal functions.

[0095] In a possible scenario, the RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next generation NodeB (gNB), a base station in a future mobile communication system, or an access node in a WiFi system, etc. The RAN node can be a macro base station (such as 110a in FIG. 1), a micro base station or an indoor station (such as 110b in FIG. 1), a relay node or a donor node, or a wireless controller in a CRAN scenario. Optionally, the RAN node can also be a server, a wearable device, a vehicle or a vehicle-mounted device, etc. For example, the access network device in vehicle to everything (V2X) technology can be a road side unit (RSU). All or part of the functions of the RAN node in this application can also be implemented by software functions running on hardware, or by virtualized functions instantiated on a platform (such as a cloud platform). The RAN node can also be provided with a communication module, circuit or chip for performing corresponding communication functions, and program instructions for performing corresponding communication functions. The RAN node in this application can also be a logical node, a logical module or software that can implement all or part of the functions of the RAN node.

[0096] In another possible scenario, multiple RAN nodes cooperate to assist a terminal to implement wireless access, and different RAN nodes respectively implement part of the functions of a base station. For example, the RAN node can be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), etc. The CU and the DU can be separately arranged, or can be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or a radio frequency unit, such as a remote radio unit (RRU), an active antenna processing unit (AAU), or a remote radio head (RRH).

[0097] In different systems, the CU (or CU-CP and CU-UP), DU or RU can also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, the CU can also be referred to as O-CU (open CU), the DU can also be referred to as O-DU, the CU-CP can also be referred to as O-CU-CP, the CU-UP can also be referred to as O-CU-UP, and the RU can also be referred to as O-RU. For the convenience of description, the CU, CU-CP, CU-UP, DU and RU are taken as examples for description in this application. Any one of the CU (or CU-CP, CU-UP), DU and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0098] III. Core network device

[0099] The core network device refers to a device in the core network that provides service support for the terminal device, and is mainly responsible for registration, call connection, charging, mobility management, providing user connection, management of users, and completion of service bearing, data processing and routing, etc. The core network device can correspond to different devices in different communication systems. For example, in the 4G communication system, it can correspond to one or more of the mobility management entity (MME), the serving gateway (S-GW), etc. For another example, in the 5G communication system, it can correspond to one or more of the access and mobility management function (AMF) network element, the session management function (SMF) network element, the user plane function (UPF) network element, etc. In the next generation communication system or future communication system, it can correspond to one or more network elements, devices or entities that provide service support for the terminal device.

[0100] IV. Data network (DN)

[0101] The data network is a network outside the mobile communication system, and can provide services for users. For example, the DN can be a packet data network (PDN), such as the Internet, an Internet Protocol Multimedia Service (IMS) network, a data network dedicated to some application, an Ethernet network, an Internet Protocol (IP) local network, etc. Among them, the IP protocol can use IPv4 or IPv6. The DN can deploy multiple services to provide data and / or voice services for terminal devices. There can be multiple application servers (ASs) in the DN, and each AS can provide at least one service.

[0102] It should be noted that the communication system shown in FIG. 1 is not limited to only including the terminal device, access network device, core network device and data network shown in the figure, but can also include other devices not shown in the figure, which will not be enumerated one by one here.

[0103] For example, taking the 5G communication system as an example, as shown in FIG. 2, FIG. 2 is a network architecture of a 5G communication system based on a service-oriented architecture provided by an embodiment of the present application. The network architecture can include a UE, a radio access network (RAN), and a core network (CN). The network architecture can also include a data network (DN) and / or an application function (AF) network element. The UE accesses the core network through the RAN, and communicates with the DN or the AF network element through the core network.

[0104] Among them, the AF network element supports interaction with the 3GPP core network to provide services, such as affecting data routing decisions, policy control functions, or providing third-party services to the network side. Specifically, it can be responsible for unified policy formulation, provision of policy control, and obtaining subscription information related to policy decision from the unified data repository (UDR) network element, and other policy-related functions. The provision of policy control can include providing service data flow and application detection, gating, quality of service (QoS), and flow-based charging control, etc. In future communication systems, the application function network element can also have other names, which are not limited.

[0105] The core network element can include two types of user plane network elements and control plane network elements. Among them, the control plane network element can include AMF, SMF, unified data management (UDM) network element, network exposure function (NEF), network function repository function (NRF), and policy control function (PCF) network element, etc.

[0106] The AMF network element can complete connection management, registration process, mobility management, access authentication and authorization management, reachability management, security context management, SMF network element selection, and other access and mobility related functions. In addition, it is also responsible for transmitting user policies between the terminal device and the PCF network element.

[0107] The SMF network element is mainly responsible for session management in the mobile network, selection and control of the UPF network element, service and session continuity (SSC) mode selection, roaming, and other session related functions. Session management can include session establishment, modification, release, update, etc. Session management can also include tunnel maintenance between the UPF network element and the access network device.

[0108] The UDM network element is mainly used to manage user subscription data and authentication data, and perform authentication credit processing, user identification processing, access authorization, registration / mobility management, subscription management, and short message management, etc. In some embodiments, the UDM can also include a unified data repository (UDR) network element. Alternatively, in other embodiments, the 3GPP SBA of the 5G system can also include a UDR. Among them, the UDR is used to provide storage and retrieval for PCF policies, storage and retrieval of open structured data, and storage of user information requested by application functions, etc.

[0109] The NEF network element is mainly responsible for the business and capabilities provided by the open 3GPP network function, which can be internally opened or opened to third parties, etc. It translates or translates information interacted with the AF network element and information interacted with internal network functions, such as AF network element service identification and internal 5G core network information, such as data network name (DNN), single network slice selection support information (NSSAI) (single NSSAI, S-NSSAI), etc.

[0110] The NRF network element is used for NF registration, management, and state detection, and realizes automatic management of all NFs. Each NF, when started, registers with the NRF to provide services, and the registration information includes NF type, address, service list, and the like.

[0111] The PCF network element is a control plane function provided by an operator, and includes user subscription data management functions, policy control functions, charging policy control functions, quality of service (QoS) control, and the like, and is mainly used to provide policies for PDU sessions to the SMF. The policies can include charging-related policies, QoS-related policies, and authorization-related policies, and the like.

[0112] The user plane network element can be a user plane function (UPF) network element, and is mainly responsible for user plane-related content, such as data packet routing and transmission, mobility anchor points, uplink classifiers to support routing traffic flows to data networks, branch points to support multi-homing protocol data unit (PDU) sessions, packet detection, service usage reporting, QoS processing, lawful interception, downlink packet storage, charging information statistics, and the like; and can also be responsible for receiving and forwarding user data, for example, can receive user data from a data network and transmit it to a terminal device through an access network device; the user plane network element can also receive user data from a terminal device through an access network device and forward it to a data network. In future communication systems, the user plane network element can also have other names, which are not limited.

[0113] Of course, the communication system shown in FIG. 2 can also involve other network elements, which are not limited here. For example, the core network can also include an authentication server function (AUSF) network element, a network slice selection function (NSSF), and the like. In addition, the UE, RAN, CN, and DN involved in FIG. 2 can refer to the description of FIG. 1 above, and are not described here.

[0114] It should be noted that the above-mentioned core network device can also be referred to as a network element or a functional network element. In the 5G communication system, each functional network element can be the name of each functional network element shown in FIG. 2, and in the communication system evolved after 5G (such as the 6G communication system), each functional network element can still be the name of each functional network element shown in FIG. 2, or can also have other names. For example, in the 5G communication system, the user plane function can be a UPF, and in the communication system evolved after 5G (such as the 6G communication system), the user plane function can still be a UPF, or can also have other names, which are not limited by the present application.

[0115] It also needs to be explained that in the 5G communication system, the functions implemented by each functional network element can be independent as shown in FIG. 2. In the communication system evolved after 5G (such as 6G communication system), each functional network element can still be in the state shown in FIG. 2, or the functions of multiple functional network elements in FIG. 2 can be implemented by an integrated functional network element. For example, in the 5G communication system, the functions related to the user plane are implemented by the UPF, and the functions related to access and mobility management are implemented by the AMF. In the communication system evolved after 5G (such as 6G communication system), the functions related to the user plane can still be implemented by the UPF, the functions related to access and mobility management can still be implemented by the AMF, or an integrated functional network element can simultaneously implement the functions related to the user plane and the functions related to access and mobility management. The application is not limited.

[0116] In FIG. 2, Nnrf, Nnef, Npcf, Namf, Nudm, Nsmf, Naf, N1, N2, N3, N4, N6 and N9 are interface serial numbers. The meanings of these interface serial numbers can be referred to the meanings defined in the related standard protocols, which are not limited herein.

[0117] The application scenarios of the present application are introduced as follows.

[0118] Embodiments of the present application can be applied to the Internet of Things scenario, and in particular, can be applied to the Ambient Internet of Things (A-IoT) scenario. The so-called A-IoT, also known as passive Internet of Things, is to collect energy from the environment for data communication, and aims to provide a battery-free, low-power, low-complexity and low-cost Internet of Things solution. A-IoT technology is an extremely low-power and extremely low-complexity Internet of Things technology defined by the 3GPP plenary, which can be understood as an extension of passive radio frequency identification (RFID) in 3GPP. Although it has some principles in common with RFID, such as a similar inventory service process, more value-added scenarios will be introduced in 3GPP. Among them, A-IoT technology can be used to implement one or more of the following services: inventory, positioning, sensing, or command. It can be understood that the command service can include one or more of the following services: read, write, lock, disable / kill, enable. For application scope, A-IoT technology can be applied to logistics, warehousing, industrial manufacturing, identity recognition or environmental monitoring scenarios, and the present application does not limit this. It should be noted that A-IoT can also have other names, which are not limited herein. In the embodiments of the present application, the A-IoT service can be referred to as an Internet of Things service, and in addition, "service" can be replaced by "business".

[0119] The topology of the A-IoT-based communication system is exemplarily introduced below. Of course, other topologies can also be included, which are not limited herein.

[0120] Topology 1: Referring to 3-1 of FIG. 3, in 3-1 of FIG. 3, the access network device acts as a reader / writer. The access network device directly communicates with the A-IoT device in both directions. The communication between the access network device and the A-IoT device includes A-IoT data and / or signaling.

[0121] Topology 2: Referring to 3-2 of FIG. 3, in 3-2 of FIG. 3, the intermediate node acts as a reader / writer. The access network device indirectly communicates with the A-IoT device through the intermediate node. In topology 2, the access network device and the A-IoT device communicate with each other through the intermediate node. The intermediate node can be a relay capable of implementing A-IoT, such as an IAB node, a terminal device, or a repeater, and the present application does not limit the form of the intermediate node. The various devices involved in FIG. 3 will be described in detail below.

[0122] (1) Reader / writer

[0123] The reader, also referred to as a reader-writer, is a device with reading and writing functions. The reader-writer can communicate with the A-IoT device in a non-contact manner, such as through broadcasting. In this way, the reader-writer can read information from the A-IoT device and / or write information to be stored into the A-IoT device.

[0124] The reader-writer can be the terminal device or the access network device in FIG. 1 or FIG. 2, and the application does not limit the form of the reader-writer. For example, the device for implementing the function of the reader-writer can be the reader-writer; or the device can be a chip system that can support the reader-writer to implement the function. The device can be installed in the reader-writer or used in combination with the reader-writer.

[0125] Optionally, when the terminal device is the reader-writer, the terminal device can be referred to as a terminal device reader-writer (UE reader). When the access network device is the reader-writer, the access network device can be referred to as an A-IoT RAN node. The application does not limit the name.

[0126] (2) A-IoT device

[0127] The A-IoT device is different from the communication device in the conventional cellular network, and it does not have a radio resource control (RRC) state and does not need to establish an RRC connection. Generally, the A-IoT device can communicate with the reader through backscatter technology, or the A-IoT device can generate a carrier (or can be understood as having a carrier recovery capability) by itself and does not need to rely on an external carrier source for communication, and has an active communication capability. In the embodiments of the application, the A-IoT device can be referred to as an Internet of Things device.

[0128] For the A-IoT device that communicates with the reader through backscatter technology, the A-IoT device can be powered through RF signals or obtain energy through energy harvesting (light energy, thermal energy, kinetic energy, etc.). In this case, the A-IoT device can be referred to as a passive A-IoT device or a semi-passive A-IoT device. The passive A-IoT device can also be referred to as device 1 (device 1) or device A (device A), and the semi-passive A-IoT device can also be referred to as device 2a (device 2a) or device A (device A), and the application does not limit the name.

[0129] For the A-IoT device that generates a carrier by itself, the A-IoT device can be referred to as an active A-IoT device. The active A-IoT device can also be referred to as device 2b (device 2b) or device B (device B).

[0130] The A-IoT device can be a tag, a terminal, or any other form, such as a sensor, a license plate, a nameplate, etc. Embodiments of the present application do not limit the form of the A-IoT device. For example, the device for implementing the function of the A-IoT device can be the A-IoT device; or can be a device capable of supporting the A-IoT device to implement the function, such as a chip system. The device can be installed in the A-IoT device or used in conjunction with the A-IoT device.

[0131] It should be noted that the number of devices in FIG. 3 is only illustrative and should not be considered as a specific limitation of the present application. Optionally, FIG. 3 can also include a core network (not shown in FIG. 3), which is accessed by the terminal through the access network, and communicates with the DN or AF network element. For details, refer to FIG. 1 and FIG. 2, which will not be described here.

[0132] In addition to the two topologies, 3GPP is also developing a transmission scheme for data of the A-IoT device in the core network: one is a control plane (CP) transmission scheme, and the other is a user plane (UP) transmission scheme. The two transmission schemes will be described in detail below.

[0133] For the CP transmission scheme, as shown in FIG. 4A, in the architecture of topology 1, the AF network element can communicate with the NEF network element, the NEF network element can communicate with the A-IoT NF network element, the A-IoT NF network element can communicate with the AMF network element, and the AMF network element can communicate with the A-IoT device (A-IoT device) through the access network (RAN) device. In the architecture of topology 2, an intermediate node (UE reader) is added. The AF network element can communicate with the NEF network element, the NEF network element can communicate with the A-IoT NF network element, the A-IoT NF network element can communicate with the AMF network element, and the AMF network element can communicate with the intermediate node (UE reader) through the access network (RAN) device. Then, the intermediate node (UE reader) is used to communicate with the A-IoT device (A-IoT device).

[0134] For UP transmission scheme, as shown in FIG. 4B, in the architecture of topology 1, the AF network element can communicate with the UPF network element, and the UPF network element can communicate with the A-IoT device (i.e., A-IoT device) through the access network (RAN) device. In the architecture of topology 2, an intermediate node (UE reader) is added, the AF network element can communicate with the UPF network element, and the UPF network element can communicate with the intermediate node (UE reader) through the access network (RAN) device, and then communicate with the A-IoT device (i.e., A-IoT device) through the intermediate node (UE reader).

[0135] Taking the inventory service of A-IoT as an example, there can be multiple AFs, and each AF can initiate an inventory instruction to one or more A-IoT devices, at which time the reader (such as UE reader) needs to communicate with one or more A-IoT devices.

[0136] Among them, the network elements in the core network not only include the network elements in FIG. 2, but also include an A-IoT NF network element (hereinafter referred to as a second network element). The A-IoT NF network element here is responsible for processing the logic of the A-IoT service, specifically including: executing A-IoT service requests (such as inventory, command, etc.) in the network, and processing corresponding A-IoT specific NAS messages; supporting inventory, command, registration, and message routing of A-IoT devices; authorizing A-IoT service requests; performing verification of the identity (such as identification (ID)) of the A-IoT device, and performing operations to protect the A-IoT device when needed; collecting A-IoT data and summarizing reports; collecting charging information; and the like. Of course, the naming of the A-IoT NF network element here is only an example, and other naming methods can also be used, which are not limited here. In addition, the A-IoT NF network element can be regarded as an upgrade based on the AMF network element, and the A-IoT NF network element can be deployed together with the AMF network element or separately, which is not limited here.

[0137] It should be noted that the network application architecture and application scenarios described in the embodiments of the present application are for more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art can know that, with the evolution of network application architecture and the appearance of new business scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0138] In order to facilitate understanding of the scheme provided by the embodiments of the present application, the related concepts involved in the embodiments of the present application are introduced as follows:

[0139] 1. Quality of Service (QoS)

[0140] Currently, QoS refers to the ability of a network to provide better service capabilities for specified network communications using various underlying technologies, and is a security mechanism for a network and a technology used to solve network delay and congestion problems. QoS protection is very important for networks with limited capacity, especially for streaming multimedia applications, because these applications often require fixed transmission rates and are sensitive to latency.

[0141] QoS provides end-to-end quality of service protection for different service requirements. QoS does not increase network bandwidth, it is a tool for efficient use of existing network resources, and it allows different traffic to compete for network resources unequally, with voice, video and important data applications being given priority in network devices. QoS technology is increasingly used in today's Internet and plays an increasingly important role. Among them, the traffic processing actions corresponding to the QoS service can include traffic forwarding (or service forwarding), traffic policing, traffic shaping, interface rate limiting, congestion avoidance, congestion management, etc.

[0142] 2. QoS flow (QoS Flow) and QoS configuration

[0143] QoS flow is the finest QoS granularity in a PDU session, that is, the difference between two PDU sessions is that their QoS flows are different (specifically, the traffic flow template (TFT) parameters of the QoS flow are different). In the 5G system, a QoS flow ID (QoS Flow ID, QFI) is used to identify a QoS flow; user plane data with the same QFI in a PDU session will receive the same forwarding processing (such as the same resource allocation, resource scheduling, the same admission threshold, etc.); QFI is unique within a PDU session, that is, a PDU session can have multiple (up to 64) QoS flows, but the QFI of each QoS flow is different (the value range is 0-63). The QFI of two PDU sessions of a terminal device can be repeated, and the QFI can be dynamically configured or equal to the 5G QoS identifier (5G QoS Identifier, 5QI). Among them, 5QI is a parameter used to identify the quality of service in a 5G network, which represents a set of values of a group of parameters such as resource type, priority, reliability, and packet loss rate, and is used to control QoS flow forwarding processing. In the 5G network, the specific value of 5QI determines the resource type, priority, and other characteristics of different QoS flows. Among them, the characteristics of the QoS flow are:

[0144] For RAN side QoS profiles, these profiles can be provided by SMF network element through AMF network element to RAN or pre-configured on RAN.

[0145] For UE side QoS rules, these rules are provided by SMF network element to UE in PDU establishment or modification procedure or derived by UE through reflective QoS mechanism.

[0146] For UPF side uplink and downlink packet detection rules (PDRs), these PDRs are configured by SMF.

[0147] In the 5G communication system, one PDU session requires one QoS flow associated with a default QoS rule, this default QoS flow remains existing in the whole life cycle of the PDU, and this default QoS flow is a non-guaranteed bit rate (Non-GBR) QoS flow. It should be noted that in the embodiments of the present application, the synchronization of the QoS profile is based on the QoS profile synchronization mechanism, that is, the synchronization between the SMF, AIOT NF, AMF / UPF, RAN node, UE reader, and each network node uses the same QFI identifier to identify the QoS profile corresponding to the data packet (for details, refer to the protocol [TS23.501]).

[0148] In addition, the current 5G QoS characteristics related to 5QI include resource type, priority level, packet delay budget (PDB), packet error rate (PER), averaging window, and maximum data burst volume (MDBV). Among them, the QoS characteristics here are QoS indicators for data packets, specifically:

[0149] (1) Resource type: can be guaranteed bit rate (GBR) or non-GBR;

[0150] (2) Priority level: indicates the resource scheduling priority among 5G QoS flows, this parameter is used to distinguish the QoS flows of one UE, and also used to distinguish the QoS flows of different terminals, the smaller the parameter value, the higher the priority;

[0151] (3) Packet delay budget: defines the upper limit of the delay of data packet transmission between the UE and the anchor NPF;

[0152] (4) Packet error rate (PER): refers to the ratio of data packets that have been processed by the link layer (such as the RLC layer of the 3GPP access network) of the sending end, but not submitted to the upper layer (such as the PDCP layer of the 3GPP access network) of the corresponding receiving end. The function of the PER parameter is to allow the network to configure appropriate link layer parameters (such as RLC and HARQ configuration of the 3GPP access network);

[0153] (5) Average window: defined for GBR QoS flow, used by the relevant network element to calculate the guaranteed flow bit rate (GFBR) and the maximum flow bit rate (MFBR);

[0154] (6) Maximum data burst volume (MDBV): each GBR QoS flow with delay-critical resource type should be associated with an MDBV; MDBV represents the maximum amount of data that the RAN needs to serve during a PDB.

[0155] Specifically, the mapping of standard 5QI to 5G QoS characteristics is shown in Table 1, and Table 1 only describes part of the mapping relationship. More mapping relationships can be referred to the protocol [TS23.501 Table 5.7.4-1].

[0156] Table 1

[0157] Based on the above, as A-IoT is put into commercial use, more and more A-IoT devices access the network, resulting in heavier traffic processing burden of the network. In the case of limited and scarce network resources, the service quality of A-IoT cannot be effectively guaranteed at present.

[0158] Therefore, in order to effectively guarantee the service quality of A-IoT in the case of limited and scarce network resources, the embodiments of the present application provide a service quality guarantee method and a communication device. The service quality guarantee method and the communication device provided by the embodiments of the present application are described in detail below.

[0159] In the embodiments of the present application, the Internet of Things service can be A-IoT service, or can be represented by other names, which are not limited here; the "service" here can be replaced by "business"; the service quality here can be referred to as business quality, or can be represented by other names, which are not limited here, and the embodiments of the present application take the service quality as an example;

[0160] Currently, 3GPP is in the early stage of defining the A-IoT device function, service interaction process, and service interaction content, and has not discussed the service quality indicators and methods for A-IoT. Moreover, the current service quality indicators (such as the packet error rate and packet delay budget mentioned above) are mainly indicators for data packets. Since the number of A-IoT devices is large, and the amount of data transmitted by each A-IoT service is small (that is, the A-IoT device has low power consumption), if the current service quality indicators are still used to guarantee the service quality of A-IoT, it will increase the signaling interaction burden of the network. Therefore, the current service quality indicators are not suitable for A-IoT services.

[0161] In order to guarantee the service quality of A-IoT in the case that the network side resource is limited and cannot meet the resource requirements of all A-IoT services, the embodiments of the present application define new service quality indicators (which can be called QoS-like indicators, or other names, which are not limited here) and related network processing solutions for A-IoT services. The service quality identifier is notified to the RAN reader side or the UE reader side to do resource scheduling on the wireless side, so as to more efficiently meet the requirements of A-IoT services and guarantee the efficiency of A-IoT inventory, command, registration and other services end-to-end.

[0162] Taking the QoS-like indicator as an example, the QoS-like indicator can include one or more of the following: the priority corresponding to the Internet of Things service, the resource type (Resource Type), the service time budget (Service Time Budget), or the size of the uplink data packet (Device UL Packet Size), the uplink and / or downlink rate size. Of course, the QoS-like indicator can also include other information, which is not limited here. The information included in the QoS-like indicator is described in detail below:

[0163] 1. Resource Type: It can be a guaranteed bit rate (GBR) provided for the service request of the Internet of Things service, or a non-guaranteed bit rate (Non-GBR) provided for the message of the Internet of Things service. Here, the service request can also be referred to as a message.

[0164] 2. Priority corresponding to the Internet of Things service: For example, the priority corresponding to the A-IoT service. The Internet of Things service can be a service requested by different AFs, or a service requested by the same AF. Four priorities are defined as follows:

[0165] Case 1: Priority of AF

[0166] It can be understood that the priority is set according to the identifier of the different AFs. The priority of the AFs includes but is not limited to "high", "higher", "ordinary", and the like. The identifier of the AFs includes but is not limited to any one of the following: a uniform resource identifier (URL) of the AF, an internet protocol (IP) address of the AF, a media access control (MAC) address of the AF, a Local Area Network (LAN) address of the AF, port information of the AF, or an identification (ID) of the AF. The UPF user plane offloading identifier can be the identifier of the AF.

[0167] Exemplarily, for different AFs, if the identifier of the AF is 1 (for example, the AF is a video application), the corresponding priority can be set as high; if the identifier of the AF is 2 (at this time, the AF is a storage application), the corresponding priority can be set as ordinary.

[0168] Case 2: Priority of different service types of the same AF

[0169] It can be understood that the priority is set according to different service types of the same AF. The priority of the service types includes but is not limited to "high", "higher", "ordinary", and the like. The service types include but are not limited to one or more of the following: inventory, command, or registration. The command includes one or more of the following: read, write, lock, disable / kill, and enable. The UPF user plane offloading identifier can be the service type.

[0170] Exemplarily, for the same AF, if the service type is read or write, the corresponding priority can be set as high; if the service type is inventory, the corresponding priority can be set as ordinary.

[0171] Case 3: Priority of different service requests of the same AF

[0172] It can be understood that the priority is set according to different service requests of the same AF. The priority of the service requests includes but is not limited to "high", "higher", "ordinary", and the like. The UPF user plane offloading identifier can be the type of the service request (request type), such as traffic forwarding (or service forwarding), traffic policing, and the like.

[0173] Exemplarily, for the same AF, if the priority indicated by the service request is high, the corresponding priority can be set as high; if the priority indicated by the service request is normal, the corresponding priority can be set as normal. Alternatively, if the service request does not indicate the priority, the default priority can also be set as normal.

[0174] Case 4: Priority of the same AF and different terminal device types

[0175] It can be understood that the priority is set according to different terminal device types (for example, A-IoT device types) of the same AF. The priority of the terminal device type includes but is not limited to “high”, “higher”, “normal”, etc. The terminal device type includes type A and type B, type A is used to indicate a terminal device with extremely low power consumption and / or extremely low complexity (such as “goods label”), and type B is used to indicate a terminal device with low power consumption and / or low complexity (such as “sensor”). The UPF user plane shunting identifier can be the terminal device type.

[0176] Exemplarily, for the same AF, if the terminal device type is a sensor, the corresponding priority can be set as high; if the terminal device type is a goods label, the corresponding priority can be set as normal.

[0177] 3, Service Time Budget: The difference between the service time budget and the PDB in the existing QoS index is that the PDB is the one-way delay of a single data packet or a group of data packets in the network node. The service time budget in the embodiment of the application can be the time length from the triggering of the service by the AF request to the response of the last terminal device (such as A-IoT device); it can also be the time length from the triggering of the service by the AF request to the response of the last terminal device (such as A-IoT device) and the return to the AF; it can also be the time length from the triggering of the service by the AF request to the reception of the response message. It can be understood that one Internet of Things service request (A-IoT request) generally has multiple A-IoT devices responding, and there are multiple signaling interactions at the RAN side, while the existing PDB can at most represent the transmission delay of one data.

[0178] 4, Size of uplink data packet (Device UL Packet Size): It refers to the estimation of the AF on the size of the data packet of the terminal device (such as A-IoT device) response, which can be used for resource allocation, traffic processing action guarantee of the base station and UPF when the uplink A-IoT data is transmitted in the network. When the service object is a terminal device group, the size of the uplink data packet is the sum of the sizes of the uplink data packets of all terminal devices in the terminal device group, or the size of the uplink data packet of a single terminal device in the terminal device group.

[0179] 5. Uplink and / or downlink rate size: the uplink rate size refers to the data transmission rate from the terminal device to the network, and the downlink rate size refers to the data transmission rate from the network to the terminal device.

[0180] Based on the new service quality indicators (such as QoS-like indicators) proposed above, embodiments of the present application respectively design the way of synchronizing the QOS-like indicators of the UP transmission scheme and the CP transmission scheme to the user plane node in the network, effectively solving the problem of guaranteeing the service quality of A-IoT when CN / RAN faces the competition of forwarding / processing resources. Next, in combination with the application scenarios of A-IoT, the service quality guarantee method provided by the embodiments of the present application will be described in detail for different transmission schemes:

[0181] I. For the UP transmission scheme

[0182] Method one: each network node on the path of the UP transmission scheme performs traffic processing actions according to the QoS-like identifier (i.e., the first identifier).

[0183] FIG. 5 is a flowchart of a service quality guarantee method provided by an embodiment of the present application. As shown in FIG. 5, the service quality guarantee method includes the following steps S501-S503. Optionally, the service quality guarantee method further includes the following steps S504-S509. The method execution subject shown in FIG. 5 can be the first network element (user plane network element, such as UPF), access network device, and terminal device mentioned above. Alternatively, the method execution subject shown in FIG. 5 can be a chip in the first network element, a chip in the access network device, and a chip in the terminal device, which is not limited in the embodiments of the present application. FIG. 5 takes the first network element, the access network device, and the terminal device as the execution subject of the method for example. Among them, the terminal device can include UE and Internet of Things devices (such as A-IoT devices), and the UE can be considered as an intermediate node.

[0184] It can be understood that, in the embodiments of the present application, the first network element, the access network device and the terminal device are taken as examples of the execution subject of the interaction diagram, but the present application does not limit the execution subject of the interaction diagram. For example, the method executed by the first network element in the present application can also be implemented by a module (such as a circuit, a chip or a chip system, etc.) in the first network element, or a logical node, a logical module or software capable of realizing all or part of the functions of the first network element; the method executed by the access network device in the present application can also be implemented by a module (such as a circuit, a chip or a chip system, etc.) in the access network device, or a logical node, a logical module or software capable of realizing all or part of the functions of the access network device; the method executed by the terminal device in the present application can also be implemented by a communication / processing module in the terminal device or a circuit or chip (such as a modem chip (also known as a baseband chip), or a SoC chip / SIP chip containing a modem core, or a GPU / AI processor / ASIC) responsible for communication / processing functions in the terminal device.

[0185] S501, the first network element receives a first message, the first message comprising first information; or, the first network element receives a first message and first information.

[0186] The first information comprises one or more of the following: an identifier of the AF, a service type, a service object, a priority of the first message, a terminal device type, a first service time budget, a destination network address, and a network address of the terminal device.

[0187] S502, the first network element determines a first identifier and / or second information based on the first information, the first identifier being associated with the second information.

[0188] The second information comprises one or more of the following: a priority corresponding to an Internet of Things service, a resource type, a second service time budget, a size of an uplink data packet, and an uplink and / or downlink rate size.

[0189] In the embodiments of the present application, the first network element can receive a first message from the AF, the first message comprising first information; or the first network element can receive a first message from other devices, which is not limited herein. Alternatively, the first network element can receive a first message and first information from the AF, or the first network element can receive a first message and first information from other devices, which is not limited herein. Here, the first message can also be understood as a service request.

[0190] It should be noted that the first information can be sent together with the first message to the first network element. The first information and the first message can also be sent separately to the first network element, wherein the first message can be sent to the first network element first, and then the first information is sent to the first network element; or the first information can be sent to the first network element first, and then the first message is sent to the first network element; or the first information and the first message can be sent to the first network element at the same time, which is not limited here.

[0191] Exemplarily, the AF can send a first message (such as an A-IoT request) of an Internet of Things service (such as an A-IoT service) to the first network element, where the first message can be considered as a structured data packet (such as an IP data packet, a MAC data packet). The protocol adopted by the structured data packet is a protocol that can be understood by 3GPP, that is, the core network can identify it. At this time, the first information can be carried in the packet header (such as the GTP-U message header) of the data packet.

[0192] As shown in FIG. 6A, in the GTP-U packet format, the A-IoT request (that is, the first message) sent by the AF can be located in the T-PDU, and the first information can be located in the GTP-U Header (that is, the GTP-U message header). Wherein, the T-PDU and the GTP-U Header are collectively referred to as the G-PDU, and the format also includes PDU / IP and other data information. It should be noted that GTP-U is the abbreviation of GPRS Tunneling Protocol-User Plane, which is a user data transmission protocol used in general packet radio service (GPRS) network. GTP-U is a protocol for establishing a tunnel in the user plane, which can transmit IP datagrams from one GPRS support node to another GPRS support node, thereby realizing user data transmission in the GPRS network.

[0193] Wherein, the identifier of the AF includes but is not limited to one or more of the following: the URL of the AF, the IP address of the AF, the MAC address of the AF, the LAN address of the AF, the port information of the AF, or the ID of the AF.

[0194] The service type includes but is not limited to one or more of the following: inventory, command, or registration. Wherein, the command includes one or more of the following: read, write, lock, disable / kill, and enable.

[0195] The service object includes a group of terminal devices or a single terminal device.

[0196] The priority of the first message includes, but is not limited to, "high", "higher", "ordinary", etc.

[0197] The terminal device type includes type A and type B, type A is used to indicate a terminal device with extremely low power consumption and / or extremely low complexity (such as "goods label"), and type B is used to indicate a terminal device with low power consumption and / or low complexity (such as "sensor").

[0198] The first service time budget can be the time length from the start of receiving the first message to the reception of the response message of the last first message; or, the time length from the start of receiving the first message to the reception of the response message of the last first message and returning to the AF; or, the time length from the start of receiving the first message to the reception of the response message of the first message.

[0199] The destination network address refers to the network address of the receiving end, and the network address of the terminal device can be considered as the network address of the Internet of Things device (such as A-IoT device).

[0200] Further, after the first network element receives the data packet (i.e. the first message), it only needs to parse the packet header (such as GTP-U message header) of the data packet to obtain the first information, so as to determine the first identifier (such as QoS-like ID) and / or the second information according to the first information. Exemplarily, the specific rule of the first network element for detecting the data packet (i.e. the rule for determining the first identifier according to the first information) is as follows:

[0201] (1) The identifier of the AF: that is, the first network element can determine the first identifier according to the identifier of the AF.

[0202] (2) The identifier of the AF + service type: that is, the first network element can determine the first identifier according to the identifier of the AF and the service type.

[0203] (3) The identifier of the AF + the priority of the first message (request priority): that is, the first network element can determine the first identifier according to the identifier of the AF and the priority of the first message (request priority).

[0204] (4) The identifier of the AF + terminal device type: that is, the first network element can determine the first identifier according to the identifier of the AF and the terminal device type.

[0205] Further, since the SMF configures the association between the first identifier and the second information to the first network element in advance, the first network element can determine the second information associated with the first identifier through the association after determining the first identifier. Alternatively, it can also be understood that the first network element determines the second information according to the first information.

[0206] Exemplarily, the association can refer to Table 2 as shown in the table. The first identifier can be referred to as a QoS-like ID, and the second information includes the QoS-like indicators mentioned above: the priority corresponding to the Internet of Things service (such as the priority corresponding to the A-IoT service), the resource type, the service time budget (i.e., the second service time budget), the size of the uplink data packet (Device UL Packet Size), and the uplink and / or downlink rate size. Among them, the service time budget, the size of the uplink data packet, and the uplink and / or downlink rate size are optional.

[0207] The priority corresponding to the Internet of Things service includes but is not limited to one or more of the following: the priority of the AF, the priority of the service type, the priority of the first message, or the priority of the terminal device type.

[0208] The resource type can be a guaranteed bit rate (GBR) provided for the first message of the Internet of Things service, or a non-guaranteed bit rate (Non-GBR) provided for the first message of the Internet of Things service.

[0209] The service time budget (i.e., the second service time budget) can be the time length from the start of receiving the first message to the reception of the response message of the last first message; or the time length from the start of receiving the first message to the reception of the response message of the last first message and returning to the AF; or the time length from the start of receiving the first message to the reception of the response message of the first message.

[0210] The size of the uplink data packet refers to the estimation of the AF for the size of the data packet responding to the terminal device (such as the A-IoT device), which can be used for resource allocation of the base station and UPF, traffic processing action guarantee when the uplink A-IoT data is transmitted in the network. When the service object is a terminal device group, the size of the uplink data packet is the sum of the sizes of the uplink data packets of all terminal devices in the terminal device group, or the size of the uplink data packet of a single terminal device in the terminal device group.

[0211] The uplink rate size refers to the data transmission rate from the terminal device to the network, and the downlink rate size refers to the data transmission rate from the network to the terminal device.

[0212] For example, when the resource type is Non-GBR by default, the priority corresponding to the IoT service is high, the service time budget is 100s, the size of the uplink data packet is 800 bits, and the uplink and / or downlink rate size is 50 kbps when the QoS-like ID is 1; when the QoS-like ID is 2, the priority corresponding to the IoT service is higher, the service time budget is 100s, the size of the uplink data packet is 500 bits, and the uplink and / or downlink rate size is 100 Mbps; when the QoS-like ID is 3, the priority corresponding to the IoT service is ordinary, the service time budget is 200s, the size of the uplink data packet is not limited, and the uplink and / or downlink rate size is not limited; when the QoS-like ID is 4, the priority corresponding to the IoT service is ordinary, the service time budget is not limited, the size of the uplink data packet is not limited, and the uplink and / or downlink rate size is not limited.

[0213] Table 2

[0214] S503, the first network element performs a traffic processing action on the first message based on the second information.

[0215] Optionally, before receiving the first message, or, receiving the first message and the first information, the method further comprises: receiving first rule information from the SMF, the first rule information comprising first indication information, the first indication information being used to indicate the traffic processing action.

[0216] It can be understood that, before the first network element receives the first message, or, the first network element receives the first message and the first information, the SMF will pre-configure the first network element with the first rule information, which can be considered as a packet detection rule (i.e., PDR(s)) issued by the SMF, and the PDR(s) contains relevant instructions (i.e., the first indication information) for processing data packets, which are used to indicate specific traffic processing actions (including forwarding action rules (i.e., traffic forwarding), QoS-like execution rules, etc.). After the first network element receives the data packet (i.e., the first message) from the AF, it identifies the packet forwarding control protocol (PFCP) session corresponding to the data packet, finds the PDR matching the data packet in the packet detection rule (i.e., PDR(s)) configured for this PFCP session. If there are multiple PDRs that match, a PDR with the highest priority is selected to detect the data packet, and then the data packet is processed according to the requirements of the second information, i.e., the traffic processing action is performed, and finally the data packet is sent out of the user plane network element.

[0217] Exemplarily, assuming that the first network element determines the QoS-like ID (i.e., the first identifier) as 1, according to the association relationship described in Table 2 above, it can be known that when the QoS-like ID is 1, the associated second information includes that the priority corresponding to the Internet of Things service is high, the service time budget is 100s, the size of the uplink data packet fed back by the device is 800 bits, and the uplink and / or downlink rate size is 50kbps. The first network element identifies the PFCP session corresponding to the received data packet (i.e., the first message), finds the rule matched with the data packet in the first rule information configured for the PFCP session. If there are multiple matched rules, a rule with the highest priority is selected to detect the data packet, and then the data packet is processed according to the requirements of the second information, i.e., a traffic processing action is performed, and finally the data packet is sent out of the user plane network element, so as to realize the quality of service guarantee for the Internet of Things service.

[0218] S504, the first network element sends the first identifier and / or the second information to the access network device. Correspondingly, the access network device receives the first identifier and / or the second information from the first network element.

[0219] In the embodiment of the present application, after the first network element determines the first identifier and / or the second information, the first network element can further send a data packet to the access network device, where the data packet can also be considered as a structured data packet. At this time, the first identifier and / or the second information can be carried in the packet header (such as the GTP-U message header) of the data packet. The access network device only needs to parse the packet header of the data packet to obtain the first identifier and / or the second information. Specifically, the first identifier and / or the second information can be located in the field of the QoS flow ID in the existing scheme, or can be located in the spare field of the GTP-U message header of the DL PDU session information type (for reference, see the protocol [TS 38.415]), which is not limited here.

[0220] Further, since the SMF will also pre-configure the access network device with the association relationship between the first identifier and the second information, after the access network device obtains the first identifier, the access network device can determine the second information associated with the first identifier through the association relationship. Exemplarily, the association relationship can refer to Table 2 above, which is not described here.

[0221] S505, the access network device performs a resource allocation action and / or a traffic processing action based on the second information.

[0222] Optionally, before the access network device receives the first identifier from the first network element, the method further comprises: the access network device receiving a configuration file (i.e., a first configuration file) from the SMF, the first configuration file including the first identifier and second indication information, the second indication information being used to indicate resource allocation actions and / or traffic processing actions.

[0223] It can be understood that, before the access network device receives the first identifier from the first network element, the SMF will pre-configure the first configuration file to the access network device through the AMF, where the first configuration file can be considered as a QoS-like configuration file (profile) issued by the SMF, including the first identifier and second indication information, where the second indication information is used to indicate specific resource allocation actions (including resource allocation rules, etc.) and / or traffic processing actions (including forwarding action rules (i.e., traffic forwarding), QoS-like execution rules, etc.). After the access network device receives the data packet, the first identifier can be used to find the first configuration file, and the data packet is processed according to the requirement of the second information, i.e., the traffic processing actions are performed.

[0224] If the UP transmission scheme adopts the architecture of topology 1, the subsequent access network device also needs to send the data packet to the Internet of Things device (i.e., A-IoT device), i.e., step S506 is performed; if the UP transmission scheme adopts the architecture of topology 2, the subsequent access network device also needs to send the data packet to the UE (i.e., the intermediate node), i.e., steps S507 and S508 are performed.

[0225] Exemplarily, assuming that the QoS-like ID (i.e., the first identifier) obtained by the access network device is 1, according to the association relationship described in Table 2 above, it can be known that when the QoS-like ID is 1, the corresponding second information includes: the priority of the Internet of Things service is high, the service time budget is 100s, the size of the uplink data packet fed back by the device is 800 bits, and the uplink and / or downlink rate size is 50kbps. The access network device can find the first configuration file through the first identifier, and the second indication information in the first configuration file indicates specific resource allocation actions (including resource allocation rules, etc.) and / or traffic processing actions (including forwarding action rules (i.e., traffic forwarding), QoS-like execution rules, etc.). The access network device can process the data packet according to the requirement of the second information, i.e., perform resource allocation actions and / or traffic processing actions, so as to realize the quality of service guarantee for the Internet of Things service.

[0226] S506, the access network device sends the first identifier and / or the second information to the Internet of Things device. Correspondingly, the Internet of Things device receives the first identifier and / or the second information from the access network device.

[0227] In the embodiments of the present application, it is assumed that the UP transmission scheme adopts the architecture of topology 1, and after the access network device obtains the first identifier and / or the second information, the access network device can further send a data packet to the Internet of Things device, and the first identifier and / or the second information can be carried in the packet header of the data packet.

[0228] Since the SMF also pre-configures the association relationship between the first identifier and the second information to the Internet of Things device, after the Internet of Things device obtains the first identifier, the Internet of Things device can determine the second information associated with the first identifier through the association relationship. For example, the association relationship can refer to Table 2, which is not repeated here. Subsequently, the Internet of Things device can perform a traffic processing action according to the second information.

[0229] S507, the access network device sends the first identifier and / or the second information to the UE. Correspondingly, the UE receives the first identifier and / or the second information from the access network device.

[0230] In the embodiments of the present application, it is assumed that the UP transmission scheme adopts the architecture of topology 2, and after the access network device obtains the first identifier and / or the second information, the access network device can further send a data packet to the UE, which can also be regarded as a structured data packet. At this time, the first identifier and / or the second information can be carried in the packet header (such as the GTP-U message header) of the data packet. Subsequently, the UE only needs to parse the packet header of the data packet to obtain the first identifier and / or the second information. Specifically, the first identifier can be located in the field of the existing scheme QoS flow ID, or in the spare field of the GTP-U message header of the DL PDU session information type (for details, please refer to the protocol [TS 38.415]), which is not limited here.

[0231] Further, since the SMF also pre-configures the association relationship between the first identifier and the second information to the UE, after the terminal device obtains the first identifier, the terminal device can determine the second information associated with the first identifier through the association relationship. For example, the association relationship can refer to Table 2, which is not repeated here.

[0232] S508, the UE performs a resource allocation action and / or a traffic processing action based on the second information.

[0233] Optionally, before the UE receives the first identifier and / or the second information from the access network device, the method further includes: the UE receives a configuration file (i.e., a second configuration file) from the SMF, the second configuration file including the first identifier and second indication information, the second indication information being used to indicate the resource allocation action and / or the traffic processing action. It should be noted that the second configuration file and the first configuration file mentioned above can be collectively referred to as a configuration file.

[0234] It can be understood that, before the UE receives the first identifier and / or the second information from the access network device, the SMF will pre-configure the second configuration file to the UE through the AMF and the access network device, where the second configuration file can be considered as a QoS-like rule issued by the SMF, including the first identifier and the second indication information, where the second indication information is used to indicate specific resource allocation actions (including resource allocation rules, etc.) and / or traffic processing actions (including forwarding action rules (i.e. traffic forwarding), QoS-like execution rules, etc.). After the UE receives the data packet from the access network device, the second configuration file can be found through the first identifier, and the data packet is processed according to the requirement of the second information, that is, the resource allocation actions and / or the traffic processing actions are executed, and finally the data packet is sent to the IoT device.

[0235] Exemplarily, assuming that the QoS-like ID (i.e. the first identifier) obtained by the UE is 1, according to the association relationship described in the above table 2, it can be known that when the QoS-like ID is 1, the corresponding second information includes that the priority of the IoT service is high, the service time budget is 100s, the size of the uplink data packet fed back by the device is 800 bits, and the uplink and / or downlink rate size is 50kbps. The UE can find the second configuration file through the first identifier, and the second indication information in the second configuration file indicates specific resource allocation actions (including resource allocation rules, etc.) and / or traffic processing actions (including forwarding action rules (i.e. traffic forwarding), QoS-like execution rules, etc.). The UE can process the data packet according to the requirement of the second information, that is, the resource allocation actions and / or the traffic processing actions are executed, so as to realize the service quality guarantee of the IoT service.

[0236] S509, the UE sends the first identifier and / or the second information to the IoT device. Correspondingly, the IoT device receives the first identifier and / or the second information from the UE.

[0237] In the embodiment of the present application, assuming that the UP transmission scheme adopts the architecture of topology 2, after the UE obtains the first identifier and / or the second information, the UE can further send a data packet to the IoT device, where the first identifier and / or the second information can be carried in the data packet. Since the SMF will also pre-configure the association relationship between the first identifier and the second information to the IoT device, after the IoT device obtains the first identifier, the second information associated with the first identifier can be determined through the association relationship. Exemplarily, the association relationship can refer to the above table 2, which is not described herein. Subsequently, the IoT device can execute the traffic processing actions according to the second information.

[0238] The service quality guarantee method proposed in the embodiment of the present application will be described below by using a specific example:

[0239] As shown in FIG. 6B, assuming that the first network element is a UPF, the UP transmission scheme adopts the architecture of topology 2. The AF sends an A-IoT request (i.e., the first message) to the UPF, which can be regarded as a data packet, and the packet header of the data packet carries first information, which includes one or more of the following: the identity of the AF, the service type, the service object, the priority of the first message, the terminal device type, the first service time budget, the destination network address, and the network address of the terminal device.

[0240] The UPF can obtain the first information by parsing the packet header of the data packet. According to the rules for detecting data packets shown in FIG. 6B, the UPF can determine the first identity (i.e., QoS-like ID) according to the first information. The rules for detecting data packets by the UPF can be to determine the first identity according to the identity of the AF; or to determine the first identity according to the identity of the AF and the service type; or to determine the first identity according to the identity of the AF and the priority of the first message (request priority); or to determine the first identity according to the identity of the AF and the terminal device type (e.g., A-IoT device type).

[0241] For example, assuming that the first information is the identity of AF1, the UPF determines that QoS-like ID = 1 according to the identity of AF1. When QoS-like ID = 1, according to the pre-issued association relationship between QoS-like ID and the second information, it can be determined that the associated second information includes: the priority of the Internet of Things service is high, the service time budget is 100s, the size of the uplink data packet is 800 bits, and the uplink and / or downlink rate size is 50kbps. In the case of network resource shortage and limitation, the UPF further finds a rule matching the data packet according to the first rule information (such as PDR(s)) pre-issued by the SMF. If there are multiple matching rules, a rule with the highest priority is selected to detect the data packet, and then the data packet is processed according to the requirements of the second information, i.e., the traffic processing action is performed, and finally the data packet is sent out of the user plane network element, thereby realizing the quality of service guarantee for the Internet of Things service.

[0242] Further, the UPF sends a third message to the access network device, which can be considered as a data packet, and the packet header of the data packet carries the first identifier (i.e., the QoS-like ID). The access network device can parse the packet header of the data packet to obtain the QoS-like ID, and at this time, the QoS-like ID = 1. According to the pre-deployed association relationship between the QoS-like ID and the second information, it can be determined that the associated second information includes: the priority corresponding to all A-IoT services of the AF1 is high, the service time budget is 100s, the size of the uplink data packet is 800 bits, and the uplink and / or downlink rate size is 50kbps. In the case that the network side resource is tight and limited, the access network device further finds the first configuration file (such as the QoS-like configuration file) pre-deployed by the SMF according to the first identifier, and the second indication information in the first configuration file indicates specific resource allocation actions (including resource allocation rules, etc.) and / or traffic processing actions (including forwarding action rules (i.e., traffic forwarding), QoS-like execution rules, etc.). The access network device can process the data packet according to the requirement of the second information, that is, perform the resource allocation action and / or the traffic processing action, so as to realize the quality of service guarantee for the Internet of Things service.

[0243] Further, the access network device sends a fourth message to the UE, which can be considered as a data packet, and the packet header of the data packet carries the first identifier (i.e., the QoS-like ID). The UE can parse the packet header of the data packet to obtain the QoS-like ID, and at this time, the QoS-like ID = 1. According to the pre-deployed association relationship between the QoS-like ID and the second information, it can be determined that the associated second information includes: the priority corresponding to all A-IoT services of the AF1 is high, the service time budget is 100s, the size of the uplink data packet is 800 bits, and the uplink and / or downlink rate size is 50kbps. In the case that the network side resource is tight and limited, the UE further finds the second configuration file pre-deployed by the SMF through the first identifier, and the third indication information in the second configuration file indicates specific resource allocation actions (including resource allocation rules, etc.) and / or traffic processing actions (including forwarding action rules (i.e., traffic forwarding), QoS-like execution rules, etc.). The UE can process the data packet according to the requirement of the second information, that is, perform the resource allocation action and / or the traffic processing action, so as to realize the quality of service guarantee for the Internet of Things service.

[0244] Furthermore, the UE sends a fifth message to the IoT device, which carries the first identifier. Since the SMF also pre-configures the association between the first identifier and the second information for the IoT device, the IoT device, after obtaining the first identifier, can determine the second information associated with the first identifier through this association. For example, this association can be referred to in Table 2 above, and will not be elaborated here. Subsequently, the IoT device can perform traffic processing actions based on the second information, thereby achieving quality of service assurance for the IoT service.

[0245] Similarly, assuming the first piece of information is the identifier of AF2, the UPF can also determine the QoS-like ID based on the identifier of AF2. Subsequently, the UPF, access network equipment, UE and IoT equipment can also perform traffic processing actions based on the QoS-like ID. For specific implementation methods, please refer to the above description, which will not be elaborated here.

[0246] For example, assuming the first information is the identifier and service type of AF1, where the identifier of AF1 is 1 and the service type is read, the UPF determines the QoS-like ID = 1 based on the identifier and service type of AF1. When the QoS-like ID = 1, based on the association between the pre-issued QoS-like ID and the second information, the associated information can be determined as follows: all A-IoT services of AF1 have a high priority, a service time budget of 100s, an uplink data packet size of 800 bits, and an uplink and / or downlink rate of 50kbps. When network resources are scarce and limited, the UPF further finds a rule matching the data packet based on the first rule information (such as PDR(s)) pre-issued by the SMF. If multiple rules match, the rule with the highest priority is selected to inspect the data packet, and then the data packet is processed according to the requirements of the second information, i.e., traffic processing is performed. Finally, the data packet is sent out of the user plane network element, thereby achieving service quality assurance for IoT services. Subsequently, access network devices, UEs, and IoT devices can also perform traffic processing actions based on QoS-like IDs. For specific implementation methods, please refer to the above description, which will not be elaborated here.

[0247] It can be seen that, based on the method described in FIG. 5, the first network element receives the first information, which includes one or more of the following: the identifier of the AF, the service type, the service object, the priority of the first message, the terminal device type, the first service time budget, the destination network address, and the network address of the terminal device. Then, the first network element can determine the first identifier (i.e., QoS-like ID) and / or the second information according to the first information. The first identifier here is associated with a new quality of service indicator defined for A-IoT services, such as the priority corresponding to the Internet of Things service, the resource type, the second service time budget, the size of the uplink data packet, the uplink and / or downlink rate size, etc. Each network node (i.e., UPF, access network device, UE, and Internet of Things device) on the subsequent UP transmission scheme path can perform traffic processing actions according to the second information, thereby facilitating the provision of quality of service guarantees for A-IoT services in the case of network resource shortage and limitation.

[0248] Method two: each network node on the UP path performs processing operations corresponding to the quality of service according to the QoS-like indicator (i.e., the third information).

[0249] FIG. 7 is a flow diagram of another quality of service guarantee method provided by an embodiment of the present application. As shown in FIG. 7, the quality of service guarantee method includes steps S701 and S702. Optionally, the quality of service guarantee method further includes steps S703-S707. The method execution subject shown in FIG. 7 can be the first network element (user plane network element, such as UPF), access network device, and terminal device mentioned above. Alternatively, the method execution subject shown in FIG. 7 can be a chip in the first network element, a chip in the access network device, or a chip in the terminal device, which is not limited in the embodiments of the present application. FIG. 7 takes the first network element, access network device, and terminal device as the method execution subject for example. Among them, the terminal device can include UE and Internet of Things devices (such as A-IoT devices), and the UE can be considered as an intermediate node.

[0250] It can be understood that, in the embodiments of the present application, the first network element, the access network device, the terminal device and the Internet of Things device are taken as examples of the execution subject of the interaction scenario, but the present application does not limit the execution subject of the interaction scenario. For example, the method executed by the first network element in the present application can also be implemented by a module (such as a circuit, a chip or a chip system, etc.) in the first network element, or a logical node, a logical module or software capable of realizing all or part of the functions of the first network element; the method executed by the access network device in the present application can also be implemented by a module (such as a circuit, a chip or a chip system, etc.) in the access network device, or a logical node, a logical module or software capable of realizing all or part of the functions of the access network device; the method executed by the terminal device in the present application can also be implemented by a communication / processing module in the terminal device or a circuit or chip (such as a modem chip (also known as a baseband chip), or a SoC chip / SIP chip containing a modem core, or a GPU / AI processor / ASIC) responsible for communication / processing functions in the terminal device.

[0251] S701, the first network element receives third information, the third information including one or more of the following: a priority corresponding to the Internet of Things service, a resource type, a second service time budget, a size of an uplink data packet, and an uplink and / or downlink rate size.

[0252] In the embodiments of the present application, the first network element can receive the third information from the AF, or can receive the third information from other devices, which is not limited here. Optionally, when the first network element receives the third information, the specific implementation manner can be that the first network element receives a sixth message of the Internet of Things service, and the sixth message includes the first information.

[0253] Taking the AF as an example, the AF can send a sixth message to the first network element, where the sixth message can be considered as an unstructured data packet (such as other data packets in addition to IP data packets and MAC data packets). The protocol adopted by the unstructured data packet is a protocol that cannot be understood by 3GPP, that is, the core network cannot identify it. At this time, a tunnel of the GTP-U protocol needs to be established between the AF and the first network element, the data packet is encapsulated by using the GTP-U protocol, and the third information is carried in the packet header (such as the GTP-U message header) of the data packet.

[0254] The third information includes the new quality of service indicators defined for the A-IoT service, such as the priority of the A-IoT service, the resource type, the service time budget, the size of the uplink data packet, and the uplink and / or downlink rate size. Of course, the third information can specifically include the identifiers of the quality of service indicators, such as the identifiers of the priority of the A-IoT service, the identifiers of the resource type, the identifiers of the service time budget, the identifiers of the size of the uplink data packet, and the identifiers of the uplink and / or downlink rate size, without limitation.

[0255] The priority of the A-IoT service includes but is not limited to one or more of the following: the priority of the AF, the priority of the service type, the priority of the first message, or the priority of the terminal device type.

[0256] The resource type can be a guaranteed bit rate (GBR) provided for the first message of the A-IoT service, or a non-guaranteed bit rate (Non-GBR) provided for the first message of the A-IoT service.

[0257] The service time budget (i.e., the second service time budget) can be the time length from the start of receiving the first message to the reception of the response message of the last first message, or the time length from the start of receiving the first message to the reception of the response message of the last first message and returning to the AF, or the time length from the start of receiving the first message to the reception of the response message of the first message.

[0258] The size of the uplink data packet refers to the estimation of the AF on the size of the data packet in response to the terminal device (such as the A-IoT device), which can be used for resource allocation of the base station and the UPF, traffic processing action guarantee when the uplink A-IoT data is transmitted in the network. When the service object is a terminal device group, the size of the uplink data packet is the sum of the sizes of the uplink data packets of all terminal devices in the terminal device group, or the size of the uplink data packet of a single terminal device in the terminal device group.

[0259] The uplink rate size refers to the data transmission rate from the terminal device to the network, and the downlink rate size refers to the data transmission rate from the network to the terminal device.

[0260] S702, the first network element performs a traffic processing action based on the third information.

[0261] In the embodiments of the present application, after the first network element receives the data packet (i.e., the sixth message), in the case that the network side resource is limited and scarce, the third information can be obtained by analyzing the packet header (such as the GTP-U message header) of the data packet, so that the traffic processing action can be directly performed according to the third information, for example, the forwarding action rule (i.e., traffic forwarding), the QoS-like execution rule, etc., which are not limited herein.

[0262] S703, the first network element sends the third information to the access network device. Correspondingly, the access network device receives the third information from the first network element.

[0263] In the embodiments of the present application, after the first network element obtains the third information, the first network element further sends the data packet to the access network device (i.e., the seventh message), at this time, the third information can also be carried in the packet header (such as the GTP-U message header) of the data packet. The access network device only needs to analyze the packet header of the data packet to obtain the third information.

[0264] Specifically, the third information can be located in the extensible message header type reserved in the GTP-U message header, such as octets12; or a new type of GTP-U packet header can be added to carry the third information which needs to be delivered to the access network device.

[0265] S704, the access network device performs the traffic processing action based on the third information.

[0266] In the embodiments of the present application, after the access network device receives the data packet (i.e., the seventh message) from the first network element, in the case that the network side resource is limited and scarce, the third information can be obtained by analyzing the packet header (such as the GTP-U message header) of the data packet, so that the traffic processing action can be directly performed according to the third information, for example, the forwarding action rule (i.e., traffic forwarding), the QoS-like execution rule, etc., which are not limited herein.

[0267] If the UP transmission scheme adopts the architecture of topology 1, the subsequent access network device also needs to send the data packet to the Internet of Things device (i.e., A-IoT device), that is, step S705 is performed; if the UP transmission scheme adopts the architecture of topology 2, the subsequent access network device also needs to send the data packet to the UE (i.e., the intermediate node), that is, steps S706 and S707 are performed.

[0268] S705, the access network device sends the third information to the Internet of Things device. Correspondingly, the Internet of Things device receives the third information from the access network device.

[0269] In the embodiments of the present application, after the access network device obtains the third information, the access network device further sends a data packet (i.e., an eighth message) to the IoT device, and at this time, the third information can also be carried in the packet header (such as a GTP-U packet header) of the data packet. The IoT device only needs to analyze the packet header of the data packet to obtain the third information. Subsequently, the IoT device can directly perform a traffic processing action according to the third information, for example, a forwarding action rule (i.e., traffic forwarding), a QoS-like execution rule, and the like, which are not limited herein.

[0270] Specifically, the third information can be located in an extensible packet header type (such as octets 12) reserved in the GTP-U packet header, or a new type of GTP-U packet header can be added to carry the third information that needs to be delivered to the IoT device.

[0271] S706, the access network device sends the third information to the UE. Correspondingly, the UE receives the third information from the access network device.

[0272] In the embodiments of the present application, after the access network device obtains the third information, the access network device further sends a data packet (i.e., an eighth message) to the IoT device, and at this time, the third information can also be carried in the packet header (such as a GTP-U packet header) of the data packet. The IoT device only needs to analyze the packet header of the data packet to obtain the third information. Subsequently, the IoT device can directly perform a traffic processing action according to the third information, for example, a forwarding action rule (i.e., traffic forwarding), a QoS-like execution rule, and the like, which are not limited herein.

[0273] S707, the UE sends the third information to the IoT device. Correspondingly, the IoT device receives the third information from the UE.

[0274] In the embodiments of the present application, after the access network device obtains the third information, the access network device further sends a data packet (i.e., an eighth message) to the IoT device, and at this time, the third information can also be carried in the packet header (such as a GTP-U packet header) of the data packet. The IoT device only needs to analyze the packet header of the data packet to obtain the third information. Subsequently, the IoT device can directly perform a traffic processing action according to the third information, for example, a forwarding action rule (i.e., traffic forwarding), a QoS-like execution rule, and the like, which are not limited herein.

[0275] It can be seen that, based on the method described in FIG. 7, the first network element receives third information including a new service quality indicator (such as a QoS-like indicator) defined for the Internet of Things service, which can specifically include one or more of the following: a priority corresponding to the Internet of Things service, a resource type, a second service time budget, a size of an uplink data packet, and an uplink and / or downlink rate size. Each network node (i.e., UPF, access network device, UE, and Internet of Things device) on the subsequent UP transmission scheme path can directly perform traffic processing actions according to these service quality indicators, thereby facilitating the provision of service quality guarantees for A-IoT in the case of network-side resource scarcity and limitation, while also reducing the signaling interaction overhead.

[0276] II. For CP transmission scheme

[0277] FIG. 8 is a flow diagram of another service quality guarantee method according to an embodiment of the present application. As shown in FIG. 8, the service quality guarantee method includes the following steps S801-S803. The method execution subject shown in FIG. 8 can be the second network element (such as the A-IoT NF network element mentioned above) and the first AMF mentioned above. Alternatively, the method execution subject shown in FIG. 8 can be a chip in the second network element and a chip in the first AMF, which is not limited in the present application. FIG. 8 takes the second network element and the first AMF as the method execution subject as an example for illustration.

[0278] It can be understood that the second network element and the first AMF are taken as the execution subject of the interaction in the embodiments of the present application as an example for illustration, but the present application does not limit the execution subject of the interaction. For example, the method executed by the second network element in the present application can also be implemented by a module (such as a circuit, a chip, or a chip system, etc.) in the second network element, or a logical node, a logical module, or software capable of realizing all or part of the function of the second network element; the method executed by the first AMF in the present application can also be implemented by a module (such as a circuit, a chip, or a chip system, etc.) in the first AMF, or a logical node, a logical module, or software capable of realizing all or part of the function of the first AMF.

[0279] S801, the second network element receives a second message including fourth information; or receives the second message and the fourth information; wherein the fourth information includes one or more of the following: an identifier of the AF, a service type, a terminal device type, or a priority of the second message.

[0280] In the embodiments of the present application, the second network element can receive a second message from the AF, the second message comprising the fourth information; or the second network element can receive a second message from another device, which is not limited herein. Alternatively, the second network element can receive the second message and the fourth information from the AF, or the second network element can receive the second message and the fourth information from another device, which is not limited herein. Here, the second message can also be understood as a service request.

[0281] It should be noted that the fourth information can be sent to the second network element together with the second message. Alternatively, the fourth information and the second message can be sent to the second network element separately, wherein the second message can be sent to the second network element first, and then the fourth information can be sent to the second network element; or the fourth information can be sent to the second network element first, and then the second message can be sent to the second network element; or the fourth information and the second message can be sent to the second network element at the same time, which is not limited herein.

[0282] The identifier of the AF includes, but is not limited to, one or more of the following: a URL of the AF, an IP address of the AF, a MAC address of the AF, a LAN address of the AF, port information of the AF, or an ID of the AF.

[0283] The service type includes, but is not limited to, one or more of the following: inventory, command, or registration. The command includes one or more of the following: read, write, lock, disable / kill, and enable.

[0284] The priority of the second message includes, but is not limited to, "high", "higher", "normal", and the like.

[0285] The terminal device type includes type A and type B, wherein type A is used to indicate a terminal device with extremely low power consumption and / or extremely low complexity (such as a "goods tag"), and type B is used to indicate a terminal device with low power consumption and / or low complexity (such as a "sensor").

[0286] For example, the AF can send a second message to the NEF, wherein the second message carries the fourth information. After the NEF successfully authenticates, the NEF forwards the second message to the second network element.

[0287] If the fourth information includes the identifier of the AF and the service type, or the fourth information includes the identifier of the AF and the terminal device type, the following step S802 can be performed; if the fourth information includes the identifier of the AF and the priority of the second message, the following step S803 can be performed.

[0288] S802, if the application subscription information corresponding to the AF includes the priority of the service type or the priority of the terminal device type, the priority of the service type or the priority of the terminal device type is sent to the first AMF.

[0289] In the embodiments of the present application, the fourth information includes the identifier of the AF and the service type, or the fourth information includes the identifier of the AF and the terminal device type.

[0290] After the NEF authenticates, the second message is forwarded to a second network element (such as the A-IoT NF network element mentioned above). After the second network element receives the second message, the UDM / PCF is further requested to query whether the priority of the service type or the priority of the terminal device type is included in the application subscription information corresponding to the AF according to the identifier of the AF. If so, the second network element sends the priority of the service type or the priority of the terminal device type to the first AMF, so that each network node (such as the second network element, the first AMF, the access network device, the UE (intermediate node), and the Internet of Things device) on the subsequent CP transmission scheme path can perform traffic processing actions according to the priority of the service type or the priority of the terminal device type.

[0291] S803, if the AF is successfully authenticated, the second network element sends the priority of the service request to the first AMF.

[0292] In the embodiments of the present application, the fourth information includes the identifier of the AF and the priority of the service request.

[0293] After the NEF authenticates, the second message is forwarded to a second network element (such as the A-IoT NF network element mentioned above). After the second network element receives the second message, the AF is authenticated (specifically, whether the AF has the capability of indicating the priority of the second message is verified). If the second network element successfully authenticates the AF, the priority of the second message is sent to the first AMF, so that each network node (such as the second network element, the first AMF, the access network device, the UE (intermediate node), and the Internet of Things device) on the subsequent CP transmission scheme path can perform traffic processing actions according to the priority of the second message.

[0294] In a possible implementation, in the application subscription information corresponding to the AF, the priority corresponding to the service type or the priority corresponding to the Internet of Things device type is included, or in the case that the AF is successfully authenticated, the second network element needs to request the address information of the AMF from the NRF, and the method further includes the following steps s11 and s12.

[0295] s11, the second network element sends a first request to the NRF, the first request being used for requesting address information of the AMF, the first request comprising fifth information used for indicating a load requirement of the AMF. Correspondingly, the NRF receives the first request from the second network element.

[0296] s12, the NRF sends the address information of the first AMF satisfying the load requirement to the second network element. Correspondingly, the second network element receives the address information of the first AMF from the NRF.

[0297] It can be understood that the priority corresponding to the service type or the priority corresponding to the Internet of Things device type is included in the application subscription information corresponding to the AF, or, in the case that the AF is successfully authenticated, the second network element requests the address information of the AMF from the NRF while carrying the fifth information used for indicating the load requirement (such as NF load indication) of the AMF. At this time, the NRF finds the first AMF satisfying the load requirement and feeds back the address information of the first AMF to the second network element, so as to facilitate the selection of the AMF network element with appropriate load to complete the communication. For example, assuming that the load requirement of the AMF is the lowest load, the NRF finds the AMF (i.e., the first AMF) with the lowest load and feeds back the address information of the first AMF to the second network element.

[0298] Subsequently, each network node (such as the second network element, the first AMF, the access network device, the UE (intermediate node), and the Internet of Things device) on the CP transmission scheme path can perform traffic processing actions according to the priority of the service type, the priority of the terminal device type, or the priority of the service request.

[0299] It can be seen that based on the method described in FIG. 8, the first network element receives the fourth information comprising one or more of the following: the identifier of the AF, the service type, the Internet of Things device type, or the priority of the service request. If the priority of the service type or the priority of the terminal device type is included in the application subscription information corresponding to the AF, the second network element sends the priority of the service type or the priority of the terminal device type to the first AMF; or, if the AF is successfully authenticated, the second network element sends the priority of the second message to the first AMF. Here, the first AMF can be an AMF satisfying the load requirement expected by the second network element, so as to facilitate the selection of the AMF network element with appropriate load to complete the communication. Each network node (such as the second network element, the first AMF, the access network device, the UE (intermediate node), and the Internet of Things device) on the CP transmission scheme path can perform traffic processing actions according to these priorities, reduce the congestion of network forwarding processing, and realize the guarantee of service quality.

[0300] The following will introduce the apparatus provided by the embodiments of the present application.

[0301] The device is divided into functional modules according to the method embodiments, for example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The integrated module can be realized in the form of hardware or in the form of a software functional module. It should be noted that the division of the modules in the present application is illustrative, and is only a logical function division. In actual implementation, there can be another division manner. The device of the embodiments of the present application will be described in detail below with reference to FIGS. 9-11.

[0302] FIG. 9 is a structural schematic diagram of a communication device according to an embodiment of the present application. As shown in FIG. 9, the communication device includes a processing module 901 and a transceiver module 902. The transceiver module 902 can realize corresponding communication functions, and the processing module 901 is configured to realize corresponding processing functions. The transceiver module 902 can also be referred to as an interface, a communication interface, or a communication module, etc.

[0303] In some embodiments of the present application, the communication device can be used to perform the actions performed by the first network element in the above method embodiments. At this time, the communication device can be the first network element itself or a chip or functional module configured in the first network element, etc. The transceiver module 902 is configured to perform the transceiving related operations of the first network element in the above method embodiments, and the processing module 901 is configured to perform the processing related operations of the first network element in the above method embodiments.

[0304] For example, the transceiver module 902 can be configured to: receive a first message, the first message including first information; or receive a first message and first information.

[0305] The processing module 901 can be configured to: determine a first identifier and / or second information based on the first information, the first identifier being associated with the second information.

[0306] The processing module 901 can be further configured to: perform a traffic processing action on the first message based on the second information.

[0307] For example, the first information includes one or more of the following: an identifier of the AF, a service type, a service object, a priority of the first message, a terminal device type, a first service time budget, a destination network address, and a network address of the terminal device. The second information includes one or more of the following: a priority corresponding to the Internet of Things service, a resource type, a second service time budget, a size of an uplink data packet, and an uplink and / or downlink rate size.

[0308] For example, the identifier of the AF includes one or more of the following: a URL of the AF, an IP address of the AF, a MAC address of the AF, a LAN address of the AF, port information of the AF, or an ID of the AF.

[0309] As another example, the service type includes one or more of: inventory, command, or registration.

[0310] As another example, the service object includes a group of terminal devices or a single terminal device.

[0311] As another example, when the service object is a group of terminal devices, the size of the uplink data packet is a sum of sizes of uplink data packets of all terminal devices in the group of terminal devices, or a size of an uplink data packet of a single terminal device in the group of terminal devices.

[0312] As another example, the terminal device type includes Type A and Type B, Type A indicating a terminal device with very low power consumption and / or very low complexity, and Type B indicating a terminal device with low power consumption and / or low complexity.

[0313] As another example, the priority corresponding to the Internet of Things service includes one or more of: a priority of the AF, a priority of the service type, a priority of the first message, or a priority of the terminal device type.

[0314] As another example, the first service time budget or the second service time budget includes: a time length from when the first message is received to when a response message to the last first message is received; or, a time length from when the first message is received to when a response message to the last first message is received and returned to the AF; or, a time length from when the first message is received to when a response message to the first message is received.

[0315] As another example, the resource type includes: GBR or Non-GBR provided for the first message of the Internet of Things service.

[0316] As another example, before receiving the first message, or, before receiving the first message and the first information, the transceiver 902 can further be configured to: receive first rule information from the SMF, the first rule information including first indication information, the first indication information being used to indicate a traffic processing action.

[0317] As another example, the transceiver 902 can further be configured to: send the first identifier and / or the second information to the access network device.

[0318] In another embodiment of the application, the communication apparatus in Figure 9 can be configured to perform the actions of the access network device or the terminal device in the above method embodiments. The communication apparatus can be the access network device or the terminal device itself, or a chip or a functional module configured in the access network device or the terminal device. The transceiver module 902 is configured to perform the transceiving related operations of the access network device or the terminal device in the above method embodiments, and the processing module 901 is configured to perform the processing related operations of the access network device or the terminal device in the above method embodiments.

[0319] For example, the transceiver module 902 can be configured to: receive the first identifier and / or the second information, the first identifier being associated with the second information, the second information including one or more of the following: a priority corresponding to the IoT service, a resource type, a second service time budget, a size of the uplink data packet, an uplink and / or downlink rate size.

[0320] The processing module 901 can be configured to: perform a resource allocation action and / or a traffic processing action based on the second information.

[0321] For example, the priority corresponding to the IoT service includes one or more of the following: a priority of the AF, a priority of the service type, a priority of the first message, or a priority of the terminal device type.

[0322] For another example, the resource type includes: a GBR or a Non-GBR provided for the first message of the IoT service.

[0323] For another example, the second service time budget includes: a time length from the start of receiving the first message to the reception of the response message of the last first message; or, a time length from the start of receiving the first message to the reception of the response message of the last first message and returning to the AF; or, a time length from the start of receiving the first message to the reception of the response message of the first message.

[0324] For another example, when the service object is a terminal device group, the size of the uplink data packet is the sum of the sizes of the uplink data packets of all terminal devices in the terminal device group, or the size of the uplink data packet of a single terminal device in the terminal device group.

[0325] For another example, before receiving the first identifier and / or the second information, the transceiver module 902 can be further configured to: receive a configuration file from the SMF, the configuration file including the first identifier and second indication information, the second indication information being used to indicate the resource allocation action and / or the traffic processing action.

[0326] For another example, when the communication apparatus is the access network device, the transceiver module 902 can be further configured to: send the first identifier and / or the second information to the terminal device.

[0327] In another embodiment of the disclosure, the communication apparatus can be configured to perform the actions performed by the first network element or the access network device in the above method embodiments. In this case, the communication apparatus can be the first network element or the access network device itself, or a chip or a functional module configured in the first network element or the access network device. The transceiver module 902 is configured to perform the transceiver-related operations of the first network element or the access network device in the above method embodiments, and the processing module 901 is configured to perform the processing-related operations of the first network element or the access network device in the above method embodiments.

[0328] For example, the transceiver module 902 can be configured to receive third information, the third information including one or more of the following: a priority corresponding to the IoT service, a resource type, a second service time budget, a size of the uplink data packet, an uplink and / or downlink rate size.

[0329] The processing module 901 can be configured to perform a traffic processing action based on the third information.

[0330] For example, the priority corresponding to the IoT service includes one or more of the following: a priority of the AF, a priority of the service type, a priority of the first message, or a priority of the terminal device type.

[0331] For another example, the resource type includes GBR or Non-GBR provided for the first message of the IoT service.

[0332] For another example, the second service time budget includes: a time length from the start of receiving the first message to the reception of the response message of the last first message; or, a time length from the start of receiving the first message to the reception of the response message of the last first message and returning to the AF; or, a time length from the start of receiving the first message to the reception of the response message of the first message.

[0333] For another example, when the service object is a terminal device group, the size of the uplink data packet is the sum of the sizes of the uplink data packets of all terminal devices in the terminal device group, or the size of the uplink data packet of a single terminal device in the terminal device group.

[0334] For another example, the transceiver module 902 can be further configured to send the third information to the access network device or the terminal device. Specifically, when the communication apparatus is the first network element, the transceiver module 902 sends the third information to the access network device. When the communication apparatus is the access network device, the transceiver module 902 sends the third information to the terminal device.

[0335] Referring to FIG. 9, in some embodiments of the present disclosure, the communication apparatus can be configured to perform the actions performed by the terminal device in the method embodiments. The communication apparatus can be the terminal device itself or a chip or functional module configured in the terminal device. The transceiver module 902 is configured to perform the operations related to the transceiving of the terminal device in the method embodiments, and the processing module 901 is configured to perform the operations related to the processing of the terminal device in the method embodiments.

[0336] For example, the transceiver module 902 can be configured to receive third information, the third information comprising one or more of: a priority corresponding to the IoT service, a resource type, a second service time budget, a size of the uplink data packet, an uplink and / or downlink rate size.

[0337] The processing module 901 can be configured to perform a traffic processing action based on the third information.

[0338] For example, the priority corresponding to the IoT service comprises one or more of: a priority of the AF, a priority of the service type, a priority of the first message, or a priority of the terminal device type.

[0339] For another example, the resource type comprises: a GBR or a Non-GBR provided for the first message of the IoT service.

[0340] For another example, the second service time budget comprises: a time length from the start of receiving the first message to the reception of the response message of the last first message; or, a time length from the start of receiving the first message to the reception of the response message of the last first message and returning to the AF; or, a time length from the start of receiving the first message to the reception of the response message of the first message.

[0341] Referring to FIG. 9, in some embodiments of the present disclosure, the communication apparatus can be configured to perform the actions performed by the second network element in the method embodiments. The communication apparatus can be the second network element itself or a chip or functional module configured in the second network element. The transceiver module 902 is configured to perform the operations related to the transceiving of the second network element in the method embodiments, and the processing module 901 is configured to perform the operations related to the processing of the second network element in the method embodiments.

[0342] For example, the transceiver module 902 can be configured to receive a second message, the second message comprising fourth information; or, receive the second message and the fourth information; wherein the fourth information comprises one or more of: an identifier of the AF, a service type, a terminal device type, or a priority of the second message.

[0343] As an example, the identity of the AF comprises one or more of: a URL of the AF, an Internet Protocol (IP) address of the AF, a MAC address of the AF, a LAN address of the AF, port information of the AF, or an identity (ID) of the AF.

[0344] As another example, the service type comprises one or more of: inventory, command, or registration.

[0345] As another example, the terminal device type comprises a Type A and a Type B, the Type A being used to indicate a terminal device with extremely low power consumption and / or extremely low complexity, and the Type B being used to indicate a terminal device with low power consumption and / or low complexity.

[0346] As another example, the fourth information comprises the identity of the AF and the service type, or the fourth information comprises the identity of the AF and the terminal device type; if the priority of the service type or the priority of the terminal device type is included in the application subscription information corresponding to the AF, the priority of the service type or the priority of the terminal device type is sent to the first AMF.

[0347] As another example, the fourth information comprises the identity of the AF and the priority of the second message; if the authentication to the AF is successful, the priority of the second message is sent to the first AMF.

[0348] As another example, the transceiver 902 can also be configured to send, to the NRF, a first request for address information of an AMF, the first request comprising fifth information used to indicate a load requirement of the AMF, and receive, from the NRF, the address information of the first AMF that meets the load requirement.

[0349] Exemplarily, the transceiver 902 can further comprise a radio frequency module, an antenna module, etc. Exemplarily, the transceiver 902 can further comprise a pin module, etc.

[0350] Optionally, in each of the above embodiments, the communication apparatus can further comprise a storage module, which can be configured to store instructions and / or data, and the processing module 901 can read the instructions and / or data in the storage module to enable the apparatus to implement the foregoing method embodiments. Exemplarily, the storage module can also store the first information, the second information, the first identity, the first rule information, the configuration file, etc. shown above.

[0351] In each of the above embodiments, the specific description of the terms or steps such as the Internet of Things service, the quality of service, the resource type, the service time budget, the uplink data packet, the terminal device type, etc. in each sub-block can refer to the description in the foregoing method embodiments, which will not be repeated here.

[0352] The specific description of the transceiver module and the processing module shown in each of the above embodiments is only an example. For the specific functions or executed steps of the transceiver module and the processing module, reference can be made to the above method embodiments, which will not be described in detail here.

[0353] The device of the embodiments of the present application is introduced above. The possible product forms of the device are introduced below. Any product form having the functions of the device shown in FIG. 9 falls within the protection scope of the embodiments of the present application. The introduction below is only an example, and the product form of the device of the embodiments of the present application is not limited to this.

[0354] In a possible implementation, in the communication device shown in FIG. 9, the processing module 901 can be one or more processing circuits, and the transceiver module 902 can be a transceiver circuit, or the transceiver module 902 can also be a sending module and a receiving module, the sending module can be a sending circuit, and the receiving module can be a receiving circuit, and the sending module and the receiving module are integrated in one device, for example, a transceiver circuit. In the embodiments of the present application, the processing circuit and the transceiver circuit can be coupled, and the connection mode of the processing circuit and the transceiver circuit is not limited in the embodiments of the present application. In the process of executing the above method, the process of sending information in the above method can be the process of outputting the above information by the processing circuit. When the above information is output, the processing circuit outputs the above information to the transceiver circuit, so as to be transmitted (or output) by the transceiver circuit. After the above information is output by the processing circuit, it can also need to be processed further, and then reach the transceiver circuit. Similarly, the process of receiving information in the above method can be the process of receiving the input above information by the processing circuit. When the processing circuit receives the input information, the transceiver circuit receives the above information and inputs it to the processing circuit. Further, after the transceiver circuit receives the above information, the above information can need to be processed further, and then input to the processing circuit.

[0355] FIG. 10 is a structural schematic diagram of a communication device provided by the embodiments of the present application. As shown in FIG. 10, the communication device 1000 includes one or more processing circuits 1020 and a transceiver circuit 1010.

[0356] In some embodiments of the present application, the communication device can be used to execute the steps or methods or functions executed by the first network element, for example, the processing circuit 1020 can be used to execute the functions or steps implemented by the processing module 901 shown in FIG. 9, and the transceiver circuit 1010 can be used to execute the functions or steps implemented by the transceiver module 902 shown in FIG. 9. For the specific description of the processing circuit 1020 and the transceiver circuit 1010, reference can be made to FIG. 9 or the above method embodiments, which will not be described in detail here.

[0357] In some embodiments of the application, the apparatus is configured to perform the steps or methods or functions described above as being performed by the access network device, e.g. the processing circuitry 1020 can be configured to perform the functions or steps implemented by the processing module 901 as illustrated in Figure 9, and the transceiver circuitry 1010 can be configured to perform the functions or steps implemented by the transceiving module 902 as illustrated in Figure 9. More details about the processing circuitry 1020 and the transceiver circuitry 1010 can be found in the method embodiments described above or in Figure 9.

[0358] In some embodiments of the application, the apparatus is configured to perform the steps or methods or functions described above as being performed by the terminal device, e.g. the processing circuitry 1020 can be configured to perform the functions or steps implemented by the processing module 901 as illustrated in Figure 9, and the transceiver circuitry 1010 can be configured to perform the functions or steps implemented by the transceiving module 902 as illustrated in Figure 9. More details about the processing circuitry 1020 and the transceiver circuitry 1010 can be found in the method embodiments described above or in Figure 9.

[0359] In some embodiments of the application, the apparatus is configured to perform the steps or methods or functions described above as being performed by the second network element, e.g. the processing circuitry 1020 can be configured to perform the functions or steps implemented by the processing module 901 as illustrated in Figure 9, and the transceiver circuitry 1010 can be configured to perform the functions or steps implemented by the transceiving module 902 as illustrated in Figure 9. More details about the processing circuitry 1020 and the transceiver circuitry 1010 can be found in the method embodiments described above or in Figure 9.

[0360] By way of example, the processing circuitry can be one or more processors, or all or part of one or more processors. The transceiver circuitry can be a transceiver, or input / output circuitry, or interface circuitry, etc.

[0361] By way of example, in each of the various implementations of the apparatus illustrated in Figure 10, the transceiver circuitry can comprise a receiver configured to perform the functions (or operations) of receiving, and a transmitter configured to perform the functions (or operations) of transmitting. The transceiver circuitry is configured to communicate with other devices / apparatus over a transmission medium.

[0362] Optionally, the communications apparatus 1000 further includes one or more memories 1030 that are configured to store program instructions and / or data. The memory 1030 is coupled to the processing circuitry 1020. The coupling in embodiments of the application is an indirect coupling or communication connection between apparatuses, units or modules, which can be electrical, mechanical or other type, for information exchange between apparatuses, units or modules. The processing circuitry 1020 can operate in coordination with the memory 1030. The processing circuitry 1020 can execute program instructions stored in the memory 1030. Optionally, at least one of the one or more memories can be included in the processing circuitry.

[0363] The specific connection medium between the transceiver circuit 1010, the processing circuit 1020 and the memory 1030 in the embodiments of the present application is not limited. In FIG. 10, the memory 1030, the processing circuit 1020 and the transceiver circuit 1010 are connected through a bus 1040, which is represented by a thick line in FIG. 10, and the connection mode between other components is only illustrative and is not limited. The bus can be divided into an address bus, a data bus, a control bus and the like. For convenience of representation, only one thick line is used in FIG. 10, but it does not mean that there is only one bus or only one type of bus.

[0364] In the embodiments of the present application, the processing circuit can be a general-purpose processing circuit, a digital signal processing circuit, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc., which can implement or execute the disclosed methods, steps and logic block diagrams in the embodiments of the present application. The general-purpose processing circuit can be a micro-processing circuit or any conventional processing circuit, etc. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as execution completed by a hardware processing circuit, or executed by a combination of hardware and software modules in the processing circuit, etc.

[0365] In the embodiments of the present application, the memory can include, but is not limited to, a non-volatile memory such as a hard disk drive (HDD) or a solid-state drive (SSD), a random access memory (RAM), an erasable programmable ROM (EPROM), a read-only memory (ROM) or a compact disc read-only memory (CD-ROM), etc. The memory is any storage medium that can be used to carry or store program codes in the form of instructions or data structures and can be read and / or written by a computer (such as the device shown in the present application, etc.), but is not limited thereto. The memory in the embodiments of the present application can also be a circuit or any other device capable of realizing a storage function, used for storing program instructions and / or data.

[0366] Exemplarily, the processing circuit 1020 is mainly used for processing communication protocols and communication data, and controlling the whole device, executing software programs, and processing data of the software programs. The memory 1030 is mainly used for storing software programs and data. The transceiver circuit 1010 can include a control circuit mainly used for conversion between baseband signals and radio frequency signals and processing of the radio frequency signals, and an antenna mainly used for transceiving radio frequency signals in the form of electromagnetic waves. Input and output devices such as touch screens, display screens, keyboards, and the like are mainly used for receiving user input data and outputting data to users.

[0367] When the device is powered on, the processing circuit 1020 can read the software program in the memory 1030, interpret and execute instructions of the software program, and process data of the software program. When data needs to be transmitted wirelessly, the processing circuit 1020 outputs a baseband signal to the radio frequency circuit after baseband processing of the data to be transmitted, and the radio frequency circuit converts the baseband signal into a radio frequency signal and transmits the radio frequency signal in the form of electromagnetic waves through the antenna. When data is transmitted to the device, the radio frequency circuit receives a radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processing circuit 1020, and the processing circuit 1020 converts the baseband signal into data and processes the data.

[0368] In another implementation, the radio frequency circuit and the antenna can be arranged independently of the processing circuit performing baseband processing, for example, in a distributed scenario, the radio frequency circuit and the antenna can be arranged remotely from the device.

[0369] The device shown in the embodiments of the present application can also have more components and the like than those shown in FIG. 10, which are not limited in the embodiments of the present application. The methods performed by the processing circuit and the transceiver circuit shown above are only examples, and the specific steps performed by the processing circuit and the transceiver circuit can refer to the methods introduced above.

[0370] In another possible implementation, in the device shown in FIG. 9, the processing module 901 can be one or more logic circuits, and the transceiver module 902 can be an input and output interface, also called a communication interface, or an interface circuit, or an interface, and the like. Alternatively, the transceiver module 902 can also be a sending module and a receiving module, the sending module can be an output interface, and the receiving module can be an input interface, and the sending module and the receiving module are integrated into one module, for example, an input and output interface.

[0371] FIG. 11 is a structural schematic diagram of a communication apparatus provided in an embodiment of the present application. As shown in FIG. 11, the communication apparatus shown in FIG. 11 includes a logic circuit 1101 and an interface circuit 1102. That is, the processing module 901 can be implemented by the logic circuit 1101, and the transceiver module 902 can be implemented by the interface circuit 1102. The logic circuit 1101 can be a chip, a processing circuit, an integrated circuit, or a system on chip (SoC) chip, and the interface circuit 1102 can be a communication interface, an input / output interface, a pin, etc. For example, FIG. 11 is a chip in which the communication apparatus is taken as an example, and the chip includes the logic circuit 1101 and the interface circuit 1102.

[0372] In an embodiment of the present application, the logic circuit and the interface can also be coupled to each other. The specific connection mode of the logic circuit and the interface is not limited in the embodiments of the present application. For example, the logic circuit 1101 can be used to execute the functions or steps implemented by the processing module 901 shown in FIG. 9, and the interface circuit 1102 can be used to execute the functions or steps implemented by the transceiver module 902 shown in FIG. 9. The specific description of the logic circuit 1101 and the interface circuit 1102 can be referred to the method embodiments shown in FIG. 9 or the above, which will not be described in detail here.

[0373] The apparatus shown in the embodiments of the present application can be used to implement the methods provided in the embodiments of the present application in the form of hardware, software, or the like, and the present application is not limited thereto.

[0374] The embodiments of the present application further provide a communication system, which includes a first network element, an access network device, and a terminal device. The first network element, the access network device, and the terminal device can be used to execute the method in any of the preceding embodiments. The terminal device can include a UE and an Internet of Things device (such as an A-IoT device), and the UE can be regarded as an intermediate node.

[0375] The embodiments of the present application further provide a communication system, which includes a second network element. The second network element can be used to execute the method in any of the preceding embodiments.

[0376] In addition, the present application further provides a computer program for implementing the operations and / or processes performed by various apparatuses in the methods provided in the present application.

[0377] The present application further provides a computer readable storage medium, which stores computer code. When the computer code is run on a computer, the computer is caused to execute the operations and / or processes performed by various apparatuses in the methods provided in the present application.

[0378] The application further provides a computer program product comprising computer code or a computer program which, when run on a computer, causes the operations and / or processes performed in the method provided by the application to be performed by the respective executing.

[0379] In several embodiments provided by the application, it should be understood that the disclosed system, device and method can be implemented by other manners. For example, the device embodiments described above are only illustrative, for example, the division of the modules is only a logical function division, and actual implementation can have another division manner, for example, a plurality of modules or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the displayed or discussed each other can be indirect coupling or communication connection through some interfaces, devices or modules, and can also be electrical, mechanical or other form of connection.

[0380] The modules described as separate components can or can not be physically separated, and the components displayed as modules can or can not be physical modules, that is, can be located in one place, or can be distributed to a plurality of network modules. Part or all of the modules can be selected to achieve the technical effects of the scheme provided by the embodiments of the application according to actual needs.

[0381] In addition, the function modules in each embodiment of the application can be integrated in one processing module, or each module can exist physically, or two or more modules can be integrated in one module. The integrated module can be realized in the form of hardware or in the form of a software function module.

[0382] The integrated module, if realized in the form of a software function module and sold or used as an independent product, can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the application essentially or the part of the prior art that contributes to the technical solutions, or all or part of the technical solutions can be embodied in the form of a software product, which is stored in a readable storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in the embodiments of the application. The aforementioned readable storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various program code storage media.

[0383] The above merely provides the specific implementation of the present application, but the protection scope of the present application is not limited to this. Any person skilled in the art can easily think of the changes or replacements within the technical range disclosed by the present application, which should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A quality of service guarantee method characterized by comprising: The method applied to a first network element comprises: receiving a first message, the first message comprising first information; or, receiving the first message and the first information; determining a first identifier and / or second information based on the first information, the first identifier being associated with the second information; performing a traffic processing action on the first message based on the second information; wherein the first information comprises one or more of the following: an identifier of an application function, a service type, a service object, a priority of the first message, a terminal device type, a first service time budget, a destination network address, a network address of a terminal device; the second information comprises one or more of the following: a priority corresponding to an Internet of Things service, a resource type, a second service time budget, a size of an uplink data packet, an uplink and / or downlink rate size.

2. The method of claim 1, wherein, the identifier of the application function comprises one or more of the following: a uniform resource identifier (URL) of the application function, an Internet Protocol (IP) address of the application function, a Media Access Control (MAC) address of the application function, a Local Area Network (LAN) address of the application function, port information of the application function, or an identity (ID) of the application function; the service type comprises one or more of the following: inventory, command, or registration.

3. The method according to claim 1 or 2, characterized in that, the service object comprises a terminal device group or a single terminal device.

4. The method of claim 3, wherein, when the service object is a terminal device group, the size of the uplink data packet is the sum of the sizes of the uplink data packets of all terminal devices in the terminal device group, or the size of the uplink data packet of a single terminal device in the terminal device group.

5. The method according to any one of claims 1-4, characterized in that, the terminal device type comprises Type A and Type B, Type A indicating a terminal device with extremely low power consumption and / or extremely low complexity, and Type B indicating a terminal device with low power consumption and / or low complexity.

6. The method according to any one of claims 1-5, characterized in that, the priority corresponding to the Internet of Things service comprises one or more of the following: a priority of an application function, a priority of a service type, a priority of the first message, or a priority of a terminal device type.

7. The method according to any one of claims 1 to 6, characterized in that, the first service time budget or the second service time budget comprises: a time length from the start of receiving the first message to the reception of a response message to the last first message; or, a time length from the start of receiving the first message to the reception of a response message to the last first message and returning to the application function; or, a time length from the start of receiving the first message to the reception of a response message to the first message.

8. The method according to any one of claims 1-7, characterized in that, the resource type comprises a Guaranteed Bit Rate (GBR) or a Non-GBR provided for the first message of the Internet of Things service.

9. The method according to any one of claims 1-8, characterized in that, before the reception of the first message, or the reception of the first message and the first information, the method further comprises: receiving first rule information from a session management function, the first rule information comprising first indication information, the first indication information being used to indicate a traffic processing action.

10. The method according to any one of claims 1-9, characterized in that, the method further comprises: sending the first identifier and / or the second information to an access network device.

11. A quality of service guarantee method characterized by, the method applied to an access network device or a terminal device comprises: receiving a first identifier and / or second information, the first identifier being associated with the second information, the second information comprising one or more of: a priority corresponding to the IoT service, a resource type, a second service time budget, a size of uplink data packets, an uplink and / or downlink rate size; performing a resource allocation action and / or a traffic handling action based on the second information.

12. The method of claim 11, wherein, The priority corresponding to the IoT service comprises one or more of: a priority of an application function, a priority of a service type, a priority of the first message, or a priority of a terminal device type.

13. The method according to claim 11 or 12, characterized in that, The resource type comprises a guaranteed bit rate (GBR) or a non-guaranteed bit rate (Non-GBR) provided for the first message of the IoT service.

14. The method according to any one of claims 11-13, characterized in that, The second service time budget comprises: a time length from receiving a first message to receiving a response message to the last first message; or, a time length from receiving a first message to receiving a response message to the last first message and returning to an application function; or, a time length from receiving a first message to receiving a response message to the first message.

15. The method according to any one of claims 11-14, characterized in that, When the service object is a terminal device group, the size of the uplink data packets is a sum of sizes of uplink data packets of all terminal devices in the terminal device group, or a size of uplink data packets of a single terminal device in the terminal device group.

16. The method according to any one of claims 11-15, characterized in that, Before the receiving the first identifier and / or the second information, the method further comprises: receiving a configuration file from a session management function, the configuration file comprising the first identifier and second indication information, the second indication information being used to indicate the resource allocation action and / or the traffic handling action.

17. The method according to any one of claims 11-16, characterized in that, When the quality of service guarantee method is applied to an access network device, the method further comprises: sending the first identifier and / or the second information to a terminal device.

18. A quality of service guarantee method characterized by, Applied to a first network element or an access network device, the method comprises: receiving third information, the third information comprising one or more of: a priority corresponding to the IoT service, a resource type, a second service time budget, a size of uplink data packets, an uplink and / or downlink rate size; performing a traffic handling action based on the third information.

19. The method of claim 18, wherein, The priority corresponding to the IoT service comprises one or more of: a priority of an application function, a priority of a service type, a priority of the first message, or a priority of a terminal device type.

20. The method of claim 18 or 19, wherein, The second service time budget comprises: a time length from receiving a first message to receiving a response message to the last first message; or, a time length from receiving a first message to receiving a response message to the last first message and returning to an application function; or, a time length from receiving a first message to receiving a response message to the first message.

21. The method of any one of claims 18-20, wherein, When the service object is a terminal device group, the size of the uplink data packets is a sum of sizes of uplink data packets of all terminal devices in the terminal device group, or a size of uplink data packets of a single terminal device in the terminal device group.

22. The method of any one of claims 18-21, wherein, The method further comprises: sending the third information to an access network device or a terminal device.

23. A quality of service guarantee method characterized by, Applied to a second network element, the method comprises: receiving a second message, the second message comprising fourth information; or, receiving the second message and the fourth information; wherein the fourth information comprises one or more of: an identity of the application function, a service type, a terminal device type, or a priority of the second message.

24. The method of claim 23, wherein, the identity of the application function comprises one or more of: a uniform resource identifier (URL) of the application function, an internet protocol (IP) address of the application function, a media access control (MAC) address of the application function, a local area network (LAN) address of the application function, port information of the application function, or an identity (ID) of the application function; the service type comprises one or more of: inventory, command, or registration.

25. The method of claim 23 or 24, wherein, the terminal device type comprises a type A and a type B, the type A indicating a terminal device of extremely low power consumption and / or extremely low complexity, and the type B indicating a terminal device of low power consumption and / or low complexity.

26. The method of any one of claims 23-25, wherein, the fourth information comprises the identity of the application function and the service type, or the fourth information comprises the identity of the application function and the terminal device type. if the service type or the terminal device type is included in application subscription information corresponding to the application function, sending the priority of the service type or the priority of the terminal device type to the first access and mobility management function.

27. The method of any one of claims 23-26, wherein, the fourth information comprises the identity of the application function and the priority of the second message. if the application function is authenticated successfully, sending the priority of the second message to the first access and mobility management function.

28. The method of any one of claims 23-27, wherein, the method further comprises: sending a first request to a network storage function, the first request being used to request address information of an access and mobility management function, the first request comprising fifth information, the fifth information being used to indicate a load requirement of the access and mobility management function; receiving the address information of the first access and mobility management function from the network storage function, the first access and mobility management function satisfying the load requirement.

29. A communications device, characterized by a module for performing the method of any one of claims 1-10, or a module for performing the method of any one of claims 11-17, or a module for performing the method of any one of claims 18-22, or a module for performing the method of any one of claims 23-28.

30. A communication system, characterized by the communication system comprises a first network element, an access network device, and a terminal device, wherein the first network element is configured to perform the method of any one of claims 1-10, and the access network device and the terminal device are configured to perform the method of any one of claims 11-17; or, the communication system comprises a first network element and an access network device, and the first network element and the access network device are configured to perform the method of any one of claims 18-22; or, the communication system comprises a second network element, and the second network element is configured to perform the method of any one of claims 23-28.

Images