Data processing method, related device and communication system

Abstract

A data processing method, a related device and a communication system. The method comprises: a first device acquiring a first data packet and a second data packet from a service flow, wherein the first data packet comprises a first data identifier and a flow identifier of the service flow, and the second data packet comprises a second data identifier and the flow identifier of the service flow; and on the basis of the first data identifier, the second data identifier and a processing rule corresponding to the flow identifier, performing quality of services (QoS) flow mapping on the first data packet and the second data packet, so as to map the first data packet to a first QoS flow bearer and map the second data packet to a second QoS flow bearer.

Description

Data processing method, related equipment and communication system

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on October 31, 2023, with application number 202311438912.2 and invention name “Data processing method, related equipment and communication system”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of extended reality (XR), and in particular to a data processing method, related equipment, and a communication system. Background Art

[0003] Currently, for mixed service scenarios where multiple types of data, such as audio and video, are transmitted simultaneously, the main technique used is real-time transport protocol (RTP) session-level multiplexing. This technology multiplexes different types of service data packets into the same real-time transport protocol (RTP) session. In this case, different types of service data streams share the same service flow description information (such as Internet Protocol (IP) quintuples or IP triples). Fifth-generation wireless communication systems (5GS) can only distinguish between data packets in different RTP sessions and perform corresponding quality of service (QoS) processing on these RTP sessions. However, they cannot distinguish between data packets with different QoS requirements within the same RTP session. In other words, they cannot perform corresponding QoS processing on different data packets multiplexed in the same RTP session.

[0004] Summary of the Invention

[0005] The embodiments of the present application provide a data processing method, related equipment and communication system. By using the embodiments of the present application, the QoS requirements of different data packets in the same service flow can be distinguished, and corresponding QoS processing can be performed on different data packets.

[0006] In a first aspect, an embodiment of the present application provides a data processing method. The method can be applied to a first device, wherein the first device can be a user plane function (UPF) network element or a user equipment.

[0007] The first device obtains a first data packet and a second data packet in a service flow, where the first data packet includes a flow identifier and a first data identifier of the service flow, and the second data packet includes a flow identifier and a second data identifier of the service flow; the first device performs QoS flow mapping on the first data packet and the second data packet based on the first data identifier, the second data identifier and a processing rule corresponding to the flow identifier, so as to map the first data packet to a first QoS flow bearer and map the second data packet to a second QoS flow bearer.

[0008] The QoS flow indicated by the QoS flow identifier is used to carry the corresponding data packets. The flow identifier in each data packet is used to indicate the service flow. Optionally, the flow identifier is optional and can be an IP quintuple, an IP triplet, the type of service (ToS) in the IPv4 header, or a flow label in the IPv6 header. The data packets included in the service flow can include data packets of different data streams, such as audio data packets, video data packets, tactile data packets, RTP data packets, and RTCP data packets.

[0009] By detecting the data identifier carried in the data packets of the business flow, different data packets in the same business flow are distinguished based on the data identifier, and mapped to QoS flows corresponding to different QoS requirement parameters, thereby achieving corresponding QoS processing for different data packets in the same business flow.

[0010] In conjunction with the first aspect, in one possible implementation, the first device performs QoS flow mapping on the first data packet and the second data packet based on the first data identifier, the second data identifier, and a processing rule corresponding to the flow identifier, including:

[0011] The identifier of the first QoS flow is added to the first data packet, and the identifier of the second QoS flow is added to the second data packet, wherein the first data identifier corresponds to the identifier of the first QoS flow, and the second data identifier corresponds to the identifier of the second QoS flow.

[0012] In conjunction with the first aspect, in one possible implementation, the method of this embodiment further includes:

[0013] The first device obtains a processing rule corresponding to the flow identifier of the business flow, and the processing rule includes the data identifier of each data packet in the business flow and the QoS flow identifier corresponding to the data identifier of each data packet; the processing rule of the business flow is used to instruct the first device to perform QoS flow mapping on the data packets of the business flow based on the data identifier.

[0014] It should be understood that one QoS flow identifier corresponds to one or more data identifiers.

[0015] It should be understood that the processing rules of the service flow can be understood as the processing rules containing information related to the service flow, such as flow identification information.

[0016] By introducing the processing rules, the first device can determine the QoS flow identifier added to the data packet based on the data identifier of the data packet, thereby achieving corresponding QoS processing for different data packets in the same service flow.

[0017] In combination with the first aspect, in one possible implementation, the processing rule is used to indicate that the data identifier is a synchronization source (SSRC) identifier or a payload type identifier. Specifically, the SSRC identifier and the payload type identifier are in the RTP layer header of the data packet.

[0018] In conjunction with the first aspect, in a possible implementation, the processing rule is used to indicate that the data identifier is a data type identifier used to indicate that the data packet is an RTP data packet or a real-time transport control protocol (RTCP) data packet.

[0019] In conjunction with the first aspect, in one possible implementation, the processing rule is used to:

[0020] The data identifier indicating the data packet includes an identifier indicating that the data packet is an RTP data packet and an SSRC identifier of the data packet.

[0021] Or the data identifier indicating the data packet includes an identifier indicating that the data packet is an RTP data packet and a load type identifier of the data packet,

[0022] Or the data identifier of the data packet indicates that the data packet is an RTCP data packet.

[0023] In conjunction with the first aspect, in one possible implementation, the processing rule is generated based on the data identifier and the QoS requirement parameter corresponding to the data identifier. The QoS requirement parameter may be a specific QoS parameter, such as bandwidth, latency, packet loss rate, transmission priority, etc.

[0024] In conjunction with the first aspect, in one possible implementation, the first device is a user plane function network element or a user equipment. When the first device is the user equipment, the method of this embodiment further includes:

[0025] The data identifier and the QoS requirement parameters corresponding to the data identifier are sent to the session management function (SMF) network element or the policy control function (PCF) network element. The user equipment sends the data identifier and the QoS requirement parameters corresponding to the data packet to the SMF network element or the PCF network element through the access network equipment and the mobility management function (AMF) network element.

[0026] In a second aspect, an embodiment of the present application provides a data processing method, which is applied to an SMF network element.

[0027] The SMF network element obtains a flow identifier, a first data identifier included in a first data packet of a service flow identified by the flow identifier, a second data identifier included in a second data packet of the service flow identified by the flow identifier, a first QoS requirement parameter corresponding to the first data identifier, and a QoS requirement parameter corresponding to the second data identifier; the SMF network element generates a processing rule corresponding to the flow identifier based on the flow identifier, the first data identifier, the second data identifier, the first QoS requirement parameter, and the second QoS requirement parameter; the SMF network element sends the processing rule corresponding to the flow identifier to the target UPF network element or user equipment, the processing rule including the first data identifier and the QoS flow identifier corresponding to the first data identifier, the second data identifier, and the QoS flow identifier corresponding to the second data identifier. The processing rule is used to instruct the UPF network element or user equipment to perform QoS flow mapping on the data packets of the service flow based on the data identifiers of the data packets of the service flow, so as to map the first data packet to the first QoS flow bearer and the second data packet to the second QoS flow bearer.

[0028] Among them, the target UPF network element is a UPF network element selected by the SMF network element that supports the ability to perform QoS differentiated processing based on data identification.

[0029] It can be seen that SMF generates service flow processing rules based on data identification and QoS requirements corresponding to the data identification, and sends the service flow processing rules to the user equipment or UPF network element, so that different data packets in the same service flow can be processed with corresponding QoS based on the data identification.

[0030] It should be understood that the processing rule corresponds to the service flow indicated by the flow identifier, and the processing rule may include the flow identifier corresponding to the service flow, such as IP triplet, quintuple and other information.

[0031] In conjunction with the second aspect, in a possible implementation, the processing rule is used to indicate that the data identifier is an SSRC identifier or a payload type identifier.

[0032] In conjunction with the second aspect, in a possible implementation, the processing rule is used to indicate that the data identifier is a data type identifier used to indicate that the data packet is an RTP data packet or an RTCP data packet.

[0033] In conjunction with the first aspect, in one possible implementation, the processing rule is used to:

[0034] The data identifier indicating the data packet includes an identifier indicating that the data packet is an RTP data packet and an SSRC identifier of the data packet.

[0035] Or the data identifier indicating the data packet includes an identifier indicating that the data packet is an RTP data packet and a load type identifier of the data packet,

[0036] Or the data identifier of the data packet indicates that the data packet is an RTCP data packet.

[0037] In conjunction with the second aspect, in one possible implementation, a processing rule is used to indicate a data identifier and the QoS requirement parameters corresponding to the data identifier. The UPF network element or user equipment performs QoS flow mapping on the data packets of the service flow based on the data identifier, and maps the data packets of the service flow to a QoS flow that meets the QoS requirement parameters corresponding to the data identifier based on the data identifier. The QoS flow mapping specifically adds the QoS flow identifier corresponding to the QoS flow to the data packet.

[0038] In combination with the second aspect, in one possible implementation method, the SMF network element obtains multiple data identifiers and the QoS requirement parameters corresponding to each data identifier, including: the SMF network element obtains multiple PCC rules, each PCC rule includes at least one data identifier and corresponding QoS requirement parameters with the same corresponding QoS requirement parameters.

[0039] In a third aspect, an embodiment of the present application provides a data processing method, which is applied to a PCF network element.

[0040] The PCF network element receives an application function AF request sent by an application server. The AF request includes a flow identifier, multiple data identifiers and QoS requirement parameters corresponding to each data identifier; multiple PCC rules are generated based on the multiple data identifiers and the QoS requirement parameters corresponding to each data identifier, and each PCC rule includes at least one data identifier and corresponding QoS requirement parameters with the same corresponding QoS requirement parameters; the flow identifier and multiple PCC rules are used to generate processing rules, and the processing rules correspond to the service flow indicated by the flow identifier, and the processing rules include multiple data identifiers and a QoS flow identifier corresponding to each data identifier; the processing rules are used to instruct the UPF network element or user equipment to perform QoS flow mapping on the data packets of the service flow based on the data identifier.

[0041] The PCF network element generates multiple PCC rules based on multiple data identifiers and the QoS parameters corresponding to each data identifier, and sends the multiple PCC rules to the SMF network element, so that the SMF network element generates processing rules for the service flow based on the multiple PCC rules and the flow identifier of the service flow, and sends the processing rules for the service flow to the user equipment or UPF network element, and performs corresponding QoS processing on different data packets in the same service flow based on the data identifier.

[0042] It should be understood that the processing rule corresponds to the service flow indicated by the flow identifier, and the processing rule may include the flow identifier corresponding to the service flow, such as IP triplet, quintuple and other information.

[0043] In conjunction with the third aspect, in a possible implementation, the processing rule is used to indicate that the data identifier is an SSRC identifier or a payload type identifier.

[0044] In conjunction with the third aspect, in a possible implementation, the processing rule is used to indicate that the data identifier is a data type identifier used to indicate that the data packet is an RTP data packet or an RTCP data packet.

[0045] In conjunction with the third aspect, in one possible implementation, the processing rule is used to:

[0046] The data identifier indicating the data packet includes an identifier indicating that the data packet is an RTP data packet and an SSRC identifier of the data packet.

[0047] Or the data identifier indicating the data packet includes an identifier indicating that the data packet is an RTP data packet and a load type identifier of the data packet,

[0048] Or the data identifier indicating the data packet includes an identifier indicating that the data packet is an RTCP data packet.

[0049] In a fourth aspect, an embodiment of the present application provides a first device, comprising a unit or module for implementing the method provided in the first aspect or any possible implementation manner of the first aspect.

[0050] In a fifth aspect, an embodiment of the present application provides an SMF network element, comprising a unit or module for implementing the method provided in the second aspect or any possible implementation method of the second aspect.

[0051] In a sixth aspect, an embodiment of the present application provides a PCF network element, comprising a unit or module for implementing the method provided in the third aspect or any possible implementation method of the third aspect.

[0052] In a seventh aspect, an embodiment of the present application provides a first device comprising a processor and a memory. The memory is configured to store program code. The processor is configured to call the program code stored in the memory to execute the method provided in the first aspect or any possible implementation of the first aspect.

[0053] In an eighth aspect, an embodiment of the present application provides an SMF network element, comprising a processor and a memory. The memory is configured to store program code. The processor is configured to invoke the program code stored in the memory to execute the method provided in the second aspect or any possible implementation of the second aspect.

[0054] In a ninth aspect, an embodiment of the present application provides a PCF network element, comprising a processor and a memory. The memory is configured to store program code. The processor is configured to invoke the program code stored in the memory to execute the method provided in the third aspect or any possible implementation of the third aspect.

[0055] In the tenth aspect, an embodiment of the present application provides a computer storage medium comprising computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes a method as provided in any possible implementation of the first aspect, or a method as provided in any possible implementation of the second aspect, or a method as provided in any possible implementation of the third aspect.

[0056] In the eleventh aspect, an embodiment of the present application provides a computer program product, which, when the computer program product is run on a computer, enables the computer to execute the method provided in any possible implementation of the first aspect, or the method provided in any possible implementation of the second aspect, or the method provided in any possible implementation of the third aspect.

[0057] In a twelfth aspect, an embodiment of the present application further provides a data processing method, which is applied to a communication system, the communication system including a user equipment, a UPF network element, an SMF network element and an application server, the method comprising:

[0058] The SMF network element obtains a flow identifier from the user equipment or application server, a first data identifier included in a first data packet of a service flow identified by the flow identifier, a second data identifier included in a second data packet of the service flow identified by the flow identifier, a first service quality QoS requirement parameter corresponding to the first data identifier, and a second QoS requirement parameter corresponding to the second data identifier;

[0059] The SMF network element generates a processing rule corresponding to the flow identifier according to the flow identifier, the first data identifier, the second data identifier, the first QoS requirement parameter, and the second QoS requirement parameter; the processing rule is used to instruct the UPF network element or the user equipment to perform QoS flow mapping on the data packet of the service flow based on the data identifier; the processing rule includes the first data identifier and the QoS flow corresponding to the first data identifier and the second data identifier and the QoS flow corresponding to the second data identifier;

[0060] The SMF network element sends the processing rules corresponding to the flow identifier to the UPF network element or user equipment.

[0061] The application server sends the first data packet and the second data packet to the UPF network element, or the user equipment obtains the first data packet and the second data packet;

[0062] The UPF network element or user equipment performs service quality QoS flow mapping on the first data packet and the second data packet based on the first data identifier, the second data identifier and the processing rule corresponding to the flow identifier, so as to map the first data packet to the first QoS flow bearer and map the second data packet to the second QoS flow bearer.

[0063] In a thirteenth aspect, an embodiment of the present application further provides a communication system, which includes a user equipment, a UPF network element, an SMF network element and an application server.

[0064] The SMF network element is configured to obtain, from a user device or an application server, a flow identifier, a first data identifier included in a first data packet of a service flow identified by the flow identifier, a second data identifier included in a second data packet of the service flow identified by the flow identifier, a first service quality QoS requirement parameter corresponding to the first data identifier, and a second QoS requirement parameter corresponding to the second data identifier;

[0065] The SMF network element is further used to generate a processing rule corresponding to the flow identifier according to the flow identifier, the first data identifier, the second data identifier, the first QoS requirement parameter, and the second QoS requirement parameter; the processing rule is used to instruct the UPF network element or the user equipment to perform QoS flow mapping on the data packet of the service flow based on the data identifier; the processing rule includes the first data identifier and the QoS flow corresponding to the first data identifier and the second data identifier and the QoS flow corresponding to the second data identifier;

[0066] The SMF network element is also used to send the processing rules corresponding to the flow identifier to the UPF network element or user equipment.

[0067] The application server is configured to send the first data packet and the second data packet to the UPF network element, or the user equipment is configured to obtain the first data packet and the second data packet;

[0068] The UPF network element or user equipment is used to perform service quality QoS flow mapping on the first data packet and the second data packet based on the first data identifier, the second data identifier and the processing rule corresponding to the flow identifier, so as to map the first data packet to the first QoS flow bearer and map the second data packet to the second QoS flow bearer.

[0069] It can be understood that the beneficial effects of the embodiments described in the fourth to thirteenth aspects can refer to the beneficial effects of the methods described in the first to third aspects, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0070] FIG1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application;

[0071] FIG2 is a flow chart of a data processing method provided in an embodiment of the present application;

[0072] Figure 2a is a schematic diagram of the header data of an RTP packet;

[0073] Figure 2b is a schematic diagram of the header data of the RTCP packet;

[0074] FIG3 is a flow chart of another data processing method provided in an embodiment of the present application;

[0075] FIG4 is a flow chart of another data processing method provided in an embodiment of the present application;

[0076] FIG5 is a schematic diagram of an interactive flow chart of a data processing method provided in an embodiment of the present application;

[0077] FIG6 is a schematic structural diagram of a first device provided in an embodiment of the present application;

[0078] FIG7 is a schematic structural diagram of an SMF network element provided in an embodiment of the present application;

[0079] FIG8 is a schematic diagram of the structure of a PCF network element provided in an embodiment of the present application;

[0080] FIG9 is a schematic structural diagram of another first device provided in an embodiment of the present application;

[0081] FIG10 is a schematic structural diagram of another SMF network element provided in an embodiment of the present application;

[0082] FIG11 is a schematic diagram of the structure of another PCF network element provided in an embodiment of the present application. DETAILED DESCRIPTION

[0083] The terms "first", "second", "third" and "fourth" in the specification, claims and drawings of this application are used to distinguish different objects rather than to describe a specific order.

[0084] "Multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating the existence of three relationships. For example, "A and / or B" means: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the related objects are in an "or" relationship.

[0085] The embodiments of the present application are described below with reference to the accompanying drawings.

[0086] Refer to Figure 1, which is a schematic diagram of a communication system architecture provided in an embodiment of the present application. The communication system is a schematic diagram of the network architecture of the fifth generation mobile communication technology (5th Generation Mobile Networks, 5G). It includes a (radio) access network ((radio) access network, (R)AN, which can be expressed as two parts: RAN equipment and core network (CN). RAN equipment is used to provide network access functions for authorized user equipment (User Equipment, UE) in a specific area, and can use transmission tunnels of different qualities according to the level of UE, business requirements, etc. For example, RAN equipment can manage wireless resources, provide access services for UE, and then complete the forwarding of control information and / or data information between UE and CN.

[0087] To facilitate understanding of the embodiment of the present application, an application scenario of the embodiment of the present application is first described in detail with reference to FIG1 .

[0088] 1. User equipment (UE): can be referred to as terminal equipment, terminal, access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user device. The terminal equipment can also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, an unmanned aerial vehicle (UAV), a wearable device, a terminal device in a 5G network, or a terminal device in an evolved public land mobile network (PLMN), etc., and the embodiments of the present application are not limited to this.

[0089] 2. Access network (AN): Provides network access for authorized users in a specific area and can use transmission tunnels of different qualities based on user levels and business requirements. Access networks can be access networks that use different access technologies. Current access network technologies include: wireless access network technology used in third-generation (3G) systems, wireless access network technology used in fourth-generation (4G) systems, or next-generation radio access network (NG-RAN) technology (such as the wireless access technology used in 5G systems).

[0090] An access network that implements network access functions based on wireless communication technologies is called a radio access network (RAN). The RAN manages radio resources, provides access services to terminals, and forwards control signals and user data between terminals and the core network.

[0091] The wireless access network device can be, for example, a base station (NodeB), an evolved NodeB (eNB or eNodeB), a next generation Node base station (gNB) in a 5G mobile communication system, a base station in a future mobile communication system, or an access point (AP) in a wifi wireless hotspot system, etc. It can also be a wireless controller in a cloud radio access network (CRAN) scenario, or the wireless access network device can be a relay station, an access point, a vehicle-mounted device, a drone, a wearable device, a network device in a 5G network, or a network device in an evolved PLMN, etc. The embodiments of the present application do not limit the specific technology and specific device form adopted by the wireless access network device.

[0092] 3. Access Management NE: This is primarily responsible for mobility management and access management, and is responsible for delivering user policies between user devices and PCF NEs. It can be used to implement other functions of the Mobility Management Entity (MME) besides session management, such as access authorization (authentication).

[0093] In a 5G communication system, the access management network element may be an access and mobility management function (AMF) network element. In future communication systems, the access management network element may still be an AMF network element, or may have other names, which are not limited in this application.

[0094] 4. Session management network element: It is mainly used for session management, allocation and management of Internet protocol (IP) addresses of user devices, selection of endpoints for manageable user plane functions, policy control and charging function interfaces, and downlink data communications.

[0095] In a 5G communication system, the session management network element may be an SMF network element. In future communication systems, the session management network element may still be an SMF network element, or may have other names, which are not limited in this application.

[0096] 5. User plane network element: used for packet routing and forwarding, QoS processing of user plane data, completion of user plane data forwarding, session / flow-level billing statistics, bandwidth limitation functions, etc.

[0097] In a 5G communication system, the user plane network element may be a UPF network element. In future communication systems, the user plane network element may still be a UPF network element, or may have other names, which are not limited in this application.

[0098] 6. Data network element: a network used to provide data transmission.

[0099] In a 5G communication system, a data network element may be a data network (DN) element. In future communication systems, a data network element may still be a DN element, or may have other names, which are not limited in this application.

[0100] 7. Policy control network element: A unified policy framework used to guide network behavior and provide policy rule information for control plane functional network elements (such as AMF, SMF network elements, etc.).

[0101] In a 4G communication system, the policy control network element may be a policy and charging rules function (PCRF) network element. In a 5G communication system, the policy control network element may be a PCF network element. In future communication systems, the policy control network element may still be a PCF network element, or may have other names, which are not limited in this application.

[0102] 8. Data management network element: used to process user equipment identification, access authentication, registration and mobility management, etc.

[0103] In a 5G communication system, the data management network element may be a unified data management (UDM) network element; in a 4G communication system, the data management network element may be a home subscriber server (HSS) network element. In future communication systems, the data management network element may still be a UDM network element, or may have other names, which are not limited in this application.

[0104] 9. Network exposure function (NEF) network element: used to securely open up services and capabilities provided by the 3rd Generation Partnership Project (3GPP) network function to the outside world.

[0105] 10. Application Function (AF) Network Element: Provides certain application layer services to the UE. When providing services to the UE, the AF has requirements for QoS and charging policies and needs to notify the network. At the same time, the AF also needs to obtain application-related information from the core network. The AF can have all the functions of the AF defined in the technical specification (TS) 23.501R-15, as well as related functions for application services. In other words, in the user plane architecture, the application server (AS) and the UE communicate in the user plane through the UE-RAN-UPF-AF path. The AF can also communicate with other network function (NF) network elements in the 5G core network (5GC) through the NEF in the control plane architecture. For example, it communicates with the PCF network element through the NEF network element. If the AF is deployed by the 5GC operator, the AF network element can also communicate directly with other NF network elements in the 5GC in the control plane architecture without going through the NEF network element, such as directly communicating with the PCF network element.

[0106] 11. Network data analysis function (NWDAF) network element: It can be used to collect data from the network element, AF, and operation administration and maintenance (OAM) side, analyze the data through machine learning, artificial intelligence and other solutions, and feedback to the network element, AF, etc. to optimize network or service configuration, thereby providing better network quality and service experience.

[0107] 12. Network repository function (NRF) element: This element provides NE discovery and provides NE information corresponding to the NE type upon request from other NEs. NRF elements also provide NE management services, such as NE registration, update, and deregistration, as well as NE status subscription and push notification.

[0108] 13. Authentication server function (AUSF) network element: Mainly responsible for authenticating users to determine whether users or devices are allowed to access the network.

[0109] 14. Service communication proxy (SCP) network element: It can be used for direct and indirect communication between NFs. The service requests of NFs can be proxied by SCP.

[0110] In Figure 1, N1, N2, N3, N4, N6, N9, Nnwdaf, Nnef, Nnrf, Npcf, Nudm, Naf, Nausf, Namf, and Nsmf are interface sequence numbers. The meanings of these interface sequence numbers can be found in 3GPP TS 23.501.

[0111] It should be understood that the above-mentioned network architecture applied to the embodiments of the present application is only an example, and the network architecture applicable to the embodiments of the present application is not limited to this. Any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiments of the present application.

[0112] It should also be understood that the AMF network element, SMF network element, UPF network element, NEF network element, PCF network element, UDM network element, NWDAF network element, NRF network element, AUSF network element, SCP network element, etc. shown in Figure 1 can be understood as network elements used to implement different functions in the core network, for example, they can be combined into network slices as needed. These core network network elements can be independent devices or integrated into the same device to implement different functions. This application does not limit the specific form of the above network elements.

[0113] It should also be understood that the above naming is only defined to facilitate the distinction between different functions and should not constitute any limitation to this application. This application does not exclude the possibility of adopting other naming in 5G networks and other networks in the future. For example, in a 6G network, some or all of the above networks may continue to use the terminology in 5G, or other names may be used. The interface name between the various network elements in Figure 1 is only an example. The name of the interface in the specific implementation may be other names, and this application does not make specific limitations on this. In addition, the name of the message (or signaling) transmitted between the above-mentioned network elements is only an example and does not constitute any limitation on the function of the message itself.

[0114] Referring to FIG2 , FIG2 is a flow chart of a data processing method provided in an embodiment of the present application. The method is applied to a first device, which is a UPF network element or user equipment in the 5G system shown in FIG1 . As shown in FIG2 , the method includes:

[0115] S201. A first device obtains a first data packet and a second data packet in a service flow.

[0116] The service flow includes one or more data packets. The first data packet and the second data packet are data packets included in the same service flow. The first data packet includes a flow identifier and a first data identifier, and the second data packet includes a flow identifier and a second data identifier. The flow identifier is used to identify the service flow. Optionally, the flow identifier is an IP quintuple, an IP triplet, the ToS of the IPv4 header, or a flow label (flowlabel) of the IPv6 header. The IP quintuple includes the source IP address, source port, destination IP address, destination port, and transport layer protocol. The IP triplet includes the destination IP address, destination port number, and protocol.

[0117] In an example, the data packets of the service flow may be one or more of audio data packets, video data packets, tactile data packets, RTP data packets, RTCP data packets, and the like.

[0118] Optionally, the data identifier is an SSRC identifier, a payload type identifier, or a data type identifier used to indicate that the data packet is an RTP stream or an RTCP stream.

[0119] It should be noted that service flows come from two sources: the application layer of the user device and the application server. Service flows from the application layer of the user device are uplink service flows, while service flows from the application server are downlink service flows.

[0120] S202. The first device performs QoS flow mapping on the first data packet and the second data packet based on the first data identifier, the second data identifier and the processing rule corresponding to the flow identifier, so as to map the first data packet to the first QoS flow bearer and map the second data packet to the second QoS flow bearer.

[0121] The processing rule includes a data identifier of a data packet in a service flow and a QoS flow identifier corresponding to the data identifier.

[0122] The first device performs QoS flow mapping on the first data packet and the second data packet based on the first data identifier, the second data identifier and the processing rules corresponding to the flow identifier, specifically referring to: adding the identifier of the first QoS flow to the first data packet and adding the identifier of the second QoS flow to the second data packet; or carrying the first data packet on the first QoS flow for transmission and carrying the second data packet on the second QoS flow for transmission, wherein the first data identifier corresponds to the identifier of the first QoS flow and the second data identifier corresponds to the identifier of the second QoS flow.

[0123] In this way, data packets in the service flow can be mapped to corresponding QoS flows based on data identifiers, thereby achieving corresponding QoS processing for the data packets in the service flow.

[0124] It should be understood that data packets belonging to the same service flow have the same flow identifier, such as the IP five-tuple, IP triplet and other information carried in these data packets are the same. For example, the above-mentioned service flow includes a first data packet and a second data packet, wherein the first data packet includes a flow identifier and a first data identifier, and the second data packet includes a flow identifier and a second data identifier. The first data packet and the second data packet have different QoS requirements, the first data identifier corresponds to the identifier of the first QoS flow, and the second data identifier corresponds to the identifier of the second QoS flow. In other words, the identifier of the first QoS flow is added to the first data packet, and the identifier of the second QoS flow is added to the second data packet, that is, the first data packet is mapped to the first QoS flow, and the second data packet is mapped to the second QoS flow, thereby achieving corresponding QoS processing for the first data packet and the second data packet. Specifically, the identifier of the QoS flow can be added to the user plane general packet radio service tunneling protocol (general packet radio service tunneling protocol-userplane) GTP-U layer or the service data adaptation protocol (SDAP) layer of the data packet.

[0125] In one possible embodiment, the first device obtains a processing rule corresponding to a flow identifier, where the processing rule includes a data identifier for each data packet of the service flow and a QoS flow identifier corresponding to each data identifier, where there is one or more data identifiers corresponding to one QoS flow identifier. The processing rule of the service flow is used to instruct the UPF network element or user equipment to perform QoS flow mapping on the data packets of the service flow based on the data identifier.

[0126] It should be pointed out here that for user equipment, the processing rule is the QoS rule, and for the UPF network element, the processing rule is the N4 rule.

[0127] Among them, the first device obtains the processing rules of the business flow based on the flow identifier of the business flow, that is, the processing rules of the business flow refer to the processing rules of the business flow for data detection and QoS mapping for the data packets in the business flow, or the processing rules of the business flow will contain description information of the business flow, such as the flow identifier, which can be an IP triplet, an IP quintuple, the ToS of the IPv4 header, or the flow label (Flowlabel) of the IPv6 header, etc. It can also be understood that there is a correspondence between the processing rules and the flow identifier. In one example, the processing rules include the flow identifier, and the first device matches the flow identifier of the data packet with the flow identifier in the processing rules, and determines the processing rules of the matching flow identifier as the processing rules of the business flow. In another example, the first device obtains a correspondence table between processing rules and flow identifiers, and the first device traverses the correspondence table between processing rules and flow identifiers based on the flow identifier of the data packet to obtain the processing rules corresponding to the flow identifier of the data packet, and determines the processing rules as the processing rules of the above-mentioned business flow.

[0128] In one possible implementation, the processing rule indicates that the data identifier of a data packet is an SSRC identifier or a payload type identifier. It should be noted that the data packets included in the service flow are RTP data packets, and the data identifier of the data packets is included in the header of the RTP data packets. The first device distinguishes the data packets based on the SSRC identifier or payload type identifier of the data packets, thereby determining the QoS requirements of the data packets.

[0129] In one possible implementation, the processing rule indicates that the data identifier of a data packet is a data type identifier indicating whether the data packet is an RTP packet or an RTCP packet. The service flow includes RTCP packets and RTP packets. The first device distinguishes whether a data packet is an RTCP packet or an RTP packet based on the data type identifier of the data packet. In one example, when the data type identifier of the data packet includes a payload type (PT) identifier and an M field, the first device determines that the data packet is an RTP packet based on the payload type identifier and the M field. The payload type identifier and the M field occupy 8 bits in the RTP packet header, the payload type identifier occupies 7 bits, and the M field occupies 1 bit, as shown in FIG2a. The first device determines that the data packet is an RTP packet based on the value of these 8 bits. When the data type identifier of the data packet includes only a packet type (PT) identifier, the first device determines that the data packet is an RTCP packet. The packet type identifier occupies 8 bits in the RTCP packet header, as shown in FIG2b. The first device determines that the data packet is an RTCP packet based on the value of these 8 bits. It should be noted that PT in FIG2a represents the payload type, and PT in FIG2b represents the packet type.

[0130] The load type identifier and M field in the RTP data packet are in the same position as the data packet type identifier in the RTCP data packet, both occupying 8 bits. The first device determines whether the data packet is an RTP data packet or an RTCP data packet based on the value of these 8 bits.

[0131] In one possible implementation, the processing rules are used to:

[0132] The data identifier indicating the data packet includes an identifier indicating that the data packet is an RTP data packet and an SSRC identifier of the data packet.

[0133] Or the data identifier indicating the data packet includes an identifier indicating that the data packet is an RTP data packet and a load type identifier of the data packet,

[0134] Or the data identifier of the data packet is an identifier indicating that the data packet is an RTCP data packet.

[0135] This implementation method targets the following scenario: when a service flow includes both RTP packets and RTCP packets, and different RTP packets correspond to different QoS requirements, the first device determines the type of data packet (RTP packet and RTCP packet) of the service flow based on the data identifier of the data packet in the service flow, and then maps the RTCP packet to the corresponding QoS flow, thereby ensuring that the RTCP packet meets the corresponding QoS requirement; for RTP packets corresponding to different QoS requirements, the first device further determines the third QoS flow corresponding to the first RTP packet based on the SSRC identifier or load type identifier in the data identifier of the RTP packet, and maps the first RTP packet to the third QoS flow corresponding to its SSRC identifier or load type identifier, and the first device further determines the fourth QoS flow corresponding to the second RTP packet based on the SSRC identifier or load type identifier carried in the data identifier of the RTP packet, and maps the second RTP packet to the fourth QoS flow corresponding to its SSRC identifier or load type identifier.

[0136] It should be noted that different QoS requirement parameters corresponding to RTP packets mean that different RTP packets have different QoS requirements. RTP packets can be of the same type, such as all video packets, or they can be of different types. For example, the first RTP packet mentioned above can be a video packet, and the second RTP packet can be an audio packet. Alternatively, some RTP packets of the same type can have different QoS requirements, such as the first RTP data packet being a first video packet, the second RTP packet being a second video packet, and the third RTP packet being an audio packet. The second RTP packet, the third RTP packet, and the third RTP packet can each have different QoS requirements.

[0137] It should be pointed out that, for data packets of type RTP data packets, there are two forms of data identification: one is that the data identification includes a load type identifier, an M field and an SSRC identifier; wherein, the load type identifier and the M field are used to identify the data packet as an RTP data packet, that is, the data packet is determined to be an RTP data packet through the values ​​corresponding to the load type identifier and the M field, and the SSRC identifier is used to further identify the data packet within the range of the RTP data packet to determine the QoS requirement or QoS flow corresponding to the RTP data packet; the other is that the data identification includes a load type identifier and an M field, wherein the load type identifier and the M field are used to identify the data packet as an RTP data packet, that is, the data packet is determined to be an RTP data packet through the values ​​corresponding to the load type identifier and the M field, and the load type identifier is used to further identify the data packet within the range of the RTP data packet to determine the QoS requirement or QoS flow corresponding to the RTP data packet.

[0138] In one possible implementation, the processing rule is generated based on the data identifier and the QoS requirement parameter corresponding to the data identifier, wherein the QoS requirement parameter may be a specific QoS parameter such as bandwidth, delay, packet loss rate, transmission priority, etc.

[0139] In one possible implementation, the processing rules come from the SMF network element.

[0140] In one example, the SMF network element obtains the flow identifier of the service flow and multiple PCC rules. A PCC rule includes at least one data identifier and corresponding QoS requirement parameters and the flow identifier of the service flow. It should be understood that the QoS requirement parameters corresponding to the data identifier included in a PCC rule are the same. The SMF network element generates a processing rule for the service flow based on the flow identifier of the service flow and multiple PCC rules. Among them, the PCC rule is generated by the PCF network element based on at least one data identifier from the user equipment or application server and the QoS requirement parameters corresponding to each data identifier. It should be understood that the flow identifier of the service flow comes from the user equipment or application server and is forwarded to the SMF network element by the PCF network element. The PCC rule will include a flow identifier to clarify that the data packet carrying the data identifier in the current service flow needs to be subjected to QoS processing corresponding to the QoS requirement parameters. In another example, the SMF network element obtains at least one data identifier from the user equipment or application function (AF) network element and the QoS requirement parameters corresponding to each data identifier and the flow identifier of the service flow from the PCF network element. The SMF network element generates a processing rule for the service flow based on the at least one data identifier from the user equipment or application function network element and the QoS requirement parameters corresponding to each data identifier and the flow identifier of the service flow. Optionally, the user equipment directly sends at least one data identifier and the QoS requirement parameters corresponding to each data identifier and the flow identifier of the service flow to the SMF network element. Specifically, the user equipment sends the above information to the AMF network element, which forwards it to the SMF network element.

[0141] It should be understood that when data packets with the same QoS requirement exist in multiple service flows, one PCC rule includes multiple flow identifiers.

[0142] It should be noted that the user equipment here may refer to a communication module (modem) of the user equipment.

[0143] In one possible implementation, when the first device is a user equipment, the method of this embodiment further includes:

[0144] The user equipment sends at least one data identifier, a QoS requirement parameter corresponding to each data identifier in the at least one data identifier, and a flow identifier of the service flow to the PCF network element or the SMF network element.

[0145] Specifically, the application layer of the user device sends an AT command to the communication module of the user device. The AT command is used to request QoS differentiated processing of data packets in the service flow. The AT command includes at least one data identifier, a QoS requirement parameter corresponding to each data identifier in the at least one data identifier, and a flow identifier of the service flow. It should be understood that the data identifier included in the AT command is the data identifier of the data packet in the service flow. When the communication module of the user device receives the AT command, the communication module of the user device determines whether the communication module of the user device supports the ability to perform QoS differentiated processing based on the data identifier of the data packet; if it is determined that the communication module of the user device supports the ability to perform QoS differentiated processing based on the data identifier of the data packet, the communication module of the user device sends at least one data identifier, a QoS requirement parameter corresponding to each data identifier, and a flow identifier of the service flow to the PCF network element or the SMF network element, requesting the network side to provide corresponding QoS requirements for the service flow data packet corresponding to each data identifier.

[0146] It can be seen that in the solution of this embodiment, by detecting the data identifier carried in the data packet of the business flow, different data packets in the same business flow are distinguished based on the data identifier, and they are mapped to QoS flows corresponding to different QoS requirement parameters, thereby realizing corresponding QoS processing of different data packets in the same business flow.

[0147] Referring to FIG3 , FIG3 is a flow chart of another data processing method provided in an embodiment of the present application. Applied to the SMF network element in FIG1 . The method includes:

[0148] S301, the SMF network element obtains the flow identifier, the first data identifier included in the first data packet of the service flow identified by the flow identifier, the second data identifier included in the second data packet of the service flow identified by the flow identifier, the first service quality QoS requirement parameter corresponding to the first data identifier, and the second QoS requirement parameter corresponding to the second data identifier.

[0149] The QoS requirement parameters may be specific QoS parameters, such as bandwidth, delay, packet loss rate, transmission priority, etc.

[0150] In one example, the SMF network element obtains multiple PCC rules from the PCF network element. Each PCC rule includes at least one data identifier, corresponding QoS requirement parameters, and a flow identifier of a service flow. It should be understood that the QoS requirement parameters corresponding to the data identifiers included in a PCC rule are the same. The PCC rule is generated by the PCF network element based on at least one data identifier from a user device or an application server and the QoS requirement parameters corresponding to each data identifier. It should be understood that the flow identifier of the service flow comes from the user device or application server and is sent by the PCF network element to the SMF network element via the PCC rule.

[0151] In another example, the SMF network element obtains at least one data identifier from the user equipment or application server and the QoS requirement parameters corresponding to each data identifier and the flow identifier of the service flow from the PCF network element.

[0152] Optionally, the user equipment directly sends at least one data identifier and the QoS requirement parameters corresponding to each data identifier and the flow identifier of the service flow to the SMF network element. In other words, the at least one data identifier and the QoS requirement parameters corresponding to each data identifier and the flow identifier of the service flow obtained by the SMF network element come from the user equipment, passing through the access network device and the AMF network element.

[0153] S302. The SMF network element generates a processing rule corresponding to the flow identifier according to the flow identifier, the first data identifier, the second data identifier, the first QoS requirement parameter, and the second QoS requirement parameter.

[0154] In one feasible implementation, the SMF network element generates a processing rule for the service flow based on the received PCC rule. In another feasible implementation, the SMF network element generates a processing rule corresponding to the flow identifier based on the received flow identifier, the first data identifier, the second data identifier, the first QoS requirement parameter, and the second QoS requirement parameter. In another feasible implementation, the SMF network element generates a processing rule for the service flow based on at least one pre-configured data identifier and the QoS requirement parameter corresponding to each data identifier, as well as the flow identifier of the service flow.

[0155] The service flow processing rules include the data identifier of each data packet in the service flow and the QoS flow identifier corresponding to each data identifier. There are one or more data identifiers corresponding to a QoS flow identifier. The service flow processing rules are used to instruct the UPF network element or user equipment to perform QoS flow mapping on the data packets of the service flow based on the data identifier, that is, based on the data identifier carried by the data packets in the service flow, add the QoS flow identifier corresponding to the data identifier to the data packet.

[0156] According to the above method, the SMF network element can obtain multiple processing rules, and the multiple processing rules correspond to the business flow.

[0157] In one example, each of the plurality of processing rules includes a flow identifier of a corresponding service flow. In another example, the SMF network element generates a correspondence table between processing rules and flow identifiers based on the correspondence between the plurality of processing rules and the plurality of service flows.

[0158] In one possible implementation, the processing rule indicates that the data identifier of a data packet is an SSRC identifier or a payload type identifier. It should be noted that the data packets included in the service flow are RTP packets, and the data identifier of the data packet is included in the RTP packet header. The user equipment or target UPF network element distinguishes the data packets based on the SSRC identifier or payload type identifier of the data packets, thereby determining the QoS requirements of the data packets.

[0159] In one possible implementation, the processing rule is used to indicate that the data identifier of a data packet is a data type identifier used to indicate that the data packet is an RTP packet or an RTCP packet. The service flow includes RTCP packets and RTP packets. The user equipment or target UPF network element distinguishes whether a data packet is an RTCP packet or an RTP packet based on the data type identifier of the data packet. In one example, when the data type identifier of the data packet includes a payload type identifier and an M field, the user equipment or target UPF network element determines that the data packet is an RTP packet based on the payload type identifier and the M field, wherein the payload type identifier and the M field occupy 8 bits in the header of the RTP packet, the payload type PT identifier occupies 7 bits, and the M field occupies 1 bit; the user equipment or target UPF network element determines that the data packet is an RTP packet based on the values ​​corresponding to these 8 bits. When the data type identifier of the data packet only includes a packet type identifier, the user equipment or target UPF network element determines that the data packet is an RTCP packet based on the packet type identifier, wherein the packet type identifier occupies 8 bits in the header of the RTCP packet; the user equipment or target UPF network element determines that the data packet is an RTCP packet based on the value corresponding to these 8 bits. The load type identifier and M field in the RTP data packet are in the same position as the data packet type identifier field in the RTCP data packet. The first device determines whether the data packet is an RTP data packet or an RTCP data packet based on the value of these 8 bits.

[0160] In one possible implementation, the processing rules are used to:

[0161] The data identifier indicating the data packet includes an identifier indicating that the data packet is an RTP data packet and an SSRC identifier of the data packet.

[0162] Or the data identifier indicating the data packet includes an identifier indicating that the data packet is an RTP data packet and a load type identifier in the data packet,

[0163] Or the data identifier of the indication data packet is an identifier indicating that the data packet is an RTCP data packet.

[0164] This implementation method is targeted at the following scenarios: when a service flow includes both RTP packets and RTCP packets, and there are multiple RTP packets, the user device or the target UPF network element determines the type of data packet in the service flow (RTP packets and RTCP packets) based on the data identifier of the data packet in the service flow, and then maps the RTCP data packet to the corresponding QoS flow, thereby ensuring that the RTCP data packet meets the corresponding QoS requirements; for multiple RTP data packets, the user device or the target UPF network element further determines the QoS flow corresponding to the RTP data packet based on the SSRC identifier or load type identifier carried in the RTP data packet, and maps the RTP data packet to the QoS flow corresponding to its SSRC identifier or load type identifier.

[0165] It should be pointed out that for data packets of type RTP data packets, there are two forms of data identification: one is that the data identification includes a load type identifier, an M field and an SSRC identifier; wherein, the load type identifier and the M field are used to identify the data packet as an RTP data packet, that is, the data packet is determined to be an RTP data packet through the values ​​corresponding to the load type identifier and the M field, and the SSRC identifier is used to further identify the data packet within the range of the RTP data packet; the other is that the data identification includes a load type identifier and an M field, wherein the load type identifier and the M field are used to identify the data packet as an RTP data packet, that is, the data packet is determined to be an RTP data packet through the values ​​corresponding to the load type identifier and the M field, and the load type identifier is used to further identify the data packet within the range of the RTP data packet.

[0166] S303, the SMF network element sends a processing rule to the target UPF network element or user equipment, and the processing rule is used to perform QoS flow mapping on the data packets of the service flow based on the data identifier of the data packets of the service flow, so as to map the first data packet to the first QoS flow bearer and map the second data packet to the second QoS flow bearer.

[0167] In one example, the processing rules include the flow identifier of the corresponding service flow, and the SMF network element only needs to send the processing rules to the target UPF network element or user equipment.

[0168] In another example, the processing rules do not include the flow identifier of the corresponding service flow, and the SMF network element also needs to send a correspondence table between the processing rules and the flow identifier to the target UPF network element or user equipment.

[0169] Optionally, there may be multiple UPF network elements in the 5GS network, some of which do not support the ability to perform differentiated QoS processing on data packets based on the data identifier of the data packet, while some support the ability to perform differentiated QoS processing on data packets based on the data identifier of the data packet. The SMF network element obtains the UPF network element that supports the ability to perform differentiated QoS processing on data packets based on the data identifier of the data packet from multiple UPF network elements, and uses the UPF network element as the target UPF network element. Specifically, the ability to support differentiated QoS processing on data packets based on the data identifier of the data packet mainly refers to the ability to identify the data identifier in the data packet and to map the data packet to the corresponding QoS flow according to the data identifier, or simply refers to the ability to identify the data identifier in the data packet. It should be pointed out here that for user equipment, the processing rule is the QoS rule, and for UPF network elements, the processing rule is the N4 rule.

[0170] It can be seen that in the solution of this embodiment, SMF generates service flow processing rules based on data identification and QoS requirements corresponding to the data identification, and sends the service flow processing rules to the user equipment or UPF network element, so that different data packets in the same service flow are subjected to corresponding QoS processing based on the data identification.

[0171] Referring to FIG4 , FIG4 is a flow chart of another data processing method provided in an embodiment of the present application. Applied to the PCF network element in FIG1 , the method includes:

[0172] S401. A PCF network element receives an application function AF request sent by an application server. The AF request includes a flow identifier, multiple data identifiers, and a QoS requirement parameter corresponding to each data identifier.

[0173] The AF request is used to request differentiated QoS processing for packets in a service flow. The flow identifier is used to indicate the service flow and can specifically include descriptive information about the service flow, such as an IP triplet, an IP quintuple, the Type of Service (ToS) in the IPv4 header, or a Flow Label (FlowLabel) in the IPv6 header. The QoS requirement parameters can be specific QoS parameters, such as bandwidth, latency, packet loss rate, and transmission priority.

[0174] The PCF network element sends a response message to the application server regarding the AF request. If the PCF network element supports the capability to perform differentiated QoS processing on packets in a service flow based on the packet's data identifier, the response message indicates that the PCF network element can meet the requirement for differentiated QoS processing on packets in a service flow based on the packet's data identifier. If the PCF network element does not support the capability to perform differentiated QoS processing on packets in a service flow based on the packet's data identifier, the response message carries error indication information, indicating that the PCF network element does not support the capability to perform differentiated QoS processing on packets in a service flow based on the packet's data identifier. The PCF network element's failure to support differentiated QoS processing on packets in a service flow based on the packet's data identifier means that the network in which the PCF network element resides does not support the capability to perform differentiated QoS processing on packets in a service flow based on the packet's data identifier, or that the UPF network element or UE in the network in which the PCF network element resides does not support the capability to perform differentiated QoS processing on packets in a service flow based on the packet's data identifier. The specific meaning of supporting the capability to perform differentiated QoS processing on packets in a service flow based on the packet's data identifier can be found in the explanation in S302 above.

[0175] S402: The PCF network element generates multiple PCC rules based on multiple data identifiers and QoS parameters corresponding to each data identifier.

[0176] Each PCC rule includes at least one data identifier and corresponding QoS requirement parameters that are identical to the corresponding QoS requirement parameters. Furthermore, the PCC rule also includes a flow identifier. Multiple PCC rules are used to generate processing rules, each of which includes a flow identifier for a service flow. The processing rules include multiple data identifiers and a QoS flow identifier corresponding to each data identifier. The processing rules are used to instruct the UPF network element or user equipment to perform QoS flow mapping on data packets of the service flow based on the data identifiers.

[0177] In one possible implementation, the processing rules are used to indicate that the data identifier of the data packet is an SSRC identifier or a load type identifier. It should be noted that the data packets included in the service flow are RTP data packets, and the data identifier of the data packet is in the header of the RTP data packet. The UPF network element or user equipment distinguishes the data packets by the SSRC identifier or load type identifier of the data packet, thereby determining the QoS requirements of the data packet. The processing rules also include the flow identifier of the service flow, that is, the flow description information. The processing rules are used to instruct the UPF network element or user equipment to determine that the RTP data packet is a data packet of the service flow based on the flow identifier / flow description information, and further map the data packet to the corresponding QoS flow based on the data identifier.

[0178] In one possible implementation, a processing rule indicates that the data identifier of a data packet is a data type identifier used to indicate that the data packet is an RTP data packet or an RTCP data packet. The data type identifier is used to distinguish whether the data packet is an RTP data packet or an RTCP data packet. Specifically, it may refer to the value or value range corresponding to the 8 bits occupied by the M field of the payload type identifier in the RTP data packet header and / or the value or value range corresponding to the 8 bits occupied by the packet type identifier in the RTCP data packet header. A service flow includes RTCP data packets and RTP data packets. A UPF network element or user equipment distinguishes whether a data packet is an RTCP data packet or an RTP data packet based on the data type identifier of the data packet, that is, determines whether the data packet is an RTP data packet or an RTCP data packet based on the value corresponding to the 8 bits occupied by the M field of the payload type identifier in the RTP data packet header or the value corresponding to the 8 bits occupied by the packet type identifier in the RTCP data packet header. In one example, if the data type identifier is used to indicate that the data packet is an RTP data packet or RTCP data packet, when the value of the 8 bits corresponding to the data type identifier is a preset value or within a preset range, it indicates that the data packet carrying the 8 bits is an RTP data packet; otherwise, it is an RTCP data packet. When the data type identifier of a data packet corresponds to an 8-bit value representing the payload type identifier and the M field, the UPF network element or user equipment determines that the data packet is an RTP data packet, wherein the payload type identifier and the M field occupy 8 bits in the header of the RTP data packet, the payload type identifier occupies 7 bits, and the M field occupies 1 bit. When the data type identifier of a data packet corresponds to an 8-bit value representing the packet type identifier, the UPF network element or user equipment determines that the data packet is an RTCP data packet, wherein the packet PT identifier occupies 8 bits in the header of the RTCP data packet.

[0179] In one possible implementation, the processing rules are used to:

[0180] The data identifier indicating the data packet includes an identifier indicating that the data packet is an RTP data packet and an SSRC identifier of the data packet.

[0181] or the data identifier indicating the data packet includes an identifier indicating that the data packet is an RTP data packet and a payload type identifier of the data packet,

[0182] Or the data identifier of the data packet is an identifier indicating that the data packet is an RTCP data packet.

[0183] This implementation method targets the following scenarios: when a service flow includes both RTP packets and RTCP packets, and there are multiple RTP packets, the user device or UPF network element determines the type of data packet (RTP packet and RTCP packet) of the service flow based on the data identifier of the data packet in the service flow, and then maps the RTCP packet to the corresponding QoS flow, thereby ensuring that the RTCP packet meets the corresponding QoS requirements; for multiple RTP packets, the user device or target UPF network element further determines the QoS flow corresponding to the RTP packet based on the SSRC identifier or load type identifier carried in the RTP packet, and maps the RTP packet to the QoS flow corresponding to its SSRC identifier or load type identifier.

[0184] It should be pointed out that, for data packets of type RTP data packets, there are two forms of data identification: one is that the data identification includes a load type identifier, an M field, and an SSRC identifier; wherein, the load type identifier and the M field are used to identify the data packet as an RTP data packet, that is, the data packet is determined to be an RTP data packet through the values ​​corresponding to the load type identifier and the M field, and the SSRC identifier is used to further identify the data packet within the range of the RTP data packet; the other is that the data identification includes a load type identifier and an M field, wherein the load type identifier and the M field are used to identify the data packet as an RTP data packet, that is, the data packet is determined to be an RTP data packet through the values ​​corresponding to the load type identifier and the M field, and the load type identifier is used to further identify the data packet within the range of the RTP data packet.

[0185] When the PCF network element obtains multiple PCC rules, it sends them to the SMF network element, so that the SMF network element generates a processing rule for the service flow based on the multiple PCC rules and the flow identifier of the service flow. It should be noted that for user equipment, the processing rule is the QoS rule; for the UPF network element, the processing rule is the N4 rule, which specifically includes the packet detection rule PDR (Packet Detection Rule) and the QoS enforcement rule (QER).

[0186] It should be understood that S402 is executed when the PCF network element supports the capability of performing QoS differentiation processing on data packets in the service flow based on the data identification of the data packets.

[0187] It can be seen that in the solution of this embodiment, the PCF network element generates multiple PCC rules based on multiple data identifiers and the QoS requirement parameters corresponding to each data identifier, and sends the multiple PCC rules to the SMF network element, so that the SMF network element generates service flow processing rules based on multiple PCC rules, and sends the service flow processing rules to the user equipment or UPF network element, and performs corresponding QoS processing on different data packets in the same service flow based on the data identifier.

[0188] It should be understood that the flow identifier in this application has two meanings. One is to distinguish business flows, and the other is to determine whether the data packets in the business flows are subjected to corresponding QoS processing. For example, the data packets carry flow identifiers and data identifiers. After the communication module of the UPF network element or the user equipment obtains the data packet, it determines whether the data packet belongs to a business flow that performs corresponding QoS processing on the data packet based on the flow identifier in the data packet; if it does, the communication module of the UPF network element or the user equipment performs corresponding QoS processing on the data packet based on the data identifier in the data packet.

[0189] See Figure 5, which is a schematic diagram of an interactive flow of a data processing method provided in an embodiment of the present application. The method is applied to the system shown in Figure 1. As shown in Figure 5, the method includes:

[0190] S501. The application function network element sends an AF request to the PCF network element.

[0191] AF requests are used to perform differentiated QoS processing on packets within the same service flow. They include a flow identifier, at least one data identifier, and the QoS requirement parameters corresponding to each data identifier. The flow identifier indicates the service flow, i.e., the flow description information. Specifically, it can be an IP triplet, an IP quintuple, the ToS in the IPv4 header, or a flow label in the IPv6 header.

[0192] In an example, the AF request includes a flow identifier, multiple groups of data identifiers, and QoS requirement parameters corresponding to each group of data identifiers, where each group of data identifiers includes one or more data identifiers.

[0193] In an example, the AF request includes a flow identifier, multiple data identifiers, and a QoS requirement parameter corresponding to each data identifier.

[0194] It should be understood that the data identifier carried in the AF request and the QoS requirement parameter corresponding to the data identifier implicitly instruct the PCF network element to perform corresponding QoS processing on the data packets in the service flow based on the data identifier.

[0195] Optionally, the AF request also includes indication information, which is used to instruct the PCF network element to perform corresponding QoS processing on the data packets in the service flow based on the data identifier, or to instruct the 5GS to perform corresponding QoS processing on the data packets in the service flow based on the data identifier.

[0196] Specifically, the application function network element can be an AF network element in the application server, that is, the application function network element can be a part of the function or a part of the application server, or a functional network element outside the application server, which is not limited here. When the AF network element is in a trusted domain, the AF network element directly sends an AF request to the PCF network element by calling the service interface of the PCF network element. In one example, the service interface of the PCF network element is the Npcf_PolicyAuthorization service interface. When the AF network element is located in a non-trusted domain, the AF network element needs to send an AF request to the PCF network element through the NEF network element. The AF network element calls the service interface of the NEF network element to send an AF request to the NEF network element. In one example, the service interface of the NEF network element is the Nnef_AFSessionWithQoS service interface. The NEF network element calls the service interface of the PCF network element to send an AF request to the PCF network element.

[0197] S502. The PCF network element sends a first response message to the application function network element.

[0198] The first response message is used to respond to the first request.

[0199] When the PCF network element or NEF network element determines, based on its own configuration or perception of 5GS capabilities, that the current 5GS network does not support the ability to perform differentiated QoS processing on data packets in the same service flow based on data identifiers, or that the current 5GS network cannot distinguish different QoS requirements of different data packets in the same service flow based on data identifiers, the first response message carries error indication information, which is used to indicate that the current 5GS network does not support the ability to perform differentiated QoS processing on data packets in the same service flow based on data identifiers, or that the current 5GS network cannot distinguish different QoS requirements of different data packets in the same service flow based on data identifiers. Specifically, the ability to support differentiated QoS processing of data packets based on the data identifiers of the data packets mainly refers to the ability to identify the data identifiers in the data packets and to map the data packets to the corresponding QoS flows based on the data identifiers, or simply refers to the ability to identify the data identifiers in the data packets. When the PCF network element or NEF network element determines, based on its own configuration or perception of 5GS capabilities, that the current 5GS network supports the ability to perform differentiated QoS processing on data packets in the same service flow based on data identification, or that the current 5GS network can distinguish different QoS requirements of different data packets in the same service flow based on data identification, the first response message is used to indicate that differentiated QoS processing can be performed on data packets in the same service flow.

[0200] Optionally, the current 5GS network here includes at least PCF network elements, SMF network elements, UPF network elements, NEF network elements, RAN equipment, and user equipment. The current 5GS network does not support the ability to perform QoS differentiated processing on data packets in the same service flow based on data identification, which means that at least one of the application server, PCF network element, SMF network element, UPF network element, NEF network element, and RAN equipment does not support the ability to perform QoS differentiated processing on data packets in the same service flow based on data identification. The current 5GS network supports the ability to perform QoS differentiated processing on data packets in the same service flow based on data identification, which means that the application server, PCF network element, SMF network element, UPF network element, NEF network element, and RAN equipment all support the ability to perform QoS differentiated processing on data packets in the same service flow based on data identification.

[0201] In one example, the error indication information is a reason value.

[0202] S503: The application function network element performs processing based on the first response message.

[0203] This step is optional.

[0204] Specifically, when the first response message carries error indication information, the application server determines that the current 5GS does not support the ability to perform differentiated QoS processing on data packets in the same service flow based on data identification or the current 5GS network cannot distinguish the different QoS requirements of different data packets in the same service flow based on data identification, and the application server will not multiplex data packets with different QoS requirements into the same service flow. For example, when it is necessary to implement differentiated QoS processing on data packets with different QoS requirements, and the ability to perform differentiated QoS processing on data packets in the same service flow based on data identification is not supported or the current 5GS network cannot distinguish the different QoS requirements of different data packets in the same service flow based on data identification, the application server will put the data packets with the same QoS requirement into the same service flow for transmission.

[0205] S504: The application layer of the user equipment sends an AT command to the communication module of the user equipment.

[0206] It should be noted that the function and information carried by the AT command can be found in the description of the AF request in S501 and will not be described here. The application layer of the user equipment includes the operating system, applications, etc. of the user equipment.

[0207] S505. The communication module of the user equipment sends a second response message to the application layer.

[0208] The second response message is used to respond to the AT command.

[0209] When the communication module of the user equipment determines that the current 5GS network does not support the ability to perform QoS differentiated processing on data packets in the same service flow based on data identification or the current 5GS network cannot distinguish the different QoS requirements of different data packets in the same service flow based on data identification, the second response message carries error indication information, which is used to indicate that the current 5GS network does not support the ability to perform QoS differentiated processing on data packets in the same service flow based on data identification or the current 5GS network cannot distinguish the different QoS requirements of different data packets in the same service flow based on data identification.

[0210] When the communication module of the user equipment determines that the current 5GS network supports the ability to perform differentiated QoS processing on data packets in the same service flow based on data identification, or the current 5GS network cannot distinguish the different QoS requirements of different data packets in the same service flow based on data identification, the second response message is used to indicate that differentiated QoS processing can be performed on data packets in the same service flow.

[0211] S506: The application layer of the user equipment performs processing based on the second response message.

[0212] This step is optional.

[0213] Specifically, when the second response message includes error indication information, the application layer of the user device determines that the current 5GS network does not support the ability to perform differentiated QoS processing on data packets in the same service flow based on data identifiers or the current 5GS network cannot distinguish different QoS requirements of different data packets in the same service flow based on data identifiers, the application layer of the user device will not multiplex data packets with different QoS requirements into the same service flow.

[0214] Here, the current 5GS network does not support the ability to perform QoS differentiated processing on data packets in the same service flow based on data identification, or the current 5GS network cannot distinguish different QoS requirements of different data packets in the same service flow based on data identification, which means that the modem of the user equipment does not support the ability to perform QoS differentiated processing on data packets in the same service flow based on data identification, or cannot distinguish different data packets in the same service flow based on data identification.

[0215] S507. The user equipment sends a first request to the AMF network element.

[0216] This step is optional.

[0217] Specifically, the user equipment sends a first request to the AMF network element. The first request is used to request the creation or modification of a packet data unit (PDU) session between the user equipment and the AMF network element. The first request carries flow description information, which includes a flow identifier, at least one data identifier, and QoS requirement parameters corresponding to each data identifier.

[0218] It should be noted here that S507 is executed when the second response message does not carry error indication information.

[0219] Specifically, the user equipment sends a first request to the AMF network element through the access network device.

[0220] S508. The AMF network element sends a second request to the SMF network element.

[0221] The second request is used to request the creation or modification of a PDU session between an SMF network element and an AMF network element. The second request carries a flow identifier, at least one data identifier, and QoS requirement parameters corresponding to each data identifier.

[0222] S509: The PCF network element generates a PCC rule.

[0223] Specifically, the PCF network element generates at least one PCC rule based on at least one data identifier from the application server or user equipment and the QoS requirement parameters corresponding to each data identifier. A PCC rule includes at least one data identifier and the corresponding QoS requirement parameters corresponding to the same QoS requirement parameters. Specifically, the PCC rule also includes the flow identifier corresponding to the service flow. The PCF network element sends the PCC rule to the SMF network element.

[0224] It should be understood that if the data identification information and the QoS requirement parameters corresponding to the data identification come from the user equipment, S509 is executed after S510; if the data identification and the QoS requirement parameters corresponding to the data identification come from the application function network element, S509 is executed before S510. The data identification and the QoS requirement parameters corresponding to the data identification come from the user equipment. For the PCF network element, the SMF network element obtains the flow identification, at least one data identification and the QoS requirement parameters corresponding to each data identification from the user equipment, and then sends the flow identification, at least one data identification and the QoS requirement parameters corresponding to each data identification to the PCF network element. In one example, the SMF network element sends a third request to the PCF network element, and the third request is used to request the creation or modification of an SM policy association. The third request carries the flow identification, at least one data identification and the QoS requirement parameters corresponding to each data identification.

[0225] S510. The SMF network element performs processing based on the PCC rule.

[0226] Specifically, the SMF network element generates QoS rules, QoS profiles (QoS Profile) and N4 rules based on the PCC rules, and sends the QoS rules, QoS profiles and N4 rules to the user equipment, RAN equipment and UPF network element respectively.

[0227] It should be noted here that the specific description of QoS rules, QoS profiles and N4 rules can be found in the relevant description of processing rules in the embodiments corresponding to Figures 2-4, and will not be described again here.

[0228] Optionally, there may be multiple UPF network elements in the 5GS network, some of which do not support the ability to perform QoS differentiated processing on data packets based on the data identifiers of the data packets, while some support the ability to perform QoS differentiated processing on data packets based on the data identifiers of the data packets. The UPF network element in the N4 rule sent by the SMF network element to the UPF network element is the UPF network element that the SMF network element obtains from multiple UPF network elements and that supports the ability to perform QoS differentiated processing on data packets based on the data identifiers of the data packets.

[0229] S511. The SMF network element binds the PCC rules to different QoS flows.

[0230] It should be understood that there are multiple PCC rules, each corresponding to different QoS requirements. The SMF network element binds different PCC rules to different QoS flows based on information such as QoS requirements, enabling subsequent mapping of data packets to different QoS flows based on data identifiers.

[0231] S512. The SMF network element sends a fourth request to the UPF network element.

[0232] The fourth request is used to request the creation of an N4 session between the SMF network element and the UPF network element. The fourth request carries an N4 rule. The N4 rule includes a flow identifier, a data identifier, and a QoS flow identifier corresponding to the data identifier. The N4 rule is used by the UPF network element to perform corresponding data packet detection and QoS flow mapping based on the data identifier of the downlink data packet.

[0233] S513. The SMF network element sends a third response message to the user equipment.

[0234] The third response message is used to respond to the first request. The third response message is a PDU session creation or modification acceptance message. The third response message carries a QoS rule. Optionally, the QoS rule includes a data identifier and a QoS flow identifier corresponding to the data identifier, which is used by the user equipment to map the uplink data packet to the corresponding QoS flow.

[0235] S514, user equipment, RAN equipment, AMF network element, SMF network element, UPF network element and PCF network element complete the remaining PDU session creation or modification process.

[0236] It should be pointed out here that the specific process of the user equipment, RAN equipment, AMF network element, SMF network element, UPF network element and PCF network element completing the remaining PDU session creation or modification process can be referred to Section 4.3.2.1 of TS23.502 and will not be described here.

[0237] S515. The UPF network element receives the downlink data packet sent by the application server and processes it.

[0238] This step is optional and is for downlink service scenarios.

[0239] Specifically, the UPF network element receives at least one downlink data packet of the same service flow sent by the application server, and detects and obtains the flow identifier and data identifier of each downlink data packet; the UPF network element maps the downlink data packet carrying the data identifier in the service flow to the corresponding QoS flow based on the flow identifier and data identifier, that is, adds the QoS flow identifier corresponding to the data identifier to the corresponding downlink data packet.

[0240] The downlink data packet may be transmitted via RTP, with the data identifier of the downlink data stream carried in the header of the RTP message, or the downlink data packet may be transmitted via RTCP, with the data identifier of the downlink data packet carried in the header of the RTCP message.

[0241] S516: The user equipment processes the uplink data packet.

[0242] This step is optional and is for downlink service scenarios.

[0243] Specifically, the uplink data packet here refers to the data packet sent by the application layer of the user equipment to the communication module. The communication module of the user equipment receives at least one uplink data packet of the same service flow sent by the application layer of the user equipment, and detects and obtains the flow identifier and data identifier of each uplink data packet; based on the flow identifier and data identifier, the UE maps the uplink data packet carrying the data identifier in the service flow to the corresponding QoS flow, that is, adds the QoS flow identifier corresponding to the data identifier to the corresponding uplink data packet.

[0244] S517 : The RAN device performs corresponding QoS processing on different QoS flows.

[0245] The RAN device receives different QoS flows sent by the UPF device or the user equipment. Different QoS flows correspond to different QoS requirements. The RAN device performs corresponding QoS processing on the different QoS flows.

[0246] It can be seen that in the solution of this embodiment, the UPF network element or user equipment can achieve more fine-grained QoS requirement detection of data packets through data identification in mixed media service transmission scenarios, or when RTP packets and RTCP packets are multiplexed in the same service flow, and map the data packets to the corresponding QoS flow based on the data identification for corresponding QoS processing. When RTP packets and RTCP packets are multiplexed in the same service flow, the service transmission quality is improved because the RTP packets and RTCP packets can be identified and mapped to the corresponding QoS flow.

[0247] 6 is a schematic diagram of the structure of a first device provided in an embodiment of the present application. The first device 600 is the UPF network element or user equipment in FIG1 . As shown in FIG6 , the first device 600 includes:

[0248] An acquiring unit 601 is configured to acquire a first data packet and a second data packet in a service flow, where the first data packet includes a flow identifier and a first data identifier of the service flow, and the second data packet includes a flow identifier and a second data identifier of the service flow;

[0249] The processing unit 602 is used to perform QoS flow mapping on the first data packet and the second data packet based on the first data identifier, the second data identifier and the processing rules corresponding to the flow identifier, so as to map the first data packet to the first QoS flow bearer and map the second data packet to the second QoS flow bearer.

[0250] In one possible implementation, the processing unit 602 is specifically configured to:

[0251] The identifier of the first QoS flow is added to the first data packet, and the identifier of the second QoS flow is added to the second data packet, wherein the first data identifier corresponds to the identifier of the first QoS flow, and the second data identifier corresponds to the identifier of the second QoS flow.

[0252] In a possible implementation, the acquiring unit 601 is further configured to:

[0253] Obtain the processing rules of the service flow, which include the data identifier of each data packet in the service flow and the QoS flow identifier corresponding to the data identifier of each data packet; the processing rules of the service flow are used to instruct the UPF network element or user equipment to perform QoS flow mapping on the data packets of the service flow based on the data identifier.

[0254] It should be understood that one QoS flow identifier corresponds to one or more data identifiers.

[0255] In a possible implementation, the processing rule is used to indicate that the data identifier is an SSRC identifier or a payload type identifier.

[0256] In a possible implementation, the processing rule is used to indicate that the data identifier is a data type identifier used to indicate that the data packet is an RTP data packet or an RTCP data packet.

[0257] In one possible implementation, the processing rules are used to:

[0258] The data identifier indicating the data packet includes an identifier indicating that the data packet is an RTP data packet and an SSRC identifier of the data packet.

[0259] Or the data identifier indicating the data packet includes an identifier indicating that the data packet is an RTP data packet and a load type identifier of the data packet,

[0260] Or the data identifier indicating the data packet includes an identifier indicating that the data packet is an RTCP data packet.

[0261] In a possible implementation, the processing rule is generated based on the data identifier and the QoS requirement parameter corresponding to the data identifier.

[0262] In one possible implementation, the first device is a UPF network element or a user equipment. When the first device is a user equipment, the first device further includes:

[0263] The sending unit 603 is used to send the data identifier and the QoS requirement parameter corresponding to the data identifier to the SMF network element or the PCF network element.

[0264] It is worth noting that, for the specific functional implementation of the first device 600, please refer to the specific description of the embodiment shown in Figure 2. For example, the acquisition unit 601 is used to execute the relevant content of S201, and the processing unit 602 and the sending unit 603 are used to execute the relevant content of S202. The various units or modules in the first device 600 can be individually or completely merged into one or several other units or modules to form a structure, or one (or some) of the units or modules can be further divided into multiple functionally smaller units or modules to form a structure, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present invention. The above-mentioned units or modules are divided based on logical functions. In actual applications, the functions of one unit (or module) are implemented by multiple units (or modules), or the functions of multiple units (or modules) are implemented by one unit (or module).

[0265] 7, which is a schematic diagram of the structure of an SMF network element provided in an embodiment of the present application. The SMF network element 700 is the SMF network element in FIG1. ​​The SMF network element 700 includes:

[0266] An acquiring unit 701 is configured to acquire a flow identifier, a first data identifier included in a first data packet of a service flow identified by the flow identifier, a second data identifier included in a second data packet of the service flow identified by the flow identifier, a first QoS requirement parameter corresponding to the first data identifier, and a QoS requirement parameter corresponding to the second data identifier;

[0267] A generating unit 702 is configured to generate a processing rule corresponding to the flow identifier based on the flow identifier, the first data identifier, the second data identifier, the first QoS requirement parameter, and the second QoS requirement parameter;

[0268] A sending unit 703 is configured to send a processing rule corresponding to a flow identifier to a target UPF network element or user equipment, where the processing rule includes a first data identifier and a QoS flow identifier corresponding to the first data identifier, and a second data identifier and a QoS flow identifier corresponding to the second data identifier. The processing rule is configured to instruct the UPF network element or user equipment to perform QoS flow mapping on the data packets of the service flow based on the data identifiers of the data packets of the service flow, so as to map the first data packet to the first QoS flow bearer and the second data packet to the second QoS flow bearer.

[0269] Among them, the target UPF network element is the UPF network element selected by the SMF network element 700 that supports the ability to perform QoS differentiated processing based on data identification.

[0270] In a possible implementation, the processing rule is used to indicate that the data identifier is an SSRC identifier or a payload type identifier.

[0271] In a possible implementation, the processing rule is used to indicate that the data identifier is a data type identifier used to indicate that the data packet is an RTP data packet or an RTCP data packet.

[0272] In one possible implementation, the processing rules are used to:

[0273] The data identifier indicating the data packet includes an identifier indicating that the data packet is an RTP data packet and an SSRC identifier of the data packet.

[0274] Or the data identifier indicating the data packet includes an identifier indicating that the data packet is an RTP data packet and a load type identifier of the data packet,

[0275] Or the data identifier indicating the data packet includes an identifier indicating that the data packet is an RTCP data packet.

[0276] In one possible implementation, in terms of obtaining multiple data identifiers and the QoS requirement parameter corresponding to each data identifier, the obtaining unit 701 is specifically configured to:

[0277] A plurality of PCC rules are obtained, each PCC rule including at least one data identifier and a corresponding QoS requirement parameter having the same corresponding QoS requirement parameter.

[0278] It is worth noting that, for the specific functional implementation of the SMF network element 700, please refer to the specific description of the embodiment shown in Figure 3 above. For example, the acquisition unit 701 is used to execute the relevant content of S301, and the generation unit 702 is used to execute the relevant content of S302. The sending unit 703 is used to execute the relevant content of S303. The various units or modules in the SMF network element 700 can be merged into one or several other units or modules separately or in full, or one (or some) of the units or modules can be further divided into multiple functionally smaller units or modules to constitute, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present invention. The above-mentioned units or modules are divided based on logical functions. In actual applications, the functions of one unit (or module) are implemented by multiple units (or modules), or the functions of multiple units (or modules) are implemented by one unit (or module).

[0279] 8 is a schematic diagram of the structure of a PCF network element provided in an embodiment of the present application. The PCF network element 800 is the PCF network element in FIG1 . The PCF network element 800 includes:

[0280] The receiving unit 801 is configured to receive an application function AF request sent by an application server, where the AF request includes a flow identifier, multiple data identifiers, and a QoS requirement parameter corresponding to each data identifier;

[0281] Generation unit 802 is used to generate multiple PCC rules based on multiple data identifiers and the QoS requirement parameters corresponding to each data identifier, each PCC rule includes at least one data identifier and corresponding QoS requirement parameters with the same corresponding QoS requirement parameters; the flow identifier and multiple PCC rules are used to generate processing rules, the processing rules correspond to the service flow indicated by the flow identifier, the processing rules include multiple data identifiers and the QoS flow identifier corresponding to each data identifier; the processing rules are used to instruct the UPF network element or user equipment to perform QoS flow mapping on the data packets of the service flow based on the data identifier.

[0282] In a possible implementation, the processing rule is used to indicate that the data identifier is an SSRC identifier or a payload type identifier.

[0283] In a possible implementation, the processing rule is used to indicate that the data identifier is a data type identifier used to indicate that the data packet is an RTP data packet or an RTCP data packet.

[0284] In one possible implementation, the processing rules are used to:

[0285] The data identifier indicating the data packet includes an identifier indicating that the data packet is an RTP data packet and an SSRC identifier of the data packet.

[0286] Or the data identifier indicating the data packet includes an identifier indicating that the data packet is an RTP data packet and a load type identifier of the data packet,

[0287] Or the data identifier indicating the data packet includes an identifier indicating that the data packet is an RTCP data packet.

[0288] It is worth noting that, for the specific functional implementation of the PCF network element 800, please refer to the specific description of the embodiment shown in Figure 4 above. For example, the receiving unit 801 is used to execute the relevant content of S401, and the generating unit 802 is used to execute the relevant content of S402. The various units or modules in the PCF network element 800 can be individually or completely merged into one or several other units or modules to form a structure, or one (or some) of the units or modules can be further divided into multiple functionally smaller units or modules to form a structure, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present invention. The above-mentioned units or modules are divided based on logical functions. In actual applications, the functions of one unit (or module) are implemented by multiple units (or modules), or the functions of multiple units (or modules) are implemented by one unit (or module).

[0289] Based on the description of the above method embodiments and related device embodiments, please refer to Figure 9, which shows a schematic structural diagram of a first device 900 provided in an embodiment of the present invention. The first device 900 shown in Figure 9 includes a memory 901, a processor 902, a communication interface 903, and a bus 904. The memory 901, processor 902, and communication interface 903 are connected to each other via bus 904.

[0290] Optionally, the memory 901 is a read-only memory (ROM), a static storage device, a dynamic storage device or a random access memory (RAM).

[0291] The memory 901 can store programs. When the program stored in the memory 901 is executed by the processor 902, the processor 902 and the communication interface 903 are used to execute the various steps of the data processing method of the embodiment shown in FIG. 2 .

[0292] The processor 902 uses a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), a graphics processing unit (GPU) or one or more integrated circuits to execute relevant programs to implement the functions required to be performed by the units in the first device 600 of the embodiment of the present application, or to execute the data processing method of the embodiment shown in Figure 2 of the present application.

[0293] The processor 902 can also be an integrated circuit chip with signal processing capabilities. During implementation, each step of the data processing method shown in FIG. 2 of the present application can be completed by hardware integrated logic circuits or software instructions in the processor 902. Optionally, the processor 902 is a general-purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA), or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The processor 902 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor is a microprocessor or any conventional processor. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. Optionally, the software module is located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, or other mature storage media in the art. The storage medium is located in the memory 901, and the processor 902 reads the information in the memory 901 and combines its hardware to complete the functions required to be performed by the units included in the first device 600 of the embodiment of the present application, or executes the data processing method of the embodiment shown in Figure 2.

[0294] The communication interface 903 uses a transceiver device such as but not limited to a transceiver to implement communication between the first device 900 and other devices (such as the RAN or SMF network element shown in Figure 1) or a communication network.

[0295] The bus 904 may include a path for transmitting information between various components of the first device 900 (eg, the memory 901 , the processor 902 , and the communication interface 903 ).

[0296] It should be noted that although the first device 900 shown in FIG9 only shows a memory, a processor, and a communication interface, in the specific implementation process, those skilled in the art will understand that the first device 900 also includes other components necessary for normal operation. At the same time, according to specific needs, those skilled in the art will understand that the first device 900 may also include hardware components that implement other additional functions. In addition, those skilled in the art will understand that the first device 900 may also include only the components necessary to implement the embodiments of the present application, and does not necessarily include all the components shown in FIG9.

[0297] Based on the description of the above method embodiments and related device embodiments, please refer to Figure 10, which shows a schematic diagram of the structure of an SMF network element 1000 provided in an embodiment of the present invention. The SMF network element 1000 shown in Figure 10 includes a memory 1001, a processor 1002, a communication interface 1003, and a bus 1004. The memory 1001, the processor 1002, and the communication interface 1003 are connected to each other via the bus 1004.

[0298] Optionally, the memory 1001 is a ROM, a static storage device, a dynamic storage device or a RAM.

[0299] The memory 1001 can store programs. When the program stored in the memory 1001 is executed by the processor 1002, the processor 1002 and the communication interface 1003 are used to execute the various steps of the data processing method of the embodiment shown in FIG. 3 .

[0300] The processor 1002 uses a general-purpose CPU, microprocessor, ASIC, GPU or one or more integrated circuits to execute relevant programs to implement the functions required to be performed by the units in the SMF network element 700 of the embodiment of the present application, or to execute the data processing method of the embodiment shown in Figure 3 of the present application.

[0301] Processor 1002 can also be an integrated circuit chip with signal processing capabilities. During implementation, each step of the data processing method shown in Figure 3 of the present application can be completed by hardware integrated logic circuits in processor 1002 or by software instructions. Optionally, processor 1002 is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component. Processor 1002 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of this application. A general-purpose processor is a microprocessor or any conventional processor. The steps of the methods disclosed in conjunction with the embodiments of this application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. Optionally, the software module is located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in the memory 1001, and the processor 1002 reads the information in the memory 1001 and combines its hardware to complete the functions required to be performed by the units included in the SMF network element 700 of the embodiment of the present application, or executes the data processing method of the embodiment shown in Figure 3.

[0302] The communication interface 1003 uses a transceiver device such as but not limited to a transceiver to realize communication between the SMF network element 1000 and other devices (such as UPF network elements and PCF network elements) or communication networks.

[0303] The bus 1004 may include a path for transmitting information between the various components of the SMF network element 1000 (eg, the memory 1001, the processor 1002, the communication interface 1003).

[0304] It should be noted that although the SMF network element 1000 shown in FIG10 only shows a memory, a processor, and a communication interface, in the specific implementation process, those skilled in the art should understand that the SMF network element 1000 also includes other devices necessary for normal operation. At the same time, according to specific needs, those skilled in the art should understand that the SMF network element 1000 may also include hardware devices that implement other additional functions. In addition, those skilled in the art should understand that the SMF network element 1000 may also include only the devices necessary to implement the embodiments of the present application, and does not necessarily include all the devices shown in FIG10.

[0305] Based on the description of the above method embodiments and related device embodiments, please refer to Figure 11 , which provides a schematic structural diagram of a PCF network element 1100 according to an embodiment of the present invention. The PCF network element 1100 shown in Figure 11 includes a memory 1101, a processor 1102, a communication interface 1103, and a bus 1104. The memory 1101, processor 1102, and communication interface 1103 are interconnected via bus 1104.

[0306] Optionally, the memory 1101 is a ROM, a static storage device, a dynamic storage device or a RAM.

[0307] The memory 1101 can store programs. When the program stored in the memory 1101 is executed by the processor 1102, the processor 1102 and the communication interface 1103 are used to execute the various steps of the data processing method of the embodiment shown in FIG. 4 .

[0308] The processor 1102 uses a general-purpose CPU, microprocessor, ASIC, GPU or one or more integrated circuits to execute relevant programs to implement the functions required to be performed by the units in the PCF network element 800 in the embodiment of the present application, or to execute the data processing method of the embodiment shown in Figure 4 of the present application.

[0309] Processor 1102 can also be an integrated circuit chip with signal processing capabilities. During implementation, each step of the data processing method shown in Figure 4 of the present application can be completed by hardware integrated logic circuits in processor 1102 or by software instructions. Optionally, processor 1102 is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component. Processor 1102 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of this application. A general-purpose processor is a microprocessor or any conventional processor. The steps of the methods disclosed in conjunction with the embodiments of this application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. Optionally, the software module is located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in the memory 1101, and the processor 1102 reads the information in the memory 1101 and combines its hardware to complete the functions required to be performed by the units included in the PCF network element 800 of the embodiment of the present application, or executes the data processing method of the embodiment shown in Figure 4.

[0310] The communication interface 1103 uses a transceiver device such as, but not limited to, a transceiver to implement communication between the PCF network element 1100 and other devices (such as PCF network elements, application servers) or communication networks.

[0311] The bus 1104 may include a path for transmitting information between various components of the PCF network element 1100 (eg, the memory 1101 , the processor 1102 , and the communication interface 1103 ).

[0312] It should be noted that although the PCF network element 1100 shown in FIG11 only shows a memory, a processor, and a communication interface, during specific implementation, those skilled in the art will understand that the PCF network element 1100 also includes other components necessary for normal operation. Furthermore, those skilled in the art will understand that the PCF network element 1100 may also include hardware components that implement other additional functions, depending on specific needs. Furthermore, those skilled in the art will understand that the PCF network element 1100 may only include the components necessary to implement the embodiments of the present application, and does not necessarily need to include all of the components shown in FIG11.

[0313] An embodiment of the present application further provides a chip, which includes a processor and a data interface. The processor reads instructions stored in a memory through the data interface to implement the data processing method of the embodiment of the present application.

[0314] Optionally, as an implementation, the chip further includes a memory, in which instructions are stored, and the processor is used to execute the instructions stored in the memory. When the instructions are executed, the processor is used to execute the data processing method.

[0315] An embodiment of the present application also provides a computer-readable storage medium, which stores instructions. When the computer-readable storage medium is executed on a computer or a processor, the computer or processor executes one or more steps in any of the above methods.

[0316] The present application also provides a computer program product comprising instructions, which, when executed on a computer or processor, causes the computer or processor to execute one or more steps in any of the above methods.

[0317] Those skilled in the art will appreciate that the functions described in conjunction with the various illustrative logic blocks, modules, and algorithm steps disclosed herein can be implemented by hardware, software, firmware, or any combination thereof. If implemented in software, the functions described by the various illustrative logic blocks, modules, and steps may be stored or transmitted as one or more instructions or codes on a computer-readable medium and executed by a hardware-based processing unit. Computer-readable media may include computer-readable storage media, which corresponds to tangible media, such as data storage media, or communication media including any media that facilitates the transfer of computer programs from one place to another (e.g., based on a communication protocol). In this manner, computer-readable media may generally correspond to (1) non-transitory tangible computer-readable storage media, or (2) communication media, such as signals or carrier waves. Data storage media may be any available media that can be accessed by one or more computers or one or more processors to retrieve instructions, codes, and / or data structures for implementing the techniques described in this application. A computer program product may include computer-readable media.

[0318] By way of example, and not limitation, such computer-readable storage media include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage, flash memory, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer. Furthermore, any connection is properly referred to as a computer-readable medium. For example, if instructions are transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included in the definition of media. However, it should be understood that the computer-readable storage media and data storage media do not include connections, carrier waves, signals, or other transient media, but are actually directed to non-transitory tangible storage media. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), and Blu-ray disc. Disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also intended to be included within the scope of computer-readable media.

[0319] Instructions may be executed by one or more processors, such as one or more DSPs, general-purpose microprocessors, ASICs, FPGAs, or other equivalent integrated or discrete logic circuits. Thus, the term "processor," as used herein, may refer to any of the aforementioned structures or any other structure suitable for implementing the techniques described herein. Additionally, in some aspects, the functionality described by the various illustrative logical blocks, modules, and steps described herein is provided within dedicated hardware and / or software modules configured for encoding and decoding, or incorporated into a combined codec. Furthermore, the techniques may be fully implemented in one or more circuits or logic elements.

[0320] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the division of the unit is only a logical function division, and there are other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Optionally, the mutual coupling, direct coupling, or communication connection shown or discussed is an indirect coupling or communication connection through some interfaces, devices or units, such as electrical, mechanical or other forms.

[0321] Optionally, the units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, i.e., located in one place, or distributed across multiple network units. Some or all of the units may be selected based on actual needs to achieve the purpose of the solution of this embodiment.

[0322] In the above embodiments, all or part of the embodiments can be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are generated in whole or in part.

[0323] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present invention should be included in the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.

Claims

1. A data processing method, characterized in that: Applied to a first device, the method includes: Acquire a first data packet and a second data packet in a service flow, wherein the first data packet includes a first data identifier and a flow identifier of the service flow, and the second data packet includes a second data identifier and a flow identifier of the service flow; Based on the first data identifier, the second data identifier and the processing rule corresponding to the flow identifier, the first data packet and the second data packet are mapped to a service quality QoS flow, so as to map the first data packet to a first QoS flow bearer and map the second data packet to a second QoS flow bearer.

2. The method according to claim 1, characterized in that The performing QoS flow mapping on the first data packet and the second data packet based on the first data identifier, the second data identifier and a processing rule corresponding to the flow identifier includes: Add the identifier of the first QoS flow to the first data packet, and add the identifier of the second QoS flow to the second data packet, wherein the first data identifier corresponds to the identifier of the first QoS flow, and the second data identifier corresponds to the identifier of the second QoS flow.

3. The method according to claim 1 or 2, characterized in that: The method comprises: Obtain a processing rule corresponding to the flow identifier, wherein the processing rule includes a data identifier of each data packet of the service flow and a QoS flow identifier corresponding to the data identifier of each data packet; the processing rule is used to instruct the first device to perform QoS flow mapping on the data packets of the service flow based on the data identifier.

4. The method according to any one of claims 1 to 3, characterized in that: The processing rule is used to indicate that the data identifier is a synchronization source SSRC identifier or a load type identifier.

5. The method according to any one of claims 1 to 3, characterized in that: The processing rule is used to indicate that the data identifier is a data type identifier used to indicate that the data packet is a real-time transport protocol RTP data packet or a real-time transport control protocol RTCP data packet.

6. The method according to any one of claims 1 to 3, characterized in that: The processing rules are used to: Indicating that the data identifier includes an identifier indicating that the data packet is an RTP data packet and an SSRC identifier including the data packet, or indicating that the data identifier includes an identifier indicating that the data packet is an RTP data packet and a load type identifier of the data packet, Or the data identifier is an identifier indicating that the data packet is an RTCP data packet.

7. The method according to any one of claims 1 to 6, characterized in that: The processing rule is generated based on the data identifier and the QoS requirement parameter corresponding to the data identifier.

8. The method according to any one of claims 1 to 7, characterized in that: The first device user equipment, the method further includes: The data identifier and the QoS requirement parameter corresponding to the data identifier are sent to the session management function SMF network element or the policy control function PCF network element.

9. A data processing method, characterized in that: Applied to a session management function (SMF) network element, the method comprises: Obtain a flow identifier, a first data identifier included in a first data packet of a service flow identified by the flow identifier, a second data identifier included in a second data packet of the service flow identified by the flow identifier, a first service quality QoS requirement parameter corresponding to the first data identifier, and a second QoS requirement parameter corresponding to the second data identifier; generating a processing rule corresponding to the flow identifier according to the flow identifier, the first data identifier, the second data identifier, the first QoS requirement parameter, and the second QoS requirement parameter; The processing rules are sent to the user plane function UPF network element or user equipment, and the processing rules are used to perform QoS flow mapping on the data packets of the service flow based on the data identifiers of the data packets of the service flow, so as to map the first data packet to the first QoS flow bearer and map the second data packet to the second QoS flow bearer.

10. The method according to claim 9, characterized in that The processing rule is used to indicate that the data identifier is a synchronization source SSRC identifier or a load type identifier.

11. The method according to claim 9, characterized in that The processing rule is used to indicate that the data identifier is a data type identifier used to indicate that the data packet is a real-time transport protocol RTP data packet or a real-time transport control protocol RTCP data packet.

12. The method according to claim 9, characterized in that The processing rules are used to: Indicating that the data identifier includes an identifier indicating that the data packet is an RTP data packet and an identifier of a synchronization source SSRC of the data packet, or indicating that the data identifier includes an identifier indicating that the data packet is an RTP data packet and a load type identifier of the data packet, Or the data identifier is an identifier indicating that the data packet is an RTCP data packet.

13. The method according to any one of claims 9 to 12, characterized in that: The obtaining of multiple data identifiers and QoS requirement parameters corresponding to each of the data identifiers includes: A plurality of PCC rules are obtained, each of the PCC rules including at least one data identifier and a corresponding QoS requirement parameter having the same corresponding QoS requirement parameter.

14. The method according to any one of claims 9 to 12, characterized in that: The target UPF network element is a UPF network element selected by the SMF network element that supports the capability of performing QoS differentiated processing based on the data identifier.

15. A data processing method, characterized in that: Applied to a policy control function (PCF) network element, the method comprises: Receive an application function AF request sent by an application server, where the AF request includes a flow identifier, multiple data identifiers, and a service quality QoS requirement parameter corresponding to each data identifier; Generate multiple PCC rules based on the multiple data identifiers and the QoS requirement parameters corresponding to each of the data identifiers, each of the PCC rules including at least one of the data identifiers and the corresponding QoS requirement parameters with the same corresponding QoS requirement parameters; The flow identifier and the multiple PCC rules are used to generate processing rules, the processing rules correspond to the service flow indicated by the flow identifier, and the processing rules include multiple data identifiers and a QoS flow identifier corresponding to each data identifier; the processing rules are used to instruct the user plane function UPF network element or user equipment to perform QoS flow mapping on the data packets of the service flow based on the data identifier.

16. The method according to claim 15, characterized in that The processing rule is used to indicate that the data identifier is a synchronization source SSRC identifier or a load type identifier.

17. The method according to claim 15, characterized in that The processing rule is used to indicate that the data identifier is a data type identifier used to indicate that the data packet is a real-time transport protocol RTP data packet or a real-time transport control protocol RTCP data packet.

18. The method according to claim 15, characterized in that The processing rules are used to: Indicating that the data identifier includes an identifier indicating that the data packet is an RTP data packet and an identifier of a synchronization source SSRC of the data packet, or indicating that the data identifier includes an identifier indicating that the data packet is an RTP data packet and a load type identifier of the data packet, Or indicating that the data identifier indicates that the data packet is an RTCP data packet.

19. The method according to claim 15, characterized in that The method further comprises: A first response message is sent to the application server, where the first response message includes indication information for indicating that the capability of identifying the data identifier is not supported.

20. The method according to claim 19, characterized in that The first response message is sent when it is determined that the UE or the UPF network element does not support the capability of identifying the data identifier.

21. A first device, characterized in that: The first device includes a unit or a module implementing any one of claims 1-8.

22. A session management function SMF network element, characterized in that: The SMF network element includes a unit or module implementing any one of claims 9-14.

23. A policy control function PCF network element, characterized in that: The PCF network element includes a unit or module implementing any one of claims 15-20.

24. A data processing method, characterized in that: The method is applied to a communication system, the communication system comprising a user equipment, a user plane function UPF network element, a session management function SMF network element and an application server, and the method comprises: The SMF network element obtains a flow identifier from the user equipment or the application server, a first data identifier included in a first data packet of a service flow identified by the flow identifier, a second data identifier included in a second data packet of the service flow identified by the flow identifier, a first service quality QoS requirement parameter corresponding to the first data identifier, and a second QoS requirement parameter corresponding to the second data identifier; The SMF network element generates a processing rule corresponding to the flow identifier according to the flow identifier, the first data identifier, the second data identifier, the first QoS requirement parameter, and the second QoS requirement parameter; the processing rule is used to instruct the UPF network element or user equipment to perform QoS flow mapping on the data packets of the service flow based on the data identifier; the processing rule includes the first data identifier and the QoS flow corresponding to the first data identifier and the second data identifier and the QoS flow corresponding to the second data identifier; The SMF network element sends the processing rule to the UPF network element or the user equipment, The application server sends the first data packet and the second data packet to the UPF network element, or the user equipment obtains the first data packet and the second data packet; The UPF network element or the user equipment performs service quality QoS flow mapping on the first data packet and the second data packet based on the first data identifier, the second data identifier and the processing rule corresponding to the flow identifier, so as to map the first data packet to the first QoS flow bearer and map the second data packet to the second QoS flow bearer.

25. A communication system, characterized in that: The communication system includes a user equipment, a user plane function UPF network element, a session management function SMF network element and an application server, The SMF network element is used to obtain the flow identifier from the user equipment or the application server, the business a first data packet of a service flow including a first data identifier, a second data packet of a service flow identified by the flow identifier including a second data identifier, a first service quality QoS requirement parameter corresponding to the first data identifier, and a second QoS requirement parameter corresponding to the second data identifier; The SMF network element is further used to generate a processing rule corresponding to the flow identifier according to the flow identifier, the first data identifier, the second data identifier, the first QoS requirement parameter, and the second QoS requirement parameter; the processing rule is used to instruct the UPF network element or user equipment to perform QoS flow mapping on the data packet of the service flow based on the data identifier; the processing rule includes the first data identifier and the QoS flow corresponding to the first data identifier and the second data identifier and the QoS flow corresponding to the second data identifier; The SMF network element is further used to send the processing rule to the UPF network element or the user equipment, The application server sends the first data packet and the second data packet to the UPF network element, or the user equipment is used to obtain the first data packet and the second data packet; The UPF network element or the user equipment is used to perform service quality QoS flow mapping on the first data packet and the second data packet based on the first data identifier, the second data identifier and the processing rule corresponding to the flow identifier, so as to map the first data packet to the first QoS flow bearer and map the second data packet to the second QoS flow bearer.

26. A first device, characterized in that: The method comprises a processor and a memory, wherein the memory is used to store program codes, and the processor is used to execute the program codes to implement the method according to any one of claims 1 to 8.

27. A session management function SMF network element, characterized in that: The method comprises a processor and a memory, wherein the memory is used to store program codes, and the processor is used to execute the program codes to implement the method according to any one of claims 9 to 14.

28. A policy control function PCF network element, characterized in that: The method comprises a processor and a memory, wherein the memory is used to store program codes, and the processor is used to execute the program codes to implement the method according to any one of claims 15 to 20.

29. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 20 is implemented.

Images