CN117135699A

CN117135699A - Quality of service parameter management method, node and storage medium

Info

Publication number: CN117135699A
Application number: CN202210553953.5A
Authority: CN
Inventors: 刘光毅; 李娜; 张慧敏; 佟舟
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Priority date: 2022-05-20
Filing date: 2022-05-20
Publication date: 2023-11-28

Abstract

The embodiment of the application provides a service quality parameter management method, a first network node, a domain control node and a computer readable storage medium, wherein the method comprises the following steps: the first network node transmits the QoS configuration of different domains to each domain control node; wherein the QoS configuration includes at least one of: qoS parameters; qoS parameter generation strategy; qoS parameter adjustment strategy; qoS parameter generator.

Description

Quality of service parameter management method, node and storage medium

Technical Field

The present application relates to the field of communications technologies, and in particular, to a quality of service parameter management method, a first network node, a domain control node, and a computer readable storage medium.

Background

The quality of service (Quality of Service, qoS) management of the current network is service-granularity, and the same QoS parameters are configured for all users aiming at the same service, and the differentiated requirements of different users on user experience (Quality of Experience, qoE) are not considered. For example, for some users, when the packet loss rate (Packet Error Rate, PER) exceeds the QoS requirement of the service, the user experience may not be affected, so long as the corresponding increase of the traffic bit rate (Guaranteed Flow Bit Rate, GFBR) is ensured. However, the related art does not support dynamic adjustment between parameters, nor does the related art support flexible dynamic adjustment of the same parameter between AN Access Network (AN) side and a Core Network (CN) side. This is particularly important for 6G networks where QoS is more multi-dimensional.

In summary, in the related art, the QoS parameters of the network cannot be dynamically adjusted, which results in low resource usage efficiency of the network.

Disclosure of Invention

The embodiment of the application provides a quality of service parameter management method, a first network node, a domain control node and a computer readable storage medium.

In a first aspect, a quality of service parameter management method is provided, including:

the first network node transmits the QoS configuration of different domains to each domain control node;

wherein the QoS configuration includes at least one of:

QoS parameters;

QoS parameter generation strategy;

QoS parameter adjustment strategy;

QoS parameter generator.

In a second aspect, a quality of service parameter management method is provided, including:

the domain control node receives QoS configuration issued by a first network node;

wherein the QoS configuration includes at least one of:

QoS parameters;

QoS parameter generation strategy;

QoS parameter adjustment strategy;

QoS parameter generator.

In a third aspect, there is provided a first network node comprising:

the first sending module is used for sending the QoS configuration of different domains to each domain control node;

wherein the QoS configuration includes at least one of:

QoS parameters;

QoS parameter generation strategy;

QoS parameter adjustment strategy;

QoS parameter generator.

In a fourth aspect, there is provided a domain control node comprising:

the second receiving module is used for receiving QoS configuration issued by the first network node;

wherein the QoS configuration includes at least one of:

QoS parameters;

QoS parameter generation strategy;

QoS parameter adjustment strategy;

QoS parameter generator.

In a fifth aspect, there is provided a first network node comprising: the system comprises a processor and a memory, wherein the memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory to execute the quality of service parameter management method.

In a sixth aspect, there is provided a domain control node comprising: the system comprises a processor and a memory, wherein the memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory to execute the quality of service parameter management method.

In a seventh aspect, a computer-readable storage medium is provided for storing a computer program that causes a computer to execute the above-described quality of service parameter management method.

Through the above technical solution, the QoS configuration issued by the first network node to the control node of each domain may be at least one of the following: qoS parameters; a QoS parameter generation policy or QoS parameter generator for generating QoS parameters; qoS parameter adjustment policies for adjusting QoS parameters. Thus, dynamic adjustment among QoS parameters is realized based on QoS configuration, and the resource utilization efficiency of the network is improved.

Drawings

Fig. 1 is a schematic diagram of a quality of service parameter management system according to an embodiment of the present application;

fig. 2 is a flow chart of a 5G QoS management mechanism in the related art;

fig. 3 is a schematic diagram illustrating the overall descriptions of entities involved in a control plane and related QoS communications in the related art;

fig. 4 is a flowchart of a method for managing qos parameters according to an embodiment of the present application;

fig. 5 is a schematic diagram of an association Flow provided as a part of an IP Flow according to an embodiment of the present application;

fig. 6 is a schematic flow chart of a first network node sending out QoS configuration according to an embodiment of the present application;

fig. 7 is a second flowchart of a first network node sending out QoS configuration according to an embodiment of the present application;

fig. 8 is a second flowchart of a method for managing qos parameters according to an embodiment of the present application;

Fig. 9 is a schematic diagram of interaction between a first network node and a plurality of domain control nodes according to an embodiment of the present application;

fig. 10 is a second schematic interaction diagram of a first network node and a plurality of domain control nodes according to an embodiment of the present application;

fig. 11 is a flowchart illustrating a method for managing qos parameters according to an embodiment of the present application;

fig. 12 is a diagram showing QoS distribution of communication situations between a calling subscriber network and a called subscriber network in the related art;

fig. 13 is an interaction schematic diagram of a first network node of a first network and a second network node of a second network according to an embodiment of the present application;

fig. 14 is a schematic structural diagram of a first network node according to an embodiment of the present application;

fig. 15 is a second schematic structural diagram of a first network node according to an embodiment of the present application;

fig. 16 is a schematic structural diagram of a domain control node according to an embodiment of the present application;

fig. 17 is a schematic diagram of a domain control node according to a second embodiment of the present application.

Detailed Description

The following description of the technical solutions according to the embodiments of the present application will be given with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

Fig. 1 is a schematic diagram of a wireless communication system of an embodiment of the present application.

As shown in fig. 1, a wireless communication system 100 may include a terminal device 110 and a network device 120. Network device 120 may communicate with terminal device 110 over the air interface. Multi-service transmission is supported between terminal device 110 and network device 120.

It should be understood that embodiments of the present application are illustrated by way of example only in wireless communication system 100, and embodiments of the present application are not limited thereto. That is, the technical solution of the embodiment of the present application may be applied to various communication systems, for example: long term evolution (Long Term Evolution, LTE) system, LTE time division duplex (Time Division Duplex, TDD), universal mobile telecommunications system (Universal Mobile Telecommunication System, UMTS), internet of things (Internet of Things, ioT) system, narrowband internet of things (Narrow Band Internet of Things, NB-IoT) system, enhanced Machine-type communication (eMTC) system, fifth generation mobile telecommunications technology (5th Generation Mobile Communication Technology,5G) communication system (also referred to as New Radio (NR) communication system), or future communication system, etc.

In the wireless communication system 100 shown in fig. 1, the network device 120 may be an access network device that communicates with the terminal device 110. The access network device may provide communication coverage for a particular geographic area and may communicate with terminal devices 110 (e.g., user Equipment (UE)) located within the coverage area.

The network device 120 may be an evolved base station (Evolutional Node B, eNB or eNodeB) in a long term evolution (Long Term Evolution, LTE) system, or a next generation radio access network (Next Generation Radio Access Network, NG RAN) device, or a base station (gNB) in a NR system, or a radio controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device 120 may be a relay station, an access point, a vehicle device, a wearable device, a hub, a switch, a bridge, a router, or a network device in a future evolved public land mobile network (Public Land Mobile Network, PLMN), etc.

Terminal device 110 includes, but is not limited to, any terminal device that employs a wired or wireless connection with network device 120 or other terminal devices.

For example, the terminal device 110 may refer to an access terminal, user Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, an IoT device, a satellite handset, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA), a handset with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network or a terminal device in a future evolution network, etc.

The terminal Device 110 may be used for Device-to-Device (D2D) communication.

The wireless communication system 100 may further comprise a core network device 130 in communication with the base station, which core network device 130 may be a 5G core,5gc device, e.g. an access and mobility management function (Access and Mobility Management Function, AMF) device, further e.g. an authentication server function (Authentication Server Function, AUSF) device, further e.g. a user plane function (User Plane Function, UPF) device, further e.g. a session management function (Session Management Function, SMF) device. Optionally, the core network device 130 may also be a packet core evolution (Evolved Packet Core, EPC) device of the LTE network, for example a session management function+a data gateway (Session Management Function + Core Packet Gateway, smf+pgw-C) device of the core network. It should be appreciated that SMF+PGW-C may perform the functions performed by both SMF and PGW-C. In the network evolution process, the names of the core network devices may be changed, or new network entities may be formed by dividing the functions of the core network, which is not limited in the embodiment of the present application.

The wireless communication system 100 may further include a first network node having a policy/generator that generates and/or is capable of generating each domain quality of service parameter in the wireless communication system 100, where the first network node may be a device independently configured in the wireless communication system 100 or may be configured with an SMF in the core network device 130, which is not specifically limited in this embodiment of the present application.

Communication may also be achieved by establishing a connection between the various functional units in the wireless communication system 100 via a next generation Network (NG) interface.

For example, the terminal device establishes an air interface connection with the access network device through an NR interface, and is used for transmitting user plane data and control plane signaling; the terminal equipment can establish control plane signaling connection with AMF through NG interface 1 (N1 for short); an access network device, such as a next generation radio access base station (gNB), can establish a user plane data connection with a UPF through an NG interface 3 (N3 for short); the access network equipment can establish control plane signaling connection with AMF through NG interface 2 (N2 for short); the UPF can establish control plane signaling connection with the SMF through an NG interface 4 (N4 for short); the UPF can interact user plane data with the data network through an NG interface 6 (N6 for short); the AMF may establish a control plane signaling connection with the SMF through NG interface 11 (N11 for short); the SMF may establish a control plane signaling connection with the PCF via NG interface 7 (N7 for short).

Fig. 1 exemplarily illustrates one base station, one core network device, and two terminal devices, alternatively, the wireless communication system 100 may include a plurality of base station devices and each base station may include other number of terminal devices within a coverage area, which is not limited by the embodiment of the present application.

It should be noted that fig. 1 is only an exemplary system to which the present application is applicable, and of course, the method shown in the embodiment of the present application may be applicable to other systems. Furthermore, the terms "system" and "network" are often used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship. It should also be understood that, in the embodiments of the present application, the "indication" may be a direct indication, an indirect indication, or an indication having an association relationship. For example, a indicates B, which may mean that a indicates B directly, e.g., B may be obtained by a; it may also indicate that a indicates B indirectly, e.g. a indicates C, B may be obtained by C; it may also be indicated that there is an association between a and B. It should also be understood that "corresponding" mentioned in the embodiments of the present application may mean that there is a direct correspondence or an indirect correspondence between the two, may mean that there is an association between the two, and may also be a relationship between an instruction and an indicated, configured, or the like. It should also be understood that "predefined" or "predefined rules" mentioned in the embodiments of the present application may be implemented by pre-storing corresponding codes, tables or other manners in which related information may be indicated in devices (including, for example, terminal devices and network devices), and the present application is not limited to the specific implementation thereof. Such as predefined may refer to what is defined in the protocol. It should be further understood that, in the embodiment of the present application, the "protocol" may refer to a standard protocol in the field of communications, and may include, for example, an LTE protocol, an NR protocol, and related protocols applied in a future communication system, which is not limited by the present application.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following description describes related technologies of the embodiments of the present application, and the following related technologies may be optionally combined with the technical solutions of the embodiments of the present application as alternatives, which all belong to the protection scope of the embodiments of the present application.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of the application only and is not intended to be limiting of the application.

Fig. 2 is a flow chart of a 5G QoS management mechanism in the related art. As shown in fig. 2, an Application/Service Layer (Application/Service Layer) sends packets from an Application to the UPF and/or UE (Data packets from applications). The UE maps UpLink (UL) packets to QoS flows and generates application QoS flows according to quality of service Flow identities (QoS Flow Identifier, QFI) in matching quality of service rules (QoS rules) (mapping UL packets to QoS Flows and apply QoS Flow making). The UE then maps the QoS Flow into Access Network (AN) resources (Mapping QoS Flows to AN Resources). Wherein all packets (all packets marked with the same QFI) marked with the same QFI are included in the UL packet.

The QoS Flow is the minimum management granularity. QoS Flow is controlled by SMF and may be preconfigured or established during protocol data unit session (Protocol Data Unit session, PDU session) establishment/modification.

In the Downlink (DL), the UPF classifies incoming packets according to their priority by packet filter groups (Packet Filter Set) of PDRs, or classifies incoming packets for QoS Flow labeling and other operations (classify packets for QoS Flow marking and other actions). UPF delivers the classification of user plane traffic belonging to QoS flows by using the N3 (and N9) user plane labels of QFI. There is no strict 1:1 relationship between QoS Flow and resources. The necessary AN resources to which QoS flows can be mapped are established by the AN and released. The AN should indicate to the SMF when the AN resources to which the QoS Flow maps are released. In UL, for an internetworking protocol (Internet Protocol, IP) or ethernet type PDU session, the UE evaluates UL packets in ascending order according to UL packet filters among packet filters set in QoS rules based on the priority value of the QoS rules until a matching QoS rule is found.

In order to implement QoS in the related art, related entities need to support QoS requests and related QoS parameters. Fig. 3 is a schematic diagram of an entity involved in a control plane and an overall description of related QoS communication in the related art. As shown in fig. 3, first, the UE may issue a QoS request to the 5GC using network attached storage session management (Network Attached Storage Session Management, NAS SM) signaling or through application layer signaling directed to the AF. After establishing the PDU session, the SMF retrieves session management subscription data including a default QoS from the unified data management (Unified Data Management, UDM). When the PCF obtains a QoS request from the AF, the PCF generates PCC rules based on subscription and policy and sends to the SMF. Further, based on the traffic demand, the SMF derives QoS profile, UPF operation, and QoS rules from the PCC rules and other information provided by the PCF, and assigns QFI to the QoS Flow. The UPF operations include, among other things, performing classification, bandwidth policy enforcement, and marking of user plane traffic. The SMF then provides the QFI, qoS profile, or alternative QoS profile to the RAN. Here, the access network QoS profile is controlled by the SMF, and may be issued to the RAN by the AMF through N2, or preconfigured in the RAN.

It should be noted that the QoS profile determines whether a QoS Flow is a guaranteed bit rate (Guaranteed Bit Rate, GBR) or a non-guaranteed bit rate (non-GBR). Each QoS profile has a corresponding QFI.

The SMF sends QoS profile to the RAN, containing the following QoS parameters (QoS parameters): for each QoS Flow, the QoS profile includes a 5G QoS identification (5G QoS Identifier,5QI) and an address resolution protocol (Address Resolution Protocol, ARP). The QoS profile also includes a reflective QoS attribute (Reflective QoS Attribute, RQA) for each non-GBR QoS Flow. The QoS profile also includes, for each GBR QoS Flow, GFBR, maximum traffic bit rate (Maximum Flow Bit Rate, MFBR), one or more notification control (Notification control), and maximum packet loss rate (Maximum Packet Loss Rate).

ARP is used to determine if the establishment/modification/handoff of QoS Flow can be accepted or rejected in the case of resource limitation. Which determines the relative importance of a QoS Flow. The RQA is an optional parameter for indicating whether a reflective QoS can be used by a particular service corresponding to one QoS Flow or a portion of one QoS Flow. Notification control is used to indicate whether RAN notification is required when GFBR for one QoS Flow cannot be guaranteed. Maximum Packet Loss Rate indicates a QoS Flow maximum packet loss number. 5QI is related to the following QoS characteristics (characteristics): resource type (Resource type), priority Level (Priority Level), PDB, PER, and average window (Averaging window).

Resource types include Non-GBR, and Delay-critical (GBR). The Priority Level is mainly issued to the RAN for instructing the RAN how to schedule resources. The RAN may also consider channel quality, resource type in scheduling decisions. PDB is used between the UE and all UPFs to define the time delay between the access network AN and the N6-terminated UPF, but AN-PDB and CN-PDB are defined as fixed values, respectively, and AN-PDB and CN-PDB cannot be dynamically adjusted. In practice, AN-PDB is directly related to radio channel quality and CN-PDB is directly related to congestion status of the wired transmission. The same value is used for the PDB for UL and DL. The PDB is used to support scheduling and link layer function configuration. The link layer functional configuration includes hybrid automatic repeat request (Hybrid Automatic Repeat reQuest, HARQ), scheduling priority weights. The Access Network packet delay budget (AN-PDB) is a value obtained by subtracting the Core Network packet delay budget (CN-PDB), and the CN-PDB is a static value. The CN-PDB may be 1ms, 2ms, 5ms for different traffic types. To obtain a more accurate AN-PDB, a dynamic Delay-critical CN-PDB value may be employed. The dynamic Delay-critical CN-PDB can be obtained in two ways: directly configured to each RAN; configured to the SMF and sent to the RAN through signaling. PER defines the upper limit of packet loss for non-congestion related PDUs (e.g., IP packets) between link layer protocols (e.g., radio link layer control protocol, (Radio Link Control, RLC)). The purpose of the PER is to support a suitable link layer protocol configuration (e.g., RLC/HARQ). There is one Averaging window per GBR QoS Flow. The window is used to calculate GFBR/MFBR between RAN, UPF and UE. Each Delay-critical GBR QoS Flow is associated with a maximum burst size (Maximum Data Burst Volume, MDBV). The MDBV represents the upper data limit that AN needs to serve during the AN-PDB period.

The SMF provides packet detection rules (packet detection rule, PDR), PDR priority and QoS related configuration information, and packet label information to the UPF; based on the PDR, the UPF can separate a specific QoS Flow from all packets, applying QoS priority control to the flows. Exemplary QoS-related configuration information includes maximum Bit Rate (Max Bit Rate, MBR) of traffic data flows (Service Data Flow, SDF) and GFBR and MFBR of a GBR QoS Flow (MBR for an SDF, GFBR and MFBR for a GBR QoS Flow). The packet marking information includes QFI and a transport layer packet marking value. Wherein the transport layer packet marker value comprises an IP header differential service code point (Differentiated Services Code Point, DSCP).

The SMF provides the UE with parameters of QoS Rule ID (QRI), qoS rule priority, and QoS Flow level for dynamically allocated QFI. It should be noted that, qoS rule and relevant QoS parameters of rule are issued to UE by network through N1 port, or terminal itself is obtained through reverse push mechanism. Illustratively, the QoS rule includes a QFI, a packet filter set, and a priority value. Parameters of QoS Flow class include 5QI, GFBR, and MFBR. For QoS rule, the UE uses QoS rule for each PDU session to decide whether and how to mark or transmit UL packets, i.e., associate UL traffic with QoS Flow. QoS rule may be allocated to the UE by signaling, or preconfigured to the UE, or obtained by a reflective QoS mechanism. QoS rule includes QFI, packet Filter Set and priority values. The QoS rule configured by signaling also includes a QRI, which is generated by the SMF and is unique in the PDU session. The same QFI may have multiple QoS rule. In the PDU session establishment process, a default QoS rule needs to be sent to the UE, and the QoS rule is associated with a QoS Flow. The PDR priority or QoS rule priority determines which QoS rule or PDR to use with priority.

Fig. 4 is a flowchart of a method for managing qos parameters according to an embodiment of the present application, as shown in fig. 4, where the method is applied to a first network node in the wireless communication system 100 shown in fig. 1, and the embodiment of the present application is not limited thereto specifically, and the method includes:

step 401, the first network node issues QoS configuration of different domains to each domain control node.

Wherein the QoS configuration comprises at least one of:

QoS parameters;

QoS parameter generation strategy;

QoS parameter adjustment strategy;

QoS parameter generator.

Step 402, the domain control node receives the QoS configuration issued by the first network node.

The embodiment of the application provides a service quality parameter management method, which comprises the following steps: the first network node transmits the QoS configuration of different domains to each domain control node; wherein the QoS configuration includes at least one of: qoS parameters; qoS parameter generation strategy; qoS parameter adjustment strategy; qoS parameter generator. That is, the QoS configuration issued by the first network node to the control node of each domain may be at least one of: qoS parameters; a QoS parameter generation policy or QoS parameter generator for generating QoS parameters; qoS parameter adjustment policies for adjusting QoS parameters. Thus, the first network node realizes dynamic adjustment among QoS parameters based on QoS configuration, and improves the resource utilization efficiency of the network.

In other embodiments of the present application, the QoS parameters include at least one of: qoS parameters related to connection/communication; qoS parameters related to computing power; qoS parameters associated with artificial intelligence AI; a QoS parameter related to security; qoS parameters related to perceived capability; qoS parameters related to data quality. Wherein the QoS parameters associated with the connection/communication include at least one of: resource type, priority, packet delay prediction, packet loss rate, maximum data burst size, average window, allocation and reservation priority, reverse-push QoS attribute, notification control. The QoS parameters associated with the computing power include at least one of: calculation accuracy and calculation efficiency. The AI-related QoS parameters include at least one of: training time consuming, interpretability, performance index boundaries. The security-related QoS parameters include at least one of: storing security level, calculating security level, transmitting security level. The QoS parameters related to the perceived capability include at least one of: distance resolution, angle resolution, speed resolution, perceived distance range, recognition rate, and imaging accuracy. The QoS parameters associated with the data quality include at least one of: feature redundancy, integrity, data accuracy, and data preparation are time consuming. That is, the embodiment of the application expands the QoS parameter range, improves the utilization rate of network multidimensional resources, and better ensures the user experience.

In other embodiments of the present application, the area covered by the wireless communication system may be divided into a plurality of domains, each of which performs a different function.

In other embodiments of the application, a QoS parameter generation policy and/or QoS parameter adjustment policy and/or QoS parameter generator is used to generate QoS parameters that meet requirements for quality of experience (Quality of Experience, qoE) and/or QoS parameters for a user.

Wherein the QoE comprises a score for QoS parameter accuracy generated by the QoS parameter generation policy and/or QoS parameter adjustment policy and/or QoS parameter generator. The QoS parameter requirements include the accuracy of QoS parameters generated by the QoS parameter generation policy and/or QoS parameter adjustment policy and/or QoS parameter generator with the control node requirements.

In other embodiments of the present application, qoS configuration is defined for an associated Flow that includes at least one IP Flow and/or a portion of one IP Flow. In the case where the associated Flow is part of one IP Flow, one IP Flow includes different flows divided into one IP Flow based on data traffic characteristics. For Extended Reality (XR) services, data exists in the form of a Group of pictures (GOP) frames, for example. One GOP frame includes 3 types of I frames, P frames, B frames, where I frames are key frames requiring no loss, while P frames and B frames may have different degrees of packet loss through the application's partial recovery capability. Within a GOP, the positions of I frames, P frames, B frames are fixed, the period is fixed, the number is fixed, i.e. the traffic characteristics are determined. As shown in fig. 5, each GOP frame is made up of a set of IBBPBBPBB frames, with the I frame always being the first of 9 frames. So, if this IP Flow is split further, the first of every 9 frames can be extracted to form one "stream", the remaining 8 to form another "stream".

In other embodiments of the present application, the first network node has at least one of the following functions:

first, a function with QoS parameter policy or QoS parameter generator, and/or issuing the generated QoS parameters of each domain to each domain control node.

Fig. 6 is a schematic flow chart of a first network node issuing QoS configuration according to an embodiment of the present application. As shown in fig. 6, the first network node has a function of QoS parameter policy or QoS parameter generator, i.e. the first network node is able to generate QoS parameters for each domain. Further, the first network node indicates the generated QoS parameters of each domain to a control node of each domain, for example, the domain control node 1 is an SMF of a node of the core network, and the domain control node 2 is a Central Unit (CU) of an access network node.

Second, the system has a function of generating the QoS parameter policy or QoS parameter generator of each domain, and/or transmits the generated QoS parameter policy or QoS parameter generator of each domain to each domain control node.

Fig. 7 is a schematic flow chart of a first network node issuing QoS configuration according to an embodiment of the present application. As shown in fig. 7, the first network node has a function of generating QoS parameter policies or QoS parameter generators, i.e., the first network node is able to generate QoS parameter policies or QoS parameter generators for each domain. Further, the first network node indicates the generated QoS parameter policy or QoS parameter generator of each domain to a control node of each domain, for example, the domain control node 1 is an SMF of a node of the core network, and the domain control node 2 is a CU of the access network node. Here, the QoS parameter policy includes, but is not limited to, a QoS parameter adjustment policy and a QoS parameter generation policy.

In the embodiment of the application, different QoS identification tables are set for different domains, and the value of each QoS identification in the QoS identification table can be standard default or dynamic configuration. Table 1 describes the mapping relationship between the partial QoS identities and the partial QoS parameters. Wherein Z represents a value corresponding to the Z-th QoS identification; z is a positive integer greater than or equal to 4; qoS parameters include, but are not limited to, priority, packet delay prediction, allocation reservation priority, computational security level, and data accuracy.

TABLE 1

QoS identification

Priority level

Packet delay prediction

Packet loss rate

Assigning reservation priorities

Calculating a security level

Data accuracy

1

x

2

x

3

x

4

x

……

x

Z

x

In other embodiments of the present application, different domains may configure different values for the same QoS parameters, or may configure different QoS parameters for different domains. For example, both RAN and CN need to set PER values in order to meet end-to-end packet loss requirements; the MDBV may only need to be configured to the RAN because the CN may always be satisfied without configuration.

In other embodiments of the present application, the manner in which the first network node issues the QoS parameters to the control node of each domain in step 401 includes one of the following:

mode one: the first network node issues QoS identities to the domains.

In other embodiments of the present application, by defining QoS identifiers and related QoS parameter values in advance, that is, x in table 1 is a specific value of a QoS parameter, a first network node divides the QoS parameter and issues the QoS parameter to a control node of each domain, if the first network node divides the QoS parameter value based on a standard default value, only a value corresponding to the QoS identifier needs to be issued when the QoS parameter issues the QoS parameter. Further, the domain control node receives the QoS identifier issued by the first network node, and determines each QoS parameter in the domain and a parameter value of each QoS parameter based on the QoS identifier.

For example, the end-to-end PDB requirement is 50ms, the AN-PDB standard value range is {4ms,8ms,16ms,32ms,64ms,128ms,256ms,512ms }, the CN-PDB standard value range is {4ms,8ms,16ms,32ms,64ms,128ms,256ms,512ms }, which is classified into AN-pdb=16 ms and CN-pdb=32 ms, and AN-pdb+cn-pdb=48 ms is greater than 50ms of the end-to-end PDB requirement, i.e., the end-to-end PDB requirement is satisfied, considering status information, subscription information, etc.; and allows for larger AN-PDBs, smaller CN-PDBs, to provide more accommodation for the AN when the AN-PDBs are not satisfactory and the CN transmissions are more stable. AN-pdb=16 ms and CN-pdb=32 ms correspond to AN access network QoS identity x and a core network QoS identity y, respectively. Only QoS identification x and QoS identification y need to be issued to the corresponding domain control node.

Mode two: the first network node issues QoS identification to each domain and the QoS parameter value of QoS parameter corresponding to the QoS identification.

In other embodiments of the present application, by defining a mapping relationship between QoS identifiers and QoS parameters in advance, but not defining specific parameter values of QoS parameters, that is, x in table 1 is used to indicate whether a certain QoS parameter exists for a specific QoS identifier, so that when a QoS parameter is issued, the QoS identifier and the parameter value of the QoS parameter corresponding to the QoS identifier need to be issued simultaneously. Further, the domain control node receives the QoS identifier issued by the first network node and the parameter value of the QoS parameter corresponding to the QoS identifier, and determines each QoS parameter in the domain and the parameter value of each QoS parameter based on the QoS identifier and the parameter value of the QoS parameter corresponding to the QoS identifier.

For example, the end-to-end PDB requirement is 50ms, which is divided into AN-pdb=16 ms and CN-pdb=34 ms in consideration of state information, subscription information, and the like, where AN-pdb=16 ms and CN-pdb=32 ms correspond to the access network QoS identifier x and the core network QoS identifier y, respectively. And when the configuration is issued, the QoS identifier is x, the parameter value corresponding to x is 16ms, and the QoS identifiers are y and the parameter value corresponding to y are 34ms, and are issued to the corresponding domain control nodes at the same time.

Mode three: the first network node issues QoS parameters and parameter values of the QoS parameters to the domains.

In other embodiments of the present application, the first network node directly transmits QoS parameters and parameter values of the QoS parameters corresponding to each domain to the control node of each domain. Further, the domain control node receives the QoS parameters and the parameter values of the QoS parameters issued by the first network node, and determines each QoS parameter in the domain and the parameter values of each QoS parameter.

In other embodiments of the present application, if the QoS received by the domain control node is configured as a QoS parameter generation policy, the domain control node generates the QoS parameter based on the QoS parameter generation policy.

In other embodiments of the present application, if the QoS received by the domain control node is configured as a QoS parameter generator, the domain control node generates QoS parameters based on the QoS parameter generator. Wherein the QoS parameter generator comprises an AI model.

In other embodiments of the present application, if the QoS received by the domain control node is configured as a QoS parameter adjustment policy, the domain control node adjusts the QoS parameter based on the QoS parameter adjustment policy. In the event that any one of the QoS parameters does not meet QoE and/or QoS parameter requirements, a QoS parameter adjustment policy adjusts one or more of the QoS parameters that are different from the any one QoS parameter. That is, based on the QoS parameter adjustment policy, the domain control node has a function of adjusting QoS parameters in the domain, so that dynamic coordination between different QoS index parameters, such as adjustment between PER and MFBR, adjustment between computing efficiency and MFBR, can be realized. Obviously, the QoS management mechanism in the embodiment of the present application is performed with UE as granularity, for example, the PER exceeds the QoS requirement of the service, but the transmission rate enhancement (such as MFBR) may also ensure the user experience.

In some embodiments, after the domain control node receives the QoS configuration issued by the first network node in step 402, if any one of the QoS parameters in the domain control node does not meet the QoE and/or QoS parameter requirements, the first network node adjusts one or more QoS parameters different from the any one of the QoS parameters.

For example, in the case where QoS received by the domain control node is configured as QoS parameters, after the domain control node runs for a period of time with QoS parameters, if any QoS parameter in the QoS parameters of the domain control node does not meet QoE and/or QoS parameter requirements, an adjustment request may be sent to the first network node, or any QoS performance information may be sent, and the first network node adjusts one or more QoS parameters different from any QoS parameter in the QoS parameters based on the adjustment request, or the QoS performance information is sent. Here, one or more QoS parameters and any QoS parameter may belong to the same domain, i.e. the first network node adjusts only other parameters of the domain to which any QoS parameter corresponds; one or more QoS parameters and any QoS parameter may also belong to different domains, that is, the first network node may adjust the QoS parameter of the domain, that is, the first network node may dynamically adjust the QoS parameter in different domains, so as to dynamically adjust different types of QoS parameters in different domains, and ensure that the utilization efficiency of various network resources is maximized.

In some embodiments, after the domain control node receives the QoS configuration issued by the first network node in step 402, if any one of the QoS parameters in the domain control node does not meet QoE and/or QoS parameter requirements, the first network node adjusts the QoS parameter generation policy and/or the QoS parameter adjustment policy and/or the QoS parameter generator.

In an exemplary case that the QoS received by the domain control node is configured to be a QoS parameter generating policy and/or the QoS parameter adjusting policy and/or the QoS parameter generator, the domain control node obtains the QoS parameter of the domain control node based on the QoS parameter generating policy and/or the QoS parameter adjusting policy and/or the QoS parameter generator, and after the QoS parameter is operated for a period of time, if any QoS parameter in the QoS parameters of the domain control node does not meet the QoE and/or QoS parameter requirement, the first network node may send an adjusting request to the first network node, or send any QoS performance information, and the first network node sends the QoS parameter generating policy and/or the QoS parameter adjusting policy and/or the QoS parameter generator based on the adjusting request, or sends the QoS parameter adjusting policy and/or the QoS parameter generator, that is, when the QoS parameter generated by the first network node and the QoS parameter generated by the QoS parameter adjusting policy and/or the QoS parameter generator fails to meet the QoE and/or QoS parameter requirement, the first network node sends the QoS parameter generating policy and/or the QoS parameter generator to the QoS parameter generator after the QoS parameter generating policy and/or the QoS parameter generator generates the QoS parameter and/the QoS parameter and the QoS parameter generator.

The period of time during which the QoS parameters are run for a period of time includes any period of time from when the QoS parameters start to when the QoS parameters do not meet QoE and/or QoS parameter requirements.

In the embodiment of the present application, the domain control node may trigger the first network node to perform adjustment in other manners, and the triggering manner is not specifically limited.

Fig. 8 is a flowchart of a method for managing qos parameters according to an embodiment of the present application, as shown in fig. 8, where the method is applied to a first network node in the wireless communication system 100 shown in fig. 1, and the embodiment of the present application is not limited thereto specifically, and the method includes:

step 801, a first network node obtains an end-to-end QoS parameter requirement.

Wherein the QoS parameter requirement carries a QoS parameter and an expected value of the QoS parameter.

In the embodiment of the present application, the obtaining of the end-to-end QoS parameter requirement in step 801 may be implemented by step A1 or may be implemented by step A2:

In step A1, the first network node receives QoS parameter requirements sent by an application function AF or a terminal device UE.

And step A2, the first network node obtains QoS parameter requirements defined by standards for the service.

Step 802, the first network node generates QoS configuration of each domain based on at least one of policy information provided by the policy control function PCF, subscription data provided by the unified data management UDM, the QoS parameter requirements, network resource usage status and QoS monitoring status.

In the embodiment of the application, the first network node generates the QoS parameters of each domain based on policy information provided by PCF, subscription data provided by UDM, qoS parameters in QoS parameter demands, expected values of the QoS parameters, network resource use states and QoS monitoring states.

In the embodiment of the application, the first network node generates a QoS parameter generation strategy and/or the QoS parameter adjustment strategy and/or the QoS parameter generator of each domain at least based on at least one of strategy information provided by PCF and subscription data provided by UDM.

In the embodiment of the application, the network resource use state and the QoS monitoring state are issued to the first network node in advance by the domain control node.

In some embodiments, the network resource usage status includes at least one of: the number of processes that can run in the domain, the number of processes in the blocked state, the amount of memory that is free, and the free time.

In the embodiment of the present application, the QoS monitoring status includes at least one of the following: maximum traffic bit rate, time delay, packet loss rate, computational efficiency.

In the embodiment of the application, the QoS configuration further comprises QoS performance reporting configuration. The QoS performance reporting configuration carries at least one of: reporting the period; triggering an event; the QoS parameters of the performance need to be reported. Wherein the triggering event comprises one of: at least one QoS parameter cannot reach a configuration index value; the available resources exceed the configuration threshold.

The QoS performance reporting configuration includes QoS parameters that need to report performance, so that the first network node may issue the QoS performance reporting configuration for at least some QoS parameters, so that the domain control node periodically or event triggers to report a QoS monitoring state of at least some QoS parameters.

Here, for periodically reporting the QoS monitoring state, the QoS performance reporting configuration needs to carry a reporting period and a trigger event, that is, when the trigger event occurs, the QoS monitoring state is periodically reported. For event-triggered reporting of QoS monitoring status, qoS performance reporting configuration needs to carry triggering events.

Step 803, the first network node issues the QoS configuration of different domains to the domain control nodes.

Wherein the QoS configuration comprises at least one of:

QoS parameters;

QoS parameter generation strategy;

QoS parameter adjustment strategy;

QoS parameter generator.

In some embodiments, the first network node adjusts the first QoS parameter value or the second QoS parameter value of the second domain in case the first network node receives the first QoS parameter of the first domain fed back by the control node of the first domain fails to meet the QoE and/or QoS parameter requirements. Wherein the first QoS parameter is one or more QoS parameters and the second QoS parameter is a QoS parameter different from the first QoS parameter.

Step 804, the domain control node receives the QoS configuration issued by the first network node.

In some embodiments, in the event that any of the QoS parameters in the domain control node do not meet QoE and/or QoS parameter requirements, the domain control node adjusts one or more of the QoS parameters that are different from the any of the QoS parameters.

It should be noted that, in this embodiment, the descriptions of the same steps and the same content as those in other embodiments may refer to the descriptions in other embodiments, and are not repeated here.

Fig. 9 is a schematic interaction diagram of a first network node and a plurality of domain control nodes according to an embodiment of the present application. As shown in fig. 9:

Step 901, a first network node obtains an end-to-end QoS parameter requirement.

In the embodiment of the present application, the first network node obtains the end-to-end QoS parameter requirement from the AF (through the NEF) or the UE, and may directly obtain the end-to-end QoS parameter requirement defined by the standard for a certain service.

Step 902, generating QoS parameters of each domain.

In the embodiment of the application, the first network node divides the QoS parameter values according to domains, and generates QoS parameters of each domain based on at least one of policy information provided by PCF, user subscription data provided by UDM, end-to-end QoS parameter requirements, network resource use state and QoS monitoring state.

Step 903, the first network node issues QoS parameters of each domain to the domain control node of each domain.

In the embodiment of the application, the first network node sends the divided parameters to each domain control node, such as SMF in the core network and CU in the access network.

Taking an example that the domain control node of each domain includes a domain control node 1 and a domain control node 2, the first network node issues QoS parameters corresponding to the domain control node 1, and the first network node issues QoS parameters corresponding to the domain control node 2.

In some embodiments, the QoS configuration may carry a QoS performance reporting configuration.

And 904, reporting the QoS monitoring state by the control nodes of each domain.

Each domain control node reports the QoS monitoring state based on the QoS performance reporting configuration and the period/event trigger.

Taking the example that the domain control node of each domain includes the domain control node 1 and the domain control node 2, the domain control node 1 reports the QoS monitoring state, and the domain control node 2 reports the QoS monitoring state.

Step 905, the first network node adjusts QoS parameters of each domain.

In the embodiment of the application, the QoS monitoring state received by the first network node is used for adjusting QoS parameters of each domain based on the QoS monitoring state; wherein adjusting the QoS parameters of each domain includes adjusting the QoS parameters of each domain and the corresponding QoS parameter values.

Step 906, the first network node sends the adjusted QoS parameter configuration to each domain control node.

Taking the example that the domain control node of each domain includes the domain control node 1 and the domain control node 2, the first network node issues the adjusted QoS parameters corresponding to the domain control node 1, and the first network node issues the adjusted QoS parameters corresponding to the domain control node 2.

Fig. 10 is a schematic interaction diagram of a first network node and a plurality of domain control nodes according to an embodiment of the present application. As shown in fig. 10:

Step 1001, generating a QoS parameter generation policy or QoS parameter generator or QoS parameter adjustment policy for each domain.

In the embodiment of the application, the first network node generates a QoS parameter generation strategy or a QoS parameter generator or a QoS parameter adjustment strategy of each domain based on at least one of strategy information provided by PCF and user subscription data provided by UDM.

Step 1002, the first network node issues a QoS parameter generation policy or a QoS parameter generator or a QoS parameter adjustment policy for each domain to a domain control node for each domain.

In the embodiment of the application, after each domain control node receives each domain QoS parameter generation strategy or QoS parameter generator or QoS parameter adjustment strategy, qoS parameters are generated; and, each domain control node can implement adjustment between intra-domain QoS parameters based on QoS parameter generation policies or QoS parameter generator or QoS parameter adjustment policies.

For example, taking a case that the domain control node of each domain includes a domain control node 1 and a domain control node 2, the first network node issues a QoS parameter generation policy or a QoS parameter generator or a QoS parameter adjustment policy corresponding to the domain control node 1, and the first network node issues a QoS parameter generation policy or a QoS parameter generator or a QoS parameter adjustment policy corresponding to the domain control node 2.

And step 1003, the control node of each domain reports the QoS monitoring state.

In the embodiment of the application, when the QoS parameter generation strategy or the QoS parameter generator or the QoS parameter adjustment strategy can not generate the intra-domain QoS parameters which can meet the QoE and/or QoS parameter requirements, the QoS performance reporting is triggered.

Step 1004, the first network node adjusts the QoS parameter generation policy or QoS parameter generator or QoS parameter adjustment policy of each domain.

Step 1005, issue the QoS parameter generation policy or QoS parameter generator or QoS parameter adjustment policy of each domain after adjustment to each domain control node.

Taking the example that the domain control node of each domain includes the domain control node 1 and the domain control node 2, the first network node issues the adjusted QoS parameter generating policy or QoS parameter generator or QoS parameter adjusting policy corresponding to the domain control node 1, and the first network node issues the adjusted QoS parameter generating policy or QoS parameter generator or QoS parameter adjusting policy corresponding to the domain control node 2.

In the embodiment of the application, the QoS parameter generation strategy or QoS parameter adjustment strategy or QoS parameter generator of each domain is updated at least based on QoS strategy information and QoS monitoring state.

Fig. 11 is a flowchart of a method for managing qos parameters according to an embodiment of the present application, as shown in fig. 11, where the method is applied to a first network node in the wireless communication system 100 shown in fig. 1, and the embodiment of the present application is not limited thereto specifically, and the method includes:

step 1101, the first network node sends a QoS parameter adjustment request to a second network node of the second network.

Wherein, the QoS parameter adjustment request carries at least one of the following:

in the embodiment of the application, a first network QoS monitoring state corresponding to a first network node; qoS parameters to be adjusted; advice for QoS parameters to be adjusted; qoS parameter policy suggestions to be adjusted; the QoS parameter generator to be adjusted suggests.

In the embodiment of the application, the first network node and the second network node are two different network nodes with specific same functions in different networks.

It should be noted that, the meeting of QoS requirements of Long Term Evolution Voice bearer (VoLTE) or new air-interface Voice bearer (Voice over New Radio, voNR) services involves two networks, namely, a calling user network and a called user network. In the related art, the network node performs adjustment based on local information only, and does not know the end-to-end overall QoS status. For example, the calling UE serving base station may configure a longer discontinuous reception period (Discontinuous Reception cycle, DRX cycle) for the calling UE based on the channel quality condition to reduce the terminal power consumption, and the configuration may also meet the PDB requirement of the calling side. But this adjustment may result in the end-to-end VoLTE/VoNR traffic QoS requirements not being met, as the channel quality of the called UE may be poor. Therefore, it is necessary to have the QoS monitoring status or QoS parameter adjustment requests interacted between the first network nodes of the two networks to meet the end-to-end traffic demand.

Fig. 12 is a diagram showing QoS distribution of communication situations of a calling subscriber network and a called subscriber network in the related art. Among them, a calling subscriber Network such as an Access Network (a side) and a called subscriber Network such as a B side Access Network (a side) include a UE and a policy charging enforcement function (Policy and Charging Enforcement Function, PCEF). The PCEF of the calling subscriber network and the PCEF of the called subscriber network have a range of standardized Quasi-location (QCl) features between the network (IP) layers (Scope of the standardized QCl characteristics). Communication between the calling subscriber network and the called subscriber network is via a Backbone network (Backbone) having a higher bandwidth and a higher reliability. The reception/transmission (Send/Rcv) of the user network at the Application/Service Level is opposite.

Step 1102, the second network node responds to the QoS parameter adjustment request, and generates a response message.

Wherein the response message carries at least one of:

the QoS parameter to be adjusted takes the value suggestion or confirmation value;

suggested QoS parameter policies or acknowledgement values to be adjusted;

suggested QoS parameters to be adjusted generator or acknowledgement values.

In the embodiment of the application, the QoS parameter value suggestion or confirmation value to be adjusted refers to the QoS parameter value suggestion to be adjusted or the QoS parameter confirmation value to be adjusted; the suggested QoS parameter policy or acknowledgement value to be adjusted refers to the suggested QoS parameter policy to be adjusted or the suggested QoS parameter policy acknowledgement value to be adjusted; the suggested QoS parameter generator to be adjusted or the acknowledgement value refers to the suggested QoS parameter generator to be adjusted or the suggested QoS parameter generator to be adjusted acknowledgement value.

In the embodiment of the present application, the second network node may respond to the QoS parameter adjustment request according to the QoS monitoring state of the second network, and give the corresponding QoS parameter to be adjusted or the QoS parameter policy to be adjusted or the suggested value or the acknowledgement value of the QoS parameter generator to be adjusted.

Step 1103, the first network node receives the response message.

Step 1104, the first network node sends an acknowledgement message to the second network node.

The confirmation message carries the concrete proposal adopted; or the acknowledgement message carries at least one of:

whether to adopt the value of the suggested QoS parameter to be adjusted;

whether to adopt the QoS parameter strategy to be adjusted of suggestion;

whether to employ a proposed QoS parameter generator to be adjusted.

Step 1105, the first network node generates a QoS configuration.

In the embodiment of the present application, the first network node may generate the QoS configuration according to the corresponding QoS parameter to be adjusted or the QoS parameter policy to be adjusted or the suggested value or the acknowledgement value of the QoS parameter generator to be adjusted of the second network node in the response message, and based on policy information provided by the PCF, subscription data provided by the UDM, the use state of the first network resource, and the QoS monitoring state of the first network. Of course, the first network node may update the QoS configuration pre-generated by the first network node according to the corresponding QoS parameter to be adjusted or the QoS parameter policy to be adjusted or the suggested value or the acknowledgement value of the QoS parameter generator to be adjusted of the second network node in the response message. The embodiment of the present application is not particularly limited in this regard.

Step 1106, the first network node issues QoS configurations of different domains to each domain control node.

Wherein the QoS configuration comprises at least one of:

QoS parameters;

QoS parameter generation strategy;

QoS parameter adjustment strategy;

QoS parameter generator.

Step 1107, the domain control node receives the QoS configuration issued by the first network node.

Fig. 13 is an interaction schematic diagram of a first network node of a first network and a second network node of a second network according to an embodiment of the present application.

Step 1301, the first network node sends a QoS parameter adjustment request to the second network node.

Wherein the request message includes at least one of the following: a first network QoS monitoring state, a desired adjustment QoS parameter; the first network comprises a first network node, a domain control node 1 and a domain control node 2; the second network comprises a second network node, a domain control node 3 and a domain control node 4.

In some embodiments, prior to performing step 1301, domain control node 1 and domain control node 2 report QoS monitoring status to the first network node; the domain control node 3 and the domain control node 4 report the QoS monitoring status to the second network node.

Step 1302, the second network node responds to the QoS parameter adjustment request, generates a response message, and sends the response message to the first network node.

Wherein the response message may carry at least one of: qoS parameter value suggestion or QoS parameter value confirmation value; suggested QoS parameter policies/generators or confirmed QoS parameter policies/generators.

In step 1303, the first network node receives the QoS parameter adjustment response message, confirms the QoS parameter adjustment response message, generates a confirmation message, and sends the confirmation message to the second network node.

Wherein the acknowledgement message carries at least an indication of whether or not to employ the proposed QoS parameter value/QoS parameter policy/generator, and may also carry which proposal to employ.

Step 1304, the first network node and the second network node respectively issue the updated QoS parameter values/QoS parameter policies/generators to the control nodes of each domain.

In the embodiment of the application, the first network node updates the QoS configuration of the first network based on the response message. The second network node may update the QoS configuration of the second network based on the acknowledgement message.

An embodiment of the present application provides a first network node, which may be used to implement the quality of service parameter management method provided in the embodiments corresponding to fig. 4, 8 and 11, and referring to fig. 14, the first network node 1400 includes:

a first sending module 1401, configured to send the QoS configuration of different domains to each domain control node; wherein the QoS configuration comprises at least one of: qoS parameters; qoS parameter generation strategy; qoS parameter adjustment strategy; qoS parameter generator.

In other embodiments of the present application, the QoS parameters include at least one of: qoS parameters related to connection/communication; qoS parameters related to computing power; qoS parameters associated with artificial intelligence AI; a QoS parameter related to security; qoS parameters related to perceived capability; qoS parameters related to data quality.

In other embodiments of the present application, the QoS parameters associated with the connection/communication include at least one of: resource type, priority, packet delay prediction, packet loss rate, maximum data burst, average window, allocation and reservation priority, reverse push QoS attribute, notification control; the QoS parameters associated with the computing power include at least one of: calculation accuracy and calculation efficiency; the AI-related QoS parameters include at least one of: training time-consuming, interpretable, performance index boundaries; the security-related QoS parameters include at least one of: storing the security level, calculating the security level and transmitting the security level; the QoS parameters related to the perceived capability include at least one of: distance resolution, angle resolution, speed resolution, perceived distance range, recognition rate, and imaging accuracy; the QoS parameters associated with the data quality include at least one of: feature redundancy, integrity, data accuracy, and data preparation are time consuming.

In other embodiments of the present application, qoS configurations are defined for associated flows that include at least one network protocol Flow IP Flow and/or a portion of an IP Flow.

In other embodiments of the present application, where the associated Flow is part of an IP Flow, the IP Flow includes different flows that are partitioned into IP flows based on data traffic characteristics.

In other embodiments of the present application, a QoS parameter generation policy and/or QoS parameter adjustment policy and/or QoS parameter generator is used to generate QoS parameters that meet the requirements for quality of experience QoE and/or QoS parameters for the user.

In other embodiments of the present application, the first processing module 1402 is configured to adjust one or more QoS parameters different from any one of the QoS parameters if any one of the QoS parameters does not meet the requirements for QoE and/or QoS parameters.

In other embodiments of the present application, the first processing module 1402 is configured to adjust the QoS parameter generating policy and/or the QoS parameter adjusting policy and/or the QoS parameter generator if any one of the QoS parameters does not meet the requirements for QoE and/or QoS parameters.

In other embodiments of the present application, the first network node has at least one of the following functions: the system has the functions of QoS parameter strategy or QoS parameter generator, and/or issues the generated QoS parameters of each domain to each domain control node; the system has the function of generating the QoS parameter policies of each domain or QoS parameter generators of each domain and/or sending the generated QoS parameter policies of each domain or QoS parameter generators of each domain to each domain control node.

In other embodiments of the present application, a first sending module 1401 is configured to send QoS identifiers to each domain;

the first sending module 1401 is further configured to send QoS identifiers and parameter values of QoS parameters corresponding to the QoS identifiers to each domain;

the first sending module 1401 is further configured to send QoS parameters and parameter values of the QoS parameters to each domain.

In other embodiments of the present application, the first receiving module 1403 is configured to obtain an end-to-end QoS parameter requirement; the QoS parameter requirements carry QoS parameters and expected values of QoS parameters.

In other embodiments of the present application, the first receiving module 1403 is configured to receive a QoS parameter requirement sent by the application function AF or the terminal device UE or a QoS parameter requirement for a service defined by a standard.

In other embodiments of the present application, the first processing module 1402 is configured to generate QoS configuration of each domain based on at least one of policy information provided by the PCF, subscription data provided by the UDM, qoS parameter requirements, network resource usage status, and QoS monitoring status.

In other embodiments of the present application, the first processing module 1402 is configured to adjust the first QoS parameter value or the second QoS parameter value of the second domain if the first QoS parameter of the first domain cannot meet the QoE and/or QoS parameter requirements.

In other embodiments of the present application, the first QoS parameter is one or more QoS parameters and the second QoS parameter is a QoS parameter different from the first QoS parameter.

In other embodiments of the present application, the QoS monitoring status includes at least one of: maximum traffic bit rate, time delay, packet loss rate, computational efficiency.

In other embodiments of the present application, the QoS configuration further includes a QoS performance reporting configuration.

In other embodiments of the present application, the QoS performance reporting configuration carries at least one of the following: reporting the period; triggering an event; the QoS parameters of the performance need to be reported.

In other embodiments of the present application, the triggering event comprises one of: at least one QoS parameter cannot reach a configuration index value; the available resources exceed the configuration threshold.

In other embodiments of the present application, a first sending module 1401 is configured to send a QoS parameter adjustment request to a second network node of a second network; the QoS parameter adjustment request carries at least one of the following: a first network QoS monitoring state; qoS parameters to be adjusted; advice for QoS parameters to be adjusted; qoS parameter policy suggestions to be adjusted; the QoS parameter generator to be adjusted;

a first receiving module 1403, configured to receive a response message sent by the second network node for the QoS parameter adjustment request;

A first sending module 1401 is configured to send an acknowledgement message to the second network node.

In other embodiments of the present application, the response message carries at least one of: the QoS parameter to be adjusted takes the value suggestion or confirmation value; suggested QoS parameter policies or acknowledgement values to be adjusted; suggested QoS parameters to be adjusted generator or acknowledgement values.

In other embodiments of the present application, the confirmation message carries a specific suggestion for adoption; or the acknowledgement message carries at least one of: whether to adopt the value of the suggested QoS parameter to be adjusted; whether to adopt the QoS parameter strategy to be adjusted of suggestion; whether to employ a proposed QoS parameter generator to be adjusted.

The description of the apparatus embodiments above is similar to that of the method embodiments above, with similar advantageous effects as the method embodiments. For technical details not disclosed in the embodiments of the apparatus of the present application, please refer to the description of the embodiments of the method of the present application.

It should be noted that, in the embodiment of the present application, if the above-mentioned test data generating method is implemented in the form of a software functional module, and sold or used as a separate product, the test data generating method may also be stored in a computer readable storage medium. Based on such understanding, the technical solution of the embodiments of the present application may be essentially or partly contributing to the related art, embodied in the form of a software product stored in a storage medium, including several instructions for causing a terminal device to execute all or part of the methods of the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read Only Memory (ROM), a magnetic disk, an optical disk, or other various media capable of storing program codes. Thus, embodiments of the application are not limited to any specific combination of hardware and software.

An embodiment of the present application provides a first network node, which may be used to implement the quality of service parameter management methods provided in the embodiments corresponding to fig. 4, 8 and 11, and referring to fig. 15, the first network node 1500 (the first network node 1400 in fig. 14 corresponds to the first network node 1500 in fig. 15) includes: a first processor 1501, a first memory 1502 and a first communication bus 1503, wherein:

a first communication bus 1503 is used to enable a communication connection between the first processor 1501 and the first memory 1502.

The first processor 1501 is configured to execute a computer program stored in the first memory 1502 to implement the quality of service parameter management method as provided in the corresponding embodiments of fig. 4, 8 and 11.

An embodiment of the present application provides a domain control node, which may be used to implement the quality of service parameter management method provided in the embodiments corresponding to fig. 4, 8 and 11, and referring to fig. 16, the domain control node 1600 includes:

a second receiving module 1601, configured to receive a QoS configuration issued by the first network node; wherein the QoS configuration comprises at least one of: qoS parameters; qoS parameter generation strategy; qoS parameter adjustment strategy; qoS parameter generator.

In other embodiments of the present application, the second processing module 1602 is configured to generate a policy based on the QoS parameters, and generate the QoS parameters.

In other embodiments of the present application, the second processing module 1602 is configured to adjust QoS parameters based on a QoS parameter adjustment policy.

In other embodiments of the present application, the second processing module 1602 is configured to generate QoS parameters based on the QoS parameter generator.

In other embodiments of the present application, the QoS parameter generator includes an AI model.

It should be noted that, in the embodiment of the present application, if the above-mentioned test data generating method is implemented in the form of a software functional module, and sold or used as a separate product, the test data generating method may also be stored in a computer readable storage medium. Based on such understanding, the technical solution of the embodiments of the present application may be essentially or partly contributing to the related art, embodied in the form of a software product stored in a storage medium, including several instructions for causing a terminal device to execute all or part of the methods of the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a magnetic disk or an optical disk. Thus, embodiments of the application are not limited to any specific combination of hardware and software.

An embodiment of the present application provides a domain control node, which may be used to implement the quality of service parameter management methods provided in the embodiments corresponding to fig. 4, 8 and 11, with reference to fig. 17, the domain control node 1700 (the domain control node 1600 in fig. 16 corresponds to the domain control node 1700 in fig. 17) includes: a second processor 1701, a second memory 1702 and a second communication bus 1703, wherein:

a second communication bus 1703 is used to implement a communication connection between the second processor 1701 and the second memory 1702.

The second processor 1701 is configured to execute a computer program stored in the second memory 1702 to implement a quality of service parameter management method as provided in the corresponding embodiments of fig. 4, 8 and 11.

Embodiments of the present application provide a computer readable storage medium storing a computer program executable by one or more processors to implement a quality of service parameter management method as provided by the corresponding embodiments of fig. 4, 8 and 11.

The computer readable storage medium may be a Read Only Memory (ROM), a programmable Read Only Memory (Programmable Read-Only Memory, PROM), an erasable programmable Read Only Memory (Erasable Programmable Read-Only Memory, EPROM), an electrically erasable programmable Read Only Memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), a magnetic random access Memory (Ferromagnetic Random Access Memory, FRAM), a Flash Memory (Flash Memory), a magnetic surface Memory, an optical disk, or a compact disk Read Only Memory (Compact Disc Read-Only Memory, CD-ROM), or the like; but may be various electronic devices such as mobile phones, computers, tablet devices, personal digital assistants, etc., that include one or any combination of the above-mentioned memories.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The foregoing embodiment numbers of the present application are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method described in the embodiments of the present application.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer application products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer application instructions. These computer application instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer application instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer application instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The foregoing description is only of the preferred embodiments of the present application, and is not intended to limit the scope of the application, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.

Claims

1. A quality of service parameter management method, the method comprising:

wherein the QoS configuration includes at least one of:

QoS parameters;

QoS parameter generation strategy;

QoS parameter adjustment strategy;

QoS parameter generator.

2. The method of claim 1, wherein the QoS parameters comprise at least one of:

QoS parameters related to connection/communication;

QoS parameters related to computing power;

QoS parameters associated with artificial intelligence AI;

a QoS parameter related to security;

QoS parameters related to perceived capability;

QoS parameters related to data quality.

3. The method of claim 2, wherein the connection/communication related QoS parameters include at least one of: resource type, priority, packet delay prediction, packet loss rate, maximum data burst, average window, allocation and reservation priority, reverse push QoS attribute, notification control;

the QoS parameters related to computing power include at least one of: calculation accuracy and calculation efficiency;

the AI-related QoS parameters include at least one of: training time-consuming, interpretable, performance index boundaries;

the security-related QoS parameters include at least one of: storing the security level, calculating the security level and transmitting the security level;

the QoS parameters related to the perceived capability include at least one of: distance resolution, angle resolution, speed resolution, perceived distance range, recognition rate, and imaging accuracy;

the QoS parameters associated with data quality include at least one of: feature redundancy, integrity, data accuracy, and data preparation are time consuming.

4. The method according to claim 1, wherein the QoS configuration is defined for associated flows comprising at least one network protocol Flow, IP Flow, and/or a part of one IP Flow.

5. The method of claim 4, wherein in the case where the associated Flow is part of one IP Flow, the one IP Flow comprises different flows divided into one IP Flow based on data traffic characteristics.

6. The method according to claim 1, wherein the QoS parameter generation policy and/or the QoS parameter adjustment policy and/or the QoS parameter generator is for generating the QoS parameters meeting user quality of experience, qoE, and/or QoS parameter requirements.

7. The method according to claim 1, wherein the method further comprises:

in case any one of the QoS parameters does not meet QoE and/or QoS parameter requirements, the first network node adjusts one or more of the QoS parameters that are different from the any one QoS parameter.

8. The method according to claim 1, wherein the method further comprises:

in case any one of the QoS parameters does not meet QoE and/or QoS parameter requirements, the first network node adjusts the QoS parameter generation policy and/or the QoS parameter adjustment policy and/or the QoS parameter generator.

9. The method according to claim 1, wherein the first network node has at least one of the following functions:

the function of QoS parameter strategy or QoS parameter generator is provided, and/or generated QoS parameters of each domain are issued to each domain control node;

the system has the function of generating the QoS parameter policies of each domain or QoS parameter generators of each domain and/or sending the generated QoS parameter policies of each domain or QoS parameter generators of each domain to each domain control node.

10. The method of claim 1, wherein the QoS parameter delivery method for each domain comprises one of:

the first network node issues QoS identification to each domain;

the first network node transmits the QoS identifier and the parameter value of the QoS parameter corresponding to the QoS identifier to each domain;

the first network node issues the QoS parameters and parameter values of the QoS parameters to each domain.

11. The method of claim 1, wherein prior to issuing the QoS configuration, the method further comprises:

the first network node obtains an end-to-end QoS parameter requirement; the QoS parameter requirements carry QoS parameters and expected values of the QoS parameters.

12. The method of claim 11, wherein the obtaining QoS parameter requirements comprises:

The first network node receives QoS parameter requirements sent by an application function AF or terminal equipment UE; or,

the first network node obtains QoS parameter requirements for the traffic defined by the standard.

13. The method of claim 11, further comprising, prior to issuing the configuration,

the first network node generates QoS configuration of each domain based on at least one of policy information provided by a policy control function PCF, subscription data provided by a unified data management UDM, the QoS parameter requirements, a network resource usage status and a QoS monitoring status.

14. The method of claim 13, wherein the first network node generates the domain-specific QoS configuration based on at least one of policy information provided by a policy control function PCF, subscription data provided by a unified data management UDM, the QoS parameter requirements, a network resource usage status, a QoS monitoring status, comprising:

in case the first QoS parameters of the first domain cannot meet QoE and/or QoS parameter requirements, the first network node adjusts the first QoS parameter value or the second QoS parameter value of the second domain.

15. The method of claim 14, wherein the first QoS parameter is one or more QoS parameters and the second QoS parameter is a QoS parameter different from the first QoS parameter.

16. The method according to any of claims 13 to 15, wherein the QoS monitoring status comprises at least one of:

maximum traffic bit rate, time delay, packet loss rate, computational efficiency.

17. The method of claim 1, wherein the QoS configuration further comprises a QoS performance reporting configuration.

18. The method of claim 17, wherein the QoS-performance reporting configuration carries at least one of:

reporting the period; triggering an event; the QoS parameters of the performance need to be reported.

19. The method of claim 18, wherein the triggering event comprises one of:

at least one QoS parameter cannot reach a configuration index value;

the available resources exceed the configuration threshold.

20. The method of claim 1, wherein prior to issuing the QoS configuration, the method further comprises:

the first network node sends a QoS parameter adjustment request to a second network node of a second network; the QoS parameter adjustment request carries at least one of the following:

a first network QoS monitoring state corresponding to the first network node; qoS parameters to be adjusted; advice for QoS parameters to be adjusted; qoS parameter policy suggestions to be adjusted; the QoS parameter generator to be adjusted;

The first network node receives a response message for the QoS parameter adjustment request sent by the second network node;

the first network node sends an acknowledgement message to the second network node.

21. The method of claim 20, wherein the response message carries at least one of:

the QoS parameter to be adjusted takes a value suggestion or confirmation value;

the suggested QoS parameter strategy or confirmation value to be adjusted;

the suggested QoS parameters to be adjusted are generated or validated.

22. The method of claim 20, wherein the confirmation message carries a specific suggestion of adoption; or the acknowledgement message carries at least one of:

whether to adopt the suggested value of the QoS parameter to be adjusted;

whether to adopt the suggested QoS parameter strategy to be adjusted;

whether to employ the proposed QoS parameter generator to be adjusted.

23. A quality of service parameter management method, the method comprising:

wherein the QoS configuration includes at least one of:

QoS parameters;

QoS parameter generation strategy;

QoS parameter adjustment strategy;

QoS parameter generator.

24. The method of claim 23, wherein the method further comprises:

the domain control node generates a policy based on the QoS parameters, generating the QoS parameters.

25. The method of claim 23, wherein the method further comprises:

the domain control node adjusts the QoS parameters based on the QoS parameter adjustment policy.

26. The method of claim 23, wherein the method further comprises:

the domain control node generates the QoS parameters based on the QoS parameter generator.

27. The method of claim 26, wherein the QoS parameter generator comprises an AI model.

28. A first network node, the first network node comprising:

wherein the QoS configuration includes at least one of:

QoS parameters;

QoS parameter generation strategy;

QoS parameter adjustment strategy;

QoS parameter generator.

29. A first network node, the first network node comprising:

a first processor and a first memory for storing a computer program, the first processor for invoking and running the computer program stored in the first memory to perform the method of any of claims 1 to 22.

30. A domain control node, the domain control node comprising:

wherein the QoS configuration includes at least one of:

QoS parameters;

QoS parameter generation strategy;

QoS parameter adjustment strategy;

QoS parameter generator.

31. A domain control node, the domain control node comprising:

a second processor and a second memory for storing a computer program, the second processor being for invoking and running the computer program stored in the second memory for performing the method of any of claims 23 to 27.

32. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 22 or 23 to 27.