WO2019154036A1

WO2019154036A1 - Qos flow processing method, device and system

Info

Publication number: WO2019154036A1
Application number: PCT/CN2019/072112
Authority: WO
Inventors: 舒林
Original assignee: 华为技术有限公司
Priority date: 2018-02-12
Filing date: 2019-01-17
Publication date: 2019-08-15
Also published as: CN110166407A; CN110166407B

Abstract

Provided in an embodiment of the present invention are a quality of service (QoS) flow processing method, device and system capable of solving a problem resulting from an increase in the number of QoS flows during inter-operation between a target system supporting the increased QoS flows and an evolved packet system (EPS). The method comprises: a terminal associated with increased QoS flows in an active state accessing an EPS; and the terminal suspending the increased QoS flows.

Description

QoS flow processing method, device and system

This application claims priority to Chinese Patent Application No. 201101147571.6, entitled "QoS Flow Processing Method, Equipment and System", filed on February 12, 2018, the entire contents of which are incorporated by reference. In this application.

Technical field

The present application relates to the field of communications technologies, and in particular, to a quality of service (QoS) flow processing method, device, and system.

Background technique

With the development of mobile communication technology, the first generation (1G) mobile communication system, the second generation (2G) mobile communication system, and the third generation (3G) mobile have been experienced. After the communication system and the evolved packet system (EPS), the 3rd generation partnership project (3GPP) proposed a new generation mobile communication system in the 15th release (Rel-15) phase. Fifth generation system (5th generation system, 5GS).

5GS adopts a completely different network architecture than EPS. Typically, in the 5G core network (5GCN), mobility management (MM) and session management (SM) are separated, and the control plane (control) The plane, CP) is separated from the user plane (UP), and the serviced control plane architecture and service interface protocol are adopted. The session management context of the 5GS includes a packet data unit (PDU) session (PDU session). Currently, the maximum number of theoretically supported PDU sessions in the 5GS is 256, and one PDU session may include one or Multiple QoS flows. That is to say, at the beginning of the proposed 5GS, it aims to provide a universal access network to provide access services for terminals of different application types in different vertical industries, which satisfies the concurrent data service requirements of the terminal.

However, when 3GPP defines the interoperability between 5GS and EPS, the coordination of session management between 5GS and EPS is realized by mapping between EPS bearer context and 5G QoS flow. Considering the backward compatibility with the EPS, the current 3GPP supports the maximum number of PDU sessions supported by the 5GS, which is consistent with the maximum number of EPS bearers supported in the EPS, that is, the maximum supported by 11, which obviously cannot be satisfied. Concurrent data service requirements of the terminal. Considering that 5GS can theoretically support more QoS flows, it is an inevitable trend to extend QoS flows in 5GS. However, how to deal with the problems caused by QoS flow expansion when 5GS and EPS interoperate is an urgent problem to be solved.

Summary of the invention

The embodiment of the present application provides a QoS flow processing method, device, and system, which can solve the problem of extending QoS flow when a target system supporting extended QoS flow and EPS interoperate, wherein the target system supporting the extended QoS flow can be, for example, 5GS or other systems are not limited in this embodiment.

To achieve the above objective, the embodiment of the present application adopts the following technical solutions:

In a first aspect, a quality of service QoS flow processing method is provided, the method comprising: a terminal having an active state extended QoS flow accessing an evolved packet system EPS; the terminal suspending the extended QoS flow. Based on the QoS flow processing method, it can solve the problem caused by the QoS flow expansion when the target system supporting the extended QoS flow and the EPS interoperate, and avoid the possibility that the terminal may move from the target system supporting the extended QoS flow to the EPS. The problem that the extended QoS flow must be deleted, and then the suspended extended QoS flow can be directly restored in the case that the subsequent terminal re-accesses the target system supporting the extended QoS flow, without rebuilding the extended QoS flow, thereby realizing the service Quick recovery.

In a possible design, the method further includes: deleting, in the case that the suspended extended QoS flow is still in a suspended state when the first preset duration arrives, the terminal deletes the suspended extended QoS flow. Based on the solution, it is possible to avoid the problem of resource waste caused by the hang of the extended QoS flow.

In a possible design, the method further includes: the terminal having the suspended extended QoS flow accessing a target system supporting the extended QoS flow; the terminal having the active state extended QoS flow session in the target system The management network element sends a session modification request, the session modification request carrying at least one of a flow identifier of the extended QoS flow or a session identifier of the session to which the extended QoS flow belongs, the session modification request being used to restore the extended QoS flow; the terminal Receiving a session modification command from the session management network element, the session modification command carrying a flow identifier of the extended QoS flow; the terminal recovering the suspended extended QoS flow according to the flow identifier of the extended QoS flow. Based on the solution, since the terminal re-accesses the target system supporting the extended QoS flow, the extended QoS flow does not need to be reconstructed, but the suspended extended QoS flow is directly restored, so that the service can be quickly recovered.

In a possible design, the session modification command further carries a second preset duration; the method further includes: the terminal storing the second preset duration, wherein the second preset duration is the extended QoS flow suspension Length of time. Based on the scheme, the length of the hang time of the extended QoS flow can be updated in time.

In a second aspect, a method for processing a quality of service QoS stream is provided, the method comprising: a session management network element having an active state extended QoS flow of the terminal determines that the terminal accesses an evolved packet system EPS; the session management network element The extended QoS flow is suspended; the session management network element sends a first notification message to the network device associated with the extended QoS flow, and the first notification message is used to notify the network device to suspend the extended QoS flow. Based on the QoS flow processing method, it can solve the problem caused by the QoS flow expansion when the target system supporting the extended QoS flow and the EPS interoperate, and avoid the possibility that the terminal may move from the target system supporting the extended QoS flow to the EPS. The problem that the extended QoS flow must be deleted, and then the suspended extended QoS flow can be directly restored in the case that the subsequent terminal re-accesses the target system supporting the extended QoS flow, without rebuilding the extended QoS flow, thereby realizing the service Quick recovery.

In a possible design, the method further includes: when the suspended extended QoS flow is still in a suspended state when the first preset duration arrives, the session management network element deletes the suspended extended QoS And the session management network element sends a second notification message to the network device, where the second notification message is used to notify the network device to delete the suspended extended QoS flow. Based on the solution, it is possible to avoid the problem of resource waste caused by the hang of the extended QoS flow.

Optionally, the second notification message carries at least one of a flow identifier of the extended QoS flow or a session identifier of a session to which the extended QoS flow belongs.

In a possible design, the method further includes: in case the terminal accesses a target system supporting the extended QoS flow, the session management network element receives a session modification request from the terminal, the session modification request carrying the extension At least one of a flow identifier of the QoS flow or a session identifier of the session to which the extended QoS flow belongs; the session management network element recovers the extended QoS flow according to the session modification request; and the session management network element sends the session QoS element to the network device The indication information is used to indicate that the network device resumes the suspended extended QoS flow. Based on the solution, since the terminal re-accesses the target system supporting the extended QoS flow, the extended QoS flow does not need to be reconstructed, but the suspended extended QoS flow is directly restored, so that the service can be quickly recovered.

In a possible design, the network device includes a user plane function network element; the session management network element sends the indication information to the network device, where the session management network element sends a packet forwarding control protocol to the user plane function network element. A PFCP session modification request, the PFCP session modification request carrying the indication information.

In a possible design, the network device includes a network open network element; the session management network element sends the indication information to the network device, where the session management network element sends a session update request to the network open network element, the session The update request carries the indication information.

Optionally, the indication information includes at least one of a flow identifier of the extended QoS flow or a session identifier of a session to which the extended QoS flow belongs.

In a possible design, the method further includes: the session management network element sending a session modification command to the terminal, the session modification command carrying a flow identifier of the extended QoS flow.

In a possible design, after the session management network element suspends the extended QoS flow, the method further includes: the session management network element storing a terminal context related to the suspended extended QoS flow, the terminal context The identifier information of the terminal, the identifier information of the network device, and the first preset duration are included, where the first preset duration is a length of time for the extended QoS flow to hang.

In a possible design, the session management network element determines that the terminal accesses the EPS, and the session management network element receives a context request message, where the context request message carries a mobility management network serving the terminal in the evolved packet system EPS. Meta-information for requesting the context of the mapped EPS bearer of the terminal. Based on the scheme, the session management network element can determine that the terminal accesses the EPS.

In a third aspect, a QoS flow processing method is provided, the method comprising: when a terminal accesses an evolved packet system EPS, a network device having an active state extended QoS flow of the terminal receives the extended QoS flow The first notification message; the network device suspends the extended QoS flow according to the first notification message. Based on the QoS flow processing method, it can solve the problem caused by the QoS flow expansion when the target system supporting the extended QoS flow and the EPS interoperate, and avoid the possibility that the terminal may move from the target system supporting the extended QoS flow to the EPS. The problem that the extended QoS flow must be deleted, and then the suspended extended QoS flow can be directly restored in the case that the subsequent terminal re-accesses the target system supporting the extended QoS flow, without rebuilding the extended QoS flow, thereby realizing the service Quick recovery.

In a possible design, the method further includes: when the suspended extended QoS flow is still in a suspended state when the first preset duration arrives, the network device receives the extended pending QoS flow a second notification message; the network device deletes the suspended extended QoS flow according to the second notification message. Based on the solution, it is possible to avoid the problem of resource waste caused by the hang of the extended QoS flow.

In a possible design, the method further includes: when the terminal accesses the target system supporting the extended QoS flow, the network device receives the indication information of the resumed extended QoS flow; the network device according to the Indicates that the extended QoS flow is resumed. Based on the solution, since the terminal re-accesses the target system supporting the extended QoS flow, the extended QoS flow does not need to be reconstructed, but the suspended extended QoS flow is directly restored, so that the service can be quickly recovered.

In a possible design, the network device includes a user plane function network element; the network device receives the indication information of the resumed extended QoS flow, and the network device receives the packet forwarding control protocol PFCP session modification request, where The PFCP session modification request carries the indication information.

In a possible design, the network device includes a network open network element; the network device receives the indication information of the resumed extended QoS flow, and the network device receives a session update request, where the session update request carries the indication information.

In a fourth aspect, a terminal is provided, the terminal having the function of implementing the method of any of the above first aspects. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

A fifth aspect provides a terminal, including: a processor and a memory; the memory is configured to store a computer execution instruction, and when the terminal is running, the processor executes the computer execution instruction stored in the memory, so that the terminal performs, for example, The QoS stream processing method according to any of the above aspects.

In a sixth aspect, a terminal is provided, comprising: a processor; the processor is configured to perform coupling with a memory, and after reading an instruction in the memory, perform QoS according to any one of the foregoing first aspects according to the instruction Stream processing method.

A seventh aspect, a computer readable storage medium having instructions stored therein that, when executed on a computer, cause the computer to perform the QoS stream processing of any of the above first aspects method.

In an eighth aspect, a computer program product comprising instructions, when run on a computer, causes the computer to perform the QoS stream processing method of any of the above first aspects.

A ninth aspect, a chip system is provided, the chip system comprising a processor, configured to support a terminal to implement the functions involved in the foregoing first aspect, for example, after the terminal having the active state extended QoS flow accesses the EPS, the QoS flow is extended. Hang up. In a possible design, the chip system further includes a memory for storing necessary program instructions and data of the terminal. The chip system can be composed of chips, and can also include chips and other discrete devices.

For the technical effects brought by any one of the fourth aspect to the ninth aspect, refer to the technical effects brought by different design modes in the first aspect, and details are not described herein again.

In a tenth aspect, a session management network element is provided, the session management network element having the function of implementing the method of any of the foregoing second aspects. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In an eleventh aspect, a session management network element is provided, including: a processor and a memory; the memory is configured to store a computer execution instruction, and when the session management network element is running, the processor executes the computer execution instruction stored by the memory So that the session management network element performs the QoS flow processing method according to any one of the above second aspects.

A twelfth aspect, a session management network element includes: a processor; the processor is configured to couple with a memory, and after reading an instruction in the memory, execute any one of the foregoing second aspects according to the instruction The QoS flow processing method.

A thirteenth aspect, a computer readable storage medium having stored therein instructions that, when executed on a computer, cause the computer to perform the QoS flow of any of the above second aspects Approach.

In a fourteenth aspect, a computer program product comprising instructions, when run on a computer, causes the computer to perform the QoS stream processing method of any of the above second aspects.

According to a fifteenth aspect, a chip system is provided, the chip system includes a processor, configured to support a session management network element to implement the functions involved in the foregoing second aspect, for example, determining that the terminal hangs the EPS and then extends the extended QoS flow. . In one possible design, the chip system further includes a memory for storing program instructions and data necessary for the session management network element. The chip system can be composed of chips, and can also include chips and other discrete devices.

For the technical effects brought by any one of the tenth to fifteenth aspects, refer to the technical effects brought by different design modes in the second aspect, and details are not described herein again.

In a sixteenth aspect, a network device is provided, the network device having the function of implementing the method of any of the above third aspects. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In a seventeenth aspect, a network device is provided, comprising: a processor and a memory; the memory is configured to store a computer execution instruction, and when the network device is running, the processor executes the computer execution instruction stored in the memory to enable the The network device performs the QoS stream processing method according to any one of the above third aspects.

An eighteenth aspect, a network device, comprising: a processor; the processor is configured to be coupled to a memory, and after reading an instruction in the memory, perform the instruction according to any one of the foregoing third aspects according to the instruction QoS flow processing method.

A nineteenth aspect, a computer readable storage medium having instructions stored therein that, when executed on a computer, cause the computer to perform the QoS flow of any of the above third aspects Approach.

In a twentieth aspect, a computer program product comprising instructions, when run on a computer, causes the computer to perform the QoS stream processing method of any of the above third aspects.

A twenty-first aspect, a chip system is provided, the chip system comprising a processor, configured to support a network device to implement the functions involved in the foregoing aspects, for example, suspending the extended QoS flow according to the first notification message . In a possible design, the chip system further includes a memory for storing necessary program instructions and data of the network device. The chip system can be composed of chips, and can also include chips and other discrete devices.

For the technical effects brought by any one of the seventeenth to twenty-first aspects, refer to the technical effects brought by different design modes in the third aspect, and details are not described herein again.

In a twenty-second aspect, a QoS stream processing system is provided, the QoS stream processing system comprising the session management network element of the above aspect and the network device of the above aspect.

These and other aspects of the present application will be more readily apparent from the following description of the embodiments.

DRAWINGS

1 is a schematic diagram 1 of a network architecture provided by an embodiment of the present application;

2 is a schematic diagram 2 of a network architecture provided by an embodiment of the present application;

FIG. 3 is a schematic structural diagram of a QoS flow processing system according to an embodiment of the present disclosure;

4 is a schematic structural diagram of hardware of a communication device according to an embodiment of the present disclosure;

FIG. 5 is a schematic diagram of a capability negotiation process provided by an embodiment of the present application;

FIG. 6 is a schematic flowchart 1 of a QoS flow processing method according to an embodiment of the present application;

FIG. 7 is a second schematic flowchart of a QoS flow processing method according to an embodiment of the present disclosure;

FIG. 8 is a schematic flowchart 3 of a QoS flow processing method according to an embodiment of the present disclosure;

FIG. 9 is a schematic structural diagram of an apparatus according to an embodiment of the present application;

FIG. 10 is a schematic structural diagram of a session management network element according to an embodiment of the present disclosure;

FIG. 11 is a schematic structural diagram of a network device according to an embodiment of the present disclosure.

Detailed ways

First, the network architecture involved in the embodiment of the present application is as follows:

As shown in FIG. 1 , the network architecture involved in the embodiment of the present application includes an existing 5 GS. The 5GS includes access and mobility management function (AMF) network elements, session management function (SMF) network elements, user plane function (UPF) network elements, and unified data management. (unified data management, UDM) network element, policy control function (PCF) network element, authentication server function (AUSF) network element, network exposure function (NEF) network element, and Some network elements (not shown), such as a network function storage function (NRF) network element, are not specifically limited in this embodiment of the present application.

As shown in FIG. 1 , in the embodiment of the present application, the terminal accesses the 5GS through the access device, and the terminal communicates with the AMF network element through the Next Generation (N) 1 interface (N1 for short), and the access device passes the The N2 interface (N2) communicates with the AMF network element. The access device communicates with the UPF network element through the N3 interface (N3). The AMF network element communicates with the SMF network element through the N11 interface (N11), and the AMF network element passes the N8 interface. (N8) communicates with the UDM network element. The AMF network element communicates with the AUSF network element through the N12 interface (N12 for short). The AMF network element communicates with the PCF network element through the N15 interface (N15 for short), and the SMF network element passes the N7 interface. N7) communicates with the PCF network element. The SMF network element communicates with the UPF network element through the N4 interface (N4). The NEF network element communicates with the SMF network element through the N29 interface (N29). The UPF network element passes the N6 interface (N6 for short). Access to the data network.

In addition, as shown in FIG. 1 , in order to implement interworking between the 5GS and the EPS, the network architecture involved in the embodiment of the present application may further include a mobility management entity (MME) in the EPS, where the MME passes the N26 interface ( Referred to as N26), it communicates with the SMF network element. Certainly, the network architecture involved in the embodiment of the present application may further include other network elements in the EPS, such as an evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (evolved UMTS territorial radio access network, E-UTRAN) device, packet data network (PDN) user plane function (PGW-U) network element, PDN gateway control plane function (PGW-C) The network element, the device and the charging rule function (PCRF) network element, the home subscriber server (HSS), and other network elements or devices, etc., are not specifically limited in this embodiment.

In a possible implementation manner, some network elements in the 5GS and EPS interworking architecture may be deployed in a unified manner. For example, as shown in FIG. 2, it is a schematic diagram of an existing 5GS and EPS interworking architecture. Among them, 5GS and EPS share UPF network element + PGW-U network element, SMF network element + PGW-C network element, PCF network element + PCRF network element, UDM network element + HSS. Here, "+" means the setting, UPF is the user plane function in the 5GS, PGW-U is the gateway user plane function in the EPS corresponding to the UPF, SMF is the session management function in the 5GS, and PGW-C is the corresponding to the SMF. The gateway control plane function in the EPS, the PCF is the policy control function in the 5GS, and the PCRF is the policy charging rule function in the EPS corresponding to the PCF.

In addition, as shown in FIG. 2, the foregoing 5GS and EPS interworking architecture may further include an MME and a Serving Gateway (SGW) in the EPS, and an AMF network element in the 5GS. Optionally, the 5GS and EPS interworking architecture may further include a network slice selection function (NSSF) network element and some network elements, not shown, such as NEF network elements. limited. When the AMF network element cannot select a network slice for the terminal, the AMF network element may request the NSSF network element to select a network slice for the terminal.

As shown in FIG. 2, in the embodiment of the present application, the terminal accesses the EPS through the E-UTRAN device, and the terminal accesses the 5GS through the next generation radio access network (NG-RAN) device. The E-UTRAN device communicates with the MME through the S1-MME interface, the E-UTRAN device communicates with the SGW through the S1-U interface, the MME communicates with the SGW through the S11 interface, the MME communicates with the UDM network element + HSS through the S6a interface, and the MME passes the N26 interface. Communicate with the AMF network element, the SGW communicates with the UPF network element + PGW-U network element through the S5-U interface, and the SGW communicates with the SMF network element + PGW-C network element through the S5-C interface, and the UPF network element + PGW-U network The element communicates with the NG-RAN device through the N3 interface, and the UPF network element + PGW-U network element communicates with the SMF network element + PGW-C network element through the N4 interface, and the SMF network element + PGW-C network element passes the N7 interface and the PCF network. Element + PCRF network element communication, UDM network element + HSS communicates with SMF network element + PGW-C network element through N10 interface, UDM network element + HSS communicates with AMF network element through N8 interface, PCF network element + PCRF network element passes N15 The interface communicates with the AMF network element. The SMF network element + PGW-C network element communicates with the AMF network element through the N11 interface. The AMF network element communicates with the NG-RAN device through the N2 interface, and the AMF network element communicates with the terminal through the N1 interface.

It should be noted that FIG. 2 is only a schematic diagram of an existing 5 GS and EPS interworking architecture. Of course, the interworking architecture of the 5 GS and the EPS may be other, which is not specifically limited in this embodiment.

It should be noted that the name of the interface between the network elements and the network elements in FIG. 1 or FIG. 2 is only an example. In the implementation, the name of the interface between each network element and each network element may be other. This example does not specifically limit this.

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. In the description of the present application, unless otherwise stated, "/" means the meaning of or, for example, A/B may represent A or B; "and/or" herein is merely an association describing the associated object. The relationship indicates that there may be three kinds of relationships, for example, A and/or B, which may indicate that there are three cases where A exists separately, A and B exist at the same time, and B exists separately. Also, in the description of the present application, "a plurality" means two or more than two unless otherwise stated. In addition, in order to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first", "second", and the like are used to distinguish the same items or similar items whose functions and functions are substantially the same. Those skilled in the art can understand that the words "first", "second" and the like do not limit the number and execution order, and the words "first", "second" and the like are not necessarily limited.

In addition, the network architecture and the service scenario described in the embodiments of the present application are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present application, and are not limited to the technical solutions provided by the embodiments of the present application. With the evolution of the network architecture and the emergence of new service scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

As shown in FIG. 3, a QoS flow processing system 30 is provided in the embodiment of the present application. The QoS flow processing system 30 includes a session management network element 301 and a network device 302 with an active state extended QoS flow of the terminal.

The session management network element 301 is configured to suspend the extended QoS flow after determining that the terminal accesses the EPS, and send a first notification message to the network device 302 associated with the extended QoS flow, where the first notification message is used. The network device 302 is notified to suspend the extended QoS flow.

The network device 302 is configured to receive a first notification message from the session management network element 301, and suspend the extended QoS flow according to the first notification message.

Optionally, the extended QoS flow in the embodiment of the present application refers to a QoS flow of the QoS flow that cannot be mapped to the EPS bearer or the information of the associated EPS bearer in the target system that supports the extended QoS flow. . Exemplarily, the target system supporting the extended QoS flow may be, for example, the above 5GS, and the extended QoS flow may be: when the 5GS supports more QoS flows than the EPS supports the maximum number of EPS bearers, the EPS maximum EPS bearer number is exceeded. QoS flow. For example, the number of QoS flows supported by the 5GS is 32, and the maximum number of EPS bearers supported by the EPS is 16, and the 16 additional QoS flows are extended QoS flows; or, exemplaryly, the extended QoS flows may be: During the process of creating a flow, the terminal or the session management network element does not generate information about the associated EPS bearer for the QoS flow. The information of the EPS bearer associated with the QoS flow includes an EPS bearer identity and an EPS QoS parameter. (mapped EPS QoS parameters), mapped extended EPS QoS parameters, and optionally mapped traffic flow template, etc.; or, by way of example, the extended QoS flow may be: 5GS policy The defined QoS flows that cannot be mapped to EPS bearers, and so on.

It should be noted that, in the embodiment of the present application, the information of the EPS bearer associated with the QoS flow is also referred to as the information of the EPS bearer of the QoS flow or the mapped EPS bearer context of the QoS flow, which is not specifically limited in this embodiment of the present application.

Optionally, in the embodiment of the present application, the information about the EPS bearer associated with the QoS flow may include, for example, an identifier of the EPS bearer, mapping the EPS QoS parameter, mapping the extended EPS QoS parameter, mapping the service flow template, and mapping the mobility associated with the EPS bearer. The embodiment of the present application does not specifically limit the at least one of the address information of the management network element and the address information of the gateway network element.

Optionally, the extended QoS flow in the embodiment of the present application is only a naming manner, and may also have other namings for characterization of a QoS flow that cannot be mapped to an EPS bearer or a non-mapped EPS in a target system that supports extended QoS flows. The QoS flow of the carried information, for example, the QoS flow that cannot be interoperable with the EPS, is not specifically limited in this embodiment of the present application.

Optionally, the network device in the embodiment of the present application includes a user plane function network element or a network open network element, which is not specifically limited in this embodiment.

Optionally, the session management network element 301 and the network device 302 in the embodiment of the present application may directly communicate with each other, and may also perform communication by forwarding of other devices, which is not specifically limited in this embodiment of the present application.

Optionally, the QoS flow processing system provided by the embodiment of the present application may be applied to the network architecture shown in FIG. 1 or FIG. 2, and may also be applied to other network architectures with QoS flows. Specifically limited.

Illustratively, if the QoS flow processing system provided by the embodiment of the present application is applied to the network architecture as shown in FIG. 1 or FIG. 2, the network element or entity corresponding to the foregoing session management network element may be the foregoing SMF network. The network element or the entity corresponding to the user plane function network element may be the above-mentioned UPF network element, and the network element or entity corresponding to the capability open network element may be the NEF network element.

In the QoS flow processing system provided by the embodiment of the present application, the session management network element with the active state extended QoS flow of the terminal suspends the extended QoS flow after determining that the terminal accesses the EPS, and the network associated with the extended QoS flow. The device sends a first notification message, which is used to notify the network device to suspend the extended QoS flow. Therefore, based on the QoS flow processing system, it is possible to solve the problem of how to handle the QoS flow extension when the target system supporting the extended QoS flow and the EPS interoperation, and avoid the possibility that the terminal moves from the target system supporting the extended QoS flow to the EPS. The resulting extended QoS flow must be deleted, and then the suspended extended QoS flow can be directly restored in the case that the subsequent terminal re-accesses the target system supporting the extended QoS flow without reconstructing the extended QoS flow, thereby realizing Rapid recovery of business.

Optionally, the terminal involved in the embodiment of the present application may include various handheld devices having wireless communication functions, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to the wireless modem; Including user unit (subscriber unit), cellular phone, smart phone, wireless data card, personal digital assistant (PDA) computer, tablet computer, wireless modem (modem), handheld device Handheld, laptop computer, cordless phone or wireless local loop (WLL) station, machine type communication (MTC) terminal, user equipment (user equipment) , UE), mobile station (MS), terminal device or relay user equipment. The relay user equipment may be, for example, a 5G residential gateway (RG). For convenience of description, in the present application, the above mentioned devices are collectively referred to as terminals.

Optionally, the access device involved in the embodiment of the present application refers to a device that accesses the core network, and may be, for example, an NG-RAN device, a base station, a broadband network gateway (BNG), and an aggregation switch. Non-3rd Generation Partnership Project (3GPP) access equipment, etc. The base station 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, and the like.

Optionally, the session management network element or the network device in the embodiment of the present application may be implemented by one device, or may be implemented by multiple devices, or may be a function module in a device. Specifically limited. It can be understood that the above functions can be either a network component in a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform).

For example, the session management network element or the network device in the embodiment of the present application may be implemented by using the communication device in FIG. 4. FIG. 4 is a schematic structural diagram of hardware of a communication device according to an embodiment of the present application. The communication device 400 includes at least one processor 401, a communication line 402, a memory 403, and at least one communication interface 404.

The processor 401 can be a general central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more for controlling the execution of the program of the present application. integrated circuit.

Communication line 402 can include a path for communicating information between the components described above.

Communication interface 404, using any type of transceiver, for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .

The memory 403 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions. The dynamic storage device can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this. The memory may be stand-alone and connected to the processor via communication line 402. The memory can also be integrated with the processor.

The memory 403 is used to store computer execution instructions for executing the solution of the present application, and is controlled by the processor 401 for execution. The processor 401 is configured to execute computer execution instructions stored in the memory 403, thereby implementing the QoS stream processing method provided by the following embodiments of the present application.

Optionally, the computer-executed instructions in the embodiment of the present application may also be referred to as an application code, which is not specifically limited in this embodiment of the present application.

In a specific implementation, as an embodiment, the processor 401 may include one or more CPUs, such as CPU0 and CPU1 in FIG.

In a particular implementation, as an embodiment, communication device 400 can include multiple processors, such as processor 401 and processor 408 in FIG. Each of these processors can be a single-CPU processor or a multi-core processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.

In a particular implementation, as an embodiment, the communication device 400 can also include an output device 405 and an input device 406. Output device 405 is in communication with processor 401 and can display information in a variety of ways. For example, the output device 405 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. Wait. Input device 406 is in communication with processor 401 and can receive user input in a variety of ways. For example, input device 406 can be a mouse, keyboard, touch screen device, or sensing device, and the like.

The communication device 400 described above may be a general purpose device or a dedicated device. In a specific implementation, the communication device 400 can be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, or the like in FIG. device. The embodiment of the present application does not limit the type of the communication device 400.

The QoS flow processing method provided by the embodiment of the present application will be specifically described below with reference to FIG. 1 to FIG.

It should be noted that the name of the message or the name of each parameter in the message in the following embodiments of the present application is only an example, and may be other names in the specific implementation. limited.

In addition, in the following embodiments of the present application, the message sent by the terminal to the core network and the message between the core network carry the identity information of the terminal, so that the receiver knows which terminal to operate for. That is to say, the operations of creating, suspending, restoring, or deleting all the extended QoS flows are all granularities of the terminal, and are collectively described herein, and are not described here.

First, the QoS flow processing system shown in FIG. 3 is applied to the network architecture shown in FIG. 1 or FIG. 2 as an example. As shown in FIG. 5, a flow for the terminal and the network side to support extended QoS flow negotiation is given. The negotiation process is the basis of the QoS flow processing method provided by the following embodiments of the present application, and includes the following steps:

S501. The terminal sends a first non-access stratum (NAS) message to the AMF network element, so that the AMF network element receives the first NAS message from the terminal.

The first NAS message carries the UE extended QoS flow support capability information, and is used to tell the AMF network element that the terminal supports the extended QOS flow.

Optionally, after receiving the first NAS message, the AMF network element may save the capability information of the terminal to support the extended QoS flow in the context of the terminal, which is not specifically limited in this embodiment.

Optionally, in this embodiment, the first NAS message may be different messages corresponding to different processes. For example, corresponding to the registration process, the first NAS message may be, for example, a registration request message; or, corresponding to a PDU session establishment process, the first NAS message may be, for example, a NAS transport message, the NAS transmission. A complete PDU session establishment request message is encapsulated in the message. In this embodiment, the specific message of the first NAS message is not specifically limited.

Optionally, for the PDU session establishment process, the PDU session establishment request may also carry the capability information of the terminal to support the extended QoS flow, which is not specifically limited in this embodiment.

S502. The AMF network element invokes a service operation 1 to request the SMF network element to establish a PDU session for the terminal.

Illustratively, in this embodiment, the service operation 1 invoked by the AMF network element may be a PDU session_Create SM Context provided by the SMF network element, which is not specifically limited in this embodiment.

The service operation 1 carries the capability information of the terminal supporting the extended QoS flow, and is used to tell the SMF network element that the terminal supports the extended QoS flow; or, for the PDU session establishment process, optionally, the service operation request 1 carries the terminal. The PDU session establishment request is sent, and the PDU session establishment request carries the capability information of the terminal to support the extended QoS flow, and the SMF network element can learn the capability information of the extended QoS flow supported by the terminal from the PDU session establishment request sent by the terminal. This example does not specifically limit this.

Optionally, in this embodiment, after acquiring the capability information of the terminal to support the extended QoS flow, the SMF network element may save the capability information of the terminal to support the extended QoS flow in the context of the terminal, which is not specifically limited in this embodiment.

Optionally, in the registration process or the PDU session establishment process, if the extended QoS flow affected by the process is an extended QoS flow through the UPF network element, proceed to steps S503a-S504a: if the extended QoS flow affected by the process If the QoS flow is extended by the NEF network element, steps S503b-S504b are continued.

The steps S503a-S504a of this embodiment are as follows:

The S503a and the SMF network element determine the UPF network element according to the capability information of the terminal supporting the extended QoS flow, to ensure that the selected UPF network element supports the extended QoS flow.

S504a. The SMF network element sends a packet forwarding control protocol (PFCP) session establishment request (PFCP session establishment request) message to the UPF network element, so that the UPF network element receives the PFCP session establishment request message from the SMF network element.

The PFCP session establishment request is used to establish a PFCP session corresponding to the PDU session.

The PFCP session establishment request message carries the capability information of the terminal supporting the extended QoS flow, and is used to tell the UPF network element that the terminal supports the extended QoS flow.

Optionally, in this embodiment, after receiving the capability information of the extended QoS flow from the terminal of the SMF network element, the UPF network element may save the capability information of the terminal to support the extended QoS flow in the context of the terminal, which is not used in this embodiment. Specifically limited.

Wherein, steps S503b-S504b of this embodiment are as follows:

S503b. The SMF network element determines the NEF network element according to the capability information of the terminal supporting the extended QoS flow, to ensure that the selected NEF network element supports the extended QoS flow.

S504b. The SMF network element invokes service operation 2 to instruct the NEF network element to establish a PDU session for the terminal.

Illustratively, in this embodiment, the service operation 2 invoked by the SMF network element may be a PDU session_create session management context provided by the SMF network element, which is not specifically limited in this embodiment.

The service operation request 2 carries the capability information of the terminal supporting the extended QoS flow, and is intended to inform the NEF network element that the terminal supports the extended QoS flow.

Optionally, in this embodiment, after the NEF network element receives the capability information of the extended QoS flow from the terminal of the SMF network element, the capability information of the terminal supporting the extended QoS flow may be saved in the context of the terminal, which is not used in this embodiment. Specifically limited.

Further, the process of the terminal and the network side supporting the extended QoS flow negotiation provided by the embodiment of the present application further includes the following steps:

S505. The SMF network element sends a service operation response to the AMF network element, so that the AMF network element receives the service operation response from the SMF network element.

The service operation response in step S505 is a response of the service operation 1 invoked by the AMF network element in step S502.

The service operation response carries the capability information of the network supporting the extended QoS flow, so that the AMF network element can learn the capability information of the network to support the extended QoS flow according to the service operation response; or, for the PDU session establishment process, optionally, The service operation response carries a PDU session establishment accept message sent by the SMF network element to the terminal, where the PDU session establishment accept message carries the capability information of the network supporting the extended QoS flow, and is intended to inform the terminal network to support the extension. The QoS flow is not specifically limited in this embodiment.

Optionally, in this embodiment, the PDU session establishment accept message may further carry the extended QoS flow suspension (Suspend) length allocated by the SMF network element to the terminal, as in the first preset duration in the following embodiment. The second preset duration is used for the subsequent processing of the extended QoS flow, which is not specifically limited in this embodiment. Of course, the first preset duration or the second preset duration may be configured in the terminal and the SMF network element in advance, which is not specifically limited in this embodiment.

Optionally, in this embodiment, if the NAS process triggered by the first NAS message is successfully executed, the process of the terminal and the network side supporting the extended QoS flow negotiation further includes the following steps:

S506. The AMF network element sends a second NAS message to the terminal, so that the terminal receives the second NAS message from the AMF network element.

The second NAS message carries the capability information of the network supporting the extended QoS flow. Optionally, after receiving the second NAS message, the terminal may save the capability information of the network supporting the extended QoS flow in the context of the terminal.

Optionally, if the network does not support the extended QoS flow, the second NAS message does not carry the capability information of the network to support the extended QoS flow. In this way, the terminal can know whether the network supports the extended QoS flow according to the second NAS message.

Optionally, in this embodiment, the second NAS message may be different messages corresponding to different processes. For example, corresponding to the registration process, the second NAS message may be, for example, a registration accept message; or, corresponding to a PDU session establishment process, the second NAS message may be, for example, a NAS transport message, and the NAS transport message The complete PDU session establishment accept message is encapsulated, and the specific information of the second NAS message is not specifically limited in this embodiment.

It should be noted that the foregoing steps in FIG. 5 are all performed in a registration process initiated by a terminal or a PDU session establishment process, and the complete registration process or other steps included in the PDU session establishment process are prior art. This will not be repeated.

Based on the negotiation process provided by the embodiment, both the terminal and the network know whether the other party supports the extended QoS flow, and then the required extended QoS flow can be activated according to the needs of the service to meet the requirements of more service concurrency.

The actions of the terminal or the SMF network element or the UPF network element or the NEF network element in the foregoing steps S501 to S506 may be performed by the processor 401 in the communication device 400 shown in FIG. 4 calling the application code stored in the memory 403. This embodiment does not impose any limitation on this.

The QoS flow processing system shown in FIG. 3 is applied to the network architecture shown in FIG. 1 or FIG. 2 as an example. The QoS flow method provided in the embodiment of the present application is as shown in FIG. 6 to FIG. 8 .

Optionally, the application scenario of the QoS flow processing method is as follows: the terminal idle state of the active state extended QoS flow is moved to the EPS. As shown in FIG. 6, the QoS flow processing method provided in this embodiment includes the following steps:

S601. The terminal activates the extended QoS flow in the 5GS, and accesses the EPS after the idle state moves into the EPS.

In the embodiment of the present application, the terminal accessing the EPS specifically means that the terminal successfully selects a suitable cell of the access technology supported by the EPS for normal camping. For example, if the terminal successfully camps in an E-UTRAN suitable cell, it indicates that the terminal accesses the EPS, which is uniformly described herein, and will not be described below.

S602. The terminal sends a tracking area update (TAU) request message to the MME in the EPS, so that the MME receives the TAU request message from the terminal.

Wherein, the TAU request message is used to implement location update to the EPS.

S603. The MME sends a context request to the AMF network element in the 5GS supporting the extended QoS flow, so that the AMF network element receives the context request from the MME.

The context request is used to request the context of the terminal, including the mapped EPS bearer context of the terminal.

Optionally, in this embodiment, since the MME does not support the extended QoS flow, the context request in step S703 does not carry the capability information of the network supporting the extended QoS flow. After the AMF network element receives the context request from the MME, since the context request does not carry the capability information of the network supporting the extended QoS flow, the AMF network element can determine that the EPS does not support the extended QoS flow. Of course, if the AMF network element learns that the context request is sent by the MME, the AMF network element may also determine that the target network does not support the extended QoS flow, because the MME is a network element in the EPS, and the EPS itself does not support the extended QoS flow. This embodiment does not limit how the AMF network element determines that the EPS does not support the extended QoS flow.

S604. The AMF network element invokes a service operation to obtain a session management context (SM context) of the terminal from the SMF network element, where the session management context of the terminal includes a mapped EPS bearer context of the terminal.

Illustratively, the service operation invoked by the AMF network element may be a PDU session_Context Request (Nsmf_PDU Session_Context Request) provided by the SMF network element, which is not specifically limited in this embodiment.

The service operation carries the information of the MME, and is used to notify the SMF network element that the target side service network element of the SM context of the requesting terminal is the MME.

In addition, since the target side service network element of the terminal is the MME, the SMF network element can determine that the terminal of the active state extended QoS flow accesses the EPS, and then step S607 can be performed.

Optionally, in this embodiment, the information of the MME may be, for example, the identifier information of the MME and the capability information supported by the MME, which is not specifically limited in this embodiment.

S605. The SMF network element sends a service operation response to the AMF network element, so that the AMF network element receives the service operation response from the SMF network element.

The service operation response is a response of the service operation invoked by the AMF network element in step S604.

The service operation response carries a mapped EPS bearer context of the QoS flow of the terminal.

Optionally, in this embodiment, the SMF network element does not send the mapped EPS bearer context of the extended QoS flow to the AMF network element because the SMF network element learns that the serving network element of the target side is the MME. As a reasonable implementation manner, in the process of establishing the extended QoS flow, the SMF network element does not synchronously generate the mapped EPS bearer context of the extended QoS flow, that is, the mapped EPS bearer context of the extended QoS flow of the terminal that is not stored in the SMF network element. In this step, the mapped EPS bearer context of the non-extended QoS flow that the SMF network element can provide to the AMF network element is uniformly described herein, and details are not described herein.

Optionally, in this embodiment, if the terminal currently has multiple PDU sessions associated with multiple SMF network elements, the operations in steps S604-S605 are performed for each SMF network element, so that the AMF network element can obtain and The mapped EPS bearer context of the terminal corresponding to each PDU session is uniformly described herein, and is not described here.

S606. The AMF network element sends a context response to the MME, so that the MME receives the context response from the AMF network element.

The context response carries a mapped EPS bearer context of the QoS flow of the terminal.

S607: The SMF network element suspends all extended QoS flows of the terminal, that is, is in a suspended state.

Optionally, in this embodiment, the SMF network element may simultaneously start a suspension timer allocated to the terminal for a preset duration, and save the terminal context related to the suspended extended QoS flow, including the terminal. Identity information, address information of the AMF network element, address information of the UPF network element, or address information of the NEF network element, so that the SMF network element can identify which terminal the extended extended QoS flow is, and which UPF network element or The NEF network element is not specifically limited in this embodiment.

Optionally, there is no necessary sequence of execution between step S607 and steps S605-S606 in this embodiment, and step S607 may be performed first, and then steps S605-S606 may be performed; or steps S605-S606 may be performed first, and then steps S605-S606 may be performed first. Step S607 is performed; step S607 and steps S605-S606 are also performed at the same time, which is not specifically limited in this embodiment.

Optionally, if the suspended extended QoS flow is an extended QoS flow of the UPF network element, proceeding to steps S608a-S609a; if the suspended extended QoS flow is an extended QoS flow of the NEF network element, proceeding Steps S608b-S609b are performed.

The steps S608a-S609a of this embodiment are as follows:

S608a. The SMF network element sends a suspend notification message 1 to the UPF network element associated with the extended QoS flow, so that the UPF network element receives the suspend notification message 1 from the SMF network element.

Optionally, the suspension notification message 1 in this embodiment may carry a QoS flow identifier (QFI) of the extended QoS flow to be suspended or a session identifier of the PDU session to which the extended QoS flow to be suspended belongs. At least one of the purpose is to clearly inform the UPF network element to suspend only the extended QoS flow corresponding to the flow identifier of the extended QoS flow, or only the extended QoS flow associated with the PFCP session corresponding to the session identifier of the PDU session. Suspended, other QoS flows are not affected.

Optionally, the flow identifier of the extended QoS flow in this embodiment may be a rule identifier (QRI) of the QoS rule associated with the extended QoS flow, or may be an identifier QFI of the extended QoS flow itself. Etc., this embodiment does not specifically limit this.

S609a and the UPF network element suspend all extended QoS flows of the terminal according to the suspension notification message 1, that is, set to a suspended state.

Optionally, in this embodiment, the UPF network element further saves the terminal context related to the suspended extended QoS flow, including the identity information of the terminal, the address information of the SMF network element, and the like, which is not specifically limited in this embodiment.

Optionally, in this embodiment, after the UPF network element suspends all the extended QoS flows of the terminal, the UPF network element also discards the downlink data received from the suspended extended QoS flow, which is not used in this embodiment. Specifically limited.

The steps S608b-S609b of this embodiment are as follows:

S608b. The SMF network element sends a suspension notification message 2 to the NEF network element associated with the extended QoS flow, so that the NEF network element receives the suspension notification message 2 from the SMF network element.

Optionally, the suspension notification message 2 in this embodiment may carry at least one of a flow identifier of the extended QoS flow to be suspended or a session identifier of the PDU session to which the extended QoS flow to be suspended belongs. The NEF network element is informed that only the extended QoS flow corresponding to the flow identifier of the extended QoS flow is suspended, or only the extended QoS flow corresponding to the session identifier of the PDU session is suspended, and other QoS flows are not affected. For a description of the flow identifier of the extended QoS flow, refer to step S608a, and details are not described herein again.

S609b and the NEF network element suspend all extended QoS flows of the terminal according to the suspension notification message 1, that is, the suspended state is set.

Optionally, in this embodiment, the NEF network element further saves the terminal context related to the suspended extended QoS flow, including the identity information of the terminal, the address information of the SMF network element, and the like, which is not specifically limited in this embodiment.

Optionally, in this embodiment, after the NEF network element suspends all the extended QoS flows of the terminal, the NEF network element also discards the downlink data received from the suspended extended QoS flow, which is not used in this embodiment. Specifically limited.

Optionally, in this embodiment, if multiple extended QoS flows of the terminal are associated with multiple SMF network elements, each of the associated SMF network elements needs to perform the foregoing steps S607-S608a or S607-S608b, and the foregoing description is unified. , will not repeat them below.

Further, if the TAU process is successfully executed, the QoS flow processing method provided in this embodiment further includes the following steps:

S610. The MME sends a TAU accept message to the terminal, so that the terminal receives the TAU accept message from the MME.

Optionally, in this embodiment, since the MME does not support the extended QoS flow, the TAU accept message does not carry the capability information of the network supporting the extended QoS flow.

It should be noted that the steps S602-S610 in this embodiment are all performed in the TAU process initiated by the terminal. The other steps included in the complete TAU process are all prior art, and are not described herein.

Further, the QoS flow processing method provided in this embodiment further includes the following steps, as the terminal can learn that the target network does not support the extended QoS flow:

S611. The terminal suspends all extended QoS flows, that is, is suspended.

Optionally, in this embodiment, the terminal may start a suspension timer allocated to the terminal for a preset duration, and save a terminal context related to the suspended extended QoS flow, including the suspended extension. The session identifier of the PDU session to which the QoS flow belongs, and the like.

Optionally, in this embodiment, step S611 may be performed immediately after the terminal accesses the EPS, because the terminal itself knows that the EPS does not support the extended QoS flow, which is not specifically limited in this embodiment.

S612. If the suspended extended QoS flow is still in a suspended state when the first preset duration arrives, the terminal deletes the suspended extended QoS flow, for example, locally releasing the suspended extended QoS flow.

S613. The SMF network element deletes the suspended extended QoS flow when the suspended extended EPS bearer is still in the suspended state when the first preset duration arrives.

It should be noted that there is no necessary execution sequence between step S612 and step S613 in this embodiment, and step S612 may be performed first, and then step S613 may be performed; or step S613 may be performed first, and then step S612 is performed; Steps S612 and S613 may be performed at the same time, which is not specifically limited in this embodiment.

Further, if the suspended extended QoS flow is an extended QoS flow of the UPF network element, the QoS flow processing method provided in this embodiment further includes the following steps S614a-S615a; if the suspended extended QoS flow is through the NEF The QoS flow processing method provided by this embodiment further includes the following steps S614b-S615b.

Wherein, steps S614a-S615a of this embodiment are as follows:

The S614a and the SMF network element send a delete suspension notification message 1 to the UPF network element, so that the UPF network element receives the deletion suspension notification message 1 from the SMF network element.

The deletion pending notification message 1 is used to notify the UPF network element to delete the suspended extended QoS flow of the terminal.

The S615a and the UPF network element delete the suspended extended QoS flow of the terminal according to the deletion pending notification message 1.

Wherein, steps S614b-S615b of this embodiment are as follows:

S614b. The SMF network element sends a delete suspension notification message 2 to the NEF network element, so that the NEF network element receives the deletion suspension notification message 2 from the SMF network element.

The deletion pending notification message 2 is used to notify the NEF network element to delete the suspended extended QoS flow of the terminal.

The S615b and the NEF network element delete the suspended extended QoS flow of the terminal according to the delete pending notification message 2.

Based on the QoS flow processing method provided in this embodiment, it is possible to solve the problem of how to handle the QoS flow extension when the 5GS and EPS interoperate, and avoid the problem that the extended QoS flow that may be caused when the terminal moves from the 5GS to the EPS must be deleted. In the case that the subsequent terminal re-accesses the 5GS, the suspended extended QoS flow can be directly restored without rebuilding the extended QoS flow, thereby achieving fast service recovery.

The action of the terminal or the SMF network element or the UPF network element or the NEF network element in the foregoing steps S601 to S615a or S615b may be invoked by the processor 401 in the communication device 400 shown in FIG. 4 to call the application code stored in the memory 403. To perform this, this embodiment does not impose any limitation on this.

Optionally, if the application scenario of the QoS flow processing method is: the terminal connection state with the active state extended QoS flow is switched to the EPS, as shown in FIG. 7, the QoS flow processing method provided in this embodiment includes the following steps:

S701. The access device currently serving the terminal sends a handover request to the AMF network element currently serving the terminal, so that the AMF network element receives the handover request from the access device.

The handover request carries the identification information of the mobility management network element in the target network. In this embodiment, the target network is an EPS, and the mobility management network element in the target network is an MME.

S702-S703, the same as the steps S604-S605, the related description can refer to the embodiment shown in FIG. 6, and details are not described herein again.

S704. The AMF network element sends a relocation request to the MME, so that the MME receives the relocation request from the AMF network element.

The relocation request carries a mapped EPS bearer context of the QoS flow of the terminal.

Optionally, in this embodiment, the relocation request may also be a forwarding relocation request, which is not specifically limited in this embodiment.

S705. During the handover process, the access device sends a handover command to the terminal, so that the terminal receives the handover command from the access device.

S706. The terminal accesses the EPS according to the handover command.

For the related description, reference may be made to the embodiment shown in FIG. 6 , and details are not described herein again.

S708a-S709a, the same as the steps S608a-S609a, the related description can refer to the embodiment shown in FIG. 6, and details are not described herein again.

S708b-S709b, the same as the steps S608b-S609b, the related description can refer to the embodiment shown in FIG. 6, and details are not described herein again.

S710. The terminal sends a TAU request message to the MME, so that the MME receives the TAU request message from the terminal.

S711. The MME sends a TAU accept message to the terminal, so that the terminal receives the TAU accept message from the MME.

Optionally, the step S707-S709a or the S707-S709b in the embodiment may be performed after the terminal initiates the TAU process (ie, step S710), which is not specifically limited in this embodiment.

It should be noted that all the steps S701-S711 in the embodiment are performed in the handover process and the TAU process initiated by the terminal, and the complete handover process and other steps included in the TAU process are all prior art. Do not repeat them.

S712-S714, the same as the steps S611-S613, the related description can refer to the embodiment shown in FIG. 6, and details are not described herein again.

For the related description, refer to the embodiment shown in FIG. 6 and the details are not described herein again.

S715b-S716b, the same as the steps S614b-S615b, the related description can refer to the embodiment shown in FIG. 6, and details are not described herein again.

Optionally, in this embodiment, after the terminal accesses the EPS, that is, after the step S706, the step S712 is performed, because the terminal itself knows that the EPS does not support the extended QoS flow, which is not specifically limited in this embodiment.

The action of the terminal or the SMF network element or the UPF network element or the NEF network element in the foregoing steps S701 to S716a or S716b may be invoked by the processor 401 in the communication device 400 shown in FIG. 4 to call the application code stored in the memory 403. To perform this, this embodiment does not impose any limitation on this.

Optionally, the application scenario of the QoS flow processing method is as follows: the terminal idle state mobile with the suspended state extended QoS flow or the connected state is switched to the 5GS, as shown in FIG. 8 , the QoS flow processing method provided in this embodiment Including the following steps:

S801. The terminal with the suspended state extended QoS flow accesses the 5GS.

The pending timer on the terminal is running to indicate that the terminal has an extended QoS flow in a suspended state.

Optionally, in this embodiment, the terminal may initiate a registration update process to the 5GS. If the terminal is connected to the 5GS, the mapping between the EPS bearer context and the non-extended QoS flow between the terminal and the 5GS is completed in the handover process, and the registration update process is initiated by the terminal from the connected state after the handover process is completed. The mapping between the EPS bearer context and the non-extended QoS flow between the terminal and the 5GS is completed in the registration update process, and is not described here.

Optionally, in this embodiment, for the registration update process initiated by the terminal, if the AMF network element changes in the registration update process, the service AMF network element when the terminal returns from the EPS to the 5GS is different from the last terminal. The AMF network element registered in the 5GS, the service AMF network element when the terminal returns from the EPS to the 5GS will obtain the context information of the terminal from the AMF network element registered by the last terminal in the 5GS, including the session management context information of the terminal, for example. The information of the PDU session and the information of the associated SMF network element are collectively described herein, and are not described here.

Further, after the registration update process is successfully completed, if the extended QoS flow in the suspended state is still stored on the terminal, the QoS flow processing method provided in this embodiment may further include the following steps:

S802. The terminal sends the NAS transmission message 1 to the AMF network element, so that the AMF network element receives the NAS transmission message 1 from the terminal.

The NAS transport message 1 carries a PDU session modification request, where the PDU session modification request carries the flow identifier of the suspended extended QoS flow or the session identifier of the PDU session to which the suspended extended QoS flow belongs. At least one, intended to clearly inform the recipient, to restore the extended QoS flow corresponding to the flow identifier of the suspended extended QoS flow, or to restore the extended QoS flow associated with the PDU session corresponding to the session identifier of the PDU session, other QoS flows Not affected. That is, the PDU session modification request is used to recover the suspended extended QoS flow.

For a description of the flow identifier of the extended QoS flow, reference may be made to the embodiment shown in FIG. 6, and details are not described herein again.

Optionally, the NAS transport message 1 in this embodiment may further carry the session identifier of the PDU session to which the suspended extended QoS flow belongs, and the session identifier is used to select the SMF network element, which is not specifically limited in this embodiment.

S803. The AMF network element determines the SMF network element.

Optionally, in this embodiment, the AMF network element may obtain the information of the corresponding SMF network element from the session management context of the terminal according to the session identifier of the PDU session to which the suspended extended QoS flow carried in the NAS transport message 1 belongs. The following operations are performed for each SMF network element.

S804. The AMF network element sends a PDU session modification request to the SMF network element, so that the SMF network element receives the PDU session modification request from the AMF network element.

Optionally, in this embodiment, the AMF network element may invoke a defined service operation to encapsulate the PDU session modification request. Illustratively, the service operation invoked by the AMF network element may be a PDU session_Update SM Context provided by the SMF network element, which is not specifically limited in this embodiment.

S805. The SMF network element recovers the suspended extended QoS flow according to the PDU session modification request, that is, clears the suspended state of the suspended extended QoS flow, and stops the running suspension timer.

Further, if the suspended extended QoS flow is an extended QoS flow through the UPF network element, the QoS flow processing method provided in this embodiment further includes the following steps S806a-S807a; or, if the suspended extended QoS flow is The QoS flow processing method provided by this embodiment further includes the following steps S806b-S807b.

Wherein, steps S806a-S807a of this embodiment are as follows:

S806a. The SMF network element sends a PFCP session modification request to the UPF network element associated with the suspended extended QoS flow, so that the UPF network element receives the PFCP session modification request from the SMF network element.

The PFCP session modification request carries at least one of a flow identifier of the suspended extended QoS flow or a session identifier of the PDU session to which the suspended extended QoS flow belongs, in order to clearly inform the UPF network element to resume the suspended extension. The flow of the QoS flow identifies the extended QoS flow, or only the extended QoS flow associated with the PFCP session corresponding to the session identifier of the PDU session is restored, and other QoS flows are not affected. That is, the PFCP session modification request is used to recover the suspended extended QoS flow.

The S807a and the UPF network element restore the suspended extended QoS flow according to the PFCP session modification request, that is, clear the suspended state of the suspended extended QoS flow.

Wherein, steps S806b-S807b of this embodiment are as follows:

S806b. The SMF network element sends a PDU session update request to the NEF network element associated with the suspended extended QoS flow, so that the NEF network element receives the PDU session update request from the SMF network element.

The PDU session update request carries at least one of a flow identifier of the suspended extended QoS flow or a session identifier of the PDU session to which the suspended extended QoS flow belongs, in order to clearly inform the NEF network element to resume the suspended extension. The flow of the QoS flow identifies the corresponding extended QoS flow, or only the extended QoS flow associated with the PDU session corresponding to the session identifier of the PDU session is recovered, and other QoS flows are not affected. That is, the PDU session update request is used to recover the suspended extended QoS flow.

The S807b and the NEF network element restore the suspended extended QoS flow according to the PDU session update request, that is, clear the suspended state of the suspended extended QoS flow.

S808. The SMF network element sends a PDU session modification command to the AMF network element, so that the AMF network element receives the PDU session modification command from the SMF network element. The PDU session modification command carries a flow identifier of the extended QoS flow.

Optionally, in this embodiment, if the SMF network element is to allocate a new extended QoS flow to be suspended, such as the second preset duration, the PDU session modification command further carries the second preset duration. The embodiment does not specifically limit this.

Optionally, in this embodiment, the SMF network element may invoke a defined service operation response to encapsulate the PDU session modification command, where the service operation response is a response to the service operation invoked by the AMF network element in step S804. Illustratively, the service operation response invoked by the SMF network element may be a “PDU Session_Update SM Context” provided by the SMF network element, which is not specifically limited in this embodiment.

S809. The AMF network element sends the NAS transmission message 2 to the terminal, so that the terminal receives the NAS transmission message 2 from the AMF network element. The NAS transport message 2 carries the PDU session modification command.

S810. The terminal recovers the suspended extended QoS flow according to the flow identifier of the extended QoS flow carried in the PDU session modification command, that is, clears the suspended state of the suspended extended QoS flow.

Optionally, in this embodiment, if the suspend timer is started when the extended QoS flow is suspended, and the suspend timer is running, the terminal may also stop the running suspend timer, this implementation This example does not specifically limit this.

Optionally, in this embodiment, if the PDU session modification command further carries the second preset duration, after receiving the NAS transmission message 2, the terminal further stores the second preset duration, in preparation for suspending the extended QoS flow. This embodiment does not specifically limit this.

The QoS flow processing method provided by the embodiment can directly restore the suspended extended QoS flow in the case that the terminal has the suspended extended QoS flow terminal accessing the 5GS, without rebuilding the extended QoS flow, thereby implementing the service. Fast recovery.

The actions of the terminal or the SMF network element or the UPF network element or the NEF network element in the foregoing steps S801 to S810 may be performed by the processor 401 in the communication device 400 shown in FIG. 4 calling the application code stored in the memory 403. This embodiment does not impose any limitation on this.

In summary, the embodiment of the present application discloses a QoS flow processing method, which includes: a terminal having an active state extended QoS flow accesses an EPS; and the terminal suspends the extended QoS flow.

As an implementation, the QoS flow processing method disclosed in the present application may further include: when the suspended extended QoS flow is still in a suspended state when the first preset duration arrives, the terminal deletes the suspended extended QoS flow.

As an implementation, the QoS flow processing method disclosed in the present application may further include: a terminal with a suspended extended QoS flow accessing a target system supporting the extended QoS flow; and a terminal having an active state extended QoS flow in the target system. The network element sends a session modification request, where the session modification request carries at least one of a flow identifier of the extended QoS flow or a session identifier of the session to which the extended QoS flow belongs, the session modification request is used to restore the extended QoS flow; and the terminal receives the session management network from the session management network. A session modification command of the element, the session modification command carrying a flow identifier of the extended QoS flow; the terminal recovers the suspended extended QoS flow according to the flow identifier of the extended QoS flow.

As an implementation, the session modification command further carries a second preset duration; the QoS flow processing method disclosed in the present application may further include: the terminal storing the second preset duration, where the second preset duration is an extended QoS flow suspension Length of time.

For the operation of the terminal, for example, the operation of the terminal may refer to the operation of the terminal in FIG. 5 to FIG. 8 and the related text description, and details are not described herein again.

In addition, the embodiment of the present application further discloses a QoS flow processing method, where the method includes: a session management network element having an active state extended QoS flow of the terminal determines that the terminal accesses the EPS; and the session management network element suspends the extended QoS flow; The session management network element sends a first notification message to the network device associated with the extended QoS flow, where the first notification message is used to notify the network device to suspend the extended QoS flow.

As an implementation, the QoS flow processing method disclosed in the present application may further include: when the suspended extended QoS flow is still in a suspended state when the first preset duration arrives, the session management network element deletes the suspended extension. The QoS flow; and the session management network element sends a second notification message to the network device, where the second notification message is used to notify the network device to delete the suspended extended QoS flow.

Optionally, the second notification message carries at least one of a flow identifier of the extended QoS flow or a session identifier of the session to which the extended QoS flow belongs.

As an implementation, the QoS flow processing method disclosed in the present application may further include: when the terminal accesses the target system supporting the extended QoS flow, the session management network element receives the session modification request from the terminal, and the session modification request carries the extended QoS. At least one of the stream identifier of the stream or the session identifier of the session to which the extended QoS flow belongs; the session management network element recovers the extended QoS flow according to the session modification request; and the session management network element sends indication information to the network device, where the indication information is used Instructs the network device to resume the suspended extended QoS flow.

As an implementation, the network device includes a user plane function network element; the session management network element sends the indication information to the network device, including: the session management network element sends a packet forwarding control protocol PFCP session modification request to the user plane function network element, and the PFCP session is modified. Request to carry instructions.

As another implementation, the network device includes a network open network element, and the session management network element sends the indication information to the network device, where the session management network element sends a session update request to the network open network element, where the session update request carries the indication information.

Optionally, the indication information includes at least one of a flow identifier of the extended QoS flow or a session identifier of the session to which the extended QoS flow belongs.

As an implementation, the QoS flow processing method disclosed in the present application may further include: the session management network element sends a session modification command to the terminal, where the session modification command carries the flow identifier of the extended QoS flow.

As an implementation, after the session management network element suspends the extended QoS flow, the QoS flow processing method disclosed in the present application may further include: the session management network element stores the terminal context related to the suspended extended QoS flow, in the terminal context. The identifier information of the terminal, the identifier information of the network device, and the first preset duration, where the first preset duration is the length of time for the extended QoS flow to hang.

As an implementation, the session management network element determines that the terminal accesses the EPS, and the method includes: the session management network element receives the context request message, where the context request message carries the information of the mobility management network element serving as the terminal in the evolved packet system EPS, and is used to request the terminal. Map the context of the EPS bearer.

For the operation of the QoS flow processing method, for example, the operation of the session management network element may refer to the operation of the SMF network element in FIG. 5 to FIG. 8 and the related text description, and details are not described herein again.

In addition, the embodiment of the present application further discloses a QoS flow processing method, where the method includes: when the terminal accesses the EPS, the network device that has the active state extended QoS flow of the terminal receives the first that suspends the extended QoS flow. a notification message; the network device suspends the extended QoS flow according to the first notification message.

As an implementation, the QoS flow processing method disclosed in the present application may further include: when the suspended extended QoS flow is still in a suspended state when the first preset duration arrives, the network device receives the extended pending QoS by deleting the suspension. a second notification message of the flow; the network device deletes the suspended extended QoS flow according to the second notification message.

As an implementation, the QoS flow processing method disclosed in the present application may further include: when the terminal accesses the target system supporting the extended QoS flow, the network device receives the indication information for recovering the suspended extended QoS flow; and the network device according to the indication Information, resumes the suspended extended QoS flow.

As an implementation, the network device includes a user plane function network element, and the network device receives the indication information of the resumed extended QoS flow, where the network device receives the packet forwarding control protocol PFCP session modification request, and the PFCP session modification request carries the indication information.

As another implementation, the network device includes a network open network element, and the network device receives the indication information of the resumed extended QoS flow, where the network device receives the session update request, and the session update request carries the indication information.

For the operation of the network device, for example, the operation of the network device may refer to the operations of the UPF network element or the NEF network element in FIG. 5 to FIG. 8 and the related text descriptions, and details are not described herein again.

The solution provided by the embodiment of the present application is mainly introduced from the perspective of interaction between the network elements. It can be understood that, in order to implement the above functions, the terminal, the session management network element or the network device includes a hardware structure and/or a software module corresponding to each function. Those skilled in the art will readily appreciate that the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.

The embodiment of the present application may divide a function module into a terminal, a session management network element, or a network device according to the foregoing method. For example, each function module may be divided according to each function, or two or more functions may be integrated into one. Processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner.

For example, in the case of dividing each functional module in an integrated manner, FIG. 9 shows a schematic structural view of a device 90. The device 90 may be the terminal in the above embodiment, or may be the chip or the circuit in the terminal in the above embodiment, which is not specifically limited in the embodiment of the present application. The device 90 includes an access module 901 and a processing module 902. The access module 901 is configured to access an EPS, and the processing module 902 is configured to suspend the extended QoS flow.

Optionally, the processing module 902 is further configured to: when the suspended extended QoS flow is still in a suspended state when the first preset duration arrives, delete the suspended extended QoS flow.

Optionally, as shown in FIG. 9, the device 90 further includes a transceiver module 903. The access module 901 is further configured to access a target system that supports extended QoS flows, and the transceiver module 903 is configured to extend to an active state in the target system. The session management network element of the QoS flow sends a session modification request, the session modification request carries at least one of the flow identifier of the extended QoS flow or the session identifier of the session to which the extended QoS flow belongs, and the session modification request is used to restore the extended QoS flow; the transceiver module 903 And the method further includes: receiving a session modification command from the session management network element, where the session modification command carries a flow identifier of the extended QoS flow; and the processing module 902 is further configured to restore the suspended extended QoS flow according to the flow identifier of the extended QoS flow.

Optionally, as shown in FIG. 9, the session modification command further carries a second preset duration; the device 90 further includes: a storage module 904; and a storage module 904, configured to store a second preset duration, where the second preset duration The length of time to extend the QoS flow.

All the related content of the steps involved in the foregoing method embodiments may be referred to the functional descriptions of the corresponding functional modules, and details are not described herein again.

In the present embodiment, the device 90 is presented in a form that divides the various functional modules in an integrated manner. A "module" herein may refer to a particular ASIC, circuitry, processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other devices that provide the functionality described above.

In a simple embodiment, those skilled in the art will appreciate that device 90 can take the form shown in FIG.

For example, the processor 401 in FIG. 4 can execute an instruction by calling a computer stored in the memory 403, so that the device 90 executes the QoS stream processing method in the above method embodiment.

Specifically, the function/implementation process of the access module 901, the processing module 902, the transceiver module 903, and the storage module 904 in FIG. 9 can be implemented by the processor 401 in FIG. 4 calling a computer execution instruction stored in the memory 403. Alternatively, the function/implementation process of the access module 901 and the processing module 902 in FIG. 9 can be implemented by the processor 401 in FIG. 4 calling the computer execution instruction stored in the memory 403, and the function of the transceiver module 903 in FIG. The implementation process can be implemented by the communication interface 404 in FIG. 4, and the function/implementation process of the storage module 904 in FIG. 9 can be implemented by the memory 403 in FIG.

Alternatively, when the device 90 is a chip or a circuit, the memory 403 may be a memory unit within the chip or circuit, such as a register, a cache, or the like. Of course, when the device 90 is a terminal, the memory 403 may be a storage unit located outside the chip in the terminal, which is not specifically limited in this embodiment of the present application.

The device provided in the embodiment of the present application can be used to perform the foregoing QoS flow processing method. Therefore, the technical effects of the foregoing embodiments can be referred to the foregoing method embodiments, and details are not described herein.

For example, in the case of dividing each functional module in an integrated manner, FIG. 10 shows a schematic structural diagram of a session management network element 100. The session management network element 100 includes a processing module 1002 and a transceiver module 1001. The processing module 1002 is configured to determine that the terminal accesses the EPS, and the processing module 1002 is further configured to suspend the extended QoS flow. The transceiver module 1001 is configured to send a first notification message, the first notification message, to the network device associated with the extended QoS flow. Used to notify the network device to suspend the extended QoS flow.

Optionally, the processing module 1002 is further configured to: when the suspended extended QoS flow is still in a suspended state when the first preset duration arrives, deleting the suspended extended QoS flow; and, the transceiver module 1001, further And a second notification message is sent to the network device, where the second notification message is used to notify the network device to delete the suspended extended QoS flow.

Optionally, the transceiver module 1001 is further configured to receive a session modification request from the terminal, where the session modification request carries at least one of a flow identifier of the extended QoS flow or a session identifier of the session to which the extended QoS flow belongs; and the processing module 1002 is configured to: The extended QoS flow is resumed according to the session modification request; and the transceiver module 1001 is further configured to send the indication information to the network device, where the indication information is used to instruct the network device to resume the suspended extended QoS flow.

In a possible implementation manner, the network device includes a user plane function network element, and the transceiver module 1001 is configured to send the indication information to the network device, where the method includes: sending a PFCP session modification request to the user plane function network element, and carrying the PFCP session modification request Instructions.

In another possible implementation manner, the network device includes a network open network element, and the transceiver module 1001 is configured to send the indication information to the network device, where the method includes: sending a session update request to the network open network element, where the session update request carries the indication information.

Optionally, the transceiver module 1001 is further configured to send a session modification command to the terminal, where the session modification command carries a flow identifier of the extended QoS flow.

Optionally, as shown in FIG. 10, the session management network element 100 further includes a storage module 1003. The storage module 1003 is configured to store a terminal context related to the suspended extended QoS flow, where the terminal context includes identity identification information of the terminal, The identifier information of the network device and the first preset duration, where the first preset duration is the length of time for the extended QoS flow to hang.

Optionally, the processing module 1002 is configured to determine that the terminal accesses the EPS, and is configured to: receive a context request message, where the context request message carries information about the mobility management network element serving the terminal in the EPS, and is used to request the mapping of the terminal by the EPS bearer. Context.

In the present embodiment, the session management network element 100 is presented in a form that divides each functional module in an integrated manner. A "module" herein may refer to a particular ASIC, circuitry, processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other devices that provide the functionality described above. In a simple embodiment, those skilled in the art will appreciate that the session management network element 100 can take the form shown in FIG.

For example, the processor 401 in FIG. 4 can execute the instruction by calling the computer stored in the memory 403, so that the session management network element 100 executes the QoS flow processing method in the above method embodiment.

Specifically, the function/implementation process of the transceiver module 1001, the processing module 1002, and the storage module 1003 in FIG. 10 can be implemented by the processor 401 in FIG. 4 calling a computer execution instruction stored in the memory 403. Alternatively, the function/implementation process of the processing module 1002 in FIG. 10 can be implemented by the processor 401 in FIG. 4 calling the computer execution instructions stored in the memory 403. The function/implementation process of the transceiver module 1001 in FIG. The communication interface 404 of 4 is implemented, and the function/implementation process of the storage module 1003 in FIG. 10 can be implemented by the memory 403 in FIG.

The session management network element provided by this embodiment can perform the foregoing QoS flow processing method. Therefore, the technical effects that can be obtained by reference to the foregoing method embodiments are not described herein.

Optionally, the embodiment of the present application further provides a chip system, where the chip system includes a processor, and is configured to support the session management network element to implement the foregoing QoS flow processing method, for example, determining that the terminal accesses the EPS and then expanding the extended QoS flow. Start. In one possible design, the chip system also includes a memory. The memory is used to store program instructions and data necessary for the session management network element. Of course, the memory may not be in the chip system. The chip system may be composed of a chip, and may also include a chip and other discrete devices. This embodiment of the present application does not specifically limit this.

For example, in the case of dividing each functional module in an integrated manner, FIG. 11 shows a schematic structural diagram of a network device 110. The network device 110 includes a transceiver module 1101 and a processing module 1102. The transceiver module 1101 is configured to: when the terminal accesses the EPS, receive a first notification message that suspends the extended QoS flow; and the processing module 1102 is configured to suspend the extended QoS flow according to the first notification message.

Optionally, the transceiver module 1101 is further configured to: receive, when the suspended extended QoS flow is still in a suspended state when the first preset duration arrives, receive a second notification message that deletes the suspended extended QoS flow; The module 1102 is further configured to delete the suspended extended QoS flow according to the second notification message.

Optionally, the transceiver module 1101 is further configured to receive indication information for recovering the suspended extended QoS flow, and the processing module 1102 is further configured to recover the suspended extended QoS flow according to the indication information.

In a possible implementation, the network device includes a user plane function network element, and the transceiver module 1101 is configured to receive the indication information of the resumed extended QoS flow, including: receiving a PFCP session modification request, and the PFCP session modification request carrying indication information.

In a possible implementation, the network device includes a network open network element, and the transceiver module 1101 is configured to receive the indication information of the resumed extended QoS flow, including: receiving a session update request, and the session update request carrying the indication information.

In the present embodiment, the network device 110 is presented in a form that divides the various functional modules in an integrated manner. A "module" herein may refer to a particular ASIC, circuitry, processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other devices that provide the functionality described above. In a simple embodiment, those skilled in the art will appreciate that the network device 110 can take the form shown in FIG.

For example, the processor 401 in FIG. 4 can execute the instruction by calling a computer stored in the memory 403, so that the network device 110 executes the QoS stream processing method in the above method embodiment.

Specifically, the function/implementation process of the transceiver module 1101 and the processing module 1102 in FIG. 11 can be implemented by the processor 401 in FIG. 4 calling a computer execution instruction stored in the memory 403. Alternatively, the function/implementation process of the processing module 1102 in FIG. 11 can be implemented by the processor 401 in FIG. 4 calling the computer execution instructions stored in the memory 403, and the function/implementation process of the transceiver module 1101 in FIG. The communication interface 404 in 4 is implemented.

The network device provided in this embodiment can perform the above-mentioned QoS flow processing method, and the technical effects that can be obtained by referring to the foregoing method embodiments are not described herein.

Optionally, the embodiment of the present application further provides a chip system, where the chip system includes a processor, configured to support the network device to implement the foregoing QoS flow processing method, for example, suspending the extended QoS flow according to the first notification message. In one possible design, the chip system also includes a memory. This memory is used to store the necessary program instructions and data for the network device. Of course, the memory may not be in the chip system. The chip system may be composed of a chip, and may also include a chip and other discrete devices. This embodiment of the present application does not specifically limit this.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using a software program, it 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 the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transmission to another website site, computer, server or data center via wired (eg coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.). The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device that includes one or more servers, data centers, etc. that can be integrated with the media. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)) or the like.

Although the present application has been described herein in connection with the various embodiments, those skilled in the art can Other variations of the disclosed embodiments are achieved. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit may fulfill several of the functions recited in the claims. Certain measures are recited in mutually different dependent claims, but this does not mean that the measures are not combined to produce a good effect.

While the present invention has been described in connection with the specific embodiments and embodiments thereof, various modifications and combinations can be made without departing from the spirit and scope of the application. Accordingly, the description and drawings are to be regarded as It will be apparent to those skilled in the art that various modifications and changes can be made in the present application without departing from the spirit and scope of the application. Thus, it is intended that the present invention cover the modifications and variations of the present invention.

Claims

A method for processing a quality of service QoS stream, the method comprising:

a terminal access evolved packet system EPS having an active state extended QoS flow;

The terminal suspends the extended QoS flow.
The method of claim 1 further comprising:

The terminal deletes the suspended extended QoS flow when the suspended extended QoS flow is still in a suspended state when the first preset duration arrives.
The method according to claim 1 or 2, wherein the method further comprises:

The terminal having the extended QoS flow that is suspended accesses a target system supporting the extended QoS flow;

Transmitting, by the terminal, a session modification request to a session management network element that has the active state extended QoS flow in the target system, where the session modification request carries a flow identifier of the extended QoS flow or a session to which the extended QoS flow belongs At least one of the session identifiers, the session modification request for restoring the extended QoS flow;

Receiving, by the terminal, a session modification command from the session management network element, where the session modification command carries a flow identifier of the extended QoS flow;

The terminal recovers the suspended extended QoS flow according to the flow identifier of the extended QoS flow.
The method according to claim 3, wherein the session modification command further carries a second preset duration; the method further comprises:

The terminal stores the second preset duration, where the second preset duration is a length of time for the extended QoS flow to hang.
A method for processing a quality of service QoS stream, the method comprising:

a session management network element having an active state extended QoS flow of the terminal determines that the terminal accesses the evolved packet system EPS;

The session management network element suspends the extended QoS flow;

The session management network element sends a first notification message to the network device associated with the extended QoS flow, where the first notification message is used to notify the network device to suspend the extended QoS flow.
The method of claim 5, wherein the method further comprises:

The session management network element deletes the suspended extended QoS flow when the suspended extended QoS flow is still in a suspended state when the first preset duration arrives; and the session management network element And sending, by the network device, a second notification message, where the second notification message is used to notify the network device to delete the suspended extended QoS flow.
The method according to claim 6, wherein the second notification message carries at least one of a flow identifier of the extended QoS flow or a session identifier of a session to which the extended QoS flow belongs.
The method of any of claims 5-7, wherein the method further comprises:

And in a case that the terminal accesses a target system that supports the extended QoS flow, the session management network element receives a session modification request from the terminal, where the session modification request carries a flow identifier of the extended QoS flow or At least one of the session identifiers of the session to which the extended QoS flow belongs;

The session management network element recovers the extended QoS flow according to the session modification request;

The session management network element sends indication information to the network device, where the indication information is used to instruct the network device to resume the suspended extended QoS flow.
The method according to claim 8, wherein the network device comprises a user plane function network element; and the session management network element sends the indication information to the network device, including:

The session management network element sends a packet forwarding control protocol PFCP session modification request to the user plane function network element, where the PFCP session modification request carries the indication information.
The method according to claim 8, wherein the network device comprises a network open network element, and the session management network element sends the indication information to the network device, including:

The session management network element sends a session update request to the network open network element, where the session update request carries the indication information.
The method according to any one of claims 8 to 10, wherein the indication information comprises at least one of a flow identifier of the extended QoS flow or a session identifier of a session to which the extended QoS flow belongs.
The method of any of claims 8-11, wherein the method further comprises:

The session management network element sends a session modification command to the terminal, where the session modification command carries a flow identifier of the extended QoS flow.
The method according to any one of claims 5 to 12, wherein after the session management network element suspends the extended QoS flow, the method further includes:

The session management network element stores a terminal context related to the suspended extended QoS flow, where the terminal context includes identity identification information of the terminal, identification information of the network device, and a first preset duration. The first preset duration is the length of time that the extended QoS flow is suspended.
The method according to any one of claims 5 to 13, wherein the session management network element determines that the terminal accesses the EPS, including:

The session management network element receives a context request message, where the context request message carries information of a mobility management network element serving the terminal in the evolved packet system EPS, and is used to request a context of the mapped EPS bearer of the terminal.
A method for processing a quality of service QoS stream, the method comprising:

In the case that the terminal accesses the evolved packet system EPS, the network device having the activated state extended QoS flow of the terminal receives the first notification message suspending the extended QoS flow;

The network device suspends the extended QoS flow according to the first notification message.
The method of claim 15 wherein the method further comprises:

And in a case that the suspended extended QoS flow is still in a suspended state when the first preset duration arrives, the network device receives a second notification message that deletes the suspended extended QoS flow;

And the network device deletes the suspended extended QoS flow according to the second notification message.
The method according to claim 15 or 16, wherein the method further comprises:

And in a case that the terminal accesses a target system that supports the extended QoS flow, the network device receives indication information that restores the suspended extended QoS flow;

The network device recovers the suspended extended QoS flow according to the indication information.
The method according to claim 17, wherein the network device comprises a user plane function network element;

And the receiving, by the network device, the indication information of the extended QoS flow that is suspended, including:

The network device receives a packet forwarding control protocol PFCP session modification request, and the PFCP session modification request carries the indication information.
The method according to claim 17, wherein the network device comprises a network open network element;

And the receiving, by the network device, the indication information of the extended QoS flow that is suspended, including:

The network device receives a session update request, and the session update request carries the indication information.
A terminal, the terminal has an active state extended quality of service QoS flow, and the terminal includes: an access module and a processing module;

The access module is configured to access an evolved packet system EPS;

The processing module is configured to suspend the extended QoS flow.
The terminal according to claim 20, characterized in that

The processing module is further configured to delete the suspended extended QoS flow when the suspended extended QoS flow is still in a suspended state when the first preset duration arrives.
The terminal according to claim 20 or 21, wherein the terminal further comprises a transceiver module;

The access module is further configured to access a target system that supports the extended QoS flow;

The transceiver module is configured to send a session modification request to a session management network element that has the active state extended QoS flow in the target system, where the session modification request carries a flow identifier of the extended QoS flow or the extended QoS At least one of session identifiers of sessions to which the flow belongs, the session modification request being used to restore the extended QoS flows;

The transceiver module is further configured to receive a session modification command from the session management network element, where the session modification command carries a flow identifier of the extended QoS flow;

The processing module is further configured to recover the suspended extended QoS flow according to the flow identifier of the extended QoS flow.
A session management network element, where the session management network element has an active state extended quality of service QoS flow of the terminal, wherein the session management network element includes: a processing module and a transceiver module;

The processing module is configured to determine that the terminal accesses an evolved packet system EPS;

The processing module is further configured to suspend the extended QoS flow;

The transceiver module is configured to send a first notification message to the network device associated with the extended QoS flow, where the first notification message is used to notify the network device to suspend the extended QoS flow.
A session management network element according to claim 23, wherein

The processing module is further configured to delete the suspended extended QoS flow when the suspended extended QoS flow is still in a suspended state when the first preset duration arrives; and

The transceiver module is further configured to send a second notification message to the network device, where the second notification message is used to notify the network device to delete the suspended extended QoS flow.
A session management network element according to claim 23 or 24, wherein

The transceiver module is further configured to receive a session modification request from the terminal, where the session modification request carries at least one of a flow identifier of the extended QoS flow or a session identifier of a session to which the extended QoS flow belongs;

The processing module is configured to recover the extended QoS flow according to the session modification request; and

The transceiver module is further configured to send indication information to the network device, where the indication information is used to instruct the network device to resume the suspended extended QoS flow.
The session management network element according to claim 25, wherein the network device includes a user plane function network element, and the transceiver module is configured to send indication information to the network device, including: for the user The face function network element sends a packet forwarding control protocol PFCP session modification request, and the PFCP session modification request carries the indication information.
The session management network element according to claim 25, wherein the network device comprises a network open network element, and the transceiver module is configured to send the indication information to the network device, including: for opening to the network The network element sends a session update request, and the session update request carries the indication information.
A session management network element according to any one of claims 25-27, characterized in that

The transceiver module is further configured to send a session modification command to the terminal, where the session modification command carries a flow identifier of the extended QoS flow.
The session management network element according to any one of claims 23 to 29, wherein the processing module is configured to determine that the terminal accesses the EPS, and is configured to: receive a context request message, where the context request message carries The information of the mobility management network element serving the terminal in the evolved packet system EPS is used to request the context of the mapped EPS bearer of the terminal.
A network device, the network device having an active state extended quality of service QoS flow of the terminal, wherein the network device comprises: a transceiver module and a processing module;

The transceiver module is configured to receive a first notification message that suspends the extended QoS flow;

The processing module is configured to suspend the extended QoS flow according to the first notification message.
A network device according to claim 30, wherein

The transceiver module is further configured to: receive, when the suspended extended QoS flow is still in a suspended state when the first preset duration arrives, receive a second notification message that deletes the suspended extended QoS flow;

The processing module is further configured to delete the suspended extended QoS flow according to the second notification message.
A network device according to claim 30 or 31, wherein

The transceiver module is further configured to: when the terminal accesses a target system that supports the extended QoS flow, receive indication information that restores the suspended extended QoS flow;

The processing module is further configured to recover the suspended extended QoS flow according to the indication information.
The network device according to claim 32, wherein the network device comprises a user plane function network element;

The receiving and receiving module is configured to receive the indication information of the extended QoS flow that is suspended, and includes: a method for receiving a packet forwarding control protocol PFCP session modification request, where the PFCP session modification request carries the indication information.
The network device according to claim 32, wherein the network device comprises a network open network element;

The receiving and receiving module is configured to receive the indication information of the extended QoS flow that is suspended, and includes: receiving a session update request, where the session update request carries the indication information.
A QoS flow processing system, the QoS flow processing system comprising: the session management network element according to any one of claims 23-29, and the method of any one of claims 30-34 Network equipment.
An apparatus, comprising: a processor and a memory; the memory for storing computer execution instructions, the processor executing the computer-executed instructions stored by the memory when the apparatus is operative, such that The apparatus performs the quality of service QoS flow processing method according to any one of claims 1-4.
A processor, wherein the processor executes a computer-executed instruction to perform the quality of service QoS flow processing method according to any one of claims 1-4.
A session management network element, comprising: a processor and a memory; the memory is configured to store a computer execution instruction, and when the session management network element is running, the processor executes the memory storage The computer executes instructions to cause the session management network element to perform the quality of service QoS flow processing method of any of claims 5-14.
A network device, comprising: a processor and a memory; the memory is configured to store a computer execution instruction, and when the network device is running, the processor executes the computer execution instruction stored by the memory, The network device is configured to perform the quality of service QoS flow processing method according to any one of claims 15-19.
A computer readable storage medium, wherein the computer readable storage medium stores instructions that, when run on a computer, cause the computer to perform any of claims 1-4, or 5-14 Any one of the quality of service QoS flow processing methods described in any of clauses 15-19.
A computer program product, wherein the computer program product stores instructions that, when run on a computer, cause the computer to perform any of claims 1-4, or any of 5-14, Or the quality of service QoS flow processing method according to any one of 15-19.
An apparatus for performing the quality of service QoS flow processing method of any of claims 1-4.
An apparatus for performing the quality of service QoS flow processing method of any of claims 5-14, or any of clauses 15-19.