Service quality control method and device and readable storage medium

Abstract

The invention provides a service quality control method and device and a readable storage medium. The method comprises the following steps: receiving an uplink user data packet of a terminal; the uplink user data packet is packaged into an SRv6 data packet format, the head SRH of the SRv6 data packet comprises 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 executing corresponding operation according to the QFI. And the QoS demand of the user is ensured.

Description

Technical Field

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

[0002] SRv6 is a new generation of IP bearer protocol based on IPv6 and source routing. It can simplify network protocols and guarantee application-level SLAs. It will be the basis for building intelligent IP networks 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. This SID is called the SRv6 SID (here refers to the SRv6 segment identifier SID), which uses the IPv6 address format, but does not correspond to the IPv6 address of the interface included in any SR node.

[0003] New SRv6 Behaviors—Args.Mob.Session—are defined in IETF RFC 9433. The SRv6 Behaviors extend the Quality of Service (QoS) and QoS Flow ID (QFI) fields to meet QoS requirements.

[0004] However, Args.Mob.Session is SID-granular. In a mobile network based on the SRv6 user plane, the allocation of SID is not necessarily at the QoS flow granularity. If a corresponding SID is assigned to the UPF of each protocol data unit (PDU) Session, then after the SID is applied with 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 existing technology cannot implement QoS control by applying SID to different PDU Sessions or different QoS flows, and thus cannot guarantee the user's QoS requirements. Summary of the invention

[0005] The present application provides a service quality control method, device and readable storage medium, which solves the technical problem in the prior art that SID cannot be applied to different PDU Sessions or different QoS flows for QoS control, and thus cannot guarantee the user's QoS requirements.

[0006] In a first aspect, the present application provides a service quality control method, which is applied to a radio access network RAN, and the method includes:

[0007] receiving uplink user data packets from a 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 the SRv6 data packet header SRH contains quality of service QoS flow information, and the QoS flow information includes a quality of service flow identifier QFI, and the QFI is used to indicate the QoS flow;

[0009] 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.

[0010] In an embodiment of the present application, based on the received uplink user data packet, it is encapsulated and 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 QFI is sent to UPF. UPF performs corresponding operations based on the indicated QoS flow, which can realize QoS control of SID applied to different PDUSessions or different QoS flows, thereby ensuring the user's QoS requirements.

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

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

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

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

[0015] In the embodiment of the present application, different encapsulation strategies are supported based on different SID granularities, and then QoS flow information encapsulation is implemented according to the corresponding strategies, so that 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 be bound to one QoS flow information in the prior art is solved, resulting in the SID being applied to only one QoS flow after applying the Args.Mob.Session behavior, and the problem of being unable to realize the identification and positioning of multiple QoS flows in the PDU Session is solved. At the same time, the problem that the number of SIDs on the UPF increases due to different SIDs for different QoS flows in the PDU session, which in turn leads to excessive occupation and waste of storage resources and processing resources in the UPF node is solved. It can realize the QoS control of SIDs applied to different PDU Sessions or different QoS flows while saving resources.

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

[0017] When encapsulating the SRH for the uplink user data packet, encapsulating the QoS flow information into the Tag field of the SRH; the QoS flow information also includes a reflective service quality 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, the QoS flow information is encapsulated into the extension field of the SRH; the QoS flow information also includes an RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS.

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

[0020] By setting a flag bit Flag in the Tag field of the SRH, determining to indicate that the Tag field of the SRH carries the QoS flow information;

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

[0022] In an embodiment of the present application, if the SID is a single PDU Session granularity, by setting a flag bit Flag in the Tag field of the SRH, for example, when the flag bit Flag is a custom or specified arbitrary value, it indicates that the Tag field of the SRH carries QoS flow information, where the QoS flow information may include QFI and RQI, and the corresponding QoS flow is determined by QFI, and whether reflective QoS is enabled is determined by RQI.

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

[0024] Encapsulating the QFI and RQI into the extension fields of the SRH respectively;

[0025] By setting a flag Flag in the SRH, it is determined that the Map field in the extended 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 extended field is used to determine the corresponding QoS flow.

[0026] In an embodiment of the present application, if the SID is a single PDU Session granularity, the QFI and RQI are first encapsulated into the extended fields of the SRH respectively, and the flag Flag is set in the SRH. For example, when the flag Flag is a custom or specified arbitrary value, it indicates that the Map field in the extended field of the SRH is invalid or ignored. Therefore, the corresponding QoS flow is determined by the QoS flow information carried in the extended field of the SRH.

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

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

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

[0030] Encapsulating the QFI and RQI into the extension fields of the SRH respectively;

[0031] By setting a flag bit Flag in the SRH, it is determined that a Map field in an extended field indicating the SRH is effective, wherein 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 the designated QoS flow of the designated PDU session of the corresponding user.

[0033] In an embodiment of the present application, if the SID is a multi-PDU Session granularity, the QFI and RQI can be respectively encapsulated into the extension field of the SRH, and by setting the flag bit Flag in the SRH, for example, when the flag bit Flag is a custom or specified arbitrary value, it indicates that the Map field in the extension field of the SRH is valid. Therefore, the mapping relationship between the PDU SessionID and the UE ID carried in the extension field of the SRH is used to determine the specified QoS flow of the specified PDU Session of the corresponding user, and whether to enable reflective QoS is determined through the RQI.

[0034] Optionally, if the SID is a QoS granularity, encapsulating the uplink user data packet into an SRv6 data packet format includes:

[0035] 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.

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

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

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

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

[0040] In a second aspect, the present application provides a service quality control method, which is applied to a user plane function UPF, and the method includes:

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

[0042] Sending the SRv6 data packet carrying the QFI to the intermediate UPF, where the intermediate UPF is used to send the SRv6 data packet carrying the QFI to the RAN; or,

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

[0044] In an embodiment of the present application, a downlink user data packet of a terminal UE is encapsulated and encapsulated into an SRv6 data packet format including at least QoS flow information of a QFI to indicate a corresponding QoS flow, and the SRv6 data packet carrying the QFI is sent to an intermediate UPF, which is then sent to the RAN by the intermediate UPF, or the SRv6 data packet carrying the QFI is sent to the RAN; 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 QoS control of different PDU Sessions or different QoS flows, thereby ensuring the user's QoS requirements.

[0045] Optionally, encapsulating the downlink user data packet of the UE into an SRv6 data packet format includes:

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

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

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

[0049] In the embodiment of the present application, different encapsulation strategies are supported based on different SID granularities, and QoS flow information encapsulation is implemented 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 is solved, 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 the PDUSession cannot be realized. At the same time, the problem that the number of SIDs on the UPF increases due to different SIDs for different QoS flows in the PDU session, which in turn leads to excessive occupation and waste of storage resources and processing resources in the UPF node is solved. It can realize the QoS control of SIDs applied to different PDU Sessions or different QoS flows while saving resources.

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

[0051] When encapsulating the SRH for the downlink user data packet, encapsulating the QoS flow information into the Tag field of the SRH; the QoS flow information also includes a reflective service quality 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, the QoS flow information is encapsulated into the extension field of the SRH; the QoS flow information also includes an RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS.

[0053] Optionally, encapsulating the QoS flow information into the Tag field of the SRH includes:

[0054] By setting a flag bit Flag in the Tag field of the SRH, determining to indicate that the Tag field of the SRH carries the QoS flow information;

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

[0056] In an embodiment of the present application, if the SID is a single PDU Session granularity, by setting a flag bit Flag in the Tag field of the SRH, for example, when the flag bit Flag is a custom or specified arbitrary value, it indicates that the Tag field of the SRH carries QoS flow information, where the QoS flow information may include QFI and RQI, and the corresponding QoS flow is determined by QFI, and whether reflective QoS is enabled is determined by RQI.

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

[0058] Encapsulating the QFI and RQI into the extension fields of the SRH respectively;

[0059] By setting a flag Flag in the SRH, it is determined that the Map field in the extended 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 extended field is used to determine the corresponding QoS flow.

[0060] In an embodiment of the present application, if the SID is a single PDU Session granularity, the QFI and RQI are first encapsulated into the extended fields of the SRH respectively, and the flag Flag is set in the SRH. For example, when the flag Flag is a custom or specified arbitrary value, it indicates that the Map field in the extended field of the SRH is invalid or ignored. Therefore, the corresponding QoS flow is determined by the QoS flow information carried in the extended field of the SRH.

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

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

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

[0064] Encapsulating the QFI and RQI into the extension fields of the SRH respectively;

[0065] By setting a flag bit Flag in the SRH, it is determined that a Map field in an extended field indicating the SRH is effective, wherein 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 the designated QoS flow of the designated PDU session of the corresponding user.

[0067] In an embodiment of the present application, if the SID is a multi-PDU Session granularity, the QFI and RQI can be respectively encapsulated into the extension field of the SRH, and by setting the flag bit Flag in the SRH, for example, when the flag bit Flag is a custom or specified arbitrary value, it indicates that the Map field in the extension field of the SRH is valid. Therefore, the mapping relationship between the PDU SessionID and the UE ID carried in the extension field of the SRH is used to determine the specified QoS flow of the specified PDU Session of the corresponding user, and whether to enable reflective QoS is determined through the RQI.

[0068] Optionally, if the SID is a QoS granularity, encapsulating the downlink user data packet into an SRv6 data packet format includes:

[0069] 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.

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

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

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

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

[0074] In a third aspect, the present application provides a service quality control device, the device is applied to a radio access network RAN, and the device includes:

[0075] A receiving unit, used for receiving an uplink user data packet from a terminal;

[0076] A processing unit, configured to encapsulate the uplink user data packet into an SRv6 data packet format, wherein the SRv6 data packet header SRH includes quality of service QoS flow information; wherein the QoS flow information includes a QFI, and the QFI is used to indicate a QoS flow;

[0077] A sending unit is used to send 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.

[0078] In a fourth aspect, the present application provides a service quality control device, the device is applied to a user plane function UPF, and the device includes:

[0079] A processing unit, configured to encapsulate a downlink user data packet of the UE into an SRv6 data packet format, wherein the SRv6 data packet header SRH includes QoS flow information; wherein the QoS flow information includes a QFI, and the QFI is used to indicate a QoS flow;

[0080] a sending unit, configured to send the SRv6 data packet carrying the QFI to an intermediate UPF, wherein the intermediate UPF is configured to send the SRv6 data packet carrying the QFI to the RAN; or

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

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

[0083] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0084] receiving uplink user data packets from a terminal;

[0085] Encapsulating the uplink user data packet into an SRv6 data packet format, wherein the SRv6 data packet header SRH contains quality of service QoS flow information, the QoS flow information includes QFI, and the QFI is used to indicate the QoS flow;

[0086] 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.

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

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

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

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

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

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

[0093] When encapsulating the SRH for the uplink user data packet, the QoS flow information is encapsulated into the extension field of the SRH; the QoS flow information also 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 a multi-PDU Session granularity, encapsulate the uplink user data packet into an SRv6 data packet format, specifically including:

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

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

[0097] 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.

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

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

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

[0101] Sending the SRv6 data packet carrying the QFI to the intermediate UPF, where the intermediate UPF is used to send the SRv6 data packet carrying the QFI to the RAN; or,

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

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

[0104] If the SID is a single PDU Session granularity, the downlink user data packet is encapsulated into an SRv6 data packet format by using the Tag field in the SRH to carry the QoS flow information, or by using the extended field in the SRH to carry the QoS flow information;

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

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

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

[0108] When encapsulating the SRH for the downlink user data packet, encapsulating the QoS flow information into the Tag field of the SRH; the QoS flow information also 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 also includes an RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS.

[0110] Optionally, the processor is configured to, when the SID is a multi-PDU Session granularity, encapsulate the downlink user data packet into an SRv6 data packet format, specifically comprising:

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

[0112] Optionally, the processor is configured to, when the SID is a QoS granularity, encapsulate the downlink user data packet into an SRv6 data packet format, specifically comprising:

[0113] 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.

[0114] In a seventh aspect, the present application provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute any of the methods described above.

[0115] The present application provides a method, device and readable storage medium for controlling quality of service. First, an uplink user data packet of a 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, and the QoS flow information includes a 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, it is encapsulated and 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 that the SID can be applied to different PDU Sessions or different QoS flows. QoS control, thereby ensuring the user's QoS requirements.

[0116] It should be understood that the contents described in the above summary of the invention are not intended to limit the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0117] In order to more clearly illustrate the technical solutions in the present application or the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

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

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

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

[0121] Figure 4 A flow chart of a method for controlling quality of service provided in an embodiment of the present application;

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

[0123] Figure 6 A schematic diagram of the structure of a service quality control device provided in an embodiment of the present application;

[0124] Figure 7 A schematic diagram of the structure of a service quality control device provided by another embodiment of the present application;

[0125] Figure 8 A schematic diagram of the structure of a service quality control device provided in yet another embodiment of the present application;

[0126] Fig. 9 A schematic diagram of the structure of a service quality control device provided in yet another embodiment of the present application. DETAILED DESCRIPTION

[0127] The term "and / or" in this application describes the association relationship of associated objects, indicating that there may be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.

[0128] In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.

[0129] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0130] In order to clearly understand the technical solution of the present application, the solution of the prior art is first introduced in detail. The 5G QoS model is based on QoS flows, where QoS flows are 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 need to guarantee the flow bit rate (GBR QoS flows) and QoS flows that do not need to guarantee the flow bit rate (non GBR QoS flows).

[0131] Among them, for the downlink (DL): the data packet is compared with the packet detection rule (PDR) established by the session management function (SMF) in the user plane function (UPF) to classify the data packet, and then each PDR is associated with one or more QoS enforcement rules (QER), which contains information on how to execute, such as the specific rate. The QER also includes the QFI value to be added to the GTP-U header (N3 encapsulation header).

[0132] For the uplink (UL): The UE application layer generates a packet and first compares it with the packet filters selected from the packet filter set in the UE. At this time, these packet filters are checked in priority order, and when a match is found, a QFI is assigned to the packet. The assigned QFI and the packet are sent to the SDAP layer (service data adaption protocol, a new protocol layer in NR) of the UE access stratum (AS), which performs the mapping of QFI to data radio bearer (DRB) according to the available mapping rules. If a match is found, the packet will be sent on the corresponding DRB; if there is no match, the packet will be sent on the default DRB, and the SDAP header will contain the QFI so that NG-RAN can decide whether to move the QFI to another DRB.

[0133] SRv6 is a new generation of IP bearer protocol based on IPv6 and source routing. It can unify traditional complex network protocols, simplify network protocols and guarantee application-level SLAs. It will be the basis for building intelligent IP networks 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. This SID is called the SRv6 SID (here refers to the SRv6 segment identifier SID), which uses the IPv6 address format, but does not correspond to the IPv6 address of the interface included in any SR node.

[0134] New SRv6 Behaviors—Args.Mob.Session—are defined in IETF RFC 9433. The SRv6 Behaviors extend the Quality of Service (QoS) and QoS Flow ID (QFI) fields to meet QoS requirements.

[0135] However, Args.Mob.Session (i.e., providing billing, buffering, or other purpose requirements for each PDU session provided by some mobile nodes; Args.Mob.Session argument format is used in combination with End.Map, End.DT4 / End.DT6 / End.DT46 and End.DX4 / End.DX6 / End.DX2behaviors. Args.Mob.Session is applied in scenarios where multiple PDU Sessions are aggregated in one SID. Because SRv6 SID is not necessarily instantiated as per PDUSession (per PDU session). Args.Mob.Session helps UPF to perform the requirements of each QFI and / or each PDU session granularity, which is SID granularity. In mobile networks based on the SRv6 user plane, the allocation of SIDs is not necessarily at the QoS flow granularity. If the allocation of SIDs is at the PDU Session granularity, after the SID applies Args.Mob.Session, the extended field can only be applied to one QoS flow, and 1 PDU cannot be implemented. 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 of the user application to be inconsistent with the user's request, thereby failing to meet the user's needs.

[0136] Therefore, the prior art cannot implement QoS control by applying SID to different PDU Sessions or different QoS flows, and thus cannot guarantee the QoS requirements of users.

[0137] The inventors further discovered that in order to solve the problem in the prior art that it is impossible to implement QoS control of SIDs for different PDU Sessions or different QoS flows, and thus is unable to guarantee the user's QoS requirements, the QoS Flow information can be encapsulated in the SRv6 packet header SRH when encapsulating the SRv6 packet format, so that QoS Flow information encapsulation can be achieved based on different SID granularities, thereby achieving QoS control.

[0138] Therefore, based on the creative research of the above inventors, the service quality control method and device proposed in the present application are proposed. In the present application, based on the received uplink user data packet, it is encapsulated and 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 QFI is sent to UPF. UPF performs corresponding operations based on the indicated QoS flow, so that SID can be applied to different PDU Sessions or different QoS flows. QoS control, thereby ensuring the user's QoS requirements, solves the problem that one SID can only be bound to one QoS flow information in the prior art, resulting in the SID being applied to only one QoS flow after applying the Args.Mob.Session behavior, and cannot realize the identification and positioning of multiple QoS flows in PDUSession. At the same time, it also solves the problem that the number of SIDs on the UPF increases due to different SIDs of different QoS flows in PDU sessions, thereby causing excessive occupation and waste of storage resources and processing resources in the UPF node. It can realize the QoS control of SID applied to different PDU Sessions or different QoS flows while saving resources.

[0139] Among them, the method and the device are based on the same application concept. Since the method and the device solve the problem in a similar principle, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.

[0140] Embodiments of the present application will be described below with reference to the accompanying drawings.

[0141] The following implements QoS control by carrying or identifying QoS flow information in at least three ways:

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

[0143] Combination Figure 1 As shown, Figure 1 A schematic diagram of using the Tag field in the SRH to carry QoS flow information provided by an embodiment of the present application, such as Figure 1 As shown, a flag Flag is set in the Tag field, and the flag Flag value can be custom or specified (not specifically limited here), which is used to indicate whether the Tag field of the SRH carries QoS flow information. For example: the flag Flag takes a value of 0 or 1. When the Flag value is 1, it indicates that the field carries QoS flow information. When the Flag value is 1, the flag Flag is ignored, which can indicate that the QoS flow information carried by the field is invalid or ignored.

[0144] Among them, QFI is used to identify the QoS flow in the 5G system. RQI (Reflective QoS Indication) is used to indicate whether the QoS flow enables reflective QoS. The RQI value can be custom or specified (not specifically limited here), indicating whether a QoS flow enables reflective QoS; for example: the RQI value is 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 applicable to scenarios where the SID is a single PDUSession granularity or QoS granularity. That is, the UPF of each PDU Session has only one SID corresponding to the PDU Session (single PDU Session granularity) 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 in the table are only recommended options, which are only exemplary and not exclusive. The QFI and RQI lengths are not specifically limited here. Figure 2-Figure 3 The QFI and RQI lengths involved are exemplary and not specifically limited.

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

[0147] By carrying QoS flow information in the optional TLV (extension field) of the SRv6 packet header, the device is instructed to process the TLV.

[0148] Combination Figure 2 As shown, Figure 2 A schematic diagram of using the TLV field in the SRH to carry QoS flow information provided by an embodiment of the present application, such as Figure 2 As shown, a flag Flag is set in the TLV field in the SRH. The Flag value can be custom or specified (not specifically limited here), which is used to indicate whether the Map field in the extended field of the SRH (the Map field is used to indicate the mapping relationship between the PDU Session ID and the UE ID) is effective. For example: the Flag value is 0 or 1. When the Flag value is 1, it indicates 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 indicates that the Map field is invalid or does not exist, indicating that the subsequent fields of the flag Flag are no longer parsed, which can indicate that the QoS flow information indicated by the field is invalid or ignored. This method 2 is applicable to scenarios where the SID is a single PDU Session granularity or a multi-PDUSession granularity.

[0149] Among them, QFI is used to identify the QoS flow in the 5G system. RQI is used to indicate whether the QoS flow enables reflective QoS. The RQI value can be customized or specified (not specifically limited here), indicating whether a QoS flow enables reflective QoS; for example: RQI value is 0 or 1. When the RQI value is 1, it means that the UE enables reflective QoS; when the RQI value is 0, it means that the UE does not enable reflective QoS.

[0150] Map (PDU Session ID, UE ID): Applicable to the scenario where multiple PDU Sessions share a SID. Map (PDU Session ID, UE ID) + QFI is used to uniquely locate a QoS flow of a PDU Session of a user, that is, to determine the specified QoS flow of the specified PDU session of the corresponding user. Figure 3 The length and format of Map (PDU Session ID, UE ID) are only exemplary and are not specifically limited.

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

[0152] Combination Figure 3 As shown, Figure 3 A schematic diagram of identifying QoS flow information through the Argument field of the SID in the SRH provided in an embodiment of the present application, such as Figure 3 As shown, the Argument field carries QFI and RQI information or mapping information of QFI and RQI with SID (here, the mapping relationship is used to determine QoS flow information), so that the user plane node (including RAN) can determine the user's QoS requirements according to 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. This method 3 is applicable to the scenario where SID is the QoS granularity.

[0153] Among them, QFI is used to identify the QoS flow in the 5G system. RQI is used to indicate whether the QoS flow enables reflective QoS. The RQI value can be customized or specified (not specifically limited here), indicating whether a QoS flow enables reflective QoS; for example: RQI value is 0 or 1. When the RQI value is 1, it means that the UE enables reflective QoS; when the RQI value is 0, it means that the UE does not enable reflective QoS.

[0154] Therefore, a field is set or extended in the SRv6 packet header to identify the QoS Flow information, or a new SID Behavior is defined, that is, the Tag field in the SRH is used to carry the QoS information (here, the QoS flow information), the optional TLA field in the SRH is used to carry the QoS information (here, the QoS flow information), and the Argument field of the SID is used to carry or map the QoS information (here, the QoS flow information). Based on the QoS control method of the SRv6 user plane, QoS control is implemented in three cases: the same SID is the QoS Flow granularity, the single PDU Session granularity, and the multi-PDU Session granularity, thereby ensuring the user's QoS requirements.

[0155] Figure 4 A flow chart of a method for controlling quality of service provided in an embodiment of the present application is shown in FIG. Figure 4 As shown, the execution subject of the service quality control method provided in this embodiment is the radio access network RAN; the service quality control method provided in this embodiment of the application includes the following steps:

[0156] Step 101: Receive an uplink user data packet from a terminal.

[0157] Step 102: encapsulate the uplink user data packet into a data packet format of a new generation IP bearer protocol SRv6 based on IPv6 and source routing.

[0158] The SRv6 packet header SRH contains the quality of service QoS flow information, and the QoS flow information includes the quality of service flow identifier QFI, which is used to indicate the QoS flow

[0159] In an embodiment of the present application, for the downlink, the RAN receives an uplink user data packet of the terminal, and then encapsulates the uplink user data packet into an SRv6 data packet format. In order to be applicable to scenarios with different SID granularities, when encapsulating the uplink user data packet into an SRv6 data packet format, the SRv6 data packet header SRH can be used to encapsulate QoS flow information or information used to indicate or determine the QoS flow information, so that the SRH carries the QoS flow information or information used to indicate or determine the QoS flow information, wherein the QoS flow information includes a QFI used to indicate the QoS flow.

[0160] Step 103: Send the SRv6 data packet carrying the QFI to the 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, and the UPF determines the unique QoS flow according to the QFI carried by the SRv6 data packet, and then performs corresponding operations such as rate control and counting according to the characteristics corresponding to the QoS flow, such as rate.

[0162] In the embodiment of the present application, first, an uplink user data packet of a 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, and the QoS flow information includes a 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, it is encapsulated and encapsulated into an SRv6 data packet format including at least QoS flow information of the QFI, so as 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 that the SID can be applied to different PDU Sessions or different QoS flows. QoS control, thereby ensuring the user's QoS requirements.

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

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

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

[0166] If the SID is a QoS granularity, the uplink user data packet is encapsulated into an SRv6 data packet format by using the Tag field in the SRH to carry the QoS flow information, or by 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 a single PDU Session granularity, the uplink user data packet can be encapsulated into the SRv6 data packet format based on method 1 or method 2; if the SRv6 segment identifier SID is a multi-PDU Session granularity, the uplink user data packet can be encapsulated into the SRv6 data packet format based on method 2; if the SRv6 segment identifier SID is a QoS granularity, the uplink user data packet can be encapsulated into the SRv6 data packet format based on method 1 or method 3.

[0168] Therefore, based on different SID granularities, different encapsulation strategies are supported, and QoS flow information encapsulation is implemented according to the corresponding strategies, so that 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 be bound to one QoS flow information in the prior art is solved, resulting in the SID being applied to only one QoS flow after applying the Args.Mob.Session behavior, and being unable to realize the identification and positioning of multiple QoS flows in the PDU Session. At the same time, the problem that the number of SIDs on the UPF increases due to different SIDs for different QoS flows in the PDU session, which in turn leads to excessive occupation and waste of storage resources and processing resources in the UPF node is solved. It can realize the QoS control of SIDs applied to different PDU Sessions or different QoS flows while saving resources.

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

[0170] When encapsulating the SRH for the uplink user data packet, encapsulating the QoS flow information into the Tag field of the SRH; the QoS flow information also includes a reflective service quality 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, the QoS flow information is encapsulated into the extension field of the SRH; the QoS flow information also includes an RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS.

[0172] In an embodiment of the present application, if the SID is a single PDU Session granularity, the uplink user data packet can be encapsulated into an SRv6 data packet format based on method 1 or method 2: for method 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 method 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, encapsulating the QoS flow information into the Tag field of the SRH includes:

[0174] By setting a flag bit Flag in the Tag field of the SRH, determining to indicate that 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 an embodiment of the present application, if the SID is a single PDU Session granularity, by setting a flag bit Flag in the Tag field of the SRH, for example, when the flag bit Flag is a custom or specified arbitrary value, it indicates that the Tag field of the SRH carries QoS flow information, where the QoS flow information may include QFI and RQI, and the corresponding QoS flow is determined by QFI, and whether reflective QoS is enabled is determined by RQI.

[0177] Specifically, for method 1, by setting the flag bit Flag in the Tag field, the flag bit Flag value can be custom or specified (not specifically limited here), which is used to indicate whether the Tag field of the SRH carries QoS flow information, for example: the flag bit Flag takes a value of 0 or 1. When the Flag value is 1, it indicates that the field carries QoS flow information.

[0178] Based on method 1, the following is a detailed description through embodiment 1.

[0179] Exemplary embodiment 1 (SID is PDU Session granularity)

[0180] Combination Figure 1 As shown, when the SID is a PDU Session granularity, the service quality control method provided by this embodiment includes the following steps:

[0181] UL: When RAN encapsulates the SRv6 header for the data packet (here refers to the uplink user data packet) according to the QFI and QoS Profile (QoS configuration information), the QoS information described in mode 1 is carried in the Tag field of the SRH. After that, the UPF performs the corresponding QoS features 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 encapsulating the QoS flow information into the extension field of the SRH includes:

[0183] Encapsulating the QFI and RQI into the extension fields of the SRH respectively;

[0184] By setting a flag Flag in the SRH, it is determined that the Map field in the extended 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 extended field is used to determine the corresponding QoS flow.

[0185] In an embodiment of the present application, if the SID is a single PDU Session granularity, the QFI and RQI are first encapsulated into the extended fields of the SRH respectively, and the flag Flag is set in the SRH. For example, when the flag Flag is a custom or specified arbitrary value, it indicates that the Map field in the extended field of the SRH is invalid or ignored. Therefore, the corresponding QoS flow is determined by the QoS flow information carried in the extended field of the SRH.

[0186] For method 2, by setting the flag bit Flag in the extended field (for example, TLV field) in the SRH, the Flag value can be custom 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 extended field of the SRH is effective. 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, indicating that the subsequent fields of the flag bit Flag are no longer parsed, which can indicate that the QoS flow information indicated by the field is invalid or ignored. The unique QoS flow is determined by the QFI carried by the TLV field in the SRH, and whether to enable reflective QoS is determined by the RQI.

[0187] Based on method 2, the following is a detailed description through embodiment 2.

[0188] Exemplary embodiment 2 (SID is PDU Session granularity)

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

[0190] UL: When RAN encapsulates the SRv6 header for the data packet (here refers to the uplink user data packet) according to the QFI and QoS Profile (QoS configuration information), it carries the QoS information in the TLV field of the SRH and sets the value of the Flag to 0, indicating that the subsequent fields will no longer be parsed. After that, the UPF performs the corresponding QoS features based on the QoS information in the TLV in the SRH.

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

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

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

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

[0195] Encapsulating the QFI and RQI into the extension fields of the SRH respectively;

[0196] By setting a flag bit Flag in the SRH, it is determined that a Map field in an extended field indicating the SRH is effective, wherein the Map field is used to indicate a mapping relationship between a PDU Session ID and a UE ID;

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

[0198] In an embodiment of the present application, if the SID is a multi-PDU Session granularity, the QFI and RQI can be respectively encapsulated into the extension field of the SRH, and by setting the flag bit Flag in the SRH, for example, when the flag bit Flag is a custom or specified arbitrary value, it indicates that the Map field in the extension field of the SRH is valid. Therefore, the mapping relationship between the PDU SessionID and the UE ID carried in the extension field of the SRH is used to determine the specified QoS flow of the specified PDU Session of the corresponding user, and whether to enable reflective QoS is determined through the RQI.

[0199] Specifically, for method 2, by setting a flag Flag in an extended field (e.g., a TLV field) in the SRH, the Flag value can be custom 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 extended field of the SRH is effective. For example: the Flag value is 0 or 1. When the Flag value is 1, it indicates 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.

[0200] Based on method 2, the following is described in detail through embodiment 3.

[0201] Exemplary embodiment 3 (SID is a multi-PDU session granularity)

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

[0203] UL: When RAN encapsulates the SRv6 header for the data packet (here refers to the uplink user data packet) according to the QFI and QoS Profile (QoS configuration information), it carries the QoS information in the TLV field of the SRH, sets the Flag value to 1, and uses Map (PDU Session ID, UE ID) to determine the user and PDU Session, and uses QFI to determine the QoS information. After that, the UPF performs the corresponding QoS features based on the QoS information in the TLV in the SRH.

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

[0205] 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.

[0206] In an embodiment of the present application, if the SID is a QoS granularity, the uplink user data packet can be encapsulated into an SRv6 data packet format based on method 1 or method 3; wherein, for the implementation of method 1, a flag bit Flag is set in the Tag field of the SRH, for example, when the flag bit Flag is a custom or specified arbitrary value, it indicates that the Tag field of the SRH carries QoS flow information, and the QoS flow information here may include QFI and RQI, and the corresponding QoS flow is determined by QFI, and whether reflective QoS is enabled is determined by RQI.

[0207] It should be noted that this is consistent with the implementation method of encapsulating the uplink user data packet into the SRv6 data packet format based on mode 1 if the SID is a single PDU Session granularity, and will not be repeated here.

[0208] Among them, for method 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 data packet, it performs corresponding operations based on the QFI carried by 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 an RQI; the RQI is used to indicate whether a QoS flow enables reflective QoS; and the encapsulating the QoS flow information into the Argument field of the SID in the SRH includes:

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

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

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

[0213] Specifically, for mode 3, the Argument field carries QFI and RQI information or mapping information of QFI and RQI with SID (here, the mapping relationship is used to determine QoS flow information), so that the user plane node (including RAN) can determine the user's QoS requirements according to 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 method 3, the following is a detailed description through embodiment 4.

[0215] Exemplary embodiment 4 (SID is QoS granularity)

[0216] Combination Figure 3 As shown, when SID is the QoS granularity, the Args.mob.QoS behavior of the SID is defined to identify the QoS flow information through the Argument field of the SID in the SRH; the service quality control method provided in this embodiment includes the following steps:

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

[0218] UL: After receiving the data packet from the UE (here refers to the uplink user data packet), the RAN node encapsulates the corresponding SID list for the uplink user data packet according to the QoS Profile (QoS configuration information) corresponding to the QFI. Then the UPF executes the corresponding QoS features according to the Behavior of the SID (for example, the QoS flow information carried by the Argument field of the SID in the SRH).

[0219] Therefore, by setting or extending a field in the SRv6 data packet header to identify the QoS Flow information, or defining a new SID Behavior, the SRv6 node executes the corresponding QoS characteristics according to the QoS Flow information or SID in the SRH, 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 is solved, 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 the PDU Session cannot be realized. At the same time, the problem that the number of SIDs on the UPF increases due to different SIDs of different QoS flows in the PDU session, which leads to excessive occupation and waste of storage resources and processing resources in the UPF node is solved. The QoS control of SID applied to different PDU Sessions or different QoS flows can be realized while saving resources; at the same time, the problem that the combination of QFI+PDU Session ID described in Args.Mob.Session cannot uniquely identify a QoS flow may cause the QoS characteristics applied to the user to be inconsistent with the user's request, thereby failing to meet the user's needs. Therefore, it is possible to implement QoS control by applying SID to different PDU Sessions or different QoS flows, thereby ensuring the QoS requirements of users.

[0220] Figure 5 A flow chart of a service quality control method provided by another embodiment of the present application is shown as follows: Figure 5 As shown, the execution subject of the service quality control method provided in this embodiment is UPF; the service quality control method provided in this embodiment of the application includes the following steps:

[0221] Step 201: encapsulate a downlink user data packet of the UE into an SRv6 data packet format, wherein the SRv6 data 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;

[0222] Step 202: Send the SRv6 data packet carrying the QFI to the intermediate UPF, where the intermediate UPF is used to send the SRv6 data packet carrying the QFI to the RAN; or,

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

[0224] In an embodiment of the present application, a downlink user data packet of the UE is encapsulated and 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 intermediate UPF, and then sent to the RAN by the intermediate UPF. Alternatively, 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, which can realize QoS control of SID applied to different PDU Sessions or different QoS flows, thereby ensuring the user's QoS requirements.

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

[0226] If the SID is a single PDU Session granularity, the downlink user data packet is encapsulated into an SRv6 data packet format by using the Tag field in the SRH to carry the QoS flow information, or by using the extended field in the SRH to carry the QoS flow information;

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

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

[0229] In the present application examples, see Figures 1 to 3 , the downlink user data packet is encapsulated into the SRv6 data packet format through the above-mentioned method 1, method 2 or method 3, and method 1, method 2 and method 3 are not repeated here.

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

[0231] Therefore, based on different SID granularities, different encapsulation strategies are supported, and QoS flow information encapsulation is implemented according to the corresponding strategies, so that 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, so as to achieve QoS control. The problem that one SID can only be bound to one QoS flow information in the prior art is solved, resulting in the SID being applied to only one QoS flow after applying the Args.Mob.Session behavior, and the identification and positioning of multiple QoS flows in the PDU Session cannot be achieved. At the same time, the problem that the number of SIDs on the UPF increases due to different SIDs for different QoS flows in the PDU session, which in turn leads to excessive occupation and waste of storage resources and processing resources in the UPF node is solved. The SID can be applied to different PDU Sessions or different QoS flows for QoS control while saving resources.

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

[0233] When encapsulating the SRH for the downlink user data packet, encapsulating the QoS flow information into the Tag field of the SRH; the QoS flow information also includes a reflective service quality 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, the QoS flow information is encapsulated into the extension field of the SRH; the QoS flow information also includes an RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS.

[0235] In an embodiment 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 method 1 or method 2: for method 1, when encapsulating the SRH for the downlink user data packet, the QoS flow information is encapsulated into the Tag field of the SRH; for method 2, when encapsulating the SRH for the downlink user data packet, the QoS flow information is encapsulated into the extended field of the SRH.

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

[0237] By setting a flag bit Flag in the Tag field of the SRH, determining to indicate that the Tag field of the SRH carries the QoS flow information;

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

[0239] In an embodiment of the present application, if the SID is a single PDU Session granularity, by setting a flag bit Flag in the Tag field of the SRH, for example, when the flag bit Flag is a custom or specified arbitrary value, it indicates that the Tag field of the SRH carries QoS flow information, where the QoS flow information may include QFI and RQI, and the corresponding QoS flow is determined by QFI, and whether reflective QoS is enabled is determined by RQI.

[0240] Specifically, for method 1, by setting the flag bit Flag in the Tag field, the flag bit Flag value can be custom or specified (not specifically limited here), which is used to indicate whether the Tag field of the SRH carries QoS flow information, for example: the flag bit Flag takes a value of 0 or 1. When the Flag value is 1, it indicates that the field carries QoS flow information.

[0241] Based on method 1, the following is a detailed description through embodiment 5.

[0242] Exemplary embodiment 5 (SID is PDU Session granularity)

[0243] Combination Figure 1 As shown, when the SID is a PDU Session granularity, the service quality control method provided by this embodiment includes the following steps:

[0244] DL: The protocol data unit session anchor (PDU Session Anchor, PSA) (here refers to a UPF) encapsulates the SRv6 header for the user data packet (here refers to the downlink user data packet) according to the packet detection rule PDR, forwarding operation rule FAR and QoS execution rule QER, and carries QoS information in the Tag field of SRH. After that, the UPF executes the corresponding QoS features based on the QoS information in the Tag field in SRH. RAN decapsulates the SRv6 data packet according to QFI and QoS profile (QoS configuration information), and sends it to the UE from the DRB mapped by QFI.

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

[0246] Encapsulating the QFI and RQI into the extension fields of the SRH respectively;

[0247] By setting a flag Flag in the SRH, it is determined that the Map field in the extended 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 extended field is used to determine the corresponding QoS flow.

[0248] In an embodiment of the present application, if the SID is a single PDU Session granularity, the QFI and RQI are first encapsulated into the extended fields of the SRH respectively, and the flag Flag is set in the SRH. For example, when the flag Flag is a custom or specified arbitrary value, it indicates that the Map field in the extended field of the SRH is invalid or ignored. Therefore, the corresponding QoS flow is determined by the QoS flow information carried in the extended field of the SRH.

[0249] For method 2, by setting the flag bit Flag in the extended field (for example, TLV field) in the SRH, the Flag value can be custom 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 extended field of the SRH is effective. 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, indicating that the subsequent fields of the flag bit Flag are no longer parsed, which can indicate that the QoS flow information indicated by the field is invalid or ignored. The unique QoS flow is determined by the QFI carried by the TLV field in the SRH, and whether to enable reflective QoS is determined by the RQI.

[0250] Based on method 2, the following is described in detail through embodiment 6.

[0251] Exemplary embodiment 6 (SID is PDU Session granularity)

[0252] Combination Figure 2 As shown, when the SID is a PDU Session granularity, the service quality control method provided by this embodiment includes the following steps:

[0253] DL: The protocol data unit session anchor (PDU Session Anchor, PSA) (here refers to a UPF) encapsulates the SRv6 header for the user data packet (here refers to the downlink user data packet) according to the data packet detection rule PDR, forwarding operation rule FAR and QoS execution rule QER, etc., and carries QoS information in the TLV field of SRH, and sets the value of Flag to 0, indicating that the subsequent fields are no longer parsed. After that, UPF executes the corresponding QoS features based on the QoS information carried in the TLV field of SRH. RAN decapsulates the SRv6 data packet according to QFI and QoS profile (QoS configuration information), and sends it to the UE from the DRB mapped by QFI.

[0254] Optionally, if the SID is a multi-PDU Session granularity, encapsulating the downlink user data packet into an SRv6 data 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 embodiment of the present application, if the SID is a single PDU Session granularity, the downlink user data packet can be encapsulated into the SRv6 data packet format based on method 2.

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

[0258] Encapsulating the QFI and RQI into the extension fields of the SRH respectively;

[0259] By setting a flag bit Flag in the SRH, it is determined that a Map field in an extended field indicating the SRH is effective, wherein the Map field is used to indicate a mapping relationship between a PDU Session ID and a UE ID;

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

[0261] In an embodiment of the present application, if the SID is a multi-PDU Session granularity, the QFI and RQI can be respectively encapsulated into the extension field of the SRH, and by setting the flag bit Flag in the SRH, for example, when the flag bit Flag is a custom or specified arbitrary value, it indicates that the Map field in the extension field of the SRH is valid. Therefore, the mapping relationship between the PDU SessionID and the UE ID carried in the extension field of the SRH is used to determine the specified QoS flow of the specified PDU Session of the corresponding user, and whether to enable reflective QoS is determined through the RQI.

[0262] Specifically, for method 2, by setting a flag Flag in an extended field (e.g., a TLV field) in the SRH, the Flag value can be custom 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 extended field of the SRH is effective. For example: the Flag value is 0 or 1. When the Flag value is 1, it indicates 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.

[0263] Based on method 2, the following is described in detail through embodiment 3.

[0264] Exemplary Embodiment 7 (SID is a multi-PDU Session granularity)

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

[0266] DL: When the protocol data unit session anchor (PDU Session Anchor, PSA) (here refers to a UPF) encapsulates the SRv6 header for the user data packet (here refers to the downlink user data packet) according to the data packet detection rule PDR, forwarding operation rule FAR and QoS execution rule QER, it carries QoS information in the TLV field of SRH, sets the value of Flag to 1, and uses Map (PDU Session ID, UE ID) to determine the user and PDU Session, and uses QFI to determine the QoS information. After that, UPF executes the corresponding QoS features based on the QoS information in the TLV in SRH.

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

[0268] 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.

[0269] In an embodiment of the present application, if the SID is a QoS granularity, the downlink user data packet can be encapsulated into an SRv6 data packet format based on method 1 or method 3; wherein, for the implementation of method 1, a flag is set in the Tag field of the SRH, for example, when the flag is a custom or specified arbitrary value, it indicates that the Tag field of the SRH carries QoS flow information, where the QoS flow information may include QFI and RQI, the corresponding QoS flow is determined by QFI, and whether reflective QoS is enabled is determined by RQI.

[0270] It should be noted that this is consistent with the implementation method of encapsulating the downlink user data packet into the SRv6 data packet format based on mode 1 if the SID is a single PDU Session granularity, and will not be repeated here.

[0271] Among them, for method 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 data packet, it performs corresponding operations based on the QFI carried by the Argument field of the SID in the SRH or the mapping relationship used to determine the QoS flow information.

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

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

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

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

[0276] Specifically, for mode 3, the Argument field carries QFI and RQI information or mapping information of QFI and RQI with SID (here, the mapping relationship is used to determine QoS flow information), so that the user plane node (including RAN) can determine the user's QoS requirements according to 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.

[0277] Based on method 3, the following is a detailed description through embodiment 8.

[0278] Exemplary Embodiment 8 (SID is QoS granularity)

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

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

[0281] DL: After receiving the data packet (here refers to the downlink user data packet), PSA encapsulates the SRv6 header of the corresponding QoS flow for the downlink user data packet according to the data packet detection rules, etc., which contains the corresponding SID list. After receiving the downlink user data packet, RAN determines the QFI according to the Args.mob.QoS behavior of the SID.

[0282] Therefore, by setting or extending a field in the SRv6 data packet header to identify the QoS Flow information, or defining a new SID Behavior, the SRv6 node executes the corresponding QoS characteristics according to the QoS Flow information or SID in the SRH, 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 is solved, 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 the PDU Session cannot be realized. At the same time, the problem that the number of SIDs on the UPF increases due to different SIDs of different QoS flows in the PDU session, which leads to excessive occupation and waste of storage resources and processing resources in the UPF node is solved. The QoS control of SID applied to different PDU Sessions or different QoS flows can be realized while saving resources; at the same time, the problem that the combination of QFI+PDU Session ID described in Args.Mob.Session cannot uniquely identify a QoS flow may cause the QoS characteristics applied to the user to be inconsistent with the user's request, thereby failing to meet the user's needs. Therefore, it is possible to implement QoS control by applying SID to different PDU Sessions or different QoS flows, thereby ensuring the QoS requirements of users.

[0283] It should be noted here that the service quality control method with UPF as the execution subject can be referred to in its specific implementation process. Figure 1-Figure 3 The embodiments shown here will not be described in detail in detail.

[0284] Figure 6 A schematic diagram of the structure of the service quality control device provided in the embodiment of the present application is shown in FIG. Figure 6 As shown, the service quality control device provided by this embodiment is applied to a radio access network RAN. Then the service quality control device provided by this embodiment includes: a transceiver 600, which is used to receive and send data under the control of a processor 610.

[0285] Among them, Figure 6In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 610 and memory represented by memory 620. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 600 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium may include a wireless channel, a wired channel, an optical cable, and the like. The processor 610 is responsible for managing the bus architecture and general processing, and the memory 620 may store data used by the processor 610 when performing operations.

[0286] The processor 610 may 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 may also adopt a multi-core architecture.

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

[0288] receiving uplink user data packets from a terminal;

[0289] Encapsulating the uplink user data packet into an SRv6 data packet format, wherein the SRv6 data packet header SRH contains quality of service QoS flow information, the QoS flow information includes QFI, and the QFI is used to indicate the QoS flow;

[0290] 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.

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

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

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

[0294] If the SID is a QoS granularity, the uplink user data packet is encapsulated into an SRv6 data packet format by using the Tag field in the SRH to carry the QoS flow information, or by defining the SID behavior to carry the QoS flow information through the 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 data packet format, specifically including:

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

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

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

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

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

[0301] Optionally, the extension field is used to indicate the type, length and value of the information element; the processor is used to encapsulate the QoS flow information into the extension field of the SRH, specifically including:

[0302] Encapsulating the QFI and RQI into the extension fields of the SRH respectively;

[0303] By setting a flag Flag in the SRH, it is determined that the Map field in the extended 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 extended field is used to determine the corresponding QoS flow.

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

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

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

[0307] Encapsulating the QFI and RQI into the extension fields of the SRH respectively;

[0308] By setting a flag bit Flag in the SRH, it is determined that a Map field in an extended field indicating the SRH is effective, wherein 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 the designated QoS flow of the designated PDU session of the corresponding user.

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

[0311] 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.

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

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

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

[0315] It should be noted that the service quality control device provided in this application can achieve Figure 1-Figure 4 All the method steps implemented in the method embodiment shown can achieve the same technical effect, and the parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0316] Figure 7 A structural diagram of a service quality control device provided in another embodiment of the present application is shown in FIG. Figure 7 As shown, the service quality control device provided in this embodiment is applied to a radio access network RAN, and the service quality control device 700 provided in this embodiment includes:

[0317] The receiving unit 701 is used to receive an uplink user data packet from a terminal;

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

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

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

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

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

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

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

[0325] When the SID is a single PDU Session granularity, when encapsulating the SRH for the uplink user data packet, the QoS flow information is encapsulated into the Tag field of the SRH; the QoS flow information also includes an RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS; or,

[0326] When the SID is a single PDU Session granularity, when the SRH is encapsulated for the uplink user data packet, the QoS flow information is encapsulated into an extended field of the SRH; the QoS flow information also includes an RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS.

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

[0328] By setting a flag bit Flag in the Tag field of the SRH, determining to indicate that the Tag field of the SRH carries the QoS flow information;

[0329] The QFI and 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 the information element; the processing unit 702 is specifically used to:

[0331] Encapsulating the QFI and RQI into the extension fields of the SRH respectively;

[0332] By setting a flag Flag in the SRH, it is determined that the Map field in the extended 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 extended field is used to determine the corresponding QoS flow.

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

[0334] When the SID is a multi-PDU Session granularity, when encapsulating the SRH 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 the information element, and the QoS flow information further includes a mapping relationship between the PDU Session ID and the UE ID, and an RQI; the RQI is used to indicate whether a QoS flow enables reflective QoS; the processing unit 702 is specifically used to:

[0336] Encapsulating the QFI and RQI into the extension fields of the SRH respectively;

[0337] By setting a flag bit Flag in the SRH, it is determined that a Map field in an extended field indicating the SRH is effective, wherein the Map field is used to indicate a mapping relationship between a PDU Session ID and a UE ID;

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

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

[0340] When the SID is a 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.

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

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

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

[0344] It should be noted that the service quality control device provided in this application can achieve Figure 1-Figure 4 All the method steps implemented in the method embodiment can achieve the same technical effect, and the parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0345] Figure 8 A structural diagram of a service quality control device provided in yet another embodiment of the present application is shown in FIG. Figure 8 As shown, the service quality control device provided in this embodiment is applied to the user plane function UPF, and the service quality control device provided in this embodiment includes: a transceiver 800, which is used to receive and send data under the control of a processor 810.

[0346] Among them, Figure 8In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 810 and memory represented by memory 820. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 800 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium may include a wireless channel, a wired channel, an optical cable, and the like. The processor 810 is responsible for managing the bus architecture and general processing, and the memory 820 may store data used by the processor 810 when performing operations.

[0347] The processor 810 may 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 may also adopt a multi-core architecture.

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

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

[0350] Sending the SRv6 data packet carrying the QFI to the intermediate UPF, where the intermediate UPF is used to send the SRv6 data packet carrying the QFI to the RAN; or,

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

[0352] Optionally, the processor 810 is configured to, when encapsulating a downlink user data packet of the UE into an SRv6 data packet format, specifically include:

[0353] If the SID is a single PDU Session granularity, the downlink user data packet is encapsulated into an SRv6 data packet format by using the Tag field in the SRH to carry the QoS flow information, or by using the extended field in the SRH to carry the QoS flow information;

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

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

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

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

[0358] 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 also includes that the RQI is used to indicate whether a QoS flow enables reflective QoS.

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

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

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

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

[0363] Encapsulating the QFI and RQI into the extension fields of the SRH respectively;

[0364] By setting a flag Flag in the SRH, it is determined that the Map field in the extended 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 extended field is used to determine the corresponding QoS flow.

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

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

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

[0368] Encapsulating the QFI and RQI into the extension fields of the SRH respectively;

[0369] By setting a flag bit Flag in the SRH, it is determined that a Map field in an extended field indicating the SRH is effective, wherein 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 the designated QoS flow of the designated PDU session of the corresponding user.

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

[0372] 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.

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

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

[0375] The mapping relationship among QFI, RQI and SID is encapsulated into the Argument field of SID in the SRH, and the mapping relationship among 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 can achieve Figure 1-Figure 3 as well as Figure 5 All the method steps implemented in the method embodiment shown can achieve the same technical effect, and the parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0377] Fig. 9 A structural diagram of a service quality control device provided in another embodiment of the present application is shown in FIG. Fig. 9 As shown, the service quality control device provided in the embodiment of the present application is applied to the user plane function UPF, and the service quality control device 900 provided in this embodiment includes:

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

[0379] The sending unit 902 is configured to send the SRv6 data packet carrying the QFI to the intermediate UPF, and the intermediate UPF is configured to send the SRv6 data packet carrying the QFI to the RAN; or,

[0380] The SRv6 data packet carrying the QFI is sent to the RAN, and the RAN 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 configured to:

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

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

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

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

[0386] When the SID is at the PDU Session granularity, 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,

[0387] When the SID is at the PDU Session granularity, when the SRH is encapsulated for the downlink user data packet, the QoS flow information is encapsulated into an extended field of the SRH; the QoS flow information also includes an RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS.

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

[0389] By setting a flag bit Flag in the Tag field of the SRH, determining to indicate that the Tag field of the SRH carries the QoS flow information;

[0390] The 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 the information element; the processing unit 901 is specifically used to:

[0392] Encapsulating the QFI and RQI into the extension fields of the SRH respectively;

[0393] By setting a flag Flag in the SRH, it is determined that the Map field in the extended 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 extended field is used to determine the corresponding QoS flow.

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

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

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

[0397] Encapsulating the QFI and RQI into the extension fields of the SRH respectively;

[0398] By setting a flag bit Flag in the SRH, it is determined that a Map field in an extended field indicating the SRH is effective, wherein the Map field is used to indicate a mapping relationship between a PDU Session ID and a UE ID;

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

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

[0401] When the SID is a 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 an RQI; the RQI is used to indicate whether a QoS flow enables reflective QoS; the processing unit 901 is specifically configured to:

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

[0404] The mapping relationship among QFI, RQI and SID is encapsulated into the Argument field of SID in the SRH, and the mapping relationship among 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 can achieve Figure 1-Figure 3 as well as Figure 5 All the method steps implemented in the method embodiment can achieve the same technical effect, and the parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0406] It should be noted that the division of units in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional unit in each embodiment of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0407] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of each embodiment method of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program code.

[0408] The embodiment of the present application further provides a non-transitory readable storage medium. The non-transitory readable storage medium stores a computer program, and the computer program is used to enable a processor to execute any of the above method embodiments.

[0409] Among them, 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 magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NANDFLASH), solid-state drive (SSD)), etc.

[0410] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) that contain computer-usable program code.

[0411] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer executable instructions. These computer executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0412] These processor executable instructions may also be stored in a processor readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0413] These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0414] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A method for controlling quality of service, characterized in that: Applied to a radio access network RAN, the method comprises: receiving uplink user data packets from a terminal; Encapsulating the uplink user data packet 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, and the QoS flow information includes a 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 a user plane function UPF, and the UPF is used to perform corresponding operations according to the QFI.

2. The method according to claim 1, characterized in that The encapsulating the uplink user data packet into a new generation IP bearer protocol SRv6 data packet format based on IPv6 and source routing includes: If the SRv6 segment identifier SID is a single protocol data unit session PDU Session granularity, the uplink user data packet is encapsulated into an SRv6 data packet format by using the Tag field in the SRH to carry the QoS flow information, or by using the extended field in the SRH to carry the QoS flow information; If the SID is a multi-PDU Session granularity, the uplink user data packet is encapsulated into an SRv6 data packet format by using an extension field in the SRH to carry QoS flow information; If the SID is a QoS granularity, the uplink user data packet is encapsulated into an SRv6 data packet format by using the Tag field in the SRH to carry the QoS flow information, or by defining the SID behavior to carry the QoS flow information through the Argument field of the SID in the SRH.

3. The method according to claim 2, characterized in that If the SID is a single PDU Session granularity, encapsulating the uplink user data packet into an SRv6 data packet format includes: When encapsulating the SRH for the uplink user data packet, encapsulating the QoS flow information into the Tag field of the SRH; the QoS flow information also includes a reflective service quality identifier RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS; or, When encapsulating the SRH for the uplink user data packet, the QoS flow information is encapsulated into the extension field of the SRH; the QoS flow information also includes an RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS.

4. The method according to claim 3, characterized in that The encapsulating the QoS flow information into the Tag field of the SRH includes: By setting a flag bit Flag in the Tag field of the SRH, determining to indicate that the Tag field of the SRH carries the QoS flow information; The QFI and RQI in the QoS flow information are respectively encapsulated into the Tag field of the SRH.

5. The method according to claim 3, characterized in that: The extended field is used to indicate the type, length and value of the information element; and the encapsulating the QoS flow information into the extended field of the SRH includes: Encapsulating the QFI and RQI into the extension fields of the SRH respectively; By setting a flag Flag in the SRH, it is determined that the Map field in the extended 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 extended field is used to determine the corresponding QoS flow.

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

7. The method according to claim 6, characterized in that The extended field is used to indicate the type, length and value of the information element, and the QoS flow information also includes a mapping relationship between the PDU Session ID and the UE ID, and an RQI; The RQI is used to indicate whether reflective QoS is enabled for a QoS flow; The encapsulating the QoS flow information into the extension field of the SRH includes: Encapsulating the QFI and RQI into the extension fields of the SRH respectively; By setting a flag bit Flag in the SRH, it is determined that a Map field in an extended field indicating the SRH is effective, wherein 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 the designated QoS flow of the designated PDU session of the corresponding user.

8. The method according to any one of claims 2 to 7, characterized in that: If the SID is a QoS granularity, encapsulating the uplink user data packet into an SRv6 data packet format includes: 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.

9. The method according to claim 8, characterized in that The QoS flow information further includes an RQI; the RQI is used to indicate whether a QoS flow enables reflective QoS; and the encapsulating the QoS flow information into the Argument field of the SID in the SRH includes: Encapsulate the QFI and RQI into the Argument field of the SID in the SRH respectively; or, The mapping relationship among QFI, RQI and SID is encapsulated into the Argument field of SID in the SRH, and the mapping relationship among QFI, RQI and SID is used to determine QoS flow information.

10. A method for controlling quality of service, characterized in that: The method is applied to a user plane function UPF, and the method comprises: Encapsulate the downlink user data packet of the UE into the SRv6 data packet format, wherein the SRv6 message header SRH contains QoS flow information; wherein the QoS flow information includes QFI, and the QFI is used to indicate the QoS flow; Sending the SRv6 data packet carrying the QFI to the intermediate UPF, where the intermediate UPF is used to send the SRv6 data packet carrying the QFI to the RAN; or, The SRv6 data packet carrying the QFI is sent to the RAN, and the RAN is used to map the QoS flow to the corresponding data radio bearer DRB according to the QFI and the corresponding QoS configuration information.

11. The method according to claim 10, characterized in that The step of encapsulating the downlink user data packet of the UE into the SRv6 data packet format includes: If the SID is a single PDU Session granularity, the downlink user data packet is encapsulated into an SRv6 data packet format by using the Tag field in the SRH to carry the QoS flow information, or by using the extended field in the SRH to carry the QoS flow information; If the SID is a multi-PDU Session granularity, the downlink user data packet is encapsulated into an SRv6 data 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 data packet format by using the Tag field in the SRH to carry the QoS flow information, or by defining the SID behavior to carry the QoS flow information through the Argument field of the SID in the SRH.

12. The method according to claim 11, characterized in that If the SID is a single PDU Session granularity, encapsulating the downlink user data packet into an SRv6 data packet format includes: When encapsulating the SRH for the downlink user data packet, encapsulating the QoS flow information into the Tag field of the SRH; the QoS flow information also includes a reflective service quality identifier 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, the QoS flow information is encapsulated into the extension field of the SRH; the QoS flow information also includes an RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS.

13. The method according to claim 12, characterized in that The encapsulating the QoS flow information into the Tag field of the SRH includes: By setting a flag bit Flag in the Tag field of the SRH, determining to indicate that the Tag field of the SRH carries the QoS flow information; The QFI and RQI in the QoS flow information are respectively encapsulated into the Tag field of the SRH.

14. The method according to claim 12, characterized in that The extended field is used to indicate the type, length and value of the information element; and the encapsulating the QoS flow information into the extended field of the SRH includes: Encapsulating the QFI and RQI into the extension fields of the SRH respectively; By setting a flag Flag in the SRH, it is determined that the Map field in the extended 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 extended field is used to determine the corresponding QoS flow.

15. The method according to claim 11, characterized in that If the SID is a multi-PDU Session granularity, encapsulating the downlink user data packet into an SRv6 data packet format includes: When encapsulating the SRH for the downlink user data packet, the QoS flow information is encapsulated into an extension field of the SRH.

16. The method according to claim 15, characterized in that The extended field is used to indicate the type, length and value of the information element, and the QoS flow information also includes a mapping relationship between the PDU SessionID and the UE ID, and an RQI; The RQI is used to indicate whether reflective QoS is enabled for a QoS flow; The encapsulating the QoS flow information into the extension field of the SRH includes: Encapsulating the QFI and RQI into the extension fields of the SRH respectively; By setting a flag bit Flag in the SRH, it is determined that a Map field in an extended field indicating the SRH is effective, wherein 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 the designated QoS flow of the designated PDU session of the corresponding user.

17. The method according to any one of claims 11 to 16, characterized in that: If the SID is a QoS granularity, encapsulating the downlink user data packet into an SRv6 data packet format includes: 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.

18. The method according to claim 17, characterized in that The QoS flow information further includes an RQI; the RQI is used to indicate whether a QoS flow enables reflective QoS; and the encapsulating the QoS flow information into the Argument field of the SID in the SRH includes: Encapsulate the QFI and RQI into the Argument field of the SID in the SRH respectively; or, The mapping relationship among QFI, RQI and SID is encapsulated into the Argument field of SID in the SRH, and the mapping relationship among QFI, RQI and SID is used to determine QoS flow information.

19. A service quality control device, characterized in that: The device is applied to a radio access network RAN, and the device includes: A receiving unit, used for receiving an uplink user data packet from a terminal; A processing unit, configured to encapsulate the uplink user data packet into an SRv6 data packet format, wherein the SRv6 data packet header SRH includes QoS flow information; wherein the QoS flow information includes a QFI, and the QFI is used to indicate a QoS flow; A sending unit is used to send 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.

20. A service quality control device, characterized in that: 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 the UE into an SRv6 data packet format, wherein the SRv6 data packet header SRH includes QoS flow information; wherein 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, wherein the intermediate UPF is configured to send the SRv6 data packet carrying the QFI to the RAN; or The SRv6 data packet carrying the QFI is sent to the RAN, and the RAN is used to map the QoS flow to the corresponding data radio bearer DRB according to the QFI and the corresponding QoS configuration information.

21. A service quality control device, characterized in that: The device is applied to a radio access network RAN, and includes a memory, a transceiver, and a processor: a memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; A processor is configured to read the computer program in the memory and perform the following operations: receiving uplink user data packets from a terminal; Encapsulating the uplink user data packet into an SRv6 data packet format, wherein the SRv6 data packet header SRH contains quality of service QoS flow information, the QoS flow information includes QFI, and the QFI is used to indicate the 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.

22. The device according to claim 21, characterized in that The processor is used to encapsulate the uplink user data packet into the SRv6 data packet format, specifically including: If the SRv6 segment identifier SID is a single PDU Session granularity, the uplink user data packet is encapsulated into an SRv6 data packet format by using the Tag field in the SRH to carry the QoS flow information, or by using the extended field in the SRH to carry the QoS flow information; If the SID is a multi-PDU Session granularity, the uplink user data packet is encapsulated into an SRv6 data packet format by using an extension field in the SRH to carry QoS flow information; If the SID is a QoS granularity, the uplink user data packet is encapsulated into an SRv6 data packet format by using the Tag field in the SRH to carry the QoS flow information, or by defining the SID behavior to carry the QoS flow information through the Argument field of the SID in the SRH.

23. The device according to claim 22, characterized in that The processor is configured to encapsulate the uplink user data packet into an SRv6 data packet format when the SID is a single PDUSession granularity, specifically comprising: When encapsulating the SRH for the uplink user data packet, encapsulating the QoS flow information into the Tag field of the SRH; the QoS flow information also includes an RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS; or, When encapsulating the SRH for the uplink user data packet, the QoS flow information is encapsulated into the extension field of the SRH; the QoS flow information also includes an RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS.

24. The device according to claim 22, characterized in that The processor is configured to encapsulate the uplink user data packet into an SRv6 data packet format when the SID is a multi-PDUSession granularity, specifically comprising: When encapsulating the SRH for the uplink user data packet, the QoS flow information is encapsulated into an extension field of the SRH.

25. The device according to any one of claims 22 to 24, characterized in that The processor is configured to encapsulate the uplink user data packet into an SRv6 data packet format when the SID is a QoS granularity, specifically comprising: 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.

26. A service quality control device, characterized in that: The device is applied to a user plane function UPF, and includes: a memory, a transceiver, and a processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Encapsulating a downlink user data packet for the UE into an SRv6 data packet format, wherein the SRv6 data packet header SRH includes QoS flow information; wherein the QoS flow information includes a QFI, and the QFI is used to indicate the QoS flow; Sending the SRv6 data packet carrying the QFI to the intermediate UPF, where the intermediate UPF is used to send the SRv6 data packet carrying the QFI to the RAN; or, The SRv6 data packet carrying the QFI is sent to the RAN, and the RAN is used to map the QoS flow to the corresponding data radio bearer DRB according to the QFI and the corresponding QoS configuration information.

27. The device according to claim 26, characterized in that The processor is used to encapsulate the downlink user data packet of the UE into the SRv6 data packet format, specifically including: If the SID is a single PDU Session granularity, the downlink user data packet is encapsulated into an SRv6 data packet format by using the Tag field in the SRH to carry the QoS flow information, or by using the extended field in the SRH to carry the QoS flow information; If the SID is a multi-PDU Session granularity, the downlink user data packet is encapsulated into an SRv6 data 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 data packet format by using the Tag field in the SRH to carry the QoS flow information, or by defining the SID behavior to carry the QoS flow information through the Argument field of the SID in the SRH.

28. The device according to claim 27, characterized in that The processor is configured to encapsulate the downlink user data packet into an SRv6 data packet format when the SID is a single PDUSession granularity, specifically comprising: When encapsulating the SRH for the downlink user data packet, encapsulating the QoS flow information into the Tag field of the SRH; the QoS flow information also includes an 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, the QoS flow information is encapsulated into the extension field of the SRH; the QoS flow information also includes an RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS.

29. The device according to claim 27, characterized in that The processor is configured to encapsulate the downlink user data packet into an SRv6 data packet format when the SID is a multi-PDUSession granularity, specifically comprising: When encapsulating the SRH for the downlink user data packet, the QoS flow information is encapsulated into an extension field of the SRH.

30. The device according to any one of claims 27 to 29, characterized in that The processor is configured to encapsulate the downlink user data packet into an SRv6 data packet format when the SID is a QoS granularity, specifically comprising: 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.

31. A processor-readable storage medium, characterized in that: The processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the method according to any one of claims 1 to 18.

Images