Service quality control method and device, and readable storage medium

Abstract

The present disclosure provides a service quality control method and device, and a readable storage medium. The method comprises: receiving an uplink user data packet of a terminal; and encapsulating the uplink user data packet in SRv6 data packet format, wherein the SRv6 data packet header (SRH) comprises quality of service (QoS) flow information, the QoS flow information comprising a QFI used for indicating a QoS flow; and sending to a user plane function (UPF) the SRv6 data packet carrying the QFI, wherein the UPF is used for executing, on the basis of the QFI, a corresponding operation. The method ensures user QoS requirements are met.

Description

Service quality control method, device and readable storage medium

[0001] This disclosure claims priority to the Chinese patent application filed with the China Patent Office on September 25, 2023, with application number 202311250618.9 and application name “Service Quality Control Method, Device and Readable Storage Medium”, the entire contents of which are incorporated by reference into this disclosure. Technical Field

[0002] The present disclosure relates to the field of communication technologies, and in particular to a method, device, and readable storage medium for controlling quality of service. Background Art

[0003] SRv6 is a next-generation IP bearer protocol based on IPv6 and source routing. It simplifies network protocols and ensures application-level service level agreements (SLAs). It will be the foundation for building intelligent IP networks in the 5G and cloud eras. In SRv6, an SRv6 segment identifier (SID) defines a network function and represents network instructions. This SID, called an SRv6 SID (here, SRv6 Segment Identifier SID), uses an IPv6 address but does not correspond to the IPv6 address of any interface included in an SR node.

[0004] IETF RFC 9433 defines a new SRv6 Behavior, Args.Mob.Session. This SRv6 Behavior extends the Quality of Service (QoS) and QoS Flow ID (QFI) fields to meet QoS requirements.

[0005] However, Args.Mob.Session is SID-granular. In mobile networks based on the SRv6 user plane, the allocation of SIDs is not necessarily QoS flow-granular. 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 extended 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.

[0006] Summary of the Invention

[0007] The present disclosure 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.

[0008] In a first aspect, the present disclosure provides a method for controlling quality of service (QoS), applied to a radio access network (RAN). The method includes:

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

[0010] 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;

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

[0012] In the embodiment of the present disclosure, 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. The UPF performs corresponding operations based on the indicated QoS flow, which can realize QoS control of SID applied to different PDU Sessions or different QoS flows, thereby ensuring the user's QoS requirements.

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

[0014] If the SRv6 segment identifier SID is a single protocol data unit session (PDU) 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 using the extension field in the SRH to carry QoS flow information;

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

[0016] 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 QoS flow information, or by defining the SID behavior to carry QoS flow information through the Argument field of the SID in the SRH.

[0017] In the embodiment of the present disclosure, 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 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. This solves the problem that in the prior art, one SID can only be bound to one QoS flow information, resulting in the SID being applied to only one QoS flow after the Args.Mob.Session behavior is applied, and the identification and positioning of multiple QoS flows in the PDU Session cannot be realized. At the same time, it also solves the problem that the number of SIDs on the UPF increases due to different SIDs for different QoS flows in the PDU session, thereby causing excessive occupation and waste of storage resources and processing resources in the UPF node. It can realize QoS control of SIDs applied to different PDU Sessions or different QoS flows while saving resources.

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

[0019] 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,

[0020] 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 reflective QoS is enabled for a QoS flow.

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

[0022] Setting a flag in the Tag field of the SRH to indicate that the Tag field of the SRH carries QoS flow information;

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

[0024] In the embodiment of the present disclosure, if the SID is a single PDU Session granularity, by setting the 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. The QoS flow information here may include QFI and RQI. The corresponding QoS flow is determined by QFI, and whether reflective QoS is enabled is determined by RQI.

[0025] 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:

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

[0027] By setting a 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.

[0028] In the embodiment of the present disclosure, if the SID is a single PDU Session granularity, the QFI and RQI are first encapsulated into the extension field 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 extension field of the SRH is invalid or ignored. Therefore, the corresponding QoS flow is determined by the QoS flow information carried in the extension field of the SRH.

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

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

[0031] Optionally, the extension field is used to indicate the type, length, and value of the information element; 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 reflective QoS is enabled for a QoS flow; and encapsulating the QoS flow information into the extension field of the SRH includes:

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

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

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

[0035] In an embodiment of the present disclosure, if the SID is a multi-PDU Session granularity, the QFI and RQI can be encapsulated into the extension field of the SRH respectively. 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 Session ID 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.

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

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

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

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

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

[0041] In an embodiment of the present disclosure, if the SID is the QoS granularity, the QFI and RQI are respectively encapsulated into the Argument field of the SID in the SRH, or the mapping relationship between the 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.

[0042] In a second aspect, the present disclosure provides a method for controlling quality of service, which is applied to a user plane function (UPF), the method comprising:

[0043] Encapsulating the UE's downlink 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 the QoS flow;

[0044] 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,

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

[0046] In the embodiment of the present disclosure, a downlink user data packet of the 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 then sends the data packet to the RAN. Alternatively, 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. This enables QoS control of SIDs applied to different PDU Sessions or different QoS flows, thereby ensuring the user's QoS requirements.

[0047] Optionally, encapsulating the UE's downlink user data packet into an SRv6 data packet format includes:

[0048] 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 QoS flow information, or by using the extension field in the SRH to carry QoS flow information;

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

[0050] 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 QoS flow information, or by defining the SID behavior to carry QoS flow information through the Argument field of the SID in the SRH.

[0051] In the disclosed embodiment, 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 implementing QoS control. This solves the problem in the prior art that one SID can only be bound to one QoS flow information, resulting in the SID being applied to only one QoS flow after the Args.Mob.Session behavior is applied, and the identification and positioning of multiple QoS flows in the PDU Session cannot be implemented. At the same time, it also solves 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. This can implement QoS control of SIDs applied to different PDU Sessions or different QoS flows while saving resources.

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

[0053] 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,

[0054] 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 reflective QoS is enabled for a QoS flow.

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

[0056] Setting a flag in the Tag field of the SRH to indicate that the Tag field of the SRH carries QoS flow information;

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

[0058] In the embodiment of the present disclosure, if the SID is a single PDU Session granularity, by setting the 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. The QoS flow information here may include QFI and RQI. The corresponding QoS flow is determined by QFI, and whether reflective QoS is enabled is determined by RQI.

[0059] 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:

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

[0061] By setting a 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.

[0062] In the embodiment of the present disclosure, if the SID is a single PDU Session granularity, the QFI and RQI are first encapsulated into the extension field 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 extension field of the SRH is invalid or ignored. Therefore, the corresponding QoS flow is determined by the QoS flow information carried in the extension field of the SRH.

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

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

[0065] Optionally, the extension field is used to indicate the type, length, and value of the information element; 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 reflective QoS is enabled for a QoS flow; and encapsulating the QoS flow information into the extension field of the SRH includes:

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

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

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

[0069] In an embodiment of the present disclosure, if the SID is a multi-PDU Session granularity, the QFI and RQI can be encapsulated into the extension field of the SRH respectively. 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 Session ID 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.

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

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

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

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

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

[0075] In an embodiment of the present disclosure, if the SID is the QoS granularity, the QFI and RQI are respectively encapsulated into the Argument field of the SID in the SRH, or the mapping relationship between the 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.

[0076] In a third aspect, the present disclosure provides a service quality control device, which is applied to a radio access network (RAN). The device includes:

[0077] A receiving unit, configured to receive uplink user data packets from a terminal;

[0078] 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;

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

[0080] In a fourth aspect, the present disclosure provides a service quality control device, which is applied to a user plane function (UPF), and includes:

[0081] 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 the QoS flow;

[0082] 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

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

[0084] In a fifth aspect, the present disclosure provides a service quality control device, which is applied to a radio access network (RAN). The device includes a memory, a transceiver, and a processor.

[0085] 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:

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

[0087] Encapsulating 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, the QoS flow information includes a QFI, and the QFI is used to indicate the QoS flow;

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

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

[0090] 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 QoS flow information, or by using the extension field in the SRH to carry QoS flow information;

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

[0092] 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 QoS flow information, or by defining the SID behavior to carry QoS flow information through the Argument field of the SID in the SRH.

[0093] 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 including:

[0094] 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 reflective QoS is enabled for a QoS flow; or,

[0095] 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 reflective QoS is enabled for a QoS flow.

[0096] 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:

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

[0098] 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 including:

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

[0100] In a sixth aspect, the present disclosure provides a service quality control device, which is applied to a user plane function (UPF). The device includes: a memory, a transceiver, and a processor.

[0101] 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:

[0102] 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;

[0103] 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,

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

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

[0106] 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 QoS flow information, or by using the extension field in the SRH to carry QoS flow information;

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

[0108] 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 QoS flow information, or by defining the SID behavior to carry QoS flow information through the Argument field of the SID in the SRH.

[0109] 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 including:

[0110] 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 reflective QoS is enabled for a QoS flow; or,

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

[0112] 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 including:

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

[0114] 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 including:

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

[0116] In a seventh aspect, the present disclosure 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.

[0117] The present disclosure provides a method, apparatus, and readable storage medium for controlling quality of service. First, an uplink user data packet from a terminal is received, and then the uplink user data packet is encapsulated into an SRv6 data packet format, a new generation IP bearer protocol based on IPv6 and source routing. The SRv6 data packet header (SRH) contains quality of service (QoS) flow information, and the QoS flow information includes a quality of service (QFI) flow identifier (QFI) for indicating a QoS flow. The SRv6 data packet carrying the QFI is sent to a user plane function (UPF), and the UPF is configured to perform corresponding operations based on the QFI. Specifically, based on the received uplink user data packet, the uplink user data packet is encapsulated into an SRv6 data packet format, including at least QoS flow information including the QFI, for indicating a corresponding QoS flow. The SRv6 data packet carrying the QFI is sent to the UPF, and the UPF performs corresponding operations based on the indicated QoS flow. This enables QoS control where the SID is applied to different PDU sessions or different QoS flows, thereby ensuring the user's QoS requirements.

[0118] 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 readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0119] In order to more clearly illustrate the technical solutions in the present disclosure or the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. 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 any creative labor.

[0120] FIG1 is a schematic diagram of using the Tag field in the SRH to carry QoS flow information according to an embodiment of the present disclosure;

[0121] FIG2 is a schematic diagram of using the TLV field in the SRH to carry QoS flow information according to an embodiment of the present disclosure;

[0122] FIG3 is a schematic diagram of identifying QoS flow information through the Argument field of the SID in the SRH according to an embodiment of the present disclosure;

[0123] FIG4 is a flow chart of a method for controlling quality of service according to an embodiment of the present disclosure;

[0124] FIG5 is a flow chart of a method for controlling quality of service according to another embodiment of the present disclosure;

[0125] FIG6 is a schematic structural diagram of a service quality control device provided by an embodiment of the present disclosure;

[0126] FIG7 is a schematic structural diagram of a service quality control device provided by another embodiment of the present disclosure;

[0127] FIG8 is a schematic structural diagram of a service quality control device provided by yet another embodiment of the present disclosure;

[0128] FIG9 is a schematic structural diagram of a service quality control device provided by yet another embodiment of the present disclosure. DETAILED DESCRIPTION

[0129] In this disclosure, the term "and / or" describes the relationship between associated objects, indicating that three possible relationships exist. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.

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

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

[0132] In order to clearly understand the technical solutions of the present disclosure, the solutions of the prior art are 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 require guaranteed flow bit rates (GBR QoS flows) and QoS flows that do not require guaranteed flow bit rates (non-GBR QoS flows).

[0133] For the downlink (DL), the user plane function (UPF) compares packets with the packet detection rules (PDRs) established by the session management function (SMF) to classify them. Each PDR is then associated with one or more QoS enforcement rules (QERs), which contain enforcement information such as the specific rate. The QER also includes the QFI value to be added to the GTP-U header (N3 encapsulation header).

[0134] For the uplink (UL), packets generated by the UE application layer are first compared against packet filters selected from a set of packet filters in the UE. These filters are checked in order of priority, and if a match is found, a QFI is assigned to the packet. The assigned QFI and the packet are sent to the SDAP layer (a new protocol layer in NR) in the UE's access stratum (AS). The SDAP layer maps the QFI to a data radio bearer (DRB) based on available mapping rules. If a match is found, the packet is sent on the corresponding DRB. If no match is found, the packet is sent on a default DRB, and the SDAP header contains the QFI so that the NG-RAN can decide whether to move the QFI to another DRB.

[0135] SRv6 is a next-generation IP bearer protocol based on IPv6 and source routing. It unifies traditional, complex network protocols, simplifies them, and ensures application-level service level agreements (SLAs). It will be the foundation for building intelligent IP networks in the 5G and cloud eras. In SRv6, an SRv6 segment identifier (SID) defines a network function and represents network instructions. This SID, called an SRv6 SID (here, an SRv6 segment identifier SID), uses an IPv6 address but does not correspond to the IPv6 address of any interface included in an SR node.

[0136] IETF RFC 9433 defines a new SRv6 Behavior, Args.Mob.Session. This SRv6 Behavior extends the Quality of Service (QoS) and QoS Flow ID (QFI) fields to meet QoS requirements.

[0137] 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 a scenario where multiple PDU Sessions are aggregated in a SID. Because SRv6 SID is not necessarily instantiated as per PDU Session (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 SID is allocated at the PDU Session granularity, then after the SID applies Args.Mob.Session, the extended field can only be applied to one QoS flow, and cannot be implemented for one PDU In addition, the combination of QFI+PDU Session ID described in Args.Mob.Session cannot uniquely identify a QoS flow, which may cause the QoS characteristics applied to the user to be inconsistent with the user's request, thus failing to meet the user's needs.

[0138] Therefore, the existing technology cannot implement QoS control by applying SIDs to different PDU Sessions or different QoS flows, and thus cannot guarantee the QoS requirements of users.

[0139] The inventors further discovered that in order to solve the problem in the prior art that SID cannot be applied to QoS control of different PDU Sessions or different QoS flows, and thus cannot 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 can be encapsulated based on different SID granularities, thereby realizing QoS control.

[0140] Therefore, based on the creative research of the above inventors, the service quality control method and device proposed in the present disclosure are proposed. In the present disclosure, 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 the UPF. The UPF performs corresponding operations based on the indicated QoS flow, 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. This solves the problem in the prior art that one SID can only be bound to one QoS flow information, resulting in the SID being applied to only one QoS flow after applying the Args.Mob.Session behavior, and being unable to implement the identification and positioning of multiple QoS flows in the PDU Session. At the same time, it also solves the problem that the number of SIDs on the UPF increases due to different SIDs for different QoS flows in the PDU session, thereby causing excessive occupation and waste of storage resources and processing resources in the UPF node. It can realize the QoS control of SIDs applied to different PDU Sessions or different QoS flows while saving resources.

[0141] Among them, the method and the device are based on the same application concept. Since the principles of solving problems by the method and the device are similar, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.

[0142] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings.

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

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

[0145] In combination with Figure 1, Figure 1 is a schematic diagram of using the Tag field in the SRH to carry QoS flow information provided by an embodiment of the present disclosure. As shown in Figure 1, a flag Flag is set in the Tag field, and the flag Flag value can be customized 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.

[0146] 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 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 (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 PDU Session 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).

[0147] It should be noted that the QFI and RQI lengths shown in Figure 1 are only recommended options and are merely exemplary, not exclusive. No specific limitations are imposed on the QFI and RQI lengths. Furthermore, the QFI and RQI lengths mentioned in Figures 2 and 3 below are exemplary and are not specifically limited.

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

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

[0150] As shown in Figure 2, Figure 2 is a schematic diagram of using the TLV field in the SRH to carry QoS flow information provided by an embodiment of the present disclosure. As shown in Figure 2, a flag Flag is set in the TLV field in the SRH. The Flag value can be customized 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-PDU Session granularity.

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

[0152] Map (PDU Session ID, UE ID): Applicable to scenarios where multiple PDU Sessions share a single SID. Map (PDU Session ID, UE ID) + QFI uniquely locates a QoS flow for a user's PDU Session, thereby determining the specific QoS flow for the user's specified PDU session. The length and format of Map (PDU Session ID, UE ID) in Figure 3 are for illustrative purposes only and are not intended to be limiting.

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

[0154] As shown in Figure 3, Figure 3 is a schematic diagram of an embodiment of the present disclosure providing an embodiment of identifying QoS flow information through the Argument field of the SID in the SRH. As shown in Figure 3, the Argument field carries QFI and RQI information or mapping information of QFI and RQI to SID (herein, the mapping relationship used to determine QoS flow information), so that the user plane node (including RAN) can determine the user's QoS requirements based on the SID. Among them, Args.mob.QoS can be used in combination with End.Map, End.DT4 / End.DT6 / End.DT46 or End.DX4 / End.DX6 / End.DX2. This method 3 is applicable to scenarios where SID is the QoS granularity.

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

[0156] Therefore, a field is set or extended in the SRv6 packet header to identify and carry QoS Flow information, or a new SID Behavior is defined, namely: using the Tag field in the SRH to carry QoS information (here refers to QoS flow information), using the optional TLA field in the SRH to carry QoS information (here refers to QoS flow information), using the Argument field of the SID to carry or map QoS information (here refers to 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.

[0157] FIG4 is a flow chart of a method for controlling quality of service provided in an embodiment of the present disclosure. As shown in FIG4 , the method for controlling quality of service provided in this embodiment is performed by a radio access network RAN. The method for controlling quality of service provided in this embodiment of the present disclosure includes the following steps:

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

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

[0160] 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

[0161] In the embodiment of the present disclosure, for the downlink, the RAN receives an uplink user data packet from 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 the 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.

[0162] Step 103: Send the SRv6 data packet carrying the QFI to the user plane function UPF, and the UPF is configured to perform corresponding operations according to the QFI.

[0163] Specifically, the SRv6 data packet is sent to the UPF, and the UPF determines the unique QoS flow based on the QFI carried by the SRv6 data packet, and then performs corresponding operations such as rate control and counting based on the characteristics corresponding to the QoS flow, such as rate.

[0164] In the disclosed embodiment, an uplink user data packet from a terminal is first received. The uplink user data packet is then encapsulated into an SRv6 data packet format, a new generation IP bearer protocol based on IPv6 and source routing. The SRv6 data packet header (SRH) contains quality of service (QoS) flow information, including a quality of service (QFI) flow identifier (QFI) for indicating a QoS flow. The SRv6 data packet carrying the QFI is then sent to a user plane function (UPF), which performs corresponding operations based on the QFI. Specifically, based on the received uplink user data packet, the data packet is encapsulated into an SRv6 data packet format, including at least the QoS flow information including the QFI, for indicating a corresponding QoS flow. The SRv6 data packet carrying the QFI is then sent to the UPF, and the UPF performs corresponding operations based on the indicated QoS flow. This enables QoS control by applying the SID to different PDU sessions or different QoS flows, thereby ensuring the user's QoS requirements.

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

[0166] If the SRv6 segment identifier SID is a single protocol data unit session (PDU) 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 using the extension field in the SRH to carry QoS flow information;

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

[0168] 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 QoS flow information, or by defining the SID behavior to carry QoS flow information through the Argument field of the SID in the SRH.

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

[0170] 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 the UPF can perform corresponding operations (such as rate control, counting, etc.) according to the QFI carried by the encapsulated SRv6 data packet, thereby realizing QoS control based on the SRv6 user plane. This solves the problem that in the prior art, one SID can only be bound to one QoS flow information, resulting in the SID being applied to only one QoS flow after the Args.Mob.Session behavior is applied, and the identification and positioning of multiple QoS flows in the PDU Session cannot be realized. At the same time, it also solves the problem that the number of SIDs on the UPF increases due to different SIDs for different QoS flows in the PDU session, which leads to excessive occupation and waste of storage resources and processing resources in the UPF node. It can realize the QoS control of SIDs applied to different PDU Sessions or different QoS flows while saving resources.

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

[0172] 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,

[0173] 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 further includes an RQI, and the RQI is used to indicate whether reflective QoS is enabled for a QoS flow.

[0174] In an embodiment of the present disclosure, 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 encapsulating the SRH for the uplink 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 uplink user data packet, the QoS flow information is encapsulated into the extension field of the SRH.

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

[0176] Setting a flag in the Tag field of the SRH to indicate that the Tag field of the SRH carries QoS flow information;

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

[0178] In the embodiment of the present disclosure, if the SID is a single PDU Session granularity, by setting the 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. The QoS flow information here may include QFI and RQI. The corresponding QoS flow is determined by QFI, and whether reflective QoS is enabled is determined by RQI.

[0179] Specifically, for method 1, by setting the flag Flag in the Tag field, 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 value is 0 or 1, when the Flag value is 1, it indicates that the field carries QoS flow information.

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

[0181] Example 1 (SID is the PDU Session granularity)

[0182] 1 , when the SID is at the PDU Session granularity, the quality of service control method provided in this embodiment includes the following steps:

[0183] UL: The RAN encapsulates the SRv6 header for the data packet (here, the uplink user data packet) based on the QFI and QoS profile (QoS configuration information), and carries the QoS information described in Method 1 in the Tag field of the SRH. The UPF then implements the corresponding QoS features based on the QoS information in the Tag field of the SRH.

[0184] 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:

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

[0186] By setting a 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.

[0187] In the embodiment of the present disclosure, if the SID is a single PDU Session granularity, the QFI and RQI are first encapsulated into the extension field 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 extension field of the SRH is invalid or ignored. Therefore, the corresponding QoS flow is determined by the QoS flow information carried in the extension field of the SRH.

[0188] For method 2, by setting the flag bit Flag in the extension 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 in the extension 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 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 reflective QoS is enabled is determined by the RQI.

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

[0190] Example 2 (SID is the PDU Session granularity)

[0191] As shown in FIG2 , when the SID is a PDU Session granularity, the service quality control method provided in this embodiment includes the following steps:

[0192] UL: When the RAN encapsulates the SRv6 header for a data packet (here, an uplink user data packet) based on the QFI and QoS profile (QoS configuration information), it carries the QoS information in the TLV field of the SRH and sets the Flag value to 0, indicating that subsequent fields will not be parsed. The UPF then implements the corresponding QoS features based on the QoS information in the TLV of the SRH.

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

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

[0195] In the embodiment of the present disclosure, 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.

[0196] 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 reflective QoS is enabled for a QoS flow; and encapsulating the QoS flow information into the extension field of the SRH includes:

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

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

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

[0200] In an embodiment of the present disclosure, if the SID is a multi-PDU Session granularity, the QFI and RQI can be encapsulated into the extension field of the SRH respectively. 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 Session ID 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.

[0201] Specifically, for method 2, by setting the flag bit Flag in the extension 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 in the extension 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.

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

[0203] Example 3 (SID is multi-PDU session granularity)

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

[0205] UL: Based on the QFI and QoS profile (QoS configuration information), the RAN encapsulates the SRv6 header for the data packet (here, the uplink user data packet). It carries QoS information in the TLV field of the SRH, sets the Flag value to 1, uses a Map (PDU Session ID, UE ID) to identify the user and PDU Session, and uses the QFI to determine the QoS information. The UPF then implements the corresponding QoS features based on the QoS information in the TLV of the SRH.

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

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

[0208] In an embodiment of the present disclosure, 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.

[0209] It should be noted that this is consistent with the above-mentioned 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.

[0210] Among them, for method 3, the corresponding QoS flow is indicated by encapsulating the QoS flow information into the Argument field of the SID in the SRH. When the UPF receives the SRv6 data packet, it performs the corresponding operation according to the QFI carried by the Argument field of the SID in the SRH or the mapping relationship used to determine the QoS flow information.

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

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

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

[0214] In an embodiment of the present disclosure, if the SID is the QoS granularity, the QFI and RQI are respectively encapsulated into the Argument field of the SID in the SRH, or the mapping relationship between the 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.

[0215] Specifically, for Method 3, the Argument field carries the QFI and RQI information, or the mapping between the QFI, RQI, and SID (this mapping relationship is used to determine QoS flow information). This allows user plane nodes (including the RAN) to determine the user's QoS requirements based on the SID. Args.mob.QoS can be used in combination with End.Map, End.DT4 / End.DT6 / End.DT46, or End.DX4 / End.DX6 / End.DX2.

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

[0217] Example 4 (SID is the QoS granularity)

[0218] As shown in FIG3 , when the 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 quality of service control method provided in this embodiment includes the following steps:

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

[0220] UL: After receiving the UE's data packet (here, the uplink user data packet), the RAN node encapsulates the uplink user data packet with the corresponding SID list according to the QoS profile (QoS configuration information) corresponding to the QFI. The UPF then implements the corresponding QoS features based on the SID's behavior (for example, the QoS flow information carried in the SID's Argument field in the SRH).

[0221] Therefore, by setting or extending a field in the SRv6 packet header to identify and carry QoS Flow information, or defining a new SID Behavior, the SRv6 node can execute the corresponding QoS features according to the QoS Flow information or SID in the SRH, thereby realizing QoS control based on the SRv6 user plane. This solves the problem in the prior art that one SID can only be bound to one QoS flow information, resulting in the SID being applied to only one QoS flow after the Args.Mob.Session behavior is applied, and it is impossible to identify and locate multiple QoS flows in the PDU Session. It also solves 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 and processing resources in the UPF node. It can realize QoS control by applying SIDs to different PDU Sessions or different QoS flows while saving resources. At the same time, it solves the problem that the combination of QFI + PDU Session ID described in Args.Mob.Session cannot uniquely identify a QoS flow, which may cause the QoS features 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 user's QoS requirements.

[0222] FIG5 is a flow chart of a service quality control method provided by another embodiment of the present disclosure. As shown in FIG5 , the execution subject of the service quality control method provided by this embodiment is the UPF; the service quality control method provided by this embodiment of the present disclosure includes the following steps:

[0223] 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 the QoS flow;

[0224] 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

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

[0226] In the embodiment of the present disclosure, 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 a QFI to indicate a corresponding QoS flow, and the SRv6 data packet carrying the QFI is sent to an intermediate UPF, which then sends the data packet to the RAN. 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. This enables QoS control of SIDs applied to different PDU Sessions or different QoS flows, thereby ensuring the user's QoS requirements.

[0227] Optionally, encapsulating the UE's downlink user data packet into an SRv6 data packet format includes:

[0228] 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 QoS flow information, or by using the extension field in the SRH to carry QoS flow information;

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

[0230] 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 QoS flow information, or by defining the SID behavior to carry QoS flow information through the Argument field of the SID in the SRH.

[0231] In the embodiments of the present disclosure, referring to FIG. 1 to FIG. 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 described again here.

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

[0233] 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 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. This solves the problem in the prior art that one SID can only be bound to one QoS flow information, 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, it also solves 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. It can realize the application of SIDs to different PDU Sessions or different QoS flows for QoS control while saving resources.

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

[0235] 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,

[0236] 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 reflective QoS is enabled for a QoS flow.

[0237] In an embodiment of the present disclosure, 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 extension field of the SRH.

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

[0239] Setting a flag in the Tag field of the SRH to indicate that the Tag field of the SRH carries QoS flow information;

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

[0241] In the embodiment of the present disclosure, if the SID is a single PDU Session granularity, by setting the 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. The QoS flow information here may include QFI and RQI. The corresponding QoS flow is determined by QFI, and whether reflective QoS is enabled is determined by RQI.

[0242] Specifically, for method 1, by setting the flag bit Flag in the Tag field, the flag bit Flag value can be customized 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.

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

[0244] Example 5 (SID is PDU Session granularity)

[0245] 1 , when the SID is at the PDU Session granularity, the quality of service control method provided in this embodiment includes the following steps:

[0246] DL: The Protocol Data Unit Session Anchor (PSA) (here, a UPF) encapsulates the SRv6 header for the user data packet (here, the downlink user data packet) according to the packet detection rules (PDR), forwarding action rules (FAR), and QoS enforcement rules (QER). It also carries QoS information in the Tag field of the SRH. The UPF then applies the appropriate QoS features based on the QoS information in the Tag field of the SRH. The RAN decapsulates the SRv6 packet based on the QFI and QoS profile (QoS configuration information) and sends it to the UE through the DRB mapped to the QFI.

[0247] 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:

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

[0249] By setting a 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.

[0250] In the embodiment of the present disclosure, if the SID is a single PDU Session granularity, the QFI and RQI are first encapsulated into the extension field 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 extension field of the SRH is invalid or ignored. Therefore, the corresponding QoS flow is determined by the QoS flow information carried in the extension field of the SRH.

[0251] For method 2, by setting the flag bit Flag in the extension 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 in the extension 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 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 reflective QoS is enabled is determined by the RQI.

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

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

[0254] As shown in FIG2 , when the SID is a PDU Session granularity, the service quality control method provided in this embodiment includes the following steps:

[0255] DL: The Protocol Data Unit 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 rules PDR, forwarding action rules FAR and QoS execution rules QER, etc., carries QoS information in the TLV field of the SRH, and sets the Flag value to 0, indicating that the subsequent fields are no longer parsed. After that, the UPF implements the corresponding QoS features based on the QoS information carried in the TLV field of the SRH. The RAN decapsulates the SRv6 data packet according to the QFI and QoS profile (QoS configuration information) and sends it to the UE from the DRB mapped by the QFI.

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

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

[0258] In the embodiment of the present disclosure, 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.

[0259] Optionally, the extension field is used to indicate the type, length, and value of the information element; 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 reflective QoS is enabled for a QoS flow; and encapsulating the QoS flow information into the extension field of the SRH includes:

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

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

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

[0263] In an embodiment of the present disclosure, if the SID is a multi-PDU Session granularity, the QFI and RQI can be encapsulated into the extension field of the SRH respectively. 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 Session ID 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.

[0264] Specifically, for method 2, by setting the flag bit Flag in the extension 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 in the extension 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.

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

[0266] Example 7 (SID is multi-PDU session granularity)

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

[0268] DL: When the Protocol Data Unit 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 rules PDR, forwarding action rules FAR and QoS execution rules QER, it carries 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. The UPF then implements the corresponding QoS features based on the QoS information in the TLV in the SRH.

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

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

[0271] In an embodiment of the present disclosure, 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 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, 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.

[0272] It should be noted that this is consistent with the above-mentioned 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.

[0273] Among them, for method 3, the corresponding QoS flow is indicated by encapsulating the QoS flow information into the Argument field of the SID in the SRH. When the UPF receives the SRv6 data packet, it performs the corresponding operation according to the QFI carried by the Argument field of the SID in the SRH or the mapping relationship used to determine the QoS flow information.

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

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

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

[0277] In an embodiment of the present disclosure, if the SID is the QoS granularity, the QFI and RQI are respectively encapsulated into the Argument field of the SID in the SRH, or the mapping relationship between the 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.

[0278] Specifically, for method 3, the Argument field carries QFI and RQI information, or the mapping between QFI, RQI, and SID (this refers to the mapping relationship used to determine QoS flow information), allowing user plane nodes (including the RAN) to determine the user's QoS requirements based on the SID. Args.mob.QoS can be used in combination with End.Map, End.DT4 / End.DT6 / End.DT46, or End.DX4 / End.DX6 / End.DX2.

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

[0280] Exemplary embodiment 8 (SID is QoS granularity)

[0281] As shown in FIG3 , when the 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 quality of service control method provided in this embodiment includes the following steps:

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

[0283] DL: After receiving a data packet (here, a downlink user data packet), the PSA encapsulates the downlink user data packet with the SRv6 header of the corresponding QoS flow, including the corresponding SID list, based on packet inspection rules. After receiving the downlink user data packet, the RAN determines the QFI based on the Args.mob.QoS behavior of the SID.

[0284] Therefore, by setting or extending a field in the SRv6 packet header to identify and carry QoS Flow information, or defining a new SID Behavior, the SRv6 node can execute the corresponding QoS features according to the QoS Flow information or SID in the SRH, thereby realizing QoS control based on the SRv6 user plane. This solves the problem in the prior art that one SID can only be bound to one QoS flow information, resulting in the SID being applied to only one QoS flow after the Args.Mob.Session behavior is applied, and it is impossible to identify and locate multiple QoS flows in the PDU Session. It also solves 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 and processing resources in the UPF node. It can realize QoS control by applying SIDs to different PDU Sessions or different QoS flows while saving resources. At the same time, it solves the problem that the combination of QFI + PDU Session ID described in Args.Mob.Session cannot uniquely identify a QoS flow, which may cause the QoS features 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 user's QoS requirements.

[0285] It should be noted here that the specific implementation process of the service quality control method with UPF as the execution body can refer to the embodiments shown in Figures 1 to 3, and the specific implementation process will not be repeated here.

[0286] FIG6 is a schematic diagram of the structure of a QoS control device according to an embodiment of the present disclosure. As shown in FIG6 , the QoS control device according to this embodiment is applied to a radio access network (RAN). The QoS control device according to this embodiment includes a transceiver 600 configured to receive and transmit data under the control of a processor 610.

[0287] In FIG6 , the bus architecture may include any number of interconnected buses and bridges, specifically various circuits linked together by 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 peripheral devices, 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 over a transmission medium, such as 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.

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

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

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

[0291] Encapsulating 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, the QoS flow information includes a QFI, and the QFI is used to indicate the QoS flow;

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

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

[0294] 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 QoS flow information, or by using the extension field in the SRH to carry QoS flow information;

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

[0296] 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 QoS flow information, or by defining the SID behavior to carry QoS flow information through the Argument field of the SID in the SRH.

[0297] 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:

[0298] 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 reflective QoS is enabled for a QoS flow; or,

[0299] 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 further includes an RQI, and the RQI is used to indicate whether reflective QoS is enabled for a QoS flow.

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

[0301] Setting a flag in the Tag field of the SRH to indicate that the Tag field of the SRH carries QoS flow information;

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

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

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

[0305] By setting a 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.

[0306] 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:

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

[0308] 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 reflective QoS is enabled for a QoS flow; the processor is configured to, when encapsulating the QoS flow information into the extension field of the SRH, specifically include:

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

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

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

[0312] 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 including:

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

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

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

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

[0317] It should be noted here that the service quality control device provided by the present disclosure can implement all the method steps implemented by the method embodiments shown in Figures 1 to 4, and can achieve the same technical effects. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0318] FIG7 is a schematic structural diagram of a service quality control apparatus provided in another embodiment of the present disclosure. As shown in FIG7 , the service quality control apparatus provided in this embodiment is applied to a radio access network RAN. The service quality control apparatus 700 provided in this embodiment includes:

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

[0320] 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;

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

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

[0323] 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 extension field in the SRH to carry QoS flow information;

[0324] 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 extension field in the SRH to carry QoS flow information;

[0325] 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 defining the SID behavior to carry QoS flow information through the Argument field of the SID in the SRH.

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

[0327] 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 further includes an RQI, and the RQI is used to indicate whether reflective QoS is enabled for a QoS flow; or,

[0328] 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 extension field of the SRH; the QoS flow information also includes an RQI, and the RQI is used to indicate whether reflective QoS is enabled for a QoS flow.

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

[0330] Setting a flag in the Tag field of the SRH to indicate that the Tag field of the SRH carries QoS flow information;

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

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

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

[0334] By setting a 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.

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

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

[0337] Optionally, the extension field is used to indicate the type, length, and value of the information element; 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 reflective QoS is enabled for a QoS flow; the processing unit 702 is specifically configured to:

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

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

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

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

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

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

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

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

[0346] It should be noted here that the service quality control device provided by the present disclosure can implement all the method steps implemented in the method embodiments of Figures 1 to 4, and can achieve the same technical effects. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0347] Figure 8 is a structural diagram of a service quality control device provided in another embodiment of the present disclosure. As shown in Figure 8, 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.

[0348] In FIG8 , the bus architecture may include any number of interconnected buses and bridges, specifically various circuits linked together by 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 peripheral devices, 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, such as 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.

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

[0350] 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; and the processor 810 is used to read the computer program in the memory and perform the following operations:

[0351] Encapsulating the UE's downlink 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 the QoS flow;

[0352] 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,

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

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

[0355] 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 QoS flow information, or by using the extension field in the SRH to carry QoS flow information;

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

[0357] 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 QoS flow information, or by defining the SID behavior to carry QoS flow information through the Argument field of the SID in the SRH.

[0358] 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:

[0359] 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 reflective QoS is enabled for a QoS flow; or,

[0360] 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 the RQI used to indicate whether reflective QoS is enabled for a QoS flow.

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

[0362] Setting a flag in the Tag field of the SRH to indicate that the Tag field of the SRH carries QoS flow information;

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

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

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

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

[0367] 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:

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

[0369] 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 reflective QoS is enabled for a QoS flow; the processor 810 is configured to, when encapsulating the QoS flow information into the extension field of the SRH, specifically include:

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

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

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

[0373] 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:

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

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

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

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

[0378] It should be noted here that the service quality control device provided by the present disclosure can implement all the method steps implemented by the method embodiments shown in Figures 1-3 and 5, and can achieve the same technical effects. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0379] FIG9 is a schematic structural diagram of a service quality control apparatus provided in another embodiment of the present disclosure. As shown in FIG9 , the service quality control apparatus provided in the embodiment of the present disclosure is applied to a user plane function (UPF). The service quality control apparatus 900 provided in this embodiment includes:

[0380] 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 the QoS flow;

[0381] 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

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

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

[0384] 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 extension field in the SRH to carry QoS flow information;

[0385] 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 extension field in the SRH to carry QoS flow information;

[0386] 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 defining the SID behavior to carry QoS flow information through the Argument field of the SID in the SRH.

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

[0388] When the SID is a single 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 also includes an RQI, and the RQI is used to indicate whether reflective QoS is enabled for a QoS flow; or,

[0389] When the SID is a single PDU Session granularity, 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 reflective QoS is enabled for a QoS flow.

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

[0391] Setting a flag in the Tag field of the SRH to indicate that the Tag field of the SRH carries QoS flow information;

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

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

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

[0395] By setting a 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.

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

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

[0398] Optionally, the extension field is used to indicate the type, length, and value of the information element; 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 reflective QoS is enabled for a QoS flow; the processing unit 901 is specifically configured to:

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

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

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

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

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

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

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

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

[0407] It should be noted here that the service quality control device provided by the present disclosure can implement all the method steps implemented in the method embodiments of Figures 1-3 and Figure 5, and can achieve the same technical effects. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0408] It should be noted that the division of units in the embodiments of the present disclosure is illustrative and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of the present disclosure may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0409] 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 invention 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, a server, or a network device, etc.) or a processor (processor) to execute all or part of the steps of the various embodiments of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0410] The embodiments of the present disclosure further provide a non-transitory readable storage medium storing a computer program configured to cause a processor to execute any of the above method embodiments.

[0411] 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)), optical storage (such as CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drives (SSDs)), etc.

[0412] Those skilled in the art will appreciate that the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage and optical storage, etc.) containing computer-usable program code.

[0413] The present disclosure 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 disclosure. 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 produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0414] 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 a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0415] 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, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0416] Obviously, those skilled in the art may make various changes and modifications to the present disclosure without departing from the spirit and scope of the present disclosure. Thus, if these modifications and variations of the present disclosure fall within the scope of the claims of the present disclosure and their equivalents, the present disclosure is 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 the flag bit Flag in the Tag field of the SRH, it is determined to indicate the SRH The Tag field carries 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 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.

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 also includes an RQI; the RQI is used to indicate whether a QoS flow enables reflective QoS; The encapsulating the QoS flow information into the Argument field of the SID in the SRH 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. The device according to claim 19, characterized in that The processing unit is specifically used for: 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; 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; 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.

21. The device according to claim 20, characterized in that The processing unit is specifically used for: 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, 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.

22. The device according to claim 21, characterized in that The processing unit is specifically used for: 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.

23. The device according to claim 21, characterized in that The extension field is used to indicate the type, length and value of the information element; the processing unit is specifically used to: 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.

24. The device according to claim 20, characterized in that The processing unit is specifically used for: 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.

25. The device according to claim 24, characterized in that The extended 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 processing unit is specifically used to: 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.

26. The device according to any one of claims 20 to 25, characterized in that The processing unit is specifically used for: 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.

27. The device according to claim 26, characterized in that The QoS flow information further includes an RQI; the RQI is used to indicate whether a QoS flow enables reflective QoS; the processing unit is specifically used to: 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.

28. 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.

29. The device according to claim 28, characterized in that The processing unit is specifically used for: 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; 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; 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.

30. The device according to claim 29, characterized in that The processing unit is specifically used for: When the SID is a single 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 also includes an RQI, and the RQI is used to indicate whether a QoS flow enables reflective QoS; or, When the SID is a single PDU Session granularity, 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 is also Includes an RQI, where the RQI is used to indicate whether a QoS flow enables reflective QoS.

31. The device according to claim 30, characterized in that The processing unit is specifically used for: 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.

32. The device according to claim 30, characterized in that The extension field is used to indicate the type, length and value of the information element; the processing unit is specifically used to: 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.

33. The device according to claim 29, characterized in that The processing unit is specifically used for: 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.

34. The device according to claim 33, characterized in that The extended 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 processing unit is specifically used to: 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.

35. The device according to any one of claims 29 to 34, characterized in that The processing unit is specifically used for: 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.

36. The device according to claim 35, characterized in that The QoS flow information further includes an RQI; the RQI is used to indicate whether a QoS flow enables reflective QoS; the processing unit is specifically used to: 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.

37. 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.

38. The device according to claim 37, 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.

39. The device according to claim 38, 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 PDU Session granularity, specifically comprising: 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 a QoS Whether the flow has reflective QoS enabled; 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.

40. The device according to claim 38, 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-PDU Session 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.

41. The device according to any one of claims 38 to 40, 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.

42. 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.

43. The device according to claim 42, 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.

44. The device according to claim 43, 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 PDU Session 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.

45. The device according to claim 43, 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-PDU Session 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.

46. ​​The device according to any one of claims 43 to 45, 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.

47. 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