Quality of service control method, apparatus, and readable storage medium

Abstract

The application provides a quality of service control method and device and a readable storage medium. The method comprises the following steps: receiving uplink user data packets of a terminal; encapsulating the uplink user data packets into an SRv6 data packet format, wherein an SRv6 data packet header SRH contains quality of service (QoS) flow information, the QoS flow information comprises a QFI, and the QFI is used for indicating a QoS flow; and sending the SRv6 data packet carrying the QFI to a user plane function (UPF), wherein the UPF is used for performing corresponding operations according to the QFI. The QoS requirement of a user is guaranteed.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, and in particular to a quality of service control method and device and a readable storage medium. BACKGROUND

[0002] SRv6 is a new generation of IP carrying protocol based on IPv6 and source routing, which can realize network protocol simplification and application level SLA guarantee, and will be the basis for building intelligent IP network in the 5G and cloud era. In SRv6, SRv6 segment identifier (SID) refers to an identifier that defines a certain network function and represents network instructions. The SID is referred to as SRv6 SID (here referring to SRv6 segment identifier SID), which adopts the form of IPv6 address, but does not correspond to the IPv6 address of any interface included in the SR node.

[0003] A new SRv6 Behavior, Args.Mob.Session, is defined in IETF RFC 9433, which extends the extension of the Quality of Service (QoS) flow identifier (QFI) related field to meet the QoS requirement.

[0004] However, Args.Mob.Session is a SID granularity, and in a mobile network based on SRv6 user plane, the allocation of SIDs is not necessarily a QoS flow granularity. If a corresponding SID is allocated for each Protocol Data Unit (PDU) Session UPF, after the SID applies Args.Mob.Session, the extension field can only be applied to one QoS flow, and cannot correspond to multiple QoS flows in the PDU Session, that is, other QoS flows in the PDU Session cannot be identified. Therefore, the prior art cannot realize QoS control of SIDs applied to different PDU Sessions or different QoS flows, and thus cannot guarantee the QoS requirement of users. SUMMARY

[0005] The present application provides a quality of service control method and device and a readable storage medium, which solve the technical problem that the prior art cannot realize QoS control of SIDs applied to different PDU Sessions or different QoS flows, and thus cannot guarantee the QoS requirement of users.

[0006] In a first aspect, the present application provides a quality of service control method applied to a radio access network (RAN), the method comprising:

[0007] an uplink user data packet of the receiving terminal;

[0008] encapsulating the uplink user data packet into a new generation IP bearer protocol SRv6 data packet format based on IPv6 and source routing, wherein a service quality QoS flow information is contained in a SRv6 packet header SRH, and the QoS flow information comprises a quality of service flow identifier QFI, which is used to indicate a QoS flow;

[0009] sending the SRv6 data packet carrying the QFI to a user plane function UPF, which is used to perform a corresponding operation according to the QFI.

[0010] In the embodiments of the present application, the received uplink user data packet is encapsulated and encapsulated into an SRv6 data packet format comprising at least QoS flow information of the QFI, so as to indicate a corresponding QoS flow, and the SRv6 data packet carrying the QFI is sent to the UPF, and the UPF performs a corresponding operation based on the indicated QoS flow, so as to realize QoS control of the SID applied to different PDUSessions or different QoS flows, and further guarantee the QoS requirement of the user.

[0011] Optionally, the encapsulating the uplink user data packet into the new generation IP bearer protocol SRv6 data packet format based on IPv6 and source routing comprises:

[0012] if the SRv6 segment identifier SID is single protocol data unit session PDU Session granularity, the uplink user data packet is encapsulated into the SRv6 data packet format by using a Tag field in the SRH to carry QoS flow information, or using an extension field in the SRH to carry QoS flow information;

[0013] if the SID is multi-PDU Session granularity, the uplink user data packet is encapsulated into the SRv6 data packet format by using an extension field in the SRH to carry QoS flow information;

[0014] if the SID is QoS granularity, the uplink user data packet is encapsulated into the SRv6 data packet format by using a Tag field in the SRH to carry QoS flow information, or defining a SID behavior to carry QoS flow information through an Argument field of the SID in the SRH.

[0015] In the embodiments of the present application, different encapsulation strategies are supported based on different SID granularities, and then QoS flow information encapsulation is realized according to the corresponding strategies, so that the UPF can perform corresponding operations (such as rate control, counting, etc.) according to the QFI carried by the encapsulated SRv6 data packet, thereby realizing QoS control based on the SRv6 user plane. The problem that one SID can only bind one QoS flow information in the prior art, resulting in that after the SID applies Args.Mob.Session behavior, it can only be applied to one QoS flow, and the identification and positioning of multiple QoS flows in a PDU Session cannot be realized, is solved. At the same time, the problem of excessive occupation and waste of storage resources and processing resources in the UPF node caused by the increase in the number of SIDs on the UPF due to different QoS flows and different SIDs of a PDU session is also solved. The QoS control of the SID applied to different PDU Sessions or different QoS flows can be realized while resources are saved.

[0016] Optionally, if the SID is a single PDU Session granularity, the encapsulating the uplink user data packet into an SRv6 data packet format comprises:

[0017] When encapsulating the SRH for the uplink user data packet, encapsulating QoS flow information into a Tag field of the SRH; the QoS flow information further comprises a reflective quality of service identifier RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS; or

[0018] When encapsulating the SRH for the uplink user data packet, encapsulating QoS flow information into an extension field of the SRH; the QoS flow information further comprises an RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS.

[0019] Optionally, the encapsulating the QoS flow information into the Tag field of the SRH comprises:

[0020] A flag bit Flag in the Tag field of the SRH is set to determine whether the Tag field of the SRH carries QoS flow information.

[0021] The QFI and the RQI in the QoS flow information are encapsulated into the Tag field of the SRH, respectively.

[0022] In the embodiments of the present application, if the SID is single-PDU Session granularity, a flag bit Flag in the Tag field of the SRH is set, and when the flag bit Flag is a self-defined or specified arbitrary value, it is indicated that the Tag field of the SRH carries QoS flow information. The QoS flow information can include QFI and RQI. The corresponding QoS flow is determined by the QFI, and whether the reflective QoS is enabled is determined by the RQI.

[0023] Optionally, the extension field is used to indicate the type, length and value of an information element; and the encapsulation of the QoS flow information into the extension field of the SRH includes:

[0024] The QFI and the RQI are respectively encapsulated into the extension field of the SRH.

[0025] The flag bit Flag in the SRH is set to determine that the Map field in the extension field of the SRH is invalid or ignored. The Map field is used to indicate the mapping relationship between the PDU Session ID and the UE ID, and the extension field is used to determine the corresponding QoS flow.

[0026] In the embodiments of the present application, if the SID is single-PDU Session granularity, the QFI and the RQI are first respectively encapsulated into the extension field of the SRH. The flag bit Flag in the SRH is set, and when the flag bit Flag is a self-defined or specified arbitrary value, it is indicated that the Map field in the extension field of the SRH is invalid or ignored. Therefore, the corresponding QoS flow is determined by the QoS flow information carried in the extension field of the SRH.

[0027] Optionally, if the SID is multi-PDU Session granularity, the encapsulation of the uplink user data packet into the SRv6 packet format includes:

[0028] When the SRH is encapsulated for the uplink user data packet, the QoS flow information is encapsulated into the extension field of the SRH.

[0029] Optionally, the extension field is used to indicate the type, length and value of an information element, and the QoS flow information further includes the mapping relationship between the PDU Session ID and the UE ID and the RQI. The RQI is used to indicate whether the reflective QoS of a QoS flow is enabled. The encapsulation of the QoS flow information into the extension field of the SRH includes:

[0030] The QFI and the RQI are respectively encapsulated into the extension field of the SRH.

[0031] By setting a flag Flag in the SRH, it is determined that a Map field in an extension field of the SRH is effective, and the Map field is used to indicate a mapping relationship between a PDU Session ID and a UE ID.

[0032] The extension field is used to determine a specified QoS flow of a specified PDU session of a corresponding user.

[0033] In the embodiments of the present application, if the SID is a multi-PDU Session granularity, the QFI and the RQI can be respectively encapsulated into the extension field of the SRH. By setting a flag Flag in the SRH, it is indicated that the Map field in the extension field of the SRH is effective when the flag Flag is a self-defined or specified arbitrary value. Therefore, by the mapping relationship between the PDU Session ID and the UE ID carried in the extension field of the SRH, a specified QoS flow of a specified PDU session of a corresponding user is determined, and whether to enable reflective QoS is determined by the RQI.

[0034] Optionally, if the SID is a QoS granularity, the encapsulation of the uplink user data packet into the SRv6 data packet format comprises:

[0035] QoS flow information is encapsulated into an Argument field of the SID in the SRH, and the SID is used to determine a QoS flow.

[0036] Optionally, the QoS flow information further comprises an RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS. The encapsulation of the QoS flow information into the Argument field of the SID in the SRH comprises:

[0037] QFI and RQI are respectively encapsulated into the Argument field of the SID in the SRH, or

[0038] A mapping relationship between QFI, RQI and the SID is encapsulated into the Argument field of the SID in the SRH, and the mapping relationship between the QFI, the RQI and the SID is used to determine QoS flow information.

[0039] In the embodiments of the present application, if the SID is a QoS granularity, the QFI and the RQI are respectively encapsulated into the Argument field of the SID in the SRH, or the mapping relationship between the QFI, the RQI and the SID is encapsulated into the Argument field of the SID in the SRH, and the corresponding QoS flow is determined by the Argument field of the SID in the SRH.

[0040] In a second aspect, the application provides a quality of service control method applied to a user plane function (UPF), the method comprising:

[0041] encapsulating a downlink user data packet of a UE into an SRv6 packet format, wherein an SRv6 packet header (SRH) contains QoS flow information, and wherein the QoS flow information comprises a QFI used to indicate a QoS flow;

[0042] sending the SRv6 packet carrying the QFI to an intermediate UPF, which is configured to send the SRv6 packet carrying the QFI to a radio access network (RAN); or

[0043] sending the SRv6 packet carrying the QFI to the RAN, which is configured to map the QoS flow to a corresponding data radio bearer (DRB) according to the QFI and corresponding QoS configuration information.

[0044] In the embodiments of the application, the downlink user data packet of a terminal UE is encapsulated into an SRv6 packet format containing at least QoS flow information of a QFI to indicate a corresponding QoS flow, and the SRv6 packet carrying the QFI is sent to an intermediate UPF, which sends the SRv6 packet to a RAN, or the SRv6 packet carrying the QFI is sent to the RAN. The RAN maps the QoS flow to a DRB based on the QFI and corresponding QoS configuration information, and then sends the SRv6 packet on the corresponding DRB, thereby realizing QoS control of an SID applied to different PDU Sessions or different QoS flows, and guaranteeing the QoS requirement of a user.

[0045] Optionally, the encapsulation of the downlink user data packet of the UE into the SRv6 packet format comprises:

[0046] if the SID is single-PDU Session granularity, the downlink user data packet is encapsulated into the SRv6 packet format by carrying QoS flow information in a Tag field of the SRH or using an extension field of the SRH to carry the QoS flow information;

[0047] if the SID is multi-PDU Session granularity, the downlink user data packet is encapsulated into the SRv6 packet format by using an extension field of the SRH to carry QoS flow information;

[0048] if the SID is QoS granularity, the downlink user data packet is encapsulated into the SRv6 packet format by using a Tag field of the SRH to carry QoS flow information or defining an SID behavior to carry QoS flow information in an Argument field of the SID of the SRH.

[0049] In the embodiments of the present application, different encapsulation strategies are supported based on different SID granularities, and then QoS flow information encapsulation is realized according to the corresponding strategies, so that the RAN can map the QoS flow to the DRB according to the QFI carried by the encapsulated SRv6 data packet and the corresponding QoS configuration information, thereby realizing QoS control. The problem that one SID can only bind one QoS flow information in the prior art, which leads to the problem that after the SID applies Args.Mob.Session behavior, it can only be applied to one QoS flow and cannot realize the identification and positioning of multiple QoS flows in a PDUSession, is solved. At the same time, the problem of excessive occupation and waste of storage resources and processing resources in the UPF node caused by the increase in the number of SIDs on the UPF due to different QoS flows of PDU sessions is also solved. The SID can be applied to the QoS control of different PDU sessions or different QoS flows while saving resources.

[0050] Optionally, if the SID is single-PDU Session granularity, the encapsulation of the downlink user data packet into an SRv6 data packet format comprises:

[0051] When encapsulating the SRH for the downlink user data packet, encapsulating QoS flow information into the Tag field of the SRH; the QoS flow information further comprises a reflective quality of service identifier RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS; or,

[0052] When encapsulating the SRH for the downlink user data packet, encapsulating QoS flow information into the extension field of the SRH; the QoS flow information further comprises an RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS.

[0053] Optionally, the encapsulation of the QoS flow information into the Tag field of the SRH comprises:

[0054] By setting a flag bit Flag in the Tag field of the SRH, it is determined whether the Tag field of the SRH carries QoS flow information.

[0055] The QFI and RQI in the QoS flow information are encapsulated into the Tag field of the SRH, respectively.

[0056] In the embodiments of the present application, if the SID is single-PDU Session granularity, a flag bit Flag in the Tag field of the SRH is set, and when the flag bit Flag is a self-defined or specified arbitrary value, it is indicated that the Tag field of the SRH carries QoS flow information. The QoS flow information can include QFI and RQI. The corresponding QoS flow is determined by the QFI, and whether the reflective QoS is enabled is determined by the RQI.

[0057] Optionally, the extension field is used to indicate the type, length and value of an information element; and the encapsulation of the QoS flow information into the extension field of the SRH includes:

[0058] The QFI and the RQI are respectively encapsulated into the extension field of the SRH.

[0059] The flag bit Flag in the SRH is set to determine that the Map field in the extension field of the SRH is invalid or ignored. The Map field is used to indicate the mapping relationship between the PDU Session ID and the UE ID, and the extension field is used to determine the corresponding QoS flow.

[0060] In the embodiments of the present application, if the SID is single-PDU Session granularity, the QFI and the RQI are first respectively encapsulated into the extension field of the SRH. The flag bit Flag in the SRH is set, and when the flag bit Flag is a self-defined or specified arbitrary value, it is indicated that the Map field in the extension field of the SRH is invalid or ignored. Therefore, the corresponding QoS flow is determined by the QoS flow information carried in the extension field of the SRH.

[0061] Optionally, if the SID is multi-PDU Session granularity, the encapsulation of the downlink user data packet into the SRv6 packet format includes:

[0062] When the SRH is encapsulated for the downlink user data packet, the QoS flow information is encapsulated into the extension field of the SRH.

[0063] Optionally, the extension field is used to indicate the type, length and value of an information element, and the QoS flow information further includes the mapping relationship between the PDU Session ID and the UE ID and the RQI. The RQI is used to indicate whether the reflective QoS of a QoS flow is enabled. The encapsulation of the QoS flow information into the extension field of the SRH includes:

[0064] The QFI and the RQI are respectively encapsulated into the extension field of the SRH.

[0065] By setting a flag Flag in the SRH, it is determined that a Map field in an extension field of the SRH is effective, and the Map field is used to indicate a mapping relationship between a PDU Session ID and a UE ID.

[0066] The extension field is used to determine a specified QoS flow of a specified PDU session of a corresponding user.

[0067] In the embodiments of the present application, if the SID is a multi-PDU Session granularity, the QFI and the RQI can be respectively encapsulated into the extension field of the SRH. By setting a flag Flag in the SRH, it is indicated that the Map field in the extension field of the SRH is effective when the flag Flag is a self-defined or specified arbitrary value. Therefore, by the mapping relationship between the PDU Session ID and the UE ID carried in the extension field of the SRH, a specified QoS flow of a specified PDU session of a corresponding user is determined, and whether to enable reflective QoS is determined by the RQI.

[0068] Optionally, if the SID is a QoS granularity, the encapsulation of the downlink user data packet into the SRv6 packet format comprises:

[0069] QoS flow information is encapsulated into an Argument field of the SID in the SRH, and the SID is used to determine a QoS flow.

[0070] Optionally, the QoS flow information further comprises an RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS. The encapsulation of the QoS flow information into the Argument field of the SID in the SRH comprises:

[0071] The QFI and the RQI are respectively encapsulated into the Argument field of the SID in the SRH, or

[0072] A mapping relationship between the QFI, the RQI and the SID is encapsulated into the Argument field of the SID in the SRH, and the mapping relationship between the QFI, the RQI and the SID is used to determine QoS flow information.

[0073] In the embodiments of the present application, if the SID is a QoS granularity, the QFI and the RQI are respectively encapsulated into the Argument field of the SID in the SRH, or the mapping relationship between the QFI, the RQI and the SID is encapsulated into the Argument field of the SID in the SRH, and a corresponding QoS flow is determined by the Argument field of the SID in the SRH.

[0074] In a third aspect, the application provides a quality of service control device, which is applied to a radio access network (RAN), and the device comprises:

[0075] a receiving unit, configured to receive uplink user data packets of a terminal;

[0076] a processing unit, configured to encapsulate the uplink user data packets into an SRv6 packet format, wherein an SRv6 packet header (SRH) contains quality of service (QoS) flow information; and wherein the QoS flow information comprises a QFI, which is used to indicate a QoS flow.

[0077] a sending unit, configured to send the SRv6 packet carrying the QFI to a user plane function (UPF), and the UPF is configured to perform corresponding operations according to the QFI.

[0078] In a fourth aspect, the application provides a quality of service control device, which is applied to a user plane function (UPF), and the device comprises:

[0079] a processing unit, configured to encapsulate downlink user data packets of a terminal into an SRv6 packet format, wherein an SRv6 packet header (SRH) contains QoS flow information; and wherein the QoS flow information comprises a QFI, which is used to indicate a QoS flow.

[0080] a sending unit, configured to send the SRv6 packet carrying the QFI to an intermediate UPF, and the intermediate UPF is configured to send the SRv6 packet carrying the QFI to a radio access network (RAN); or

[0081] send the SRv6 packet carrying the QFI to the RAN, and the RAN is configured to map the QoS flow to a corresponding data radio bearer (DRB) according to the QFI and corresponding QoS configuration information.

[0082] In a fifth aspect, the application provides a quality of service control device, which is applied to a radio access network (RAN), and the device comprises a memory, a transceiver, and a processor:

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

[0084] receive uplink user data packets of a terminal;

[0085] encapsulate the uplink user data packets into an SRv6 packet format, wherein an SRv6 packet header (SRH) contains quality of service (QoS) flow information, and the QoS flow information comprises a QFI, which is used to indicate a QoS flow.

[0086] send the SRv6 data packet carrying the QFI to a user plane function (UPF), and the UPF is configured to perform corresponding operations according to the QFI.

[0087] Optionally, the processor is configured to, when encapsulating the uplink user data packet into the SRv6 data packet format, specifically include:

[0088] If the SRv6 segment identifier (SID) is single-PDU session granularity, the uplink user data packet is encapsulated into the SRv6 data packet format by using a Tag field in the SRH to carry QoS flow information or using an extension field in the SRH to carry QoS flow information.

[0089] If the SID is multi-PDU session granularity, the uplink user data packet is encapsulated into the SRv6 data packet format by using an extension field in the SRH to carry QoS flow information.

[0090] If the SID is QoS granularity, the uplink user data packet is encapsulated into the SRv6 data packet format by using a Tag field in the SRH to carry QoS flow information or defining a SID behavior to carry QoS flow information through an Argument field in the SRH.

[0091] Optionally, the processor is configured to, when the SID is single-PDU session granularity and the uplink user data packet is encapsulated into the SRv6 data packet format, specifically include:

[0092] When the SRH is encapsulated for the uplink user data packet, QoS flow information is encapsulated into a Tag field in the SRH; the QoS flow information further includes an RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS; or

[0093] When the SRH is encapsulated for the uplink user data packet, QoS flow information is encapsulated into an extension field in the SRH; the QoS flow information further includes an RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS.

[0094] Optionally, the processor is configured to, when the SID is multi-PDU session granularity and the uplink user data packet is encapsulated into the SRv6 data packet format, specifically include:

[0095] When the SRH is encapsulated for the uplink user data packet, QoS flow information is encapsulated into an extension field in the SRH.

[0096] Optionally, the processor is configured to, when the SID is QoS granularity, encapsulate the uplink user data packet into an SRv6 packet format, and specifically includes:

[0097] encapsulate QoS flow information into an Argument field of the SID in the SRH, wherein the SID is used to determine a QoS flow.

[0098] In a sixth aspect, the present application provides a quality of service control device, the device is applied to a user plane function UPF, the device includes a memory, a transceiver, and a processor:

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

[0100] encapsulate downlink user data packets for a UE into an SRv6 packet format, wherein an SRv6 packet header SRH contains QoS flow information; wherein the QoS flow information includes a QFI, and the QFI is used to indicate a QoS flow;

[0101] send the SRv6 packet carrying the QFI to an intermediate UPF, and the intermediate UPF is configured to send the SRv6 packet carrying the QFI to a RAN; or

[0102] send the SRv6 packet carrying the QFI to a RAN, and the RAN is configured to map a QoS flow to a corresponding data radio bearer DRB according to the QFI and corresponding QoS configuration information.

[0103] Optionally, the processor is configured to, when encapsulating the downlink user data packets for the UE into the SRv6 packet format, specifically include:

[0104] if the SID is single-PDU session granularity, encapsulate the downlink user data packets into the SRv6 packet format by using a Tag field in the SRH to carry QoS flow information, or using an extension field in the SRH to carry QoS flow information;

[0105] if the SID is multi-PDU session granularity, encapsulate the downlink user data packets into the SRv6 packet format by using an extension field in the SRH to carry QoS flow information;

[0106] If the SID is QoS granularity, the downlink user data packet is encapsulated into the SRv6 packet format by carrying QoS flow information in the Tag field in the SRH or defining the SID behavior to carry QoS flow information in the Argument field of the SID in the SRH.

[0107] Optionally, when the SID is single-PDU Session granularity, the processor encapsulates the downlink user data packet into the SRv6 packet format, and specifically includes:

[0108] When encapsulating the SRH for the downlink user data packet, the QoS flow information is encapsulated into the Tag field of the SRH; the QoS flow information further includes an RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS; or,

[0109] When encapsulating the SRH for the downlink user data packet, the QoS flow information is encapsulated into the extension field of the SRH; the QoS flow information further includes an RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS.

[0110] Optionally, when the SID is multi-PDU Session granularity, the processor encapsulates the downlink user data packet into the SRv6 packet format, and specifically includes:

[0111] When encapsulating the SRH for the downlink user data packet, the QoS flow information is encapsulated into the extension field of the SRH.

[0112] Optionally, when the SID is QoS granularity, the processor encapsulates the downlink user data packet into the SRv6 packet format, and specifically includes:

[0113] The QoS flow information is encapsulated into the Argument field of the SID in the SRH; and the SID is used to determine a QoS flow.

[0114] In a seventh aspect, the present application provides a processor-readable storage medium, which stores a computer program for causing a processor to execute the method of any one of the above aspects.

[0115] The application provides a service quality control method and device and a readable storage medium. First, uplink user data packets of a terminal are received, and then the uplink user data packets are encapsulated into a new generation IP bearing protocol SRv6 data packet format based on IPv6 and source routing, wherein a service quality QoS flow information is contained in a SRv6 data packet header SRH, the QoS flow information comprises a quality of service flow identifier QFI, and the QFI is used to indicate a QoS flow. The SRv6 data packet carrying the QFI is sent to a user plane function UPF, and the UPF is used to perform corresponding operations according to the QFI. That is, based on the received uplink user data packets, the uplink user data packets are encapsulated into the SRv6 data packet format of the QoS flow information at least comprising the QFI, so as to indicate the corresponding QoS flow, and the SRv6 data packet carrying the QFI is sent to the UPF, and corresponding operations are performed by the UPF based on the indicated QoS flow, so that the SID can be applied to QoS control of different PDU Sessions or different QoS flows, and the QoS demand of a user is ensured.

[0116] It should be understood that the content described in the foregoing summary section is not intended to define key or important features of the embodiments of the present application, nor is it intended to limit the scope of the present application. Other features of the present application will become apparent from the following description. BRIEF DESCRIPTION OF DRAWINGS

[0117] In order to more clearly illustrate the technical solutions in the application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or the prior art description. Obviously, the drawings in the following description are some embodiments of the present application, and those skilled in the art can also obtain other drawings according to these drawings without creative labor.

[0118] Figure 1 A schematic diagram for carrying QoS flow information by using a Tag field in an SRH is provided for an embodiment of the present application;

[0119] Figure 2 A schematic diagram for carrying QoS flow information by using a TLV field in an SRH is provided for an embodiment of the present application;

[0120] Figure 3 A schematic diagram for identifying QoS flow information by using an Argument field of an SRH is provided for an embodiment of the present application;

[0121] Figure 4 A flowchart of a service quality control method is provided for an embodiment of the present application;

[0122] Figure 5 A flowchart of a service quality control method is provided for another embodiment of the present application;

[0123] Figure 6 A structure diagram of a service quality control device provided by an embodiment of the present application is shown in FIG. 1.

[0124] Figure 7 A structure diagram of a service quality control device provided by another embodiment of the present application is shown in FIG. 2.

[0125] Figure 8 A structure diagram of a service quality control device provided by still another embodiment of the present application is shown in FIG. 3.

[0126] Figure 9 A structure diagram of a service quality control device provided by yet another embodiment of the present application is shown in FIG. 4. DETAILED DESCRIPTION

[0127] In the present application, the term "and / or" describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can represent the following three cases: A exists alone, A and B exist together, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after it.

[0128] In the embodiments of the present application, the term "multiple" means two or more, and other quantifiers are similar.

[0129] The technical solutions in the embodiments of the present application will be described clearly and completely in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, not all. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of the present application.

[0130] In order to clearly understand the technical solutions of the present application, the prior art solutions are first described in detail. The 5G QoS model is based on QoS flow, wherein the QoS flow is the finest granularity of QoS differentiation in a PDU session (i.e., PDU Session), and each QoS flow is identified by a unique QoS flow ID (QFI) in each PDU session. The 5G QoS model supports QoS flows that require guaranteed bit rates (GBR QoS flows) and QoS flows that do not require guaranteed bit rates (non GBR QoS flows).

[0131] For downlink (DL): in the user plane function (UPF) the data packets are compared with the packet detection rules (PDRs) established by the session management function (SMF) to classify the data packets. Each PDR is then associated with one or more QoS enforcement rules (QERs) that contain information on how to enforce, e.g. a specific rate. The QERs also include the QFI value to be added to the GTP-U header (N3 encapsulation header).

[0132] For uplink (UL): the UE application layer generates data packets that are first compared with those selected from the set of data packet filters in the UE. These data packet filters are checked in order of priority and when a match is found, the data packet is assigned a QFI. The assigned QFI and data packet are sent to the service data adaption protocol (SDAP) layer in the UE access-stratum (AS) that performs the mapping of the QFI to a data radio bearer (DRB) according to the available mapping rules. If a match is found, the data packet is sent on the corresponding DRB; if no match is found, the data packet is sent on a default DRB and the SDAP header contains the QFI so that the NG-RAN can decide whether to move the QFI to another DRB.

[0133] SRv6 is a new generation of IP carrying protocol based on IPv6 and source routing, which can unify traditional complex network protocols, realize network protocol simplification and application level SLA guarantee, and will be the basis for building intelligent IP network in the 5G and cloud era. In SRv6, the SRv6 segment identifier (SID) refers to an identifier that defines a certain network function and represents a network instruction. The SID is referred to as an SRv6 SID (here, the SRv6 segment identifier SID), which adopts an IPv6 address form, but does not correspond to the IPv6 address of any interface included in an SR node.

[0134] A new SRv6 Behavior, Args.Mob.Session, is defined in IETF RFC 9433, which extends the extension of the Quality of Service (QoS) Flow ID (QFI) related field to meet the QoS requirement.

[0135] However, Args.Mob.Session (i.e., providing charging, buffering or other purpose requirements provided by some mobile nodes for each PDU session; Args.Mob.Session argument format is used in combination with End.Map, End.DT4 / End.DT6 / End.DT46 and End.DX4 / End.DX6 / End.DX2 behaviors). Args.Mob.Session is applied in a scenario of a SID aggregating multiple PDU sessions. Because SRv6 SIDs are not necessarily instantiated per PDU session. Args.Mob.Session helps the UPF to perform per QFI and / or per PDU session granularity requirements, which is a SID granularity. In a mobile network based on SRv6 user plane, the allocation of SIDs is not necessarily QoS flow granularity. If the allocation of SIDs is PDU Session granularity, after the SID applies Args.Mob.Session, the extension field can only be applied to one QoS flow, and it is impossible to achieve 1 PDU Session to multiple QoS flow mapping. In addition, the combination of QFI+PDU Session ID described in Args.Mob.Session cannot uniquely identify a QoS flow, which may cause the QoS characteristics applied to the user to be inconsistent with the user's request, and thus cannot meet the user's requirements.

[0136] Therefore, the prior art cannot achieve QoS control of SIDs applied to different PDU sessions or different QoS flows, and thus cannot guarantee the QoS requirements of users.

[0137] The inventors have further found that to solve the problem that the prior art cannot achieve QoS control of SIDs applied to different PDU sessions or different QoS flows, and thus cannot guarantee the QoS requirements of users, the QoS Flow information can be encapsulated in the SRH of the SRv6 packet header when encapsulating the SRv6 packet format, and QoS Flow information encapsulation can be achieved based on different SID granularity, so as to achieve QoS control.

[0138] Therefore, based on the inventors' inventive research, the service quality control method and apparatus proposed in this application are presented. In this application, the received uplink user data packets are encapsulated into SRv6 data packets containing at least QFI QoS flow information to indicate the corresponding QoS flow. The SRv6 data packets carrying QFI are then sent to the UPF. The UPF performs corresponding operations based on the indicated QoS flow, enabling the application of SIDs to different PDU Sessions or different QoS flows for QoS control, thereby ensuring the user's QoS requirements. This solves the problem in the prior art where one SID can only be bound to one QoS flow information, resulting in the SID being applied to only one QoS flow after applying Args.Mob.Session behavior, thus failing to identify and locate multiple QoS flows in a PDU Session. It also solves the problem of the increased number of SIDs on the UPF due to different QoS flows and SIDs in different PDU sessions, leading to excessive occupation and waste of storage and processing resources in the UPF node. This method enables the application of SIDs to different PDU Sessions or different QoS flows for QoS control while saving resources.

[0139] The method and apparatus are based on the same concept of the application. Since the methods and apparatus solve problems in similar ways, the implementation of the apparatus and methods can refer to each other, and the repeated parts will not be described again.

[0140] The embodiments of this application will now be described with reference to the accompanying drawings.

[0141] QoS control is achieved by carrying or identifying QoS flow information in at least three ways:

[0142] Method 1: Use the Tag field in SRH to carry QoS Flow information.

[0143] Combination Figure 1 As shown, Figure 1 This application provides an embodiment of the use of the Tag field in SRH to carry QoS flow information, as shown in the diagram. Figure 1 As shown, the Tag field sets a flag bit. The value of the flag bit can be custom or specified (no specific limitation is made here). It is used to indicate whether the Tag field of SRH carries QoS flow information. For example, the flag bit can be 0 or 1. When the value of the flag bit is 1, it means that the field carries QoS flow information. When the value of the flag bit is 1, the flag bit is ignored, which can be interpreted as the field carrying QoS flow information being invalid or ignored.

[0144] QFI is used to identify QoS flows in the 5G system. RQI (Reflective QoS Indication) is used to indicate whether a QoS flow enables reflective QoS. The RQI value can be user-defined or specified (not specifically limited here), indicating whether a QoS flow enables reflective QoS. For example, RQI values ​​are 0 or 1. When the RQI value is 1, it means that the UE (terminal) enables reflective QoS; when the RQI value is 0, it means that the UE does not enable reflective QoS. This method is suitable for scenarios where the SID is at the single PDU Session granularity or QoS granularity. That is, each PDU Session's UPF has only one SID (single PDU Session granularity) corresponding to that PDU Session, or each QoS flow in each PDU Session has a corresponding SID (QoS granularity).

[0145] It should be noted that, Figure 1 The QFI and RQI lengths shown are only recommended options, merely examples, and not the only ones. No specific limitations are made regarding the QFI and RQI lengths here. Furthermore, the following... Figures 2-3 The QFI and RQI lengths mentioned are exemplary and not specifically limited.

[0146] Method 2: Use extended fields in SRH (e.g., TLV field) to carry QoS flow information.

[0147] QoS flow information is carried in the optional TLV (Extended Field) in the SRv6 packet header, which instructs the device to process the TLV.

[0148] Combination Figure 2 As shown, Figure 2 This application provides an embodiment of the use of the TLV field in the SRH to carry QoS flow information, as shown in the following diagram. Figure 2 As shown, a flag is set in the TLV field of the SRH. The flag value can be custom or specified (not specifically limited here). It is used to indicate whether the Map field in the extended fields of the SRH (the Map field is used to indicate the mapping relationship between PDU Session ID and UE ID) is effective. For example, the flag value can be 0 or 1. When the flag value is 1, it means that the Map field is effective. By combining the Map field, the specified QoS flow of the specified PDU session of the corresponding user is determined. When the flag value is 0, it means that the Map field is invalid or does not exist. It means that the subsequent fields of the flag will not be parsed, which can be interpreted as the QoS flow information indicated by the field being invalid or ignored. This method 2 is suitable for scenarios where the SID is at the single PDU Session granularity or the multi-PDU Session granularity.

[0149] QFI is used to identify QoS flows in the 5G system. RQI is used to indicate whether a QoS flow has reflective QoS enabled. The RQI value can be custom or specified (not specifically limited here), indicating whether a QoS flow has reflective QoS enabled. For example, RQI can be 0 or 1. When the RQI value is 1, it means that the UE has reflected QoS enabled; when the RQI value is 0, it means that the UE has not enabled reflective QoS.

[0150] Map(PDU Session ID, UE ID): Applicable to scenarios where multiple PDU sessions share a single SID. It uniquely identifies a user's QoS flow for a specific PDU session using Map(PDU Session ID, UE ID) and QFI, thus determining the specified QoS flow for that user's given PDU session. Figure 3 The length and format of the Map(PDU Session ID, UE ID) are merely examples and are not specifically limited.

[0151] Method 3: Define the Args.mob.QoS behavior of SID by identifying QoS flow information through the Argument field of SID in SRH.

[0152] Combination Figure 3 As shown, Figure 3 This is a schematic diagram illustrating how QoS flow information is identified through the Argument field of the SID in the SRH, as provided in the embodiments of this application. Figure 3 As shown, the Argument field carries QFI and RQI information, or mapping information between QFI and RQI and SID (referring to the mapping relationship used to determine QoS flow information), enabling user plane nodes (including RAN) to determine the user's QoS requirements based on the SID. Args.mob.QoS can be used in combination with End.Map, End.DT4 / End.DT6 / End.DT46, or End.DX4 / End.DX6 / End.DX2. This method 3 is suitable for scenarios where the SID is the QoS granularity.

[0153] QFI is used to identify QoS flows in the 5G system. RQI is used to indicate whether a QoS flow has reflective QoS enabled. The RQI value can be custom or specified (not specifically limited here), indicating whether a QoS flow has reflective QoS enabled. For example, RQI can be 0 or 1. When the RQI value is 1, it means that the UE has reflected QoS enabled; when the RQI value is 0, it means that the UE has not enabled reflective QoS.

[0154] Therefore, the field in the SRv6 packet header is set or extended to identify the carried QoS flow information, or a new SID behavior is defined, that is, the QoS information (herein referred to as QoS flow information) is carried in the Tag field in the SRH, the QoS information (herein referred to as QoS flow information) is carried in the optional TLA field in the SRH, and the QoS information (herein referred to as QoS flow information) is carried or mapped in the Argument field of the SID. Based on the QoS control method of the SRv6 user plane, the QoS control in the three cases of QoS flow granularity, single PDU session granularity and multi-PDU session granularity is realized, and the QoS requirements of the user are guaranteed.

[0155] Figure 4 The flowchart of the service quality control method provided by the embodiments of the present application is shown in FIG. 1, wherein the execution subject of the service quality control method provided by the embodiments of the present application is a radio access network (RAN), and the service quality control method provided by the embodiments of the present application includes the following steps. Figure 4

[0156] Step 101, receiving an uplink user data packet of a terminal.

[0157] Step 102, encapsulating the uplink user data packet into a new generation IP bearer protocol (SRv6) data packet format based on IPv6 and source routing.

[0158] The SRH in the SRv6 packet header includes quality of service (QoS) flow information, and the QoS flow information includes a QoS flow identifier (QFI) used to indicate a QoS flow.

[0159] In the embodiments of the present application, for the downlink, the RAN receives the uplink user data packet of the terminal, and then encapsulates the uplink user data packet into an SRv6 data packet format. In order to adapt to different SID granularity scenarios, when the uplink user data packet is encapsulated into the SRv6 data packet format, the SRH in the SRv6 packet header is used to encapsulate the QoS flow information or information used to indicate or determine the QoS flow information, so that the SRH carries the QoS flow information or the information used to indicate or determine the QoS flow information, wherein the QoS flow information includes a QFI used to indicate a QoS flow.

[0160] Step 103, sending the SRv6 data packet carrying the QFI to a user plane function (UPF), and the UPF is used to perform corresponding operations according to the QFI.

[0161] ​Specifically, the SRv6 data packet is sent to the UPF, the UPF determines a unique QoS flow according to the QFI carried by the SRv6 data packet, and then performs corresponding operations such as rate control, counting, etc. according to the characteristics of the QoS flow, such as rate, etc.

[0162] In the embodiment of the application, first, the uplink user data packet of the terminal is received, and then the uplink user data packet is encapsulated into a new generation IP bearer protocol SRv6 data packet format based on IPv6 and source routing, wherein the SRv6 data packet header SRH contains quality of service QoS flow information, the QoS flow information includes quality of service flow identifier QFI, and the QFI is used to indicate the QoS flow; the SRv6 data packet carrying the QFI is sent to the user plane function UPF, and the UPF is used to perform corresponding operations according to the QFI. That is, based on the received uplink user data packet, the uplink user data packet is encapsulated into an SRv6 data packet format including at least QoS flow information of the QFI, to indicate the corresponding QoS flow, and the SRv6 data packet carrying the QFI is sent to the UPF, and the UPF performs corresponding operations based on the indicated QoS flow, so as to realize the QoS control of the SID applied to different PDU Session or different QoS flow, and further guarantee the QoS requirement of the user.

[0163] Optionally, the encapsulation of the uplink user data packet into the SRv6 data packet format based on IPv6 and source routing includes:

[0164] If the SRv6 segment identifier SID is single protocol data unit session PDU Session granularity, the uplink user data packet is encapsulated into the SRv6 data packet format by using the Tag field in the SRH to carry the QoS flow information, or using the extension field in the SRH to carry the QoS flow information;

[0165] If the SID is multi-PDU Session granularity, the uplink user data packet is encapsulated into the SRv6 data packet format by using the extension field in the SRH to carry the QoS flow information;

[0166] If the SID is QoS granularity, the uplink user data packet is encapsulated into the SRv6 data packet format by using the Tag field in the SRH to carry the QoS flow information, or defining the SID behavior to carry the QoS flow information through the Argument field of the SID in the SRH.

[0167] Specifically, if the SRv6 segment identifier SID is single PDU Session granularity, the uplink user data packet can be encapsulated into SRv6 packet format based on mode 1 or mode 2; if the SRv6 segment identifier SID is multi-PDU Session granularity, the uplink user data packet can be encapsulated into SRv6 packet format based on mode 2; if the SRv6 segment identifier SID is QoS granularity, the uplink user data packet can be encapsulated into SRv6 packet format based on mode 1 or mode 3.

[0168] Therefore, based on different SID granularity, different encapsulation strategies are supported, and then QoS flow information encapsulation is realized according to the corresponding strategy, so that the UPF can perform corresponding operations (such as rate control, counting, etc.) according to the QFI carried by the encapsulated SRv6 data packet, so as to realize QoS control based on the SRv6 user plane. The problem that one SID can only bind one QoS flow information in the prior art, resulting in that after the SID applies Args.Mob.Session behavior, it can only be applied to one QoS flow, and the identification and positioning of multiple QoS flows in the PDU Session cannot be realized, is solved. At the same time, the problem of excessive occupation and waste of storage resources and processing resources in the UPF node caused by the increase of the number of SIDs on the UPF due to different QoS flows of the PDU session is also solved. The SID can be applied to QoS control of different PDU Sessions or different QoS flows, and resources are saved.

[0169] Optionally, if the SID is single PDU Session granularity, the encapsulation of the uplink user data packet into SRv6 packet format comprises:

[0170] When encapsulating the SRH for the uplink user data packet, encapsulating QoS flow information into the Tag field of the SRH; the QoS flow information further comprises a reflective quality of service identifier RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS; or

[0171] When encapsulating the SRH for the uplink user data packet, encapsulating QoS flow information into the extension field of the SRH; the QoS flow information further comprises an RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS.

[0172] In the embodiments of the present application, if the SID is single-PDU Session granularity, the uplink user data packet can be encapsulated into an SRv6 packet format based on mode 1 or mode 2: for mode 1, when the SRH is encapsulated for the uplink user data packet, the QoS flow information is encapsulated into the Tag field of the SRH; for mode 2, when the SRH is encapsulated for the uplink user data packet, the QoS flow information is encapsulated into the extension field of the SRH.

[0173] Optionally, the QoS flow information is encapsulated into the Tag field of the SRH, including:

[0174] The flag bit Flag in the Tag field of the SRH is set to determine whether the Tag field of the SRH carries the QoS flow information.

[0175] The QFI and RQI in the QoS flow information are respectively encapsulated into the Tag field of the SRH.

[0176] In the embodiments of the present application, if the SID is single-PDU Session granularity, the flag bit Flag in the Tag field of the SRH is set to indicate that the Tag field of the SRH carries the QoS flow information, and the QoS flow information can include QFI and RQI. The QFI is used to determine the corresponding QoS flow, and the RQI is used to determine whether to enable reflective QoS.

[0177] Specifically, for mode 1, the flag bit Flag in the Tag field is set, and the value of the flag bit Flag can be self-defined or specified (not limited herein). The flag bit Flag is used to indicate whether the Tag field of the SRH carries the QoS flow information. For example, the flag bit Flag takes value 0 or 1, and when the value of the flag bit Flag is 1, it indicates that the field carries the QoS flow information.

[0178] Based on mode 1, the following is described in detail by way of embodiment 1.

[0179] For example, embodiment 1 (SID is PDU Session granularity)

[0180] In combination with Figure 1 When the SID is PDU Session granularity, the service quality control method provided in the embodiments includes the following steps:

[0181] UL: RAN encapsulates SRv6 header for data packet (herein referred to as uplink user data packet) based on QFI and QoS Profile (QoS configuration information), and carries the QoS information in the Tag field of the SRH in the manner 1. Then, the UPF performs corresponding QoS characteristics based on the QoS information in the Tag field of the SRH.

[0182] Optionally, the extension field is used to indicate the type, length and value of the information element; and the encapsulation of the QoS flow information into the extension field of the SRH includes:

[0183] The QFI and the RQI are encapsulated into the extension field of the SRH, respectively.

[0184] A flag bit is set in the SRH to determine whether the Map field in the extension field of the SRH is invalid or ignored, wherein the Map field is used to indicate the mapping relationship between the PDU Session ID and the UE ID, and the extension field is used to determine the corresponding QoS flow.

[0185] In the embodiment, if the SID is single-PDU Session granularity, the QFI and the RQI are first encapsulated into the extension field of the SRH, and the flag bit is set in the SRH to indicate that the Map field in the extension field of the SRH is invalid or ignored when the flag bit is a self-defined or specified arbitrary value, for example, the flag bit Flag. Therefore, the corresponding QoS flow is determined by the QoS flow information carried in the extension field of the SRH.

[0186] For the manner 2, a flag bit is set in the extension field (such as the TLV field) in the SRH, and the Flag value can be self-defined or specified (not specifically limited herein), which is used to indicate whether the Map field (the Map field is used to indicate the mapping relationship between the PDU Session ID and the UE ID) in the extension field of the SRH is valid. For example, the Flag value is 0 or 1, and when the Flag value is 0, the Map field is invalid or ignored, which means that the subsequent field of the flag bit Flag is no longer parsed, and can represent that the QoS flow information indicated by the field is invalid or ignored. The unique QoS flow is determined by the QFI carried in the TLV field in the SRH, and whether the reflective QoS is enabled is determined by the RQI.

[0187] Based on the manner 2, the following is described in detail by the second embodiment.

[0188] Exemplarily, the second embodiment (SID is PDU Session granularity)

[0189] In combination Figure 2As shown, when the SID is PDU Session granularity, the service quality control method provided by the embodiment includes the following steps:

[0190] UL: When the RAN encapsulates the SRv6 header for the data packet (herein referred to as an uplink user data packet) according to the QFI and the QoS Profile (QoS configuration information), the QoS information is carried in the TLV field of the SRH, and the value of the Flag is set to 0, indicating that the subsequent field is no longer parsed. Then, the UPF performs corresponding QoS characteristics based on the QoS information in the TLV in the SRH.

[0191] Optionally, if the SID is multi-PDU Session granularity, the encapsulation of the uplink user data packet into the SRv6 data packet format includes:

[0192] When the SRH is encapsulated for the uplink user data packet, the QoS flow information is encapsulated into the extension field of the SRH.

[0193] In the embodiment of the application, if the SID is single-PDU Session granularity, the uplink user data packet can be encapsulated into the SRv6 data packet format based on mode 2.

[0194] Optionally, the extension field is used to indicate the type, length and value of the information element, the QoS flow information further includes the mapping relationship between the PDU Session ID and the UE ID, and the RQI; the RQI is used to indicate whether a QoS flow enables reflective QoS; and the encapsulation of the QoS flow information into the extension field of the SRH includes:

[0195] The QFI and the RQI are respectively encapsulated into the extension field of the SRH;

[0196] The flag bit Flag is set in the SRH to determine that the Map field in the extension field of the SRH is effective, and the Map field is used to indicate the mapping relationship between the PDU Session ID and the UE ID.

[0197] The extension field is used to determine the specified QoS flow of the specified PDU session of the corresponding user.

[0198] In the embodiments of the present application, if the SID is a multi-PDU Session granularity, the QFI and the RQI can be encapsulated into the extension field of the SRH respectively. By setting a flag bit Flag in the SRH, such as when the flag bit Flag is a self-defined or specified arbitrary value, it is indicated that the Map field in the extension field of the SRH is valid. Therefore, by the mapping relationship between the PDU Session ID and the UE ID carried in the extension field of the SRH, the specified QoS flow of the specified PDU Session of the corresponding user is determined, and whether to enable the reflective QoS is determined by the RQI.

[0199] Specifically, for mode 2, a flag bit Flag is set in the extension field (such as a TLV field) in the SRH. The Flag value can be self-defined or specified (not specifically limited here), which is used to indicate whether the Map field (the Map field is used to indicate the mapping relationship between the PDU Session ID and the UE ID) in the extension field of the SRH is valid. For example, when the Flag value is 1, it indicates that the Map field is valid. By combining the Map field, the specified QoS flow of the specified PDU Session of the corresponding user is determined.

[0200] Based on mode 2, the following is described in detail by embodiment three.

[0201] Exemplarily, embodiment three (SID is a multi-PDU Session granularity)

[0202] In combination with Figure 2 As shown in the figure, when the SID is a multi-PDU Session granularity, when different PDU Sessions of different users share the same SID, the RAN and the UPF need to distinguish different QoS flows of different sessions of different users. The service quality control method provided in the embodiment includes the following steps:

[0203] UL: The RAN encapsulates the SRv6 header for the data packet (herein referred to as an uplink user data packet) according to the QFI and the QoS Profile (QoS configuration information). When the SRH carries the QoS information in the TLV field, the value of the Flag is set to 1, and the Map (PDU Session ID, UE ID) is used to determine the user and the PDU Session, and the QFI is used to determine the QoS information. Then, the UPF performs corresponding QoS characteristics based on the QoS information in the TLV in the SRH.

[0204] Optionally, if the SID is a QoS granularity, the encapsulation of the uplink user data packet into the SRv6 data packet format includes:

[0205] encapsulate the QoS flow information into an Argument field of the SID in the SRH; wherein the SID is used to determine the QoS flow.

[0206] In the embodiments of the present application, if the SID is of QoS granularity, the uplink user data packet can be encapsulated into the SRv6 packet format based on mode 1 or mode 3; for the implementation of mode 1, a flag bit Flag is set in the Tag field of the SRH, for example, when the flag bit Flag is a self-defined or specified arbitrary value, it indicates that the Tag field of the SRH carries the QoS flow information, which can include QFI and RQI, the corresponding QoS flow is determined by the QFI, and whether to enable reflective QoS is determined by the RQI.

[0207] It should be noted that, consistent with the above embodiment of encapsulating the uplink user data packet into the SRv6 packet format based on mode 1 if the SID is of single PDU session granularity, details are not repeated here.

[0208] For mode 3, the QoS flow information is encapsulated into the Argument field of the SID in the SRH to indicate the corresponding QoS flow, and the UPF, upon receiving the SRv6 packet, performs corresponding operations according to the QFI carried in the Argument field of the SID in the SRH or the mapping relationship used to determine the QoS flow information.

[0209] Optionally, the QoS flow information further includes RQI; the RQI is used to indicate whether reflective QoS is enabled for a QoS flow; and the encapsulation of the QoS flow information into the Argument field of the SID in the SRH includes:

[0210] the QFI and the RQI are respectively encapsulated into the Argument field of the SID in the SRH; or

[0211] the mapping relationship between the QFI, the RQI and the SID is encapsulated into the Argument field of the SID in the SRH, and the mapping relationship between the QFI, the RQI and the SID is used to determine the QoS flow information.

[0212] In the embodiments of the present application, if the SID is of QoS granularity, the QFI and the RQI are respectively encapsulated into the Argument field of the SID in the SRH, or the mapping relationship between the QFI, the RQI and the SID is encapsulated into the Argument field of the SID in the SRH, and the corresponding QoS flow is determined by the Argument field of the SID in the SRH.

[0213] Specifically, for mode 3, the Argument field carries QFI and RQI information or QFI and RQI mapping information (herein referred to as mapping relationship, used to determine QoS flow information) with SID, so that the user plane node (including RAN) can determine the user's QoS requirement according to the SID. Among them, Args.mob.QoS can be used in combination with End.Map, End.DT4 / End.DT6 / End.DT46 or End.DX4 / End.DX6 / End.DX2.

[0214] Based on mode 3, the following is described in detail through embodiment four.

[0215] Exemplarily, embodiment four (SID is QoS granularity)

[0216] In combination Figure 3 As shown in the figure, when the SID is the QoS granularity, the Args.mob.QoS behavior of defining the SID identifies the QoS flow information through the Argument field of the SRH SID; the service quality control method provided in the embodiment includes the following steps:

[0217] Assuming that the RAN and the core network user plane UPF are both based on the SRv6 protocol forwarding, then:

[0218] UL: After the RAN node receives the data packet (herein referred to as uplink user data packet) of the UE, it encapsulates the corresponding SID list (SID list) for the uplink user data packet according to the QFI and its corresponding QoSProfile (QoS configuration information). Then the UPF performs the corresponding QoS characteristics according to the Behavior (behavior) of the SID (such as the QoS flow information carried by the Argument field of the SRH SID).

[0219] Therefore, by setting or extending a field in the SRv6 packet header to identify the QoS flow information carried, or defining a new SID Behavior, the SRv6 node performs corresponding QoS characteristics according to the QoS flow information or SID in the SRH, so as to realize QoS control based on the SRv6 user plane. The problem that one SID can only bind one QoS flow information in the prior art, resulting in that after the SID applies the Args.Mob.Session behavior, it can only be applied to one QoS flow, and the identification and positioning of multiple QoS flows in a PDU Session cannot be realized, is solved. At the same time, the problem that the number of SIDs on the UPF increases due to different QoS flows of the PDU session and different SIDs, and further causes excessive occupation and waste of storage resources and processing resources in the UPF node is also solved. The QoS control of the SID applied to different PDU Sessions or different QoS flows can be realized, and resources are saved at the same time. At the same time, the combination of QFI+PDU Session ID described in Args.Mob.Session cannot uniquely identify a QoS flow, which may cause the QoS characteristics applied to the user to be inconsistent with the user's request, so as to meet the user's demand. Therefore, the QoS control of the SID applied to different PDU Sessions or different QoS flows can be realized, and the QoS demand of the user is guaranteed.

[0220] Figure 5 The flowchart of the service quality control method provided by another embodiment of the present application is shown in FIG. 2, and the execution subject of the service quality control method provided by the embodiment of the present application is a UPF. The service quality control method provided by the embodiment of the present application includes the following steps. Figure 5

[0221] Step 201, encapsulating a downlink user data packet of a UE into an SRv6 packet format, wherein an SRH in a header of the SRv6 packet contains QoS flow information; wherein the QoS flow information includes a QFI, and the QFI is used to indicate a QoS flow.

[0222] Step 202, sending the SRv6 packet carrying the QFI to an intermediate UPF, and the intermediate UPF is used to send the SRv6 packet carrying the QFI to a RAN; or,

[0223] sending the SRv6 packet carrying the QFI to the RAN, and the RAN is used to map the QoS flow to a corresponding data radio bearer (DRB) according to the QFI and corresponding QoS configuration information.

[0224] ​In the embodiments of the present application, based on the downlink user data packet of the UE, the downlink user data packet is encapsulated into an SRv6 data packet format including at least QoS flow information of QFI, to indicate the corresponding QoS flow, and the SRv6 data packet carrying the QFI is sent to the intermediate UPF, and the intermediate UPF sends the SRv6 data packet to the RAN, or the SRv6 data packet carrying the QFI is sent to the RAN, and the RAN maps the QoS flow to the DRB based on the QFI and the corresponding QoS configuration information, and then sends the SRv6 data packet on the corresponding DRB, so that the SID can be applied to the QoS control of different PDU Sessions or different QoS flows, thereby guaranteeing the QoS requirement of the user.

[0225] Optionally, the encapsulating the downlink user data packet of the UE into the SRv6 data packet format comprises:

[0226] If the SID is single-PDU Session granularity, the downlink user data packet is encapsulated into the SRv6 data packet format by carrying the QoS flow information in the Tag field of the SRH or carrying the QoS flow information in the extension field of the SRH;

[0227] If the SID is multi-PDU Session granularity, the downlink user data packet is encapsulated into the SRv6 data packet format by carrying the QoS flow information in the extension field of the SRH;

[0228] If the SID is QoS granularity, the downlink user data packet is encapsulated into the SRv6 data packet format by carrying the QoS flow information in the Tag field of the SRH or defining the SID behavior to carry the QoS flow information in the Argument field of the SID of the SRH.

[0229] In the embodiments of the present application, referring to Figures 1 to 3 The downlink user data packet is encapsulated into the SRv6 data packet format by the above-mentioned mode 1, mode 2 or mode 3, and the mode 1, mode 2 and mode 3 will not be described here.

[0230] Specifically, if the SRv6 segment identifier SID is single-PDU Session granularity, the uplink user data packet can be encapsulated into the SRv6 data packet format based on mode 1 or mode 2; if the SRv6 segment identifier SID is multi-PDU Session granularity, the uplink user data packet can be encapsulated into the SRv6 data packet format based on mode 2; if the SRv6 segment identifier SID is QoS granularity, the uplink user data packet can be encapsulated into the SRv6 data packet format based on mode 1 or mode 3.

[0231] Therefore, different encapsulation strategies are supported based on different SID granularities, and QoS flow information encapsulation is realized according to the corresponding strategy, so that the RAN can map the QoS flow to the DRB according to the QFI carried by the encapsulated SRv6 data packet and the corresponding QoS configuration information, thereby realizing QoS control. The problem that one SID can only bind one QoS flow information in the prior art, resulting in that after the SID applies Args.Mob.Session behavior, it can only be applied to one QoS flow, and the identification and positioning of multiple QoS flows in a PDU Session cannot be realized, is solved. At the same time, the problem of excessive occupation and waste of storage resources and processing resources in the UPF node caused by the increase in the number of SIDs on the UPF due to different QoS flows of a PDU session is also solved, and the resources can be saved while the SID is applied to different PDU Sessions or different QoS flow QoS control.

[0232] Optionally, if the SID is a PDU Session granularity, the encapsulating the downlink user data packet into an SRv6 data packet format comprises:

[0233] When encapsulating the SRH for the downlink user data packet, encapsulating QoS flow information into a Tag field of the SRH; the QoS flow information further comprises a reflective quality of service identifier RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS; or

[0234] When encapsulating the SRH for the downlink user data packet, encapsulating QoS flow information into an extension field of the SRH; the QoS flow information further comprises an RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS.

[0235] In the embodiments of the present application, if the SID is a single PDU Session granularity, the downlink user data packet can be encapsulated into an SRv6 data packet format based on mode 1 or mode 2: for mode 1, when encapsulating the SRH for the downlink user data packet, encapsulating QoS flow information into a Tag field of the SRH; for mode 2, when encapsulating the SRH for the downlink user data packet, encapsulating QoS flow information into an extension field of the SRH.

[0236] Optionally, the encapsulating the QoS flow information into the Tag field of the SRH comprises:

[0237] A flag bit Flag in the Tag field of the SRH is set to determine whether the Tag field of the SRH carries QoS flow information.

[0238] The QFI and the RQI in the QoS flow information are encapsulated into the Tag field of the SRH, respectively.

[0239] In the embodiments of the present application, if the SID is single-PDU Session granularity, a flag bit Flag in the Tag field of the SRH is set, such as the flag bit Flag being a self-defined or specified arbitrary value, to indicate that the Tag field of the SRH carries QoS flow information. The QoS flow information can include QFI and RQI. The corresponding QoS flow is determined by the QFI, and whether to enable reflective QoS is determined by the RQI.

[0240] Specifically, for the first mode, a flag bit Flag is set in the Tag field. The flag bit Flag value can be self-defined or specified (not specifically limited here), and is used to indicate whether the Tag field of the SRH carries QoS flow information, such as the flag bit Flag taking a value of 0 or 1. When the Flag value is 1, it indicates that the field carries QoS flow information.

[0241] Based on the first mode, the following is described in detail in Embodiment Five.

[0242] For example, Embodiment Five (SID is PDU Session granularity)

[0243] In combination with Figure 1 As shown in the figure, when the SID is PDU Session granularity, the quality of service control method provided by the embodiment includes the following steps:

[0244] A protocol data unit session anchor (PDU Session Anchor, PSA) (herein referred to as a UPF) encapsulates an SRv6 header for a user data packet (herein referred to as a downlink user data packet) according to a data packet detection rule PDR, a forwarding operation rule FAR, and a QoS execution rule QER, and carries QoS information in the Tag field of the SRH. Then, the UPF performs corresponding QoS characteristics based on the QoS information in the Tag field of the SRH. The RAN decapsulates the SRv6 data packet according to the QFI and the QoS profile (QoS configuration information), and sends it to the UE from the DRB mapped by the QFI.

[0245] Optionally, the extension field is used to indicate the type, length, and value of the information element; and the encapsulation of the QoS flow information into the extension field of the SRH includes:

[0246] The QFI and the RQI are encapsulated into the extension field of the SRH, respectively.

[0247] By setting a flag in the SRH, it is determined that the Map field in the extension field of the SRH is invalid or ignored; wherein the Map field is used to indicate the mapping relationship between the PDU Session ID and the UE ID, and the extension field is used to determine the corresponding QoS flow.

[0248] In the embodiment of the application, if the SID is single-PDU Session granularity, the QFI and the RQI are first encapsulated into the extension field of the SRH, and by setting a flag in the SRH, for example, when the flag is a self-defined or specified arbitrary value, it is indicated that the Map field in the extension field of the SRH is invalid or ignored, therefore, by the QoS flow information carried in the extension field of the SRH, the corresponding QoS flow is determined.

[0249] For mode 2, by setting a flag in the extension field (such as a TLV field) in the SRH, the Flag value can be self-defined or specified (not specifically limited here), which is used to indicate whether the Map field (the Map field is used to indicate the mapping relationship between the PDU Session ID and the UE ID) in the extension field of the SRH is valid, for example: the Flag value is 0 or 1, when the Flag value is 0, it means that the Map field is invalid or ignored, which means that the subsequent field of the flag is no longer parsed, which can mean that the QoS flow information indicated by the field is invalid or ignored, the unique QoS flow is determined by the QFI carried in the TLV field in the SRH, and whether the reflective QoS is enabled is determined by the RQI.

[0250] Based on mode 2, the following is described in detail by embodiment six.

[0251] For example, embodiment six (SID is PDU Session granularity)

[0252] In combination Figure 2 As shown in the figure, when the SID is PDU Session granularity, the service quality control method provided by the embodiment includes the following steps:

[0253] DL: A Protocol Data Unit Session Anchor (PDU Session Anchor, PSA) (herein referred to as a UPF) encapsulates an SRv6 header for a user data packet (herein referred to as a downlink user data packet) according to a packet detection rule PDR, a forwarding action rule FAR, and a QoS execution rule QER, carries QoS information in a TLV field of the SRH, and sets a value of a Flag to 0, indicating that subsequent fields are not parsed. Subsequently, the UPF performs corresponding QoS characteristics based on the QoS information carried in the TLV field of the SRH. The RAN decapsulates the SRv6 packet according to the QFI and the QoS profile (QoS configuration information), and sends the packet to the UE from a DRB mapped by the QFI.

[0254] Optionally, if the SID is a multi-PDU Session granularity, the encapsulating the downlink user data packet into an SRv6 packet format includes:

[0255] When encapsulating the SRH for the downlink user data packet, the QoS flow information is encapsulated into an extension field of the SRH.

[0256] In the embodiments of the application, if the SID is a single-PDU Session granularity, the downlink user data packet can be encapsulated into an SRv6 packet format based on a manner 2.

[0257] Optionally, the extension field is used to indicate a type, length, and value of an information element, the QoS flow information further includes a mapping relationship between a PDU Session ID and a UE ID, and an RQI; the RQI is used to indicate whether a reflective QoS is enabled for a QoS flow; and the encapsulating the QoS flow information into the extension field of the SRH includes:

[0258] The QFI and the RQI are encapsulated into the extension field of the SRH, respectively;

[0259] A flag bit Flag is set in the SRH to determine that a Map field in the extension field of the SRH is effective, and the Map field is used to indicate the mapping relationship between the PDU Session ID and the UE ID.

[0260] The extension field is used to determine a specified QoS flow of a specified PDU session of a corresponding user.

[0261] In the embodiments of the present application, if the SID is a multi-PDU Session granularity, the QFI and the RQI can be encapsulated into the extension field of the SRH respectively. By setting a flag bit Flag in the SRH, such as when the flag bit Flag is a self-defined or specified arbitrary value, it is indicated that the Map field in the extension field of the SRH is valid. Therefore, by the mapping relationship between the PDU Session ID and the UE ID carried in the extension field of the SRH, the specified QoS flow of the specified PDU Session of the corresponding user is determined, and whether to enable the reflective QoS is determined by the RQI.

[0262] Specifically, for the mode 2, by setting a flag bit Flag in the extension field (such as a TLV field) in the SRH, the Flag value can be self-defined or specified (not specifically limited here), which is used to indicate whether the Map field (the Map field is used to indicate the mapping relationship between the PDU Session ID and the UE ID) in the extension field of the SRH is valid. For example, when the Flag value is 1, it indicates that the Map field is valid, and by combining the Map field, the specified QoS flow of the specified PDU Session of the corresponding user is determined.

[0263] Based on the mode 2, the following is described in detail by way of embodiment three.

[0264] Exemplarily, embodiment seven (SID is a multi-PDU Session granularity)

[0265] In combination Figure 2 As shown in the figure, when the SID is a multi-PDU Session granularity, when different PDU Sessions of different users share the same SID, the RAN and the UPF need to distinguish different QoS flows of different sessions of different users. The service quality control method provided in the embodiment includes the following steps:

[0266] DL: The protocol data unit session anchor (PDU Session Anchor, PSA) (herein referred to as a UPF) encapsulates the SRv6 header for the user data packet (herein referred to as a downlink user data packet) according to the data packet detection rule PDR, the forwarding operation rule FAR and the QoS execution rule QER, carries the QoS information in the TLV field of the SRH, sets the value of the Flag to 1 at the same time, and uses Map (PDU Session ID, UE ID) to determine the user and the PDU Session, and uses QFI to determine the QoS information. Then, the UPF performs corresponding QoS characteristics based on the QoS information in the TLV in the SRH.

[0267] Optionally, if the SID is QoS granularity, the encapsulating the downlink user data packet into the SRv6 packet format comprises:

[0268] encapsulating QoS flow information into an Argument field of the SID in the SRH, wherein the SID is used to determine the QoS flow.

[0269] In the embodiments of the present application, if the SID is QoS granularity, the downlink user data packet can be encapsulated into the SRv6 packet format based on mode 1 or mode 3. For the implementation of mode 1, a flag bit Flag in the Tag field of the SRH is set, for example, when the flag bit Flag is a self-defined or specified arbitrary value, it indicates that the Tag field of the SRH carries QoS flow information. The QoS flow information can include QFI and RQI. The QFI is used to determine the corresponding QoS flow, and the RQI is used to determine whether to enable reflective QoS.

[0270] It should be noted that, consistent with the above-mentioned implementation of encapsulating the downlink user data packet into the SRv6 packet format based on mode 1 if the SID is single-PDU session granularity, the implementation is not repeated here.

[0271] For mode 3, the QoS flow information is encapsulated into the Argument field of the SID in the SRH to indicate the corresponding QoS flow. When the UPF receives the SRv6 packet, the QFI carried in the Argument field of the SID in the SRH or the mapping relationship used to determine the QoS flow information is used to perform corresponding operations.

[0272] Optionally, the QoS flow information further includes RQI. The RQI is used to indicate whether a QoS flow enables reflective QoS. The encapsulating the QoS flow information into the Argument field of the SID in the SRH comprises:

[0273] encapsulating the QFI and the RQI into the Argument field of the SID in the SRH, or

[0274] encapsulating the mapping relationship between the QFI, the RQI and the SID into the Argument field of the SID in the SRH. The mapping relationship between the QFI, the RQI and the SID is used to determine the QoS flow information.

[0275] In the embodiments of the application, if the SID is QoS granularity, the QFI and the RQI are respectively encapsulated into the Argument field of the SID in the SRH, or the mapping relationship between the QFI, the RQI and the SID is encapsulated into the Argument field of the SID in the SRH, and the corresponding QoS flow is determined through the Argument field of the SID in the SRH.

[0276] Specifically, for the mode 3, the Argument field carries the QFI and the RQI information or the mapping information (here, the mapping relationship is used to determine the QoS flow information) between the QFI and the RQI and the SID, so that the user plane node (including the RAN) can determine the QoS requirement of the user according to the SID. The Args.mob.QoS can be used in combination with the End.Map, the End.DT4 / End.DT6 / End.DT46 or the End.DX4 / End.DX6 / End.DX2.

[0277] Based on the mode 3, the following is described in detail through Embodiment 8.

[0278] Exemplarily, Embodiment 8 (SID is QoS granularity)

[0279] In combination with Figure 3 As shown in the figure, when the SID is QoS granularity, the Args.mob.QoS behavior of the SID is used to identify the QoS flow information through the Argument field of the SID in the SRH; the service quality control method provided in the embodiment includes the following steps:

[0280] It is assumed that the RAN and the core network user plane UPF are both based on the SRv6 protocol forwarding.

[0281] DL: After the PSA receives the data packet (here, the downlink user data packet), the SRv6 header of the corresponding QoS flow is encapsulated for the downlink user data packet according to the data packet detection rule, and the corresponding SID list is included. After the RAN receives the downlink user data packet, the QFI is determined according to the Args.mob.QoS behavior of the SID.

[0282] Therefore, by setting or extending the field in the SRv6 packet header to identify the QoS flow information carried, or defining a new SID Behavior, the SRv6 node performs corresponding QoS characteristics according to the QoS flow information or SID in the SRH, so as to realize the QoS control based on the SRv6 user plane. The problem that one SID can only bind one QoS flow information in the prior art, resulting in that after the SID applies Args.Mob.Session behavior, it can only be applied to one QoS flow, and the identification and positioning of multiple QoS flows in a PDU Session cannot be realized, is solved. At the same time, the problem that the number of SIDs on the UPF increases due to different QoS flows of the PDU session and different SIDs, and further causes the excessive occupation and waste of storage resources and processing resources in the UPF node is solved. The QoS control of the SID applied to different PDU Sessions or different QoS flows can be realized, and resources are saved. At the same time, the combination of QFI+PDU Session ID described in Args.Mob.Session cannot uniquely identify a QoS flow, which may cause the QoS characteristics applied to the user to be inconsistent with the user's request, so that the user's demand cannot be met. Therefore, the QoS control of the SID applied to different PDU Sessions or different QoS flows can be realized, and the QoS demand of the user is guaranteed.

[0283] It should be noted that the specific implementation process of the quality of service control method with the UPF as the execution subject can refer to the embodiments shown in the Figures 1-3 The specific implementation process is not described here.

[0284] Figure 6 The structure diagram of the quality of service control device provided by the embodiments of the present application is shown in FIG. 1, and the quality of service control device provided by the embodiments of the present application is applied to a radio access network RAN. The quality of service control device provided by the embodiments of the present application includes a transceiver 600 for receiving and sending data under the control of a processor 610. Figure 6

[0285] In the embodiments of the present application, the processor 610 is configured to perform the following steps. Figure 6 ​In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 610) and memory (memory 620). The bus architecture can also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 600 can be multiple elements, including transmitters and receivers, providing units for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, etc. The processor 610 is responsible for managing the bus architecture and general processing, and the memory 620 can store data used by the processor 610 during operation.

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

[0287] In this embodiment, the memory 620 is used to store computer programs; the transceiver 600 is used to send and receive data under the control of the processor; and the processor 610 is used to read the computer programs from the memory and perform the following operations:

[0288] Receive uplink user data packets from the terminal;

[0289] The uplink user data packets are encapsulated in SRv6 data packet format, wherein the SRv6 data packet header SRH contains Quality of Service (QoS) flow information, and the QoS flow information includes QFI, which is used to indicate the QoS flow.

[0290] The SRv6 data packet carrying the QFI is sent to the User Plane Function (UPF), which is used to perform corresponding operations based on the QFI.

[0291] Optionally, the processor 610, when encapsulating the uplink user data packet into the SRv6 data packet format, specifically includes:

[0292] If the SRv6 segment identifier SID is at the single PDU Session granularity, the uplink user data packet is encapsulated into SRv6 data packet format by using the Tag field in the SRH to carry QoS flow information, or by using the extended field in the SRH to carry QoS flow information.

[0293] If the SID is a multi-PDU Session granularity, the uplink user data packet is encapsulated into an SRv6 packet format by carrying QoS flow information using an extension field in the SRH;

[0294] If the SID is a QoS granularity, the uplink user data packet is encapsulated into an SRv6 packet format by carrying QoS flow information using a Tag field in the SRH, or defining a SID behavior to carry QoS flow information through an Argument field of the SID in the SRH.

[0295] Optionally, the processor 610 is configured to, when the SID is a single-PDU Session granularity, encapsulate the uplink user data packet into an SRv6 packet format, specifically comprising:

[0296] when encapsulating the SRH for the uplink user data packet, encapsulating QoS flow information into a Tag field of the SRH; the QoS flow information further comprises an RQI, and the RQI is used to indicate whether a QoS flow enables a reflective QoS; or

[0297] when encapsulating the SRH for the uplink user data packet, encapsulating QoS flow information into an extension field of the SRH; the QoS flow information further comprises an RQI, and the RQI is used to indicate whether a QoS flow enables a reflective QoS.

[0298] Optionally, the processor is configured to, when encapsulating the QoS flow information into the Tag field of the SRH, specifically comprising:

[0299] determining that the Tag field of the SRH carries the QoS flow information by setting a flag bit Flag in the Tag field of the SRH;

[0300] encapsulating a QFI and an RQI in the QoS flow information into the Tag field of the SRH, respectively.

[0301] Optionally, the extension field is used to indicate a type, length, and value of an information element; and the processor is configured to, when encapsulating the QoS flow information into the extension field of the SRH, specifically comprising:

[0302] encapsulating a QFI and an RQI into the extension field of the SRH, respectively;

[0303] By setting a flag Flag in the SRH, it is determined that a Map field in an extension field of the SRH is invalid or ignored; wherein the Map field is used to indicate a mapping relationship between a PDU Session ID and a UE ID, and the extension field is used to determine a corresponding QoS flow.

[0304] Optionally, when the SID is a multi-PDU Session granularity, the processor is configured to encapsulate the uplink user data into an SRv6 data packet format, and specifically includes:

[0305] When encapsulating the SRH for the uplink user data, encapsulate QoS flow information into an extension field of the SRH.

[0306] Optionally, the extension field is used to indicate a type, length and value of an information element; the QoS flow information further includes a mapping relationship between a PDU Session ID and a UE ID, and an RQI; the RQI is used to indicate whether a QoS flow enables a reflective QoS; and when encapsulating the QoS flow information into the extension field of the SRH, the processor specifically includes:

[0307] encapsulate a QFI and the RQI into the extension field of the SRH, respectively;

[0308] By setting a flag Flag in the SRH, it is determined that a Map field in an extension field of the SRH is valid, and the Map field is used to indicate a mapping relationship between a PDU Session ID and a UE ID.

[0309] The extension field is used to determine a specified QoS flow of a specified PDU session of a corresponding user.

[0310] Optionally, when the SID is a QoS granularity, the processor is configured to encapsulate the uplink user data into an SRv6 data packet format, and specifically includes:

[0311] encapsulate QoS flow information into an Argument field of the SRH for the SID; wherein the SID is used to determine a QoS flow.

[0312] Optionally, the QoS flow information further includes an RQI; the RQI is used to indicate whether a QoS flow enables a reflective QoS; and when encapsulating the QoS flow information into the Argument field of the SRH for the SID, the processor specifically includes:

[0313] encapsulate a QFI and the RQI into the Argument field of the SRH for the SID, respectively; or

[0314] The mapping relationship between the QFI, the RQI and the SID is encapsulated into an Argument field of the SID in the SRH, and the mapping relationship between the QFI, the RQI and the SID is used to determine QoS flow information.

[0315] It should be noted that the service quality control device provided in the present application can achieve Figures 1-4 All method steps achieved by the method embodiment shown in the present embodiment and the same technical effects can be achieved, and the same parts and beneficial effects of the method embodiment in the present embodiment will not be described in detail.

[0316] Figure 7 The structural schematic diagram of the service quality control device provided in another embodiment of the present application is shown in the figure, and the service quality control device provided in the present embodiment is applied to a radio access network (RAN), and the service quality control device 700 provided in the present embodiment comprises: Figure 7

[0317] The receiving unit 701 is configured to receive an uplink user data packet of a terminal.

[0318] The processing unit 702 is configured to encapsulate the uplink user data packet into an SRv6 data packet format, wherein an SRH in a header of the SRv6 data packet contains quality of service (QoS) flow information; and the QoS flow information comprises a QFI, and the QFI is used to indicate a QoS flow.

[0319] The sending unit 703 is configured to send the SRv6 data packet carrying the QFI to a user plane function (UPF), and the UPF is configured to perform corresponding operations according to the QFI.

[0320] Optionally, the processing unit 702 is specifically configured to:

[0321] When a segment identifier (SID) is single-PDU session granularity, the uplink user data packet is encapsulated into the SRv6 data packet format by using a Tag field in the SRH to carry QoS flow information or using an extension field in the SRH to carry the QoS flow information;

[0322] When the SID is multi-PDU session granularity, the uplink user data packet is encapsulated into the SRv6 data packet format by using the extension field in the SRH to carry the QoS flow information;

[0323] When the SID is QoS granularity, the uplink user data packet is encapsulated into the SRv6 data packet format by using the Tag field in the SRH to carry the QoS flow information or defining a SID behavior to carry the QoS flow information through an Argument field of the SID in the SRH. ​

[0324] Optionally, the processing unit 702 is specifically configured to:

[0325] In the case that the SID is single-PDU Session granularity, when the SRH is encapsulated for the uplink user data packet, the QoS flow information is encapsulated into a Tag field of the SRH; the QoS flow information further includes an RQI, and the RQI is used to indicate whether a QoS flow is enabled for reflective QoS.

[0326] In the case that the SID is single-PDU Session granularity, when the SRH is encapsulated for the uplink user data packet, the QoS flow information is encapsulated into an extension field of the SRH; the QoS flow information further includes an RQI, and the RQI is used to indicate whether a QoS flow is enabled for reflective QoS.

[0327] Optionally, the processing unit 702 is specifically configured to:

[0328] The flag bit Flag in the Tag field of the SRH is set to determine that the Tag field of the SRH carries the QoS flow information.

[0329] The QFI and the RQI in the QoS flow information are respectively encapsulated into the Tag field of the SRH.

[0330] Optionally, the extension field is used to indicate the type, length and value of an information element; and the processing unit 702 is specifically configured to:

[0331] The QFI and the RQI are respectively encapsulated into the extension field of the SRH.

[0332] The flag bit Flag in the SRH is set to determine that a Map field in the extension field of the SRH is invalid or ignored; the Map field is used to indicate the mapping relationship between a PDU Session ID and a UE ID, and the extension field is used to determine a corresponding QoS flow.

[0333] Optionally, the processing unit 702 is specifically configured to:

[0334] In the case that the SID is multi-PDU Session granularity, when the SRH is encapsulated for the uplink user data packet, the QoS flow information is encapsulated into an extension field of the SRH.

[0335] Optionally, the extension field is used to indicate the type, length and value of an information element; the QoS flow information further includes the mapping relationship between the PDU Session ID and the UE ID, and the RQI; the RQI is used to indicate whether a QoS flow is enabled for reflective QoS; and the processing unit 702 is specifically configured to:

[0336] encapsulate the QFI and the RQI into the extension field of the SRH, respectively;

[0337] determine that the Map field in the extension field of the SRH is effective by setting a flag bit Flag in the SRH, the Map field being used to indicate a mapping relationship between a PDU Session ID and a UE ID;

[0338] The extension field is used to determine a specified QoS flow of a specified PDU session of a corresponding user.

[0339] Optionally, the processing unit 702 is specifically configured to:

[0340] encapsulate QoS flow information into an Argument field of the SID in the SRH when the SID is of a QoS granularity, the SID being used to determine a QoS flow.

[0341] Optionally, the QoS flow information further includes an RQI, the RQI being used to indicate whether a QoS flow enables reflective QoS; and the processing unit 702 is specifically configured to:

[0342] encapsulate the QFI and the RQI into the Argument field of the SID in the SRH, respectively; or

[0343] encapsulate a mapping relationship between the QFI, the RQI and the SID into the Argument field of the SID in the SRH, the mapping relationship between the QFI, the RQI and the SID being used to determine the QoS flow information.

[0344] It should be noted that the service quality control apparatus provided in the present application can achieve the following effects: Figures 1-4 All the method steps achieved by the method embodiments and the same technical effects can be achieved, and thus the same parts and beneficial effects of the method embodiments will not be described in detail.

[0345] Figure 8 A structural schematic diagram of a service quality control apparatus provided by still another embodiment of the present application is shown in FIG. 8. Figure 8 The service quality control apparatus provided by the present embodiment is applied to a user plane function (UPF), and thus the service quality control apparatus provided by the present embodiment includes a transceiver 800 configured to receive and send data under the control of a processor 810.

[0346] In the present embodiment, the transceiver 800 is configured to receive and send data under the control of the processor 810. Figure 8In particular embodiments, the bus architecture can include any number of interconnecting buses and bridges, depending on the specific application of the processor 810 and the memory 820 represented by various circuitry linking the processor 810 and the memory 820. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuitry, all of which are well known in the art, and therefore, will not be described further. A bus interface provides the interface. The transceiver 800 can be a plurality of elements, including a transmitter and a receiver, that provides the means for communicating with various other apparatus over a transmission medium, including a wireless channel, a wired channel, optical cable, and the like. The processor 810 is responsible for managing the bus architecture and general processing, and the memory 820 can store data used by the processor 810 in executing its operations.

[0347] The processor 810 can be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD), or the processor can be implemented using a multi-core architecture.

[0348] In this embodiment, the memory 820 is configured to store a computer program, and the transceiver 800 is configured to transceive data under the control of the processor 810, and the processor 810 is configured to read the computer program in the memory and perform the following operations:

[0349] The downlink user data packet of the UE is encapsulated into an SRv6 data packet format, wherein an SRv6 packet header SRH contains QoS flow information; wherein the QoS flow information includes a QFI, and the QFI is used to indicate a QoS flow;

[0350] The SRv6 data packet carrying the QFI is sent to an intermediate UPF, and the intermediate UPF is configured to send the SRv6 data packet carrying the QFI to a RAN; or

[0351] The SRv6 data packet carrying the QFI is sent to a RAN, and the RAN is configured to map a QoS flow to a corresponding data radio bearer (DRB) according to the QFI and corresponding QoS configuration information.

[0352] Optionally, when the downlink user data packet of the UE is encapsulated into an SRv6 data packet format, the processor 810 specifically includes the following operations:

[0353] If the SID is single-PDU Session granularity, the downlink user data packet is encapsulated into SRv6 packet format by carrying QoS flow information in the Tag field of the SRH or carrying QoS flow information in the extension field of the SRH;

[0354] If the SID is multi-PDU Session granularity, the downlink user data packet is encapsulated into SRv6 packet format by carrying QoS flow information in the extension field of the SRH;

[0355] If the SID is QoS granularity, the downlink user data packet is encapsulated into SRv6 packet format by carrying QoS flow information in the Tag field of the SRH or defining the SID behavior to carry QoS flow information in the Argument field of the SID in the SRH.

[0356] Optionally, the processor 810 is configured to, when the SID is single-PDU Session granularity, encapsulate the downlink user data packet into SRv6 packet format, specifically comprising:

[0357] encapsulating QoS flow information into the Tag field of the SRH when encapsulating the SRH for the downlink user data packet; the QoS flow information further comprises an RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS; or

[0358] encapsulating QoS flow information into the extension field of the SRH when encapsulating the SRH for the downlink user data packet; the QoS flow information further comprises the RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS.

[0359] Optionally, the processor 810 is configured to, when encapsulating QoS flow information into the Tag field of the SRH, specifically comprising:

[0360] determining that the Tag field of the SRH carries QoS flow information by setting a flag bit Flag in the Tag field of the SRH;

[0361] encapsulating QFI and RQI in QoS flow information into the Tag field of the SRH, respectively.

[0362] Optionally, the extension field is used to indicate the type, length and value of an information element; and the processor 810 is configured to, when encapsulating QoS flow information into the extension field of the SRH, specifically comprising:

[0363] encapsulating QFI and RQI into the extension field of the SRH, respectively;

[0364] The SRH is set with a flag to determine that a Map field in an extension field of the SRH is invalid or ignored, wherein the Map field is used to indicate a mapping relationship between a PDU Session ID and a UE ID, and the extension field is used to determine a corresponding QoS flow.

[0365] Optionally, the processor 810 is configured to, when the SID is a multi-PDU Session granularity, and the downlink user data is encapsulated into an SRv6 packet format, specifically include:

[0366] The QoS flow information is encapsulated into an extension field of the SRH when the SRH is encapsulated for the downlink user data.

[0367] Optionally, the extension field is used to indicate a type, length, and value of an information element, and the QoS flow information further includes a mapping relationship between a PDU Session ID and a UE ID and an RQI, wherein the RQI is used to indicate whether a QoS flow is enabled for reflective QoS, and the processor 810 is configured to, when the QoS flow information is encapsulated into the extension field of the SRH, specifically include:

[0368] The QFI and the RQI are respectively encapsulated into the extension field of the SRH.

[0369] The SRH is set with a flag to determine that a Map field in an extension field of the SRH is valid, and the Map field is used to indicate a mapping relationship between a PDU Session ID and a UE ID.

[0370] The extension field is used to determine a specified QoS flow of a specified PDU session of a corresponding user.

[0371] Optionally, the processor 810 is configured to, when the SID is a QoS granularity, and the downlink user data is encapsulated into an SRv6 packet format, specifically include:

[0372] The QoS flow information is encapsulated into an Argument field of the SID in the SRH, and the SID is used to determine a QoS flow.

[0373] Optionally, the QoS flow information further includes an RQI, and the RQI is used to indicate whether a QoS flow is enabled for reflective QoS, and the processor 810 is configured to, when the QoS flow information is encapsulated into the Argument field of the SID in the SRH, specifically include:

[0374] The QFI and the RQI are respectively encapsulated into the Argument field of the SID in the SRH, or

[0375] The mapping relationship between QFI, RQI, and SID is encapsulated in the Argument field of SID in the SRH, and the mapping relationship between QFI, RQI, and SID is used to determine QoS flow information.

[0376] It should be noted that the service quality control device provided in this application is capable of achieving... Figures 1-3 as well as Figure 5 All method steps implemented in the method embodiment shown are capable of achieving the same technical effect. Therefore, the parts that are the same as those in the method embodiment and their beneficial effects will not be described in detail here.

[0377] Figure 9 A schematic diagram of the structure of a service quality control device provided in another embodiment of this application is shown below. Figure 9 As shown, the quality of service control device provided in this embodiment is applied to the User Plane Function (UPF). Therefore, the quality of service control device 900 provided in this embodiment includes:

[0378] Processing unit 901 is configured to encapsulate downlink user data packets of the UE into SRv6 data packet format, wherein the SRv6 data packet header SRH contains QoS flow information; wherein the QoS flow information includes QFI, and the QFI is used to indicate QoS flow;

[0379] Transmitting unit 902 is configured to transmit the SRv6 data packet carrying the QFI to an intermediate UPF, wherein the intermediate UPF is configured to transmit the SRv6 data packet carrying the QFI to the RAN; or,

[0380] The SRv6 data packet carrying the QFI is sent to the RAN, which is used to map the QoS flow to the corresponding data radio bearer (DRB) according to the QFI and the corresponding QoS configuration information.

[0381] Optionally, the processing unit 901 is specifically used for:

[0382] When the SID is at the single PDU Session granularity, the downlink user data packet is encapsulated into SRv6 data packet format by using the Tag field in the SRH to carry QoS flow information, or by using the extended field in the SRH to carry QoS flow information.

[0383] When the SID is at the multi-PDU Session granularity, the downlink user data packet is encapsulated into SRv6 data packet format by using the extended field in the SRH to carry QoS flow information;

[0384] When the SID is QoS granularity, the downlink user data packet is encapsulated into the SRv6 packet format by using a Tag field in the SRH to carry QoS flow information, or by defining a SID behavior to carry QoS flow information in an Argument field of the SID in the SRH.

[0385] Optionally, the processing unit 901 is specifically configured to:

[0386] When the SID is PDU Session granularity, the QoS flow information is encapsulated into a Tag field of the SRH when the SRH is encapsulated for the downlink user data packet.

[0387] When the SID is PDU Session granularity, the QoS flow information is encapsulated into an extension field of the SRH when the SRH is encapsulated for the downlink user data packet.

[0388] Optionally, the processing unit 901 is specifically configured to:

[0389] A flag bit Flag in the Tag field of the SRH is set to determine that the Tag field of the SRH carries QoS flow information.

[0390] QFI and RQI in the QoS flow information are respectively encapsulated into the Tag field of the SRH.

[0391] Optionally, the extension field is used to indicate the type, length and value of an information element; and the processing unit 901 is specifically configured to:

[0392] QFI and RQI are respectively encapsulated into the extension field of the SRH.

[0393] A flag bit Flag is set in the SRH to determine that a Map field in the extension field of the SRH is invalid or ignored; the Map field is used to indicate a mapping relationship between a PDU Session ID and a UE ID, and the extension field is used to determine a corresponding QoS flow.

[0394] Optionally, the processing unit 901 is specifically configured to:

[0395] When the SID is multi-PDU Session granularity, the QoS flow information is encapsulated into an extension field of the SRH when the SRH is encapsulated for the downlink user data packet.

[0396] Optionally, the extended field is used to indicate the type, length, and value of the information element; the QoS flow information also includes the mapping relationship between PDU Session ID and UE ID, and RQI; the RQI is used to indicate whether a QoS flow enables reflective QoS; the processing unit 901 is specifically used for:

[0397] QFI and RQI are respectively encapsulated into the extended fields of the SRH;

[0398] By setting a flag bit in the SRH, it is determined that the Map field in the extended field of the SRH is effective. The Map field is used to indicate the mapping relationship between PDU Session ID and UE ID.

[0399] The extended field is used to determine the specified QoS flow for the specified PDU session of the corresponding user.

[0400] Optionally, the processing unit 901 is specifically used for:

[0401] When the SID is at the QoS granularity, the QoS flow information is encapsulated into the Argument field of the SID in the SRH; wherein, the SID is used to determine the QoS flow.

[0402] Optionally, the QoS flow information further includes RQI; the RQI is used to indicate whether a QoS flow enables reflective QoS; the processing unit 901 is specifically used for:

[0403] Encapsulate QFI and RQI into the Argument field of the SID in the SRH; or,

[0404] The mapping relationship between QFI, RQI, and SID is encapsulated in the Argument field of SID in the SRH, and the mapping relationship between QFI, RQI, and SID is used to determine QoS flow information.

[0405] It should be noted that the service quality control device provided in this application is capable of achieving... Figures 1-3 as well as Figure 5 All method steps implemented in the method embodiment can achieve the same technical effect. Therefore, the parts that are the same as those in the method embodiment and their beneficial effects will not be described in detail here.

[0406] It should be noted that the division of the units in the embodiments of the present application is illustrative, and is merely a logical function division. In actual implementation, another division manner can be used. In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0407] When the integrated unit is realized in the form of a software functional unit and sold or used as an independent product, the integrated unit can be stored in a processor-readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the part that contributes to the prior art or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to perform all or part of the steps of the methods in the embodiments of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various media that can store program codes.

[0408] The embodiments of the present application also provide a non-transitory readable storage medium. The non-transitory readable storage medium stores a computer program, and the computer program is used to cause a processor to execute any one of the method embodiments.

[0409] The non-transitory readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to a magnetic memory (such as a floppy disk, a hard disk, a magnetic tape, a magneto-optical disk (MO), etc.), an optical memory (such as a CD, a DVD, a BD, a HVD, etc.), and a semiconductor memory (such as a ROM, an EPROM, an EEPROM, a non-volatile memory (NAND FLASH), a solid state disk (SSD)), etc.

[0410] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can be in the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can be in the form of a computer program product implemented on one or more computer usable storage media (including but not limited to a magnetic disk storage and an optical storage, etc.) containing computer usable program codes.

[0411] The computer executable instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operations 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 Figure 1 one or more flows and / or functions specified in the flowchart Figure 1 one or more flows and / or functions specified in the flowchart

[0412] These processor-executable instructions can also be stored in a processor-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 processor-readable memory produce an article of manufacture including instructions which implement the functions specified in the flowchart Figure 1 one or more flows and / or functions specified in the flowchart Figure 1 one or more flows and / or functions specified in the flowchart

[0413] These processor-executable instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operations 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 Figure 1 one or more flows and / or functions specified in the flowchart Figure 1 one or more flows and / or functions specified in the flowchart

[0414] Obviously, numerous modifications and variations of the present application are possible in light of the above teachings. It is therefore to be understood that within the scope of the claims and their equivalents, the application can be practiced otherwise than as specifically described.

Claims

1. A quality of service control method, characterized by, The method is applied to a radio access network (RAN), and the method comprises: receiving uplink user data packets of a terminal; packaging the uplink user data packets into a new-generation IP bearer protocol (SRv6) data packet format based on IPv6 and source routing, wherein a service quality (QoS) flow information is contained in a segment routing header (SRH) of the SRv6 data packet, and the QoS flow information comprises a QoS flow identifier (QFI) used for indicating a QoS flow; sending the SRv6 data packet carrying the QFI to a user plane function (UPF) used for performing corresponding operations according to the QFI.

2. The method of claim 1, wherein, The packaging of the uplink user data packets into the SRv6 data packet format based on IPv6 and source routing comprises: if a segment identifier (SID) is single-protocol data unit session (PDU Session) granularity, the uplink user data packets are packaged into the SRv6 data packet format by using a Tag field in the SRH to carry QoS flow information or using an extension field in the SRH to carry QoS flow information; if the SID is multi-PDU Session granularity, the uplink user data packets are packaged into the SRv6 data packet format by using the extension field in the SRH to carry QoS flow information; if the SID is QoS granularity, the uplink user data packets are packaged into the SRv6 data packet format by using the Tag field in the SRH to carry QoS flow information or defining a SID behavior to carry QoS flow information through an Argument field in the SID in the SRH.

3. The method of claim 2, wherein, If the SID is single-PDU Session granularity, the packaging of the uplink user data packets into the SRv6 data packet format comprises: when the SRH is packaged for the uplink user data packets, QoS flow information is packaged into a Tag field of the SRH; the QoS flow information further comprises a reflective QoS identifier (RQI) used for indicating whether a QoS flow is enabled for reflective QoS; or when the SRH is packaged for the uplink user data packets, QoS flow information is packaged into an extension field of the SRH; the QoS flow information further comprises an RQI used for indicating whether a QoS flow is enabled for reflective QoS.

4. The method of claim 3, wherein, The packaging of the QoS flow information into the Tag field of the SRH comprises: determining that the Tag field of the SRH carries QoS flow information by setting a flag in the Tag field of the SRH; packaging a QFI and an RQI in QoS flow information into the Tag field of the SRH, respectively.

5. The method of claim 3, wherein, The extension field is used for indicating the type, length and value of an information element; the packaging of the QoS flow information into the extension field of the SRH comprises: packaging a QFI and an RQI into the extension field of the SRH, respectively. By setting a flag in the SRH, it is determined that a Map field in an extension field of the SRH is invalid or ignored, wherein the Map field is used to indicate a mapping relationship between a PDU Session ID and a UE ID, and the extension field is used to determine a corresponding QoS flow.

6. The method of claim 2, wherein, If the SID is a multi-PDU Session granularity, the encapsulation of the uplink user data packet into an SRv6 packet format includes: When encapsulating the uplink user data packet into the SRH, QoS flow information is encapsulated into an extension field of the SRH.

7. The method of claim 6, wherein, The extension field is used to indicate a type, length and value of an information element, and the QoS flow information further includes a mapping relationship between a PDU Session ID and a UE ID, and an RQI; The RQI is used to indicate whether a QoS flow is enabled for reflective QoS; The encapsulation of the QoS flow information into the extension field of the SRH includes: QFI and RQI are respectively encapsulated into the extension field of the SRH; By setting a flag in the SRH, it is determined that a Map field in an extension field of the SRH is valid, and the Map field is used to indicate a mapping relationship between a PDU Session ID and a UE ID. The extension field is used to determine a specified QoS flow of a specified PDU session of a corresponding user.

8. The method according to any one of claims 2 to 7, characterized in that, If the SID is a QoS granularity, the encapsulation of the uplink user data packet into an SRv6 packet format includes: QoS flow information is encapsulated into an Argument field of the SID in the SRH, wherein the SID is used to determine a QoS flow.

9. The method of claim 8, wherein, The QoS flow information further includes an RQI, and the RQI is used to indicate whether a QoS flow is enabled for reflective QoS. The encapsulation of the QoS flow information into the Argument field of the SID in the SRH includes: QFI and RQI are respectively encapsulated into the Argument field of the SID in the SRH; or 10. A quality of service control method characterized by comprising: QFI, RQI and a mapping relationship of the SID are encapsulated into the Argument field of the SID in the SRH, and the mapping relationship of the QFI, RQI and the SID is used to determine QoS flow information. The method is applied to a user plane function (UPF), and the method includes: Encapsulating a downlink user data packet of a UE into an SRv6 packet format, wherein a SRH in a header of the SRv6 packet includes QoS flow information, and the QoS flow information includes QFI, and the QFI is used to indicate a QoS flow; Sending the SRv6 packet carrying the QFI to an intermediate UPF, and the intermediate UPF is used to send the SRv6 packet carrying the QFI to a RAN; or Sending the SRv6 packet carrying the QFI to the RAN, and the RAN is used to map a QoS flow to a corresponding data radio bearer (DRB) according to the QFI and corresponding QoS configuration information. The encapsulation of the downlink user data packet of the UE into the SRv6 packet format includes: If the SID is single-PDU Session granularity, the downlink user data packet is encapsulated into SRv6 packet format by carrying QoS flow information in a Tag field in the SRH or carrying QoS flow information in an extension field in the SRH; If the SID is multi-PDU Session granularity, the downlink user data packet is encapsulated into SRv6 packet format by carrying QoS flow information in an extension field in the SRH; If the SID is QoS granularity, the downlink user data packet is encapsulated into SRv6 packet format by carrying QoS flow information in a Tag field in the SRH or defining SID behavior to carry QoS flow information in an Argument field in the SRH.

11. The method of claim 10, wherein, If the SID is single-PDU Session granularity, the encapsulating the downlink user data packet into SRv6 packet format comprises: When encapsulating the SRH for the downlink user data packet, encapsulating QoS flow information into a Tag field in the SRH; the QoS flow information further comprises reflective quality of service identification RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS; or, When encapsulating the SRH for the downlink user data packet, encapsulating QoS flow information into an extension field in the SRH; the QoS flow information further comprises RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS.

12. The method of claim 11, wherein, The encapsulating the QoS flow information into the Tag field in the SRH comprises: determining that the Tag field in the SRH carries QoS flow information by setting a flag bit Flag in the Tag field in the SRH; encapsulating QFI and RQI in the QoS flow information into the Tag field in the SRH.

13. The method of claim 11, wherein, The extension field is used to indicate the type, length and value of an information element; the encapsulating the QoS flow information into the extension field in the SRH comprises: encapsulating QFI and RQI into the extension field in the SRH; determining that a Map field in the extension field in the SRH is invalid or ignored by setting a flag bit Flag in the SRH, wherein the Map field is used to indicate the mapping relationship between a PDU Session ID and a UE ID, and the extension field is used to determine the corresponding QoS flow.

14. The method of claim 10, wherein, If the SID is multi-PDU Session granularity, the encapsulating the downlink user data packet into SRv6 packet format comprises: When encapsulating the SRH for the downlink user data packet, encapsulating QoS flow information into an extension field in the SRH.

15. The method of claim 14, wherein, The extension field is used to indicate the type, length and value of an information element, and the QoS flow information further comprises the mapping relationship between a PDU Session ID and a UE ID and RQI; the RQI is used to indicate whether a QoS flow enables reflective QoS; the encapsulating the QoS flow information into the extension field in the SRH comprises: The QFI and the RQI are respectively encapsulated into the extension field of the SRH. A flag bit is set in the SRH to determine that a Map field in the extension field of the SRH is effective, and the Map field is used to indicate a mapping relationship between a PDU Session ID and a UE ID. The extension field is used to determine a specified QoS flow of a specified PDU session of a corresponding user.

16. The method according to any one of claims 10-15, characterized in that, If the SID is QoS granularity, the encapsulation of the downlink user data packet into the SRv6 data packet format includes: QoS flow information is encapsulated into an Argument field of the SID in the SRH, and the SID is used to determine the QoS flow.

17. The method of claim 16, wherein, The QoS flow information further includes an RQI, and the RQI is used to indicate whether a QoS flow is enabled for reflective QoS. The QoS flow information is encapsulated into the Argument field of the SID in the SRH, including: The QFI and the RQI are respectively encapsulated into the Argument field of the SID in the SRH; or 18. A quality of service control apparatus characterized by comprising: A mapping relationship between the QFI, the RQI and the SID is encapsulated into the Argument field of the SID in the SRH, and the mapping relationship between the QFI, the RQI and the SID is used to determine the QoS flow information. The device is applied to a radio access network (RAN), and the device includes: A receiving unit configured to receive an uplink user data packet of a terminal; A processing unit configured to encapsulate the uplink user data packet into an SRv6 data packet format, wherein a SRH in a header of the SRv6 data packet includes QoS flow information, and the QoS flow information includes a QFI, and the QFI is used to indicate a QoS flow; 19. A quality of service control apparatus characterized by comprising: A sending unit configured to send the SRv6 data packet carrying the QFI to a user plane function (UPF), and the UPF is configured to perform a corresponding operation according to the QFI. The device is applied to a user plane function (UPF), and the device includes: A processing unit configured to encapsulate a downlink user data packet of a terminal into an SRv6 data packet format, wherein a SRH in a header of the SRv6 data packet includes QoS flow information, and the QoS flow information includes a QFI, and the QFI is used to indicate a QoS flow; A sending unit configured to send the SRv6 data packet carrying the QFI to an intermediate UPF, and the intermediate UPF is configured to send the SRv6 data packet carrying the QFI to a RAN; or The SRv6 data packet carrying the QFI is sent to the RAN, and the RAN is configured to map a QoS flow to a corresponding data radio bearer (DRB) according to the QFI and corresponding QoS configuration information. The processing unit is specifically configured to: if the SID is single-PDU Session granularity, encapsulate the downlink user data packet into an SRv6 packet format by using a Tag field in the SRH to carry QoS flow information or using an extension field in the SRH to carry the QoS flow information; if the SID is multi-PDU Session granularity, encapsulate the downlink user data packet into an SRv6 packet format by using an extension field in the SRH to carry the QoS flow information; and if the SID is QoS granularity, encapsulate the downlink user data packet into an SRv6 packet format by using a Tag field in the SRH to carry the QoS flow information or defining a SID behavior to carry the QoS flow information through an Argument field of the SID in the SRH.

20. A quality of service control apparatus characterized by comprising: The device is applied to a radio access network (RAN), and the device includes a memory, a transceiver, and a processor. The memory is configured to store a computer program, and the transceiver is configured to transceive data under control of the processor. The processor is configured to read the computer program in the memory and perform the following operations: receive uplink user data packets of a terminal; encapsulate the uplink user data packets into an SRv6 packet format, wherein an SRv6 packet header (SRH) contains quality of service (QoS) flow information, and the QoS flow information includes a QFI, which is used to indicate a QoS flow; send the SRv6 packet carrying the QFI to a user plane function (UPF), and the UPF is configured to perform corresponding operations according to the QFI.

21. The apparatus of claim 20, wherein, When the uplink user data packets are encapsulated into the SRv6 packet format, the processor is specifically configured to: if a segment routing identifier (SID) is single-PDU Session granularity, encapsulate the uplink user data packets into the SRv6 packet format by using a Tag field in the SRH to carry QoS flow information or using an extension field in the SRH to carry the QoS flow information; if the SID is multi-PDU Session granularity, encapsulate the uplink user data packets into the SRv6 packet format by using an extension field in the SRH to carry the QoS flow information; if the SID is QoS granularity, encapsulate the uplink user data packets into the SRv6 packet format by using a Tag field in the SRH to carry the QoS flow information or defining a SID behavior to carry the QoS flow information through an Argument field of the SID in the SRH.

22. The apparatus of claim 21, wherein, When the SID is single-PDU Session granularity, the processor is specifically configured to encapsulate the uplink user data packets into the SRv6 packet format by: encapsulating QoS flow information into a Tag field of the SRH when encapsulating the SRH for the uplink user data packets; the QoS flow information further includes an RQI, which is used to indicate whether a QoS flow is enabled for reflective QoS; or When the SRH is encapsulated for the uplink user data packet, QoS flow information is encapsulated into an extension field of the SRH.

23. The apparatus of claim 21, wherein, The processor is specifically configured to, when the SID is a multi-PDU Session granularity, encapsulate the uplink user data packet into an SRv6 packet format, and specifically includes: When the SRH is encapsulated for the uplink user data packet, QoS flow information is encapsulated into an extension field of the SRH.

24. The apparatus of any one of claims 21-23, wherein, The processor is specifically configured to, when the SID is a QoS granularity, encapsulate the uplink user data packet into an SRv6 packet format, and specifically includes: QoS flow information is encapsulated into an Argument field of the SID in the SRH; wherein the SID is used to determine a QoS flow.

25. A quality of service control device, characterized by The device is applied to a user plane function (UPF), and the device includes a memory, a transceiver, and a processor. The memory is configured to store a computer program; the transceiver is configured to transceive data under control of the processor; and the processor is configured to read the computer program in the memory and perform the following operations: encapsulate a downlink user data packet for a UE into an SRv6 packet format, wherein an SRv6 packet header (SRH) contains QoS flow information; wherein the QoS flow information includes a QFI, and the QFI is used to indicate a QoS flow; send the SRv6 packet carrying the QFI to an intermediate UPF, and the intermediate UPF is configured to send the SRv6 packet carrying the QFI to a radio access network (RAN); or send the SRv6 packet carrying the QFI to the RAN, and the RAN is configured to map a QoS flow to a corresponding data radio bearer (DRB) according to the QFI and corresponding QoS configuration information; The processor is specifically configured to, when the downlink user data packet for the UE is encapsulated into an SRv6 packet format, specifically include: If the SID is a single-PDU Session granularity, the downlink user data packet is encapsulated into an SRv6 packet format by using a Tag field in the SRH to carry QoS flow information or using an extension field in the SRH to carry QoS flow information; If the SID is a multi-PDU Session granularity, the downlink user data packet is encapsulated into an SRv6 packet format by using an extension field in the SRH to carry QoS flow information; If the SID is a QoS granularity, the downlink user data packet is encapsulated into an SRv6 packet format by using a Tag field in the SRH to carry QoS flow information or defining a SID behavior to carry QoS flow information through an Argument field of the SID in the SRH.

26. The apparatus of claim 25, wherein, The processor is specifically configured to, when the SID is a single-PDU Session granularity, encapsulate the downlink user data packet into an SRv6 packet format, and specifically includes: When the SRH is encapsulated for the downlink user data packet, QoS flow information is encapsulated into a Tag field of the SRH; the QoS flow information further comprises an RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS; or When the SRH is encapsulated for the downlink user data packet, QoS flow information is encapsulated into an extension field of the SRH; the QoS flow information further comprises an RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS.

27. The apparatus of claim 25, wherein, The processor is configured to, when the SID is a multi-PDUSession granularity, encapsulate the downlink user data packet into an SRv6 packet format, and specifically comprises: When the SRH is encapsulated for the downlink user data packet, QoS flow information is encapsulated into an extension field of the SRH.

28. The apparatus of any of claims 25-27, wherein, The processor is configured to, when the SID is a QoS granularity, encapsulate the downlink user data packet into an SRv6 packet format, and specifically comprises: QoS flow information is encapsulated into an Argument field of the SID in the SRH; wherein the SID is used to determine a QoS flow.

29. A processor-readable storage medium, comprising: The processor readable storage medium stores a computer program, and the computer program is used to make the processor execute the method in any one of claims 1 to 17.

Images