CN114071574A - QoS flow control method and communication device - Google Patents

QoS flow control method and communication device Download PDF

Info

Publication number
CN114071574A
CN114071574A CN202010769550.5A CN202010769550A CN114071574A CN 114071574 A CN114071574 A CN 114071574A CN 202010769550 A CN202010769550 A CN 202010769550A CN 114071574 A CN114071574 A CN 114071574A
Authority
CN
China
Prior art keywords
network element
qos flow
pdb
session management
management network
Prior art date
Legal status (The legal status 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 status listed.)
Granted
Application number
CN202010769550.5A
Other languages
Chinese (zh)
Other versions
CN114071574B (en
Inventor
李永翠
倪慧
孙海洋
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN202010769550.5A priority Critical patent/CN114071574B/en
Priority to PCT/CN2021/094349 priority patent/WO2022022014A1/en
Publication of CN114071574A publication Critical patent/CN114071574A/en
Application granted granted Critical
Publication of CN114071574B publication Critical patent/CN114071574B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/10Flow control between communication endpoints
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/16Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The present application provides a QoS flow control method and apparatus, where the QoS flow control method may include: the method comprises the steps that an intermediate session management network element determines to shunt a first service flow in a first QoS flow, wherein the first QoS flow comprises at least two service flows, and the at least two service flows comprise the first service flow; the intermediate session management network element binds the first service flow to a second QoS flow and allocates a QoS flow identifier for the second QoS flow; and the intermediate session management network element sends the QoS flow identifier to the anchor point session management network element. By adopting the embodiment of the application, the first QoS flow and the first service flow which is divided from the first QoS flow can be conveniently managed, and the anchor point session management network element can be prevented from distributing repeated QoS flow identifications.

Description

QoS flow control method and communication device
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a QoS flow control method and a communications apparatus.
Background
In a session management network element (SMF) and user plane network element (UPF) topology enhancement (enhanced topology of SMF and UPF in 5G networks, ETSUN) scenario in a 5G network, when a terminal device is far away from a server to be accessed along with the movement of the terminal device, an intermediate user plane network element is inserted, but the intermediate user plane network element is not in a service area of an anchor point session management network element, where the service area of the anchor point session management network element refers to the sum of service areas of all user plane network elements controlled by the anchor point session management network element, and then the intermediate session management network element for controlling the intermediate user plane network element is inserted. The terminal equipment establishes session with the data network for communication through the intermediate user plane network element and the anchor point user plane network element controlled by the anchor point session management network element. While quality of service (QoS) flows are the finest QoS differentiation granularity in a session, there is no perfect mechanism to implement offloading of QoS flows in a session in an ETSUN scenario in the prior art.
Disclosure of Invention
The embodiment of the application provides a QoS flow control method and a communication device, which can conveniently manage a first QoS flow and a first service flow branched from the first QoS flow, and can avoid anchor point session management network elements from distributing repeated QoS flow identifications.
In a first aspect, an embodiment of the present application provides a QoS flow control method, which may be applied to a communication system, where the communication system may include an intermediate session management network element and an anchor session management network element. The method may be performed by an intermediate session management network element in the communication system, or may be performed by a component (e.g., a processor, a chip, or a system-on-a-chip) of the intermediate session management network element. The QoS flow control method may include: the intermediate session management network element determines to split a first traffic flow of the first QoS flows, where the first QoS flow may include at least two traffic flows, and the at least two traffic flows include the first traffic flow.
The intermediate session management network element further binds the first service flow from the first QoS flow to a second QoS flow and allocates a QoS flow identifier to the second QoS flow. The intermediate session management network element sends the QoS flow identifier allocated to the second QoS flow to the anchor point session management network element, and the anchor point session management network element can avoid allocating the QoS flow identifier that is duplicated with the QoS flow identifier of the second QoS flow in the subsequent QoS flow identifier allocation process.
By implementing the method described in the first aspect, the intermediate session management network element binds the first traffic flow that flows out from the first QoS flow to the second QoS flow, and allocates a QoS flow identifier to the second QoS flow, so that the first QoS flow and the first traffic flow that flows out from the first QoS flow can be managed very conveniently, for example, CN PDBs corresponding to the two QoS flows are managed respectively. And the intermediate session management network element sends the QoS flow identifier allocated to the second QoS flow to the anchor point session management network element, which can also avoid the anchor point session management network element from allocating repeated QoS flow identifiers.
In a possible implementation manner of the first aspect, the intermediate session management Network element may determine a Core Network Packet Delay Budget (CN PDB) corresponding to the second QoS flow, and send the CN PDB corresponding to the second QoS flow to the access Network device.
Specifically, optionally, the intermediate session management network element may determine, according to the first CN PDB corresponding to the second QoS flow and the second CN PDB corresponding to the second QoS flow, the CN PDB corresponding to the second QoS flow. The first CN PDB corresponding to the second QoS flow may be a CN PDB between the access network device through which the user plane of the second QoS flow passes and an intermediate user plane network element, and the intermediate user plane network element is connected to the intermediate session management network element. Illustratively, the intermediate user plane network element may be an intermediate user plane network element connected to the access network device.
The second CN PDB corresponding to the second QoS flow may be a CN PDB between the intermediate user plane network element through which the user plane connection of the second QoS flow passes and the anchor user plane network element, and the anchor user plane network element may be an anchor session management network element into which the intermediate session management network element is inserted for the branched first service flow. The anchor user plane network element is connected with the intermediate session management network element and is controlled by the intermediate session management network element.
For example, when the access network device sends the CN PDB corresponding to the second QoS flow to the access network device, the access network device may send the correspondence between the QoS flow identifier of the second QoS flow and the CN PDB corresponding to the second QoS flow to the access network device. Correspondingly, the access network device may determine, according to the 5G QoS identifier (5G QoS identifier, 5QI) of the second QoS flow, a Packet Delay Budget (PDB) corresponding to the second QoS flow, and further determine, according to the PDB corresponding to the second QoS flow and the CN PDB corresponding to the second QoS flow, AN access network packet delay budget (AN PDB) corresponding to the second QoS flow.
By implementing the method, the intermediate session management network element can determine the CN PDB corresponding to the second QoS flow and send the CN PDB to the access network equipment, so that the access network equipment can conveniently identify the QoS flow corresponding to the CN PDB, and the access network equipment can conveniently determine the AN PDB corresponding to the second QoS flow.
In a possible implementation manner of the first aspect, the intermediate session management network element receives indication information from the anchor session management network element, where the indication information may be used to instruct the intermediate session management network element to bind the first service flow to the second QoS flow; or, the indication information may indicate the middle session management network element to distribute the first service flow; or, the indication information may further indicate the middle session management network element to allocate the QoS flow identifier for the second QoS flow; alternatively, the indication information may include a Service Data Flow (SDF) identifier of the first service flow, and the like.
By implementing the method, the anchor session network element can send the indication information to the intermediate session management network element to indicate that the first service flow is shunted without the intermediate session management network element making a decision, thereby reducing the load of the intermediate session management network element.
In a second aspect, an embodiment of the present application provides a QoS flow control method, which may be applied to a communication system, where the communication system may include an intermediate session management network element and an anchor session management network element. The method may be performed by the first session managing network element, or may be performed by a component (e.g., a processor, a chip, or a system-on-a-chip) of the first session managing network element. The first session management network element may be an intermediate session management network element or an anchor session management network element in the communication system. The QoS flow control method may include: the first session management network element obtains a first CN PDB corresponding to the QoS flow, where the first CN PDB may be a CN PDB between the access network device and an intermediate user plane network element, and the intermediate session management network element is connected to the intermediate user plane network element. Optionally, the intermediate user plane network element may be an intermediate user plane network element connected to the access network device.
And the first session management network element acquires a second CN PDB corresponding to the QoS flow, wherein the second CN PDB is a CN PDB between the intermediate user plane network element and the anchor user plane network element. Wherein, the anchor point conversation management network element is connected with the anchor point user plane network element.
The access network device, the intermediate user plane network element, and the anchor user plane network element may be network elements through which a user plane connection of a QoS flow passes.
Further, the first session management network element determines a CN PDB corresponding to the QoS flow according to the first CN PDB corresponding to the QoS flow and the second CN PDB corresponding to the QoS flow.
Wherein, when the first session management network element is an anchor session management network element, the acquiring, by the first session management network element, the first CN PDB corresponding to the QoS flow includes: the first session management network element receives a first CN PDB corresponding to the QoS flow from the intermediate session management network element. Or, when the first session management network element is an intermediate session management network element, the acquiring, by the first session management network element, the second CN PDB corresponding to the QoS flow includes: and the first session management network element receives a second CN PDB corresponding to the QoS flow from the anchor session management network element.
By implementing the method described in the second aspect, it may be implemented that the intermediate session management network element or the anchor session management network element determines the CN PDB corresponding to the QoS flow in the ETSUN scenario.
In a possible implementation manner of the second aspect, the first session management network element may further send a CN PDB corresponding to the QoS flow to the access network device. Correspondingly, the access network device may determine the PDB corresponding to the QoS flow according to the 5QI of the QoS flow, and further determine the AN PDB corresponding to the QoS flow according to the PDB corresponding to the QoS flow and the CN PDB corresponding to the QoS flow.
By implementing the method, the access network equipment can conveniently and accurately determine the AN PDB corresponding to the QoS flow.
In one possible implementation manner of the second aspect, the CN PDB corresponding to the QoS flow is equal to the sum of the first CN PDB corresponding to the QoS flow and the second CN PDB corresponding to the QoS flow.
In a possible implementation manner of the second aspect, the first session management network element is an anchor session management network element, and a manner in which the anchor session management network element receives the first CN PDB corresponding to the QoS flow from the intermediate session management network element may be that the anchor session management network element may receive a first message from the intermediate session management network element, where the first message may include the first CN PDB corresponding to the QoS flow.
Optionally, the intermediate session management network element may send the first CN PDB corresponding to the QoS flow to the anchor session management network element through the first message in the session modification flow, the Xn or N2 handover flow, or the service request flow. Illustratively, the first message may be a session update request message.
By implementing the method, the intermediate session management network element may send the first CN PDB corresponding to the QoS flow to the anchor session management network element, for example, in a session modification flow, an Xn or N2 handover flow, or a service request flow, and determine the CN PDB corresponding to the QoS flow by the anchor session management network element. Therefore, the CN PDB corresponding to the QoS flow is rapidly determined by the anchor point session management network element in the ETSUN scene, and the CN PDB determining efficiency is improved.
In a possible implementation manner of the second aspect, the first session management network element is an anchor session management network element, and the anchor session management network element may receive the first CN PDB corresponding to the QoS flow from the intermediate session management network element in a manner that the anchor session management network element may receive a second message from the intermediate session management network element, where the second message includes a correspondence between at least one 5G QoS identifier 5QI associated with the first topology and at least one first CN PDB, and optionally, the correspondence may be issued in a form of a list, and one 5QI corresponds to one first CN PDB. The first topology comprises a combination of topologies between the access network device and an intermediate user plane network element through which the user plane connection for the QoS flow passes. The intermediate user plane network element may be an intermediate user plane network element connected to the access network device.
Optionally, the intermediate session management network element may send the correspondence to the anchor session management network element through a second message in the session establishment procedure. Illustratively, the second message may be a session creation request message.
The anchor session management network element may determine the first CN PDB corresponding to the QoS flow according to the 5QI of the QoS flow and the corresponding relationship. For example, the anchor session management network element selects a first CN PDB corresponding to a 5QI of the QoS flow from the correspondence as a first CN PDB corresponding to the QoS flow.
By implementing the method, the determination of the CN PDB corresponding to the QoS flow by the anchor point session management network element in the session establishment process can be realized.
In a possible implementation manner of the second aspect, the first session management network element is an intermediate session management network element, and the manner in which the intermediate session management network element receives the second CN PDB corresponding to the QoS flow from the anchor session management network element may be that the intermediate session management network element receives a third message from the anchor session management network element, where the third message includes the second CN PDB corresponding to the QoS flow.
Optionally, the anchor session management network element may send the second CN PDB corresponding to the QoS flow to the intermediate session management network element through the third message in the session establishment procedure, the session modification procedure, the Xn or N2 handover procedure, or the service request procedure. For example, if the anchor session management network element sends the second CN PDB corresponding to the QoS flow to the intermediate session management network element in the session establishment procedure, the third message may be a session creation response message. If the anchor session management network element sends the second CN PDB corresponding to the QoS flow to the intermediate session management network element in another flow, the third message may be a session update response message.
By implementing the method, the anchor session management network element may send the second CN PDB corresponding to the QoS flow to the intermediate session management network element, for example, in a session creation procedure, or a session modification procedure, or an Xn or N2 handover procedure or a service request procedure, and determine the CN PDB corresponding to the QoS flow by the intermediate session management network element. Therefore, the CN PDB corresponding to the QoS flow is quickly determined by the middle session management network element in the ETSUN scene, and the CN PDB determining efficiency is improved.
In a third aspect, an embodiment of the present application provides a QoS flow control method, where the QoS flow control method may be applied to a communication system, and the communication system may include an access network device, an intermediate session management network element, and an anchor session management network element. The method may be performed by the access network device, or may be performed by a component (e.g., a processor, a chip, or a system-on-a-chip) of the access network device. The QoS flow control method may include: the access network equipment receives a first CN PDB corresponding to the QoS flow from the intermediate session management network element, and receives a second CN PDB corresponding to the QoS flow from the anchor session management network element, wherein the first CN PDB is a CN PDB between the access network equipment and the intermediate user plane network element, and the second CN PDB is a CN PDB between the intermediate user plane network element and the anchor user plane network element. The intermediate session management network element is connected with the intermediate user plane network element, and the anchor session management network element is connected with the anchor user plane network element.
For example, the anchor session management network element determines a first CN PDB corresponding to the QoS flow, and sends a second CN PDB corresponding to the QoS flow to the intermediate session management network element, for example, the anchor session management network element may send the second CN PDB corresponding to the QoS flow to the intermediate session management network element through a session creation response message or a session update response message. Further, the intermediate session management network element determines a second CN PDB corresponding to the QoS flow, and sends the second CN PDB corresponding to the QoS flow and the first CN PDB corresponding to the QoS flow received from the anchor session management network element to the access network device.
The access network equipment can determine the PDB corresponding to the QoS flow according to the 5QI of the QoS flow; further, the access network equipment determines the AN PDB corresponding to the QoS flow according to the first CN PDB corresponding to the QoS flow, the second CN PDB corresponding to the QoS flow and the PDB corresponding to the QoS flow.
By implementing the method described in the third aspect, the intermediate session management network element sends the first CN PDB corresponding to the QoS flow to the access network device, and the anchor session management network element sends the second CN PDB corresponding to the QoS flow to the access network device, so that the access network device accurately determines the AN PDB corresponding to the QoS flow.
In a possible implementation manner of the third aspect, the AN PDB corresponding to the QoS flow is equal to a value obtained by subtracting the first CN PDB corresponding to the QoS flow from the PDB corresponding to the QoS flow, and subtracting the second CN PDB corresponding to the QoS flow.
In a fourth aspect, an embodiment of the present application provides a communication apparatus, which includes various modules or units for performing the method of any one of the first to third aspects.
In a fifth aspect, an embodiment of the present application provides a communication apparatus, including a processor. The processor is coupled to the memory and is operable to execute instructions in the memory to implement the method of any of the first to third aspects described above. Optionally, the communication device further comprises a memory. Optionally, the communication device further comprises a communication interface, the processor being coupled to the communication interface.
In a sixth aspect, an embodiment of the present application provides a processor, including: input circuit, output circuit and processing circuit. The processing circuit is configured to receive a signal via the input circuit and transmit a signal via the output circuit, such that the processor performs the method of any of the first to third aspects.
In a specific implementation process, the processor may be one or more chips, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a flip-flop, various logic circuits, and the like. The input signal received by the input circuit may be received and input by, for example and without limitation, a receiver, the signal output by the output circuit may be output to and transmitted by a transmitter, for example and without limitation, and the input circuit and the output circuit may be the same circuit that functions as the input circuit and the output circuit, respectively, at different times. The embodiment of the present application does not limit the specific implementation manner of the processor and various circuits.
In a seventh aspect, an embodiment of the present application provides a processing apparatus, which includes a processor and a memory. The processor is configured to read instructions stored in the memory and to receive signals via the receiver and transmit signals via the transmitter to perform the method of any of the first to third aspects.
Optionally, the number of the processors is one or more, and the number of the memories is one or more.
Alternatively, the memory may be integral to the processor or provided separately from the processor.
In a specific implementation process, the memory may be a non-transient memory, such as a Read Only Memory (ROM), which may be integrated on the same chip as the processor, or may be separately disposed on different chips.
It should be understood that the relevant data interaction procedure, such as sending a CN PDB, may be a procedure of outputting the CN PDB from the processor, and receiving the CN PDB may be a procedure of receiving the CN PDB for the processor. In particular, data output by the processor may be output to a transmitter and input data received by the processor may be from a receiver. The transmitter and receiver may be collectively referred to as a transceiver, among others.
The processing means in the seventh aspect may be one or more chips. The processor in the processing device may be implemented by hardware or may be implemented by software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory, which may be integrated with the processor, located external to the processor, or stand-alone.
In an eighth aspect, an embodiment of the present application provides a computer program product, where the computer program product includes: a computer program (which may also be referred to as code, or instructions), which when executed, causes a computer to perform the method of any of the first to third aspects described above.
In a ninth aspect, the present application provides a readable storage medium storing a computer program (which may also be referred to as code or instructions) which, when executed on a computer, causes the method of any one of the first to third aspects to be implemented.
In a tenth aspect, an embodiment of the present application provides a communication system, which includes the foregoing intermediate session management network element and anchor point session management network element.
Optionally, the communication system may further include an access network device.
In an eleventh aspect, a chip system is provided, which includes a processor and an interface circuit, wherein the processor is configured to call up and execute a computer program (also referred to as code or instructions) stored in the memory to realize the functions of any one of the first to third aspects, and in a possible design, the chip system further includes a memory for storing necessary program instructions and data. The chip system may be formed by a chip, or may include a chip and other discrete devices.
Drawings
Fig. 1 is a 5G system architecture diagram in an ETSUN scenario provided in the present application;
fig. 2a to 2b are network architecture diagrams applicable to the embodiment of the present application;
fig. 3 is a flow chart illustrating a QoS flow control method provided in the present application;
fig. 4 is a schematic flow chart of a specific example of a QoS flow control method provided herein;
fig. 5 is a flow chart illustrating a QoS flow control method provided in the present application;
fig. 6 is a schematic flow chart of a specific example of a QoS flow control method provided herein;
fig. 7 is a flow chart illustrating a QoS flow control method provided in the present application;
fig. 8 is a schematic flow chart of a specific example of a QoS flow control method provided herein;
fig. 9 is a flow chart illustrating a QoS flow control method provided in the present application;
fig. 10 is a schematic flow chart of a specific example of a QoS flow control method provided herein;
fig. 11 is a schematic block diagram of a communication device provided by an embodiment of the present application;
fig. 12 is a schematic block diagram of another communication device provided by an embodiment of the present application;
fig. 13 is a schematic structural diagram of a chip according to an embodiment of the present application.
Detailed Description
The technical scheme of the embodiment of the application can be applied to various communication systems, for example: long Term Evolution (LTE) system, Universal Mobile Telecommunications System (UMTS), fifth generation (5G) system, New Radio (NR) system, and other new systems that appear with the development of technology.
Fig. 1 shows a schematic diagram of a 5G system that can be applied in the ETSUN scenario of the present application. As shown in fig. 1, the system can be divided into two parts, an access network and a core network. The access network is used for implementing functions related to wireless access, and mainly includes AN Access Network (AN) device, which may be a Radio Access Network (RAN) device and other devices (such as WiFi) accessing through AN air interface. The core network mainly comprises the following key logic network elements: user Plane Function (UPF), Intermediate user plane function (I-UPF), access and mobility management function (AMF), Session Management Function (SMF), Intermediate session management function (I-SMF), Policy Control Function (PCF), unified data management function (UDM). The system may further include a User Equipment (UE), a Data Network (DN), and an Application Function (AF). The interfaces between the network elements are shown in figure 1. It should be understood that the network elements may also communicate using a service interface.
It is understood that the system architecture may include at least one I-UPF, and at least one I-SMF, illustrated as including one I-UPF and one I-SMF.
A UE may also be referred to as a terminal device. The terminal device may communicate with one or more Core Networks (CNs) via the AN device. A terminal device may be called an access terminal, subscriber unit, subscriber station, mobile, remote station, remote terminal, mobile device, user terminal, wireless network device, user agent, or user equipment. The terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capability, a computing device or other device connected to a wireless modem, a vehicle-mounted device, a wearable device or internet of things, a terminal device in a vehicle network, a terminal device in a future network in any form, and so on.
The AN device is a device for accessing a terminal device to a wireless network, and may specifically be a base station. The base stations may include various forms of base stations, such as: macro base stations, micro base stations (also referred to as small stations), relay stations, access points, etc. The method specifically comprises the following steps: an Access Point (AP) in a Wireless Local Area Network (WLAN), a Base Transceiver Station (BTS) in a global system for mobile communications (GSM) or Code Division Multiple Access (CDMA), a base station (NodeB, NB) in a Wideband Code Division Multiple Access (WCDMA), an Evolved Node B (eNB, or eNodeB) in LTE, or a relay station or access point, or a base station in a vehicle-mounted device, a wearable device, and a next generation Node B (the next generation Node B, G NB) in a 5G system, or a base station in a future Evolved Public Land Mobile Network (PLMN) network, and the like.
The UDM has functions of managing subscription data of a user, generating authentication information of the user, and the like.
The AMF is mainly responsible for registration management of the UE, connection management of the UE, reachability management of the UE, access authorization and authentication of the UE, security function of the UE, mobility management of the UE, network slice (network slice) selection, SMF selection, and other functions. The AMF serves as an anchor point of the N1/N2 interface signaling connection and provides the SMF with the routing of the N1/N2 interface Session Management (SM) message, and maintains and manages the state information of the UE. The AMF is a mobility management network element in a 5G system.
The SMF is mainly responsible for all control plane functions of UE session management, including selection and control of UPF, address allocation and management of Internet Protocol (IP), quality of service (QoS) management of a session, Policy and Charging Control (PCC) policy acquisition from a PCF, and the like. SMF also serves as a termination point for the SM part of non-access stratum (NAS) messages.
The I-SMF is mainly responsible for the functions of selection, control and the like of the I-UPF.
The PCF has functions such as providing policy rules to the control plane functional entity.
The AF, which may be an application server, may belong to the operator or to a third party.
The UPF is mainly responsible for processing user packets, such as forwarding and charging, and may be used as an anchor point connected to a Protocol Data Unit (PDU) session (session), that is, a PDU session anchor Point (PSA), and is responsible for filtering, data transmission/forwarding, rate control, generating charging information, processing a user plane QoS, performing uplink transmission authentication, verifying a transmission level, caching a downlink packet, triggering a downlink data notification, and the like, of a data packet of the UE. The UPF may also serve as a branch point for a multi-homed PDU session.
The I-UPF is mainly responsible for intermediate forwarding of the message.
DN, a network providing data transmission services to users, such as IP Multimedia Services (IMS), internet, etc. The DN may include an Application Server (AS), which is a software framework and provides an environment for running an application program, and is used to provide services such AS security, data, transaction support, load balancing large distributed system management, and the like for the application program. And the UE acquires the application message through communication with the AS. The AF is a control plane of the AS.
It should be understood that the embodiments of the present application are not limited to be applied only to the system architecture shown in fig. 1. For example, a communication system to which the session management method of the embodiment of the present application may be applied may include more or fewer network elements or devices. The devices or network elements in fig. 1 may be hardware, or may be functionally divided software, or a combination of the two. The devices or network elements in fig. 1 may communicate with each other through other devices or network elements.
Referring to fig. 2a, which is a simplified system architecture diagram applicable to the present application, as shown in the figure, the system architecture includes a terminal device, an access network device, an intermediate user plane network element, an anchor user plane network element, a data network, an access and mobility management device, an intermediate session management network element, and an anchor session management network element. The intermediate user plane network element in the embodiment of the present application may refer to a user plane network element connected to an access network device, where the intermediate user plane network element is connected to and controlled by an intermediate session management network element. The anchor user plane network element of the embodiment of the present application may refer to a user plane network element connected to a data network, and the anchor user plane network element is connected to and controlled by the anchor session management network element. It can be understood that one or more intermediate user plane network elements may exist between the access network device and the anchor user plane network element, and the embodiment of the present application is not limited thereto.
The first CN PDB in this embodiment may refer to a CN PDB between the access network device and the intermediate user plane network element, and the second CN PDB may refer to a CN PDB between the intermediate user plane network element and the anchor user plane network element.
Alternatively, in fig. 2a, the access network device may be the RAN in fig. 1, the intermediate user plane network element may be the I-UPF connected to the RAN in fig. 1, and the intermediate session management network element may be the I-SMF in fig. 1, and the I-UPF is controlled by the I-SMF. The anchor user plane network element may be a UPF in fig. 1 connected to the SMF, and the anchor session management network element may be the SMF in fig. 1, the UPF being controlled by the SMF. Accordingly, the first CN PDB may refer to an N3CN PDB between the RAN and the I-UPF, and the second CN PDB may refer to an N9 CN PDB between the I-UPF and the UPF.
In fig. 2a, the network element through which the user plane connection of the QoS flow passes in the session may be the network element through which path 1 passes, and in some optional scenarios, one or more traffic flows in the QoS flow may be shunted to the local route by means of shunting. As shown in fig. 2b, the intermediate session management network element decides to insert a Local PDU session anchor UPF (Local psauff) as another anchor user plane network element, which is abbreviated as L-UPF in the following embodiments for convenience of description. The intermediate session management network element inserts a shunting point to realize that one or more service flow in the QoS flow are shunted and sent to the local session anchor point user plane network element. In the offloading scenario, the same session of the terminal device has a plurality of different anchor user plane network elements, as shown in fig. 2b, the same session has an anchor user plane network element 1 and an anchor user plane network element 2. The messages of different service flows of the same session can be distributed to different anchor point user plane network elements. As shown in fig. 2b, the messages of different service flows of the same session may be sent to the anchor user plane network element 1 through the path 1, and sent to the anchor user plane network element 2 through the path 2.
Wherein, this shunting point can have two kinds of realization: (1) a Branch Point (BP) mode, that is, a BP is inserted into the user plane path 1 to implement the branch point; (2) the uplink classifier (ULCL) approach, i.e., inserting a ULCL implementation on the user plane path 1. It is to be understood that the shunting point may be an intermediate user plane network element through which the user plane connection of the QoS flow passes, or may be a new intermediate user plane network element reselected by the intermediate session management network element.
A session of the terminal equipment is provided with a plurality of anchor point user plane network elements, and for an Uplink (UL), a shunting point sends a received UL service flow to different anchor point user plane network elements according to a forwarding rule; for Downlink (DL) traffic, the shunting point sends the DL traffic to the UE according to the forwarding rule.
Before describing the method of the present application in detail, a brief description of some concepts involved in the present application will be provided.
1. QoS flows (e.g., QoS Flow)
One PDU session may include one or more QoS flows. In a 5G system, a QoS Flow Identity (QFI) is used to identify a QoS flow; the user plane data with the same QFI in the PDU session will get the same forwarding process (e.g. same scheduling, same admission threshold, etc.).
The QoS flow may be SMF controlled, which may be pre-configured or established through a PDU session establishment or modification procedure. The SMF may send a QoS rule (e.g., QoS rule) of the QoS flow to the UE, where the QoS rule includes QFI, packet filter set (packet filter set), and the like, and the UE may classify and mark the uplink service flow according to the QoS rule, that is, the terminal device may associate the uplink data with the corresponding QoS flow according to the QoS rule.
The SMF may send a QoS profile (e.g., QoS profile) for the QoS flow to the RAN, the QoS profile containing 5QI, Allocation and Retention Priority (ARP), Guaranteed Flow Bit Rate (GFBR), Maximum Flow Bit Rate (MFBR), and so on. One QoS document corresponds to one QFI. The RAN may control the traffic flow based on the QoS profile.
The resource types of the QoS flow can be divided into the following types: guaranteed Bit Rate (GBR) QoS flows, delay-critical GBR (e.g., delay-critical GBR) QoS flows, and Non-guaranteed bit rate Non-GBRQoS flows.
2. 5G QoS identification (5G QoS identifier, 5QI)
The 5QI is used to indicate the 5G QoS characteristics of the QoS flow, and the 5QI is a scalar used to index a 5G QoS characteristic, which may include at least one of resource type, priority level, PDB, packet error rate, averaging window, and the like.
3、PDB
The PDB refers to the upper delay limit for the transmission of the packet between the terminal equipment and the anchor user plane network element. An anchor user plane network element may refer to a UPF in a 5G system that terminates the N6 interface. The PDB may be used to support scheduling and link layer function configuration, such as setting scheduling priority weights.
Among them, the PDB can be divided into two parts: AN PDB and CN PDB. The AN PDB refers to the upper limit of the time delay of the transmission of the message between the terminal equipment and the access network equipment. The CN PDB refers to the upper limit of the delay for the transmission of the packet between the access network device and the anchor user plane network element. PDB is equal to the sum of AN PDB and CN PDB.
The CN PDB may be configured on the session management network element, and in a session establishment process, a session modification process, a Handover (HO) process, or a service request process, the session management network element may send the CN PDB corresponding to the QoS flow to the access network device, and the access network device may obtain the PDB corresponding to the QoS flow according to the 5QI index of the QoS flow, and further determine the AN PDB corresponding to the QoS flow according to the PDB corresponding to the QoS flow and the CN PDB corresponding to the QoS flow.
The CN PDBs in the embodiment of the present application may include a first CN PDB and a second CN PDB. The first CN PDB may refer to a CN PDB between the access network device and the intermediate user plane network element, and the second CN PDB may refer to a CN PDB between the intermediate user plane network element and the anchor user plane network element. For one QoS flow, the CN PDB is equal to the sum of the first CN PDB and the second CN PDB.
The first CN PDB may be configured on an intermediate session management network element for controlling the intermediate user plane network element, and the second CN PDB may be configured on an anchor session management network element for controlling the anchor user plane network element.
It can be understood that in the embodiment of the present application, the uplink CN PDB and/or the downlink CN PDB may be configured separately, or the CN PDB may also be configured without being configured in uplink and downlink. If the uplink CN PDB and/or the downlink CN PDB are configured, correspondingly, when the uplink AN PDB is determined, the uplink PDB and the uplink CN PDB may be used for calculation. When determining the downlink AN PDB, the downlink PDB and the downlink CN PDB can be adopted for calculation.
Referring to fig. 3, a flowchart of a QoS flow control method provided in an embodiment of the present application is shown, where the embodiment relates to a scenario of offloading in a communication system including an intermediate session management network element and an anchor session management network element, and fig. 2b is a network architecture example of the scenario. As shown in fig. 3, the method may include: s101, S102, S103, optionally, S104, S105, and S106 may also be included. The execution sequence of S101, S102, S103, S104, S105, and S106 is not limited in this embodiment of the application. As shown in the figure, the QoS flow control method of the embodiment of the present application includes, but is not limited to, the following steps:
s101, an intermediate session management network element determines to shunt a first service flow in a first QoS flow, wherein the first QoS flow comprises at least two service flows, and the at least two service flows comprise the first service flow.
In one embodiment, the terminal device establishes a user plane connection for a session, where the session may be a Protocol Data Unit (PDU) session, and the user plane connection may pass through the terminal device, the access network device, the intermediate user plane network element, the anchor user plane network element, and the Data network, and may be, for example, a network element that path 1 in fig. 2b passes through. The terminal equipment can realize the access to the data network through the user plane connection. The intermediate user plane network element may be connected to and controlled by the intermediate session management network element. The anchor user plane network element may be connected to and controlled by the anchor session management network element.
The session may include a first QoS flow, and the first QoS flow may include at least two traffic flows. As the terminal device moves, the intermediate session management network element may determine to offload traffic flows in the first QoS flow when the terminal device moves to a specific location. For example, when detecting that the terminal device moves to a location area corresponding to a Data Network Access Identifier (DNAI), the intermediate session management network element determines to offload a service flow in the first QoS flow. Alternatively, the DNAI may be obtained by the intermediate session management network element from the anchor session management network element.
After the intermediate session management network element determines to offload, the intermediate session management network element may insert a Local session anchor point user plane network element (e.g., Local PSA UPF) as another anchor point user plane network element, and initiate a session establishment procedure to the Local session anchor point user plane network element to establish a control relationship between the intermediate session management network element and the Local session anchor point user plane network element. The intermediate session management network element further selects a shunting point to realize shunting of the traffic flow to the local session anchor point user plane network element. The shunting point may be an intermediate user plane network element through which the user plane connection of the session passes, or an intermediate user plane network element reselected by the intermediate session management network element. If the shunting point is an intermediate user plane network element reselected by the intermediate session management network element, the intermediate session management network element may initiate a session establishment procedure to the shunting point to establish a control relationship between the intermediate session management network element and the shunting point.
For example, the intermediate session management network element may determine to offload the first traffic flow of the first QoS flow according to policy information associated with the session. Or, the intermediate session management network element may receive indication information from the anchor session management network element, and determine to offload the first traffic flow according to the indication information. Optionally, the indication information may indicate that the intermediate session management network element binds the first service flow to the second QoS flow; or, the indication information may indicate the middle session management network element to distribute the first service flow; or, the indication information may further indicate the middle session management network element to allocate the QoS flow identifier for the second QoS flow; alternatively, the indication information may include a Service Data Flow (SDF) identifier of the first service flow, and the like.
Optionally, the anchor session management network element may send the indication information to the intermediate session management network element through a session update response message, and further optionally, the session update response message may further include 5QI, a QoS rule, a QoS document, and the like. Optionally, the 5QI, the QoS rule, the QoS document and the like in the session update response message may correspond to the first traffic flow, for example, the anchor session management network element may determine the 5QI, the QoS rule and the QoS document corresponding to the first traffic flow according to the 5QI, the QoS rule and the QoS document of the first traffic flow. Alternatively, the 5QI, the QoS rule, the QoS document, and the like in the session update response message may correspond to the first QoS flow.
It is to be understood that, before the intermediate session management network element receives the session update response message from the anchor session management network element, the intermediate session management network element may send a session update request message to the anchor session management network element, where the session update request message may include offloading indication information for indicating offloading of the first QoS flow, and for example, the session update request message may include offloading indication information inserted into an offloading point, and the anchor session management network element may determine to offload the first traffic flow according to the offloading indication information. For example, the anchor session management network element may determine to locally split the first traffic flow based on the policy information associated with the session received from the PCF and a list of DNAIs supported by the intermediate session management network element. The policy information associated with the session may specifically be a correspondence between the DNAI and the service flow.
S102, the intermediate session management network element binds the first service flow to a second QoS flow and distributes a QoS flow identification for the second QoS flow;
in one embodiment, the intermediate session management network element performs QoS flow binding (e.g., QoS flow binding) on the first traffic flow, e.g., binds the first traffic flow to the second QoS flow. And the intermediate session management network element allocates the QoS flow identification to the second QoS flow.
Further, the intermediate session managing network element may determine the QoS rules, the QoS profile and the 5QI for the second QoS flow. Optionally, the QoS rules, QoS profiles, and 5QI of the second QoS flow may be determined by the intermediate session management network element based on the 5QI, QoS rules, and QoS profiles received from the anchor session management network element.
Wherein the QoS profile of the second QoS flow may be the same as the QoS profile of the first QoS flow; the QoS rule of the second QoS flow includes a QoS flow identifier of the second QoS flow, a packet filter set (packet filter set) corresponding to the first service flow, and the like.
S103, the intermediate session management network element sends the QoS flow identification to the anchor point session management network element.
In one embodiment, the intermediate session managing network element may send a session update request message to the anchor session managing network element, the session update request message including the QoS flow identification assigned for the second QoS flow. Correspondingly, the anchor point session management network element receives the QoS flow identifier, and subsequently, when QoS flow binding is executed, repeated QFI allocation by the anchor point session management network element can be avoided.
Further optionally, the intermediate session management network element may further send the QoS flow identifier allocated for the second QoS flow to the access network device and the terminal device. For example, the intermediate session managing network element may send the QoS flow identification of the second QoS flow to the terminal device through the N1 SM information in the N1N2 message transmission request, and send the QoS flow identification of the second QoS flow to the access network device through the N2 SM information in the N1N2 message transmission request. The N1 SM information may further include a QoS rule of the second QoS flow sent to the terminal device; the N2 SM information may also include a QoS profile for the second QoS flow sent to the access network device.
And S104, the intermediate session management network element determines the CN PDB corresponding to the second QoS flow.
In one embodiment, the network element through which the user plane connection of the second QoS flow passes may include a terminal device, an access network device, an intermediate user plane network element, and a local session anchor user plane network element, and may be, for example, the network element through which path 2 passes in fig. 2 b. Optionally, the intermediate user plane network element may be a user plane network element connected to the access network device.
Optionally, the intermediate session management network element may determine the CN PDB corresponding to the second QoS flow in the following two ways, which are only examples and do not form a limitation to the present application:
in the first mode, the user plane connection between the access network device and the intermediate user plane network element and the user plane connection between the intermediate user plane network element and the local session anchor point user plane network element are both managed by the intermediate session management network element. The intermediate session management network element may be configured with first CN PDB configuration information and second CN PDB configuration information. The first CN PDB configuration information may include various topology combinations, and a corresponding relationship between each 5QI and each first CN PDB, where the various topology combinations may be topology combinations of each access network device and each intermediate user plane network element controlled by the intermediate session management network element. For example, there may be a topology combination, one 5QI corresponding to one first CN PDB. The second CN PDB configuration information may include various topology combinations, and a corresponding relationship between each 5QI and each second CN PDB, where the various topology combinations may be topology combinations of each intermediate user plane network element controlled by the intermediate session management network element and each local session anchor point user plane network element controlled by the intermediate session management network element. For example, there may be a topology combination, one 5QI for one second CN PDB.
The intermediate session management network element may determine, according to the first CN PDB configuration information, the 5QI of the second QoS flow, and the access network device and the intermediate user plane network element through which the user plane connection of the second QoS flow passes, the first CN PDB corresponding to the second QoS flow. The intermediate session management network element may determine, according to the second CN PDB configuration information, the 5QI of the second QoS flow, and the intermediate user plane network element and the local session anchor point user plane network element through which the user plane connection of the second QoS flow passes, the second CN PDB corresponding to the second QoS flow. The 5QI of the second QoS flow may be from the anchor session management network element, or may be obtained by the intermediate session management network element according to the policy of the session.
Further, the intermediate session management network element may determine, according to the first CN PDB corresponding to the second QoS flow and the second CN PDB corresponding to the second QoS flow, the CN PDB corresponding to the second QoS flow.
The following describes determining a CN PDB corresponding to the second QoS flow by taking, as an example, that the first CN PDB is an N3CN PDB, the second CN PDB is an N9 CN PDB, the intermediate session management network element is an I-SMF, the access network device is a RAN, the intermediate user plane network element is an I-UPF, and the local session anchor point user plane network element is an L-UPF, where the I-SMF may be configured with N3CN PDB configuration information and N9 CN PDB configuration information, where the N3CN PDB configuration information may be shown in table one, and the N9 CN PDB configuration information may be shown in table two.
Figure BDA0002613685350000121
Table one
Figure BDA0002613685350000122
Table two
For example, the user plane connection for the second QoS flow goes through RAN2, I-UPF1, and L-UPF2, and the 5QI for the QoS flow is 5QI2, then the second QoS flow corresponding to N3CN PDB3 can be obtained from the table one index. The second QoS flow correspondence N9 CN PDB3 is derived from the table two index. Further, the I-SMF determines that the CN PDB corresponding to the second QoS flow is the sum of N3CN PDB3 and N9 CN PDB 3.
In the second mode, the user plane connection between the access network device and the intermediate user plane network element and the user plane connection between the intermediate user plane network element and the local session anchor point user plane network element are both managed by the intermediate session management network element. The intermediate session management network element may be configured with CN PDB configuration information, where the CN PDB configuration information may include various topology combinations and corresponding relationships between each 5QI and each CN PDB, and the various topology combinations may be topology combinations between each access network device, each intermediate user plane network element controlled by the intermediate session management network element, and each local session anchor point user plane network element controlled by the intermediate session management network element. For example, there may be one topology combination, one 5QI for one CN PDB.
The intermediate session management network element may determine, according to the CN PDB configuration information, the 5QI of the second QoS flow, and the access network device through which the user plane connection of the second QoS flow passes, the intermediate user plane network element, and the local session anchor point user plane network element, a CN PDB corresponding to the second QoS flow.
Next, the CN PDB corresponding to the second QoS flow is determined by taking the intermediate session management network element as I-SMF, the access network device as RAN, the intermediate user plane network element as I-UPF, and the local session anchor point user plane network element as L-UPF as examples, where CN PDB configuration information may be configured on the I-SMF, and the CN PDB configuration information may be as shown in table three.
Figure BDA0002613685350000123
Table III
For example, the user plane connection for the second QoS flow goes through RAN2, I-UPF1, and L-UPF2, and the 5QI for the QoS flow is 5QI2, then I-SMF gets the second QoS flow corresponding to CN PDB3 from the table three index.
And S105, the intermediate session management network element sends the CN PDB corresponding to the second QoS flow to the access network equipment.
And S106, the access network equipment determines the AN PDB corresponding to the second QoS flow according to the PDB corresponding to the second QoS flow and the CN PDB corresponding to the second QoS flow.
In one embodiment, the intermediate session management network element may send the correspondence between the QoS flow identifier of the second QoS flow and the CN PDB corresponding to the second QoS flow to the access network device. Further optionally, the access network device may determine, according to the 5QI of the second QoS flow, the PDB corresponding to the second QoS flow, and determine, according to the PDB corresponding to the second QoS flow and the CN PDB corresponding to the second QoS flow, the AN PDB corresponding to the second QoS flow.
Further optionally, the intermediate session management network element may also send the correspondence between the QoS flow identifier of the first QoS flow and the CN PDB corresponding to the first QoS flow to the access network device, and the access network device determines the AN PDB corresponding to the first QoS flow. The CN PDB corresponding to the first QoS flow may be determined by an intermediate session management network element, and may specifically refer to the descriptions in the embodiments of fig. 7 and fig. 8. Alternatively, the CN PDB corresponding to the first QoS flow may also be determined by the anchor session management network element, which may specifically refer to the descriptions in the embodiments of fig. 5 and fig. 6.
Or, the intermediate session management network element may send the first CN PDB corresponding to the first QoS flow to the access network device, and the anchor session management network element sends the second CN PDB corresponding to the first QoS flow to the access network device, and the access network device determines the AN PDB corresponding to the first QoS flow, which may specifically refer to the description in the embodiments of fig. 9 and fig. 10.
The method shown in fig. 3 is described in more detail in connection with fig. 4. For convenience of understanding, in fig. 4, a terminal device is taken as a UE, a mobility management network element is taken as an AMF, an access network device is taken as a RAN, an intermediate session management network element is taken as an I-SMF, an anchor session management network element is taken as an SMF, an intermediate user plane network element is taken as an I-UPF, and an anchor user plane network element is taken as an UPF.
S201, the UE establishes a PDU session. Wherein, the user interface connection of the PDU conversation passes through UE, RAN, I-UPF and UPF. Wherein I-UPF is controlled by I-SMF and UPF is controlled by SMF. The PDU session may include a first QoS flow.
S202, the I-SMF decides to insert a local session anchor user plane network element (e.g., L-UPF) as another anchor user plane network element of the session. The I-SMF selects L-UPF and initiates an N4 session establishment procedure to the L-UPF.
And S203, the I-SMF selects a shunting point, wherein the shunting point can be an I-UPF passed by the user interface connection of the session, or can also be an I-UPF reselected by the I-SMF, and if the shunting point is reselected by the I-SMF, the I-SMF can initiate an N4 session establishment flow to the shunting point.
S204, the I-SMF sends a session update request message to the SMF, where the session update request message may include indication information of the forking point into which the I-SMF is inserted.
The session update request message may correspond to a service interface Nsmf _ pdusesion _ update _ request.
S205, the SMF updates the UPF, that is, the SMF initiates a N4 session modification procedure to the UPF. If the forking point is I-SMF reselected in step S203, the SMF may establish a downlink tunnel between the forking point and the UPF through the N4 session modification procedure. If the split point in step S203 is not I-SMF reselected, the SMF may not initiate the N4 session modification flow to the UPF.
S206, the SMF sends a session update response message to the I-SMF, optionally, the session update response message may include indication information, where the indication information may indicate that the I-SMF shunts the first traffic flow, or the indication information may indicate that the I-SMF binds the first traffic flow to the second QoS flow; or, the indication information may indicate that the I-SMF allocates the QoS flow identifier for the second QoS flow; alternatively, the indication information may further include the service data flow identification SDF1 of the first service flow. The SMF may determine the first traffic flow to be split according to the policy information of the session.
Optionally, the indication information may be N4 information contained in the session update response message, and the I-SMF obtains the indication information by parsing the N4 information, and specifically, the indication information may be an existing parameter in the N4 information, such as the first service flow identifier SDF 1. Illustratively, the session update response message may further include indication information for indicating that the I-SMF parses the N4 information.
It is to be understood that the indication information for indicating that the I-SMF shunts the first traffic flow may not be included in the N4 information, and may be included in the session update response message in parallel with the N4 information, for example.
The session update response message may correspond to the servitization interface Nsmf _ pdusesion _ update _ response.
And S207, the I-SMF determines to distribute the first service flow to the local according to the indication information. Specifically, the I-SMF performs QoS flow binding (e.g., QoS flow binding) for a first traffic flow, thereby binding the first traffic flow to a second QoS flow and assigning a QoS flow identification for the second QoS flow.
At S208, the I-SMF may send the QoS flow identification allocated for the second QoS flow to the SMF, e.g., the I-SMF sends a session update request message to the SMF, the session update request message including the QoS flow identification allocated for the second QoS flow. In the subsequent flow, when the SMF performs QoS flow binding, duplicate QoS flow identifications can be avoided from being assigned.
Further, the I-SMF may determine the CN PDB corresponding to the second QoS flow according to the N3CN PDB configuration information and the N9 CN PDB configuration information, or the I-SMF may determine the CN PDB corresponding to the second QoS flow according to the CN PDB configuration information. The specific determination method may refer to the description of step S104 in fig. 3, and is not described herein again.
S209, the I-SMF initiates an N4 session modification procedure to the L-UPF, for example, the information of the shunting point is sent to the L-UPF through an N4 session modification procedure.
The I-SMF initiates an N4 session modification procedure to the forking point, e.g., instructs the forking point to send the first traffic stream packet to the L-UPF via an N4 session modification procedure.
S210, the I-SMF sends an N1N2 message transmission request to the AMF, wherein the N1N2 message transmission request comprises PDU session identification, N2 SM information and N1 SM information, the N1 SM information refers to information about the session sent by the I-SMF to the UE, and the N2 SM information refers to information about the session sent by the I-SMF to the RAN.
The N1N2 message transmission request may further include a CN PDB corresponding to the second QoS flow. Illustratively, the CN PDB corresponding to the second QoS flow may be included in the N2 SM information.
Optionally, the N2 SM information may further include a session identifier, a QoS flow identifier corresponding to the second QoS flow, a QoS profile corresponding to the second QoS flow, and the like. The N1 SM message may include the QoS rule corresponding to the second QoS flow and the QoS flow identification corresponding to the second QoS flow.
S211, the AMF sends an N2 PDU session request to the RAN, the N2 PDU session request including N2 SM information, NAS message. Wherein the NAS message contains N1 SM information.
And S212, inserting other steps of the flow by the shunting point.
It is to be understood that the execution sequence of the above steps is not limited in this application.
In the embodiments of fig. 5-10, the communication system includes an anchor session management network element that controls an intermediate user plane network element and an intermediate session management network element that controls an anchor user plane network element. The intermediate session management network element is configured with first CN PDB configuration information, where the first CN PDB configuration information may include various topology combinations and a corresponding relationship between each 5QI and each first CN PDB, and the various topology combinations may be topology combinations between each access network device and each intermediate user plane network element controlled by the intermediate session management network element. For example, there may be a topology combination, one 5QI corresponding to one first CN PDB. The anchor session management network element is configured with second CN PDB configuration information, where the second CN PDB configuration information may include various topology combinations and corresponding relations between each 5QI and each second CN PDB, and the various topology combinations may be topology combinations between each intermediate user plane network element and each anchor user plane network element controlled by the anchor session management network element. For example, there may be a topology combination, one 5QI for one second CN PDB.
In the following, the first CN PDB is N3CN PDB, the second CN PDB is N9 CN PDB, the middle session management network element is I-SMF, the anchor session management network element is SMF, the access network device is RAN, the middle user plane network element is I-UPF, and the anchor user plane network element is UPF.
The configuration information of the first CN PDB configured on the I-SMF may be as shown in table four, where the table four includes various topology combinations of each RAN and each I-UPF controlled by the I-SMF, and a corresponding relationship between each 5QI and each N3CN PDB.
Figure BDA0002613685350000151
Table four
The second CN PDB configuration information configured on the SMF may be as shown in table five, where the table five includes various topology combinations of each I-UPF and each UPF controlled by the SMF, and a corresponding relationship between each 5QI and each N9 CN PDB.
Figure BDA0002613685350000152
Table five
Based on the configuration information of the first CN PDB configured on the intermediate session management network element, the configuration information of the second CN PDB configured on the anchor point session management network element. Referring to fig. 5 and fig. 6, the intermediate session management network element may send the first CN PDB corresponding to the QoS flow to the anchor session management network element, and the anchor session management network element determines the CN PDB corresponding to the QoS flow, and optionally, the access network device finally determines the AN PDB corresponding to the QoS flow according to the PDB corresponding to the QoS flow and the CN PDB corresponding to the QoS flow. Alternatively, as shown in fig. 7 and fig. 8, the anchor session management network element may send the second CN PDB corresponding to the QoS flow to the intermediate session management network element, and the intermediate session management network element determines the CN PDB corresponding to the QoS flow, and optionally, the access network device finally determines the AN PDB corresponding to the QoS flow according to the PDB corresponding to the QoS flow and the CN PDB corresponding to the QoS flow. Or, referring to fig. 9 and fig. 10, the intermediate session management network element may send the first CN PDB corresponding to the QoS flow to the access network device, the anchor session management network element sends the second CN PDB corresponding to the QoS flow to the access network device, and finally, the access network device determines the AN PDB corresponding to the QoS flow according to the PDB corresponding to the QoS flow, the first CN PDB corresponding to the QoS flow, and the second CN PDB corresponding to the QoS flow.
The embodiments of fig. 5-10 are described in detail below, respectively. Fig. 2a and fig. 2b may be two network architecture examples for implementing each embodiment, where in the network architecture of the offloading scenario shown in fig. 2b, the QoS flow of the embodiment of the present application may refer to a QoS flow corresponding to path 1.
Referring to fig. 5, a flowchart of a QoS flow control method provided in an embodiment of the present application is shown, where this embodiment relates to a scenario in which an anchor session management network element determines a CN PDB in a communication system including an intermediate session management network element and an anchor session management network element, and as shown in fig. 5, the method may include: s301, S302, S303, optionally, S304 and S305 may also be included. The execution sequence of S301, S302, S303, S304, and S305 is not limited in this embodiment of the application. As shown in the figure, the QoS flow control method of the embodiment of the present application includes, but is not limited to, the following steps:
s301, the middle session management network element sends a first CN PDB corresponding to the QoS flow to the anchor point session management network element, where the first CN PDB is a CN PDB between the access network device and the middle user plane network element, and the middle session management network element is connected to the middle user plane network element.
In the method 1, when the intermediate session management network element obtains the 5QI of the QoS flow, the intermediate session management network element may determine the first CN PDB corresponding to the QoS flow according to the topology combination of the access network device and the intermediate user plane network element through which the user plane connection of the QoS flow passes, the 5QI of the QoS flow, and the first CN PDB configuration information configured on the intermediate session management network element. For example, the intermediate session management network element selects the topology combination and the first CN PDB corresponding to 5QI of the QoS flow from the first CN PDB configuration information as the first CN PDB corresponding to the QoS flow. Wherein, the 5QI for acquiring the QoS flow by the intermediate session management network element may be acquired in the session establishment process. For example, the anchor session management network element sends the 5QI of the QoS flow to the intermediate session management network element, or the intermediate session management network element obtains the 5QI of the QoS flow by parsing the QoS document corresponding to the QoS flow. Further, the intermediate session management network element sends the first CN PDB corresponding to the determined QoS flow to the anchor session management network element.
Further, the intermediate session management network element may send the first CN PDB corresponding to the QoS flow to the anchor session management network element through the first message. The intermediate session management network element may send the first CN PDB corresponding to the QoS flow to the anchor session management network element through a session modification flow, an Xn or N2 handover flow, or a service request flow. Optionally, the first message may be a session Update Request message (e.g., Nsmf _ pdusesion _ Update Request).
Specifically, the first CN PDB is N3CN PDB, the middle session management network element is I-SMF, the anchor session management network element is SMF, the access network device is RAN, the middle user plane network element is I-UPF, and the first CN PDB configuration information configured on the I-SMF is table four. If the user plane connection for the QoS flow passes through the RAN2 and the I-UPF1, and the 5QI of the QoS flow is 5QI2, it is determined that the QoS flow corresponds to N3CN PDB 3. The I-SMF may send the N3CN PDB3 corresponding to the QoS flow to the SMF via a session update request message.
In the manner 2, when the intermediate session management network element does not acquire the 5QI of the QoS flow, the intermediate session management network element may determine, according to the topology combination of the access network device and the intermediate user plane network element through which the user plane connection of the QoS flow passes and the first CN PDB configuration information configured on the intermediate session management network element, the first CN PDB list corresponding to the topology combination. For example, the intermediate session management network element selects the first CN PDB list corresponding to the topology combination from the first CN PDB configuration information. The first CN PDB list may include a correspondence between at least one 5QI and at least one first CN PDB, where one 5QI may correspond to one first CN PDB.
Further, the intermediate session management network element may send the first CN PDB list to the anchor session management network element through a second message. The intermediate session management network element may send the first CN PDB list to the anchor session management network element through a session establishment procedure. Optionally, the second message may be a session creation Request message (e.g., Nsmf _ pdusesion _ Create Request).
Correspondingly, the anchor point session management network element receives the first CN PDB list, and when the anchor point session management network element acquires the policy associated with the session from the PCF, may determine the 5QI of the QoS flow included in the session. And the anchor point session management network element further determines a first CN PDB corresponding to the QoS flow from the first CN PDB list according to the 5QI of the QoS flow.
Specifically, the first CN PDB is N3CN PDB, the middle session management network element is I-SMF, the anchor session management network element is SMF, the access network device is RAN, the middle user plane network element is I-UPF, and the first CN PDB configuration information configured on the I-SMF is table four. If the user plane connection of the QoS flow passes through RAN2 and I-UPF1, since the 5QI of the QoS flow is not acquired, the I-SMF determines a first CN PDB list corresponding to the topology combination of RAN2 and I-UPF1 from table four according to the user plane connection of the QoS flow passing through RAN2 and I-UPF1, where the first CN PDB list includes the correspondence between 5QI1 and N3CN PDB2 and the correspondence between 5QI2 and N3CN PDB 3. The I-SMF may send the first CN PDB list to the SMF via a session creation request message. When the SMF acquires the policy associated with the session from the PCF, if it is determined that 5QI of the QoS flow included in the session is 5QI1, it may be determined from the first CN PDB list that N3CN PDB corresponding to the QoS flow is N3CN PDB 2.
And S302, the anchor point session management network element acquires a second CN PDB corresponding to the QoS flow, wherein the second CN PDB is a CN PDB between the intermediate user plane network element and the anchor point user plane network element, and the anchor point session management network element is connected with the anchor point user plane network element.
In an embodiment, the anchor session management network element may determine the second CN PDB corresponding to the QoS flow according to a topology combination of the intermediate user plane network element through which the user plane connection of the QoS flow passes and the anchor user plane network element, 5QI of the QoS flow, and second CN PDB configuration information configured on the anchor session management network element. For example, the anchor session management network element selects the topology combination and the second CN PDB corresponding to 5QI of the QoS flow from the second CN PDB configuration information as the second CN PDB corresponding to the QoS flow.
Specifically, the second CN PDB is N9 CN PDB, the middle session management network element is I-SMF, the anchor session management network element is SMF, the middle user plane network element is I-UPF, the anchor user plane network element is UPF, and the second CN PDB configuration information configured on the SMF is table five. If the user plane connection of the QoS flow passes through the I-UPF1 and the UPF1, and the 5QI of the QoS flow is 5QI2, it is determined that the QoS flow corresponds to N9 CN PDB 2.
And S303, the anchor point session management network element determines the CN PDB corresponding to the QoS flow according to the first CN PDB corresponding to the QoS flow and the second CN PDB corresponding to the QoS flow.
In one embodiment, the CN PDB for the QoS flow is equal to the sum of the first CN PDB for the QoS flow and the second CN PDB for the QoS flow. For example, the first CN PDB for QoS flow is N3CN PDB3, the second CN PDB for QoS flow is N9 CN PDB2, and the CN PDB for QoS flow is equal to the sum of N3CN PDB3 and N9 CN PDB 2.
Optionally, steps S304 and S305 may also be included.
S304, the anchor point conversation management network element sends the CN PDB corresponding to the QoS flow to the access network equipment.
S305, the access network equipment determines the AN PDB corresponding to the QoS flow according to the PDB corresponding to the QoS flow and the CN PDB corresponding to the QoS flow.
In an embodiment, the anchor session management network element may send the CN PDB corresponding to the QoS flow to the intermediate session management network element through a session creation Response message (e.g., Nsmf _ pduse _ Create Response) in the session establishment procedure. Optionally, the CN PDB corresponding to the QoS flow may be included in a QoS profile (QoS profile) in the session creation response message. Or, the anchor session management network element may also send the CN PDB corresponding to the QoS flow to the intermediate session management network element through a session Update Response message (for example, Nsmf _ pdussion _ Update Response) in the session modification flow, the Xn or N2 handover flow, or the service request flow.
The intermediate session management network element may send the CN PDB corresponding to the QoS flow to the access network device. The access network device may obtain the PDB corresponding to the QoS flow according to the 5QI of the QoS flow. Further, the access network equipment determines the AN PDB corresponding to the QoS flow according to the PDB corresponding to the QoS flow and the CN PDB corresponding to the QoS flow.
The method shown in fig. 5 is described in more detail in connection with fig. 6. For convenience of understanding, in fig. 6, a terminal device is taken as a UE, a mobility management network element is taken as an AMF, an access network device is taken as a RAN, an intermediate session management network element is taken as an I-SMF, an anchor session management network element is taken as an SMF, an intermediate user plane network element is taken as an I-UPF, and an anchor user plane network element is taken as an UPF.
For example, the first CN PDB configuration information configured on the I-SMF may be as shown in table four. The second CN PDB configuration information configured on the SMF may be as shown in table five.
S401, the UE sends a session establishment request message to the AMF, where the session establishment request message may be included in a non-access stratum (NAS) transport message, and the NAS transport message may further include a UE ID and a PDU session identifier.
S402, AMF selects I-SMF and SMF. AMF sends a request message for creating session management context to I-SMF, wherein the request message for creating session management context comprises UE ID, PDU session identification, session establishment request message and SMF ID. The create session management context request message may correspond to a servitization interface Nsmf pdusesion _ createsmcontextrequest.
S403, the I-SMF sends a create session management context response message to the AMF. The create session management context response message may correspond to the servitization interface Nsmf pdusesion _ createsmcontextresponse.
S404, selecting I-UPF by the I-SMF; the I-SMF initiates an N4 session creation process to the selected I-UPF.
S405, the I-SMF sends a session creation request message to the SMF, the session creation request message including the UE ID, the I-SMF ID, the selected I-UPF ID, the PDU session identification, and an N3CN PDB list, the N3CN PDB list may be determined by the I-SMF according to the RAN and I-UPF through which the user plane connection of the QoS flow passes. For example, the I-SMF selects from table four the N3CN PDB list corresponding to the topological combination of RAN and I-UPF through which the user plane connection for the QoS flow passes.
The session creation request message may correspond to a serving interface Nsmf _ pdusesion _ Create request.
S406, SMF initiates a session management policy association establishment flow to PCF to obtain the policy associated with the session. The SMF acquires the 5QI of the QoS flow contained in the session according to the policy associated with the session. It is to be appreciated that the session can include at least one QoS flow, and the SMF can obtain 5 QIs for one or more QoS flows of the at least one QoS flow, respectively.
S407, the SMF selects the N3CN PDB corresponding to the QoS flow from the N3CN PDB list according to the 5QI of the QoS flow.
S408, the SMF selects a UPF and initiates an N4 session creation procedure to the selected UPF.
S409, the SMF determines the N9 CN PDB corresponding to the QoS flow according to the I-UPF and UPF topological combination passed by the user interface connection of the QoS flow and the 5QI of the QoS flow. For example, the SMF selects from table five the topological combination of I-UPF and UPF through which the user plane connection for the QoS flow passes and the N9 CN PDB corresponding to the 5QI for the QoS flow.
Further, the SMF determines the CN PDB corresponding to the QoS flow according to the N3CN PDB corresponding to the QoS flow and the N9 CN PDB corresponding to the QoS flow.
Wherein CN PDB is N3CN PDB + N9 CN PDB.
S410, the SMF sends a session creation response message to the I-SMF, wherein the session creation response message comprises the QoS rule of the QoS flow, the QoS document of the QoS flow, the QoS flow identification of the QoS flow and the CN PDB corresponding to the QoS flow. Optionally, the CN PDB corresponding to the QoS flow may also be included in the QoS document of the QoS flow.
S411, the I-SMF sends an N1N2 message transmission request to the AMF, and the N1N2 message transmission request carries PDU session identification, N2 SM information and N1 SM information. Wherein, the N1 SM information refers to information related to the session sent by the I-SMF to the UE, and the N2 SM information refers to information related to the session sent by the I-SMF to the RAN.
The N1N2 message transmission request may further include a CN PDB corresponding to the QoS flow. Illustratively, the N2 SM information may include CN PDBs corresponding to QoS flows.
The N2 SM information may also include session identification, QoS flow identification corresponding to the QoS flow, QoS profile corresponding to the QoS flow, etc. The N1 SM information may include QoS rules corresponding to QoS flows.
The AMF sends an N2 PDU session request to the RAN S412, the N2 PDU session request including N2 SM information, NAS message. Wherein the NAS message contains N1 SM information.
S413, other steps of the session establishment procedure. Such as air interface resource establishment, core network user plane path update, etc.
It is to be understood that the execution sequence of the above steps is not limited in this application.
Referring to fig. 7, a flowchart of a QoS flow control method provided in an embodiment of the present application is shown, where this embodiment relates to a scenario in which an intermediate session management network element determines a CN PDB in a communication system including the intermediate session management network element and an anchor session management network element, and as shown in fig. 7, the method may include: s501, S502, and S503, optionally, may further include S504 and S505. The execution sequence of S501, S502, S503, S504, and S505 is not limited in this embodiment of the application. As shown in the figure, the QoS flow control method of the embodiment of the present application includes, but is not limited to, the following steps:
s501, the anchor point session management network element sends the second CN PDB corresponding to the QoS flow to the middle session management network element.
In an embodiment, the anchor session management network element may determine the second CN PDB corresponding to the QoS flow according to a topology combination of the intermediate user plane network element through which the user plane connection of the QoS flow passes and the anchor user plane network element, 5QI of the QoS flow, and second CN PDB configuration information configured on the anchor session management network element. For example, the anchor session management network element selects the topology combination and the second CN PDB corresponding to 5QI of the QoS flow from the second CN PDB configuration information as the second CN PDB corresponding to the QoS flow. Wherein, the 5QI of the QoS flow may be obtained by the anchor session management network element from the policy associated with the session.
Further, the anchor point session management network element sends the second CN PDB corresponding to the QoS flow to the intermediate session management network element. Optionally, the anchor session management network element may send the second CN PDB corresponding to the QoS flow to the intermediate session management network element through the third message in the session establishment procedure, the session modification procedure, the HO procedure, or the service request procedure. For example, if the anchor session management network element sends the second CN PDB corresponding to the QoS flow to the intermediate session management network element through the session establishment procedure, the third message may be a session creation Response message (e.g., Nsmf _ pdussion _ Create Response). If the anchor session management network element sends the second CN PDB corresponding to the QoS flow to the intermediate session management network element through other flows, the third message may be a session Update Response message (e.g., Nsmf _ pdusesion _ Update Response).
Alternatively, the second CN PDB may be sent to the intermediate session management network element as contained in a QoS document. And the intermediate session management network element acquires the second CN PDB by analyzing the QoS document.
Specifically, the second CN PDB is N9 CN PDB, the middle session management network element is I-SMF, the anchor session management network element is SMF, the middle user plane network element is I-UPF, the anchor user plane network element is UPF, and the second CN PDB configuration information configured on the SMF is table five. If the user plane connection of the QoS flow passes through I-UPF1 and UPF1 and the 5QI of the QoS flow is 5QI2, the SMF determines that the QoS flow corresponds to N9 CN PDB2 and sends N9 CN PDB2 to the I-SMF.
S502, the middle conversation management network element obtains the first CN PDB corresponding to the QoS flow.
In an embodiment, the intermediate session management network element may determine the first CN PDB corresponding to the QoS flow according to a topology combination of the access network device and the intermediate user plane network element through which the user plane connection of the QoS flow passes, a 5QI of the QoS flow, and the first CN PDB configuration information configured on the intermediate session management network element. For example, the intermediate session management network element selects the topology combination and the first CN PDB corresponding to 5QI of the QoS flow from the first CN PDB configuration information as the first CN PDB corresponding to the QoS flow. The 5QI for acquiring the QoS flow by the intermediate session management network element may be acquired in the session establishment procedure. For example, the anchor session management network element may send the 5QI of the QoS flow to the intermediate session management network element through a session creation response message in the session establishment procedure.
Specifically, the first CN PDB is N3CN PDB, the middle session management network element is I-SMF, the anchor session management network element is SMF, the access network device is RAN, the middle user plane network element is I-UPF, and the first CN PDB configuration information configured on the I-SMF is table four. If the user plane connection for the QoS flow passes through the RAN2 and the I-UPF1, and the 5QI of the QoS flow is 5QI2, it is determined that the QoS flow corresponds to N3CN PDB 3.
And S503, the intermediate session management network element determines the CN PDB corresponding to the QoS flow according to the first CN PDB corresponding to the QoS flow and the second CN PDB corresponding to the QoS flow.
In one embodiment, the CN PDB for the QoS flow is equal to the sum of the first CN PDB for the QoS flow and the second CN PDB for the QoS flow. For example, the first CN PDB for QoS flow is N3CN PDB3, the second CN PDB for QoS flow is N9 CN PDB2, and the CN PDB for QoS flow is equal to the sum of N3CN PDB3 and N9 CN PDB 2.
Optionally, steps S504 and S505 may also be included.
S504, the middle conversation management network element sends the CN PDB corresponding to the QoS flow to the access network equipment.
And S505, the access network equipment determines the AN PDB corresponding to the QoS flow according to the PDB corresponding to the QoS flow and the CN PDB corresponding to the QoS flow.
In one embodiment, the intermediate session management network element may send the CN PDB corresponding to the QoS flow to the access network device, for example, the intermediate session management network element sends the CN PDB to the access network device through the N2 SM information in the N1N2 message transmission request. Optionally, the intermediate session management network element may send the CN PDB included in the QoS document to the access network device.
The access network device may obtain the PDB corresponding to the QoS flow according to the 5QI of the QoS flow. Further, the access network equipment determines the AN PDB corresponding to the QoS flow according to the PDB corresponding to the QoS flow and the CN PDB corresponding to the QoS flow.
The method shown in fig. 7 is described in more detail in connection with fig. 8. For convenience of understanding, in fig. 8, a terminal device is taken as a UE, a mobility management network element is taken as an AMF, an access network device is taken as a RAN, an intermediate session management network element is taken as an I-SMF, an anchor point session management network element is taken as an SMF, an intermediate user plane network element is taken as an I-UPF, and an anchor point user plane network element is taken as an UPF.
For example, the first CN PDB configuration information configured on the I-SMF may be as shown in table four. The second CN PDB configuration information configured on the SMF may be as shown in table five.
S601, UE sends session establishment request message to AMF.
S602, AMF selects I-SMF and SMF. The AMF sends a Create Session management context request message to the I-SMF.
S603, the I-SMF sends a create session management context response message to the AMF.
S604, selecting I-UPF by the I-SMF; the I-SMF initiates an N4 session creation process to the selected I-UPF.
Please refer to steps S401 to S404 of the embodiment of fig. 6 for steps S601 to S604, which are not described herein again.
S605, the I-SMF sends a session creation request message to the SMF, wherein the session creation request message comprises the UE ID, the I-SMF ID, the selected I-UPF ID and the PDU session identification.
The session creation request message corresponds to a serving interface Nsmf _ pdusesion _ Create request.
S606, SMF initiates the process of establishing the conversation management strategy association to PCF to obtain the strategy of the conversation association. The SMF acquires the 5QI of the QoS flow contained in the session according to the policy associated with the session. It is to be appreciated that the session can include at least one QoS flow, and the SMF can obtain 5 QIs for one or more QoS flows of the at least one QoS flow, respectively.
S607, the SMF selects a UPF and initiates an N4 session creation procedure to the selected UPF. And the SMF determines the N9 CN PDB corresponding to the QoS flow according to the I-UPF and UPF topological combination passed by the user plane connection of the QoS flow and the 5QI of the QoS flow. For example, the SMF selects from table five the topological combination of I-UPF and UPF through which the user plane connection for the QoS flow passes and the N9 CN PDB corresponding to the 5QI for the QoS flow.
S608, the SMF sends a session creation response message to the I-SMF, wherein the session creation response message comprises the QoS rule of the QoS flow, the QoS document of the QoS flow, the QoS flow identification of the QoS flow, the 5QI identification of the QoS flow and the N9 CN PDB corresponding to the QoS flow. Optionally, the N9 CN PDB corresponding to the QoS flow may also be included in the QoS document of the QoS flow, and if the N9 CN PDB is included in the QoS document, the I-SMF may parse the QoS document, thereby obtaining the N9 CN PDB corresponding to the QoS flow. Wherein the 5QI of the QoS flow may also be contained in the QoS profile of the QoS flow, and the I-SMF may parse the QoS profile to obtain the 5QI of the QoS flow.
And S609, the I-SMF determines the N3CN PDB corresponding to the QoS flow according to the topology combination of the RAN and the I-UPF passed by the user interface connection of the QoS flow and the 5QI of the QoS flow. For example, the I-SMF selects from table four the topological combination of RAN and I-UPF through which the user plane connection for the QoS flow passes and the N3CN PDB corresponding to the 5QI for the QoS flow.
Further, the I-SMF determines the CN PDB corresponding to the QoS flow according to the N3CN PDB corresponding to the QoS flow and the N9 CN PDB corresponding to the QoS flow.
Wherein CN PDB is N3CN PDB + N9 CN PDB.
S610, the I-SMF sends an N1N2 message transmission request to the AMF.
The AMF sends an N2 PDU session request to the RAN S611.
Optionally, the I-SMF may send the CN PDB corresponding to the QoS flow to the RAN as included in the QoS document.
And S612, other steps of the session establishment flow. Such as air interface resource establishment, core network user plane path update, etc.
Please refer to steps S411 to S413 of the embodiment of fig. 6 for steps S610 to S612, which are not described herein again.
It is to be understood that the execution sequence of the above steps is not limited in this application.
Referring to fig. 9, which is a flowchart illustrating a QoS flow control method according to AN embodiment of the present application, in a communication system including AN intermediate session management network element and AN anchor session management network element, AN access network device determines a scenario of AN session quality management base (AN) Packet Data Base (PDB) according to a first CN PDB from the intermediate session management network element and a second CN PDB from the anchor session management network element, respectively. As shown in fig. 9, the method may include: s701, S702, S703 and S704. The execution sequence of S701, S702, S703, and S704 is not limited in this embodiment of the application. As shown in the figure, the QoS flow control method of the embodiment of the present application includes, but is not limited to, the following steps:
s701, the middle session management network element sends the first CN PDB corresponding to the QoS flow to the access network equipment.
And S702, the anchor point session management network element sends the second CN PDB corresponding to the QoS flow to the access network equipment.
In an embodiment, the anchor session management network element may send the second CN PDB corresponding to the QoS flow to the access network device through the intermediate session management network element.
Illustratively, the anchor session management network element determines a first CN PDB corresponding to the QoS flow, and sends a second CN PDB corresponding to the QoS flow to the intermediate session management network element. And the intermediate session management network element determines a second CN PDB corresponding to the QoS flow, and sends the first CN PDB corresponding to the QoS flow and the second CN PDB corresponding to the QoS flow to the access network equipment.
Optionally, the method for determining, by the anchor session management network element, the first CN PDB corresponding to the QoS flow may refer to the description in S302 in the embodiment of fig. 5, and the method for determining, by the intermediate session management network element, the second CN PDB corresponding to the QoS flow may refer to the description in S502 in the embodiment of fig. 7, which is not described herein again.
Optionally, the anchor session management network element may send the second CN PDB corresponding to the QoS flow to the intermediate session management network element through a fourth message in the session establishment procedure, the session modification procedure, the HO procedure, or the service request procedure. If the anchor session management network element sends the second CN PDB corresponding to the QoS flow to the intermediate session management network element through the session establishment procedure, the fourth message may be a session creation Response message (e.g., Nsmf _ pdussion _ Create Response); if the anchor session management network element sends the second CN PDB corresponding to the QoS flow to the intermediate session management network element through other flows, the fourth message may be a session Update Response message (e.g., Nsmf _ pdussion _ Update Response).
Correspondingly, the intermediate session management network element may also send the first CN PDB corresponding to the QoS flow and the second CN PDB corresponding to the QoS flow to the access and mobility management device through the fifth message in the session establishment flow, the session modification flow, the HO flow, or the service request flow, and send the first CN PDB corresponding to the QoS flow and the second CN PDB corresponding to the QoS flow to the access network device through the sixth message by the access and mobility management device. Alternatively, the fifth message may be an N1N2 transfer request and the sixth message may be an N2 PDU session request.
It can be understood that, the intermediate session management network element may also send the first CN PDB corresponding to the QoS flow and the second CN PDB corresponding to the QoS flow to the access network device through different messages, which is not limited in the embodiment of the present application.
S703, the access network device determines the PDB corresponding to the QoS flow.
In one embodiment, the access network device may determine the PDB corresponding to the QoS flow according to the 5QI of the QoS flow.
S704, the access network equipment determines the AN PDB corresponding to the QoS flow according to the first CN PDB corresponding to the QoS flow, the second CN PDB corresponding to the QoS flow and the PDB corresponding to the QoS flow.
In one embodiment, the AN PDB corresponding to the QoS flow is equal to the value obtained by subtracting the first CN PDB corresponding to the QoS flow from the PDB corresponding to the QoS flow and subtracting the second CN PDB corresponding to the QoS flow. For example, if the first CN PDB corresponding to the QoS flow is N3CN PDB3, and the second CN PDB corresponding to the QoS flow is N9 CN PDB2, the AN PDB is PDB-N3CN PDB3-N9 CN PDB 2.
The method shown in fig. 9 is described in more detail in connection with fig. 10. For convenience of understanding, in fig. 10, a terminal device is taken as a UE, a mobility management network element is taken as an AMF, an access network device is taken as a RAN, an intermediate session management network element is taken as an I-SMF, an anchor session management network element is taken as an SMF, an intermediate user plane network element is taken as an I-UPF, and an anchor user plane network element is taken as an UPF.
For example, the first CN PDB configuration information configured on the I-SMF may be as shown in table four. The second CN PDB configuration information configured on the SMF may be as shown in table five.
S801, the UE sends a session establishment request message to the AMF.
S802, AMF selects I-SMF and SMF. The AMF sends a Create Session management context request message to the I-SMF.
S803, the I-SMF sends a create session management context response message to the AMF.
S804, selecting I-UPF by the I-SMF; the I-SMF initiates an N4 session creation process to the selected I-UPF.
Please refer to steps S401 to S404 of the embodiment of fig. 6 for steps S801 to S804, which are not described herein again.
S805, the I-SMF sends a session creation request message to the SMF, wherein the session creation request message comprises the UE ID, the I-SMF ID, the selected I-UPF ID and the PDU session identification.
The session creation request message corresponds to a serving interface Nsmf _ pdusesion _ Create request.
S806, SMF initiates the process of establishing the conversation management strategy association to PCF to obtain the strategy of the conversation association. The SMF acquires the 5QI of the QoS flow contained in the session according to the policy associated with the session. It is to be appreciated that the session can include at least one QoS flow, and the SMF can obtain 5 QIs for one or more QoS flows of the at least one QoS flow, respectively.
S807, the SMF selects a UPF and initiates an N4 session creation process to the selected UPF. And the SMF determines the N9 CN PDB corresponding to the QoS flow according to the I-UPF and UPF topological combination passed by the user plane connection of the QoS flow and the 5QI of the QoS flow. For example, the SMF selects from table five the topological combination of I-UPF and UPF through which the user plane connection for the QoS flow passes and the N9 CN PDB corresponding to the 5QI for the QoS flow.
S808, the SMF sends a session creation response message to the I-SMF, wherein the session creation response message comprises the QoS rule of the QoS flow, the QoS document of the QoS flow, the QoS flow identification of the QoS flow, the 5QI identification of the QoS flow and the N9 CN PDB corresponding to the QoS flow. Optionally, the N9 CN PDB corresponding to the QoS flow may also be included in the QoS document of the QoS flow. Wherein the 5QI of the QoS flow may also be contained in the QoS profile of the QoS flow, and the I-SMF may parse the QoS profile to obtain the 5QI of the QoS flow.
And S809, the I-SMF determines the N3CN PDB corresponding to the QoS flow according to the topology combination of the RAN and the I-UPF passed by the user interface connection of the QoS flow and the 5QI of the QoS flow. For example, the I-SMF selects from table four the topological combination of RAN and I-UPF through which the user plane connection for the QoS flow passes and the N3CN PDB corresponding to the 5QI for the QoS flow.
S810, the I-SMF sends an N1N2 message transmission request to the AMF, the N1N2 message transmission request comprises N2 SM information and N1 SM information, and the N2 SM information comprises N3CN PDB corresponding to the QoS flow and N9 CN PDB corresponding to the QoS flow.
S811, the AMF sends an N2 PDU session request to the RAN. The N2 PDU session request may include N2 SM information, NAS message. Wherein the NAS message contains N1 SM information.
Optionally, both the N3CN PDB corresponding to the QoS flow and the N9 CN PDB corresponding to the QoS flow may be included in the QoS document and sent to the RAN.
S812, the RAN determines the AN PDB corresponding to the QoS flow according to the N3CN PDB corresponding to the QoS flow, the N9 CN PDB corresponding to the QoS flow and the PDB corresponding to the 5QI of the QoS flow.
S813, other steps of the session establishment procedure. Such as air interface resource establishment, core network user plane path update, etc.
It is to be understood that the execution sequence of the above steps is not limited in this application.
The method provided by the embodiment of the present application is described in detail above with reference to fig. 3 to 10. Hereinafter, the apparatus provided in the embodiment of the present application will be described in detail with reference to fig. 11 to 13.
It is to be understood that, in order to implement the functions in the foregoing embodiments, the intermediate session management network element, the anchor session management network element, and the access network device include hardware structures and/or software modules corresponding to the respective functions. Those of skill in the art will readily appreciate that the various illustrative elements and method steps described in connection with the embodiments disclosed herein may be implemented as hardware, software, or combinations of hardware and software. Whether a function is implemented as hardware, software, or computer software drives hardware depends upon the particular application and design constraints imposed on the implementation.
Fig. 11 is a schematic block diagram of a communication device provided in an embodiment of the present application. As shown in fig. 11, the communication apparatus 900 may include a processing unit 910 and a transceiving unit 920. The processing unit 910 and the transceiver 920 may be software, hardware, or a combination of software and hardware.
The transceiver 920 may include a transmitting unit and a receiving unit, where the transmitting unit is configured to implement a transmitting function, the receiving unit is configured to implement a receiving function, and the transceiver 920 may implement a transmitting function and/or a receiving function. The transceiving unit may also be described as a communication unit.
Optionally, the transceiver 920 may be configured to receive information sent by other apparatuses, and may also be configured to send information to other apparatuses. The processing unit 910 may be used to perform internal processing of the device.
In a possible design, the communication apparatus 900 may correspond to the intermediate session management network element in the foregoing method embodiment, for example, the communication apparatus 900 may be the intermediate session management network element, and may also be a chip in the intermediate session management network element. The communication apparatus 900 may include means for performing the operations performed by the intermediate session management network element in the above method embodiments, and the means in the communication apparatus 900 are respectively configured to implement the operations performed by the intermediate session management network element in the above method embodiments.
Exemplarily, the processing unit 910 is configured to determine to split a first traffic flow of a first QoS flow, where the first QoS flow includes at least two traffic flows, and the at least two traffic flows includes the first traffic flow;
the processing unit 910 is further configured to bind the first traffic flow to a second QoS flow, and allocate a QoS flow identifier to the second QoS flow;
a transceiving unit 920, configured to send the QoS flow identifier to the anchor session management network element.
In one possible design, the communication apparatus 900 may correspond to the first session management network element, and may also be a chip in the first session management network element. Optionally, the first session management network element may be an anchor session management network element or an intermediate session management network element. If the first session management network element is an anchor session management network element, the communication apparatus 900 may include a unit for performing the operation performed by the anchor session management network element in the above method embodiment, and each unit in the communication apparatus 900 is respectively configured to implement the operation performed by the anchor session management network element in the above method embodiment. If the first session management network element is an intermediate session management network element, the communication apparatus 900 may include a unit for performing the operation performed by the intermediate session management network element in the foregoing method embodiment, and each unit in the communication apparatus 900 is respectively configured to implement the operation performed by the intermediate session management network element in the foregoing method embodiment.
Exemplarily, the processing unit 910 is configured to obtain a first CN PDB corresponding to a QoS flow, where the first CN PDB is a CN PDB between an access network device and an intermediate user plane network element, and the intermediate session management network element is connected to the intermediate user plane network element;
the processing unit 910 is further configured to acquire a second CN PDB corresponding to the QoS flow, where the second CN PDB is a CN PDB between the middle user plane network element and an anchor user plane network element, and the anchor session management network element is connected to the anchor user plane network element;
the processing unit 910 is further configured to determine, according to a first CN PDB corresponding to the QoS flow and a second CN PDB corresponding to the QoS flow, a CN PDB corresponding to the QoS flow;
wherein, when the first session management network element is an anchor session management network element, the processing unit 910 is specifically configured to receive, through the transceiving unit 920, a first CN PDB corresponding to the QoS flow from an intermediate session management network element; or, when the first session management network element is the intermediate session management network element, the processing unit 910 is specifically configured to receive, through the transceiving unit 920, the second CN PDB corresponding to the QoS flow from the anchor session management network element.
In one possible design, the communication apparatus 900 may correspond to the access network device in the above method embodiment, for example, the communication apparatus 900 may be an access network device, and may also be a chip in the access network device. The communication apparatus 900 may include means for performing the operations performed by the access network device in the above method embodiments, and each of the means in the communication apparatus 900 is configured to implement the operations performed by the access network device in the above method embodiments.
Exemplarily, the transceiving unit 920 is configured to receive a first CN PDB corresponding to a QoS flow from an intermediate session management network element, and receive a second CN PDB corresponding to the QoS flow from an anchor session management network element, where the first CN PDB is a CN PDB between an access network device and an intermediate user plane network element, the second CN PDB is a CN PDB between the intermediate user plane network element and the anchor user plane network element, the intermediate session management network element is connected to the intermediate user plane network element, and the anchor session management network element is connected to the anchor user plane network element;
a processing unit 910, configured to determine a packet delay budget PDB corresponding to the QoS flow;
the processing unit 910 is further configured to determine AN access network packet delay budget AN PDB corresponding to the QoS flow according to the first CN PDB corresponding to the QoS flow, the second CN PDB corresponding to the QoS flow, and the PDB corresponding to the QoS flow.
It should be understood that, when the communication apparatus 900 is a chip configured in an intermediate session management network element, an anchor session management network element, or an access network device, the transceiver 920 in the communication apparatus 900 may be an input/output interface.
It should be understood that when the communication apparatus 900 is an intermediate session management network element, or an anchor session management network element or an access network device, the transceiving unit 920 in the communication apparatus 900 may correspond to the communication interface 1010 shown in fig. 12, and the processing unit 910 may correspond to the processor 1020 shown in fig. 12.
Fig. 12 is a schematic structural diagram of a communication device according to an embodiment of the present application. It should be understood that the communication apparatus 1000 shown in fig. 12 is only an example, and the communication apparatus of the embodiment of the present application may further include other modules or units, or include modules having functions similar to those of the respective modules in fig. 12, or not include all the modules in fig. 12.
The communication device 1000 includes a communication interface 1010 and at least one processor 1020.
The communication apparatus 1000 may correspond to any network element or device in an intermediate session management network element, an anchor session management network element, or an access network device. The at least one processor 1020 executes the program instructions to enable the communication apparatus 1000 to implement the respective flows of the methods performed by the corresponding network elements in the above-described method embodiments.
In a possible design, the communication apparatus 1000 may correspond to the intermediate session management network element in the foregoing method embodiment, for example, the communication apparatus 100 may be the intermediate session management network element, and may also be a chip in the intermediate session management network element. The communication device 1000 may comprise means for performing the operations performed by the intermediate session management network element in the above-described method embodiments.
Illustratively, the processor 1020 is configured to determine to split a first traffic flow of a first QoS flow, where the first QoS flow includes at least two traffic flows, and the at least two traffic flows includes the first traffic flow;
processor 1020 is further configured to bind the first traffic flow to a second QoS flow and assign a QoS flow identification to the second QoS flow;
the communication interface 1010 is configured to send the QoS flow identifier to the anchor session management network element.
In one possible design, the communication apparatus 1000 may correspond to the first session management network element, and may also be a chip in the first session management network element. Optionally, the first session management network element may be an anchor session management network element or an intermediate session management network element. If the first session management network element is an anchor session management network element, the communication apparatus 1000 may include components for performing the operations performed by the anchor session management network element in the above method embodiments, and each component in the communication apparatus 1000 is respectively configured to implement the operations performed by the anchor session management network element in the above method embodiments. If the first session management network element is an intermediate session management network element, the communication apparatus 1000 may include components for performing the operations performed by the intermediate session management network element in the foregoing method embodiments, and each component in the communication apparatus 1000 is respectively configured to implement the operations performed by the intermediate session management network element in the foregoing method embodiments.
Exemplarily, the processor 1020 is configured to obtain a first CN PDB corresponding to a QoS flow, where the first CN PDB is a CN PDB between an access network device and an intermediate user plane network element, and the intermediate session management network element is connected to the intermediate user plane network element;
the processor 1020 is further configured to acquire a second CN PDB corresponding to the QoS flow, where the second CN PDB is a CN PDB between the middle user plane network element and an anchor user plane network element, and the anchor session management network element is connected to the anchor user plane network element;
the processor 1020 is further configured to determine, according to the first CN PDB corresponding to the QoS flow and the second CN PDB corresponding to the QoS flow, a CN PDB corresponding to the QoS flow;
wherein, when the first session management network element is an anchor session management network element, the processor 1020 is specifically configured to receive, from an intermediate session management network element through the communication interface 1010, a first CN PDB corresponding to the QoS flow; or, when the first session management network element is the intermediate session management network element, the processor 1020 is specifically configured to receive, from the anchor session management network element through the communication interface 1010, the second CN PDB corresponding to the QoS flow.
In a possible design, the communication apparatus 1000 may correspond to the access network device in the above method embodiment, for example, the communication apparatus 1000 may be an access network device, and may also be a chip in the access network device. The communications apparatus 1000 may include components for performing the operations performed by the access network device in the above-described method embodiments.
Exemplarily, the communication interface 1010 is configured to receive a first CN PDB corresponding to a QoS flow from an intermediate session management network element and receive a second CN PDB corresponding to the QoS flow from an anchor session management network element, where the first CN PDB is a CN PDB between an access network device and an intermediate user plane network element, the second CN PDB is a CN PDB between the intermediate user plane network element and an anchor user plane network element, the intermediate session management network element is connected to the intermediate user plane network element, and the anchor session management network element is connected to the anchor user plane network element;
a processor 1020, configured to determine a packet delay budget PDB corresponding to the QoS flow;
the processor 1020 is further configured to determine AN access network packet delay budget AN PDB corresponding to the QoS flow according to the first CN PDB corresponding to the QoS flow, the second CN PDB corresponding to the QoS flow, and the PDB corresponding to the QoS flow.
Optionally, the communication device 1000 may also include a memory. The memory may store program instructions, and the at least one processor 1020 may read the program instructions stored by the memory and execute the program instructions.
For the case that the communication device may be a chip or a system of chips, see the schematic structural diagram of the chip shown in fig. 13. The chip 2000 shown in fig. 13 includes a processor 2001 and an interface 2002. The number of the processors 2001 may be one or more, and the number of the interfaces 2002 may be plural. It should be noted that the functions corresponding to the processor 2001 and the interface 2002 may be implemented by hardware design, software design, or a combination of hardware and software, which is not limited herein.
In one possible design, for a case where a chip is used to implement the function of the intermediate session management network element in the embodiment of the present application: the processor 2001 is configured to determine to split a first traffic flow of a first QoS flow, where the first QoS flow includes at least two traffic flows, and the at least two traffic flows includes the first traffic flow;
processor 2001 is further configured to bind the first traffic flow to a second QoS flow and assign a QoS flow identification to the second QoS flow;
interface 2002 is configured to send the QoS flow identifier to the anchor session management network element.
For the case that the chip is used to implement the function of the first session management network element in the embodiment of the present application: a processor 2001, configured to obtain a first CN PDB corresponding to a QoS flow, where the first CN PDB is a CN PDB between an access network device and an intermediate user plane network element, and the intermediate session management network element is connected to the intermediate user plane network element;
the processor 2001 is further configured to acquire a second CN PDB corresponding to the QoS flow, where the second CN PDB is a CN PDB between the middle user plane network element and an anchor user plane network element, and the anchor session management network element is connected to the anchor user plane network element;
the processor 2001 is further configured to determine, according to the first CN PDB corresponding to the QoS flow and the second CN PDB corresponding to the QoS flow, a CN PDB corresponding to the QoS flow;
wherein, when the first session management network element is an anchor session management network element, the processor 2001 is specifically configured to receive, from an intermediate session management network element through the interface 2002, a first CN PDB corresponding to the QoS flow; or, when the first session management network element is the intermediate session management network element, the processor 2001 is specifically configured to receive, through the interface 2002, the second CN PDB corresponding to the QoS flow from the anchor session management network element.
For the case that the chip is used to implement the function of the access network device in the embodiment of the present application: an interface 2002, configured to receive a first CN PDB corresponding to a QoS flow from an intermediate session management network element, and receive a second CN PDB corresponding to the QoS flow from an anchor session management network element, where the first CN PDB is a CN PDB between an access network device and an intermediate user plane network element, the second CN PDB is a CN PDB between the intermediate user plane network element and the anchor user plane network element, the intermediate session management network element is connected to the intermediate user plane network element, and the anchor session management network element is connected to the anchor user plane network element;
a processor 2001, configured to determine a packet delay budget PDB corresponding to the QoS flow;
the processor 2001 is further configured to determine AN access network packet delay budget AN PDB corresponding to the QoS flow according to the first CN PDB corresponding to the QoS flow, the second CN PDB corresponding to the QoS flow, and the PDB corresponding to the QoS flow.
Optionally, the chip further comprises a memory 2003, the memory 2003 being for storing necessary program instructions and data.
The processor in the embodiment of the present application may be a Central Processing Unit (CPU), and the processor may also be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
According to the method provided by the embodiment of the present application, the present application further provides a computer program product, which includes: computer program code which, when run on a computer, causes the computer to perform the method of any of the preceding method embodiments, the intermediate session management network element side, the anchor session management network element side or the access network device side.
In another embodiment of the present application, a communication system is further provided, where the communication system includes an intermediate session management network element and an anchor session management network element. Optionally, the communication system may further include an access network device. For example, the intermediate session management network element and the anchor session management network element may be the intermediate session management network element and the anchor session management network element provided in any embodiment of fig. 3 to 10, and are configured to perform steps executed by corresponding network elements in any embodiment of fig. 3 to 10; and/or the access network device may be the access network device provided in any of the embodiments of fig. 3 to 10, and is configured to perform the steps performed by the access network device in any of the embodiments of fig. 3 to 10.
The embodiment of the application also provides a processing device, which comprises a processor and an interface; the processor is configured to perform the method of any of the above method embodiments.
It should be understood that the processing means may be a chip. For example, the processing device may be a Field Programmable Gate Array (FPGA), a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, a system on chip (SoC), a Central Processing Unit (CPU), a Network Processor (NP), a digital signal processing circuit (DSP), a microcontroller (micro controller unit, MCU), a Programmable Logic Device (PLD) or other integrated chip. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.
It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM, enhanced SDRAM, SLDRAM, Synchronous Link DRAM (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a Digital Video Disk (DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), among others.
The intermediate session management network element, the anchor session management network element, or the access network device in the foregoing device embodiments completely correspond to the intermediate session management network element, the anchor session management network element, or the access network device in the method embodiments, and corresponding modules or units execute corresponding steps, for example, a communication unit (transceiver) executes a step of receiving or transmitting in the method embodiments, and other steps except for transmitting and receiving may be executed by a processing unit (processor). The functions of the specific elements may be referred to in the respective method embodiments. The number of the processors may be one or more.
As used in this specification, the terms "component," "module," "system," and the like are intended to refer to a computer-related entity, either hardware, firmware, a combination of hardware and software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, an object, an executable, a thread of execution, a program, or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components may reside within a process or thread of execution and a component may be localized on one computer and distributed between 2 or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate by way of local or remote processes such as in accordance with a signal having one or more data packets (e.g., data from two components interacting with another component in a local system, distributed system, or across a network such as the internet with other systems by way of the signal).
It should be appreciated that reference throughout this specification to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Thus, the various embodiments are not necessarily referring to the same embodiment throughout the specification. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
It should be understood that, in the embodiment of the present application, the numbers "first" and "second" … are only used for distinguishing different objects, such as for distinguishing different network devices, and do not limit the scope of the embodiment of the present application, and the embodiment of the present application is not limited thereto.
It should also be understood that, in this application, "when …", "if" and "if" all refer to a network element that performs the corresponding process under certain objective circumstances, and are not time-critical, nor do they require certain deterministic actions to be performed by the network element, nor do they imply that other limitations exist.
It should also be understood that in the embodiments of the present application, "B corresponding to a" means that B is associated with a, from which B can be determined. It should also be understood that determining B from a does not mean determining B from a alone, but may be determined from a and/or other information.
It should also be understood that the term "and/or" herein is merely one type of association that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.
Items appearing in this application as similar to "include one or more of the following: the meaning of the expressions A, B, and C "generally means that the item may be any of the following, unless otherwise specified: a; b; c; a and B; a and C; b and C; a, B and C; a and A; a, A and A; a, A and B; a, A and C, A, B and B; a, C and C; b and B, B, B and C, C and C; c, C and C, and other combinations of A, B and C. The above description is made by taking 3 elements of a, B and C as examples of optional items of the item, and when the expression "item" includes at least one of the following: a, B, … …, and X ", i.e., more elements in the expression, then the items to which the item may apply may also be obtained according to the aforementioned rules.
It is understood that, in the embodiment of the present application, the intermediate session management network element, the anchor session management network element, or the access network device may perform some or all of the steps in the embodiment of the present application, and these steps or operations are merely examples, and the embodiment of the present application may also perform other operations or variations of various operations. Further, the various steps may be performed in a different order presented in the embodiments of the application, and not all operations in the embodiments of the application may be performed.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a read-only memory ROM, a random access memory RAM, a magnetic disk, or an optical disk.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (25)

1. A QoS flow control method applied to a communication system including an intermediate session management network element and an anchor session management network element, the method comprising:
the intermediate session management network element determines to shunt a first service flow in a first QoS flow, where the first QoS flow includes at least two service flows, and the at least two service flows include the first service flow;
the intermediate session management network element binds the first service flow to a second QoS flow and allocates a QoS flow identifier for the second QoS flow;
and the intermediate session management network element sends the QoS flow identification to the anchor session management network element.
2. The method of claim 1, wherein the method further comprises:
the intermediate session management network element determines a core network message delay budget CN PDB corresponding to the second QoS flow;
and the intermediate session management network element sends the CN PDB corresponding to the second QoS flow to the access network equipment.
3. The method of claim 1 or 2, wherein the method further comprises:
and the intermediate session management network element receives indication information from the anchor session management network element, wherein the indication information is used for indicating the intermediate session management network element to bind the first service flow to a second QoS flow.
4. A QoS flow control method applied to a communication system including an anchor session management network element and an intermediate session management network element, the method comprising:
a first session management network element acquires a first core network message delay budget CN PDB corresponding to a QoS flow, wherein the first CN PDB is a CN PDB between access network equipment and an intermediate user plane network element, and the intermediate session management network element is connected with the intermediate user plane network element;
the first session management network element acquires a second CN PDB corresponding to the QoS flow, wherein the second CN PDB is a CN PDB between the intermediate user plane network element and an anchor user plane network element, and the anchor session management network element is connected with the anchor user plane network element;
the first session management network element determines a CN PDB corresponding to the QoS flow according to a first CN PDB corresponding to the QoS flow and a second CN PDB corresponding to the QoS flow;
wherein, when the first session management network element is the anchor session management network element, the acquiring, by the first session management network element, the first CN PDB corresponding to the QoS flow includes: the first session management network element receives a first CN PDB corresponding to the QoS flow from the middle session management network element; or, when the first session management network element is the intermediate session management network element, the acquiring, by the first session management network element, the second CN PDB corresponding to the QoS flow includes: and the first session management network element receives a second CN PDB corresponding to the QoS flow from the anchor point session management network element.
5. The method of claim 4, wherein the method further comprises:
and the first session management network element sends the CN PDB corresponding to the QoS flow to the access network equipment.
6. The method of claim 4 or 5, wherein the CN PDB for the QoS flow is equal to a sum of a first CN PDB for the QoS flow and a second CN PDB for the QoS flow.
7. The method of any of claims 4-6, wherein the first session management network element receiving the first CN PDB corresponding to the QoS flow from the intermediate session management network element comprises:
the first session management network element receives a first message from the intermediate session management network element, wherein the first message comprises a first CN PDB corresponding to the QoS flow;
wherein the first message is a session update request message.
8. The method of any of claims 4-6, wherein the first session management network element receiving the first CN PDB corresponding to the QoS flow from the intermediate session management network element comprises:
the first session management network element receiving a second message from the intermediate session management network element, the second message including a correspondence between at least one 5G QoS identifier 5QI associated with a first topology and at least one first CN PDB, the first topology including a topological connection between the access network device and the intermediate user plane network element;
the first session management network element determines a first CN PDB corresponding to the QoS flow according to the 5QI of the QoS flow and the corresponding relation;
wherein the second message is a session creation request message.
9. The method of any of claims 4-6, wherein the first session management network element receiving a second CN PDB corresponding to the QoS flow from the anchor session management network element, comprising:
and the first session management network element receives a third message from the anchor session management network element, wherein the third message comprises a second CN PDB corresponding to the QoS flow.
10. A method for quality of service, QoS, flow control, comprising:
the method comprises the steps that an access network device receives a first core network message delay budget CN PDB corresponding to a QoS flow from an intermediate session management network element, and receives a second CN PDB corresponding to the QoS flow from an anchor session management network element, wherein the first CN PDB is a CN PDB between the access network device and an intermediate user plane network element, the second CN PDB is a CN PDB between the intermediate user plane network element and the anchor user plane network element, the intermediate session management network element is connected with the intermediate user plane network element, and the anchor session management network element is connected with the anchor user plane network element;
the access network equipment determines a message delay budget PDB corresponding to the QoS flow;
and the access network equipment determines AN access network message delay budget AN PDB corresponding to the QoS flow according to the first CN PDB corresponding to the QoS flow, the second CN PDB corresponding to the QoS flow and the PDB corresponding to the QoS flow.
11. The method of claim 10, wherein the AN PDB for the QoS flow is equal to the PDB for the QoS flow minus a first CN PDB for the QoS flow and minus a second CN PDB for the QoS flow.
12. A communications apparatus, wherein the communications apparatus is adapted to an intermediate session management network element, the apparatus comprising:
the processing unit is configured to determine to split a first traffic flow in a first quality of service (QoS) flow, where the first QoS flow includes at least two traffic flows, and the at least two traffic flows include the first traffic flow;
the processing unit is further configured to bind the first traffic flow to a second QoS flow and allocate a QoS flow identifier to the second QoS flow;
and the transceiving unit is used for sending the QoS flow identifier to the anchor point session management network element.
13. The apparatus of claim 12,
the processing unit is further configured to determine a core network packet delay budget CN PDB corresponding to the second QoS flow;
the transceiver unit is further configured to send the CN PDB corresponding to the second QoS flow to the access network device.
14. The apparatus of claim 12 or 13,
the transceiving unit is further configured to receive indication information from the anchor session management network element, where the indication information is used to indicate the intermediate session management network element to bind the first service flow to a second QoS flow.
15. A communication device adapted for a first session managing network element, comprising:
a processing unit, configured to obtain a first core network packet delay budget CN PDB corresponding to a quality of service QoS flow, where the first CN PDB is a CN PDB between an access network device and an intermediate user plane network element, and the intermediate session management network element is connected to the intermediate user plane network element;
the processing unit is further configured to acquire a second CN PDB corresponding to the QoS flow, where the second CN PDB is a CN PDB between the middle user plane network element and an anchor user plane network element, and the anchor session management network element is connected to the anchor user plane network element;
the processing unit is further configured to determine, according to the first CN PDB corresponding to the QoS flow and the second CN PDB corresponding to the QoS flow, a CN PDB corresponding to the QoS flow;
wherein, when the first session management network element is the anchor session management network element, the processing unit is specifically configured to receive, through the transceiving unit, a first CN PDB corresponding to the QoS flow from an intermediate session management network element; or, when the first session management network element is the intermediate session management network element, the processing unit is specifically configured to receive, through the transceiving unit, the second CN PDB corresponding to the QoS flow from the anchor session management network element.
16. The apparatus of claim 15,
the processing unit is further configured to send, to the access network device, a CN PDB corresponding to the QoS flow through the transceiving unit.
17. The apparatus of claim 15 or 16, wherein the CN PDB for the QoS flow is equal to a sum of a first CN PDB for the QoS flow and a second CN PDB for the QoS flow.
18. The apparatus of any one of claims 15-17,
the processing unit is specifically configured to receive, by the transceiver unit, a first message from the intermediate session management network element, where the first message includes a first CN PDB corresponding to the QoS flow;
wherein the first message is a session update request message.
19. The apparatus of any one of claims 15-17,
the processing unit is specifically configured to receive, by the transceiver unit, a second message from the intermediate session management network element, where the second message includes a correspondence between at least one 5G QoS identifier 5QI associated with a first topology and at least one first CN PDB, and the first topology includes a topological connection between the access network device and the intermediate user plane network element;
the processing unit is specifically configured to determine, according to the 5QI of the QoS flow and the correspondence, a first CN PDB corresponding to the QoS flow;
wherein the second message is a session creation request message.
20. The apparatus of any one of claims 15-17,
the processing unit is specifically configured to receive, through the transceiving unit, a third message from the anchor point session management network element, where the third message includes a second CN PDB corresponding to the QoS flow.
21. A communications apparatus, comprising:
a transceiving unit, configured to receive a first core network packet delay budget CN PDB corresponding to a quality of service QoS flow from an intermediate session management network element, and receive a second CN PDB corresponding to the QoS flow from an anchor session management network element, where the first CN PDB is a CN PDB between an access network device and an intermediate user plane network element, the second CN PDB is a CN PDB between the intermediate user plane network element and an anchor user plane network element, the intermediate session management network element is connected to the intermediate user plane network element, and the anchor session management network element is connected to the anchor user plane network element;
a processing unit, configured to determine a packet delay budget PDB corresponding to the QoS flow;
the processing unit is further configured to determine AN access network packet delay budget AN PDB corresponding to the QoS flow according to the first CN PDB corresponding to the QoS flow, the second CN PDB corresponding to the QoS flow, and the PDB corresponding to the QoS flow.
22. The apparatus of claim 21, wherein the AN PDB for the QoS flow is equal to the PDB for the QoS flow minus a first CN PDB for the QoS flow and minus a second CN PDB for the QoS flow.
23. A communications apparatus, comprising: a processor for performing the method of any one of claims 1 to 3 or claims 4 to 9 or claims 10 or 11 when the processor invokes a computer program or instructions in memory.
24. A computer-readable storage medium, comprising a computer program or instructions which, when run on a computer, cause the computer to perform the method of any of claims 1 to 3 or claims 4 to 9 or claims 10 or 11.
25. A communication device comprising a processor, a memory, and a communication interface;
the communication interface is used for receiving information or sending information;
the memory for storing program code;
the processor for calling the program code from the memory to perform the method of any of claims 1 to 3 or claims 4 to 9 or claims 10 or 11.
CN202010769550.5A 2020-07-31 2020-07-31 QoS flow control method and communication device Active CN114071574B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202010769550.5A CN114071574B (en) 2020-07-31 2020-07-31 QoS flow control method and communication device
PCT/CN2021/094349 WO2022022014A1 (en) 2020-07-31 2021-05-18 Qos flow control method and communication device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010769550.5A CN114071574B (en) 2020-07-31 2020-07-31 QoS flow control method and communication device

Publications (2)

Publication Number Publication Date
CN114071574A true CN114071574A (en) 2022-02-18
CN114071574B CN114071574B (en) 2023-12-15

Family

ID=80036817

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010769550.5A Active CN114071574B (en) 2020-07-31 2020-07-31 QoS flow control method and communication device

Country Status (2)

Country Link
CN (1) CN114071574B (en)
WO (1) WO2022022014A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023213176A1 (en) * 2022-05-05 2023-11-09 华为技术有限公司 Qos control method and corresponding apparatus

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11528635B2 (en) * 2021-01-12 2022-12-13 Verizon Patent And Licensing Inc. Method and system for radio resource management and network slicing
CN116801405A (en) * 2022-03-11 2023-09-22 华为技术有限公司 Communication method, device and equipment
CN117439925A (en) * 2022-07-15 2024-01-23 华为技术有限公司 Communication method, device and system

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019137194A1 (en) * 2018-01-11 2019-07-18 电信科学技术研究院有限公司 User plane data security protection method and device
WO2019154036A1 (en) * 2018-02-12 2019-08-15 华为技术有限公司 Qos flow processing method, device and system
CN110351777A (en) * 2018-04-03 2019-10-18 华为技术有限公司 The method and apparatus for indicating service distributing

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108632904B (en) * 2017-03-24 2019-09-17 电信科学技术研究院 A kind of communication means and equipment
CN109392023B (en) * 2017-08-10 2023-11-14 北京三星通信技术研究有限公司 Method and equipment for controlling operation of data stream
CN110062426B (en) * 2019-04-02 2021-08-24 腾讯科技(深圳)有限公司 Communication method, communication device, computer readable medium and electronic equipment

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019137194A1 (en) * 2018-01-11 2019-07-18 电信科学技术研究院有限公司 User plane data security protection method and device
WO2019154036A1 (en) * 2018-02-12 2019-08-15 华为技术有限公司 Qos flow processing method, device and system
CN110351777A (en) * 2018-04-03 2019-10-18 华为技术有限公司 The method and apparatus for indicating service distributing

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
LG ELECTRONICS: "New solution for KI#6", 3GPP TSG-SA WG2 MEETING #130 S2-1900542 *
ZTE: "L-SMF clarification for solution 16: I-UPF insertion and L-SMF/L-UPF selection", 3GPP TSG SA WG2 MEETING #128 S2-187022 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023213176A1 (en) * 2022-05-05 2023-11-09 华为技术有限公司 Qos control method and corresponding apparatus

Also Published As

Publication number Publication date
CN114071574B (en) 2023-12-15
WO2022022014A1 (en) 2022-02-03

Similar Documents

Publication Publication Date Title
KR102436804B1 (en) Session management methods, devices and systems
CN110662270B (en) Communication method and device
CN111770531B (en) Method, system and device for obtaining data packet delay parameter
CN110121897B (en) Method and equipment for establishing session
WO2020063317A1 (en) Communication method and apparatus
CN114071574B (en) QoS flow control method and communication device
CN112566149B (en) Method for configuring service, communication device and communication system
CN110831094B (en) Method and device for processing data transmission channel
CN110149665A (en) A kind of selection method and device of network element
CN113708947B (en) Slice access method, device and system
CN113746585B (en) Time service method and communication device
CN110149651B (en) Method and device for determining SSC mode
CN113055879B (en) User identification access method and communication device
WO2019201322A1 (en) Communication method and related device
KR20210024160A (en) Communication method and device
CN115004779A (en) Communication method and device
CN114513864A (en) Multipath transmission method and communication device
CN115209395A (en) Network access method and device
CN114390634A (en) Relay terminal selection method, terminal and storage medium
CN113271561B (en) Method and device for determining communication mode and storage medium
CN113950111A (en) Session switching method and device
CN114698145A (en) Method and device for transmitting data
CN115190457A (en) Method and device for voice communication
WO2023143270A1 (en) Communication method and apparatus
CN116866881A (en) Communication method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant