A method and device for identifying a service flow

Abstract

The present application relates to the field of communication technologies, and discloses a service flow identification method and apparatus, so as to avoid the problem that after the end-to-end connection for transmitting a service flow is replaced or re-established, the terminal device needs to initiate a session modification process, so that the session management function network element and the like re-configure a control policy applicable to the new connection for the service again, which is cumbersome and has poor timeliness. The method includes: a user plane function network element receives a data packet, where the data packet includes a first service flow identifier of a first service flow to which the data packet belongs; when a first data packet filtering parameter in a first data packet detection rule corresponding to the first service flow identifier is different from a second data packet filtering parameter in the data packet, the user plane function network element updates the first data packet detection rule to a second data packet detection rule according to the second data packet filtering parameter.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technologies, and in particular, to a service flow identification method and apparatus. Background Art

[0002] At present, the media industry is developing rapidly. Users can watch live broadcasts, TV dramas, and conduct video conferences, etc. through clients installed on terminal devices such as mobile phones and tablets (such as Tencent Video client, Youku Video client, video conferencing client, etc.) or browsers. From the network layer perspective, it is expected that the proportion of media traffic in the future fifth-generation mobile communication technology (5G) network will exceed 90%, which is the main bearer traffic of the mobile communication network. The user's media experience largely determines the user's service experience of the entire mobile communication network. From the service layer perspective, the media is continuously developing towards new media forms such as ultra-high-definition video and 360-degree panoramic virtual reality (VR) video. Fashionable control requirements such as fast switching and fast bitrate adaptive switching have increasingly stringent requirements for latency and bandwidth. Simply relying on the closed-loop control of the service layer itself is difficult to meet the user's media experience requirements.

[0003] Therefore, it becomes particularly important to combine the network and the service to improve the service quality of the service through network assistance and optimize the user experience. At present, the 5G network can identify the specific service flow to which each data packet belongs through different data packet filtering parameters such as the five-tuple (the protocol (internet protocol, IP) address for interconnection between the destination / source networks, the destination / source port number, and the transport layer protocol type), so as to further provide differentiated policy control for different services.

[0004] However, due to various reasons such as load balancing of the application server and offloading of the content delivery network (CDN), the end-to-end connection between the terminal device and the application server will be replaced or rebuilt, such as the replacement or rebuilding of the transmission control protocol (TCP) connection. The replacement or rebuilding of the end-to-end connection between the terminal device and the application server will cause the end-to-end connection for transmitting the service flow to change, and the data packet filtering parameters used to identify the service flow in the configured detection and control policy need to be adjusted and updated. This requires the terminal device to frequently initiate a session modification process so that network elements such as the session management function on the core network side reconfigure the detection and control policy applicable to the new end-to-end connection for the service, such as sending a data packet detection rule applicable to the new end-to-end connection to the user plane function network element. The process is cumbersome and has poor timeliness. Summary of the Invention

[0005] An embodiment of the present application provides a service flow identification method and apparatus, which are used to solve the problem that when the end-to-end connection (such as a TCP connection, etc.) for transmitting a service flow changes, it is cumbersome and has poor timeliness to configure a control policy applicable to the new end-to-end connection.

[0006] In a first aspect, an embodiment of the present application provides a service flow identification method, which includes: a user plane function network element receives a data packet, where the data packet includes a first service flow identifier of a first service flow to which the data packet belongs; when a first data packet filtering parameter in a first data packet detection rule corresponding to the first service flow identifier is different from a second data packet filtering parameter in the data packet, the user plane function network element updates the first data packet detection rule to a second data packet detection rule according to the second data packet filtering parameter; where the first data packet detection rule is used to detect data packets including the first data packet filtering parameter and provide an execution policy for data packets including the first data packet filtering parameter, and the second data packet detection rule is used to detect data packets including the second data packet filtering parameter and provide an execution policy for data packets including the second data packet filtering parameter, and the execution policy provided by the second data packet detection rule is the same as that provided by the first data packet detection rule. Optionally, the user plane function network element updates the first data packet detection rule to the second data packet detection rule according to the second data packet filtering parameter, including: the user plane function network element sends the second data packet filtering parameter and the first service flow identifier to a session management function network element; the user plane function network element receives the second data packet detection rule from the session management function network element; the user plane function network element updates the first data packet detection rule to the second data packet detection rule.

[0007] In an embodiment of the present application, when the end-to-end connection for transmitting a service flow is replaced or rebuilt, the terminal device or the application server will carry the service flow identifier of the service flow to which the data packet belongs in the data packet sent to the user plane function network element. When the user plane function network element receives a data packet carrying the service flow identifier, it will detect whether the first data packet filtering parameter in the first data packet detection rule saved before receiving the data packet is the same as the second data packet filtering parameter in the data packet. If they are different, it will update the first data packet filtering parameter in the first data packet detection rule to the second data packet filtering parameter and construct a second data packet detection rule, so as to realize the detection of data packets of the service flow after the end-to-end connection is replaced or rebuilt and provide an execution policy, without the terminal device having to initiate a session modification process, and network elements such as the session management function on the core network side reconfigure a control policy applicable to the new end-to-end connection for the service, which can simplify the implementation process and improve timeliness.

[0008] In a possible design, the method further includes: when the data packet is a downlink data packet from an application server, the user plane function network element sends the data packet to the terminal device according to the execution policy provided by the second data packet detection rule; or, when the data packet is an uplink data packet from the terminal device, the user plane function network element sends the data packet to the application server according to the execution policy provided by the second data packet detection rule.

[0009] In the above design, it is beneficial for the data packets of the service flow to be processed in a timely manner with corresponding policies (such as being processed by the forwarding execution rule in the data packet detection rule, etc.), improving the user experience.

[0010] In a possible design, the user plane function network element adds first indication information to the data packet sent to the terminal device, and the first indication information is used to instruct the terminal device to update the first quality of service (QoS) rule of the first service flow to a second QoS rule according to the second data packet filtering parameter in the data packet.

[0011] In the above design, by adding the first indication information to the data packet sent to the terminal device, it is ensured that the terminal device can perceive that the user plane function network element has completed the update of the data packet detection rule, which is beneficial for assisting the terminal device to update the first QoS rule applicable to the end-to-end connection before replacement or reconstruction to the second QoS rule applicable to the end-to-end connection after replacement or reconstruction.

[0012] In a possible design, the user plane function network element adds second indication information to the data packet sent to the application server, and the second indication information is used to indicate that the user plane function network element has completed the update of the data packet detection rule for the first service flow.

[0013] In the above design, by sending the second indication information to the application server, the application server can learn that the user plane function network element has completed the update of the data packet detection rule, and the application server can inform the terminal device that the user plane function network element has completed the update of the data packet detection rule, so that the terminal device cancels adding the first service flow identifier to the uplink data packet.

[0014] In a possible design, before the user plane function network element receives a data packet, it further includes: the user plane function network element receives data packet detection rule configuration information from the session management function network element, and the data packet detection rule configuration information includes the first data packet detection rule and the first service flow identifier.

[0015] In the above design, the session management function network element can send the service flow identifier of the first service flow to the user plane function network element, which is beneficial for the user plane function network element to accurately identify the data packets of the service flow transmitted through the replaced or rebuilt end-to-end connection after the end-to-end connection used for transmitting the service flow is replaced or rebuilt.

[0016] In a possible design, the first service flow identifier may be carried in the network layer or transport layer or application layer of the data packet.

[0017] In a second aspect, an embodiment of the present application provides a service flow identification method, which includes: The terminal device receives a downlink data packet from the user plane function network element, and the downlink data packet includes the first service flow identifier of the first service flow to which the downlink data packet belongs; When the first packet filtering parameter in the first quality of service (QoS) rule corresponding to the first service flow identifier is different from the second packet filtering parameter in the downlink data packet, the terminal device updates the first QoS rule to a second QoS rule according to the second packet filtering parameter; Wherein the first QoS rule is used to detect data packets including the first packet filtering parameter and provide a QoS policy for data packets including the first packet filtering parameter, and the second QoS rule is used to detect data packets including the second packet filtering parameter and provide a QoS policy for data packets including the second packet filtering parameter, and the QoS policy provided by the second QoS rule is the same as the QoS policy provided by the first QoS rule.

[0018] In a possible design, the downlink data packet further includes first indication information, and the first indication information is used to instruct the terminal device to update the first QoS rule to the second QoS rule according to the second packet filtering parameter in the downlink data packet.

[0019] In a possible design, the method further includes: The terminal device sends a rule update completion indication information to the application server, and the rule update completion indication information includes the first service flow identifier, which is used to indicate that the terminal device has completed the QoS rule update for the first service flow.

[0020] In a possible design, before the terminal device receives the downlink data packet from the user plane function network element, the method further includes: The terminal device assigns the first service flow identifier to the first service flow; The terminal device sends first service flow identifier configuration information to the application function network element, and the first service flow identifier configuration information includes the flow description information of the first service flow and the first service flow identifier.

[0021] In a possible design, before the terminal device receives a downlink data packet from a user plane function network element, the method further includes: the terminal device receives QoS rule configuration information from a session management function network element, and the QoS rule configuration information includes the first QoS rule and the first service flow identifier.

[0022] In a possible design, the first service flow identifier may be carried in the network layer or the transport layer or the application layer of the downlink data packet.

[0023] In a third aspect, an embodiment of the present application provides a service flow identification method, and the method includes: the terminal device determines that an end-to-end connection corresponding to a first service flow is replaced or rebuilt; the terminal device updates the first quality of service QoS rule of the first service flow to a second QoS rule according to a second data packet filtering parameter corresponding to the end-to-end connection after replacement or rebuilding; wherein the first QoS rule includes a first data packet filtering parameter corresponding to the end-to-end connection before replacement or rebuilding of the first service flow, the first QoS rule is used to detect data packets including the first data packet filtering parameter, and provide a QoS policy for data packets including the first data packet filtering parameter, the second QoS rule is used to detect data packets including the second data packet filtering parameter, and provide a QoS policy for data packets including the second data packet filtering parameter, and the QoS policy provided by the second QoS rule is the same as the QoS policy provided by the first QoS rule.

[0024] In a possible design, the method further includes: for an uplink data packet including the second data packet filtering parameter, the terminal device sends the uplink data packet to a user plane function network element according to the QoS policy, wherein the uplink data packet includes a first service flow identifier of the first service flow.

[0025] In a possible design, the method further includes: the terminal device assigns the first service flow identifier to the first service flow; the terminal device sends first service flow identifier configuration information to an application function network element, and the first service flow identifier configuration information includes flow description information of the first service flow and the first service flow identifier.

[0026] In a possible design, the method further includes: the terminal device receives QoS rule configuration information from a session management function network element, and the QoS rule configuration information includes the first QoS rule and the first service flow identifier.

[0027] In a possible design, the first service flow identifier may be carried in the network layer or the transport layer or the application layer of the uplink data packet.

[0028] Fourthly, an embodiment of the present application provides a service flow identification method, and the method includes: an application server determines that an end-to-end connection corresponding to a first service flow is replaced or rebuilt; the application server sends a downlink data packet of the first service flow to a user plane function network element, and the first service flow identifier of the first service flow is included in the downlink data packet.

[0029] In a possible design, the method further includes: the application server receives second service flow identifier configuration information from an application function network element, and the flow description information of the first service flow and the first service flow identifier are included in the second service flow identifier configuration information.

[0030] In a possible design, the first service flow identifier may be carried in the network layer or the transport layer or the application layer of the downlink data packet.

[0031] Fifthly, an embodiment of the present application provides a service flow identification method, and the method includes: a session management function network element receives a policy and charging control rule and a first service flow identifier from a policy control function network element, and a first data packet filtering parameter is included in the policy and charging control rule; the session management function network element generates a first data packet detection rule and a first quality of service (QoS) rule for the first service flow corresponding to the first service flow identifier according to the policy and charging control rule, the first data packet detection rule is used to detect a data packet including the first data packet filtering parameter and provide an execution policy for the data packet including the first data packet filtering parameter, and the first QoS rule is used to detect a data packet including the first data packet filtering parameter and provide a QoS policy for the data packet including the first data packet filtering parameter; the session management function network element sends data packet detection rule configuration information to a user plane function network element, and the data packet detection rule configuration information includes the first data packet detection rule and the first service flow identifier; and sends the QoS rule configuration information to a terminal device, and the QoS rule configuration information includes the first QoS rule and the first service flow identifier.

[0032] In a possible design, the method further includes: the session management function network element receives a second data packet filtering parameter and the first service flow identifier from the user plane function network element; the session management function network element generates a second data packet detection rule for the first service flow according to the second data packet filtering parameter and the policy and charging control rule, the second data packet detection rule is used to detect a data packet including the second data packet filtering parameter and provide an execution policy for the data packet including the second data packet filtering parameter; the session management function network element sends the second data packet detection rule to the user plane function network element.

[0033] Sixth aspect, an embodiment of the present application provides a service flow identification method, which includes: an application function network element receives first service flow identification configuration information from a terminal device, and the first service flow identification configuration information includes flow description information of a first service flow and a first service flow identification; the application function network element sends second service flow identification configuration information to an application server, and sends third service flow identification configuration information to a policy control function network element, and both the second service flow identification configuration information and the third service flow identification configuration information include the flow description information of the first service flow and the first service flow identification.

[0034] Seventh aspect, an embodiment of the present application provides a service flow identification method, which includes: an application function network element assigns a first service flow identification to a first service flow; the application function network element sends second service flow identification configuration information to an application server, and sends third service flow identification configuration information to a policy control function network element, and both the second service flow identification configuration information and the third service flow identification configuration information include the flow description information of the first service flow and the first service flow identification.

[0035] Eighth aspect, an embodiment of the present application provides a service flow identification method, which includes: a user plane function network element receives a packet detection rule from a session management function network element, and the packet detection rule is used to detect a packet including a first service flow identification and provide an execution policy for the packet, where the first service flow identified by the first service flow identification corresponds to one or more end-to-end connections between a terminal device and an application server; when the user plane function network element receives a packet including the first service flow identification from the terminal device, the user plane function network element sends the packet to the application server according to the execution policy; or when the user plane function network element receives a packet including the first service flow identification from the application server, the user plane function network element sends the packet to the terminal device according to the execution policy.

[0036] In a possible design, the first service flow identification may be carried in the network layer or the transport layer or the application layer of the downlink packet.

[0037] In a ninth aspect, an embodiment of the present application provides a service flow identification method, which includes: a terminal device receives a Quality of Service (QoS) rule from a session management function network element, where the QoS rule is used to detect data packets including a first service flow identifier and provide a QoS policy for the data packets, and the first service flow identified by the first service flow identifier corresponds to one or more end-to-end connections between the terminal device and an application server; for a data packet including the first service flow identifier, the terminal device detects the data packet according to the QoS rule and sends the data packet to a user plane function network element based on the QoS policy, where the user plane function network element is located on one or more end-to-end connections between the terminal device and the application server.

[0038] In a possible design, the first service flow identifier may be carried in the network layer or the transport layer or the application layer of the downlink data packet.

[0039] In a tenth aspect, an embodiment of the present application provides a service flow identification method, which includes: a session management function network element generates a data packet detection rule and a Quality of Service (QoS) rule according to a policy and charging control rule of a first service flow and a first service flow identifier, where the first service flow corresponds to one or more end-to-end connections between a terminal device and an application server, the data packet detection rule is used to detect data packets including the first service flow identifier and provide an execution policy for the data packets, and the QoS rule is used to detect data packets including the first service flow identifier and provide a QoS policy for the data packets; the session management network element sends the QoS rule to the terminal device and sends the data packet detection rule to a user plane function network element, where the user plane function network element is located on one or more end-to-end connections between the terminal device and the application server.

[0040] In a possible design, the first service flow identifier may be carried in the network layer or the transport layer or the application layer of the downlink data packet.

[0041] In an eleventh aspect, an embodiment of the present application provides a service flow identification device, which has the function of implementing the method in the first aspect or any possible design of the first aspect, or implementing the method in the eighth aspect or any possible design of the eighth aspect. The function may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units (modules) corresponding to the above functions, such as a communication unit and a processing unit.

[0042] In a possible design, the device may be a chip or an integrated circuit.

[0043] In a possible design, the device includes a processor and an interface circuit. The processor is coupled to the interface circuit and is configured to implement the method in the above first aspect or any possible design of the first aspect, or implement the functions of the method in the above eighth aspect or any possible design of the eighth aspect. It can be understood that the interface circuit can be a transceiver or an input / output interface. The device may further include a memory that stores a program executable by the processor for implementing the method in the above first aspect or any possible design of the first aspect, or implementing the functions of the method in the above eighth aspect or any possible design of the eighth aspect.

[0044] In a possible design, the device may be a user plane function network element.

[0045] In a twelfth aspect, an embodiment of the present application provides a service flow identification device, which has the functions of implementing the method in the above second aspect or any possible design of the second aspect, or implementing the method in the above third aspect or any possible design of the third aspect, or implementing the method in the above ninth aspect or any possible design of the ninth aspect. The functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units (modules) corresponding to the above functions, such as a communication unit and a processing unit.

[0046] In a possible design, the device may be a chip or an integrated circuit.

[0047] In a possible design, the device includes a processor and an interface circuit. The processor is coupled to the interface circuit and is configured to implement the functions of the method in the above second aspect or any possible design of the second aspect, or implement the method in the above third aspect or any possible design of the third aspect, or implement the functions of the method in the above ninth aspect or any possible design of the ninth aspect. It can be understood that the interface circuit can be a transceiver or an input / output interface. The device may further include a memory that stores a program executable by the processor for implementing the method in the above second aspect or any possible design of the second aspect, or implementing the method in the above third aspect or any possible design of the third aspect, or implementing the functions of the method in the above ninth aspect or any possible design of the ninth aspect.

[0048] In a possible design, the device may be a terminal device.

[0049] In a thirteenth aspect, an embodiment of the present application provides a service flow identification device, which has the function of implementing the method in the above fourth aspect or any possible design of the fourth aspect. This function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units (modules) corresponding to the above functions, such as a communication unit and a processing unit.

[0050] In a possible design, the device may be a chip or an integrated circuit.

[0051] In a possible design, the device includes a processor and an interface circuit. The processor is coupled to the interface circuit and is used to implement the function of the method in the above fourth aspect or any possible design of the fourth aspect. It can be understood that the interface circuit may be a transceiver or an input / output interface. The device may further include a memory, and the memory stores a program executable by the processor for implementing the function of the method in the above fourth aspect or any possible design of the fourth aspect.

[0052] In a possible design, the device may be an application server.

[0053] In a fourteenth aspect, an embodiment of the present application provides a service flow identification device, which has the function of implementing the method in the above fifth aspect or any possible design of the fifth aspect, or implementing the method in the above tenth aspect or any possible design of the tenth aspect. This function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units (modules) corresponding to the above functions, such as a communication unit and a processing unit.

[0054] In a possible design, the device may be a chip or an integrated circuit.

[0055] In a possible design, the device includes a processor and an interface circuit. The processor is coupled to the interface circuit and is used to implement the function of the method in the above fifth aspect or any possible design of the fifth aspect, or implementing the method in the above tenth aspect or any possible design of the tenth aspect. It can be understood that the interface circuit may be a transceiver or an input / output interface. The device may further include a memory, and the memory stores a program executable by the processor for implementing the function of the method in the above fifth aspect or any possible design of the fifth aspect, or implementing the method in the above tenth aspect or any possible design of the tenth aspect.

[0056] In a possible design, the device may be a session management function network element.

[0057] In a fifteenth aspect, an embodiment of the present application provides a service flow identification device, which has the function of implementing the method in the above sixth aspect or any possible design of the sixth aspect, or implementing the method in the above seventh aspect or any possible design of the seventh aspect. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units (modules) corresponding to the above functions, such as a communication unit and a processing unit.

[0058] In a possible design, the device may be a chip or an integrated circuit.

[0059] In a possible design, the device includes a processor and an interface circuit. The processor is coupled to the interface circuit and is used to implement the function of the method in the above sixth aspect or any possible design of the sixth aspect, or to implement the function of the method in the above seventh aspect or any possible design of the seventh aspect. It can be understood that the interface circuit may be a transceiver or an input / output interface. The device may further include a memory, and the memory stores a program that can be executed by the processor to implement the method in the above sixth aspect or any possible design of the sixth aspect, or to implement the function of the method in the above seventh aspect or any possible design of the seventh aspect.

[0060] In a possible design, the device may be an application function network element.

[0061] In a sixteenth aspect, an embodiment of the present application further provides a service flow identification system, which includes the user plane function network element in the above first aspect, the terminal device in the above second and third aspects, the application server in the above fourth aspect, the session management function network element in the above fifth aspect, and the application function network element in the above sixth and seventh aspects.

[0062] In a seventeenth aspect, an embodiment of the present application further provides a service flow identification system, which includes the user plane function network element in the above eighth aspect, the terminal device in the above ninth aspect, and the session management function network element in the above tenth aspect.

[0063] In an eighteenth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program or instruction for executing the method described in the above first aspect or any possible design of the first aspect, or for executing the method described in the above second aspect or any possible design of the second aspect, or for executing the method described in the above third aspect or any possible design of the third aspect, or for executing the method described in the above fourth aspect or any possible design of the fourth aspect, or for executing the method described in the above fifth aspect or any possible design of the fifth aspect, or for executing the method described in the above sixth aspect or any possible design of the sixth aspect, or for executing the method described in the above seventh aspect or any possible design of the seventh aspect, or for executing the method described in the above eighth aspect or any possible design of the eighth aspect, or for executing the method described in the above ninth aspect or any possible design of the ninth aspect, or for executing the method described in the above tenth aspect or any possible design of the tenth aspect.

[0064] In a nineteenth aspect, an embodiment of the present application further provides a chip system, the chip system includes: a processor and an interface, the processor is used to call and run a computer program from the interface, and when the processor executes the computer program, it can implement the method described in the above first aspect or any possible design of the first aspect, or implement the method described in the above second aspect or any possible design of the second aspect, or implement the method described in the above third aspect or any possible design of the third aspect, or implement the method described in the above fourth aspect or any possible design of the fourth aspect, or implement the method described in the above fifth aspect or any possible design of the fifth aspect, or implement the method described in the above sixth aspect or any possible design of the sixth aspect, or implement the method described in the above seventh aspect or any possible design of the seventh aspect, or implement the method described in the above eighth aspect or any possible design of the eighth aspect, or implement the method described in the above ninth aspect or any possible design of the ninth aspect, or implement the method described in the above tenth aspect or any possible design of the tenth aspect.

[0065] In a twentieth aspect, a computer program product of an embodiment of the present application, when the computer program product runs on a computer, causes the computer to execute the methods described in the above aspects.

[0066] For the technical effects that can be achieved by the above second aspect to the twentieth aspect, please refer to the technical effects that can be achieved by the above first aspect, and will not be repeated here. Description of the Drawings

[0067] Figure 1Schematic diagram of the data packet detection rules provided by the embodiments of the present application;

[0068] Figure 2 Schematic diagram of the network architecture provided by the embodiments of the present application;

[0069] Figure 3 One of the schematic diagrams of the service flow identification method provided by the embodiments of the present application;

[0070] Figure 4 One of the schematic diagrams of the service flow identifier configuration process provided by the embodiments of the present application;

[0071] Figure 5 The second schematic diagram of the service flow identifier configuration process provided by the embodiments of the present application;

[0072] Figure 6 Schematic diagram of the initial rule configuration process provided by the embodiments of the present application;

[0073] Figure 7 Schematic diagram of the data packet detection rule update process provided by the embodiments of the present application;

[0074] Figure 8 The second schematic diagram of the service flow identification method provided by the embodiments of the present application;

[0075] Figure 9 The third schematic diagram of the service flow identification method provided by the embodiments of the present application;

[0076] Figure 10 Schematic diagram of the service flow identification implementation architecture provided by the embodiments of the present application;

[0077] Figure 11 One of the schematic diagrams of the service flow identification device provided by the embodiments of the present application;

[0078] Figure 12 The second schematic diagram of the service flow identification device provided by the embodiments of the present application. Detailed implementation manners

[0079] It should be understood that in the embodiments of the present application, "at least one" means one or more, and "a plurality" means two or more. "And / or" and "or / and" describe the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone, where A and B may be singular or plural. The character " / " generally indicates that the associated objects before and after are in an "or" relationship. "At least one (item) of the following" or its similar expressions refer to any combination of these items, including any combination of a single item or plural items. For example, at least one (item) of a, b, or c may represent: a, b, c, a and b, a and c, b and c, or a, b, and c, where each of a, b, and c itself may be an element or a set containing one or more elements.

[0080] In the embodiments of the present application, terms such as "exemplary", "in some embodiments", and "in another embodiment" are used to give examples, illustrations, or explanations. Any embodiment or design solution described as "exemplary" in the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of the term "exemplary" is intended to present concepts in a specific manner.

[0081] In the embodiments of the present application, "of", "corresponding", and "corresponding" can sometimes be used interchangeably. It should be noted that when the difference is not emphasized, the meanings they express are the same. In the embodiments of the present application, communication and transmission can sometimes be used interchangeably. It should be noted that when the difference is not emphasized, the meanings they express are the same. For example, transmission may include sending and / or receiving, and can be a noun or a verb.

[0082] It should be noted that the terms "first", "second", etc. involved in the embodiments of the present application are only used for the purpose of distinguishing descriptions, and should not be construed as indicating or implying relative importance, nor as indicating or implying an order.

[0083] The "network element" involved in the embodiments of the present application may also be referred to as a "device", and there is no limitation in this regard. A network element may be hardware, software functionally divided, or a structure combined by the above two. A network element may include core network elements, access network devices (or referred to as access network network elements), etc. Core network elements, such as a session management function network element, a user plane function network element, etc.

[0084] The packet filtering parameters applied by existing packet filters are mainly represented by a five-tuple, including source / destination IP addresses, source / destination port numbers, and transport layer protocol types. Based on the five-tuple carried on the data packet, the service type corresponding to each transmitted data packet can be identified. For example, based on the transport layer protocol, IP address, and port number on the application server side in the five-tuple, the services of iQIYI, Youku Video, and Tencent Video can be distinguished.

[0085] In a mobile network, in order to distinguish different service flows, such as the service flows of iQIYI, Youku, etc., or further distinguish the video service flows, audio service flows, subtitle service flows, etc. in the service flows of iQIYI, Youku, etc., a service data filter (SDF) is introduced to filter and screen the data packets of the corresponding service flow. Among them, on the terminal device side, it is often a quality of service (QoS) rule. The QoS rule includes one or more SDFs, aiming to map the data of the service flow to the corresponding QoS flow according to the SDF; similarly, on the user plane function network element side, it is often a packet detection rule (PDR), such as Figure 1 As shown, the PDR can include packet detection information (PDI), the packet filtering parameters included are usually the same as those of the SDF (such as the five-tuple, etc.), and the actions (or policies) to be performed on the data packets of the detected and identified service flow, such as one or more of the forwarding action rule (FAR), using reporting rule (URR), QoS enforcement rule (QER), etc.

[0086] After an end-to-end connection (such as a TCP connection) has been established for the service flow between the terminal device and the application server, the terminal device will initiate a session modification process, send the latest service flow description information (such as packet filtering parameters) to the session management function network element, and trigger the session modification process. Or the policy control function network element triggers the session modification process, and sends the policy and charging control (PCC) rules (including the service data filter of the service flow) to the session management function network element. The service data filter includes the packet filtering parameters used to filter and screen the data packets of the service flow. The session management function network element generates PDR and QoS rules based on the policy and charging control rules, and distributes them to the user plane function network element and the terminal device to implement the policy control of the service flow.

[0087] However, due to reasons such as load balancing of the application server and offloading of the content delivery network (CDN), the end-to-end connection established between the terminal device and the application server for transmitting the service flow is frequently replaced or rebuilt, resulting in frequent changes in the packet filtering parameters of the corresponding service flow. As a result, the original PDR and QoS rules can no longer filter and screen the packets of the service flow because of the changes in the packet filtering parameters. This requires frequent initiation of the session modification process to enable the session management function network element to reconfigure the PDR and QoS rules for the user plane function network element and the terminal device. The process is complex and has poor timeliness. Moreover, after the end-to-end connection for transmitting the service flow is replaced or rebuilt, if there are immediately packets to be transmitted, the user plane function network element may also have the problem that it cannot provide policy control for the packets because it has not obtained the PDR applicable to the replaced or rebuilt end-to-end connection, resulting in further deterioration of the user service experience.

[0088] In view of the above problems, the embodiments of the present application provide a service flow identification method. By assigning a service flow identifier to the service flow, when the end-to-end connection (such as a TCP connection, which is used as an example in the subsequent embodiments of the present application with the end-to-end connection being a TCP connection) for transmitting the service flow is replaced or rebuilt, the service flow identifier is included (i.e., carried) in the packets sent through the replaced or rebuilt end-to-end connection, so that the terminal device and / or the user plane function network element can perform packet detection and policy control according to the packet filtering parameters included in the packets, or update the packet filtering parameters used to detect the packets of the service flow in the QoS rules and / or packet detection rules (PDR) of the service flow to the packet filtering parameters corresponding to the replaced or rebuilt end-to-end connection, avoiding frequent initiation of the session modification process.

[0089] The following explains some terms in the embodiments of the present application to facilitate the understanding of those skilled in the art.

[0090] 1) Service flow. In the embodiments of the present application, the service flow refers to the data stream of the service, such as the data stream of the iQIYI service transmitted between the iQIYI client and the iQIYI application server. In some possible implementations, the service flow of the service can also be further divided according to specific data types. For example, the service flow corresponding to the live client can be divided into a video service flow, an audio service flow, and a subtitle service flow, and offloaded through different ports or the content delivery network. Among them, the video stream may include one or more video frames or video chunk files; the audio stream may include one or more audio frames or audio chunk files; the subtitle stream may include one or more segments of text.

[0091] 2) The terminal device is a device with wireless transceiver functions. It can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, satellites, etc.). For example, the terminal device can be a mobile phone, a tablet, a smart screen, a computer with wireless transceiver functions, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc.

[0092] It should be noted that when implementing the service flow identification method provided in this application, on the network side, it involves a session management function (SMF) network element, a policy control function (PCF) network element, an application function (AF) network element, a user plane function (UPF) network element, and an access network (AN) device. Among them, the session management function network element, the policy control function network element, the application function network element, and the user plane function network element are core network elements. The access network device can be used to provide wireless communication functions for terminal devices; the session management function network element can be used to control the establishment, modification, and deletion of packet data unit (PDU) sessions; the user plane function network element can be used to be responsible for connecting to an external network (such as a data network (DN)); the application function network element can be used to interact with the 3rd generation partnership project (3GPP) core network to provide services, which can affect service flow routing, access network capability opening, policy control, etc.; the policy control function network element can be used to be responsible for policy control, such as generating a quality of service (QoS) parameter set, etc. Implementing the service flow identification method provided in this application also involves a terminal device and an application server. It should be understood that in the embodiments of this application, the terminal device can also be referred to as a terminal, a user equipment (UE), a mobile terminal, a media client, a media session handler (MSH) client, etc., which is not limited herein, and the application server can also be referred to as a media stream server, etc., which is not limited herein. Hereinafter, taking the terminal device (such as a UE) and the application server as examples, the embodiments of this application will be introduced.

[0093] Exemplarily, such as Figure 2As shown, it is a schematic diagram of a network architecture applicable to the embodiments of the present application. This network architecture is a 5G network architecture. The network architecture includes a radio access network (RAN), an access and mobility management function (AMF) network element, an SMF network element, a UPF network element, a PCF network element, a DN, etc. In some embodiments, the network architecture further includes a unified data management (UDM) network element, an authentication server function (AUSF) network element, an application function (AF) network element, a network exposure function (NEF) network element, a network data analytics function (NWDAF) network element, etc.

[0094] The RAN device (also known as an access network (AN) device) mainly controls the terminal device to wirelessly access the mobile communication network and is located between the terminal device and the core network. Currently, some examples of RAN devices are: (g nodeB, gNB) in 5G, evolved node B (eNB), radio network controller (RNC), node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved nodeB, or home node B, HNB), base band unit (BBU), transmitting and receiving point (TRP), transmitting point (TP), mobile switching center, etc. In addition, the RAN device may also include a wireless fidelity (wifi) access point (AP), etc.

[0095] The AMF network element is responsible for the access management and mobility management of the terminal device, including managing user registration, reachability detection, selection of the SMF network element, management of mobile state transitions, etc.

[0096] The SMF network element is mainly responsible for controlling the establishment, modification, and deletion of PDU sessions, the selection of UPF network elements, etc.

[0097] The UPF network element is mainly responsible for packet routing and forwarding, mobility anchor points, uplink classifiers to support routing service flows to data networks, branch points to support multi-homed PDU sessions, etc.

[0098] The PCF network element is a policy decision point and is mainly responsible for providing rules based on service data flows and application detection, gating, QoS, and flow-based charging control, etc.

[0099] The UDM network element is mainly responsible for storing user subscription data.

[0100] The AUSF network element is mainly used to provide authentication services.

[0101] The AF network element is mainly used to interact with the 3rd generation partnership project (3GPP) core network to provide services, and to influence service flow routing, access network capability opening, policy control, etc.

[0102] The NEF network element is mainly used to securely open the services and capabilities provided by 3GPP network functions, such as third parties, edge computing, AF, etc.

[0103] The DN provides network services for terminal devices, such as operator services, Internet access, or third-party services, etc.

[0104] The NWDAF network element is mainly used to provide network data collection and analysis functions based on technologies such as big data and artificial intelligence, etc.

[0105] In addition, for more concise description, in the subsequent description, the "network element" in each functional network element can be removed. For example, the AMF network element is abbreviated as AMF, the UPF network element is abbreviated as UPF, and the other network elements are similar, and will not be listed one by one.

[0106] Figure 2Among NWDAF, NEF, NRF, PCF, UDM, AF, AUSF, AMF, and SMF, service - based communication can be adopted for communication between any two network elements. For example, the interfaces Nnef and Nausf used for communication between NEF and AUSF are both service - based interfaces. Similarly, the interfaces Nnwdaf, Nnrf, Npcf, Nudm, Naf, Namf, and Nsmf are all service - based interfaces. In addition, AMF and UE can communicate through the N1 interface, AMF and RAN network elements can communicate through the N2 interface, RAN network elements and UPF can communicate through the N3 interface, SMF and UPF can communicate through the N4 interface, UE and RAN network elements perform air - interface communication, UPF and DN can communicate through the N6 interface, and UPFs communicate through the N9 interface. It should be noted that Figure 2 the service - based interfaces between the various network elements in

[0107] Among them, Figure 2 in the network architecture shown, the network elements related to this application are mainly: SMF network element, UPF network element, AF network element, and terminal device (UE).

[0108] It should be noted that Figure 2 This is only an example of a network architecture applicable to the embodiments of this application and does not constitute a limitation on the embodiments of this application. The embodiments of this application can also be applied to other network architectures, such as future mobile communication network architectures (such as 6G network architectures), etc.

[0109] Due to reasons such as load balancing of the application server and CDN offloading, the end - to - end connection (such as TCP connection, etc.) established between the client of the terminal device and the application server for transmitting service flows will frequently change or be rebuilt. In this application, after the end - to - end connection for transmitting service flows changes or is rebuilt, the terminal device and the user plane function network element can automatically update the QoS rules and packet detection rules (PDR) for the service flow according to the uplink (from the terminal device to the application server) service flow or the downlink (from the application server to the terminal device) service flow. The following combines specific scenarios and takes the first service flow as an example to introduce the service flow identification method of this application.

[0110] Scenario 1: After the end - to - end connection (such as TCP connection, etc.) for transmitting service flows changes or is rebuilt, the terminal device and the user plane function network element automatically update the QoS rules and packet detection rules for the service flow according to the downlink service flow.

[0111] Figure 3 This is a schematic diagram of the service flow identification method provided by the embodiments of this application. The method includes:

[0112] S301: The application server sends the downlink data packet of the first service flow to the user plane function network element, and the user plane function network element receives the downlink data packet, where the downlink data packet includes the first service flow identifier of the first service flow.

[0113] Due to reasons such as load balancing of the application server (AS) and CDN offloading, the end-to-end connection (such as a TCP connection) established between the client of the terminal device and the application server for transmitting the first service flow may be replaced or rebuilt. If there is a downlink data packet sent first after the replacement or reconstruction of the end-to-end connection, the application server will add the first service flow identifier of the first service flow to the packet header of the downlink data packet. As an example, the first service flow identifier can be added to the extended bit (or field) of the IP / TCP layer in the downlink data packet, or even to the extended bit of the application layer or an additional intermediate layer in the downlink data packet, as long as the user plane function network element can recognize it.

[0114] In some implementations, to save the overhead of processing resources and transmission resources, the application server can add the first service flow identifier only to the first X data packets after the end-to-end connection is replaced or rebuilt, where X is an integer greater than or equal to 1, and can be configured according to the application function network element, policy control function network element, etc., or configured by the application server itself.

[0115] Regarding the configuration of the first service flow identifier of the first service flow. In a possible implementation, the first service flow identifier of the first service flow can be assigned by the terminal device. As an example: as Figure 4 shown, when the client on the terminal device is started, it will trigger the terminal device to request the 5G network to establish a session (such as request to establish a new PDU session) or use an existing session. If a session needs to be established, the session management function network element will select a user plane function network element for the session. After the session is established, the terminal device can establish an end-to-end connection (such as a TCP connection) for transmitting the first service flow with the application server through the user plane function network element.

[0116] After establishing an end-to-end connection for transmitting a first service flow, the terminal device may allocate a first service flow identifier for the first service flow. The first service flow identifier allocated by the terminal device for the first service flow may be unique within each terminal device, or may be unique within each session of each terminal device (where each session of the terminal device is allocated an IP address by the session management function network element, that is, it may be unique within each IP address of each terminal device), as long as it can be ensured that the first service flow can be uniquely determined based on the first service flow identifier, or based on the first service flow identifier and the IP address of the terminal device, such as the flow description information (such as the five-tuple in the packet filtering parameters) that uniquely determines the first service flow.

[0117] After the terminal device allocates a first service flow identifier for the first service flow, it may send the first service flow identifier of the first service flow to the application function network element through first service flow identifier configuration information including the first service flow identifier and the flow description information of the first service flow. The application function network element may also send the first service flow identifier of the first service flow to the application server through second service flow identifier configuration information including the first service flow identifier and the flow description information of the first service flow.

[0118] In another possible implementation, the first service flow identifier of the first service flow may be allocated by the application function network element. As an example, after the terminal device and the application server establish an end-to-end connection for transmitting the first service flow, the application function network element allocates a first service flow identifier for the first service flow. The implementation of the application function network element allocating the first service flow identifier for the first service flow may refer to the implementation of the terminal device allocating the first service flow identifier for the first service flow, and the repeated parts will not be elaborated. After the application function network element allocates the first service flow identifier for the first service flow, the application function network element may directly send the allocated first service flow identifier to the terminal device. For example, the application function network element may send the first service flow identifier and the flow description information of the first service flow to the user plane function network element through the user plane of the IP connection, and the user plane function network element forwards it to the access network device, and then the access network device forwards it to the terminal device. The application function network element may also send the first service flow identifier and the flow description information of the first service flow to the policy control function network element, and the policy control function network element triggers a session modification process to send to the terminal device. In addition, the application function network element may also send the first service flow identifier of the first service flow to the application server through second service flow identifier configuration information including the first service flow identifier and the flow description information of the first service flow.

[0119] In yet another possible implementation, the first service flow identifier of the first service flow may also be allocated by the policy control function network element. As an example: such as Figure 5As shown, after the terminal device establishes an end-to-end connection with the application server for transmitting the first service flow, the application function network element can send an application function request (such as an AF request) to the policy control function network element. The application function request includes the flow description information of the first service flow (which can be obtained from the application server) and the allocation indication information used to instruct the policy control function network element to allocate a first service flow identifier for the first service flow. After receiving the application function request, the policy control function network element allocates a first service flow identifier for the flow description information of the first service flow, and can reply the flow description information and the first service flow identifier of the first service flow to the application function network element through an application function response (such as an AF response). The implementation of the policy control function network element allocating a first service flow identifier for the first service flow can refer to the implementation of the terminal device allocating a first service flow identifier for the first service flow, and the repeated parts will not be elaborated. After receiving the first service flow identifier, the application function network element can directly send the allocated first service flow identifier to the terminal device, or can leave it unprocessed and trigger a session modification process by the policy control function network element to send it to the terminal device. In addition, the application function network element can send the first service flow identifier of the first service flow to the application server through the second service flow identifier configuration information including the first service flow identifier and the flow description information of the first service flow.

[0120] It should be understood that if the terminal device or the application function network element allocates a first service flow identifier for the first service flow, the application function network element also needs to send the first service flow identifier of the first service flow to the policy control function network element. For example: sending it to the policy control function network element through an application function request (such as an AF request) including the flow description information and the first service flow identifier of the first service flow. Or when the terminal device allocates a first service flow identifier for the first service flow, the terminal device directly sends the first service flow identifier of the first service flow to the session management network element and the policy control function network element during the session modification process (such as the PDU session modification process). For example: sending the flow description information and the first service flow identifier of the first service to the session management network element and the policy control function network element through a PDU session modification request message.

[0121] Taking the terminal device allocating a first service flow identifier for the first service flow as an example, such as Figure 6As shown in the figure, after the policy control function network element obtains the first service flow identifier of the first service flow, the policy control function network element will initiate a session management policy association establishment / modification process with the session management network element. For example, the policy control function network element can send a session management (SM) policy association modification request (such as an SM policy association modification request) to the session management network element, and send the policy and charging control rules including the service data filter of the first service flow (the service filter includes packet filtering parameters for filtering and screening the data packets of the first service flow) and the first service flow identifier to the session management function network element. The session management function network element generates a packet detection rule and a QoS rule according to the policy and charging control rules. It should be understood that in some possible implementations, the first service flow identifier can also be included in the policy and charging control rules.

[0122] The session management function can, through the session creation or modification process, send the packet detection rule configuration information including the packet detection rule and the first service flow identifier to the user plane function network element. For example, the packet detection rule configuration information is sent to the user plane function network element through an N4 session creation / or modification request (N4 session establishment / modification request). The QoS rule and the first service flow identifier can also be sent to the terminal device through a session modification command, etc. For example: The session management function network element can first send a communication message carrying a session modification command (such as a PDU session modification command) (such as a Namf_communication_N1N2 message transfer message) to the access and mobility management function (AMF) network element, and the access and mobility management function network element then sends the session modification command to the terminal device. It should be understood that in some possible implementations, the first service flow identifier can also be included in the QoS rule or the packet detection rule.

[0123] After the user plane function network element receives the packet detection rule configuration information, it will bind the packet detection rule of the first service flow with the corresponding first service flow identifier; the terminal device will also bind the QoS rule with the corresponding first service flow identifier. The packet detection parameters for detecting the data packets of the first service flow in the packet detection rule and the QoS rule can be dynamically adjusted, such as being dynamically adjusted according to the packet detection parameters in the data packets including the first service flow identifier.

[0124] S302: When the first packet filtering parameter in the first packet detection rule corresponding to the first service flow identifier is different from the second packet filtering parameter in the downlink packet, the user plane function network element updates the first packet detection rule to a second packet detection rule according to the second packet filtering parameter.

[0125] Among them, the first packet filtering rule is a packet detection rule used by the user plane function network element to detect packets in the first service flow before receiving the downlink packet. Specifically, the first packet detection rule is used to detect packets in the first service flow that include the first packet filtering parameter and provide an execution policy for the packets that include the first packet filtering parameter. The second packet detection rule is used to detect packets that include the second packet filtering parameter and provide an execution policy for the packets that include the second packet filtering parameter. The execution policy provided by the second packet detection rule is the same as that provided by the first packet detection rule.

[0126] Specifically, when the user plane function network element receives a downlink packet including the first service flow identifier from the application server, it will detect whether the first packet filtering parameter in the first packet detection rule corresponding to the first service flow identifier is the same as the second packet filtering parameter in the downlink packet. If they are different, it is determined that the end-to-end connection corresponding to the first service flow has been replaced or rebuilt. The user plane function network element updates the first packet filtering parameter in the first packet detection rule to the second packet filtering parameter in the downlink packet to implement the detection and identification of packets (uplink or downlink) that include the second packet filtering parameter, and provide the same execution policy as that in the first packet detection rule for the packets (uplink or downlink) that include the second packet filtering parameter, such as providing one or more of a forwarding action rule (FAR), a using reporting rule (URR), and a QoS enforcement rule (QER). Specifically, the identity information of the corresponding execution policy, such as the ID information of FAR / URR / QER, can be carried in the packet detection rule.

[0127] In a possible implementation, such as Figure 7As shown, when it is determined that the second packet filtering parameter in the downlink data packet is different from the first packet filtering parameter in the first packet detection rule corresponding to the first service flow identifier, the user plane function network element can also send the second packet filtering parameter and the first service flow identifier to the session management function network element through an N4 session modification request (such as an N4 session modification request). The session management function network element generates a second packet detection rule according to the policy and charging control rule corresponding to the first service flow identifier and the second packet filtering parameter, or the session management function network element updates the original first packet detection rule, where the first packet filtering parameter in the first packet detection rule is replaced with the second packet filtering parameter to generate a second packet detection rule. Through an N4 session modification response (such as an N4 session modification response) including the second packet detection rule, the session management function network element can send the second packet detection rule to the user plane function network element, so that after the user plane function network element receives the second packet detection rule, it binds the second packet detection rule with the first service flow identifier to ensure that the data of the first service flow can be properly processed according to the corresponding policy.

[0128] S303: The user plane function network element sends the data packet to the terminal device according to the execution policy provided by the second packet detection rule, and the terminal device receives the downlink data packet.

[0129] The user plane function network element uses the second packet detection rule to detect and identify the downlink data. After identifying that the second packet filtering parameter in the downlink data packet is consistent with the packet detection parameter recorded in the second packet detection rule, it uses the execution policy provided by the second packet detection rule, such as a forwarding execution rule, etc., to send the downlink data packet to the terminal device.

[0130] S304: When the first packet filtering parameter in the first QoS rule corresponding to the first service flow identifier is different from the second packet filtering parameter in the downlink data packet, the terminal device updates the first QoS rule to a second QoS rule according to the second packet filtering parameter.

[0131] Among them, the first QoS rule is a QoS rule in the terminal device for detecting packets in the first service flow before receiving the downlink packet. When the terminal device receives a downlink packet from the user plane function network element, it will detect whether the first packet filtering parameter in the first QoS rule is the same as the second packet filtering parameter in the downlink packet. If they are different, it is determined that the end-to-end connection corresponding to the first service flow has been replaced or rebuilt. The terminal device updates the first packet filtering parameter in the first QoS rule to the second packet filtering parameter in the downlink packet, and determines the second QoS rule to implement the detection and identification of packets including the second packet filtering parameter, and to provide a QoS policy for packets including the second packet filtering parameter, such as a policy for mapping uplink packets including the second packet filtering parameter to the corresponding QoS flow.

[0132] Specifically, the first QoS rule is used to detect packets including the first packet filtering parameter and provide a QoS policy for packets including the first packet filtering parameter. The second QoS rule is used to detect packets including the second packet filtering parameter and provide a QoS policy for packets including the second packet filtering parameter. The QoS policy provided by the second QoS rule is the same as the QoS policy provided by the first QoS rule.

[0133] In some embodiments, after the terminal device updates the first QoS rule to the second QoS rule and can already clearly know that the user plane function network element has also completed the update of the packet detection rule for the first service flow, the terminal device can also send a rule update completion indication message to the application server (such as sending it through the application layer M8d interface between the terminal device and the application server). The rule update completion indication message includes the first service flow identifier, which is used to indicate that the terminal device has completed the update of the QoS rule for the first service flow, and to inform the application server that it can no longer add the first service flow identifier to the downlink packet.

[0134] It can be understood that in some possible embodiments, the terminal device may also not identify the first service flow identifier included in the packet. If the user plane function network element updates the first packet detection rule of the first service flow to the second packet detection rule according to the second packet filtering parameter in the downlink packet, when the user plane function network element sends the downlink packet to the terminal device, it can also add a first indication in the downlink packet for instructing the terminal device to update the first QoS rule of the first service flow to the second QoS rule according to the second packet filtering parameter in the packet, to indicate that the terminal device updates the first QoS rule of the first service flow.

[0135] As an example, the user plane function network element may add first indication information at the General Packet Radio Service (GPRS) tunneling protocol user plane (GTP-U) layer of the downlink data packet. If the first indication information is added to the extension bit of the GTP-U layer, when the access network device forwards the downlink data packet to the terminal device, it may send the first indication information to the terminal device through a Radio Resource Control (RRC) message or add the first indication information to the Packet Data Convergence Protocol (PDCP) / Service Data Adaptation Protocol (SDAP) layer in the downlink data packet.

[0136] In addition, if the terminal device does not recognize the first traffic flow identifier included in the data packet, after the session management function network element generates a second data packet detection rule for the first traffic flow according to the second data packet filtering parameter reported by the user plane function network element, the session management function network element may also generate a second QoS rule for the first traffic flow according to the second data packet filtering parameter, and send it to the terminal device through a Session Management message (SM message), so that the terminal device updates the first QoS rule of the first traffic flow to the second QoS rule.

[0137] In addition, it should be understood that when the terminal device determines that the end-to-end connection corresponding to the first traffic flow has been replaced or rebuilt, it may also actively update the first QoS rule of the first traffic flow to the second QoS rule according to the second data packet filtering parameter corresponding to the end-to-end connection after replacement or reconstruction.

[0138] Scenario 2: After the end-to-end connection (such as a TCP connection, etc.) used to transmit the traffic flow is replaced or rebuilt, the terminal device and the user plane function network element automatically update the QoS rule and the data packet detection rule of the traffic flow according to the uplink traffic flow.

[0139] Figure 8 The following is a schematic diagram of the traffic flow identification method provided by the embodiments of this application. The method includes:

[0140] S801: The terminal device determines that the end-to-end connection corresponding to the first traffic flow has been replaced or rebuilt.

[0141] S802: The terminal device updates the first QoS rule of the first traffic flow to the second QoS rule according to the second data packet filtering parameter corresponding to the end-to-end connection after replacement or reconstruction.

[0142] Among them, the first QoS rule includes first packet filtering parameters corresponding to the end-to-end connection before the replacement or reconstruction of the first service flow. The first QoS rule is used to detect packets including the first packet filtering parameters and provide a QoS policy for the packets including the first packet filtering parameters. The second QoS rule is used to detect packets including the second packet filtering parameters and provide a QoS policy for the packets including the second packet filtering parameters. The QoS policy provided by the second QoS rule is the same as the QoS policy provided by the first QoS rule.

[0143] Due to reasons such as load balancing of the application server (AS) and CDN offloading, the end-to-end connection (such as a TCP connection, etc.) established between the client of the terminal device and the application server for transmitting the first service flow may be replaced or reconstructed. If there are uplink packets sent first after the replacement or reconstruction of the end-to-end connection, the terminal device will detect that the flow description information of the first service flow (such as the five-tuple in the packet filtering parameters) has changed. The terminal device will update the first packet filtering parameters in the first QoS rule to the second packet filtering parameters corresponding to the replaced or reconstructed end-to-end connection, and is used to provide a QoS policy for the packets including the second packet filtering parameters, such as providing a policy to map the uplink packets including the second packet filtering parameters to the corresponding QoS flow.

[0144] In some possible implementations, the terminal device may also initiate a session modification process (such as a PDU session modification process), and the session management function network element generates a second QoS rule based on the policy and charging control rules and sends it to the terminal device.

[0145] S803: For the uplink packets including the second packet filtering parameters, the terminal device sends the uplink packets to the user plane function network element according to the QoS policy provided by the first QoS rule, where the uplink packets include the first service flow identifier of the first service flow.

[0146] The terminal device uses the second QoS rule to detect and identify the uplink packets of the first service flow, and after identifying that the second packet filtering parameters in the uplink packets are consistent with the packet detection parameters recorded in the second QoS rule, maps the downlink packets to the QoS flow specified by the QoS policy and sends them to the user plane function network element.

[0147] Among them, for the implementation of allocating the first service flow identifier to the first service flow and how the terminal device, user plane function network element, application server, etc. obtain the first service flow identifier allocated to the first service flow, reference can be made to the above Scenario 1, and details will not be elaborated here.

[0148] As an example, the terminal device may add a first service flow identifier in the IP / TCP layer of the uplink data packet and send the first service flow identifier to the user plane function network element; or add a first service flow identifier in the PDCP / SDAP layer of the uplink data packet, and when the access network device forwards the uplink data packet to the user plane, add the first service flow identifier in the GTP-U layer of the uplink data packet and send it to the user plane function network element.

[0149] S804: When the first packet filtering parameter in the first packet detection rule corresponding to the first service flow identifier is different from the second packet filtering parameter in the uplink data packet, the user plane function network element updates the first packet detection rule to a second packet detection rule according to the second packet filtering parameter.

[0150] Among them, the first packet filtering rule is a packet detection rule in the user plane function network element for detecting packets in the first service flow before receiving the uplink data packet. Specifically, the first packet detection rule is used to detect packets including the first packet filtering parameter in the first service flow and provide an execution policy for packets including the first packet filtering parameter. The second packet detection rule is used to detect packets including the second packet filtering parameter and provide an execution policy for packets including the second packet filtering parameter. The execution policy provided by the second packet detection rule is the same as that provided by the first packet detection rule.

[0151] After the user plane function network element receives an uplink data packet including a first service flow identifier from the terminal device, it will detect whether the first packet filtering parameter in the first packet detection rule corresponding to the first service flow identifier is the same as the second packet filtering parameter in the uplink data packet. If they are different, it is determined that the end-to-end connection corresponding to the first service flow has been replaced or rebuilt. The user plane function network element updates the first packet filtering parameter in the first packet detection rule to the second packet filtering parameter in the uplink data packet to implement the detection and identification of packets (uplink or downlink) including the second packet filtering parameter, and provide the same execution policy as that in the first packet detection rule for packets (uplink or downlink) including the second packet filtering parameter, such as providing one or more of FAR, URR, QoS, etc.

[0152] In a possible implementation, such as Figure 7As shown, when it is determined that the second packet filtering parameter in the uplink data packet is different from the first packet filtering parameter in the first packet detection rule corresponding to the first service flow identifier, the user plane function network element may also send the second packet filtering parameter and the first service flow identifier to the session management function network element through an N4 session modification request (such as an N4 session modification request). The session management function network element generates a second packet detection rule based on the policy and charging control rule corresponding to the first service flow identifier and the second packet filtering parameter, or the session management function network element updates the original first packet detection rule, where the first packet filtering parameter in the first packet detection rule is replaced with the second packet filtering parameter to generate a second packet detection rule. Through an N4 session modification response (such as an N4 session modification response) including the second packet detection rule, the session management function network element can send the second packet detection rule to the user plane function network element. After the user plane function network element receives the second packet detection rule, it binds the second packet detection rule to the first service flow identifier to ensure that the data of the first service flow can be properly processed according to the corresponding policy.

[0153] S805: The user plane function network element sends the uplink data packet to the application server according to the execution policy provided by the second packet detection rule.

[0154] The user plane function network element uses the second packet detection rule to detect and identify the uplink data. After identifying that the second packet filtering parameter in the uplink data packet is consistent with the packet detection parameter recorded in the second packet detection rule, it uses the execution policy provided by the second packet detection rule, such as a forwarding execution rule, etc., to send the uplink data packet to the application server.

[0155] In some implementations, after the user plane function network element updates the first packet detection rule to the second packet detection rule, it may also add second indication information for indicating that the user plane function network element has completed the update of the packet detection rule for the first service flow to the uplink data packet sent to the application server, such as adding the second indication information in the IP / TCP layer or application layer of the uplink data packet. According to the second indication information from the user plane function network element, the application server can clearly know that the user plane function network element has completed the update of the packet detection rule for the first service flow, and can inform the terminal device through the application layer M8d interface between the application server and the terminal device that the user plane function network element has completed the update of the packet detection rule for the first service flow, and inform the terminal device that it does not need to add the first service flow identifier to the uplink data packet anymore.

[0156] It should be understood that the service flow can be divided based on the five-tuple, or can be more finely divided based on the five-tuple + other information used to identify the flow. The embodiments of the present application are not limited thereto.

[0157] In some implementations, the terminal device and the user plane function network element can also directly detect and identify the data packets of the first service flow according to the first service flow identifier of the first service flow, and provide QoS policies and enforcement policies for the data packets. For example Figure 9 As shown, after the policy control function network element obtains the first service flow identifier of the first service flow, the policy control function network element will initiate a session management policy association establishment / modification process with the session management network element. For example: the policy control function network element can send a session management (SM) policy association modification request (such as an SM policy association modification request) to the session management network element, and send the policy and charging control rules including the first service flow identifier of the first service flow to the session management function network element. The session management function network element generates a data packet detection rule and a QoS rule according to the policy and charging control rules. The data packet detection rule is used to detect the data packets including the first service flow identifier of the first service flow, and provide an enforcement policy for the data packets. The QoS rule is used to detect the data packets including the first service flow identifier, and provide a QoS policy for the data packets. That is, different from the existing data packet detection rules and QoS rules that detect and identify the data packets of the first service flow based on data packet filtering parameters, in this implementation, the data packets of the first service flow are detected and identified based on the service flow identifier of the first service.

[0158] The session management function can send the data packet detection rule to the user plane function network element through a session creation or modification process. For example, send the data packet detection rule to the user plane function network element through an N4 session creation / or modification request (N4 session establishment / modification request). The QoS rule can also be sent to the terminal device through a session modification command, etc. For example: the session management function network element can first send a communication message (such as a Namf_communication_N1N2 message transfer message) carrying a session modification command (such as a PDU session modification command) to the access and mobility management function (AMF) network element, and the access and mobility management function network element then sends the session modification command to the terminal device.

[0159] Packets of the first service flow (uplink or downlink) transmitted between the terminal device and the application server carry the identifier of the first service flow. Since the packet detection rule detects the packets of the first service flow based on the first service flow identifier and provides an execution policy, and the QoS rule detects the packets of the first service flow based on the first service flow identifier and provides a QoS policy, even if due to reasons such as load balancing of the application server and CDN offloading, the end-to-end connection established between the client of the terminal device and the application server for transmitting the first service flow is replaced or rebuilt, when the first service flow corresponds to one or more end-to-end connections between the terminal device and the application server at different times, there is no need to update and initiate an update to the packet detection rule and QoS.

[0160] It should be understood that the first service flow identifier can be carried in the network layer, transport layer, application layer, etc. of the packet. Assigning the first service flow identifier to the first service flow and how to enable the policy control function network element to know the assigned first service flow identifier can refer to the implementation in the above Scenario 1 and will not be elaborated here.

[0161] As Figure 10 shown, the above mainly introduces the terminal device and the solution provided by the present application from the perspective of the interaction between the session management function network element, user plane function network element, application server, application function network element, etc. It can be understood that in order to implement the above functions, each network element (or device) includes the corresponding hardware structure and / or software module (or unit) for executing each function. Those skilled in the art should easily realize that, combining the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the way of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0162] Figure 11 and Figure 12 is a schematic structural diagram of a possible service flow identification device provided by an embodiment of the present application. These service flow identification devices can be used to implement the functions of the terminal device, session management function network element, user plane function network element, application server, and application function network element in the above method embodiments, and thus can also achieve the beneficial effects possessed by the above method embodiments. In the embodiments of the present application, the service flow identification device can be the terminal device, session management function network element, user plane function network element, application server, or application function network element in the above method embodiments, or can also be a module (such as a chip) applied to the terminal device, session management function network element, user plane function network element, application server, or application function network element.

[0163] As shown in Figure 11 Figure. The traffic flow identification device 1100 may include: a processing unit 1102 and a communication unit 1103, and may further include a storage unit 1101. The traffic flow identification device 1100 is used to implement the functions of the terminal device, session management function network element, user plane function network element, application server, or application function network element in the above method embodiments.

[0164] In a possible design, the processing unit 1102 is used to implement corresponding processing functions. The communication unit 1103 is used to support the communication between the traffic flow identification device 1100 and other network entities. The storage unit 1101 is used to store the program code and / or data of the traffic flow identification device 1100. Optionally, the communication unit 1103 may include a receiving unit and / or a sending unit, which are respectively used to perform receiving and sending operations.

[0165] When the traffic flow identification device 1100 is used to implement the function of the user plane function network element in the method embodiment:

[0166] The communication unit 1103 is used to receive a data packet, where the data packet includes a first traffic flow identifier of a first traffic flow to which the data packet belongs;

[0167] The processing unit 1102 is used to update the first data packet detection rule to a second data packet detection rule according to the second data packet filtering parameter when the first data packet filtering parameter in the first data packet detection rule corresponding to the first traffic flow identifier is different from the second data packet filtering parameter in the data packet; where the first data packet detection rule is used to detect data packets including the first data packet filtering parameter and provide an execution policy for data packets including the first data packet filtering parameter, and the second data packet detection rule is used to detect data packets including the second data packet filtering parameter and provide an execution policy for data packets including the second data packet filtering parameter, and the execution policy provided by the second data packet detection rule is the same as that provided by the first data packet detection rule.

[0168] In a possible design, the communication unit 1103 is further used to send the data packet to the terminal device according to the execution policy provided by the second data packet detection rule when the data packet is a downlink data packet from the application server; or,

[0169] When the data packet is an uplink data packet from the terminal device, send the data packet to the application server according to the execution policy provided by the second data packet detection rule.

[0170] In a possible design, the processing unit 1102 is further configured to add first indication information to the data packet sent to the terminal device, where the first indication information is used to instruct the terminal device to update the first Quality of Service (QoS) rule of the first service flow to a second QoS rule according to a second data packet filtering parameter in the data packet.

[0171] In a possible design, the processing unit 1102 is further configured to add second indication information to the data packet sent to the application server, where the second indication information is used to instruct the service flow identification device to complete the update of the data packet detection rule for the first service flow.

[0172] In a possible design, when the processing unit 1102 updates the first data packet detection rule to a second data packet detection rule according to the second data packet filtering parameter, it is specifically configured to send the second data packet filtering parameter and the first service flow identifier to a session management function network element through the communication unit 1103; receive the second data packet detection rule from the session management function network element, where the second data packet detection rule is determined by the session management function network element according to the second data packet filtering parameter and the first service flow identifier; and update the first data packet detection rule to the second data packet detection rule.

[0173] In a possible design, the communication unit 1103 is further configured to receive data packet detection rule configuration information from a session management function network element before receiving a data packet, where the data packet detection rule configuration information includes the first data packet detection rule of the first service flow and the first service flow identifier.

[0174] In a possible design, the first service flow identifier is carried in the network layer or the transport layer or the application layer of the data packet.

[0175] In some embodiments, the communication unit 1103 is configured to receive a data packet detection rule from a session management function network element, where the data packet detection rule is used to detect data packets including a first service flow identifier and provide an execution policy for the data packets, where the first service flow identified by the first service flow identifier corresponds to one or more end-to-end connections between a terminal device and an application server;

[0176] The communication unit 1103 is further configured to, when receiving a data packet including the first service flow identifier from the terminal device, send the data packet to the application server according to the execution policy; or when receiving a data packet including the first service flow identifier from the application server, send the data packet to the terminal device according to the execution policy.

[0177] When the service flow identification device 1100 is used to implement the functions of the terminal device in the method embodiments:

[0178] In a possible implementation, the communication unit 1103 is configured to receive a downlink data packet from a user plane function network element, where the downlink data packet includes a first service flow identifier of a first service flow to which the downlink data packet belongs;

[0179] The processing unit 1102 is configured to, when a first data packet filtering parameter in a first quality of service (QoS) rule corresponding to the first service flow identifier is different from a second data packet filtering parameter in the downlink data packet, update the first QoS rule to a second QoS rule according to the second data packet filtering parameter; where the first QoS rule is used to detect data packets including the first data packet filtering parameter and provide a QoS policy for data packets including the first data packet filtering parameter, and the second QoS rule is used to detect data packets including the second data packet filtering parameter and provide a QoS policy for data packets including the second data packet filtering parameter, and the QoS policy provided by the second QoS rule is the same as the QoS policy provided by the first QoS rule.

[0180] In a possible design, the downlink data packet further includes first indication information, where the first indication information is used to instruct the service flow identification device to update the first QoS rule to the second QoS rule according to the second data packet filtering parameter in the downlink data packet.

[0181] In a possible design, the communication unit 1103 is further configured to send a rule update completion indication information to an application server, where the rule update completion indication information includes the first service flow identifier and is used to indicate that the terminal device has completed the QoS rule update for the first service flow.

[0182] In a possible design, before the communication unit 1103 receives a downlink data packet from a user plane function network element, the processing unit 1102 is further configured to allocate the first service flow identifier to the first service flow;

[0183] The communication unit 1103 is further configured to send first service flow identifier configuration information to an application function network element, where the first service flow identifier configuration information includes flow description information of the first service flow and the first service flow identifier.

[0184] In a possible design, before the communication unit 1103 receives a downlink data packet from a user plane function network element, it is further configured to receive QoS rule configuration information from a session management function network element, where the QoS rule configuration information includes the first QoS rule and the first service flow identifier.

[0185] In a possible design, the first service flow identifier is carried in the network layer or the transport layer or the application layer of the downlink data packet.

[0186] In another possible implementation, the processing unit 1102 is configured to determine that an end-to-end connection corresponding to the first service flow is replaced or re-established;

[0187] The processing unit 1102 is further configured to update the first Quality of Service (QoS) rule of the first service flow to a second QoS rule according to a second data packet filtering parameter corresponding to the end-to-end connection after replacement or re-establishment, where the first QoS rule includes a first data packet filtering parameter corresponding to the end-to-end connection before replacement or re-establishment of the first service flow, the first QoS rule is used to detect data packets including the first data packet filtering parameter and provide a QoS policy for data packets including the first data packet filtering parameter, the second QoS rule is used to detect data packets including the second data packet filtering parameter and provide a QoS policy for data packets including the second data packet filtering parameter, and the QoS policy provided by the second QoS rule is the same as the QoS policy provided by the first QoS rule.

[0188] In a possible design, the communication unit 1103 is configured to send the uplink data packet including the second data packet filtering parameter to a user plane function network element according to the QoS policy, where the uplink data packet includes the first service flow identifier of the first service flow.

[0189] In a possible design, the processing unit 1102 is further configured to allocate the first service flow identifier to the first service flow;

[0190] The communication unit 1103 is further configured to send first service flow identifier configuration information to an application function network element, where the first service flow identifier configuration information includes flow description information of the first service flow and the first service flow identifier.

[0191] In a possible design, the communication unit 1103 is further configured to receive QoS rule configuration information from a session management function network element, where the QoS rule configuration information includes the first QoS rule and the first service flow identifier.

[0192] In a possible design, the first service flow identifier is carried in the network layer or the transport layer or the application layer of the uplink data packet.

[0193] In some embodiments, the communication unit 1103 is configured to receive a Quality of Service (QoS) rule from a session management function network element. The QoS rule is used to detect data packets including a first traffic flow identifier and provide a QoS policy for the data packets, where the first traffic flow corresponding to the first traffic flow identifier corresponds to one or more end-to-end connections between a terminal device and an application server.

[0194] The communication unit 1103 is further configured to, for data packets including the first traffic flow identifier, detect the data packets according to the QoS rule and send the data packets to a user plane function network element based on the QoS policy, where the user plane function network element is located on one or more end-to-end connections between the terminal device and the application server.

[0195] When the traffic flow identification device 1100 is used to implement the function of the application server in the method embodiment:

[0196] The processing unit 1102 is configured to determine that the end-to-end connection corresponding to the first traffic flow is replaced or rebuilt.

[0197] The communication unit 1103 is configured to send a downlink data packet of the first traffic flow to a user plane function network element, where the downlink data packet includes the first traffic flow identifier of the first traffic flow.

[0198] In a possible design, the communication unit 1103 is further configured to receive second traffic flow identifier configuration information from an application function network element, where the second traffic flow identifier configuration information includes flow description information of the first traffic flow and the first traffic flow identifier.

[0199] In a possible design, the first traffic flow identifier is carried in the network layer or the transport layer or the application layer of the downlink data packet.

[0200] When the traffic flow identification device 1100 is used to implement the function of the session management function network element in the method embodiment:

[0201] The communication unit 1103 is configured to receive a policy and charging control rule and a first traffic flow identifier from a policy control function network element, where the policy and charging control rule includes a first data packet filtering parameter.

[0202] A processing unit 1102 is configured to generate a first packet detection rule and a first Quality of Service (QoS) rule for a first service flow corresponding to the first service flow identifier according to the policy and charging control rule. The first packet detection rule is used to detect packets including the first packet filtering parameter and provide an execution policy for the packets including the first packet filtering parameter. The first QoS rule is used to detect packets including the first packet filtering parameter and provide a QoS policy for the packets including the first packet filtering parameter.

[0203] The communication unit 1103 is further configured to send packet detection rule configuration information to a user plane function network element, where the packet detection rule configuration information includes the first packet detection rule and the first service flow identifier; and send the QoS rule configuration information to a terminal device, where the QoS rule configuration information includes the first QoS rule and the first service flow identifier.

[0204] In a possible design, the communication unit 1103 is further configured to receive a second packet filtering parameter and the first service flow identifier from the user plane function network element.

[0205] The processing unit 1102 is further configured to generate a second packet detection rule for the first service flow according to the second packet filtering parameter and the policy and charging control rule. The second packet detection rule is used to detect packets including the second packet filtering parameter and provide an execution policy for the packets including the second packet filtering parameter.

[0206] The communication unit 1103 is further configured to send the second packet detection rule to the user plane function network element.

[0207] In some embodiments, the processing unit 1102 is configured to generate a packet detection rule and a Quality of Service (QoS) rule according to the policy and charging control rule of a first service flow and the first service flow identifier, where the first service flow corresponds to one or more end-to-end connections between a terminal device and an application server. The packet detection rule is used to detect packets including the first service flow identifier and provide an execution policy for the packets. The QoS rule is used to detect packets including the first service flow identifier and provide a QoS policy for the packets.

[0208] The communication unit 1103 is configured to send the QoS rule to the terminal device and send the packet detection rule to a user plane function network element, where the user plane function network element is located on one or more end-to-end connections between the terminal device and the application server.

[0209] When the service flow identification device 1100 is used to implement the functions of the application function network element in the method embodiments:

[0210] In a possible implementation, the communication unit 1103 is configured to receive first service flow identification configuration information from a terminal device, where the first service flow identification configuration information includes flow description information of a first service flow and a first service flow identifier; and send second service flow identification configuration information to an application server, and send third service flow identification configuration information to a policy control function network element, where both the second service flow identification configuration information and the third service flow identification configuration information include the flow description information of the first service flow and the first service flow identifier.

[0211] In another possible implementation, the processing unit 1102 is configured to allocate a first service flow identifier for the first service flow;

[0212] The communication unit 1103 is configured to send second service flow identification configuration information to an application server, and send third service flow identification configuration information to a policy control function network element, where both the second service flow identification configuration information and the third service flow identification configuration information include the flow description information of the first service flow and the first service flow identifier.

[0213] For a more detailed description of the above processing unit 1102 and communication unit 1103, reference can be directly made to the relevant descriptions in the method embodiments and will not be elaborated here.

[0214] As Figure 12 shown, the service flow identification device 1200 includes a processor 1210 and an interface circuit 1220. The processor 1210 and the interface circuit 1220 are coupled to each other. It can be understood that the interface circuit 1220 can be a transceiver or an input / output interface. Optionally, the service flow identification device 1200 may further include a memory 1230, configured to store instructions executed by the processor 1210 or input data required for the processor 1210 to run the instructions or data generated after the processor 1210 runs the instructions.

[0215] When the service flow identification device 1200 is used to implement the service flow identification method applicable to a terminal device, a session management function network element, a user plane function network element, an application server, or an application function network element in the above method embodiments, the processor 1210 is configured to implement the functions of the above processing unit 1102, and the interface circuit 1220 is configured to implement the functions of the above communication unit 1103.

[0216] As another form of this embodiment, a computer-readable storage medium is provided, on which instructions are stored, and when the instructions are executed, the service flow identification method applicable to a terminal device, a session management function network element, a user plane function network element, an application server, or an application function network element in the above method embodiment can be executed.

[0217] As another form of this embodiment, a computer program product containing instructions is provided, and when the instructions are executed, the service flow identification method applicable to a terminal device, a session management function network element, a user plane function network element, an application server, or an application function network element in the above method embodiment can be executed.

[0218] As another form of this embodiment, a chip is provided, and when the chip runs, the service flow identification method applicable to a terminal device, a session management function network element, a user plane function network element, an application server, or an application function network element in the above method embodiment can be executed.

[0219] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

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

[0221] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory generate a manufactured product including an instruction device, and the instruction device implements in the process Figure 1 one process or multiple processes and / or blocks Figure 1 a device for the functions specified in one block or multiple blocks.

[0222] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus, so that a series of operation steps are executed on the computer or other programmable apparatus to produce a computer-implemented process, thereby providing instructions for implementing the steps of the process Figure 1 in one process or multiple processes and / or blocks Figure 1 or steps for implementing the functions specified in one block or multiple blocks.

[0223] Although the preferred embodiments of the present application have been described, additional changes and modifications can be made to these embodiments by those skilled in the art once they learn the basic creative concept. Therefore, the appended claims are intended to be construed to include the preferred embodiments as well as all changes and modifications falling within the scope of the present application.

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

Claims

1. A service flow identification method, characterized in that, Including: The user plane function network element receives a data packet, where the data packet includes a first service flow identifier of a first service flow to which the data packet belongs; When a first data packet filtering parameter in a first data packet detection rule corresponding to the first service flow identifier is different from a second data packet filtering parameter in the data packet, the user plane function network element updates the first data packet detection rule to a second data packet detection rule according to the second data packet filtering parameter; The first data packet detection rule is used to detect data packets including the first data packet filtering parameter and provide an execution policy for data packets including the first data packet filtering parameter, and the second data packet detection rule is used to detect data packets including the second data packet filtering parameter and provide an execution policy for data packets including the second data packet filtering parameter, and the execution policy provided by the second data packet detection rule is the same as that provided by the first data packet detection rule.

2. The method according to claim 1, characterized in that, The method further includes: When the data packet is a downlink data packet from an application server, the user plane function network element sends the data packet to the terminal device according to the execution policy provided by the second data packet detection rule; or When the data packet is an uplink data packet from the terminal device, the user plane function network element sends the data packet to the application server according to the execution policy provided by the second data packet detection rule.

3. The method according to claim 2, characterized in that, The user plane function network element adds first indication information to the data packet sent to the terminal device, and the first indication information is used to instruct the terminal device to update a first quality of service (QoS) rule of the first service flow to a second QoS rule according to the second data packet filtering parameter in the data packet.

4. The method according to claim 2, characterized in that, The user plane function network element adds second indication information to the data packet sent to the application server, and the second indication information is used to instruct the user plane function network element to complete the update of the data packet detection rule of the first service flow.

5. The method according to any one of claims 1 - 4, characterized in that, The user plane function network element updates the first data packet detection rule to the second data packet detection rule according to the second data packet filtering parameter, including: The user plane function network element sends the second data packet filtering parameter and the first service flow identifier to the session management function network element; The user plane function network element receives the second data packet detection rule from the session management function network element, and the second data packet detection rule is determined by the session management function network element according to the second data packet filtering parameter and the first service flow identifier; The user plane function network element updates the first data packet detection rule to the second data packet detection rule.

6. The method according to any one of claims 1 - 4, characterized in that, Before the user plane function network element receives the data packet, it further includes: The user plane function network element receives data packet detection rule configuration information from the session management function network element, and the data packet detection rule configuration information includes the first data packet detection rule and the first service flow identifier.

7. The method according to any one of claims 1 - 4, characterized in that, The first service flow identifier is carried in the network layer or the transport layer or the application layer of the data packet.

8. A service flow identification method, characterized in that, Including: The terminal device receives a downlink data packet from a user plane function network element, and the downlink data packet includes a first service flow identifier of a first service flow to which the downlink data packet belongs; When the first data packet filtering parameter in the first Quality of Service (QoS) rule corresponding to the first service flow identifier is different from the second data packet filtering parameter in the downlink data packet, the terminal device updates the first QoS rule to a second QoS rule according to the second data packet filtering parameter; Wherein the first QoS rule is used to detect data packets including the first data packet filtering parameter and provide a QoS policy for data packets including the first data packet filtering parameter, and the second QoS rule is used to detect data packets including the second data packet filtering parameter and provide a QoS policy for data packets including the second data packet filtering parameter, and the QoS policy provided by the second QoS rule is the same as the QoS policy provided by the first QoS rule.

9. The method according to claim 8, characterized in that, The downlink data packet further includes first indication information, which is used to indicate that the terminal device updates the first QoS rule to the second QoS rule according to the second data packet filtering parameter in the downlink data packet.

10. The method according to claim 8 or 9, characterized in that, The method further includes: The terminal device sends rule update completion indication information to the application server, and the rule update completion indication information includes the first service flow identifier, which is used to indicate that the terminal device has completed the QoS rule update for the first service flow.

11. The method according to claim 8 or 9, characterized in that, Before the terminal device receives the downlink data packet from the user plane function network element, the method further includes: The terminal device assigns the first service flow identifier to the first service flow; The terminal device sends first service flow identifier configuration information to the application function network element, and the first service flow identifier configuration information includes flow description information of the first service flow and the first service flow identifier.

12. The method according to claim 8 or 9, characterized in that, Before the terminal device receives the downlink data packet from the user plane function network element, the method further includes: The terminal device receives QoS rule configuration information from the session management function network element, and the QoS rule configuration information includes the first QoS rule and the first service flow identifier.

13. The method according to claim 8 or 9, characterized in that The first service flow identifier is carried in the network layer or the transport layer or the application layer of the downlink data packet.

14. A method for identifying a service flow, characterized in that Including: The terminal device determines that the end-to-end connection corresponding to the first service flow has been replaced or rebuilt; The terminal device updates the first Quality of Service (QoS) rule of the first service flow to a second QoS rule according to the second data packet filtering parameter corresponding to the end-to-end connection after replacement or reconstruction; The first QoS rule includes first packet filtering parameters corresponding to the end-to-end connection before the replacement or reconstruction of the first service flow. The first QoS rule is used to detect packets including the first packet filtering parameters and provide a QoS policy for the packets including the first packet filtering parameters. The second QoS rule is used to detect packets including the second packet filtering parameters and provide a QoS policy for the packets including the second packet filtering parameters. The QoS policy provided by the second QoS rule is the same as the QoS policy provided by the first QoS rule.

15. The method according to claim 14, characterized in that The method further includes: For an uplink packet including the second packet filtering parameters, the terminal device sends the uplink packet to the user plane function network element according to the QoS policy, where the uplink packet includes a first service flow identifier of the first service flow.

16. The method according to claim 14 or 15, characterized in that The method further includes: The terminal device assigns the first service flow identifier to the first service flow; The terminal device sends first service flow identifier configuration information to the application function network element, and the first service flow identifier configuration information includes flow description information of the first service flow and the first service flow identifier.

17. The method according to claim 14 or 15, characterized in that The method further includes: The terminal device receives QoS rule configuration information from the session management function network element, and the QoS rule configuration information includes the first QoS rule and the first service flow identifier.

18. The method according to claim 15, characterized in that The first service flow identifier is carried in the network layer or the transport layer or the application layer of the uplink packet.

19. A media service flow identification device, characterized in that including: A processor and a memory, where program instructions are stored in the memory, and the processor runs the program instructions stored in the memory to execute the method according to any one of claims 1-7, or the method according to any one of claims 8-13, or the method according to any one of claims 14-18.

20. A computer-readable storage medium, characterized in that A computer program is stored in the computer-readable storage medium. When the computer program is executed by a computer, the computer is caused to execute the method according to any one of claims 1-7, or the method according to any one of claims 8-13, or the method according to any one of claims 14-18.

21. A chip system, characterized in that The chip system includes: A processor and an interface. The processor is used to call and run instructions from the interface. When the processor executes the instructions, the method according to any one of claims 1-7, or the method according to any one of claims 8-13, or the method according to any one of claims 14-18 is implemented.

22. A service flow identification system, characterized in that The system includes a user plane function network element and a terminal device; wherein, the user plane function network element is used to execute the method according to any one of claims 1-7; The terminal device is used to execute the method according to any one of claims 8-18.

Images