WO2018205155A1 - 一种QoS控制方法及设备 - Google Patents

一种QoS控制方法及设备 Download PDF

Info

Publication number
WO2018205155A1
WO2018205155A1 PCT/CN2017/083671 CN2017083671W WO2018205155A1 WO 2018205155 A1 WO2018205155 A1 WO 2018205155A1 CN 2017083671 W CN2017083671 W CN 2017083671W WO 2018205155 A1 WO2018205155 A1 WO 2018205155A1
Authority
WO
WIPO (PCT)
Prior art keywords
qos
sdf
control information
identifier
qos control
Prior art date
Application number
PCT/CN2017/083671
Other languages
English (en)
French (fr)
Inventor
吴义壮
熊春山
韦安妮
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to CN202111209592.4A priority Critical patent/CN113923714A/zh
Priority to JP2019561743A priority patent/JP7250700B2/ja
Priority to CN201780038531.1A priority patent/CN109314921B/zh
Priority to RU2019139836A priority patent/RU2744907C1/ru
Priority to PCT/CN2017/083671 priority patent/WO2018205155A1/zh
Priority to PL17909069T priority patent/PL3624500T3/pl
Priority to BR112019023333-4A priority patent/BR112019023333A2/pt
Priority to KR1020197036331A priority patent/KR102305716B1/ko
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP21186467.3A priority patent/EP3986019A1/en
Priority to EP17909069.1A priority patent/EP3624500B1/en
Priority to CN201910168204.9A priority patent/CN109982377B/zh
Priority to CN202111209772.2A priority patent/CN113923715A/zh
Publication of WO2018205155A1 publication Critical patent/WO2018205155A1/zh
Priority to US16/398,937 priority patent/US10772004B2/en
Priority to US17/011,349 priority patent/US11259207B2/en
Priority to US17/565,829 priority patent/US20220201542A1/en
Priority to JP2022054074A priority patent/JP2022093339A/ja

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2441—Traffic characterised by specific attributes, e.g. priority or QoS relying on flow classification, e.g. using integrated services [IntServ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H04W28/0263—Traffic management, e.g. flow control or congestion control per individual bearer or channel involving mapping traffic to individual bearers or channels, e.g. traffic flow template [TFT]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a QoS (Quality of Service) control method and device.
  • QoS Quality of Service
  • Wireless networks have been used by more and more people or machines, and more and more services are carried over wireless networks.
  • various services in the wireless network such as calls, conference calls, emergency calls, public warnings, etc., they have their own specific business security requirements.
  • radio resources Due to the limited nature of radio resources, if there are many services to be processed at the same time, it is necessary to control access, resource scheduling, etc. according to the QoS rules and priorities of each service. For example, when user A is on a call, user B starts to download a file. Because the wireless resource is limited, if user B's download service preempts the wireless resource of user A's call service, it will cause a very bad user experience. Therefore, it needs to be a call. The service sets a higher priority than the download service to ensure that the radio resource scheduling of the call service is preferentially guaranteed when the radio resources are insufficient.
  • the QoS architecture may be as shown in FIG. 1.
  • One terminal may establish one or more PDU (Packet Data Unit) sessions with the 5G core network, and the RAN (Radio Access Network)
  • PDU session establishes one or more Data Radio Bearers (DRBs).
  • DRBs Data Radio Bearers
  • One DRB contains one or more QoS flows, and each QoS flow corresponds to one or more Packet Filters.
  • QoS flow1 corresponds to packet filter 1 and packet filter 2, then only packets that can pass packet filter 1 or packet filter 2 can be transmitted through QoS flow1.
  • one QoS flow corresponds to a set of QoS parameters, and the QoS processing is the same using data packets transmitted by the same QoS flow.
  • Different services correspond to different SDF (Service Data Flow), and one SDF can correspond to one or more packet filters or one application detection filter. For example, if service 1 corresponds to SDF1 and SDF1 corresponds to packet filter 3 and packet filter 4, then the packet belonging to service 1 can pass packet filter 3 or packet filter 4.
  • SDF Service Data Flow
  • the mapping rules are different when the uplink and downlink data packets are mapped to the QoS flow. Therefore, in some special cases, the terminal side may occur.
  • the network maps the upstream and downstream packets to different QoS flows, resulting in packet loss.
  • the embodiment of the present application provides a QoS control method and device for performing QoS control on an uplink data packet.
  • a QoS control method provided by an embodiment of the present application includes:
  • the session management function SMF entity obtains service data flow SDF level QoS control information
  • the SMF entity sends the SDF level QoS control information to the terminal.
  • the SMF entity sends the SDF level QoS control information to a user plane function UPF entity, so that the UPF verifies QoS control of an uplink data packet according to the SDF level QoS control information, or The SDF level QoS control information is deleted.
  • the SMF entity acquires SDF level QoS control information, including: the SMF The entity acquires SDF level QoS control information according to the session management request sent by the policy control function PCF entity; or the SMF entity acquires SDF level QoS control information according to the local policy.
  • the SDF level QoS control information includes: an identifier of the SDF; or an identifier of the SDF, and at least one or combination of the following: at least one packet filter corresponding to the SDF, priority Level, QoS flow identification, QoS parameters.
  • the SDF level QoS control information includes: an identifier of the QoS flow; or an identifier of the QoS flow, and at least one or a combination of: at least one identifier of the SDF, and the at least one At least one packet filter corresponding to the SDF, a priority corresponding to the at least one SDF, and a QoS parameter corresponding to the QoS flow.
  • the SDF level QoS control information includes: an identifier of the QoS rule; or an identifier of the QoS rule, and at least one or a combination of at least one packet filtering corresponding to the QoS rule. , priority, QoS flow identification, QoS parameters.
  • the method further includes:
  • the SMF entity sends an QoS flow identifier or an QoS flow identifier and a QoS parameter corresponding to the QoS flow to the access network device, so that the access network device establishes, releases, or binds to the corresponding air interface resource.
  • a QoS control method provided by an embodiment of the present application includes:
  • the terminal performs QoS control on the uplink data packet according to the SDF level QoS control information, or deletes the SDF level QoS control information.
  • the SDF level QoS control information includes: an identifier of the SDF; or an identifier of the SDF, and one or a combination of the following: at least one packet filter corresponding to the SDF, priority , QoS flow identification and QoS parameters.
  • the SDF level QoS control information includes: an identifier of the QoS flow; or an identifier of the QoS flow, and at least one or a combination of: at least one identifier of the SDF, and the at least one At least one packet filter corresponding to the SDF, a priority corresponding to the at least one SDF, and a QoS parameter corresponding to the QoS flow.
  • the SDF level QoS control information includes: an identifier of the QoS rule; or an identifier of the QoS rule, and at least one or a combination of at least one packet filtering corresponding to the QoS rule. , priority, QoS flow identification and QoS parameters.
  • the terminal performs QoS control on the uplink data packet according to the SDF level QoS control information, where the terminal determines, according to the priority in the SDF level QoS control information, the SDF level packet filtering.
  • the matching order of the devices the terminal performs packet matching according to the matching order of the SDF level packet filters, and performs QoS control according to the QoS flows corresponding to the packet filters that match the success.
  • an embodiment of the present invention provides a session management function SMF entity, where the session management function SMF entity has a function of implementing a session management function SMF entity in the foregoing method example.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the structure of the session management function SMF entity includes a processing unit and a communication unit, the processing unit being configured to support a session management function SMF entity to perform a corresponding function in the above method.
  • the communication unit is configured to support communication between the session management function SMF entity and other devices.
  • the session management function SMF entity also A storage unit can be included, the storage unit being operatively coupled to the processing unit for storing program instructions and data necessary for the session management function SMF entity.
  • the processing unit can be a processor
  • the communication unit can be a transceiver
  • the storage unit can be a memory
  • a session management function SMF entity provided by the embodiment of the present application includes:
  • processors and a memory and a transceiver respectively connected to the processor;
  • the processor is configured to invoke a computer program pre-stored in the memory to execute:
  • the processor is further configured to: send, by the transceiver, the SDF level QoS control information to a user plane function UPF entity, so that the UPF according to the SDF level QoS control information Verify QoS control of the upstream packet or delete the SDF level QoS control information.
  • the processor when acquiring the SDF level QoS control information, is specifically configured to: obtain the SDF level QoS control information according to the session management request sent by the policy control function PCF entity; or obtain the local QoS control information according to the local policy. SDF level QoS control information.
  • the SDF level QoS control information includes: an identifier of the SDF; or an identifier of the SDF, and at least one or combination of the following: at least one packet filter corresponding to the SDF, priority Level, QoS flow identification, QoS parameters.
  • the SDF level QoS control information includes: an identifier of the QoS flow; or an identifier of the QoS flow, and at least one or a combination of: at least one identifier of the SDF, and the at least one At least one packet filter corresponding to the SDF, a priority corresponding to the at least one SDF, and a QoS parameter corresponding to the QoS flow.
  • the SDF level QoS control information includes: an identifier of the QoS rule; or an identifier of the QoS rule, and at least one or a combination of at least one packet filtering corresponding to the QoS rule. , priority, QoS flow identification, QoS parameters.
  • the processor is further configured to:
  • the QoS flow identifier or the QoS flow identifier and the QoS parameter corresponding to the QoS flow are sent to the access network device by the transceiver, so that the access network device establishes release or binds to the corresponding air interface resource.
  • an embodiment of the present invention provides a terminal, where the terminal has a function of implementing terminal behavior in the foregoing method example.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the structure of the terminal includes a processing unit and a communication unit, the processing unit being configured to support the terminal to perform a corresponding function in the above method.
  • the communication unit is used to support communication between the terminal and other devices.
  • the terminal may further include a storage unit for coupling with the processing unit, which stores program instructions and data necessary for the terminal.
  • the processing unit can be a processor
  • the communication unit can be a transceiver
  • the storage unit can be a memory
  • a terminal provided by an embodiment of the present application includes: a processor and a memory and a transceiver respectively connected to the processor;
  • the processor is configured to invoke a computer program pre-stored in the memory to execute:
  • the SDF level QoS control information includes: an identifier of the SDF; or an identifier of the SDF, and one or a combination of the following: at least one packet filter corresponding to the SDF, priority , QoS flow identification and QoS parameters.
  • the SDF level QoS control information includes:
  • the QoS flow identifier or
  • An identifier of the QoS flow and at least one or a combination of: an identifier of the at least one SDF, at least one packet filter corresponding to the at least one SDF, a priority corresponding to the at least one SDF, corresponding to the QoS flow QoS parameters.
  • the SDF level QoS control information includes: an identifier of the QoS rule; or an identifier of the QoS rule, and at least one or a combination of at least one packet filtering corresponding to the QoS rule. , priority, QoS flow identification and QoS parameters.
  • the processor is further configured to determine, according to a priority in the SDF level QoS control information, a matching order of an SDF level packet filter; the terminal according to the SDF level packet filter The matching order performs packet matching, and performs QoS control according to the QoS flow corresponding to the packet filter that matches the success.
  • an embodiment of the present invention provides a communication system, where the system includes the session management function SMF entity of the above aspect.
  • the system may further include other devices, such as a PCF, a UPE, or a terminal device, that interact with the session management function SMF entity in the solution provided by the embodiment of the present invention.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions used by the session management function SMF entity, which includes a program designed to perform the above aspects.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions for use in the terminal, including a program designed to perform the above aspects.
  • the present application also provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the methods described in the above aspects.
  • FIG. 1 is a schematic diagram of a QoS architecture provided by an embodiment of the present application
  • FIG. 2 is a schematic diagram of mapping an uplink/downlink data packet to a QoS flow according to an embodiment of the present disclosure
  • FIG. 3 is a schematic diagram of a matching error when an uplink/downlink data packet is mapped to a QoS flow according to an embodiment of the present disclosure
  • FIG. 4 is a schematic structural diagram of a system applicable to an embodiment of the present application according to an embodiment of the present disclosure
  • FIG. 5 is a schematic flowchart of a QoS control method according to an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of a specific embodiment of an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of a second embodiment of a specific embodiment according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic flowchart of a third embodiment of a specific embodiment according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of an SMF entity according to an embodiment of the present application.
  • FIG. 10 is a second schematic structural diagram of an SMF entity according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of a terminal according to an embodiment of the present application.
  • FIG. 12 is a second schematic structural diagram of a terminal according to an embodiment of the present disclosure.
  • the terminal and the network side equipment in the prior art have the following problems when performing QoS control on the uplink and downlink data packets:
  • the NAS layer (non-access stratum) of the terminal and the User Plane Function (UPF) on the network side map the uplink and downlink data packets to a QoS flow based on the Packet Filter; the AS layer of the terminal (connected)
  • the ingress layer and the RAN associate the upstream and downstream QoS flows to one DRB.
  • the specific mapping mechanism can be as shown in Figure 2, as follows:
  • each QoS flow corresponds to a template of QoS flow
  • each QoS flow template corresponds to one or more packet filters
  • each QoS flow template has a priority.
  • the QoS flow template is matched with each QoS flow template according to the priority from high to low.
  • the QoS flow template is matched to the corresponding QoS flow template, the matching is stopped. Specifically, the data packet is first matched with the QoS flow template with the highest priority. If the data packet can pass any packet filter corresponding to the QoS flow template, that is, the matching succeeds, the data packet uses the QoS corresponding to the QoS flow template. Flow is transmitted. Otherwise, it continues to match the lower priority QoS flow template until it matches the corresponding QoS flow template.
  • each SDF corresponds to one or more packet filters, and each SDF corresponds to one priority.
  • the network device sends a data packet
  • the data packet is matched with the packet filter of the SDF in turn according to the priority of each SDF, and when the packet filter of the corresponding SDF is matched, the matching is stopped.
  • the data packet is first matched with the packet filter of the SDF with the highest priority. If the data packet can pass the packet filter of the SDF, that is, the matching succeeds, the data packet passes the QoS corresponding to the packet filter of the SDF. Flow is transmitted, otherwise it continues to match the packet filter of the lower priority SDF.
  • the terminal side and the network side use different matching rules to perform the matching of the data packets, so that the same data packet may match different QoS flows in the terminal side and the network side, thereby causing packet loss, which may be as shown in FIG. 3 .
  • the terminal wants to transmit a data packet, if the data packet can match the packet filter of SDF a and the packet filter of SDF b, the terminal is uplinked due to different matching priorities.
  • the packet will be matched to QoS flow1, and on the network side, the packet will be matched to QoS flow2.
  • the network side verifies whether the data packet sent by the terminal uses the correct QoS flow. If the network side determines that the terminal uses the wrong QoS flow, the network side will discard the data packet.
  • the embodiment of the present application provides a QoS control method and device.
  • the terminal involved in the present application may include a handheld device having a wireless communication function, an in-vehicle device, a wearable device, a computing device, or other processing device connected to the wireless modem, and various forms of UE (User Equipment).
  • MS Mobile Station
  • Terminal Equipment Terminal Equipment
  • the QoS control method provided by the embodiment of the present application can be applied to the 5G network architecture shown in FIG. 4, where:
  • UPF User Plane Function
  • its main functions include: packet routing and transmission, packet detection, service usage reporting, QoS processing, lawful interception, uplink packet detection, downlink packet storage and other user plane related functions.
  • AMF Access and Mobility Management Function
  • main function Can include: access management, mobility management, registration management, access authentication and authorization, reachability management, security context management and other access and mobility related functions.
  • SMF Session Management Function
  • session management such as session establishment, modification and release, including tunnel maintenance between UPF and AN
  • UPF selection and control UPF selection and control
  • SSC Service and Session Continuity
  • business and session continuity session-related functions such as mode selection, roaming, etc.
  • PCF Policy Control Function
  • main functions include: unified policy formulation, provision of policy control, and policy-related functions such as subscription information related to obtaining policy decisions from UDR.
  • AUSF Authentication Server Function
  • main functions include: Authenticating user equipment is legal.
  • AF Application function
  • main function which is based on the main function and provides services. Specifically, the service routing and access network capabilities are open and interact with the policy architecture.
  • UDM Unified Data Management
  • its main functions are trust, location and contract management, storing user subscription data.
  • DN Data Network
  • its main function is to provide specific data services, such as carrier services, Internet access or third-party services.
  • FIG. 4 is only an example of the application scenario of the embodiment of the present application, and is not limited to the application scenario of the embodiment of the present application, and may be applicable to the system architecture of the embodiment of the present application, and may include More or fewer network elements, or different system architectures, such as EPS system architecture or CUPS architecture.
  • FIG. 5 is a schematic flowchart of a QoS control method according to an embodiment of the present disclosure. As shown in the figure, the method includes the following steps:
  • Step 501 The SMF entity acquires SDF level QoS control information.
  • Step 502 The SMF entity sends the SDF level QoS control information to the terminal.
  • Step 503 The terminal performs QoS control on the uplink data packet according to the received SDF level QoS control information, or deletes the SDF level QoS control information.
  • the SDF level QoS control information acquired by the SMF entity is used to perform QoS control on the SDF, and the SMF entity sends the SDF level QoS control information to the terminal, so that the terminal performs QoS control on the uplink data packet.
  • the SDF level QoS control information indicates that at least one packet filter corresponding to one SDF corresponds to the same QoS flow, that is, corresponds to the same QoS parameter, and the priority of each packet filter SDF level. the same.
  • different SDFs have different priorities.
  • the QoS parameters corresponding to different SDFs may be the same, that is, they may correspond to the same QoS flow, but the priorities of the corresponding packet filters are different.
  • the SDF level QoS control information includes one or a combination of: an SDF level identifier, at least one SDF level packet filter, an SDF level priority (ie, also an SDF level packet filter priority), and QoS.
  • SDF level identifier may be in multiple forms, such as an SDF identifier (SDF ID), a QoS rule ID, or other types of identifiers that may reflect the SDF level.
  • the specific representation manner of the SDF level QoS control information acquired by the SMF entity is various, including the following three modes, but is not limited thereto:
  • the QoS control information acquired by the SMF entity is SDF level, but its representation manner is various.
  • the SDF level QoS control signal may include one or a combination of: an identifier of the SDF, at least one packet filter corresponding to the SDF, a priority, an identifier of the QoS flow, and a QoS parameter.
  • the SDF level QoS control information acquired by the SMF entity includes the newly added SDF identifier
  • Packet filter at least one packet filter corresponding to the SDF
  • Priority the priority corresponding to the SDF, that is, the priority of the above packet filter
  • the QoS flow identifier the QoS flow corresponding to the SDF, that is, the data packet belonging to the SDF is transmitted through the QoS flow;
  • the QoS parameter is included: a QoS parameter corresponding to the QoS flow, for example, a packet delay, a bit rate, and a packet loss rate.
  • the QoS parameter may further include a 5QI (5G QoS Indicator); if the QoS flow is a GBR QoS flow (guarantee bit)
  • the QoS parameter may include 5QI, Notification, GFBR (Guaranteed Flow Bit Rate), and MFBR (Maximum Flow Bit Rate).
  • the SDF level QoS control information acquired by the SMF entity includes at least the identifier of the SDF to be modified, and further includes one or a combination of the following information:
  • a packet filter at least one packet filter corresponding to the SDF, or at least one packet filter corresponding to the SDF to be deleted; or at least one packet filter corresponding to the updated SDF.
  • Priority the modified priority corresponding to the SDF
  • ID of the QoS flow the identifier of the modified QoS flow corresponding to the SDF
  • QoS parameter The modified QoS parameter corresponding to the SDF.
  • the QoS parameter may further include 5QI; if the QoS flow is GBR QoS flow, the QoS parameter may include 5QI, Notification, GFBR, and MFBR.
  • the SDF level QoS control information acquired by the SMF entity may include only the identifier of the SDF to be deleted.
  • the SDF level QoS control information may include one or a combination of: an identifier of the QoS flow, an identifier of the at least one SDF, at least one packet filter corresponding to the at least one SDF, a priority corresponding to the at least one SDF, QoS parameters corresponding to QoS flow.
  • the QoS flow is used as the unit of QoS control, and the following three scenarios may also be included:
  • the SDF level QoS control information acquired by the SMF entity includes the identifier of the newly created QoS flow, and may further include:
  • the identifier of the SDF the identifier of the at least one SDF corresponding to the newly created QoS flow; for example, the identifier of the SDF 1 corresponding to the added QoS flow and the identifier of the SDF 2;
  • Packet filter at least one packet filter corresponding to each of the above SDFs; for example, packet filtering corresponding to SDF 1 1, packet filter 2, packet filter 3 corresponding to SDF 2, packet filter 4;
  • Optional QoS parameters QoS parameters corresponding to the newly created QoS flow.
  • the QoS parameter may further include 5QI; if the newly created QoS flow is GBR QoS flow, the QoS parameter may include 5QI, Notification, GFBR, and MFBR.
  • the QoS control information acquired by the SMF entity includes at least the identifier of the QoS flow to be modified, and further includes one or a combination of the following information:
  • the identifier of the SDF the identifier of the SDF corresponding to the QoS flow to be added, or the identifier of the SDF corresponding to the QoS flow to be modified, or the identifier of the SDF corresponding to the QoS flow to be deleted;
  • a packet filter if the SDF corresponding to the QoS flow is added, at least one packet filter corresponding to the added SDF is included; if the existing packet filter corresponding to the SDF 1 corresponding to the QoS flow is modified, Include at least one packet filter corresponding to the SDF 1 to be added, or at least one packet filter corresponding to the SDF 1 to be deleted, or at least one modified packet filter corresponding to the SDF to be modified;
  • Priority if the SDF corresponding to the QoS flow is added, the priority corresponding to the SDF to be added is included; if the priority of an SDF corresponding to the QoS flow is modified, the method includes: Priority
  • QoS parameter The modified QoS parameter corresponding to the QoS flow.
  • the QoS parameter may further include 5QI; if the modified QoS flow is GBR QoS flow, the QoS parameter may include 5QI, Notification, GFBR, and MFBR.
  • the SDF level QoS control information acquired by the SMF entity may include an identifier of the QoS flow to be deleted.
  • a QoS rule corresponds to an SDF.
  • the SDF level QoS control information may include one or a combination of: an identifier of the QoS rule, at least one packet filter corresponding to the QoS rule, a priority, an identifier of the QoS flow, and a QoS parameter.
  • the QoS rule is used as the QoS control unit, and the following three scenarios may also be included:
  • the SDF level QoS control information acquired by the SMF entity includes the identifier of the newly added QoS rule, and further includes the following information:
  • Packet filter at least one packet filter corresponding to the added QoS rule
  • Priority the priority corresponding to the added QoS rule, that is, the priority of the above packet filter
  • QoS flow identifier the identifier of the QoS flow corresponding to the added QoS rule
  • Optional QoS parameters QoS parameters corresponding to QoS flow.
  • the QoS parameter may further include a 5QI; if the QoS flow corresponding to the added QoS rule is a GBR QoS flow, the QoS parameter may include a 5QI, Notification, GFBR and MFBR.
  • the SDF level QoS control information acquired by the SMF entity includes at least the identifier of the QoS rule to be modified, and further includes one or a combination of the following information:
  • Packet filter at least one packet filter to be added corresponding to the QoS rule, or the QoS to be deleted At least one packet filter corresponding to the rule, or modified at least one packet filter corresponding to the QoS rule;
  • Priority the modified priority corresponding to the QoS rule
  • the identifier of the QoS flow the identifier of the modified QoS flow corresponding to the QoS rule;
  • QoS parameter The modified QoS parameter corresponding to the modified QoS flow.
  • the QoS parameter may further include 5QI; if the modified QoS flow is GBR QoS flow, the QoS parameter may include 5QI, Notification, GFBR, and MFBR.
  • the SDF level QoS control information acquired by the SMF entity may include only the identifier of the QoS rule to be deleted.
  • one of the foregoing three methods may be selected according to specific application requirements, and the SDF level QoS control information is sent to the terminal, so that the terminal performs QoS control on the uplink data packet according to the SDF level QoS control information.
  • the SMF entity may further send the foregoing SDF level QoS control information to the UPF entity, so that the UPF entity verifies the QoS control of the uplink data packet according to the SDF level QoS control information.
  • the terminal and the UPF can perform QoS control on the uplink data packet respectively based on the same QoS control information, thereby avoiding different QoS control of the uplink data by the terminal and the UPF.
  • the phenomenon of packet loss since the SMF entity sends the SDF level QoS control information to the terminal and the UPF entity, the terminal and the UPF can perform QoS control on the uplink data packet respectively based on the same QoS control information, thereby avoiding different QoS control of the uplink data by the terminal and the UPF.
  • the SMF entity may also send the following two types of information to the access network device: one, a QoS flow identifier, or two, an identifier of the QoS flow, and a QoS parameter corresponding to the QoS flow, so that the access network device according to the foregoing Information is created, deleted, or bound to the corresponding air interface resource.
  • the SMF entity when performing the uplink step 501, specifically: receiving a policy control rule or a QoS control rule sent by the PCF entity, and the SMF acquires the SDF level QoS according to the received policy control rule or the QoS control rule. Control information. Specifically, the PCF entity may transmit the PDU-CAN session modification command to the SMF entity and carry the policy control rule or QoS control rule in the PDU session modification instruction.
  • the SMF entity when performing the foregoing step 501, specifically acquires SDF level QoS control information according to a policy stored in the SMF entity.
  • the policy stored in the PCF entity or the policy stored by the SMF entity includes a basis for updating the SDF level QoS control information. For example, when the network load reaches the preset condition, the PCF entity or the SMF entity needs to update the SDF level QoS control information to ensure that the QoS of the important service is not affected.
  • the terminal performs QoS control on the uplink data packet, specifically: the terminal may determine the matching order of the SDF level packet filter according to the priority in the received SDF level QoS control information; The matching order of the SDF level packet filters performs packet matching, and performs QoS control according to the QoS flow corresponding to the matched packet filter.
  • Step 601 The PCF entity sends a request for modifying a PDU-Connectivity Access Network (PDU) session to the SMF entity, where the request includes a policy control rule.
  • PDU PDU-Connectivity Access Network
  • the QoS requirement may also be included in the request.
  • the policy control rule information is used to create a new policy control rule; or the policy control rule information is used to modify an existing policy control rule; or the policy control rule information is used to delete an existing policy. Control rules.
  • Step 602 After receiving the request to modify the PDU-CAN session, the SMF entity determines to perform a PDU session update process.
  • Step 603 The SMF entity sends a session management request to the AMF entity, where the session management request includes NAS layer signaling (for example, a PDU session modification command, where the PDU session modification command is used as an example), and the NAS layer signaling includes The above SDF level QoS control information, that is, SDF information.
  • NAS layer signaling for example, a PDU session modification command, where the PDU session modification command is used as an example
  • the NAS layer signaling includes The above SDF level QoS control information, that is, SDF information.
  • the SDF level QoS control information includes: a newly created SDF identifier (SDF ID), at least one packet filter corresponding to the SDF, priority, and QoS. parameter.
  • SDF ID SDF identifier
  • the format of the SDF level QoS control information may be: SDF ID, QoS Parameters, QFI, Precedence value, Filters.
  • the QoS control information of the SDF level includes the established QoS flow ID (QFI);
  • the QoS flow can satisfy the QoS requirement of the newly established SDF, and the SDF level QoS control information further includes the identifier QFI of the newly established QoS flow.
  • the QoS parameter may include 5QI. If the newly established QoS flow is GRB QoS flow, the QoS parameters may include 5QI, Notification, GFBR, and MFBR.
  • the SDF level QoS control information includes: the ID of the SDF to be modified; if the established QoS flow can satisfy the modification
  • the post-QoS requirement includes the QFI of the established QoS flow. If no established QoS flow can satisfy the modified QoS requirement, the QFI of the newly established QoS flow and the QoS parameter corresponding to the new QoS flow are included.
  • the format of the SDF level QoS control information may be: Update-SDF QoS: SDF ID, QFI QoS Parameters.
  • the QoS parameter may include 5QI. If the newly established QoS flow is GRB QoS flow, the QoS parameters may include 5QI, Notification, GFBR, and MFBR. The QoS parameters are optional.
  • the SDF level QoS control information includes: the ID of the SDF to be modified, and the corresponding priority after the modification. And/or the corresponding packet filter after modification.
  • the format of the SDF level QoS control information may be: Update-SDF Filters/precedence: SDF ID, Filters/Precedence value.
  • the SDF level QoS control information includes: the ID of the SDF to be deleted.
  • the format of the SDF level QoS control information may be: Delete-SDF: SDF ID, delete operation.
  • the session management request further includes QoS flow information, including QFI and QoS parameters, for indicating that the RAN/AN stores the QoS flow information. And establish corresponding air interface resources or bind QoS flow to existing air interface resources. If the SMF entity determines that the QoS flow needs to be deleted according to the received policy control rule, the AFI of the QoS flow is separately included in the session management request, and is used to indicate that the RAN/AN releases the air interface resource.
  • Step 604 The AMF sends an N2 session request message to the RAN/AN through the N2 interface, where the N2 session message includes NAS layer signaling (for example, a PDU session modification command, and the PDU session modification command is used as an example for description).
  • the NAS layer signaling includes the above SDF level QoS control information.
  • the N2 session request message further includes information that the RAN/AN needs to store the newly created QoS flow, establish a corresponding air interface resource with the terminal, or bind the newly created QoS flow to the existing If the QoS flow needs to be deleted, the N2 session request message further includes the RAN/AN deleting the corresponding QoS flow information, so that the ANRAN/AN releases the air interface resource with the terminal.
  • Step 605 The AN sends a radio resource control request to the terminal, where the request includes a PDU session modification command, where the PDU session modification command includes the SDF level QoS control information, so that the terminal performs uplink data packet according to the SDF level QoS control information. Perform QoS control or delete the corresponding SDF information.
  • Step 606 After receiving the SDF level QoS control information, the terminal returns an acknowledgement message to the AN.
  • the terminal stores the foregoing SDF level QoS control information, and performs QoS control on the uplink data packet according to the SDF level QoS control information. Or delete the locally stored SDF level QoS control information.
  • the form in which the SDF level QoS control information is stored on the terminal may be:
  • SDF ID1 Precedence value, QFI, Filters
  • SDF ID2 Precedence value, QFI, Filters
  • Step 607 The AN returns an N2 session response to the AMF through the N2 interface.
  • Step 608 The AMF returns a session management response to the SMF, where the response includes a PDU session modification confirmation message.
  • Step 609 The SMF sends an N4 session modification request to the UPF through the N4 interface, where the request optionally includes the foregoing SDF level QoS control information.
  • the UPF When the session modification request is used to add an SDF, the UPF generates at least one SDF level packet filter in the QoS flow corresponding to the added SDF according to the SDF level QoS control information, and generates at least one SDF level packet filter.
  • the priority is the same.
  • the UPF modifies the information of the SDF. For example, the priority of the existing SDF is modified, and the UPF modifies the priority of the packet filter corresponding to the SDF.
  • the UPF deletes the packet filter corresponding to the SDF and other information of the SDF.
  • Step 610 The UPF returns an N4 session modification response to the SMF through the N4 interface.
  • Step 611 The SMF returns a PDU-CAN session modification confirmation message to the PCF.
  • the QoS control information saved in the terminal and the UPF is modified, so that the terminal and the UPF can perform QoS control on the uplink and downlink data packets according to the same SDF level QoS control information.
  • the SMF may also initiate a process of modifying the SDF level QoS control information. That is, the above steps 601 and 611 may not be performed.
  • the uplink data packet is matched with the packet filter corresponding to the highest priority SDF according to the priority of each SDF level, and the uplink data packet is matched with the packet with the highest priority SDF. If the matching is successful, the uplink data packet is transmitted by using the QoS flow corresponding to the filter; otherwise, the uplink data packet is continued to be matched with the packet filter corresponding to the priority SDF until it matches the appropriate packet filter. until.
  • the UPF performs the data packet matching according to the same SDF level QoS control information. Therefore, the QoS flow corresponding to the data packet determined by the UPF is the same as the QoS flow determined by the terminal, thereby avoiding packet loss. .
  • Step 701 The PCF entity sends a modify PDU-CAN session modification request to the SMF entity, where the request includes a policy control rule.
  • the policy control rule information is used to create a new policy control rule; or the policy control rule information is used to modify an existing policy control rule; or the policy control rule information is used to delete an existing policy. Control rules.
  • Step 702 After receiving the request for modifying the PDU-CAN session, the SMF determines to perform a PDU session update process.
  • Step 703 The SMF sends a session management request to the AMF, where the session management request includes NAS layer signaling (for example, a PDU session modification command, where the PDU session modification command is used as an example), and the NAS layer signaling includes the foregoing SDF.
  • Level QoS control information that is, QoS flow information.
  • the SDF level QoS control information includes: a QFI of the newly created QoS flow, an ID of the SDF, a priority of the SDF, and a packet filter.
  • the SDF corresponding to the newly created QoS flow may be an existing SDF or a newly created SDF.
  • the format of the SDF level QoS control information may be: QFI, QoS parameters, SDF ID, Precedence value, Filters.
  • the QoS parameter may include 5QI.
  • the QoS parameters may include 5QI, Notification, GFBR, and MFBR.
  • the QoS parameters are optional.
  • the SDF level QoS control information includes: QFI of the QoS flow to be modified, ID of the SDF, priority of the SDF, and packet filter.
  • the modified SDF corresponding to the QoS flow may be added with a new SDF or the original SDF may be deleted. It is also possible to add neither the new SDF nor the original SDF, only the priority of the original SDF and/or the packet filter.
  • the format of the SDF level QoS control information may be: QFI, SDF ID, and Filters/Precedence value.
  • the SDF level QoS control information may include only the identifier of the QoS flow to be deleted.
  • the session management request further includes QoS flow information, including QFI and QoS parameters, for indicating that the RAN/AN stores the QoS flow information. And establish corresponding air interface resources or bind QoS flow to existing air interface resources. If the SMF entity determines that the QoS flow needs to be deleted according to the received policy control rule, the session management request further includes a QFI of the QoS flow, which is used to indicate that the RAN/AN releases the air interface resource.
  • Step 704 The AMF sends an N2 session request to the N2 interface, where the N2 session message includes NAS layer signaling (for example, a PDU session modification command, where the PDU session modification command is taken as an example), the NAS layer signaling
  • NAS layer signaling for example, a PDU session modification command, where the PDU session modification command is taken as an example
  • the N2 session request message further includes information that the RAN/AN needs to store the newly created QoS flow, establish a corresponding air interface resource with the terminal, or bind the newly created QoS flow to the existing one.
  • the N2 session request message further includes the RAN/AN deleting the corresponding QoS flow information, so that the ANRAN/AN releases the air interface resource with the terminal.
  • Step 705 The AN sends a radio resource control request to the terminal, where the request includes a PDU session modification command, where the PDU session modification command includes the SDF level QoS control information, so that the terminal performs uplink data packet according to the SDF level QoS control information. Perform QoS control or delete the corresponding QoS flow information.
  • Step 706 After receiving the SDF level QoS control information, the terminal returns an acknowledgement message to the AN.
  • the terminal stores the foregoing SDF level QoS control information, and performs QoS control on the uplink data packet according to the SDF level QoS control information. Or delete the locally stored SDF level QoS control information.
  • the form in which the SDF level QoS control information is stored on the terminal may be:
  • QFI 1 SDF ID 1, Precedence value, Filters
  • QFI 2 SDF ID 3, Precedence value, Filters
  • Step 707 The AN returns an N2 session response to the AMF through the N2 interface.
  • Step 708 The AMF returns a session management response to the SMF, where the response includes a PDU session modification confirmation message.
  • Step 709 The SMF sends an N4 session modification request to the UPF through the N4 interface, where the request optionally includes the foregoing SDF level QoS control information.
  • the UPF When the session modification request is used to add a QoS flow, the UPF generates at least one SDF level packet filter of the SDF corresponding to the QoS flow in the added QoS flow according to the foregoing SDF level QoS control information, and generates at least one SDF-level packet filters have the same priority.
  • the UPF modifies the information of the QoS flow.
  • the UPF deletes the QoS flow information.
  • Step 710 The UPF returns an N4 session modification response to the SMF through the N4 interface.
  • Step 711 The SMF returns a PDU-CAN modification confirmation message to the PCF.
  • the terminal and the UPF perform QoS control on the uplink and downlink data packets according to the same SDF level QoS control information.
  • the uplink data packet is matched with the packet filter corresponding to the highest priority SDF according to the priority of each SDF level, and the uplink data packet is matched with the packet with the highest priority SDF. If the matching is successful, the uplink data packet is transmitted by using the QoS flow corresponding to the filter; otherwise, the uplink data packet is continued to be matched with the packet filter corresponding to the priority SDF until it matches the appropriate packet filter. until.
  • the UPF performs the data packet matching according to the same SDF level QoS control information. Therefore, the QoS flow corresponding to the data packet determined by the UPF is the same as the QoS flow determined by the terminal, thereby avoiding packet loss. .
  • the SMF may also actively initiate a process of modifying the SDF level QoS control information, that is, the foregoing steps 701 and 711 may not be performed.
  • the SDF level QoS control information in Embodiment 2 and the SDF level QoS control information in Embodiment 1 are slightly different in the specific content and information format of the information, but the QoS control information in Embodiment 1 and Embodiment 2 are both Based on the SDF level, different SDFs correspond to different priorities. Therefore, in Embodiment 2, the process of controlling the QoS of the uplink and downlink packets by the terminal and the UPF is the same.
  • the uplink data packet is matched with the packet filter corresponding to the highest priority SDF according to the priority of each SDF level, and the uplink data packet is matched with the packet with the highest priority SDF. If the matching is successful, the uplink data packet is transmitted by using the QoS flow corresponding to the filter; otherwise, the uplink data packet is continued to be matched with the packet filter corresponding to the priority SDF until it matches the appropriate packet filter. until.
  • the UPF performs the matching of the data packet according to the same SDF level QoS control information. Therefore, the QoS flow corresponding to the data packet determined by the UPF is the same as the QoS flow determined by the terminal, thereby avoiding the loss of the packet. Elephant.
  • Step 801 The PCF sends a modify PDU-CAN session modification request to the SMF, where the request includes policy rule information.
  • the policy control rule information is used to create a new policy control rule; or the policy control rule information is used to modify an existing policy control rule; or the policy control rule information is used to delete an existing policy. Control rules.
  • Step 802 After receiving the request for modifying the PDU session, the SMF determines to perform a PDU session update process.
  • Step 803 The SMF sends a session management request to the AMF, where the session management request includes NAS layer signaling (for example, a PDU session modification command, where the PDU session modification command is used as an example), and the NAS layer signaling includes the foregoing SDF.
  • NAS layer signaling for example, a PDU session modification command, where the PDU session modification command is used as an example
  • Level QoS control information ie QoS rules.
  • the SDF level QoS control information includes: a newly created QoS rule identifier (QoS rule ID), a packet filter, a priority, a QFI, and a QoS parameter.
  • the format of the SDF level QoS control information may be: QoS rule ID, QFI, QoS parameters, Precedence value, Filters. If there is an existing QoS flow that can meet the QoS requirements of the newly created QoS rule, the QFI is the QFI of the existing QoS flow. If the existing QoS flow does not meet the QoS requirement of the newly created QoS rule, it is required.
  • the QFI is the QFI of the newly created QoS flow. Further, if the newly established QoS flow is non-GRB QoS flow, the QoS parameter may include 5QI. If the newly established QoS flow is GRB QoS flow, the QoS parameters may include 5QI, Notification, GFBR, and MFBR. , where the QoS parameters are optional
  • the SDF level QoS control information includes: the QoS rule ID to be modified; if the established QoS flow can satisfy the modified QoS The requirement includes the QFI of the established QoS flow. If no established QoS flow can satisfy the modified QoS requirement, the QFI of the newly established QoS flow and the QoS parameter corresponding to the new QoS flow are included.
  • the format of the SDF level QoS control information may be: QoS rule ID, QoS flow ID, QoS parameters.
  • the SDF level QoS control information includes: the QoS rule ID to be modified, and the corresponding priority after the modification. Level and / or modified corresponding packet filter.
  • the SDF level QoS control information includes: the ID of the SDF to be deleted.
  • the session management request further includes QoS flow information, including QFI and QoS parameters, for indicating that the RAN/AN stores the QoS flow information. And establish corresponding air interface resources or bind QoS flow to existing air interface resources. If the SMF entity determines that the QoS flow needs to be deleted according to the received policy control rule, the session management request further includes a QFI of the QoS flow, which is used to indicate that the RAN/AN releases the air interface resource.
  • Step 804 The AMF sends an N2 session request to the RAN/AN through the N2 interface, where the N2 session message includes NAS layer signaling (for example, a PDU session modification command, where the PDU session modification command is taken as an example), the NAS
  • the layer signaling includes the above SDF level QoS control information.
  • the N2 session request message further includes information that the RAN/AN needs to store the newly created QoS flow, establish a corresponding air interface resource with the terminal, or bind the newly created QoS flow to the existing On the air interface resources. If the QoS flow needs to be deleted, the N2 session request message further includes the RAN/AN deleting the corresponding QoS flow information, so that the RAN/AN releases the air interface resource with the terminal.
  • Step 805 The AN sends a radio resource control request to the terminal, where the request includes a PDU session modification command, where the PDU session modification command includes the SDF level QoS control information, so that the terminal performs uplink data packet according to the SDF level QoS control information. Perform QoS control or delete the information of the corresponding QoS rule.
  • Step 806 After receiving the SDF level QoS control information, the terminal returns an acknowledgement message to the AN.
  • the terminal stores the foregoing SDF level QoS control information, and performs QoS control on the uplink data packet according to the SDF level QoS control information. Or delete the locally stored SDF level QoS control information.
  • the form in which the SDF level QoS control information is stored on the terminal may be:
  • QoS Rule ID2 Precedence value, QFI, Filters
  • Step 807 The AN returns an N2 session response to the AMF through the N2 interface.
  • Step 808 The AMF returns a session management response to the SMF, where the response includes a PDU session modification confirmation message.
  • Step 809 The SMF sends an N4 session modification request to the UPF through the N4 interface, where the request optionally includes the foregoing SDF level QoS control information.
  • the UPF When the session modification request is used to add a QoS rule, the UPF generates at least one SDF level packet filter of the SDF corresponding to the QoS flow in the QoS flow corresponding to the added QoS according to the SDF level QoS control information, and generates At least one SDF level packet filter has the same priority.
  • the UPF modifies the information of the QoS rule.
  • the UPF When a session modification request is used to delete an existing QoS rule, the UPF deletes all the information of the QoS rule.
  • Step 810 The UPF returns an N4 session modification response to the SMF through the N4 interface.
  • Step 811 The SMF returns a PDU-CAN modification confirmation message to the PCF.
  • the terminal and the UPF perform QoS control on the uplink and downlink data packets according to the same SDF level QoS control information.
  • the uplink data packet is matched with the packet filter corresponding to the highest priority SDF according to the priority of each SDF level, and the uplink data packet is matched with the packet with the highest priority SDF. If the matching is successful, the uplink data packet is transmitted by using the QoS flow corresponding to the filter; otherwise, the uplink data packet is continued to be matched with the packet filter corresponding to the priority SDF until it matches the appropriate packet filter. until.
  • the UPF performs the data packet matching according to the same SDF level QoS control information. Therefore, the QoS flow corresponding to the data packet determined by the UPF is the same as the QoS flow determined by the terminal, thereby avoiding packet loss. .
  • the SMF may also actively initiate a process of modifying the SDF level QoS control information, that is, the foregoing steps 801 and 811 may not be performed.
  • Embodiment 3 and the SDF level QoS control information in Embodiment 1 and Embodiment 2 are slightly different in the specific content and information format of the information, but Embodiment 1, Embodiment 2, and Embodiment
  • the QoS control information in 3 is implemented based on the SDF level, and different SDFs correspond to different priorities. Therefore, in the embodiment 3, the process of controlling the QoS of the uplink and downlink data packets by the terminal and the UPF is the same, and details are not described herein again.
  • FIG. 9 is a schematic diagram showing a possible structure of a session management function SMF entity involved in the foregoing embodiment, and the SMF entity 900 can also implement the SMF entity shown in FIG. 5, FIG. 6, FIG. 7, or FIG. Features.
  • the SMF entity 900 includes a processing unit 902 and a communication unit 903.
  • the processing unit 902 is configured to perform control management on the actions of the SMF entity.
  • the processing unit 902 is configured to support the SMF entity to perform the processes 501-503 in FIG. 5; the processes 602, 603, and 609 in FIG. 6; 702, 703, and 709; or processes 802, 803, and 809 in FIG. 8; and/or other processes for the techniques described herein.
  • the communication unit 903 is configured to support communication between the SMF entity and other network entities, such as communication with the functional modules or network entities shown in FIG. 5, FIG. 6, FIG. 7, or FIG.
  • the SMF entity may also include a storage unit 901 for storing program code and data of the SMF entity.
  • each functional unit in the embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the first obtaining unit and the second obtaining unit may be the same unit and different units.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the processing unit 902 can be a processor or a controller, and can be, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific). Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication unit 903 can be a transceiver.
  • the storage unit 901 can be a memory.
  • the SMF entity involved in the embodiment of the present invention may be the SMF entity shown in FIG.
  • FIG. 10 shows another possible structural diagram of the SMF entity involved in the foregoing embodiment, including: a processor 1001 and a memory 1002 and a transceiver 1003 respectively connected to the processor 1001.
  • the processor 1001 is configured to execute a computer program pre-stored in the memory 1002 to execute:
  • the SDF level QoS control information is sent to the terminal through the transceiver 1003.
  • the processor 1001 is further configured to: send, by the transceiver 1003, the SDF level QoS control information to the UPF entity, so that the UPF verifies the uplink data packet according to the SDF level QoS control information. QoS control, or deleting the SDF level QoS control information.
  • the processor 1001 when acquiring the SDF level QoS control information, is specifically configured to: obtain the SDF level QoS control information according to the session management request sent by the PCF entity; or obtain the SDF level QoS according to the local policy. Control information.
  • the SDF level QoS control information includes: an identifier of the SDF; or an identifier of the SDF, and at least one or combination of the following: at least one packet filter corresponding to the SDF, priority, QoS flow identification, QoS parameters.
  • the SDF level QoS control information includes: an identifier of the QoS flow; or an identifier of the QoS flow, and at least one or a combination of: an identifier of the at least one SDF, corresponding to the at least one SDF At least one packet filter, a priority corresponding to the at least one SDF, and a QoS parameter corresponding to the QoS flow.
  • the SDF level QoS control information includes: an identifier of the QoS rule; or an identifier of the QoS rule, and at least one or a combination of: at least one packet filter corresponding to the QoS rule, Priority, QoS flow identification, QoS parameters.
  • the processor 1001 is further configured to: send, by the transceiver 1003, an identifier of the QoS flow and a QoS parameter corresponding to the QoS flow to the access network device, so that the access network device establishes a corresponding Air interface resources.
  • FIG. 11 is a schematic diagram showing a possible structure of a terminal involved in the foregoing embodiment, and the terminal 1100 can also implement the functions of the terminal shown in FIG. 6, FIG. 7, or FIG.
  • the terminal 1100 includes a processing unit 1102 and a communication unit 1103.
  • the processing unit 1102 is configured to control and manage the actions of the terminal.
  • the processing unit 1102 is configured to support the terminal to perform the process 606 in FIG. 6, the process 706 in FIG. 7, the process 806 in FIG. 8, and/or Other processes of the described techniques.
  • the communication unit 1103 is for supporting communication between the terminal and other network entities, such as communication with the functional modules or network entities shown in FIG. 6, FIG. 7, or FIG.
  • the terminal may further include a storage unit 1101 for storing program codes and data of the terminal.
  • each functional unit in the embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the first obtaining unit and the second obtaining unit may be the same unit and different units.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the processing unit 1102 may be a processor or a controller, and may be, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific). Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication unit 1103 can be a transceiver.
  • the storage unit 1101 may be a memory.
  • the terminal involved in the embodiment of the present invention may be the terminal shown in FIG.
  • FIG. 12 shows another possible structural diagram of the terminal involved in the foregoing embodiment, including: a processor 1201 and a memory 1202 and a transceiver 1203 respectively connected to the processor 1201.
  • the processor 1201 is configured to invoke a computer program pre-stored in the memory 1202 to execute:
  • the uplink data packet is subjected to SDF level QoS control, or the SDF level QoS control information is deleted.
  • the SDF level QoS control information includes: an identifier of the SDF; or an identifier of the SDF, and one or a combination of the following: at least one packet filter, priority, and QoS corresponding to the SDF. Flow identification and QoS parameters.
  • the SDF level QoS control information includes: an identifier of the QoS flow; or an identifier of the QoS flow, and at least one or a combination of: an identifier of the at least one SDF, corresponding to the at least one SDF At least one packet filter, a priority corresponding to the at least one SDF, corresponding to the QoS flow QoS parameters.
  • the SDF level QoS control information includes: an identifier of the QoS rule; or an identifier of the QoS rule, and at least one or a combination of: at least one packet filter corresponding to the QoS rule, Priority, QoS flow identification and QoS parameters.
  • the processor 1201 when performing QoS control on the uplink data packet according to the SDF level QoS control information, is specifically configured to: determine the SDF level according to the priority in the SDF level QoS control information. Matching order of the packet filters; performing packet matching according to the matching order of the SDF level packet filters, and performing QoS control according to the QoS flows corresponding to the successfully matched packet filters.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种QoS控制方法及设备。在该方法中，会话管理功能SMF实体获取服务数据流SDF级别QoS控制信息；所述SMF实体发送所述SDF级别QoS控制信息给终端；终端根据所述SDF级别QoS控制信息，对上行数据包进行QoS控制，或者删除所述SDF级别QoS控制信息。通过上述方法实施例，使得终端能够根据SDF级别QoS控制信息对上行数据包进行QoS控制。

Description

一种QoS控制方法及设备 技术领域
本申请涉及通信技术领域，尤其涉及一种QoS(Quality of service，服务质量)控制方法及设备。
背景技术
无线网络已被越来越多的人或机器使用，越来越多的业务在无线网络上承载。对于无线网络中的各种业务，例如通话、电话会议、紧急呼叫、公共预警等，都有其各自明确的业务保障需求。
由于无线资源的有限性，若在同一时间需要处理的业务较多，则需要根据各业务的QoS规则、优先级来控制接入、资源调度等。例如，用户A正在通话时，用户B开始下载一个文件，由于无线资源有限，若用户B的下载业务抢占了用户A通话业务的无线资源，则会造成非常糟糕的用户体验，因此，需要为通话业务设置一个比下载业务高的优先级，以保证在无线资源不足时，优先保证通话业务的无线资源调度。
具体的，QoS架构可以如图1所示，一个终端，可以与5G核心网建立一个或者多个PDU(Packet Data Unit，分组数据单元)会话，RAN(Radio Access Network，无线接入网)为每一个PDU会话建立一个或者多个数据无线承载(Data Radio Bearer，DRB)，一个DRB中包含有一个或多个QoS flow，每个QoS flow对应一个或多个Packet Filter(包过滤器)。例如，QoS flow1对应包过滤器1和包过滤器2，那么只有能够通过包过滤器1或包过滤器2的数据包可以通过QoS flow1进行传输。此外，一个QoS flow对应一组QoS参数，使用同一QoS flow传输的数据包，QoS处理相同。
不同的业务对应不同的SDF(Service Data Flow，服务数据包流)，一个SDF可以对应一个或多个包过滤器或者一个应用检测过滤器。例如，业务1对应SDF1，而SDF1对应包过滤器3和包过滤器4，那么属于业务1的数据包能够通过包过滤器3或包过滤器4。
由于在终端侧和网络侧对上、下行数据包进行QoS控制时，即将上、下行数据包映射到QoS flow上时，映射规则不同，因此，在一些特殊的情况下，可能会发生终端侧和网络将上、下行数据包映射到不同的QoS flow上，导致丢包的情况。
发明内容
本申请实施例提供了一种QoS控制方法及设备，用以对上行数据包进行QoS控制。
第一方面，本申请实施例提供的一种QoS控制方法，包括：
会话管理功能SMF实体获取服务数据流SDF级别QoS控制信息；
所述SMF实体发送所述SDF级别QoS控制信息给终端。
在一种可能的实现方式中，所述SMF实体发送所述SDF级别QoS控制信息给用户面功能UPF实体，以使所述UPF根据所述SDF级别QoS控制信息验证上行数据包的QoS控制，或者删除所述SDF级别QoS控制信息。
在一种可能的实现方式中，所述SMF实体获取SDF级别QoS控制信息，包括：所述SMF 实体根据策略控制功能PCF实体发送的会话管理请求获取SDF级别QoS控制信息；或者，所述SMF实体根据本地策略获取SDF级别QoS控制信息。
在一种可能的实现方式中，所述SDF级别QoS控制信息，包括：SDF的标识；或者，SDF的标识，以及与以下至少一种或组合：所述SDF对应的至少一个包过滤器、优先级、QoS flow的标识、QoS参数。
在一种可能的实现方式中，所述SDF级别QoS控制信息，包括：QoS flow的标识；或者，QoS flow的标识，以及以下至少一种或组合：至少一个SDF的标识、与所述至少一个SDF对应的至少一个包过滤器、与所述至少一个SDF对应的优先级、与所述QoS flow对应的QoS参数。
在一种可能的实现方式中，所述SDF级别QoS控制信息，包括：QoS规则的标识；或者，QoS规则的标识，以及以下至少一种或组合：与所述QoS规则对应的至少一个包过滤器、优先级、QoS flow的标识、QoS参数。
在一种可能的实现方式中，所述方法还包括：
所述SMF实体向接入网设备发送QoS flow的标识或者QoS flow的标识和与所述QoS flow对应的QoS参数，以使接入网设备建立，释放或者绑定到对应的空口资源。
第二方面，本申请实施例提供的一种QoS控制方法，包括：
终端接收会话管理功能SMF实体发送的服务数据流SDF级别QoS控制信息；
终端根据所述SDF级别QoS控制信息，对上行数据包进行QoS控制，或者删除所述SDF级别QoS控制信息。
在一种可能的实现方式中，所述SDF级别QoS控制信息，包括：SDF的标识；或者，SDF的标识，以及以下一种或组合：与所述SDF对应的至少一个包过滤器、优先级、QoS flow的标识和QoS参数。
在一种可能的实现方式中，所述SDF级别QoS控制信息，包括：QoS flow的标识；或者，QoS flow的标识，以及以下至少一种或组合：至少一个SDF的标识、与所述至少一个SDF对应的至少一个包过滤器、与所述至少一个SDF对应的优先级、与所述QoS flow对应的QoS参数。
在一种可能的实现方式中，所述SDF级别QoS控制信息，包括：QoS规则的标识；或者，QoS规则的标识，以及以下至少一种或组合：与所述QoS规则对应的至少一个包过滤器、优先级、QoS flow的标识和QoS参数。
在一种可能的实现方式中，终端根据所述SDF级别QoS控制信息，对上行数据包执行Qos控制，包括：所述终端根据所述SDF级别QoS控制信息中的优先级，确定SDF级别包过滤器的匹配顺序；所述终端根据所述SDF级别包过滤器的匹配顺序执行数据包匹配，并根据匹配成功的包过滤器对应的QoS flow执行QoS控制。
第三方面，本发明实施例提供一种会话管理功能SMF实体，该会话管理功能SMF实体具有实现上述方法示例中会话管理功能SMF实体的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，会话管理功能SMF实体的结构中包括处理单元和通信单元，所述处理单元被配置为支持会话管理功能SMF实体执行上述方法中相应的功能。所述通信单元用于支持会话管理功能SMF实体与其他设备之间的通信。所述会话管理功能SMF实体还 可以包括存储单元，所述存储单元用于与处理单元耦合，其保存会话管理功能SMF实体必要的程序指令和数据。
作为示例，处理单元可以为处理器，通信单元可以为收发器，存储单元可以为存储器。
第四方面，本申请实施例提供的一种会话管理功能SMF实体，包括：
处理器以及分别与所述处理器连接的存储器和收发机；
所述处理器，用于调用所述存储器中预先存储的计算机程序执行：
获取服务数据流SDF级别QoS控制信息；
通过所述收发器发送所述SDF级别QoS控制信息给终端。
在一种可能的实现方式中，所述处理器还用于：通过所述收发器发送所述SDF级别QoS控制信息给用户面功能UPF实体，以使所述UPF根据所述SDF级别QoS控制信息验证上行数据包的QoS控制，或者删除所述SDF级别QoS控制信息。
在一种可能的实现方式中，所述处理器在获取SDF级别QoS控制信息时，具体用于：根据策略控制功能PCF实体发送的会话管理请求获取SDF级别QoS控制信息；或者，根据本地策略获取SDF级别QoS控制信息。
在一种可能的实现方式中，所述SDF级别QoS控制信息，包括：SDF的标识；或者，SDF的标识，以及与以下至少一种或组合：所述SDF对应的至少一个包过滤器、优先级、QoS flow的标识、QoS参数。
在一种可能的实现方式中，所述SDF级别QoS控制信息，包括：QoS flow的标识；或者，QoS flow的标识，以及以下至少一种或组合：至少一个SDF的标识、与所述至少一个SDF对应的至少一个包过滤器、与所述至少一个SDF对应的优先级、与所述QoS flow对应的QoS参数。
在一种可能的实现方式中，所述SDF级别QoS控制信息，包括：QoS规则的标识；或者，QoS规则的标识，以及以下至少一种或组合：与所述QoS规则对应的至少一个包过滤器、优先级、QoS flow的标识、QoS参数。
在一种可能的实现方式中，所述处理器还用于：
通过所述收发器向接入网设备发送QoS flow标识或者QoS flow的标识和与所述QoS flow对应的QoS参数，以使接入网设备建立释放或者绑定到对应的空口资源。
第五方面，本发明实施例提供一种终端，该终端具有实现上述方法示例中终端行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，终端的结构中包括处理单元和通信单元，所述处理单元被配置为支持终端执行上述方法中相应的功能。所述通信单元用于支持终端与其他设备之间的通信。所述终端还可以包括存储单元，所述存储单元用于与处理单元耦合，其保存终端必要的程序指令和数据。
作为示例，处理单元可以为处理器，通信单元可以为收发器，存储单元可以为存储器。
第六方面，本申请实施例提供的一种终端，包括：处理器以及分别与所述处理器连接的存储器和收发机；
所述处理器，用于调用所述存储器中预先存储的计算机程序执行：
通过所述收发器接收会话管理功能SMF实体发送的服务数据流SDF级别QoS控制信息；
根据所述SDF级别QoS控制信息，对上行数据包进行QoS控制，或者删除所述SDF级别QoS控制信息。
在一种可能的实现方式中，所述SDF级别QoS控制信息，包括：SDF的标识；或者，SDF的标识，以及以下一种或组合：与所述SDF对应的至少一个包过滤器、优先级、QoS flow的标识和QoS参数。
在一种可能的实现方式中，所述SDF级别QoS控制信息，包括：
QoS flow的标识；或者
QoS flow的标识，以及以下至少一种或组合：至少一个SDF的标识、与所述至少一个SDF对应的至少一个包过滤器、与所述至少一个SDF对应的优先级、与所述QoS flow对应的QoS参数。
在一种可能的实现方式中，所述SDF级别QoS控制信息，包括：QoS规则的标识；或者，QoS规则的标识，以及以下至少一种或组合：与所述QoS规则对应的至少一个包过滤器、优先级、QoS flow的标识和QoS参数。
在一种可能的实现方式中，所述处理器还用于根据所述SDF级别QoS控制信息中的优先级，确定SDF级别包过滤器的匹配顺序；所述终端根据所述SDF级别包过滤器的匹配顺序执行数据包匹配，并根据匹配成功的包过滤器对应的QoS flow执行QoS控制。
第七方面，本发明实施例提供了一种通信系统，该系统包括上述方面的会话管理功能SMF实体。在另一种可能的设计中，该系统还可以包括本发明实施例提供的方案中与该会话管理功能SMF实体进行交互的其他设备，例如PCF，UPE，或者终端设备。
第八方面，本发明实施例提供了一种计算机存储介质，用于储存为上述会话管理功能SMF实体所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
第九方面，本发明实施例提供了一种计算机存储介质，用于储存为上述终端所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
第十方面，本申请还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
附图说明
图1为本申请实施例提供的QoS架构示意图；
图2为本申请实施例提供的将上/下行数据包映射到QoS flow上的示意图；
图3为本申请实施例提供的上/下行数据包映射到QoS flow上时发生匹配错误的示意图；
图4为本申请实施例提供的一种可适用本申请实施例的系统架构示意图；
图5为本申请实施例提供的一种QoS控制方法流程示意图；
图6为本申请实施例提供的具体实施例之一的流程示意图；
图7为本申请实施例提供的具体实施例之二的流程示意图；
图8为本申请实施例提供的具体实施例之三的流程示意图；
图9为本申请实施例提供的SMF实体的结构示意图之一；
图10为本申请实施例提供的SMF实体的结构示意图之二；
图11为本申请实施例提供的终端的结构示意图之一；
图12为本申请实施例提供的终端的结构示意图之二。
具体实施方式
下面将结合附图对本申请实施例作进一步地详细描述。
申请人在研究时发现，现有技术中的终端和网络侧设备在对上、下行数据包进行QoS控制时，存在下述问题：
终端的NAS层(非接入层)和网络侧的UPF(User Plane Function，用户面功能)基于Packet Filter(包过滤器)将上下行数据包映射到一个QoS flow上；终端的AS层(接入层)和RAN将上下行的QoS flow关联到一个DRB上。终端侧和网络侧的UPF在将数据包映射到QoS flow上时，具体的映射机制可以如图2所示，具体如下：
终端侧：对于终端来说，每个QoS flow对应一个QoS flow的模板，每个QoS flow模板对应一个或多个包过滤器，且每个QoS flow模板具有一个优先级。当终端发送一个数据包时，将数据包与各QoS flow模板，按照优先级从高到低依次执行QoS flow模板的匹配，匹配到相应的QoS flow模板时，则停止匹配。具体地，数据包首先与优先级最高的QoS flow模板进行匹配，若该数据包能够通过该QoS flow模板对应的任一包过滤器，即匹配成功，该数据包使用该QoS flow模板对应的QoS flow进行传输，否则，继续与优先级较低的QoS flow模板进行匹配，直到匹配到相应的QoS flow模板。
网络侧：对于UPF来说，每种SDF对应一个或多个包过滤器，每个SDF对应一个优先级。当网络设备发送一个数据包时，按照各SDF的优先级，将数据包依次与SDF的包过滤器进行匹配，匹配到相应SDF的包过滤器时，则停止匹配。具体地，数据包首先与优先级最高的SDF的包过滤器进行匹配，若该数据包能够通过该SDF的包过滤器，即匹配成功，该数据包则通过该SDF的包过滤器对应的QoS flow进行传输，否则，继续与优先级较低的SDF的包过滤器进行匹配。
上述机制中，终端侧与网络侧使用不同的匹配规则执行数据包的匹配，使得同一个数据包在终端侧和网络侧中可能匹配到不同的QoS flow，进而导致丢包，具体可如图3所示：当一个终端要传输一个数据包时，若该数据包既能与SDF a的包过滤器匹配又能和SDF b的包过滤器匹配，由于匹配优先级的不同，在终端侧，上行数据包会被匹配到QoS flow1，而在网络侧，该数据包会被匹配到QoS flow2中。在上行数据传输时，网络侧会验证终端发送的数据包是否使用了正确的QoS flow，若网络侧判断终端使用的是错误的QoS flow，那么网络侧将丢弃该数据包。
为了解决上述技术问题，本申请实施例提供了一种QoS控制方法及设备。
本申请所涉及到的终端可以包括具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备，以及各种形式的UE(User Equipment，用户设备)，MS(Mobile Station，移动台)，终端设备(Terminal Equipment)等等。
本申请实施例提供的QoS控制方法可以应用于如图4所示的5G网络架构中，其中：
UPF(User Plane Function，用户面功能)，其主要功能包含：数据包路由和传输、包检测、业务用量上报、QoS处理、合法监听、上行包检测、下行数据包存储等用户面相关的功能。
AMF(Access and Mobility Management Function，接入和移动管理功能)，主要功 能包含：连接管理、移动性管理、注册管理、接入认证和授权、可达性管理、安全上下文管理等接入和移动性相关的功能。
SMF(Session Management function，会话管理功能)，其主要功能包含：会话管理(如会话建立、修改和释放，包含UPF和AN之间的隧道维护)、UPF的选择和控制、SSC(Service and Session Continuity，业务和会话连续性)模式选择、漫游等会话相关的功能。
PCF(Policy Control Function，策略控制功能)，其主要功能包含：统一策略制定、策略控制的提供和从UDR中获取策略决策相关的签约信息等策略相关的功能。
AUSF(Authentication Server Function，认证服务器功能)，其主要功能包含：认证用户设备是否合法。
AF(Application function，应用功能)，其驻主要功能，提供服务。具体的包含，业务路由、接入网能力开放，与策略架构交互。
UDM(Unified Data Management，统一数据管理)，其主要功能是信任状，位置和签约管理，存储用户的签约数据。
DN(Data Network，数据网络)，其主要功能是提供具体的数据业务，如运营商服务，互联网接入或者第三方业务。
当然，图4所示的仅为本申请实施例应用场景的一个示例，并不对本申请实施例的应用场景构成限定，可适用于本申请实施例的系统架构，可以包括比图4所示的更多或更少的网元，或者不同的系统架构，例如EPS系统架构或者CUPS架构中。
参见图5，为本申请实施例提供的一种QoS控制方法的流程示意图，如图所述，该方法包括如下步骤：
步骤501、SMF实体获取SDF级别QoS控制信息。
步骤502、SMF实体将SDF级别QoS控制信息发送给终端。
步骤503、终端根据接收到SDF级别QoS控制信息，对上行数据包进行QoS控制，或者删除上述SDF级别QoS控制信息。
在上述实施例中，SMF实体获取到的SDF级别QoS控制信息，用于对SDF的QoS执行控制，SMF实体将SDF级别QoS控制信息发送给终端，以使终端对上行数据包进行QoS控制。
在上述任一种可能的实现方式中，SDF级别QoS控制信息，表示一个SDF对应的至少一个包过滤器对应同一个QoS flow，即对应相同的QoS参数，且各包过滤器SDF级别的优先级相同。但不同的SDF对应的优先级不同。不同的SDF对应的QoS参数可以相同，即可以对应同一个QoS flow，但各自对应的包过滤器之间的优先级不同。
可以理解的是，SDF级别QoS控制信息包括以下一种或组合：SDF级别的标识、至少一个SDF级别包过滤器、SDF级别的优先级(即，也是SDF级别包过滤器的优先级)、QoS flow的标识，QoS参数。其中，SDF级别的标识表现形式可以是多种，例如SDF的标识(SDF ID)，QoS规则ID，或者其他可以体现SDF级别的各种形式的标识。
同理，在本申请实施例中，SMF实体获取到的SDF级别QoS控制信息的具体表现方式是多种多样的，包括以下三种方式但不限于此：
在本申请实施例中，SMF实体获取到的QoS控制信息虽然是SDF级别的，但其表现方式是多种多样的。
方式一：以SDF作为控制单位
在该方式中，SDF级别QoS控制信可以包括以下一种或组合：SDF的标识、与SDF对应的至少一个包过滤器、优先级、QoS flow的标识、QoS参数。
具体地，可以包括以下3种场景：
场景1、增加一个新的SDF
此时，SMF实体获取到的SDF级别QoS控制信息中包括新增加的SDF的标识，
包过滤器：与SDF对应的至少一个包过滤器；
优先级：SDF对应的优先级，即上述包过滤器的优先级；
QoS flow的标识：与SDF对应的QoS flow，即属于该SDF的数据包通过该QoS flow进行传输；
可选的，包含QoS参数：与QoS flow对应的QoS参数，例如：包延时、比特率、丢包率等参数。
进一步地，若该QoS flow为non-GBR QoS flow(非保证比特速率的QoS flow)，QoS参数中还可以包括5QI(5G QoS Indicator，5G QoS指示)；若QoS flow为GBR QoS flow(保证比特速率的QoS flow)，QoS参数中可以包括5QI、Notification(通知)、GFBR(Guaranteed Flow Bit Rate，保证流比特率)和MFBR(Maximum Flow Bit Rate，最大流比特率)。
场景2、修改已有的SDF
此时，SMF实体获取到的SDF级别QoS控制信息中至少包括待修改的SDF的标识，此外，还包括以下信息中的一种或组合：
包过滤器：与该SDF对应的至少一个包过滤器，或者待删除的与该SDF对应的至少一包过滤器；或者更新后的SDF对应的至少一个包过滤器。
优先级：该SDF对应的修改后的优先级；
QoS flow的标识：该SDF对应的修改后的QoS flow的标识；
QoS参数：该SDF对应的修改后的QoS参数。
进一步地，若修改后的QoS flow为non-GBR QoS flow，QoS参数中还可以包括5QI；若QoS flow为GBR QoS flow，QoS参数中可以包括5QI、Notification、GFBR和MFBR。
场景3、删除已有的SDF
此时，SMF实体获取到的SDF级别QoS控制信息中可以仅包括待删除的SDF的标识。
方式二：以QoS flow中的SDF作为控制单位
在该方式中，SDF级别QoS控制信息可以包括以下一种或组合：QoS flow的标识、至少一个SDF的标识、与至少一个SDF对应的至少一个包过滤器、与至少一个SDF对应的优先级、与QoS flow对应的QoS参数。
具体地，以QoS flow作为QoS控制的单位，也可以包括以下3种场景：
场景1、新建一个QoS flow
此时，SMF实体获取到的SDF级别QoS控制信息中包括新建的QoS flow的标识，此外，还可以包括：
SDF的标识：与新建的QoS flow对应的至少一个SDF的标识；例如与增加的QoS flow对应的SDF 1的标识和SDF 2的标识；
包过滤器：与上述每个SDF对应的至少一个包过滤器；例如，与SDF 1对应的包过滤 器1、包过滤器2，与SDF 2对应的包过滤器3、包过滤器4；
优先级：与上述每个SDF对应的优先级；
可选的包含QoS参数：与新建的QoS flow对应的QoS参数。
进一步地，若新建的QoS flow为non-GBR QoS flow，QoS参数中还可以包括5QI；若新建的QoS flow为GBR QoS flow，QoS参数中可以包括5QI、Notification、GFBR和MFBR。
场景2、修改已有的QoS flow
此时，SMF实体获取到的QoS控制信息中至少包括待修改的QoS flow的标识，此外，还包括以下信息中的一种或组合：
SDF的标识，待增加的与该QoS flow对应的SDF的标识，或者待修改的与该QoS flow对应的SDF的标识，或者待删除的与该QoS flow对应的SDF的标识；
包过滤器：若增加了与该QoS flow对应的SDF，则包括与增加的SDF对应的至少一个包过滤器；若修改了已有的与该QoS flow对应的SDF 1对应的包过滤器，则包括待增加的与SDF 1对应的至少一个包过滤器，或者待删除的与SDF 1对应的至少一个包过滤器，或者待修改的SDF对应的修改后的至少一个包过滤器；
优先级：若增加了与该QoS flow对应的SDF，则包括与待增加SDF对应的优先级；若修改了与该QoS flow对应的某个SDF的优先级，则包括；该SDF对应的修改后的优先级；
QoS参数：该QoS flow对应的修改后的QoS参数。
进一步地，若修改的QoS flow为non-GBR QoS flow，QoS参数中还可以包括5QI；若修改的QoS flow为GBR QoS flow，QoS参数中可以包括5QI、Notification、GFBR和MFBR。
场景3、删除已有的QoS flow
此时，SMF实体获取到的SDF级别QoS控制信息中可以包括待删除的QoS flow的标识。
方式三：以QoS规则作为控制单位
在该方式中，一个QoS规则，与一个SDF对应。SDF级别QoS控制信息可以包括以下一种或组合：QoS规则的标识、与QoS规则对应的至少一个包过滤器、优先级、QoS flow的标识、QoS参数。
具体地，以QoS规则作为QoS控制单位，也可以包括以下3种场景：
场景1、增加一个QoS规则
此时，SMF实体获取到的SDF级别QoS控制信息中包括新增加的QoS规则的标识，此外，还包括以下信息：
包过滤器：与增加的QoS规则对应的至少一个包过滤器；
优先级：与增加的QoS规则对应的优先级，即上述包过滤器的优先级；
QoS flow的标识：与增加的QoS规则对应的QoS flow的标识；
可选的包含QoS参数：与QoS flow对应的QoS参数。
进一步地，若与增加的QoS规则对应的QoS flow为non-GBR QoS flow，QoS参数中还可以包括5QI；若与增加的QoS规则对应的QoS flow为GBR QoS flow，QoS参数中可以包括5QI、Notification、GFBR和MFBR。
场景2、修改已有的QoS规则
此时，SMF实体获取到的SDF级别QoS控制信息中至少包括待修改的QoS规则的标识，此外，还包括以下信息中的一种或组合：
包过滤器：待增加的与该QoS规则对应的至少一个包过滤器，或者待删除的与该QoS 规则对应的至少一个包过滤器，或者修改后的与该QoS规则对应的至少一个包过滤器；
优先级：与该QoS规则对应的修改后优先级；
QoS flow的标识：与该QoS规则对应的修改后的QoS flow的标识；
QoS参数：与该修改后的QoS flow对应的修改后的QoS参数。
进一步地，若修改后的QoS flow为non-GBR QoS flow，QoS参数中还可以包括5QI；若修改后的QoS flow为GBR QoS flow，QoS参数中可以包括5QI、Notification、GFBR和MFBR。
场景3、删除已有的QoS规则
此时，SMF实体获取到的SDF级别QoS控制信息中可以仅包括待删除的QoS规则的标识。
在具体实施时，可以根据具体的应用需要，选择上述三种方式之一，将SDF级别QoS控制信息发送给终端，以使终端根据SDF级别QoS控制信息对上行数据包进行QoS控制。
在一种可能的实现方式中，SMF实体还可以将上述SDF级别QoS控制信息发送给UPF实体，以使UPF实体根据SDF级别QoS控制信息验证上行数据包的QoS控制。
由于SMF实体将SDF级别QoS控制信息发送给终端和UPF实体，能够使得终端和UPF基于相同的QoS控制信息分别对上行数据包进行QoS控制，避免了由于终端和UPF对上行数据的QoS控制不同，而导致丢包的现象。
在一些实施例中，SMF实体还可以向接入网设备发送以下两种信息：一，QoS flow标识，或者二，QoS flow的标识以及QoS flow对应的QoS参数，以使接入网设备根据上述信息建立，删除，或者绑定到对应的空口资源。
在一种可能的实现方式中，SMF实体在执行上行步骤501时，具体为：接收PCF实体发送的策略控制规则或QoS控制规则，SMF根据接收到的策略控制规则或QoS控制规则获取SDF级别QoS控制信息。具体地，PCF实体可以通过向SMF实体发送PDU-CAN会话修改指令，并将策略控制规则或QoS控制规则携带在PDU会话修改指令中。
在另外一种可能的实现方式中，SMF实体在执行上述步骤501时，具体为，根据SMF实体中存储的策略获取SDF级别QoS控制信息。
在上述任一种可能的实现方式中，PCF实体中存储的策略或者SMF实体存储的策略，包括更新SDF级别QoS控制信息的依据。例如，当网络负载达到预设条件时，PCF实体或者SMF实体需要对SDF级别QoS控制信息进行更新，以保证重要业务的QoS不受影响。
进一步地，在上述步骤503中，终端在对上行数据包进行QoS控制，具体包括：终端可以根据接收到的SDF级别QoS控制信息中的优先级，确定SDF级别包过滤器的匹配顺序；根据所述SDF级别包过滤器的匹配顺序执行数据包匹配，并根据匹配成功的包过滤器对应的QoS flow执行QoS控制。
为了更清楚理解本发明实施例提供的QoS控制方法，下面通过几个具体的实施例进行说明。
实施例1
结合图6对具体流程进行说明：
步骤601、PCF实体向SMF实体发送修改PDU-CAN(PDU-Connectivity Access Network，PDU接入网连接)会话的请求，该请求中包括策略控制规则。
进一步地，该请求中还可以包括QoS需求。
可选的，所述策略控制规则信息用于新建一个策略控制规则；或者所述策略控制规则信息用于修改已有的策略控制规则；或者所述策略控制规则信息用于删除一个已有的策略控制规则。
步骤602、SMF实体接收到修改PDU-CAN会话的请求后，确定执行PDU会话更新流程。
步骤603、SMF实体向AMF实体发送会话管理请求，会话管理请求中包含NAS层信令(例如，PDU会话修改命令，图中以PDU会话修改命令为例进行描述)，该NAS层信令中包括上述SDF级别QoS控制信息，即SDF信息。
若SMF实体根据接收到的策略控制规则信息，确定新建一个SDF，则该SDF级别QoS控制信息包括：新建的SDF的标识(SDF ID)，与SDF对应的至少一个包过滤器、优先级、QoS参数。例如，SDF级别QoS控制信息的格式可以为：SDF ID，QoS Parameters，QFI，Precedence value，Filters。
进一步地，若已建立的QoS flow能够满足新建立的SDF的QoS需求，在该SDF级别QoS控制信息中还包括该已建立的QoS flow的标识(QoS flow ID，简称QFI)；若没有已建立的QoS flow能够满足该新建立的SDF的QoS需求，则该SDF级别QoS控制信息中还包括新建立的QoS flow的标识QFI。更进一步地，若新建立的QoS flow为non-GRB QoS flow，QoS参数中可以包括5QI，若新建立的QoS flow为GRB QoS flow，QoS参数中可以包括，5QI、Notification、GFBR和MFBR。
若SMF实体根据接收到的策略控制规则信息，确定修改已有的SDF的QoS需求的策略控制规则，该SDF级别QoS控制信息包括：待修改的SDF的ID；若已建立的QoS flow能够满足修改后的QoS需求，则包括该已建立的QoS flow的QFI，若没有已建立的QoS flow能够满足修改后的QoS需求，则包括新建立的QoS flow的QFI以及新QoS flow对应的QoS参数。例如，SDF级别QoS控制信息的格式可以为：Update-SDF QoS:SDF ID，QFI QoS Parameters。更进一步地，若新建立的QoS flow为non-GRB QoS flow，QoS参数中可以包括5QI，若新建立的QoS flow为GRB QoS flow，QoS参数中可以包括，5QI、Notification、GFBR和MFBR。其中QoS参数是可选的。
若SMF实体根据接收到的策略控制规则信息，确定修改已有的SDF对应的包过滤器和/或优先级，则SDF级别QoS控制信息包括：待修改的SDF的ID，修改后对应的优先级和/或修改后对应的包过滤器。例如，SDF级别QoS控制信息的格式可以为：Update-SDF Filters/precedence:SDF ID，Filters/Precedence value。
若SMF实体根据接收到的策略控制规则信息，确定删除已有的SDF，则SDF级别QoS控制信息包括：待删除的SDF的ID。例如，SDF级别QoS控制信息的格式可以为：Delete-SDF:SDF ID，delete operation。
此外，若SMF实体根据接收到的策略控制规则信息确定需要新建立QoS flow，则上述会话管理请求中还独立包含QoS flow信息，包括QFI以及QoS参数，用于指示RAN/AN存储QoS flow的信息，并建立相应的空口资源或者将QoS flow绑定到现有的空口资源。若SMF实体根据接收到的策略控制规则确定需要删除QoS flow，则上述会话管理请求中还独立包含QoS flow的AFI，用于指示RAN/AN释放空口资源。
步骤604、AMF向通过N2接口RAN/AN发送N2会话请求消息，其中所述N2会话消息包括NAS层信令(例如，PDU会话修改命令，图中以PDU会话修改命令为例进行描述)，该NAS层信令中包括上述SDF级别QoS控制信息。
可选地，若需要新建立QoS flow，则上述N2会话请求消息中还包括需要RAN/AN存储新建的QoS flow的信息，与终端建立相应的空口资源或者将新建的QoS flow绑定到现有的空口资源上；若需要删除QoS flow，则上述N2会话请求消息中还包括需要RAN/AN删除相应的QoS flow信息，以使ANRAN/AN释放与终端的空口资源。
步骤605、AN向终端发送无线资源控制请求，该请求中包含PDU会话修改命令，该PDU会话修改命令中包括上述SDF级别QoS控制信息，以使终端根据上述SDF级别QoS控制信息，对上行数据包执行的QoS控制，或者删除相应的SDF的信息。
步骤606、终端在接收到上述SDF级别QoS控制信息后，向AN返回确认消息。
终端存储上述SDF级别QoS控制信息，并根据上述SDF级别QoS控制信息对上行数据包进行QoS控制。或者删除本地存储的SDF级别QoS控制信息。
其中，SDF级别QoS控制信息在终端上存储的形式可以是：
SDF ID1:Precedence value,QFI,Filters；
SDF ID2:Precedence value,QFI,Filters；
……
步骤607、AN通过N2接口向AMF返回N2会话响应。
步骤608、AMF向SMF返回会话管理响应，该响应中包括PDU会话修改确认消息。
步骤609、SMF通过N4接口向UPF发送N4会话修改请求，该请求中可选的包括上述SDF级别QoS控制信息。
当会话修改请求用于增加一个SDF时，UPF根据上述SDF级别QoS控制信息，在增加的SDF对应的QoS flow中生成至少一个SDF级别的包过滤器，且生成的至少一个SDF级别的包过滤器的优先级相同。
当会话修改请求用于修改已有的SDF信息时，UPF修改该SDF的信息。例如，修改已有的SDF的优先级，UPF则修改该SDF对应的包过滤器的优先级。
当会话修改的请求用于删除已有的SDF时，UPF删除该SDF对应的包过滤器以及该SDF的其他信息。
步骤610、UPF通过N4接口向SMF返回N4会话修改响应。
步骤611、SMF向PCF返回PDU-CAN会话修改确认消息。
通过上述步骤601～步骤611，实现了修改终端和UPF中保存的QoS控制信息，以使终端和UPF能够根据相同SDF级别QoS控制信息，对上、下行数据包进行QoS控制。当然，在一些情况下，例如，在网络负载较大，需要对各业务的优先级进行重新安排，以保证部分业务的QoS不受影响，SMF也可以主动发起修改SDF级别QoS控制信息的过程，即，上述步骤601和步骤611也可以不必执行。
当终端需要发送上行数据包时，根据各SDF级别的优先级，将该上行数据包与优先级最高的SDF对应的包过滤器进行匹配，若上行数据包与优先级最高的SDF对应的包过滤器匹配成功，则使用该过滤器对应的QoS flow传输该上行数据包；否则，将该上行数据包继续与优先级次之的SDF对应的包过滤器进行匹配，直到匹配到合适的包过滤器为止。UPF在接收上行数据包时，会根据相同的SDF级别QoS控制信息进行数据包的匹配，因此UPF确定出的该数据包对应的QoS flow与终端确定出的QoS flow相同，进而能够避免丢包现象。
实施例2、
结合图7对具体流程进行说明：
步骤701、PCF实体向SMF实体发送修改PDU-CAN会话修改请求，该请求中包括策略控制规则。
可选的，所述策略控制规则信息用于新建一个策略控制规则；或者所述策略控制规则信息用于修改已有的策略控制规则；或者所述策略控制规则信息用于删除一个已有的策略控制规则。
步骤702、SMF接收到修改PDU-CAN会话的请求后，确定执行PDU会话更新流程。
步骤703、SMF向AMF发送会话管理请求，会话管理请求中包含NAS层信令(例如，PDU会话修改命令，图中以PDU会话修改命令为例进行描述)，该NAS层信令中包括上述SDF级别QoS控制信息，即QoS flow信息。
若SMF实体根据接收到的策略控制规则信息，确定新建一个QoS flow，该SDF级别QoS控制信息包括：新建的QoS flow的QFI，SDF的ID，SDF的优先级，包过滤器。其中，与新建的QoS flow对应的SDF可以是已有的SDF，也可以是新建的SDF。例如，SDF级别QoS控制信息的格式可以为：QFI，QoS parameters，SDF ID，Precedence value，Filters。进一步地，若新建立的QoS flow为non-GRB QoS flow，QoS参数中可以包括5QI，若新建立的QoS flow为GRB QoS flow，QoS参数中可以包括，5QI、Notification、GFBR和MFBR。其中QoS参数为可选的。
若SMF实体根据接收到的策略控制规则信息，确定修改已有的QoS flow，该SDF级别QoS控制信息包括：待修改的QoS flow的QFI，SDF的ID，SDF的优先级，包过滤器。其中，与该QoS flow对应的修改后的SDF中，可以增加了新的SDF，也可以删除了原有的SDF。也可以既不增加新的SDF也不删除原有的SDF，仅修改原有SDF的优先级和/或包过滤器。例如，SDF级别QoS控制信息的格式可以为：QFI，SDF ID，Filters/Precedence value。
若SMF实体根据接收到的策略控制规则信息，确定删除已有的QoS flow，该SDF级别QoS控制信息中可以仅包括待删除的QoS flow的标识。
此外，若SMF实体根据接收到的策略控制规则信息确定需要新建立QoS flow，则上述会话管理请求中还独立包含QoS flow信息，包括QFI以及QoS参数，用于指示RAN/AN存储QoS flow的信息，并建立相应的空口资源或者将QoS flow绑定到现有的空口资源。若SMF实体根据接收到的策略控制规则确定需要删除QoS flow，则上述会话管理请求中还独立包含QoS flow的QFI，用于指示RAN/AN释放空口资源。
步骤704、AMF向通过N2接口AN发送N2会话请求，其中所述N2会话消息包括NAS层信令(例如，PDU会话修改命令，图中以PDU会话修改命令为例进行描述)，该NAS层信令中包括上述SDF级别QoS控制信息。
进一步地，若需要新建立QoS flow，则上述N2会话请求消息中还包括需要RAN/AN存储新建的QoS flow的信息，与终端建立相应的空口资源或者将新建的QoS flow绑定到现有的空口资源上；若需要删除QoS flow，则上述N2会话请求消息中还包括需要RAN/AN删除相应的QoS flow信息，以使ANRAN/AN释放与终端的空口资源。
步骤705、AN向终端发送无线资源控制请求，该请求中包含PDU会话修改命令，该PDU会话修改命令中包括上述SDF级别QoS控制信息，以使终端根据上述SDF级别QoS控制信息，对上行数据包执行QoS控制，或者删除相应的QoS flow的信息。
步骤706、终端在接收到上述SDF级别QoS控制信息后，向AN返回确认消息。
终端存储上述SDF级别QoS控制信息，并根据上述SDF级别QoS控制信息对上行数据包进行QoS控制。或者删除本地存储的SDF级别QoS控制信息。
其中，SDF级别QoS控制信息在终端上存储的形式可以是：
QFI 1:SDF ID 1,Precedence value,Filters；
SDF ID 2,Precedence value,Filters；……
QFI 2:SDF ID 3,Precedence value,Filters；
SDF ID 4,Precedence value,Filters；……
……
步骤707、AN通过N2接口向AMF返回N2会话响应。
步骤708、AMF向SMF返回会话管理响应，该响应中包括PDU会话修改确认消息。
步骤709、SMF通过N4接口向UPF发送N4会话修改请求，该请求中可选的包括上述SDF级别QoS控制信息。
当会话修改请求用于增加一个QoS flow时，UPF根据上述SDF级别QoS控制信息，在增加的QoS flow中生成与该QoS flow对应的SDF的至少一个SDF级别的包过滤器，且生成的至少一个SDF级别的包过滤器的优先级相同。
当会话修改请求用于修改已有的QoS flow信息时，UPF修改该QoS flow的信息。
当会话修改的请求用于删除已有的QoS flow时，UPF删除该QoS flow的信息。
步骤710、UPF通过N4接口向SMF返回N4会话修改响应。
步骤711、SMF向PCF返回PDU-CAN修改确认消息。
通过上述步骤701～步骤711，实现了终端和UPF均根据相同SDF级别QoS控制信息，对上、下行数据包进行QoS控制。
当终端需要发送上行数据包时，根据各SDF级别的优先级，将该上行数据包与优先级最高的SDF对应的包过滤器进行匹配，若上行数据包与优先级最高的SDF对应的包过滤器匹配成功，则使用该过滤器对应的QoS flow传输该上行数据包；否则，将该上行数据包继续与优先级次之的SDF对应的包过滤器进行匹配，直到匹配到合适的包过滤器为止。UPF在接收上行数据包时，会根据相同的SDF级别QoS控制信息进行数据包的匹配，因此UPF确定出的该数据包对应的QoS flow与终端确定出的QoS flow相同，进而能够避免丢包现象。
同样的，在一些情况下，SMF也可以主动发起修改SDF级别QoS控制信息的过程，即，上述步骤701和步骤711也可以不必执行。
实施例2中的SDF级别QoS控制信息与实施例1中的SDF级别QoS控制信息，在信息的具体内容、信息格式上稍有不同，但实施例1和实施例2中的QoS控制信息都是基于SDF级别实现的，不同的SDF对应不同的优先级。因此，在实施例2中，终端和UPF对上、下行数据包进行QoS的控制的过程是相同的。
当终端需要发送上行数据包时，根据各SDF级别的优先级，将该上行数据包与优先级最高的SDF对应的包过滤器进行匹配，若上行数据包与优先级最高的SDF对应的包过滤器匹配成功，则使用该过滤器对应的QoS flow传输该上行数据包；否则，将该上行数据包继续与优先级次之的SDF对应的包过滤器进行匹配，直到匹配到合适的包过滤器为止。UPF在接收上行数据包时，会根据相同的SDF级别QoS控制信息进行数据包的匹配，因此UPF确定出的该数据包对应的QoS flow与终端确定出的QoS flow相同，进而能够避免丢包现 象。
实施例3、
结合图8对具体流程进行说明：
步骤801、PCF向SMF发送修改PDU-CAN会话修改请求，该请求中包括策略规则信息。
可选的，所述策略控制规则信息用于新建一个策略控制规则；或者所述策略控制规则信息用于修改已有的策略控制规则；或者所述策略控制规则信息用于删除一个已有的策略控制规则。
步骤802、SMF接收到修改PDU会话的请求后，确定执行PDU会话更新流程。
步骤803、SMF向AMF发送会话管理请求，会话管理请求中包含NAS层信令(例如，PDU会话修改命令，图中以PDU会话修改命令为例进行描述)，该NAS层信令中包括上述SDF级别QoS控制信息，即QoS规则。
若SMF实体根据接收到的策略控制规则信息，确定新建一个QoS规则，该SDF级别QoS控制信息包括：新建的QoS规则的标识(QoS rule ID)，包过滤器、优先级、QFI及QoS参数。例如，SDF级别QoS控制信息的格式可以为：QoS rule ID，QFI，QoS parameters，Precedence value，Filters。其中，若存在已有的QoS flow能够满足新建的QoS规则对QoS的需求，则QFI为已有QoS flow的QFI，若不存在已有的QoS flow满足新建的QoS规则对应QoS的需求，则需要新建一个QoS flow，上述QFI则为新建的QoS flow的QFI。进一步地，若新建立的QoS flow为non-GRB QoS flow，QoS参数中可以包括5QI，若新建立的QoS flow为GRB QoS flow，QoS参数中可以包括，5QI、Notification、GFBR和MFBR。，其中QoS参数是可选的
若SMF实体根据接收到的策略控制规则信息，确定修改已有的QoS规则的QoS需求，该SDF级别QoS控制信息包括：待修改的QoS rule ID；若已建立的QoS flow能够满足修改后的QoS需求，则包括该已建立的QoS flow的QFI，若没有已建立的QoS flow能够满足修改后的QoS需求，则包括新建立的QoS flow的QFI以及新QoS flow对应的QoS参数。例如，SDF级别QoS控制信息的格式可以为：QoS rule ID，QoS flow ID，QoS parameters.
若SMF实体根据接收到的策略控制规则信息，确定修改已有的QoS规则对应的包过滤器和/或优先级，则SDF级别QoS控制信息包括：待修改的QoS rule ID，修改后对应的优先级和/或修改后对应的包过滤器。
若SMF实体根据接收到的策略控制规则信息，确定删除已有的SDF，则SDF级别QoS控制信息包括：待删除的SDF的ID。
此外，若SMF实体根据接收到的策略控制规则信息确定需要新建立QoS flow，则上述会话管理请求中还独立包含QoS flow信息，包括QFI以及QoS参数，用于指示RAN/AN存储QoS flow的信息，并建立相应的空口资源或者将QoS flow绑定到现有的空口资源。若SMF实体根据接收到的策略控制规则确定需要删除QoS flow，则上述会话管理请求中还独立包含QoS flow的QFI，用于指示RAN/AN释放空口资源。
步骤804、AMF向通过N2接口RAN/AN发送N2会话请求，其中所述N2会话消息包括NAS层信令(例如，PDU会话修改命令，图中以PDU会话修改命令为例进行描述)，该NAS层信令中包括上述SDF级别QoS控制信息。
可选地，若需要新建立QoS flow，则上述N2会话请求消息中还包括需要RAN/AN存储新建的QoS flow的信息，与终端建立相应的空口资源或者将新建的QoS flow绑定到现有 的空口资源上。若需要删除QoS flow，则上述N2会话请求消息中还包括需要RAN/AN删除相应的QoS flow信息，以使RAN/AN释放与终端的空口资源。
步骤805、AN向终端发送无线资源控制请求，该请求中包含PDU会话修改命令，该PDU会话修改命令中包括上述SDF级别QoS控制信息，以使终端根据上述SDF级别QoS控制信息，对上行数据包执行QoS控制，或者删除相应的QoS规则的信息。
步骤806、终端在接收到上述SDF级别QoS控制信息后，向AN返回确认消息。
终端存储上述SDF级别QoS控制信息，并根据上述SDF级别QoS控制信息对上行数据包进行QoS控制。或者删除本地存储的SDF级别QoS控制信息。
其中，SDF级别QoS控制信息在终端上存储的形式可以是：
Qos Rule ID1:Precedence value,QFI,Filters；
QoS Rule ID2:Precedence value,QFI,Filters；
……
步骤807、AN通过N2接口向AMF返回N2会话响应。
步骤808、AMF向SMF返回会话管理响应，该响应中包括PDU会话修改确认消息。
步骤809、SMF通过N4接口向UPF发送N4会话修改请求，该请求中可选的包括上述SDF级别QoS控制信息。
当会话修改请求用于增加一个QoS规则时，UPF根据上述SDF级别QoS控制信息，在增加的QoS对应的QoS flow中生成与该QoS flow对应的SDF的至少一个SDF级别的包过滤器，且生成的至少一个SDF级别的包过滤器的优先级相同。
当会话修改请求用于修改已有的QoS规则时，UPF修改该QoS规则的信息。
当会话修改的请求用于删除已有的QoS规则时，UPF删除该QoS规则的全部信息。
步骤810、UPF通过N4接口向SMF返回N4会话修改响应。
步骤811、SMF向PCF返回PDU-CAN修改确认消息。
通过上述步骤801～步骤811，实现了终端和UPF均根据相同SDF级别QoS控制信息，对上、下行数据包进行QoS控制。
当终端需要发送上行数据包时，根据各SDF级别的优先级，将该上行数据包与优先级最高的SDF对应的包过滤器进行匹配，若上行数据包与优先级最高的SDF对应的包过滤器匹配成功，则使用该过滤器对应的QoS flow传输该上行数据包；否则，将该上行数据包继续与优先级次之的SDF对应的包过滤器进行匹配，直到匹配到合适的包过滤器为止。UPF在接收上行数据包时，会根据相同的SDF级别QoS控制信息进行数据包的匹配，因此UPF确定出的该数据包对应的QoS flow与终端确定出的QoS flow相同，进而能够避免丢包现象。
同样的，在一些情况下，SMF也可以主动发起修改SDF级别QoS控制信息的过程，即，上述步骤801和步骤811也可以不必执行。
实施例3中的SDF级别QoS控制信息与实施例1和实施例2中的SDF级别QoS控制信息，在信息的具体内容、信息格式上稍有不同，但实施例1、实施例2和实施例3中的QoS控制信息都是基于SDF级别实现的，不同的SDF对应不同的优先级。因此，在实施例3中，终端和UPF对上、下行数据包进行QoS的控制的过程是相同的，此处不再赘述。
图9示出了上述实施例中所涉及的会话管理功能SMF实体的一种可能的结构示意图，该SMF实体900同样可以实现图5，图6，图7，或图8所示的SMF实体的功能。
SMF实体900包括：处理单元902和通信单元903。处理单元902用于对SMF实体的动作进行控制管理，例如，处理单元902用于支持SMF实体执行图5中的过程501～503；图6中的过程602、603和609；图7中的过程702、703和709；或图8中的过程802、803和809；和/或用于本文所描述的技术的其它过程。通信单元903用于支持SMF实体与其他网络实体的通信，例如与图5，图6，图7，或图8中示出的功能模块或网络实体之间的通信。SMF实体还可以包括存储单元901，用于存储SMF实体的程序代码和数据。
需要说明的是，本发明实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。本发明实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。例如，上述实施例中，第一获取单元和第二获取单元可以是同一个单元，也不同的单元。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
其中，处理单元902可以是处理器或控制器，例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信单元903可以是收发器。存储单元901可以是存储器。
当处理单元902为处理器，通信单元903为收发器，存储单元901为存储器时，本发明实施例所涉及的SMF实体可以为图10所示的SMF实体。
基于相同的技术构思，图10示出了上述实施例中所涉及的SMF实体另一种可能的结构示意图，包括：处理器1001以及分别与所述处理器1001连接的存储器1002和收发器1003。
其中，处理器1001，用于调用存储器1002中预先存储的计算机程序执行：
获取服务数据流SDF级别QoS控制信息；
通过收发器1003发送所述SDF级别QoS控制信息给终端。
在一种可能的实现方式中，处理器1001还用于：通过收发器1003发送所述SDF级别QoS控制信息给UPF实体，以使所述UPF根据所述SDF级别QoS控制信息验证上行数据包的QoS控制，或者删除所述SDF级别QoS控制信息。
在一种可能的实现方式中，处理器1001在获取SDF级别QoS控制信息时，具体用于：根据PCF实体发送的会话管理请求获取SDF级别QoS控制信息；或者，根据本地策略获取SDF级别的QoS控制信息。
在一种可能的实现方式中，SDF级别QoS控制信息，包括：SDF的标识；或者，SDF的标识，以及与以下至少一种或组合：所述SDF对应的至少一个包过滤器、优先级、QoS flow的标识、QoS参数。
在一种可能的实现方式中，SDF级别QoS控制信息，包括：QoS flow的标识；或者，QoS flow的标识，以及以下至少一种或组合：至少一个SDF的标识、与所述至少一个SDF对应的至少一个包过滤器、与所述至少一个SDF对应的优先级、与所述QoS flow对应的QoS参数。
在一种可能的实现方式中，SDF级别QoS控制信息，包括：QoS规则的标识；或者，QoS规则的标识，以及以下至少一种或组合：与所述QoS规则对应的至少一个包过滤器、优先级、QoS flow的标识、QoS参数。
在一种可能的实现方式中，处理器1001还用于：通过收发器1003向接入网设备发送QoS flow的标识和与所述QoS flow对应的QoS参数，以使接入网设备建立对应的空口资源。
图11示出了上述实施例中所涉及的终端的一种可能的结构示意图，该终端1100同样可以实现图6，图7，或图8所示的终端的功能。
终端1100包括：处理单元1102和通信单元1103。处理单元1102用于对终端的动作进行控制管理，例如，处理单元1102用于支持终端执行图6中的过程606，图7中的过程706，图8中的过程806，和/或用于本文所描述的技术的其它过程。通信单元1103用于支持终端与其他网络实体的通信，例如与图6，图7，或图8中示出的功能模块或网络实体之间的通信。终端还可以包括存储单元1101，用于存储终端的程序代码和数据。
需要说明的是，本发明实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。本发明实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。例如，上述实施例中，第一获取单元和第二获取单元可以是同一个单元，也不同的单元。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
其中，处理单元1102可以是处理器或控制器，例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信单元1103可以是收发器。存储单元1101可以是存储器。
当处理单元1102为处理器，通信单元1103为收发器，存储单元1101为存储器时，本发明实施例所涉及的终端可以为图10所示的终端。
基于相同的技术构思，图12示出了上述实施例中所涉及的终端另一种可能的结构示意图，包括：处理器1201以及分别与处理器1201连接的存储器1202和收发机1203。
其中，处理器1201，用于调用存储器1202中预先存储的计算机程序执行：
通过收发器1203接收SMF实体发送的服务数据流SDF级别QoS控制信息；
根据SDF级别QoS控制信息，对上行数据包进行SDF级别的Qos控制，或者删除所述SDF级别QoS控制信息。
在一种可能的实现方式中，SDF级别QoS控制信息，包括：SDF的标识；或者，SDF的标识，以及以下一种或组合：与所述SDF对应的至少一个包过滤器、优先级、QoS flow的标识和QoS参数。
在一种可能的实现方式中，SDF级别QoS控制信息，包括：QoS flow的标识；或者，QoS flow的标识，以及以下至少一种或组合：至少一个SDF的标识、与所述至少一个SDF对应的至少一个包过滤器、与所述至少一个SDF对应的优先级、与所述QoS flow对应的 QoS参数。
在一种可能的实现方式中，SDF级别QoS控制信息，包括：QoS规则的标识；或者，QoS规则的标识，以及以下至少一种或组合：与所述QoS规则对应的至少一个包过滤器、优先级、QoS flow的标识和QoS参数。
在一种可能的实现方式中，处理器1201根据所述SDF级别QoS控制信息，对上行数据包执行QoS控制时，具体用于：根据所述SDF级别QoS控制信息中的优先级，确定SDF级别包过滤器的匹配顺序；根据所述SDF级别包过滤器的匹配顺序执行数据包匹配，并根据匹配成功的包过滤器对应的QoS flow执行QoS控制。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请实施例的精神和范围。这样，倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (24)

  1. 一种服务质量QoS控制方法，其特征在于，包括：
    会话管理功能SMF实体获取服务数据流SDF级别QoS控制信息；
    所述SMF实体发送所述SDF级别QoS控制信息给终端。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    发送所述SDF级别QoS控制信息给用户面功能UPF实体，以使所述UPF根据所述SDF级别QoS控制信息验证上行数据包的QoS控制，或者删除所述SDF级别QoS控制信息。
  3. 如权利要求1或2所述的方法，其特征在于，所述SMF实体获取SDF级别QoS控制信息，包括：
    所述SMF实体根据策略控制功能PCF实体发送的会话管理请求获取SDF级别QoS控制信息；或者
    所述SMF实体根据本地策略获取SDF级别QoS控制信息。
  4. 如权利要求1～3中任一项所述的方法，其特征在于，所述SDF级别QoS控制信息，包括：
    SDF的标识；或者
    SDF的标识，以及与以下至少一种或组合：所述SDF对应的至少一个包过滤器、优先级、QoS flow的标识、QoS参数。
  5. 如权利要求1～3中任一项所述的方法，其特征在于，所述SDF级别QoS控制信息，包括：
    QoS flow的标识；或者
    QoS flow的标识，以及以下至少一种或组合：至少一个SDF的标识、与所述至少一个SDF对应的至少一个包过滤器、与所述至少一个SDF对应的优先级、与所述QoS flow对应的QoS参数。
  6. 如权利要求1～3中任一项所述的方法，其特征在于，所述SDF级别QoS控制信息，包括：
    QoS规则的标识；或者
    QoS规则的标识，以及以下至少一种或组合：与所述QoS规则对应的至少一个包过滤器、优先级、QoS flow的标识、QoS参数。
  7. 如权利要求1～6中任一项所述的方法，其特征在于，所述方法还包括：
    所述SMF实体向接入网设备发送QoS flow的标识，或者QoS flow的标识和与所述QoS flow对应的QoS参数，以使接入网设备建立，释放或者绑定到对应的空口资源。
  8. 一种服务质量QoS控制方法，其特征在于，包括：
    终端接收会话管理功能SMF实体发送的服务数据流SDF级别QoS控制信息；
    终端根据所述SDF级别QoS控制信息，对上行数据包进行QoS控制，或者删除所述SDF级别QoS控制信息。
  9. 如权利要求8所述的方法，其特征在于，所述SDF级别QoS控制信息，包括：
    SDF的标识；或者
    SDF的标识，以及以下一种或组合：与所述SDF对应的至少一个包过滤器、优先级、 QoS flow的标识和QoS参数。
  10. 如权利要求8所述的方法，其特征在于，所述SDF级别QoS控制信息，包括：
    QoS flow的标识；或者
    QoS flow的标识，以及以下至少一种或组合：至少一个SDF的标识、与所述至少一个SDF对应的至少一个包过滤器、与所述至少一个SDF对应的优先级、与所述QoS flow对应的QoS参数。
  11. 如权利要求8所述的方法，其特征在于，所述SDF级别QoS控制信息，包括：
    QoS规则的标识；或者
    QoS规则的标识，以及以下至少一种或组合：与所述QoS规则对应的至少一个包过滤器、优先级、QoS flow的标识和QoS参数。
  12. 如权利要求8～11中任一项所述的方法，其特征在于，终端根据所述SDF级别QoS控制信息，对上行数据包执行QoS控制，包括：
    所述终端根据所述SDF级别QoS控制信息中的优先级，确定SDF级别包过滤器的匹配顺序；
    所述终端根据所述SDF级别包过滤器的匹配顺序执行数据包匹配，并根据匹配成功的包过滤器对应的QoS flow执行QoS控制。
  13. 一种会话管理功能SMF实体，其特征在于，包括：处理器以及分别与所述处理器连接的存储器和收发机；
    所述处理器，用于调用所述存储器中预先存储的计算机程序执行：
    获取服务数据流SDF级别QoS控制信息；
    通过所述收发器发送所述SDF级别QoS控制信息给终端。
  14. 如权利要求13所述的SMF实体，其特征在于，所述处理器还用于：
    通过所述收发器发送所述SDF级别QoS控制信息给用户面功能UPF实体，以使所述UPF根据所述SDF级别QoS控制信息验证上行数据包的QoS控制，或者删除所述SDF级别QoS控制信息。
  15. 如权利要求13或14所述的SMF实体，其特征在于，所述处理器在获取SDF级别QoS控制信息时，具体用于：
    根据策略控制功能PCF实体发送的会话管理请求获取SDF级别QoS控制信息；或者
    根据本地策略获取SDF级别QoS控制信息。
  16. 如权利要求13～15中任一项所述的SMF实体，其特征在于，所述SDF级别QoS控制信息，包括：
    SDF的标识；或者
    SDF的标识，以及与以下至少一种或组合：所述SDF对应的至少一个包过滤器、优先级、QoS flow的标识、QoS参数。
  17. 如权利要求13～15中任一项所述的SMF实体，其特征在于，所述SDF级别QoS控制信息，包括：
    QoS flow的标识；或者
    QoS flow的标识，以及以下至少一种或组合：至少一个SDF的标识、与所述至少一个SDF对应的至少一个包过滤器、与所述至少一个SDF对应的优先级、与所述QoS flow对应的QoS参数。
  18. 如权利要求13～15中任一项所述的SMF实体，其特征在于，所述SDF级别QoS控制信息，包括：
    QoS规则的标识；或者
    QoS规则的标识，以及以下至少一种或组合：与所述QoS规则对应的至少一个包过滤器、优先级、QoS flow的标识、QoS参数。
  19. 如权利要求13～18中任一项所述的SMF实体，其特征在于，所述处理器还用于：
    通过所述收发器向接入网设备发送QoS flow的标识或者QoS flow的标识和与所述QoS flow对应的QoS参数，以使接入网设备建立，释放或者绑定到对应的空口资源。
  20. 一种终端，其特征在于，包括：处理器以及分别与所述处理器连接的存储器和收发机；
    所述处理器，用于调用所述存储器中预先存储的计算机程序执行：
    通过所述收发器接收会话管理功能SMF实体发送的服务数据流SDF级别QoS控制信息；
    根据所述SDF级别QoS控制信息，对上行数据包执行QoS控制，或者删除所述SDF级别QoS控制信息。
  21. 如权利要求20所述的终端，其特征在于，所述SDF级别QoS控制信息，包括：
    SDF的标识；或者
    SDF的标识，以及以下一种或组合：与所述SDF对应的至少一个包过滤器、优先级、QoS flow的标识和QoS参数。
  22. 如权利要求20所述的终端，其特征在于，所述SDF级别QoS控制信息，包括：
    QoS flow的标识；或者
    QoS flow的标识，以及以下至少一种或组合：至少一个SDF的标识、与所述至少一个SDF对应的至少一个包过滤器、与所述至少一个SDF对应的优先级、与所述QoS flow对应的QoS参数。
  23. 如权利要求20所述的终端，其特征在于，所述SDF级别QoS控制信息，包括：
    QoS规则的标识；或者
    QoS规则的标识，以及以下至少一种或组合：与所述QoS规则对应的至少一个包过滤器、优先级、QoS flow的标识和QoS参数。
  24. 如权利要求20～23所述的终端，其特征在于，所述处理器根据所述SDF级别QoS控制信息，对上行数据包执行QoS控制时，具体用于：
    根据所述SDF级别QoS控制信息中的优先级，确定SDF级别包过滤器的匹配顺序；
    根据所述SDF级别包过滤器的匹配顺序执行数据包匹配，并根据匹配成功的包过滤器对应的QoS flow执行QoS控制。
PCT/CN2017/083671 2017-05-09 2017-05-09 一种QoS控制方法及设备 WO2018205155A1 (zh)

Priority Applications (16)

Application Number Priority Date Filing Date Title
EP21186467.3A EP3986019A1 (en) 2017-05-09 2017-05-09 Qos control method and device
JP2019561743A JP7250700B2 (ja) 2017-05-09 2017-05-09 ＱｏＳ制御方法およびデバイス
EP17909069.1A EP3624500B1 (en) 2017-05-09 2017-05-09 Qos control method and equipment
PCT/CN2017/083671 WO2018205155A1 (zh) 2017-05-09 2017-05-09 一种QoS控制方法及设备
PL17909069T PL3624500T3 (pl) 2017-05-09 2017-05-09 Sposób i sprzęt do sterowania qos
BR112019023333-4A BR112019023333A2 (pt) 2017-05-09 2017-05-09 Método de controle de qos e dispositivo
KR1020197036331A KR102305716B1 (ko) 2017-05-09 2017-05-09 ＱｏＳ 제어 방법 및 장치
CN202111209592.4A CN113923714A (zh) 2017-05-09 2017-05-09 一种QoS控制方法及设备
CN201780038531.1A CN109314921B (zh) 2017-05-09 2017-05-09 一种QoS控制方法、设备及系统
RU2019139836A RU2744907C1 (ru) 2017-05-09 2017-05-09 Устройство и способ управления qos
CN201910168204.9A CN109982377B (zh) 2017-05-09 2017-05-09 一种QoS控制方法及设备
CN202111209772.2A CN113923715A (zh) 2017-05-09 2017-05-09 一种QoS控制方法及设备
US16/398,937 US10772004B2 (en) 2017-05-09 2019-04-30 QOS control method and device
US17/011,349 US11259207B2 (en) 2017-05-09 2020-09-03 QoS control method and device
US17/565,829 US20220201542A1 (en) 2017-05-09 2021-12-30 QoS Control Method and Device
JP2022054074A JP2022093339A (ja) 2017-05-09 2022-03-29 ＱｏＳ制御方法およびデバイス

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/083671 WO2018205155A1 (zh) 2017-05-09 2017-05-09 一种QoS控制方法及设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/398,937 Continuation US10772004B2 (en) 2017-05-09 2019-04-30 QOS control method and device

Publications (1)

Publication Number Publication Date
WO2018205155A1 true WO2018205155A1 (zh) 2018-11-15

Family

ID=64104041

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/083671 WO2018205155A1 (zh) 2017-05-09 2017-05-09 一种QoS控制方法及设备

Country Status (9)

Country Link
US (3) US10772004B2 (zh)
EP (2) EP3986019A1 (zh)
JP (2) JP7250700B2 (zh)
KR (1) KR102305716B1 (zh)
CN (4) CN113923714A (zh)
BR (1) BR112019023333A2 (zh)
PL (1) PL3624500T3 (zh)
RU (1) RU2744907C1 (zh)
WO (1) WO2018205155A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111200798A (zh) * 2018-11-20 2020-05-26 华为技术有限公司 一种v2x消息的传输方法、设备及系统
CN111200565A (zh) * 2018-11-19 2020-05-26 电信科学技术研究院有限公司 一种信息传输方法、终端及网络设备
WO2020191684A1 (zh) * 2019-03-27 2020-10-01 Oppo广东移动通信有限公司 QoS规则的优先级处理方法、设备及存储介质
WO2020224372A1 (zh) * 2019-05-06 2020-11-12 腾讯科技（深圳）有限公司 副链路通信的服务质量控制方法、装置、介质及电子设备
JP2022520592A (ja) * 2019-02-13 2022-03-31 華為技術有限公司 ポリシー制御方法、装置及びシステム

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6872006B2 (ja) 2016-10-17 2021-05-19 エスケー テレコム カンパニー リミテッドＳｋ Ｔｅｌｅｃｏｍ Ｃｏ．， Ｌｔｄ． 基地局装置及び無線区間のＱｏＳ制御方法
CN109392042B (zh) * 2017-08-14 2021-10-26 华为技术有限公司 一种会话管理方法、异系统互操作的方法及网络装置
CN110035401B (zh) * 2018-01-12 2020-06-23 电信科学技术研究院有限公司 一种默认服务质量QoS控制方法及设备
US20190313311A1 (en) 2018-04-09 2019-10-10 Mediatek Inc. Apparatuses, service networks, and methods for handling plmn-specific parameters for an inter-plmn handover
US11026124B2 (en) 2018-07-02 2021-06-01 Mediatek Inc. Enhanced handling on 5G QoS operations
US11039369B2 (en) 2018-08-10 2021-06-15 Mediatek Inc. Handling 5G QoS rules on QoS operation errors
WO2020099128A1 (en) * 2018-11-13 2020-05-22 Telefonaktiebolaget Lm Ericsson (Publ) Sidelink quality of service flow management in wireless communications systems and related methods and apparatuses
US10448268B1 (en) * 2019-01-30 2019-10-15 Cisco Technology, Inc. Preservation of policy and charging for a subscriber following a user-plane element failover
KR20200114932A (ko) * 2019-03-29 2020-10-07 삼성전자주식회사 NAS 프로토콜을 이용한 QoS 관리 방법 및 장치
KR20210031297A (ko) * 2019-09-11 2021-03-19 삼성전자주식회사 무선 통신 시스템에서 트래픽을 처리하기 위한 장치 및 방법
CN113038527A (zh) * 2021-02-25 2021-06-25 腾讯科技（深圳）有限公司 应用程序的控制方法、装置、设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101009631A (zh) * 2006-01-24 2007-08-01 华为技术有限公司 一种QoS控制方法和系统
CN101094509A (zh) * 2006-06-20 2007-12-26 华为技术有限公司 演进网络及用户设备锚点迁移的方法
CN103181221A (zh) * 2010-10-25 2013-06-26 阿尔卡特朗讯 在多接入通信系统中，通过用户设备及QoS支持，为IP业务的路由控制接入网络/接入技术的选择
WO2014016676A1 (en) * 2012-07-27 2014-01-30 Alcatel Lucent Terminate a charging session for an always on ip connectivity session

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060045128A1 (en) * 2004-09-01 2006-03-02 Lila Madour Per flow quality of service (QoS) enforcement for downlink data traffic
JP2007180889A (ja) * 2005-12-28 2007-07-12 Nec Corp 無線ＬＡＮシステム、制御装置、無線基地局及びそれらに用いるＱｏＳ制御方法
ATE449487T1 (de) * 2006-06-02 2009-12-15 Ericsson Telefon Ab L M Einrichtungen und verfahren zum garantieren einer dienstgüte pro dienstdatenfluss durch die trägerschicht
US8194540B2 (en) * 2007-08-08 2012-06-05 Samsung Electronics Co., Ltd. Apparatus and method for managing quality of service of service flow in wireless communication system
US8903059B2 (en) * 2010-10-05 2014-12-02 Tekelec, Inc. Methods, systems, and computer readable media for service data flow (SDF) based subscription profile repository (SPR) selection
US8649286B2 (en) 2011-01-18 2014-02-11 Apple Inc. Quality of service (QoS)-related fabric control
CN104683956B (zh) * 2013-11-27 2018-01-26 普天信息技术研究院有限公司 QoS控制方法和系统
US9756088B2 (en) 2015-09-08 2017-09-05 Qualcomm Incorporated IMS over soft AP admission control and resource management
WO2018075828A1 (en) * 2016-10-19 2018-04-26 Convida Wireless, Llc Apparatus
EP3536095A1 (en) * 2016-11-04 2019-09-11 Telefonaktiebolaget LM Ericsson (publ) Reflective mapping of flows to radio bearers
CN108702724B (zh) * 2016-11-27 2021-06-15 Lg 电子株式会社 无线通信系统中的注销方法及其装置
EP3331270B1 (en) * 2016-12-05 2019-11-27 NTT DoCoMo, Inc. Method for transmitting data and communication device
WO2018124810A1 (ko) * 2016-12-29 2018-07-05 엘지전자 주식회사 Drb를 확립하는 방법 및 장치
WO2018143593A1 (en) * 2017-02-01 2018-08-09 Lg Electronics Inc. Method for performing reflective quality of service (qos) in wireless communication system and a device therefor
US10542454B2 (en) * 2017-02-10 2020-01-21 Mediatek Inc. Control and management of reflective QoS
EP3603167A4 (en) * 2017-03-22 2020-10-21 LG Electronics Inc. -1- PROCESS FOR TRANSMITTING AN UPRIGHT LINK PACKAGE BASED ON A QUALITY OF SERVICE (QOS) FRAMEWORK IN A WIRELESS COMMUNICATION SYSTEM AND RELATED DEVICE

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101009631A (zh) * 2006-01-24 2007-08-01 华为技术有限公司 一种QoS控制方法和系统
CN101094509A (zh) * 2006-06-20 2007-12-26 华为技术有限公司 演进网络及用户设备锚点迁移的方法
CN103181221A (zh) * 2010-10-25 2013-06-26 阿尔卡特朗讯 在多接入通信系统中，通过用户设备及QoS支持，为IP业务的路由控制接入网络/接入技术的选择
WO2014016676A1 (en) * 2012-07-27 2014-01-30 Alcatel Lucent Terminate a charging session for an always on ip connectivity session

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111200565A (zh) * 2018-11-19 2020-05-26 电信科学技术研究院有限公司 一种信息传输方法、终端及网络设备
CN111200565B (zh) * 2018-11-19 2022-05-06 大唐移动通信设备有限公司 一种信息传输方法、终端及网络设备
CN111200798A (zh) * 2018-11-20 2020-05-26 华为技术有限公司 一种v2x消息的传输方法、设备及系统
WO2020103863A1 (zh) * 2018-11-20 2020-05-28 华为技术有限公司 一种v2x消息的传输方法、设备及系统
CN111200798B (zh) * 2018-11-20 2022-04-05 华为技术有限公司 一种v2x消息的传输方法、设备及系统
US11877215B2 (en) 2018-11-20 2024-01-16 Huawei Technologies Co., Ltd. V2X message transmission method, device, and system
JP2022520592A (ja) * 2019-02-13 2022-03-31 華為技術有限公司 ポリシー制御方法、装置及びシステム
JP7218447B2 (ja) 2019-02-13 2023-02-06 華為技術有限公司 ポリシー制御方法、装置及びシステム
US11582350B2 (en) 2019-02-13 2023-02-14 Huawei Technologies Co., Ltd. Policy charging control and session management interaction method, apparatus, and system
WO2020191684A1 (zh) * 2019-03-27 2020-10-01 Oppo广东移动通信有限公司 QoS规则的优先级处理方法、设备及存储介质
WO2020224372A1 (zh) * 2019-05-06 2020-11-12 腾讯科技（深圳）有限公司 副链路通信的服务质量控制方法、装置、介质及电子设备

Also Published As

Publication number Publication date
US20190261211A1 (en) 2019-08-22
EP3624500B1 (en) 2021-09-22
CN109982377A (zh) 2019-07-05
US20220201542A1 (en) 2022-06-23
EP3986019A1 (en) 2022-04-20
EP3624500A4 (en) 2020-05-06
BR112019023333A2 (pt) 2020-06-16
CN109982377B (zh) 2020-03-10
CN109314921B (zh) 2021-10-15
CN109314921A (zh) 2019-02-05
CN113923715A (zh) 2022-01-11
KR20200004397A (ko) 2020-01-13
JP7250700B2 (ja) 2023-04-03
JP2022093339A (ja) 2022-06-23
PL3624500T3 (pl) 2022-01-31
CN113923714A (zh) 2022-01-11
US11259207B2 (en) 2022-02-22
JP2020520171A (ja) 2020-07-02
EP3624500A1 (en) 2020-03-18
US10772004B2 (en) 2020-09-08
RU2744907C1 (ru) 2021-03-17
KR102305716B1 (ko) 2021-09-27
US20200404534A1 (en) 2020-12-24

Similar Documents

Publication Publication Date Title
WO2018205155A1 (zh) 一种QoS控制方法及设备
US10966222B2 (en) Method, device, and system for processing reflective QoS characteristics
TWI705715B (zh) 預設服務品質規則管理方法及使用者設備
JP7069108B2 (ja) データフローを伝送する無線ベアラの処理方法及び装置
WO2021037175A1 (zh) 一种网络切片的管理方法及相关装置
CN110831243B (zh) 一种用户面安全策略实现方法、装置及系统
WO2018059268A1 (zh) 网络切片的建立方法和装置
WO2019033796A1 (zh) 会话处理方法及相关设备
CN110035437B (zh) 一种用户面数据安全保护方法及装置
CN111107664B (zh) 一种资源管理方法、会话管理功能实体及设备
WO2018120183A1 (zh) 数据传输的方法及装置
CN111200565A (zh) 一种信息传输方法、终端及网络设备
CN109792407B (zh) 服务质量等级指示结构及对应的控制器和控制方法
WO2021138878A1 (zh) 侧行链路承载的管理方法、装置、终端和介质
WO2021003617A1 (zh) 数据传输方法、装置和终端

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17909069

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 122023008185

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 2019561743

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112019023333

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 20197036331

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2017909069

Country of ref document: EP

Effective date: 20191209

ENP Entry into the national phase

Ref document number: 112019023333

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20191106